Three Names, One Stack
If you have read about UAE e-invoicing, you have probably seen three terms used almost interchangeably: UBL, Peppol BIS Billing 3.0, and PINT AE. They are not the same thing - they sit in a stack, where each layer narrows the rules of the layer below it. Understanding that stack saves a lot of confusion when you talk to vendors.
Layer 1 - UBL (Universal Business Language)
UBL is an OASIS standard that defines business documents - invoices, credit notes, orders, despatch advices - as XML. It is generic, international, and not tied to any country or tax regime. UBL gives you the vocabulary: tags like Invoice, InvoiceLine, TaxTotal, Party, and so on. A valid UBL invoice can describe almost any commercial transaction in any jurisdiction.
The problem with raw UBL on its own is that it is too permissive. The same invoice can be expressed in many valid ways, which means systems on either side cannot reliably exchange them without further constraint.
Layer 2 - Peppol BIS Billing 3.0
Peppol BIS Billing 3.0 is a Business Interoperability Specification built on top of UBL. It picks a single way to express an invoice and adds rules:
- Which UBL elements are required, which are optional
- How identifiers (like VAT numbers) must be formatted
- How tax categories, currencies, and rounding must be handled
- How buyer and seller addresses must be structured
If two systems both implement Peppol BIS Billing 3.0, they can exchange invoices reliably regardless of country. BIS 3.0 is what makes Peppol a real interoperability network rather than just a transport protocol.
Layer 3 - PINT AE
PINT AE is the UAE's national specialisation of Peppol BIS Billing 3.0. It adds the country-specific rules the FTA needs:
- Mandatory TRN (Tax Registration Number) for supplier and customer
- UAE VAT category codes - standard 5 percent, zero-rated, exempt, out-of-scope, with the exact code values the FTA expects
- Free zone handling - including designated zones and the special rules that apply
- Document type codes that match FTA expectations for invoices, credit notes, debit notes, and prepayment documents
- AED as the reporting currency, with conversion rules for multi-currency invoices
- Peppol participant identifier conventions for UAE entities
An invoice that is valid Peppol BIS Billing 3.0 will not automatically be valid PINT AE - it has to also satisfy these UAE-specific rules.
So Which One Does the UAE Require?
The short answer: PINT AE. Every tax invoice issued under the UAE e-invoicing mandate must conform to PINT AE - which means it is also valid Peppol BIS Billing 3.0 and valid UBL, but the binding rule is PINT AE.
You cannot send a generic UBL invoice and expect it to pass. You also cannot send a non-UAE Peppol BIS Billing 3.0 invoice and expect it to pass - it will fail the UAE-specific business rules.
What This Means for Your ERP
Your ERP probably does not produce PINT AE natively. Most ERPs produce one of three things:
- Their own internal invoice record - useful only inside the ERP itself.
- A PDF - human-readable, not machine-readable, not compliant.
- A generic UBL or proprietary XML - not automatically PINT AE.
The Accredited Service Provider (ASP) is the layer that transforms your ERP output into PINT AE. This is the single most important reason you need an ASP rather than trying to send invoices directly to the FTA.
The Mistake to Avoid
"Our system already supports UBL" is not the same as "Our system is PINT AE ready." Every UAE compliance plan should ask the vendor for explicit PINT AE conformance test results, not just UBL or generic Peppol claims.
How InvoiceNet Handles the Stack
InvoiceNet maps your ERP's native invoice records to PINT AE, validates against the FTA business rules, signs the document, and routes it through the Peppol network. You stay on your existing ERP. We handle UBL, Peppol BIS Billing 3.0, and PINT AE as one pipeline.