PINT AE: the UAE specialisation of Peppol’s international model, and how it relates to EN 16931
PINT AE is the UAE flavour of Peppol’s international billing model, adding UAE terms and rules; unlike the EU flavour, it does not claim conformance to EN 16931.
PINT is the international billing model OpenPeppol’s Post Award Coordinating Community made as a template for globally interoperable invoice specifications. PINT AE describes itself as a national customisation of PINT for the UAE; its identifier is urn:peppol:pint:billing-1@ae-1, where the part after @ names the specialisation.
Terms in the model carry the IBT prefix, and the UAE adds BTAE terms such as the transaction type code (BTAE-02), the unique identifier (BTAE-07) and line amounts in AED (BTAE-08, BTAE-10). An invoice must pass the rules shared by every PINT implementation and then the UAE rules, IBR-xxx-AE.
The EU flavour, PINT EU, states that it is a Core Invoice Usage Specification of EN 16931-1:2017, so a conforming invoice conforms to the standard. PINT AE makes no such statement, although its datatype tables refer to EN 16931. The current release is 1.0.4 (final on 2 June 2026), with a separate self-billing specification and a Tax Data Document specification beside it.
In JooDax
Partly builtJooDax writes the PINT AE identifier in every document. The module was built from specification 1.0.1, and on 9 November 2026 its rules were checked again, one by one, against the published PINT AE Schematron tests: the 5% standard rate is now enforced, and reverse charge is refused as not built. The official Schematron has not been run on a JooDax document.
crates/jdx-einvoice-ae/src/lib.rs
Questions and answers
What is the difference between IBT and BTAE?
IBT terms belong to the shared international model; BTAE terms were added by the UAE, such as the transaction type flags and the line amounts in AED.
May a business add its own optional fields to PINT AE?
No. The guidelines say businesses may not add optional fields of their own and should discuss special needs with their provider.
Related pages
Related concepts
- The five-corner model (DCTCE) behind UAE e-invoicingAn invoice never goes straight from seller to authority: it passes through the seller’s provider and the buyer’s provider, and each reports to the Federal Tax Authority.
- Tax invoice and commercial invoice in the UAE systemThe tax invoice (380) is for supplies under VAT, the commercial invoice (480) for sales needing no tax invoice; each has its credit note and its own field list.
E-invoicing in the UAE (PINT AE)
Sources
- PINT AE Billing version 1.0.4 (v1.0.4 (PDK 1.4.4, released 29 Jul 2026)) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – specification text (BIS) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- Peppol PINT BIS Billing version 1.1.3 (specification text) (v1.1.3) — OpenPeppol AISBL (docs.peppol.eu)
- EU PINT Billing V1.1.1 (v1.1.1) — OpenPeppol AISBL (docs.peppol.eu)
- PINT AE Billing 1.0.4 – Invoice transaction, semantic model (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- Release notes for PINT AE Billing (v1.0.0 to 1.0.4) — OpenPeppol AISBL (docs.peppol.eu)
- UAE Electronic Invoicing Guidelines (vV 2.0) — Ministry of Finance, United Arab Emirates
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.