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

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 — for a freight forwarder or logistics operator, that's close to every invoice raised, since shippers, consignees and customs agents are virtually all business accounts.
• 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.

In practice, that line often runs straight through the middle of one business. A trading group selling wholesale to other companies while also running retail branches and a point-of-sale counter needs its wholesale invoices e-invoicing-ready well before 2027, even while the till receipts stay out of scope for now.

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 — Odoo itself is not on the Ministry of Finance's list of pre-approved e-invoicing service providers, so connecting an Odoo database to an accredited provider is a deliberate integration decision, not something the ERP handles by default. Where a business runs several legal entities under one roof — the kind of multi-company retail group setup I connect Shopify and branch POS into — each entity holds its own TRN, and in practice that means appointing an ASP and building the integration entity by entity, not once for the whole group.

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 — and, as with any Odoo rollout, choosing the right implementation partner matters as much as the software. It also tends to land on the part of the system that already carries the heaviest load: accounting is the most heavily customised module across the Odoo implementations I've analysed, and e-invoicing compliance adds straight onto that same layer. In my experience preparing ERP systems for structured invoicing regimes, the work breaks into five areas:

1. 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, and it multiplies across a portfolio of separate legal entities, the everyday structure behind the owners associations and property management companies I work with.
2. Tax and document configuration. Tax codes, invoice types, credit notes and document numbering all need to map cleanly onto what the FTA schema expects — a separate step from, though it builds on, your UAE VAT setup in Odoo.
3. 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.
4. 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.
5. 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 — and budget for what an implementation project like this actually costs.
• 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

Related reading

More guides from my desk: the three ways to connect Odoo to an accredited e-invoicing provider, Odoo 19 new features — what actually matters, what drives Odoo implementation cost in the UAE, and Odoo Community vs Enterprise — how to choose.