In this guide
The UAE E-Invoicing Timeline
The UAE is replacing paper and PDF tax invoices with structured electronic invoices exchanged over the Peppol network. The rollout is phased by revenue, and the first deadline that matters is not the go-live - it is the date by which you must appoint a provider.
| Who | Appoint an ASP by | Go-live |
|---|---|---|
| Voluntary pilot | - | Opened 1 July 2026 |
| Revenue AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
The first phases cover business-to-business and business-to-government invoices. Confirm your own phase and obligations against the Ministry of Finance's published decisions, as details can be amended.
How the Peppol Five-Corner Model Works
The UAE did not build a central portal that every invoice must pass through. It adopted Peppol, an international e-invoicing network, with a fifth "corner" added for the tax authority.
-
1
Seller (your ERP)
ERPNext creates and submits the sales invoice as usual.
-
2
Seller's ASP
Your Accredited Service Provider receives the invoice data, converts it to PINT AE XML, validates it and sends it over Peppol.
-
3
Buyer's ASP
The buyer's provider receives the invoice from the network.
-
4
Buyer
The invoice arrives in the buyer's system as structured data, ready to book as a purchase without retyping.
-
5
Federal Tax Authority
The ASPs report the tax data to the FTA, giving it near real-time visibility of VAT transactions.
Two consequences follow. You must appoint an ASP - you cannot connect your ERP straight to the FTA. And your suppliers will start sending you e-invoices too, so the receiving side needs a plan, not just the sending side.
UAE vs Saudi Arabia: Not the Same Project
UAE (FTA)
Decentralised Peppol exchange through accredited providers, with reporting to the FTA. Format is PINT AE XML. Mandatory from January 2027 for the largest businesses.
Saudi Arabia (ZATCA)
Invoices are cleared or reported directly with ZATCA's platform, with cryptographic stamps and QR codes. Phase 2 has been rolling out in waves since 2023.
Groups trading in both countries often assume one integration covers both. It does not. They share a goal and very little plumbing. See our ERPNext work in Saudi Arabia →
What ERPNext Has to Get Right
The ASP does the transmission. Your ERP supplies the data, and an e-invoice can only be as correct as the invoice behind it. These are the areas we check first on any UAE ERPNext site:
- Party masters: A valid TRN on every VAT-registered customer and supplier, with a clean legal name and address. Missing TRNs are the most common reason invoices fail validation.
- VAT categories: Standard-rated, zero-rated, exempt, out-of-scope and reverse charge must each map to the right tax template, not a single generic 5% template with manual overrides.
- Item data: Clear item descriptions and units of measure on every invoice line, because the structured format carries line-level detail, not just totals.
- Credit notes: Every credit note references the original invoice. Standalone credit notes are hard to report correctly.
- Numbering and amendments: Unique, sequential invoice numbers, and corrections made by credit note and re-issue rather than by editing a submitted invoice.
- Multi-currency: Invoices in USD or other currencies still need correct AED VAT amounts using the exchange rate on the invoice date.
Connecting ERPNext to an ASP
Most ASPs expose an API that accepts invoice data and returns a status - accepted, rejected with errors, or delivered. The integration typically works like this:
-
1
On submit, send
When a Sales Invoice or credit note is submitted, a background job sends its data to the ASP. The user is not kept waiting.
-
2
Store the response
The ASP's reference and status are stored on the invoice, so anyone can see whether it was delivered.
-
3
Surface the failures
Rejected invoices land in a queue with the ASP's error messages. Someone owns that queue every day.
-
4
Receive inbound invoices
Supplier e-invoices arriving through the ASP are pulled in as draft Purchase Invoices for review and matching to purchase orders.
Choose the ASP before designing the integration: field mappings, error formats and the inbound flow differ between providers. See our ERPNext integration services →
UAE E-Invoicing Readiness Checklist
Do this before your go-live
Frequently Asked Questions
When does e-invoicing become mandatory in the UAE?
Businesses with revenue of AED 50 million or more appoint an ASP by 30 October 2026 and go live on 1 January 2027. Smaller businesses appoint one by 31 March 2027 and go live on 1 July 2027. Government entities go live on 1 October 2027.
What is an Accredited Service Provider (ASP)?
A provider accredited by the Ministry of Finance to exchange e-invoices over Peppol on your behalf and report the data to the FTA. Every in-scope business must appoint one.
What format do UAE e-invoices use?
Structured XML based on PINT AE, the UAE version of the Peppol invoice standard. A PDF is not an e-invoice under the mandate.
Can ERPNext be used for UAE e-invoicing?
Yes. ERPNext produces the invoice data and an integration passes it to your ASP, which handles the format, Peppol exchange and FTA reporting. The ERPNext work is making the data complete and correct.
Is UAE e-invoicing the same as Saudi ZATCA e-invoicing?
No. Saudi Arabia clears or reports invoices directly with ZATCA. The UAE uses Peppol exchange through accredited providers. Groups in both countries need two integrations.
Final Verdict
UAE e-invoicing is a data quality project with an integration at the end, not the other way round. Appoint your ASP on time, clean your TRNs and tax templates now, and the go-live becomes a switch you flip rather than a month of rejected invoices.
