Country deep dive
The UAE built its e-invoicing framework unusually methodically — data dictionary consultation, then legislation, then ASP accreditation, then a voluntary pilot, all before the mandate itself begins.
The UAE's localised Peppol PINT specification is opened for stakeholder feedback, with updated versions following as input is integrated.
The Ministry of Finance formally adopts PINT AE as the UAE Data Dictionary and sets out the Electronic Invoicing System and its implementation, under the authority of Federal Decree-Law No. 8 of 2017 on VAT.
The MoF publishes its first list of accredited service providers, expanding progressively as more providers complete accreditation.
Six specific e-invoicing violation categories are defined with fixed penalties, alongside Cabinet Decision No. 129 of 2025, which separately revises penalties across the broader UAE tax framework — creating potential "dual penalty exposure."
Voluntary participation opened ahead of the mandate, letting businesses test Accredited Service Provider (ASP) connectivity and the PINT AE invoice format risk-free before penalties apply.
Businesses with revenue of AED 50 million or more must have appointed an Accredited Service Provider (ASP) ahead of the January 2027 go-live (deadline extended from 31 July 2026).
Structured e-invoicing becomes mandatory for large businesses, transmitted through an ASP over the Peppol network in PINT AE format, with a real-time copy reported to the FTA.
The e-invoicing mandate broadens to cover all remaining VAT-registered businesses for B2B/B2G transactions, with G2B/B2G-specific obligations following from October 2027.
PINT AE is a genuinely large specification — over 135 data elements, layered deliberately to balance global Peppol interoperability with UAE-specific VAT rules.
PINT AE is a localised extension, not a wholly separate schema — businesses already familiar with Peppol PINT elsewhere have a genuine head start.
This layered design is exactly what preserves baseline interoperability across the global Peppol network while still enforcing UAE-specific VAT rules.
Missing or incorrectly formatted mandatory fields cause outright rejection with no manual override — there's no partial acceptance or manual correction step at the ASP layer.
PDFs, scanned documents, and paper invoices are explicitly not valid under the mandate — only structured XML/JSON generated to PINT AE counts.
The UAE's "5-corner" DCTCE model bundles Peppol-style exchange with automatic tax reporting — there's no separate VAT filing step for e-invoiced transactions.
Your ERP only needs to generate the underlying invoice data — the ASP handles conversion, signing, and delivery, but that division of labour means choosing the right ASP genuinely matters.
Always verify a provider's accreditation against the MoF's official public register directly — don't rely on a provider's own marketing claim of accreditation.
This is the defining contrast with Saudi Arabia next door: there's no government clearance portal to upload to — everything routes through your accredited service provider.
Every invoice passes through all five in sequence:
Corner 5 (the FTA) receives a Tax Data Document (TDD) report from both ASPs automatically — tax data flows to the authority with every invoice exchanged, with no separate VAT reporting step required.
Don't assume your ASP alone handles everything — internal IT and finance alignment is explicitly called out as a common gap.
Check the MoF's official public register directly to confirm Peppol connectivity and current accreditation status before signing anything.
Map your invoicing data to PINT AE / UBL structures — this is foundational work that needs to happen regardless of which ASP you choose.
Build a resilient connection to the UAE e-invoicing rails rather than a fragile point solution — this is infrastructure you'll depend on continuously, not a one-time filing.
Develop structured test cases covering invoices, credit notes, cancellations, and unusual VAT scenarios (reverse charge, free zone supplies) — don't wait for a finished product to start testing.
Define master data ownership, exception workflow procedures, archiving policy, and compliance monitoring — these are organisational decisions your ASP can't make for you.
Large businesses: appoint well ahead of 30 October 2026. Late or emergency ASP onboarding carries a real cost premium beyond the standard implementation rate.
Cabinet Decision No. 106 of 2025 defines six specific violation categories — some capped monthly, others accumulating daily without limit.