The authoritative guide to UAE Federal Tax Authority e-Invoicing: PEPPOL four-corner network, PINT AE XML specifications, ASP certification, TallyPrime configuration steps, compliance timeline and penalty framework.
The United Arab Emirates Federal Tax Authority (FTA) has formally mandated structured electronic invoicing for all VAT-registered businesses conducting B2B and B2G transactions. The UAE e-Invoicing framework is built on the internationally recognised PEPPOL four-corner network, adapted with a locally-developed XML schema called PINT AE (PEPPOL International Invoice — Arabian Emirates).
Unlike KSA ZATCA's centralised clearance model, the UAE has opted for a decentralised exchange architecture. Invoices are not submitted to a government portal before delivery. Instead, they are exchanged directly between trading partners via their respective certified Access Service Providers (ASPs), while the FTA receives data feeds from ASPs for tax monitoring purposes.
This distinction matters significantly for TallyPrime configuration and ERP integration design. UAE PEPPOL compliance requires real-time API connectivity between TallyPrime and the business's selected ASP — with PINT AE XML generated, signed and transmitted automatically at the point of invoice issuance.
All UAE-registered VAT taxable persons issuing B2B and B2G invoices must comply. This includes mainland companies, free zone entities transacting with UAE VAT-registered counterparties, and foreign businesses with UAE VAT registration. B2C transactions and exports may follow separate regulatory guidance to be issued by the FTA closer to the enforcement deadline.
Businesses most urgently in scope include high-invoice-volume sectors: trading and distribution, logistics and freight forwarding, construction and contracting, manufacturing, professional services, and financial services — particularly those based in Dubai, Abu Dhabi, Sharjah and the Northern Emirates.
TallyPrime natively supports UAE e-Invoicing and is being listed as a certified solution on the UAE FTA website. TallyPrime already supports ZATCA Phase 2 e-Invoicing for KSA, and its UAE PEPPOL PINT AE capability is now following the same path. Businesses using TallyPrime are therefore well-positioned — the core software capability is in place. What remains essential is expert advisory to correctly configure TallyPrime for your specific business, complete ASP onboarding, validate PINT AE XML output end-to-end, and ensure a compliant go-live well before January 2027 enforcement begins.
| Regulation | UAE FTA e-Invoicing Mandate |
| Network | PEPPOL Four-Corner Model |
| Format | PINT AE XML |
| Intermediary | Certified UAE ASP |
| Enforcement | January 2027 |
| Scope | B2B + B2G transactions |
| VAT Rate | 5% standard |
| Coverage | All 7 Emirates |
📅 Phased ASP onboarding begins in 2026. Businesses must select, contract with and integrate a certified UAE ASP before enforcement begins. Allow a minimum of 6–9 months for TallyPrime configuration, ASP integration and UAT.
PINT AE is not a minor variation of a standard invoice. It is a formally specified XML schema with mandatory fields, conditional fields, UAE-specific code lists and strict validation logic. TallyPrime configuration must produce 100% schema-valid PINT AE output before any live submission.
Both seller and buyer party blocks in PINT AE XML must include UAE Tax Registration Numbers (TRN), legal name in English and Arabic, full address including emirate and country code. Missing or malformed party identifiers are among the most common validation rejection causes. TallyPrime ledger master data must be structured to feed these fields correctly.
Each PINT AE invoice must carry a globally unique UUID (IBT-013), issue date and time in UTC, invoice type code (380 for standard, 381 for credit note, 383 for debit note), currency code, document reference and a structured seller reference. The invoice type code must map precisely to the transaction type configured in TallyPrime.
PINT AE requires VAT to be declared at both line level and document level. Each invoice line must include taxable amount, VAT category code (S for standard, Z for zero-rated, E for exempt), VAT rate and calculated VAT amount. TallyPrime VAT ledger configurations must be mapped precisely to PINT AE VAT category codes and rate values.
PINT AE invoices must carry a valid digital signature applied by the transmitting ASP before delivery to the buyer's network. Businesses do not sign invoices directly — the ASP applies the signature as part of the PEPPOL transmission process. However, TallyPrime must transmit the invoice to the ASP in the correct format to trigger valid signing.
PINT AE includes mandatory Arabic language fields for party names and addresses where the legal registered name is in Arabic. TallyPrime must store and output Arabic text fields in proper UTF-8 encoding to pass PINT AE validation. This is a frequently underestimated configuration challenge for businesses with Arabic trading partner names.
PINT AE requires structured document totals including sum of invoice lines, allowances/charges at document level, taxable amount per VAT category, total VAT amount and payable amount. All figures must be mathematically consistent and validated against line-level amounts. TallyPrime rounding configurations can cause total-level validation failures if not precisely configured.
Dubai businesses investing in UAE PEPPOL PINT AE compliance now avoid enforcement risk, protect VAT input credit claims and build resilient B2B invoice infrastructure. January 2027 is less than 12 months away for most planning cycles.
Our TallyPrime advisory team handles every stage: PINT AE schema mapping, ASP selection and onboarding, API integration, UAT validation and go-live governance. We serve Dubai, Abu Dhabi, Sharjah and all UAE from our Office in Mankhool, Dubai.
Achieving UAE e-Invoicing compliance from TallyPrime requires structured planning across six stages. Businesses starting this process in 2026 have a viable path to January 2027 go-live — but the window is narrowing.
Identify every B2B and B2G invoice flow in your business — by legal entity, invoice type (standard, credit note, debit note, self-billing), trading partner category and monthly volume. Document current TallyPrime invoice output format and identify all data fields currently populated. This baseline mapping determines the scope of PINT AE gap analysis and configuration effort required.
Map every current TallyPrime data field against PINT AE mandatory and conditional elements. Identify gaps: missing party TRN fields, absent Arabic name fields, incorrect VAT category codes, rounding configuration mismatches, incomplete address structures. Remediate TallyPrime master data — ledger masters, stock item masters, company details — before any XML configuration work begins. Data quality upstream determines XML quality downstream.
Evaluate UAE FTA-certified Access Service Providers against your invoice volume, technical integration capability, sector experience, SLA requirements and pricing. Key criteria: API documentation quality, sandbox environment availability, support responsiveness and experience with TallyPrime integrations. Execute commercial agreements, obtain API credentials and configure sandbox connectivity. Delays in ASP contracting are the most common cause of project schedule slippage.
Configure TallyPrime to generate schema-valid PINT AE XML: field mapping, UUID generation logic, Arabic text encoding, VAT line-level and header-level calculation precision, document total validation, invoice type code mapping. Develop and test ASP API integration layer — handling authentication, invoice submission, ASP response processing, rejection handling and resubmission workflow. This stage requires both TallyPrime technical expertise and API development capability.
Execute structured UAT against the full PINT AE validation rule set and the selected ASP's acceptance criteria. Test positive scenarios (valid standard invoices, credit notes, zero-rated lines, exempt lines) and negative scenarios (rejected invoices, field-level validation failures, network errors). Validate Arabic language output, multi-currency handling, allowance and charge structures, and batch submission behaviour. Document all test evidence for audit and governance purposes.
Establish compliance governance framework: exception handling procedures, invoice rejection escalation workflow, monitoring dashboards, audit documentation standards and regulatory change management process. Train finance, accounts payable and IT operations teams. Execute controlled go-live with limited transaction volume before full production cutover. Implement post-go-live monitoring for ASP transmission success rates and validation error trends.
Non-compliance with UAE FTA PEPPOL e-Invoicing mandates creates compounding legal, financial and operational risk. The FTA has broad enforcement authority under the UAE Tax Procedures Law.
From January 2027, invoices not transmitted via PEPPOL PINT AE through a certified UAE ASP will be legally non-compliant. Trading partners — particularly government entities and large corporates — may reject non-PEPPOL invoices entirely, blocking payment and disrupting cash flow. In B2G transactions, contract compliance requirements may mandate PEPPOL from day one of enforcement.
UAE VAT law requires that invoices meet prescribed conditions to support input tax credit claims. Non-compliant invoices that fail to meet FTA e-Invoicing requirements may be challenged during VAT audits, resulting in disallowed input credits, VAT assessments and associated penalties. For high-volume procurement businesses in Dubai, this exposure can be material.
The UAE Tax Procedures Law provides the FTA with authority to impose financial penalties for failures to comply with prescribed invoicing requirements. While specific penalty amounts for PEPPOL non-compliance are subject to FTA guidance, the general penalty framework includes fixed and percentage-based charges that scale with invoice volume and duration of non-compliance.
Businesses unable to demonstrate PEPPOL-compliant invoice exchange in their FTA audit trail face elevated risk of full VAT audit investigation. The FTA's access to ASP data feeds means non-compliant businesses will be identifiable from tax authority data without the need for business self-disclosure or third-party reporting.
Major Dubai-based buyers and government procurement entities are expected to update supplier agreements to require PEPPOL-compliant invoicing. Suppliers who cannot deliver PINT AE invoices risk contract termination, delisting from approved supplier registers, or exclusion from tendering processes — particularly in construction, logistics and government-linked sectors.
Businesses that delay UAE PEPPOL readiness until Q4 2026 face sharply escalating advisory and implementation costs as demand for qualified consultants and ASP onboarding capacity peaks. Rushed implementations also increase the risk of configuration errors, failed UAT and delayed go-live — with no buffer before January 2027 enforcement begins.
The most important questions from UAE businesses preparing for FTA PEPPOL PINT AE compliance — answered with regulatory precision.
Our Dubai-based advisory team evaluates your TallyPrime setup and ASP readiness against FTA PINT AE requirements.
Request Assessment