Este artículo actualmente está disponible solo en inglés. La traducción estará disponible próximamente.
UAE e-invoicing becomes mandatory on 1 January 2027 for businesses with revenue of AED 50 million or more, on 1 July 2027 for all other in-scope businesses and on 1 October 2027 for government entities. Large businesses must appoint an accredited service provider by 30 October 2026.
Short answer: the UAE's Electronic Invoicing System becomes mandatory on 1 January 2027 for businesses with revenue of AED 50 million or more, on 1 July 2027 for all other in-scope businesses, and on 1 October 2027 for government entities. Large businesses must appoint an accredited service provider (ASP) by 30 October 2026 — a deadline the Ministry of Finance extended from 31 July. The mandate covers B2B and B2G invoices; B2C is exempt until further notice.
This guide is for finance teams in the UAE that invoice from Odoo, or are choosing an ERP with the mandate in mind. It covers what the rules require, what an ASP does, what the fines are, and what to check in Odoo before your go-live date.
The timeline
The framework is set by Ministerial Decisions No. 243 and No. 244 of 2025, issued by the Ministry of Finance on 28 September 2025, with the dates confirmed and adjusted in later announcements.
| Milestone | Date |
|---|---|
| Pilot programme and voluntary adoption | 1 July 2026 |
| ASP appointment deadline, revenue ≥ AED 50m | 30 October 2026 (extended from 31 July 2026) |
| Mandatory go-live, revenue ≥ AED 50m | 1 January 2027 |
| Mandatory go-live, all other in-scope businesses | 1 July 2027 |
| Mandatory go-live, government entities | 1 October 2027 |
Businesses below the AED 50 million line also have to appoint an ASP ahead of their own go-live. Check the Ministry of Finance e-invoicing page for the current appointment date before you plan; the large-business date has already moved once.
How the UAE model works: five corners on Peppol
The UAE uses a decentralised, five-corner continuous transaction control model on the international Peppol network:
- Corner 1 — the supplier (your ERP) creates the invoice.
- Corner 2 — the supplier's ASP validates it and sends it over Peppol.
- Corner 3 — the buyer's ASP receives it.
- Corner 4 — the buyer's ERP imports it.
- Corner 5 — the Federal Tax Authority (FTA) receives the tax data reported by the ASPs.
You do not connect to the FTA yourself. You connect your ERP to an ASP — a provider accredited by the Ministry of Finance. The Ministry requires ASPs to be active Peppol-certified service providers, to meet registration, tax and information-security requirements, and to run a solution that has been in operation for at least two years.
The penalties (Cabinet Decision No. 106 of 2025)
| Failure | Penalty |
|---|---|
| Not implementing the system or not appointing an ASP by the deadline | AED 5,000 per month |
| Invoice or credit note not issued electronically | AED 100 each, capped at AED 5,000 per month |
| Not notifying the FTA promptly of a system failure that prevents e-invoicing | AED 1,000 per day |
| Not reporting registration or master-data changes to the ASP on time | AED 1,000 per day |
Businesses that adopt voluntarily before their mandatory phase are not penalised during the voluntary period, which makes an early pilot a low-risk way to find problems.
What this means for an Odoo installation
Odoo already produces structured e-invoices and has built-in Peppol sending and receiving. For the UAE, three questions decide how much work is left:
- Which ASP will you use, and does it connect to Odoo? Some ASPs offer an Odoo connector; others expect an API integration or a file exchange. This choice is the critical path — it is also the item with the October 2026 deadline for large businesses.
- Does your Odoo version produce the UAE data specification (PINT AE) that your ASP expects? Confirm it with your ASP using real sample invoices, not a datasheet.
- Is your master data complete? Every customer needs a correct TRN (tax registration number) and address; every product needs the right VAT treatment. An e-invoice with a missing buyer TRN is rejected at corner 2, not at the FTA.
For the rest of UAE compliance in Odoo — the l10n_ae chart of accounts, 5 % VAT, corporate tax and designated zones — see our Odoo UAE localization guide and Odoo for UAE and Dubai.
Readiness checklist
- Confirm your phase: is your revenue AED 50 million or more? Your go-live is 1 January 2027 and your ASP must be appointed by 30 October 2026.
- Shortlist ASPs from the Ministry of Finance accredited list and ask each one how it connects to Odoo.
- Clean master data: customer TRNs, legal names and addresses; product VAT treatment; company TRN.
- Map every invoice source: Odoo invoices, Point of Sale, a web shop, marketplace settlements. Every B2B or B2G invoice must go through the ASP, wherever it is created.
- Test with the ASP: standard tax invoice, credit note, invoice with zero-rated and exempt lines, invoice in a foreign currency, and the incoming path (a supplier's e-invoice arriving in Odoo as a vendor bill).
- Write the failure procedure: who notifies the FTA if the system goes down — that failure carries its own daily fine.
- Join the voluntary phase if your ASP and Odoo setup are ready early; there are no penalties during voluntary adoption.
Frequently Asked Questions
When does e-invoicing become mandatory in the UAE?
On 1 January 2027 for businesses with revenue of AED 50 million or more, on 1 July 2027 for all other in-scope businesses, and on 1 October 2027 for government entities. Voluntary adoption has been possible since 1 July 2026.
What is the ASP deadline for large businesses?
30 October 2026. The Ministry of Finance extended it from 31 July 2026; the 1 January 2027 go-live date did not change.
Does UAE e-invoicing apply to B2C sales?
No, not for now. The mandate covers B2B and B2G transactions; B2C is exempt until further notice.
Can Odoo send e-invoices to the FTA directly?
No system sends directly to the FTA. Under the five-corner model your ERP sends invoices to your accredited service provider, which exchanges them over Peppol and reports the tax data to the FTA.
What is the penalty for missing the deadline?
AED 5,000 for each month that a business has not implemented the system or appointed an ASP, under Cabinet Decision No. 106 of 2025, plus AED 100 per invoice not issued electronically (capped at AED 5,000 per month).
How we can help
ECOSIRE implements Odoo for businesses in the UAE. We can clean your master data, connect Odoo to the ASP you choose, and test the full cycle — outgoing, incoming and credit notes — before your go-live. See Odoo integration, Odoo implementation or contact.
Sources (checked 25 September 2026): UAE Ministry of Finance, e-invoicing initiative; Ministerial Decisions No. 243 and 244 of 2025; Cabinet Decision No. 106 of 2025; VATupdate, UAE defines e-invoicing scope and implementation timeline (18 July 2026).
Escrito por
Muhammad Amir NazirFounder & CEO
Full-stack engineer and Odoo expert building enterprise-grade integrations, AI-powered business tools, and scalable SaaS platforms at ECOSIRE. Specializes in ERP architecture, marketplace automation, and digital transformation for mid-market enterprises.
ECOSIRE
Transforme su negocio con Odoo ERP
Implementación, personalización y soporte experto de Odoo para optimizar sus operaciones.
Artículos relacionados
German E-Invoicing (E-Rechnung) in Odoo: XRechnung, ZUGFeRD and the 2025–2028 Deadlines
Receiving e-invoices is mandatory in Germany since 2025 and issuing follows in 2027/2028: accepted formats, how Odoo produces XRechnung and ZUGFeRD, and what to test.
France's E-Invoicing Reform (2026–2027): What Changes for a Company on Odoo
Receiving e-invoices is mandatory in France since 1 September 2026 and SMEs issue them from 1 September 2027: calendar, approved platforms, Factur-X/UBL/CII and an Odoo checklist.
Guía para actualizar de Odoo 19 a 20: el proceso oficial y qué revisar en los módulos personalizados
Cómo actualizar de Odoo 19 (o 17 y 18) a Odoo 20: el proceso oficial de prueba y luego producción para Odoo Online, Odoo.sh y on-premise, y los cambios de la 20.0 que afectan a los módulos personalizados.