UAE E-Invoicing 2026–2027: Getting Odoo Ready for Peppol and PINT AE

The UAE is moving from PDF invoices to a national electronic invoicing network, and the timeline is now firm. A voluntary pilot opened on 1 July 2026. Businesses with annual revenue of AED 50 million or more must be live on 1 January 2027 and have until 30 October 2026 to appoint an accredited service provider. Everyone else follows on 1 July 2027. If you run your business on Odoo, the changes are manageable — but they are not a checkbox.

This guide explains the model the UAE chose, what it demands of your ERP, and a preparation plan that avoids a December scramble.

The UAE model in plain terms

The UAE adopted a decentralised continuous transaction control and exchange (DCTCE) model built on the Peppol network, with one addition. A standard Peppol exchange has four corners: the supplier, the supplier's access point, the buyer's access point and the buyer. The UAE adds a fifth corner — the Federal Tax Authority, which receives tax data from the access points in near real time.

Three practical consequences follow:

1. Invoices must be issued in a structured XML format called PINT AE (the Peppol International Invoice, UAE profile), not as PDFs.
2. Invoices must be transmitted through a Ministry of Finance Accredited Service Provider (ASP), which validates them and routes them to the buyer's access point and to the FTA.
3. Buyers receive invoices electronically as well — which means your purchase side changes too, not only your sales side.

This is different from Saudi Arabia's ZATCA model, where the tax authority clears invoices directly. If you operate in both countries, expect two integrations with two data models; our Odoo ZATCA guide covers the Saudi side.

What changes inside Odoo

Odoo already speaks Peppol: the Accounting app can send and receive electronic invoices through Odoo's own access point in Europe and supports UBL-based formats. For the UAE, three things need to be in place:

• The UAE localisation (l10n_ae) with the correct chart of accounts, VAT taxes and the 5 percent standard rate, zero-rated and exempt categories, and reverse charge for imports.
• PINT AE output, either through Odoo's native Peppol support as it is extended for the UAE profile, or through an ASP connector module that maps Odoo invoices to PINT AE and handles transmission and status updates.
• Inbound handling so supplier invoices arriving through the network create vendor bills automatically instead of being keyed in from PDFs.

Which of these is "native" versus "connector" depends on your Odoo version and the ASP you choose. Odoo 19 is the safest base; older versions will rely more heavily on connectors. If you are on Odoo 15 or 16, this mandate is a good reason to plan the upgrade now — see our Odoo 19 and 20 upgrade guide.

Choosing an ASP

The Ministry of Finance publishes the list of accredited service providers. When evaluating one for an Odoo system, ask:

• Do they have a maintained Odoo connector, and for which versions?
• How do they handle rejections and corrections — can a rejected invoice be fixed and resent from inside Odoo?
• What is the pricing model — per invoice, per month, or tiered — and what happens at your volume?
• Do they support inbound documents into Odoo, or only outbound?
• Where is data stored, and does that satisfy your data-residency policy?

Large businesses must have appointed an ASP by 30 October 2026. Smaller ones have more time but the same choice to make.

Data you need to clean before January

E-invoicing exposes sloppy master data instantly. Before go-live:

• Every customer and supplier needs a valid TRN and a complete address; Peppol identifiers are built from them.
• Product lines need correct tax categories; "VAT 5%" applied to a zero-rated export will be rejected.
• Credit notes must reference the original invoice.
• Multi-currency invoices need consistent exchange-rate handling.

Companies that run a data-cleaning sprint in Q3 have quiet Januaries. Companies that don't, don't.

A preparation plan

September–October 2026: confirm your Odoo version and upgrade path, shortlist ASPs, run the data audit, and decide whether to join the voluntary pilot.

November–December 2026: install the localisation and connector, configure taxes and identifiers, run test exchanges with a friendly supplier and customer, and train the finance team on the new rejection workflow.

January 2027 onward: go live (large businesses) or continue testing until July (everyone else), with an implementer on call for the first weeks.

Key takeaways

• The UAE mandate is a five-corner Peppol model: structured PINT AE invoices, transmitted through an accredited service provider, with the FTA receiving data in near real time.
• Large businesses go live on 1 January 2027 and must appoint an ASP by 30 October 2026; all others on 1 July 2027.
• In Odoo the work is the localisation, the PINT AE output via native Peppol support or an ASP connector, inbound bills, and clean master data.
• Start in autumn 2026 — the upgrade and data-cleaning steps take longer than the integration itself.

SummationWorks implements and supports Odoo for companies in the UAE, Saudi Arabia and Egypt, including e-invoicing readiness and upgrades. Explore our Odoo and ERP services, see what an implementation costs, or talk to us about your 2027 deadline.