UAE e-invoicing law (regulatory framework)
The UAE e-invoicing law explained: Federal Decree-Laws 16 and 17 of 2024, Ministerial Decisions 243, 244, 64, penalties, and deadlines. Read the full reference.
What is the UAE e-invoicing law?
The UAE e-invoicing law is the package of federal decree-laws, cabinet decisions, and ministerial decisions that makes structured electronic invoicing mandatory in the UAE. It covers VAT amendments, tax procedure changes, the 5-corner DCTCE model, ASP appointment, the PINT AE format, and the penalty regime under Cabinet Decision 106 of 2025.
The legal stack at a glance
The framework is not one document. It is a layered stack. The decree-laws sit at the top. The cabinet decisions sit below them. The ministerial decisions handle the operational detail. Each layer references the one above it.
You need to read the stack as a whole. A single article in a ministerial decision can shift a deadline by three months. The October 30, 2026 ASP appointment date moved exactly that way.
| Instrument | What it does | Year |
|---|---|---|
| Federal Decree-Law 16 of 2024 | Amends the VAT law to recognise electronic invoices and credit notes | 2024 |
| Federal Decree-Law 17 of 2024 | Amends the tax procedures law for e-invoicing data handling | 2024 |
| Cabinet Decision 106 of 2025 | Sets administrative penalties from AED 2,500 to AED 50,000 per invoice | 2025 |
| Ministerial Decision 243 of 2025 | Defines the e-invoicing system, PINT AE, and the 5-corner model | 2025 |
| Ministerial Decision 244 of 2025 | Sets and later amends ASP appointment and go-live dates | 2025 |
| Ministerial Decision 64 of 2025 | Governs ASP accreditation criteria and obligations | 2025 |
Federal Decree-Law 16 of 2024: the VAT amendment
This is the foundation. It amends Federal Decree-Law 8 of 2017 (the VAT law) to give legal status to the electronic tax invoice and the electronic tax credit note. Before this amendment, a paper or PDF invoice was the default. After it, the structured electronic invoice is the default for in-scope taxpayers.
The decree-law also changes how invoice issuance dates are calculated. The clock starts when the invoice is reported to the FTA (Federal Tax Authority) through an Accredited Service Provider, not when it leaves your ERP.
Why this matters for your VAT return
Input VAT recovery now depends on the buyer holding a valid electronic invoice. A PDF copy is not enough. If your supplier fails to report through an ASP, you lose the right to recover that input VAT until they fix it. For more on this shift, see the PDF invoice vs UAE e-invoice comparison.
Federal Decree-Law 17 of 2024: tax procedures
This amendment updates Federal Decree-Law 28 of 2022, the tax procedures law. It gives the FTA the authority to receive, store, and audit electronic invoice data in real time through the 5-corner DCTCE network. It also extends the record retention period for structured invoice data.
The decree-law specifies that the taxpayer remains liable for the accuracy of the invoice even when an ASP transmits it. You cannot push blame down to the provider. The legal record is what the FTA receives.
Cabinet Decision 106 of 2025: the penalty regime
This is the part finance teams remember. Cabinet Decision 106 sets out the administrative penalties for non-compliance. Fines run from AED 2,500 to AED 50,000 per invoice depending on the violation.
Penalty bands
| Violation | Fine per invoice |
|---|---|
| Failure to issue an electronic invoice when required | AED 2,500 |
| Issuing an invoice in the wrong format | AED 5,000 |
| Failure to transmit through an appointed ASP | AED 10,000 |
| Repeated violations within 24 months | Up to AED 20,000 |
| Falsifying or omitting required data | Up to AED 50,000 |
The numbers compound. A mid-size business issuing 500 invoices a month that fails the format requirement faces AED 2.5M in exposure inside a single quarter. Read the full breakdown on UAE e-invoicing penalties.
Ministerial Decision 243 of 2025: the technical rulebook
MD 243 is where the technology gets defined. It names the PINT AE format (Peppol International Invoice, UAE specialisation) as the only acceptable structured format. It also confirms the 5-corner DCTCE model as the transmission architecture.
What PINT AE requires
PINT AE is built on UBL 2.1 (Universal Business Language). Every invoice must carry:
- Supplier TRN (Tax Registration Number) and buyer TRN where applicable
- Line-level VAT breakdown by rate
- A unique invoice identifier issued by the supplier
- The IRN (Invoice Reference Number) returned by the FTA after validation
- A digital signature applied by the sending ASP
The format is non-negotiable. A PDF attachment alongside the XML is allowed for human readability, but the XML is the legal record. Full technical detail sits in the Peppol PINT-AE format reference.
The 5-corner model defined
MD 243 also formalises the 5-corner model. The five corners are the supplier, the supplier's ASP, the FTA, the buyer's ASP, and the buyer. The FTA sits in the middle as the fifth corner, receiving every invoice in near real time. This is what DCTCE (Decentralized Continuous Transaction Control and Exchange) means in practice. See the Peppol 5-corner model page for the diagram.
Ministerial Decision 244 of 2025: the timeline
MD 244 sets the dates. It was amended in late 2025 to extend the ASP appointment deadline. The current deadlines are:
- Q2 2026: pilot phase opens for volunteer taxpayers and ASPs
- October 30, 2026: deadline to appoint an Accredited Service Provider for Phase 1 (taxpayers with AED 50M+ annual turnover)
- January 1, 2027: mandatory go-live for Phase 1 taxpayers
- July 1, 2027: mandatory go-live for SMEs under AED 50M turnover
- October 1, 2027: mandatory go-live for government entities
The full sequence is laid out on the UAE e-invoicing timeline page.
Ministerial Decision 64 of 2025: ASP accreditation
MD 64 governs who can become an ASP. It sets capital requirements, technical certifications, security obligations, and ongoing reporting duties. The MoF (Ministry of Finance) has so far pre-approved 32 ASPs. The list is published on the official portal and updated as new providers complete accreditation.
What an ASP must do
- Validate every invoice against the PINT AE schema before transmission
- Apply a qualified digital signature
- Transmit to the FTA within the required window
- Deliver the invoice to the buyer's ASP through the Peppol network
- Retain transmission logs for the statutory period
- Notify the taxpayer of any rejection within minutes
Choosing the right partner is a board-level decision. The UAE accredited service provider guide walks through the selection criteria.
Scope: who the law actually covers
The law applies to all VAT-registered businesses in the UAE, including free-zone entities that issue invoices to mainland customers. It also covers government bodies in their B2B and B2G transactions.
Free zones
Designated free zones and qualifying free zones are inside the scope. The 0% corporate tax status of a qualifying free zone does not exempt it from e-invoicing. Free-zone exporters still need to issue PINT AE invoices where the buyer is in the UAE. See e-invoicing for free-zone companies for the detail.
Cross-border transactions
Imports and exports follow specific rules. Reverse charge mechanism transactions stay inside the system but are flagged with a specific VAT code. The reverse charge mechanism page covers the line-item treatment.
Documents the law makes mandatory
The law covers more than the standard sales invoice. The full list of mandatory electronic documents includes:
- Tax invoices
- Tax credit notes
- Simplified tax invoices above the threshold
- Self-billing invoices issued by buyers under approved arrangements
- Debit notes correcting prior invoices
Each document type has its own schema fields in PINT AE. Credit notes must reference the original invoice's IRN. See credit notes in UAE e-invoicing and self-billing under UAE e-invoicing for the mechanics.
How the law interacts with the EmaraTax portal
EmaraTax is the FTA's existing tax administration portal. Under the new framework, EmaraTax remains the destination for VAT returns, but the invoice-level data flows through the 5-corner network in near real time. By the time you file a VAT return, the FTA already holds the invoice data. The portal becomes a reconciliation surface, not a data entry surface.
Penalties in practice
The FTA has signalled a grace period in the first six months after each phase goes live. That grace period is not in the law itself. It is policy. Once it ends, penalties apply per invoice, not per filing period.
A 500-invoice-per-month business that misses the format requirement for one quarter faces AED 7.5M in theoretical exposure. The FTA has discretion to reduce, but the legal maximum is the legal maximum.
What the law does not say
The law does not name specific ERP vendors. It does not require any single archiving solution. It does not prescribe how you build your integration. Those choices stay with the taxpayer. What it does require is that the output, the PINT AE XML transmitted through an appointed ASP, meets the standard every single time.
This is where implementation choices matter. A direct ASP integration, a middleware layer, or a native ERP module all satisfy the law if the output is correct. The ERP integration reference covers the architectural options.
How to read the law as a CFO
The legal text runs to hundreds of pages across all instruments. For finance leadership, four questions matter:
- Which phase covers my entity, and what is my go-live date?
- Have I appointed an ASP before the October 30, 2026 deadline?
- Does my ERP produce PINT AE compliant XML, or do I need a middleware layer?
- Have I mapped my master data, TRNs, item codes, VAT codes, and counterparty data, against the schema?
If the answer to any of these is unclear, you are inside the risk zone. The UAE e-invoicing guide sequences the full readiness programme.
Official sources
The primary sources are published by the regulators. Cross-check any vendor claim against the original text on the UAE MoF e-invoicing portal and the UAE Federal Tax Authority site. The technical specification is mirrored in the Peppol UAE specification.
Mapping the legal stack to a working integration is where most projects stall. Massive's UAE e-invoicing software handles PINT AE generation, ASP transmission, and FTA reconciliation in one layer, so your finance team works with VAT returns instead of XML schemas.