The United Arab Emirates has defined a national mandatory e-invoicing model. It is not a PDF invoice sent by email: it is a structured document that travels over a controlled network, with a format and validation defined by the tax authority (Federal Tax Authority, FTA). This article explains what it is, who it affects and how to solve it from Odoo without building parallel manual processes.
What matters: the FTA timeline is phased. The exact dates are set by the authority and may be adjusted, so always confirm your wave before planning. What does not change is the technical model: Peppol PINT-AE and submission through an accredited Access Point.
What the UAE e-invoicing mandate is
The FTA has adopted a five-corner (5-corner) model based on Peppol. Instead of communicating directly with the administration, the issuer and the receiver each use their accredited Access Point, and a fifth node reports to the tax authority. The document format is PINT-AE, the Emirati national specialization of Peppol International (PINT), built on UBL.
Who it affects and on which transactions
- Businesses registered in the UAE that issue or receive B2B and B2G invoices.
- Phased rollout by taxpayer size: large ones first, then the rest.
- B2C is outside the first scope for now, but it is wise to design assuming it will come in.
- You must onboard with an accredited Service Provider (ASP) and register the company's Peppol identity.
What the PINT-AE invoice must carry
Unlike a classic invoice, here there are mandatory fields and strict validation rules: tax identifiers (TRN) for issuer and receiver, Peppol identification schemes, correct tax and document-type codes, normalized unit and country codes, and the handling of exemptions and zero rates. A single mis-filled field gets the document rejected by the Access Point before it reaches its destination.
How it is solved from Odoo 19
Our connector fits inside Odoo's normal invoicing flow. When you validate a customer invoice, the module generates the PINT-AE document from the data that already exists (company, partner, lines, taxes), applies the validations before sending and transmits it to the Peppol network through your Access Point. The response —acceptance or rejection reason— is recorded on the entry itself, without leaving Odoo.
Common mistakes to watch out for
- Thinking that any PDF or XML will do: the mandate requires validated PINT-AE sent over the network, not an attached file.
- Incomplete master data: TRN, country, currency or tax codes mis-configured on the partner or the company.
- Not keeping the acknowledgement: if the rejection is not traced in Odoo, you don't know which invoices failed or why.
- Relying on a parallel manual process: sooner or later someone forgets to send and an unreported invoice appears.
FAQs
Who is bound by UAE e-invoicing?
The FTA mandate applies to B2B and B2G transactions of companies registered in the UAE, with a phased rollout by taxpayer size.
What is Peppol PINT-AE?
It is the format and network on which UAE e-invoicing is built: a 5-corner model based on Peppol with the national PINT-AE specification.
Can Odoo issue invoices compliant with the UAE mandate?
Yes. With the right module, Odoo generates the PINT-AE document, validates it and sends it through an accredited Access Point, keeping the acknowledgement inside the ERP itself.
Do I need an accredited service provider (ASP)?
Yes. Submission to the Peppol network and the FTA is done through an accredited Access Point / ASP; Odoo connects to it instead of talking directly to the administration.
Want to prepare your Odoo for UAE e-invoicing?
We review your master data, your taxes and your Access Point, and tell you what is missing so every invoice goes out compliant on the first try. Book a call on Calendly or call +34 616 809 504.