UAE E-Invoicing 2026–2027: What It Means for Your Odoo ERP
The UAE is moving to a mandatory Electronic Invoicing System (EIS). If your business issues B2B or B2G invoices in the UAE, the way you produce and transmit those invoices is about to change — and the work lands squarely on your ERP. Here's the timeline, what's actually required, and how to get an Odoo system ready.
What's changing
Under Ministerial Decision No. 243 of 2025 and No. 244 of 2025, the UAE is introducing a structured electronic invoicing framework. Instead of emailing a PDF, in-scope businesses must exchange invoices as structured data, routed through an accredited intermediary and reported to the Federal Tax Authority.
This is not a formatting change. It is a change to how invoice data is created, validated and transmitted — which means your ERP becomes the compliance system.
The timeline
| Milestone | Date |
|---|---|
| Pilot / voluntary phase begins | July 2026 |
| Phase 1 businesses (revenue ≥ AED 50m) must appoint an ASP | 30 October 2026 |
| Phase 1 go-live (revenue ≥ AED 50m) | 1 January 2027 |
| Phase 2 businesses (revenue < AED 50m) must appoint an ASP | 31 March 2027 |
| Phase 2 go-live (revenue < AED 50m) | 1 July 2027 |
| Government entities | 1 October 2027 |
The deadline that catches people out is not the go-live date — it's the ASP appointment date. You need your provider selected and your ERP integration built and tested before that, not after.
Who is in scope
- B2B and B2G (and G2B) transactions are in scope.
- It applies whether or not the business is VAT-registered.
- Free zone businesses are included, unless specifically excluded.
- B2C transactions are currently excluded from the mandate.
What technically changes
1. Invoices become structured XML
The UAE mandate requires the PINT AE format — the UAE Data Dictionary built on the Peppol International (PINT) specification, with UBL as the underlying ISO standard. Every mandated field must be present and correctly typed.
2. PDFs stop being invoices
Only structured XML transmitted through an accredited channel qualifies as a valid e-invoice. A PDF may still be a human-readable copy, but it is not the legal document.
3. You must route through an ASP
Businesses cannot report each transaction directly to the FTA portal. Invoices travel through an Accredited Service Provider (ASP) — a certified intermediary that validates and transmits them. Appointing one is a mandatory step, not an optional convenience.
The practical takeaway: compliance is decided by your invoice data quality, not your invoice template. If a customer's TRN is missing, a tax code is mapped wrongly, or a unit of measure isn't standardised, the invoice fails validation — and that is an ERP problem.
What this means for your Odoo system
Odoo can absolutely meet the requirement, but it is a genuine implementation project rather than a switch you flip. In my experience preparing ERP systems for structured invoicing regimes, the work breaks into five areas:
- Master data cleanup. Every trading partner needs a valid TRN, exact legal name and complete address. This is usually the largest and most underestimated task — years of loosely-entered customer records have to be corrected.
- Tax and document configuration. Tax codes, invoice types, credit notes and document numbering all need to map cleanly onto what the FTA schema expects.
- Field-level mapping. Each mandated PINT AE field must be populated from a reliable place in Odoo. Gaps get filled with custom fields or automation, not manual entry.
- ASP integration. Odoo needs to transmit to your chosen provider and handle what comes back — acknowledgements, validation failures and rejections — with a clear process for fixing and resubmitting.
- Testing during the pilot. The voluntary phase exists precisely so you can find your data problems before penalties apply. Use it.
Readiness checklist
- Confirm which phase you fall into (above or below AED 50m revenue) and note your ASP deadline.
- Audit customer and vendor master data for TRN, legal name and address completeness.
- Review your tax code and document-type configuration against the required schema.
- Shortlist and appoint an Accredited Service Provider.
- Scope the Odoo integration — mapping, transmission, error handling, archiving.
- Run real invoices through the pilot phase and fix what fails.
- Train finance staff on the new rejection/resubmission workflow.
Penalties
Non-compliance can trigger penalties of up to AED 5,000 per month for certain violations. The bigger commercial risk, though, is operational: if your invoices aren't valid, your customers can't process them, and your receivables slow down.
Frequently asked questions
When does UAE e-invoicing become mandatory?
Does a PDF invoice count as a UAE e-invoice?
Can Odoo handle UAE e-invoicing?
What are the penalties for UAE e-invoicing non-compliance?
This guide is general information for planning purposes, based on published guidance as of July 2026. E-invoicing rules continue to evolve — always confirm the current requirements with the UAE Federal Tax Authority or your tax advisor before making compliance decisions.
Related reading
More guides from my desk: Odoo 19 new features — what actually matters, what drives Odoo implementation cost in the UAE, and Odoo Community vs Enterprise — how to choose.
Getting your Odoo system e-invoicing ready?
I'm an Odoo Techno-Functional Consultant in Dubai with 10+ years and 100+ implementations, certified across Odoo v13, v14, v15, v16, v18 and v19. Happy to review where your system stands — at no cost.
Get a free business evaluation