Peppol and PINT AE Explained for UAE Businesses

Every UAE e-invoicing conversation eventually arrives at two unfamiliar terms: Peppol and PINT AE. They sound like technical trivia. They are actually the two design decisions that define what your finance systems must be able to do by 2027 — and understanding them in business terms makes every other decision (which ASP, which ERP work, which timeline) much easier.

This guide is part of our complete UAE e-invoicing guide. If you want the broader picture first, start with our plain-language explainer of UAE e-invoicing; if you want the calendar, see our deadlines and phases guide.

What Peppol is — and why the UAE chose it

Peppol is an international network for exchanging business documents electronically. It began in Europe for public procurement and now carries e-invoices across Europe, Asia and Australasia. The simplest mental model is a postal system for structured documents: participants connect through certified operators called access points, addresses are standardised, and a document posted by one member can reach any other member regardless of which software either side uses.

Rather than building a proprietary national platform, the UAE plugged into this network. That choice has practical consequences in your favour: the infrastructure is proven at scale, there are dozens of experienced operators rather than a single gatekeeper, and businesses trading internationally get interoperability with other Peppol countries rather than another one-off local format.

The five-corner model, corner by corner

The UAE implements what the Ministry of Finance calls a Decentralised Continuous Transaction Control and Exchange (DCTCE) model — universally shortened to the "5-corner model." The corners:

1. Corner 1 — the supplier. Your ERP or accounting system creates the invoice as a structured PINT AE file.
2. Corner 2 — the supplier's Accredited Service Provider (ASP). Validates the file against the UAE rules and transmits it across the network.
3. Corner 3 — the buyer's ASP. Receives the invoice on the buyer's behalf.
4. Corner 4 — the buyer. The invoice arrives as data in their system — no re-typing, no PDF parsing.
5. Corner 5 — the Federal Tax Authority. Receives the tax data of the invoice from the ASPs in near-real time.

"Decentralised" is the operative word. Unlike clearance systems where the tax authority sits inside the issuance loop, UAE invoices flow business-to-business through ASPs, with tax data reported alongside. Three things follow:

• There is no FTA portal to upload invoices to. Your ASP relationship is your compliance interface.
• You never connect to the FTA directly for invoicing. The ASPs handle transmission and reporting.
• The FTA's view of your business activity becomes continuous rather than quarterly.

What PINT AE actually is

Peppol's standard invoice format is called PINT — the Peppol International Invoice. Countries adapt it to their own tax rules, and PINT AE is the UAE specialisation, defined by the Ministry of Finance's Data Dictionary. The Mandatory Field Requirements document published in February 2026 sets out, field by field, what a valid UAE e-invoice must contain.

A PINT AE invoice is an XML file in which every business fact has a defined home: seller and buyer TRNs, registered names and addresses, line items with standard unit codes, a tax category code on every line, and totals that must reconcile arithmetically. Validation is mechanical — the file either conforms or it is rejected.

Compared with the invoicing you run today, four things change:

• An invoice becomes data, not a document. Layout, branding and PDF appearance are irrelevant to compliance; the XML is the invoice, and it is also the tax invoice for VAT purposes.
• Validation happens before delivery. A missing or malformed mandatory field is rejected at your ASP — not discovered in a dispute months later.
• Both directions are regulated. You must receive supplier e-invoices through your ASP as well as send your own; accounts payable is in scope.
• Credit notes are first-class citizens. E-credit notes use the same format family and carry the same 14-day issuance window as invoices.

What your ERP must produce

This is where the project actually lives. To comply, your system — or its integration layer — must be able to:

• Generate complete, valid PINT AE XML for every B2B and B2G invoice and credit note.
• Carry the master data the format demands: validated TRNs, registered legal names (not trade names), granular addresses, standard unit-of-measure codes, and correct tax-category codes on every line.
• Integrate with your chosen ASP — sending, but also receiving, acknowledgements, rejections and retries.
• Enforce timing: invoices and credit notes issued within 14 days of the business transaction.
• Retain records in the UAE, accessible and auditable.

If you run Odoo, here is the honest status as of mid-2026: Odoo's native Peppol e-invoicing covers roughly 40 mostly European countries, and the UAE is not yet on that list — no official PINT AE module has shipped. Compliance for Odoo users today is an implementation exercise: mapping Odoo's partner, product and tax data to the PINT AE requirements and connecting Odoo to an accredited service provider through a connector or middleware layer. That is exactly the work we do at Oakland, and we do it ASP-agnostic — the architecture is chosen around your volumes and your provider, not the other way round.

Whatever your ERP, the single biggest predictor of a painful project is not the software — it is master data. TRN gaps, trade names where legal names should be, free-text units and inconsistent tax codes fail validation on every platform equally.

How the UAE model compares with Saudi Arabia's

Regional groups often assume their KSA e-invoicing setup transfers. It does not. Saudi Arabia's ZATCA system is a clearance model: invoices are cleared through the authority's platform as part of issuance. The UAE chose decentralised exchange — invoices travel between ASPs while the FTA receives the data in parallel.

The underlying discipline is the same — structured data, validated fields, clean masters — but the plumbing, formats and provider landscape are different. A ZATCA integration does not produce PINT AE, and a KSA-compliant ERP configuration is not UAE-compliant. Budget the UAE as its own project.

Frequently asked questions

Is Peppol mandatory in the UAE?

Effectively yes, for B2B and B2G invoicing from your phase date. The UAE's Electronic Invoicing System runs on the Peppol network, in the PINT AE format, through accredited service providers. From 1 January 2027 (revenue of AED 50 million or more) or 1 July 2027 (everyone else), that is how in-scope invoices must flow.

Do we need to register with Peppol ourselves?

No. Your ASP is the certified access point and handles network participation. Your job is to contract with one of the accredited providers — more than 40 to date — and integrate your system with it.

What is the difference between PINT AE and a regular Peppol invoice?

PINT AE is the UAE-specific version of Peppol's international invoice format. It adds the UAE's requirements from the Data Dictionary — TRN identification, UAE tax categories and the mandatory fields defined by the Ministry of Finance — so a generic Peppol invoice from another country does not automatically qualify.

Can we produce PINT AE files from Excel or Word?

Not realistically. PINT AE is structured XML that must be generated, validated and transmitted through an ASP, with acknowledgements and rejections handled in both directions. That requires a system — an ERP, an accounting platform with a compliance layer, or middleware in front of one.

Does Odoo support PINT AE out of the box?

Not yet. As of mid-2026, Odoo has not shipped native UAE Peppol support or an official PINT AE module. Odoo businesses comply today by mapping their data to PINT AE and connecting to an accredited ASP via a connector or middleware — a well-bounded implementation project, not a blocker.

When does all of this need to be in place?

Working backwards from your go-live: 1 January 2027 for businesses with revenue of AED 50 million or more (ASP appointed by 30 October 2026), and 1 July 2027 for everyone else (ASP by 31 March 2027). The integration typically takes three to six months — the full calendar is in our deadlines and phases guide, and the cost of missing it is in our UAE e-invoicing penalties breakdown.

Oakland is the UAE's #1 Odoo partner and an Odoo Gold Partner — 120+ implementations, 14 certified experts, and winner of Odoo's "Most New Projects" award. As part of ARMOR Group, we are mapping our own six group companies to PINT AE before we ask any client to trust us with theirs. If you want to know exactly which fields in your ERP would fail validation today, book a scoping call with our team.

This article is part of our complete guide to UAE e-invoicing (2026–2027) — start there for the full picture, then dive into the deadlines, penalties, Peppol/PINT AE and choosing an ASP.