A plain-English guide to the UAE's mandatory e-invoicing XML format — what it is, how it differs from standard Peppol, what fields it requires, and what it means for your accounting software.
By Ashish Singh, Founder of Infotree Computers LLC | Updated June 2026 | Read time: ~10 minutes
Quick answer: PINT-AE is the UAE's official e-invoicing XML standard — a locally customised version of the international Peppol PINT format, mandated by the FTA for all B2B and B2G e-invoices from Phase 1 of the UAE's e-invoicing rollout. If your accounting software generates e-invoices for the UAE, they must be structured as valid PINT-AE XML and transmitted through a Peppol-connected Accredited Service Provider (ASP). This guide explains exactly what PINT-AE is, how it differs from standard Peppol, what fields it requires, and what it means in practice for businesses using QuickBooks, Sage 50, or Odoo.
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).
Peppol (Pan-European Public Procurement On-Line) is a global network and set of open standards that allow businesses, governments, and their software systems to exchange structured electronic documents — invoices, credit notes, purchase orders — with each other, regardless of which accounting software or country they use.
Think of it like email, but for invoices: just as Gmail users can send emails to Outlook users without both parties agreeing on a common email platform, a business using QuickBooks in Dubai can send a compliant e-invoice to a government entity using its own procurement system — provided both are connected to the Peppol network through a certified access point.
Peppol was originally created in Europe and is now administered globally by OpenPeppol, a non-profit membership organisation. More than 40 countries, including Singapore, Australia, and now the UAE, have adopted Peppol as their national e-invoicing infrastructure.
The Peppol network works on a four-corner model:
Your accounting software sends the invoice to your ASP. Your ASP routes it through the Peppol network to the recipient's ASP. The recipient's system receives a fully structured XML document that can be read by machine — no manual re-entry, no PDF parsing, no manual reconciliation.
As Peppol expanded beyond Europe, there was a need for a single international baseline — a common set of core invoice fields that any Peppol-connected system in any country can understand. That baseline is called PINT: Peppol International CIUS (Core Invoice Usage Specification).
PINT defines the minimum required invoice fields, the data types, the code lists, and the validation rules that every Peppol invoice must meet — regardless of country. It is built on top of UBL 2.1 (Universal Business Language), the XML schema used as the technical backbone of Peppol.
PINT is not country-specific. It is the international floor. Individual countries then create their own CIUS (Core Invoice Usage Specification) — a local extension of PINT that adds country-specific mandatory fields, code lists, and business rules on top of that common foundation.
PINT-AE is the UAE's national CIUS — the UAE-specific extension of the international PINT standard, mandated by the Federal Tax Authority (FTA) as the required format for all UAE e-invoices transmitted through the Peppol network.
The "AE" stands for Arab Emirates (the ISO 3166-1 alpha-2 country code for the UAE). PINT-AE is developed and maintained by the FTA in collaboration with OpenPeppol, and its specification is publicly available from the FTA's official e-invoicing documentation.
In practical terms, PINT-AE is an XML document format. Every invoice your business issues to a UAE VAT-registered business (B2B) or to a government entity (B2G) must be structured according to PINT-AE's rules before being submitted through your ASP to the FTA and the buyer.
A PINT-AE document is still a standard Peppol invoice at its core — it passes all international Peppol validation rules — but it also passes a second layer of UAE-specific validation rules that PINT alone does not require.
Understanding what PINT-AE adds on top of international PINT helps clarify why UAE e-invoicing requires specialised software rather than a generic Peppol connector. The main UAE-specific additions are:
| Field / Rule | Standard PINT | PINT-AE Addition |
|---|---|---|
| Supplier TRN (Tax Registration Number) | Optional or VAT number | Mandatory, must be 15 digits |
| Buyer TRN | Conditional | Mandatory for B2B; must be 15 digits |
| Emirate code on address | Not required | Mandatory — specific code list for each emirate (e.g. AE-DU for Dubai) |
| Supply type code | Not required | Mandatory — distinguishes standard-rated, zero-rated, exempt, out-of-scope, and reverse-charge supplies |
| Invoice type code | Basic code | Specific UAE code list: 380 (invoice), 381 (credit note), 386 (prepayment) |
| VAT category code per line | Recommended | Mandatory per line item |
| Currency | Any ISO 4217 | AED required; tax amounts always in AED even if invoice currency differs |
| Peppol ID format | Country-specific | UAE Peppol IDs use scheme 0230 (TRN-based) |
These additions exist because UAE VAT law and FTA audit requirements are more granular than what international PINT covers by default. An invoice that passes standard Peppol validation can still fail PINT-AE validation if, for example, the emirate code is missing or the supply type is not specified at the line level.
A PINT-AE invoice is an XML file that follows the UBL 2.1 schema with Peppol-specific and UAE-specific extensions. You do not need to write XML manually — your ASP or e-invoicing software generates it automatically from your accounting data. But it helps to understand the key sections:
The top of the document identifies the invoice type, the customisation ID (which confirms this is a PINT-AE document), the process ID, the invoice number, the issue date, and the currency code. The CustomizationID field for UAE invoices will always contain the PINT-AE specification identifier.
Each party block contains the legal name, postal address (including the UAE emirate code in the CountrySubentityCode field), TRN in the CompanyID field under tax scheme VAT, and the Peppol endpoint ID using scheme 0230.
PINT-AE requires a detailed tax total section that breaks down the taxable amount and VAT amount by VAT category (standard-rated at 5%, zero-rated, exempt, reverse charge, out-of-scope). This is what allows the FTA to reconcile invoice-level tax data against your quarterly VAT 201 return.
Every invoice line must carry a description, quantity, unit price, line total, and VAT category code. Discounts and allowances must be structured according to the UBL schema, not embedded as free-text adjustments.
The legal monetary total block gives the line total, allowance total, tax-exclusive total, VAT amount, and payable amount — all in AED. For foreign-currency invoices, the accounting currency is still AED and the exchange rate must be declared.
If you use QuickBooks Online, here is where InvoiceUAE pulls each mandatory field from:
| Field ID | Name | Required? | Source in QBO |
|---|---|---|---|
BT-1 | Invoice number | Mandatory | QBO Invoice Number |
BT-2 | Invoice date | Mandatory | QBO Invoice Date |
BT-3 | Invoice type code | Mandatory | 380 (invoice) / 381 (credit note) |
BT-6 | Currency code | Mandatory | AED (for UAE) |
BT-27 | Seller name | Mandatory | Company Settings |
BT-31 | Seller VAT (TRN) | Mandatory | Company Settings → TRN |
BT-44 | Buyer name | Mandatory | QBO Customer Name |
BT-48 | Buyer VAT (TRN) | B2B only | Customer Master → TRN |
BT-151 | Line VAT category | Mandatory | QBO Line Item Tax |
BT-76 | Buyer reference | PINT-AE v1.1 | QBO PO Number / Memo |
<Invoice>
<cbc:ID>INV-2026-001</cbc:ID>
<cbc:IssueDate>2026-06-01</cbc:IssueDate>
<cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
<cbc:DocumentCurrencyCode>AED</cbc:DocumentCurrencyCode>
<cac:AccountingSupplierParty>
<cbc:RegistrationName>Your Company LLC</cbc:RegistrationName>
<cbc:CompanyID>100123456789012</cbc:CompanyID> <!-- Your TRN -->
</cac:AccountingSupplierParty>
<cac:AccountingCustomerParty>
<cbc:RegistrationName>Buyer Company FZE</cbc:RegistrationName>
<cbc:CompanyID>100987654321098</cbc:CompanyID> <!-- Buyer TRN -->
</cac:AccountingCustomerParty>
<cac:InvoiceLine>
<cbc:InvoicedQuantity>10</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount>5000.00</cbc:LineExtensionAmount>
<cac:TaxTotal>
<cbc:TaxAmount>250.00</cbc:TaxAmount>
<cbc:ID>S</cbc:ID> <!-- Standard rate -->
</cac:TaxTotal>
</cac:InvoiceLine>
<cac:LegalMonetaryTotal>
<cbc:TaxExclusiveAmount>5000.00</cbc:TaxExclusiveAmount>
<cbc:TaxInclusiveAmount>5250.00</cbc:TaxInclusiveAmount>
<cbc:PayableAmount>5250.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
</Invoice>The FTA's decision to build UAE e-invoicing on the Peppol network rather than a proprietary national platform was deliberate and has significant advantages for businesses:
You may encounter references to IBT numbers when reading PINT-AE technical documentation. IBT stands for Invoice Business Term — they are simply the unique identifiers used in the Peppol specification to refer to each field.
For example:
IBT numbers are primarily relevant to software developers building PINT-AE integrations. As a business owner or accountant, you will never see IBT numbers in your day-to-day workflow — your ASP and e-invoicing software handle the field mapping internally.
Before an invoice is accepted by the FTA's system, it passes through two layers of validation:
The XML document is checked against the UBL 2.1 schema to confirm it is structurally valid XML. Missing closing tags, incorrect data types, or malformed elements will fail here.
The document is then checked against PINT-AE's business rules — a set of named validation assertions. These rules enforce things like: TRN must be exactly 15 digits, the emirate code must be from the approved code list, VAT amounts must mathematically match the declared rate, and the invoice date cannot be in the future.
If an invoice fails either layer of validation, it is rejected with an error code and a description of what failed. Your ASP surfaces these errors as human-readable rejection reasons so you can correct and resubmit.
Common PINT-AE validation failures in practice:
An Accredited Service Provider (ASP) is a company accredited by the FTA to connect businesses to the UAE Peppol network. Your accounting software generates — or, more likely, your e-invoicing middleware generates from your accounting data — a PINT-AE XML document. Your ASP then receives that XML, validates it, signs it, and transmits it through the Peppol network to the buyer and to the FTA's system.
You cannot connect to the UAE Peppol network directly as a business — you must go through an accredited ASP. The ASP is your Peppol Access Point (Corner 2 in the four-corner model described earlier).
Key things your ASP does that your accounting software does not:
InvoiceUAE integrates directly with TaxStar, one of the FTA's approved ASPs, so the PINT-AE generation, validation, signing, and transmission happen in a single workflow from inside your accounting software connection — you do not need to manage the ASP relationship separately.
No — at least not in Phase 1. The UAE e-invoicing mandate is being rolled out in phases, and the scope expands with each phase:
This will change as the rollout progresses. Businesses should monitor FTA announcements for their cohort date — once you are in scope, all eligible B2B invoices must be transmitted as PINT-AE XML through a Peppol ASP.
Your accounting software (QuickBooks Online, Sage 50, Odoo, etc.) almost certainly cannot generate valid PINT-AE XML natively. These platforms are built for general-purpose bookkeeping and do not include UAE-specific Peppol connectors or FTA validation logic.
The practical path for most UAE businesses is:
InvoiceUAE handles steps 1 through 4 for QuickBooks Online users, including a built-in AI validator that checks your invoices against PINT-AE rules before submission and flags specific fields that need correction — so you fix issues before the FTA rejects the document, not after.
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 →No, but they are related. UBL 2.1 (Universal Business Language) is the underlying XML schema that PINT-AE is built on. PINT-AE is a specification that says which UBL fields are mandatory, which are conditional, and what UAE-specific rules apply on top of the standard UBL structure. UBL is the grammar; PINT-AE is the UAE rulebook written in that grammar.
No. Business owners and accountants do not interact with raw XML. Your e-invoicing software generates the XML behind the scenes. What you do need to ensure is that your accounting records contain the correct data — complete TRNs, correct emirate addresses, proper VAT categorisation — so that the XML generated from that data passes PINT-AE validation. The XML is the output; clean accounting data is the input.
Saudi Arabia's e-invoicing system (ZATCA) uses a different technical standard — it is based on UBL and XML like PINT-AE, but with its own CIUS, its own clearance and reporting model, and its own Fatoora portal. UAE PINT-AE and Saudi ZATCA are not interoperable. Software built for ZATCA compliance does not automatically comply with PINT-AE, and vice versa. If you operate in both countries, you need a solution that supports both standards independently.
The FTA's system rejects it. The rejection comes with a specific error code and description indicating which PINT-AE rule failed. You correct the data, regenerate the XML, and resubmit. Repeated non-compliance after the mandatory deadline for your cohort can attract FTA penalties — which are covered in detail in our UAE E-Invoicing Penalties 2026 guide.
The FTA publishes the PINT-AE specification through its official e-invoicing portal. OpenPeppol also maintains the technical documentation at their website. InvoiceUAE's validation engine is built directly against the published PINT-AE validation rules, updated as the FTA issues amendments.
Don't want to hand-build PINT-AE XML validation yourself? InvoiceUAE generates and validates compliant PINT-AE XML automatically from QuickBooks, Zoho Books, Xero, Sage, Odoo, and Dynamics 365.
Start Free Trial →PINT-AE is the UAE's mandatory e-invoicing XML format — a Peppol-based standard that specifies exactly how invoice data must be structured for FTA-compliant transmission. It adds UAE-specific requirements on top of international PINT: TRN fields, emirate codes, supply type codes, and AED tax amounts. Valid PINT-AE XML must be generated by your e-invoicing software and transmitted through an FTA-accredited ASP, not sent directly by your accounting platform.
For businesses using QuickBooks Online, InvoiceUAE handles the full PINT-AE workflow — syncing your invoices, enriching UAE-specific fields, validating against FTA rules before submission, and transmitting through TaxStar. Start your free trial to see the complete workflow for your invoice data.