E-invoicing in United Arab Emirates

01Executive overview

The UAE is implementing one of the most modern e-invoicing regimes globally: a decentralised five-corner model (DCTCE) built on the international Peppol network, with near-real-time reporting of tax data to the Federal Tax Authority. From 2027, unstructured invoices — including PDFs sent by email — cease to qualify as valid invoices for in-scope transactions.

The framework was cemented in law in 2025 through Ministerial Decisions 243 and 244 and Cabinet Decision 106 (penalties). The voluntary pilot phase opened on 1 July 2026. The defining feature for businesses: you cannot comply alone — every business must appoint an FTA-Accredited Service Provider (ASP), and readiness depends far more on data quality and process change than on the ASP contract itself.

02At a glance

03Legal basis & authority

The legislative package comprises Federal Decree-Law No. 16 of 2024 (amending the VAT law to recognise e-invoicing), Ministerial Decision No. 243 of 2025 (the e-invoicing system and obligations), Ministerial Decision No. 244 of 2025 (implementation timeline and waves), and Cabinet Decision No. 106 of 2025 (administrative penalties). The Ministry of Finance owns the framework and accredits service providers; the Federal Tax Authority administers compliance and receives the reported tax data.

A June 2026 rulebook update (v1.1) added treatment for advance payments and retention billing — significant for construction and real estate, where e-invoices must reflect only the net amount payable at each billing event.

04Timeline

• H2 2024Framework announcedVAT law amended to recognise e-invoicing; DCTCE model confirmed.
• 2025Legal package issuedMD 243 & 244 and Cabinet Decision 106 published; ASP accreditation opens (32+ ASPs approved by mid-2026).
• 1 Jul 2026Pilot phase opensVoluntary onboarding and live testing begin. No penalties apply during the pilot.
• 30 Oct 2026Wave 1 ASP deadlineBusinesses with revenue ≥ AED 50M must have appointed their ASP (extended from 31 July 2026).
• 1 Jan 2027Wave 1 go-liveE-invoicing mandatory for businesses with revenue ≥ AED 50M.
• 1 Jul 2027Wave 2 go-liveMandatory for all other VAT-registered businesses.
• 1 Oct 2027Government entitiesB2G issuance obligations for government bodies.
• 1 Jan 2029Intra-group transition endsTransactions within corporate groups fully in scope.

05Who and what is in scope

The mandate covers B2B and B2G transactions of any person conducting business in the UAE — notably including businesses that are not VAT-registered, which must obtain a Tax Identification Number (TIN). For existing registrants the TIN is the first ten digits of the TRN.

06How the system works

The UAE uses the five-corner model: (1) the supplier creates invoice data in its own system; (2) the supplier’s ASP validates it against PINT AE rules and converts it to the required XML; (3) the buyer’s ASP receives it over the Peppol network; (4) the buyer receives the invoice into its system; (5) tax data flows from the ASPs to the FTA in near real time. Both trading partners therefore need an ASP — and each legal entity appoints a single ASP for both inbound and outbound flows.

This differs fundamentally from clearance models (Italy, Poland, Saudi Arabia): the invoice is not pre-approved by the state before it can be sent, but validation failures at the ASP still block transmission, and the FTA will cross-reference reported data against VAT returns and corporate tax filings.

07Invoice content requirements

PINT AE defines 135+ data elements across 16 use cases (standard, zero-rated, reverse charge, free zone, exports, credit notes, and more). A standard tax invoice carries 51 mandatory fields across six categories:

• Invoice details (9) — number, type code, issue date (YYYY-MM-DD), currency, use-case identifiers
• Seller (11) — legal name, address, 15-digit TRN, contact details
• Buyer (9) — legal name, address, TRN
• Document totals (5) — net, VAT, gross; header must equal sum of lines
• Tax breakdown (4) — per-rate taxable amount and VAT, category codes
• Line items (13) — description, quantity, unit price, net, tax category per line

Key validation traps: VAT amounts must be stated in AED using Central Bank rates even for foreign-currency invoices; dates must be ISO-formatted; free zone and place-of-supply flags are UAE-specific extensions that generic Peppol implementations miss.

08Penalties & enforcement

Cabinet Decision 106 of 2025 sets the penalty framework. Beyond fines, the deeper exposure is data: e-invoicing gives the FTA a transaction-level view it will reconcile against VAT and corporate tax filings.

09Common pitfalls

10What leading businesses are doing

11Your action plan

1. Confirm your wave and diarise your deadline (revenue ≥ AED 50M → 1 Jan 2027; ASP appointed by 30 Oct 2026)
2. Run a field-level gap analysis against PINT AE for your actual transaction types
3. Launch a buyer master-data campaign (TRNs, legal names, addresses)
4. Shortlist and appoint an ASP from the official MoF list; contract for testing time
5. Map complex scenarios: free zone, exports, FX, intra-group, advances/retention
6. Stand up rejection-handling and FTA-notification processes with named owners
7. Join the pilot phase and run end-to-end tests before your wave

12Sources

• Ministerial Decision No. 243 of 2025 (E-Invoicing System)
• Ministerial Decision No. 244 of 2025 (Implementation timeline)
• Cabinet Decision No. 106 of 2025 (Penalties)
• UAE Ministry of Finance — eInvoicing programme & accredited ASP list (mof.gov.ae)
• PINT AE specification & UAE Data Dictionary
• FTA guidance on TIN issuance