The Problem PINT AE Solves
Every country with an e-invoicing mandate needs a standard. Without one, the same invoice would be valid in one system and rejected in another. The Federal Tax Authority's answer for the UAE is PINT AE - the Peppol Invoice Standard for the UAE - based on Peppol BIS Billing 3.0 in UBL XML.
If you are using a PDF or a custom JSON, you are not compliant under the UAE mandate. Tax invoices must be structured, machine-readable, and conform to the PINT AE schema.
What PINT AE Actually Is
PINT AE is a localisation of the international Peppol BIS Billing 3.0 standard. Three things make it specifically "for the UAE":
- Country-specific business rules - mandatory VAT identifiers, free zone designations, and FTA-specific document codes.
- Currency and tax rates - AED-default amounts, the 5 percent standard VAT rate, zero-rated and exempt category handling.
- Cardinality constraints - which fields are required, which are optional, and what cross-field validations apply.
The base format is UBL XML - Universal Business Language. UBL is an OASIS standard that defines invoices, credit notes, and supporting documents as XML elements.
What an Invoice Looks Like
A PINT AE invoice is a structured XML document. The key sections are:
- Header - document type code, invoice number, issue date, currency code, due date.
- Supplier party - name, address, TRN, Peppol identifier.
- Customer party - same fields for the buyer.
- Line items - description, quantity, unit, unit price, tax category, tax rate.
- Tax totals - subtotal per VAT rate, total tax, total amount due.
- Payment terms - IBAN, due date, payment means code.
Each of these maps to specific UBL elements with strict cardinality and data types. A small formatting error in a single line can fail FTA validation.
PINT AE vs Generic UBL
People sometimes use "UBL" and "PINT AE" interchangeably. They are not the same. Generic UBL is the global syntax. PINT AE adds the UAE-specific business rules on top - the mandatory fields, the FTA codes, the validation rules. An invoice that is valid generic UBL can easily be invalid PINT AE if it is missing UAE-specific elements.
How PINT AE Travels
PINT AE invoices are exchanged over the Peppol network, not via direct file transfer or email. The supplier's Accredited Service Provider (ASP) hands the document into Peppol; the customer's ASP receives it; both ASPs simultaneously report the document to the FTA. This is the 4-corner model.
What Your ERP Needs to Output
Most ERP systems do not produce PINT AE natively. They produce internal invoice records that must be transformed to PINT AE through a connector. Typical mapping work covers:
- Master data - customer TRN, Peppol participant ID, addresses
- Item catalogue - unit codes (each, kg, hour), tax categories
- Document types - invoices, credit notes, debit notes, prepayments
- Free zone and de-minimis handling
- Multi-currency conversion to AED for reporting
Common Pitfalls
- Missing TRN on the customer party. A surprisingly common cause of rejection during pilots.
- Wrong tax category codes. Standard rate, zero-rated, exempt, and out-of-scope each have specific codes; using a wrong one fails validation.
- Free zone handling. Free zone designated zones have specific rules - a generic UBL profile will not handle them.
- Rounding mismatches. Line-total rounding vs document-total rounding must reconcile.
- Foreign currency invoices. A USD invoice still needs an AED equivalent for FTA reporting.
How InvoiceNet Handles PINT AE
InvoiceNet sits between your ERP and the Peppol network. We pull the invoice data through an API or batch integration, transform it to PINT AE, validate it against the FTA business rules, sign it, exchange it through Peppol, and report it to the FTA - in one pipeline. You keep your existing ERP. We handle the format.