PINT-AE and Peppol: the formats and the network
PINT-AE is the UAE's invoice data specification, based on the international PINT profile and UBL 2.1 XML. It travels over the Peppol network in a five-corner model: sender, sender's provider, receiver's provider, receiver, and the Federal Tax Authority.
Last reviewed 2026-09-10
The format
PINT-AE is a specification, not a product. It defines which fields an invoice must carry, how they are named, and which combinations are valid — TRNs, tax categories, line-level amounts, references to earlier documents, and so on. Technically it is UBL 2.1 XML, the same family used across Europe and much of Asia, tailored to UAE tax requirements.
Because it is a specification, an invoice is either valid or it is not. There is no partially acceptable invoice, and no human on the other side to interpret an unusual layout. That is the real change for finance teams: correctness moves upstream, into how your master data and item setup are maintained.
The five-corner model
The fifth corner is what distinguishes the UAE model from ordinary Peppol exchange elsewhere. Reporting to the authority is part of the transaction, not a separate return you compile later.
| Corner | Who |
|---|---|
| 1 | You, the supplier, in your accounting system |
| 2 | Your Accredited Service Provider |
| 3 | Your customer's Accredited Service Provider |
| 4 | Your customer |
| 5 | The Federal Tax Authority, which receives the reported invoice data |
Message Level Responses
An MLR is the network's answer to your invoice: accepted, accepted with warnings, or rejected with reasons. It is the single most operationally important artefact in the whole model, because it is the only thing that tells you an invoice did not arrive.
Treat MLRs like bank statement exceptions. Someone must look at them daily, and unmatched or rejected documents need an owner. A cockpit view that shows acknowledgement rate and open rejections in one place turns this from a chase into a routine.
Questions people ask
What is PINT AE?
The UAE-specific Peppol International invoice specification, expressed as UBL 2.1 XML, that defines the required structure and content of a compliant UAE e-invoice.
What is a Message Level Response?
The structured acknowledgement returned over the Peppol network telling you whether your invoice was accepted or rejected and why.
Official sources
- Federal Tax Authority — UAE e-invoicing
- Ministry of Finance — eInvoicing initiative
- OpenPeppol — the Peppol network and PINT
- Deloitte Middle East — UAE e-invoicing legislation
General information, not tax or legal advice. Confirm your own position with the Federal Tax Authority or your tax adviser.
See how this looks on a dashboard
TaxFlow Cockpit shows transmission, acknowledgement and rejection across your entities and accounting platforms in one view.