PINT-AE. The UAE's Peppol invoice schema.

Technical architecture

Base: UBL 2.1 (Universal Business Language). The same foundation used by EU Peppol, Australia Peppol, Singapore InvoiceNow. Interoperability by design.

UAE extensions: cac:PartyTaxScheme with TRN in schemeID "UAE_TRN", VAT 9% rate on every tax bearing line, Arabic language tag in cbc:LanguageID when bilingual invoices, FTA specific UBL customization ID.

Customization ID: "urn:peppol:pint:billing-1@ae-1" identifies a document as PINT-AE compliant. ASPs validate against this before routing.

Profile ID: "urn:peppol:bis:billing" for B2B, extended to cover B2G routing via government endpoints.

Mandatory PINT-AE fields

Issuer and receiver TRN (Tax Registration Number), both 15 digit UAE FTA issued.

Invoice date (cbc:IssueDate), due date, invoice number (unique, sequential per FTA).

Line items: HSN code for goods, service classification for services, unit of measure (ISO 6), VAT category (Standard 9%, Zero, Exempt, Out of scope).

Currency: AED primary. Multi currency allowed with cbc:TaxCurrencyCode always AED for FTA reporting.

Totals: taxable amount, VAT amount, total including tax, rounding difference per FTA rules.

Digital signature: XAdES-B-LT applied by the Accredited Service Provider.

Arabic support: optional but recommended for B2C and regulated industries.

How PINT-AE differs from EU Peppol BIS Billing

UAE does not use EU VAT rates. VAT schemeID explicitly set to "VAT" with 9% for Standard, 0% for Zero rated, "Z" exemption for Exempt, "O" for Out of scope.

TRN format is UAE specific. 15 digits, no country prefix. EU VAT numbers include country code (e.g. DE, FR, NL).

Mandatory Arabic support for bilingual invoice templates. EU Peppol has no Arabic baseline.

FTA customization ID distinct from EU BIS Billing. ASPs must validate the UAE schema, not the EU one.

7 year archival requirement per UAE Federal Law, vs 10 year varying by EU country.

How ERPNext implements PINT-AE

OSForBiz configures the ERPNext Sales Invoice doctype with PINT-AE export hooks. At submit time, an XML document is generated in PINT-AE format using the UBL 2.1 spec.

The XML is handed to the registered Accredited Service Provider via its API. ASP applies the XAdES digital signature, logs the submission with FTA, and routes to the buyer's ASP endpoint.

Receipt acknowledgement flows back into ERPNext as a custom field on the invoice. Signed XML + acknowledgement archived for 7 years per UAE law.

All of this is automatic. Your accounts team keeps raising invoices the same way they always did.