What is the UAE e-invoicing mandate?
The UAE is replacing paper and PDF tax invoices between businesses with structured electronic invoices that are exchanged, validated and reported to the Federal Tax Authority (FTA) as they are issued. The rules are set by Ministerial Decision No. 243 of 2025 (the e-invoicing system) and Ministerial Decision No. 244 of 2025 (the implementation phases), both issued on 29 September 2025 and amended since. Penalties are set by Cabinet Decision No. 106 of 2025.
An e-invoice is not a PDF sent by email. It is a machine-readable XML file in the UAE's PINT AE format, sent from the supplier's ASP to the buyer's ASP over the Peppol network, with the tax data reported to the FTA at the same time.
Who is in scope, and when?
| Who | Appoint an ASP by | E-invoicing mandatory from |
|---|---|---|
| Businesses with revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Businesses with revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
A pilot programme and voluntary adoption have been open since 1 July 2026. Businesses that missed the 30 October 2026 ASP date should appoint one now: the penalty for not implementing the system on time runs per month of delay.
The mandate covers business-to-business (B2B) and business-to-government (B2G) transactions. Business-to-consumer (B2C) sales stay outside the system until a further ministerial decision. Some transactions are excluded, including certain financial services and international air transport, and, for 24 months from 1 January 2027, transactions between members of the same VAT tax group (Ministerial Decision No. 197 of 2026).
How does the 5-corner model work?
The UAE uses a Decentralised Continuous Transaction Control and Exchange (DCTCE) model with five corners:
- Supplier (corner 1) creates the invoice in its ERP and sends it to its ASP.
- Supplier's ASP (corner 2) validates it against PINT AE, sends it to the buyer's ASP over Peppol and reports the tax data to the FTA.
- Buyer's ASP (corner 3) validates the received invoice, delivers it to the buyer and reports its tax data to the FTA.
- Buyer (corner 4) receives the e-invoice into its ERP for matching and payment.
- FTA (corner 5) receives the tax data from both ASPs.
Each business appoints one ASP from the Ministry of Finance's list of accredited providers. The ASP handles the Peppol connection, signing and reporting; the business remains responsible for the content of the invoice. Each business is identified on Peppol by its Tax Identification Number (TIN), the first ten digits of its Tax Registration Number (TRN).
What must an e-invoice contain, and when must it be issued?
- Format: PINT AE, the UAE specification of the Peppol International invoice, in UBL XML. The published UAE data dictionary sets the mandatory fields, at document and line level.
- Documents: tax invoices, commercial invoices and credit notes, including self-billed invoices and credit notes. A credit note must refer to the original invoice.
- Timing: an e-invoice or e-credit note must be issued and transmitted within 14 business days. VAT-registered businesses must still meet the VAT invoice deadlines, which are often earlier.
- Exports: an e-invoice is still issued through your ASP when the buyer is overseas, including when the buyer has no Peppol identifier.
- Receiving: a business that buys from in-scope suppliers must be able to receive e-invoices through its ASP, even if it sells mostly to consumers.
What are the penalties?
| Violation (Cabinet Decision No. 106 of 2025) | Penalty |
|---|---|
| Not implementing the system or not appointing an ASP on time | AED 5,000 for each month or part of a month of delay |
| Not issuing or transmitting an e-invoice on time | AED 100 per invoice, up to AED 5,000 a month |
| Not issuing or transmitting an e-credit note on time | AED 100 per credit note, up to AED 5,000 a month |
| Not telling the ASP of a change to registered data on time | AED 1,000 for each day of delay |
Penalties apply from a business's mandatory date, not during voluntary adoption.
What changes in SAP?
Standard SAP billing produces a printed or PDF invoice. For UAE e-invoicing, each relevant document has to leave SAP as a validated PINT AE file, reach the ASP within the deadline, and come back with a status. In practice that touches:
| Area | What changes |
|---|---|
| Master data | Your TIN and TRN per company code; customers' and vendors' TINs and Peppol identifiers; UAE units of measure and tax categories mapped to SAP codes |
| Outgoing documents | SD billing documents and FI invoices and credit notes converted to PINT AE, with every mandatory field filled from SAP |
| Transmission | Each document sent to your ASP through an API, with retries and a log, inside the 14-business-day window |
| Status | Message Level Status from the ASP and FTA written back against the SAP document, so rejections are corrected and resent |
| Incoming invoices | Supplier e-invoices received from the ASP into SAP and matched with purchase orders and goods receipts |
| Group set-ups | Several UAE entities, company codes or ERPs sending through one hub, with tax group transactions flagged while they are excluded |
The work is mostly data: most rejections come from missing or inconsistent master data, not from the file format. Cleaning TINs, units and tax codes in SAP is the first step for every business in scope.
How does OptiE-Invoice UAE handle it?
OptiE-Invoice UAE extracts invoices and credit notes from SAP, validates them against PINT AE, maps them to UBL XML and sends them to your ASP. Message Level Status flows back into SAP. Incoming e-invoices are received, matched with purchase orders and goods receipts, and routed for acceptance.
- SAP ECC (EHP6 and above) and SAP S/4HANA on-premise or private cloud: an add-on inside SAP.
- SAP S/4HANA Public Cloud: through SAP BTP.
- Non-SAP and multi-ERP landscapes: a REST API and a hub for groups with several UAE entities or ERPs.
You appoint one accredited ASP; IVL works with MoF-accredited ASP partners. For VAT returns, OptiGulfVAT prepares the data for the VAT 201 return from the same SAP records.
Frequently asked questions
When does UAE e-invoicing become mandatory?
On 1 January 2027 for businesses with revenue of AED 50 million or more, 1 July 2027 for all other in-scope businesses, and 1 October 2027 for government entities.
By when must a business appoint an ASP?
By 30 October 2026 for businesses with revenue of AED 50 million or more, and by 31 March 2027 for smaller businesses and government entities. A business that has missed its date should appoint one now.
Are B2C invoices covered?
Not yet. B2C transactions stay outside the e-invoicing system until a further ministerial decision. B2B and B2G invoices and credit notes are covered.
Are transactions within a VAT tax group excluded?
Yes, for 24 months from 1 January 2027, under Ministerial Decision No. 197 of 2026. The exclusion is temporary, so SAP should still flag these transactions.
What is PINT AE?
The UAE specification of the Peppol International (PINT) invoice, in UBL XML. It sets the fields every e-invoice and credit note must contain.
How long do we have to issue an e-invoice?
14 business days to issue and transmit an e-invoice or e-credit note. VAT invoice deadlines still apply and are often earlier.
What are the penalties for non-compliance?
AED 5,000 a month for not implementing the system or appointing an ASP on time, and AED 100 per late e-invoice or credit note, up to AED 5,000 a month, under Cabinet Decision No. 106 of 2025.
Is IVL an ASP?
No. You appoint one MoF-accredited ASP. OptiE-Invoice UAE prepares and validates the e-invoices in SAP and sends them to that ASP; IVL works with accredited ASP partners.
Sources
This guide summarises the rules for general information and is not legal advice. Check the current notifications before acting on them.