Odoo and UAE E-Invoicing: Connecting to an Accredited Service Provider

The question turns up in the first ten minutes of every UAE e-invoicing kickoff I run, usually phrased as: we are on Odoo, so we are covered, right? No. Odoo is not on the Ministry of Finance list of pre-approved eInvoicing Service Providers, which means an Odoo database cannot put an invoice onto the network by itself. It has to reach an accredited provider, and there are exactly three architectures for getting it there. Choosing between them is not a procurement detail. It decides what every Odoo upgrade you do from here costs you.

Odoo is not on the pre-approved list

Start with the fact, because most vendor material talks around it. The Ministry of Finance publishes a list of pre-approved eInvoicing Service Providers under Ministerial Decision No. 64 of 2025. When I checked it — the page carries its own update stamp of 17/07/2026 — it held 42 providers, and Odoo was not one of them. I am deliberately not reproducing that list here, because the Ministry says it is updated periodically as new providers are approved. Read it at source before you commit to anything.

The criteria explain the shape of the list. Article 5 — replaced in full by Ministerial Decision No. 56 of 2026, so check the amended text rather than the original — requires an applicant to be "an active Peppol-certified Service Provider who has successfully completed the OpenPeppol conformance tests", on top of company registration, information security, self-declaration and insurance conditions. The experience test now sits in a new Article 5(bis) and is met where "the PSP Product through which the Electronic Invoicing Services are to be delivered has been in operation for a minimum of (2) two years", with that experience held by the provider or by a third party — because the amended Article 5 also lets a provider use a PSP Product owned by a third party, or outsource its development, operation or management, while keeping full responsibility for meeting the conditions. Approval then runs in two stages: Pre-Approval under Article 15, and Accreditation under Article 16 once the provider has completed tax data reporting testing, the OpenPeppol testing services and a trial run on the production environment with the Authority. Accreditation lasts two years and has to be renewed.

What I will not do is tell you whether Odoo will or will not appear on that list later. I do not know, nobody outside the Ministry and Odoo does, and I have watched a client stall a compliance project for a quarter on somebody's confident guess about a vendor roadmap. Plan against what is published on the day you sign, and design so that a change of provider does not mean a change of ERP.

The clock you are actually on

Ministerial Decision No. 244 of 2025 sets the phases. The Pilot Programme commenced on 1 July 2026, and voluntary implementation opened the same day for anyone who wants it. Businesses with revenue of AED 50,000,000 or more are in the first mandatory phase and must implement the Electronic Invoicing System by 1 January 2027; the appointment deadline for an Accredited Service Provider in that Decision, originally 31 July 2026, was moved to 30 October 2026 by Ministerial Resolution No. 66 of 2026. Businesses under AED 50,000,000 appoint by 31 March 2027 and implement by 1 July 2027. Government entities appoint by 31 March 2027 and implement by 1 October 2027. Business-to-consumer transactions sit outside the system until the Minister decides otherwise.

Two things get missed in every planning meeting. Appointing a provider is a signature; integrating your ERP is a project, and only one of those can be done in an afternoon. And the phase you fall into is set by revenue, so a group with one entity above the threshold and three below it is running two timelines inside one database — which argues for building the integration once, at group level.

Three routes from Odoo to the network

Route A — Odoo's own e-invoicing service. Odoo does operate as a network participant elsewhere: its 19.0 documentation describes Odoo acting "as both an access point and an SMP" and lists the countries eligible for Peppol registration in Odoo. The United Arab Emirates is not on that list, and the UAE fiscal localization — l10n_ae, l10n_ae_reports and l10n_ae_pos — does not mention e-invoicing, PINT AE, Peppol or an Accredited Service Provider anywhere. You cannot scope this route today. If it ever arrives it is the cheapest one to own, because it upgrades when the core upgrades.

Route B — a third-party connector module in your database. This is the option most clients are shown first, and it demos beautifully. The cost lands eighteen months later. A connector is third-party code sitting directly on invoice posting inside your accounting stack: when you move to the next Odoo version it has to move with you, and until it does, you are not invoicing. Before I let one be installed I ask two questions: which Odoo versions has this module actually shipped on, and who maintains it. A module that exists for exactly one version is a liability wearing an integration's clothes.

Route C — the integration built on the provider's side. Odoo exposes invoice data through the API or a scheduled export, and the provider maps it to PINT AE, validates it and transmits. It is more work up front and leaves the smallest footprint in your database, which means core upgrades stop being an e-invoicing risk at all. The trade-offs are real: the mapping lives somewhere you do not control, switching provider means rebuilding it, and you still have to bring acknowledgements and rejections back into Odoo so the finance team can see and act on them.

There is no universally correct answer, only a correct answer for a specific database and team. The deciding question is almost always the same one: who owns this mapping at the next upgrade, and will they still be around?

What the provider actually asks for

Test onboarding is the point where compliance stops being a slide deck. Every provider I have worked through wants roughly the same package: a named technical contact and an agreed test window; your TRN and exact legal entity details; sample invoices covering each document type you issue, including credit notes correctly linked to the invoice they reverse; your tax code mapping, spelled out; and units of measure and currencies expressed in the codes the schema expects rather than the free text your team has been typing for years. None of it is technically difficult. All of it takes three times longer than the plan says, because it is data work, and data work always does.

What breaks first

Across readiness assessments the failures cluster in the same three places, and none of them are Odoo's fault:

• The TRN on partner records. This is the one that hurts. On older databases I find it in an internal note, in a custom field nobody has maintained since go-live, or nowhere at all on a meaningful share of active customers. Validation is unforgiving about it, and no amount of template tuning compensates.
• Legal name versus trading name. The Odoo partner name is whatever sales typed when they created the record. The schema wants the registered entity. Reconciling the two across a few thousand customers is usually the single largest task in the whole project, and it cannot be automated safely.
• Invoice journal numbering. Cancel-and-redraft habits, sequences that reset per year, a journal per branch, and multi-company setups where two entities quietly share a prefix. Numbering that is merely untidy in-house becomes a rejection once the document leaves the building.

Fix all three during the voluntary window, not during go-live week. That is what it is there for. Note that the Pilot Programme is a separate thing you cannot simply opt into — under Ministerial Decision No. 244 of 2025 the Ministry notifies a Person of their inclusion in the Taxpayer Working Group, and inclusion requires that Person's written agreement.

Frequently asked questions

Related reading

More guides from my desk: UAE e-invoicing 2026–2027 and what it means for your Odoo ERP — the parent guide to this one, covering scope, phases and the readiness checklist; Odoo UAE VAT setup — the tax configuration the e-invoice schema reads from, so it has to be right first; and how to choose an Odoo partner in the UAE — because whichever route you pick, it is only as good as whoever maintains it at the next upgrade.