Lesson 3 — What Odoone is, and what it is not
This is the lesson that prevents a procurement mistake.
Odoone's UAE e-invoicing module is the ERP-side connector. It occupies corner 1 and corner 4: it produces the outbound document, and it takes the inbound one into your books. The Peppol transmission and the FTA tax-data reporting are performed by an MoF-accredited ASP. The module guide states the position without hedging — it "is not, and cannot legally be, the accredited access point itself".
Who does what, in one table.
| The job | Who does it |
|---|---|
| Raise the invoice and hold the data | Your ERP — Odoone, at C1 |
| Produce the PINT AE document and validate it | Odoone |
| Transmit it over Peppol to the other side | Your ASP, at C2 |
| Report the tax data to the FTA | Your ASP |
| Turn an inbound e-invoice into a draft vendor bill | Odoone, at C4 |
| Hold the accreditation | The ASP — accreditation attaches to a provider, never to installed software |
What the module does on its own side is specific. It generates the PINT AE document for in-scope UAE customer invoices, validates it against the MoF mandatory-field and business rules, transmits it through the ASP, and tracks the full lifecycle of outbound and inbound documents — FTA status, retries, and an immutable SHA-256-stamped XML archive. Inbound documents are created as draft vendor bills and are never posted automatically, so a supplier's document cannot land in your ledger without a person seeing it.
Accreditation is a status a provider applies for and holds. The eligibility conditions and the accreditation process are set by Ministerial Decision 64 of 2025, amended by Ministerial Decision 56 of 2026. The Ministry of Finance publishes the list of accredited providers at mof.gov.ae and it changes as providers are added and accredited, so check it on the day you shortlist rather than trusting a copy someone circulated in the spring. Source: MD 64/2025 as amended by MD 56/2026.
The module is ASP-agnostic, and that is a deliberate design decision. A generic REST ASP adapter ships in the box, and adding a different provider is a new adapter model plus one entry in a selection list, with no edits to the core code. You therefore choose a provider on its merits — coverage, support, price, onboarding speed — rather than because your ERP has only ever spoken to one of them.
The consequence at contract time is that you are buying two things, from two suppliers, and you may buy them in either order. The ASP contract gets you an identity on the Peppol network and a route to the FTA. The ERP work gets your invoice data into a shape the provider will accept. A business that signs an ASP in November with no ERP connector in December is no readier than one with the connector and no provider.
The two failure modes are mirror images. One is buying software described as compliant and assuming it removes the need for a provider — it does not, and an installed licence cannot confer a status the Ministry grants to service providers. The other is signing a provider and assuming they will handle everything — a provider cannot repair invoice data it never receives, and it will reject documents missing fields your ERP was supposed to carry. Ask any vendor one question: are you the accredited access point, or do you connect me to one? Both answers are legitimate. Only one of them is an ASP.
The idea to carry forward: Odoone is corner 1 and corner 4, your provider is corner 2, and neither of them replaces the other.