A technical, field-by-field breakdown of the PINT-AE XML structure — why PDFs alone no longer comply, and how TRNs, UUIDs, and invoice type codes fit together.
A PDF invoice looks correct to a human, but it tells a tax authority's system nothing it can validate automatically. That's the core reason the UAE mandate requires PINT-AE — a structured XML format designed to be parsed, validated, and cross-checked by machines at every corner of the Peppol network, not just read visually. This is a field-level technical reference; if you want the plain-English version first, read What is PINT-AE? UAE Peppol Standard Explained.
InvoiceUAE is built by Infotree Computers LLC, a Dubai-based technology firm that has been implementing QuickBooks, Sage 50, Sage 300, Zoho One and Zoho Books for UAE and GCC businesses for 14 years. Infotree is a Certified QuickBooks ProAdvisor, Authorized Zoho Partner, Authorized Sage Partner, and holds Odoo Gold Partner status at the Gold level through an affiliate partnership. The team operates from offices in Dubai (UAE), Saudi Arabia, and Bhubaneswar (India), and InvoiceUAE's ASP partner is TaxStar (FTA-approved).
Before the mandate, most UAE businesses issued invoices as PDF or paper documents with VAT details printed on them. That remains useful for the human reading the invoice, but it cannot be:
A PINT-AE invoice document is composed of two layers:
| Field | UBL Element (simplified) | Purpose |
|---|---|---|
| Supplier TRN | AccountingSupplierParty / PartyTaxScheme / CompanyID | Supplier's 15-digit UAE Tax Registration Number |
| Buyer TRN | AccountingCustomerParty / PartyTaxScheme / CompanyID | Buyer's TRN — mandatory for B2B invoices |
| Peppol Endpoint ID | EndpointID (with schemeID attribute) | Identifies each party's Peppol network address, issued via their ASP |
| Invoice UUID | UUID | Globally unique identifier for the specific invoice instance, distinct from the human-readable invoice number |
| Invoice Type Code | InvoiceTypeCode | Numeric Peppol code — e.g. 380 (Commercial Invoice), 381 (Credit Note), 383 (Debit Note) |
| Emirate Code | UAE PINT extension on PostalAddress | One of AD, DU, SH, AJ, UQ, RK, FU — required for tax jurisdiction reporting |
| Supply Type | UAE PINT extension per InvoiceLine | Goods, Services, or Mixed — classified per line item |
| Tax Category | TaxCategory / ID | S (Standard 5%), Z (Zero-rated), E (Exempt), O (Out of Scope) |
PINT-AE uses standard Peppol numeric type codes rather than free-text labels, which is what allows automated validation on both ends of the network:
The standard invoice type for goods or services rendered.
Must reference the original invoice's UUID and invoice number to maintain an auditable link.
Used for additional charges against an original invoice, also referencing the original document.
PINT-AE requires both a human-readable invoice number (e.g. INV-2847, whatever your accounting system already generates) and a machine-generated UUID unique to that specific XML document instance. The UUID exists so that ASPs and the FTA's data hub can de-duplicate and track documents at the network level, independent of however individual businesses format their own invoice numbering.
Not sure if your accounting system is ready for UAE e-invoicing? Contact Infotree for a GAP Analysis and System Impact Assessment — we'll map exactly where your setup stands against PINT-AE requirements before your ASP deadline. Have other accounting-related issues or e-invoicing compliance questions? Contact us — we're happy to help.
Request a Free GAP Analysis →Need hands-on help? Contact Infotree for UAE e-invoicing implementation — from ASP selection to go-live testing, our team handles the full setup, whichever accounting system or ERP you run.
Contact Us for E-Invoicing Implementation →The official format is PINT-AE — the Peppol International invoice model localized for the UAE, expressed as UBL 2.1 XML wrapped in an SBDH envelope. It is mandated by the Federal Tax Authority for all VAT-registered businesses under the phased e-invoicing rollout.
No. A PDF or scanned image cannot be automatically validated or transmitted through the Peppol 5-corner network. The FTA requires structured PINT-AE XML; a PDF may still be generated and sent as a human-readable courtesy copy alongside the XML, but it does not satisfy the compliance requirement on its own.
The invoice number is the human-readable identifier your business already uses (e.g. INV-2847). The UUID is a separate, machine-generated unique identifier for that specific XML document instance, used by ASPs and the FTA to track and de-duplicate documents across the network.
Credit notes (type code 381) must correctly reference the original invoice's UUID and invoice number. Missing or mismatched references to the original document are one of the most common rejection reasons ASPs report during PINT-AE validation.
InvoiceUAE generates fully compliant PINT-AE XML automatically from your QuickBooks, Zoho, Xero, Sage, or Odoo invoices — every mandatory field mapped correctly.
Start Free Trial →
Ashish Singh is a UAE E-Invoicing specialist at Infotree Computers LLC, Dubai, helping SMEs and enterprises implement FTA-compliant Peppol PINT-AE workflows across QuickBooks, Zoho, Odoo, Xero, and Sage.