← Back to .NET Made Easy

UAE PINT-AE E-Invoicing Explained for Developers and SMEs

Published September 2, 2026

The UAE Federal Tax Authority (FTA) is rolling out mandatory e-invoicing, and the format it's built on — PINT-AE — is going to touch two very different audiences at once: small business owners who just want their invoices to stay compliant, and developers who are going to be asked to build or wire up the integration. This article covers both angles: what PINT-AE actually is, when it becomes mandatory, what's inside the XML from a technical standpoint, and how to check an invoice against it today, for free, without waiting for your accounting software vendor to ship support.

What is PINT-AE?

PINT-AE stands for Peppol International Invoicing model for the UAE. It's a UAE-specific specialization of the international Peppol e-invoicing network's data model, itself based on UBL 2.1 (Universal Business Language) — an OASIS XML standard already used for e-invoicing in dozens of countries.

In practice, that means a compliant UAE e-invoice is no longer a PDF, a scanned image, or an Excel sheet emailed to a customer. It's a structured XML document with well-defined fields — supplier and buyer tax identifiers, invoice and due dates, line items with quantities and unit prices, VAT rates and amounts per line, and invoice-level totals — that can be parsed, validated, and exchanged automatically between systems, typically through an Accredited Service Provider (ASP) on the Peppol network.

When does it become mandatory?

The FTA has published a phased rollout rather than a single hard cutover date:

If you're a developer building or maintaining invoicing, ERP, or accounting integrations for UAE clients, this timeline is your real deadline — client demand for PINT-AE support will start well before the "mandatory" date, as accountants push their vendors to be ready early.

What's actually inside a PINT-AE invoice?

For developers, the useful way to think about PINT-AE is as UBL 2.1's Invoice document type with a specific customization ID and a defined set of required fields. A minimal skeleton looks like this:

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
         xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
         xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:peppol:pint:billing-1@ae-1</cbc:CustomizationID>
  <cbc:ID>INV-2026-014</cbc:ID>
  <cbc:IssueDate>2026-08-01</cbc:IssueDate>
  <cbc:DocumentCurrencyCode>AED</cbc:DocumentCurrencyCode>
  <cac:AccountingSupplierParty>...</cac:AccountingSupplierParty>
  <cac:AccountingCustomerParty>...</cac:AccountingCustomerParty>
  <cac:TaxTotal>...</cac:TaxTotal>
  <cac:LegalMonetaryTotal>...</cac:LegalMonetaryTotal>
  <cac:InvoiceLine>...</cac:InvoiceLine>
</Invoice>

The parties are identified by their Tax Registration Number (TRN), tax totals are broken out per line and rolled up at the invoice level, and each InvoiceLine carries its own quantity, price, and VAT subtotal. If you've worked with any other Peppol BIS Billing 3.0 implementation (used across the EU), the shape will feel familiar — PINT-AE is a regional variant of the same underlying model, not a from-scratch format.

The gap most SMEs are sitting in right now

Most UAE small businesses currently generate invoices as PDFs from Excel templates, Tally, Zoho Books, or QuickBooks. None of that output has any PINT-AE compliance value on its own — a PDF is a rendering, not structured data, and there is no reliable way to programmatically extract a TRN or a per-line VAT amount back out of it. The practical starting point for most SMEs is the CSV or Excel export their accounting software already produces, since that at least contains structured columns that can be mapped onto the required XML fields.

Check your invoices for free

Layerbit built a free, browser-based UAE PINT-AE Compliance Checker that does exactly this: upload a CSV or Excel invoice export, auto-detect (or manually map) the required fields, get a plain-language compliance score, and download a UBL 2.1 / PINT-AE structured XML file — no signup, and nothing ever leaves your browser.

Try the PINT-AE Checker →
Note — no liability accepted: This article and the linked tool are prepared from publicly available Peppol and FTA technical guidance and are intended as a practical starting point, not tax or legal advice. Neither .NET Made Easy nor Layerbit is liable for any tax, legal, financial, or regulatory consequence — including rejected filings or non-compliance penalties — arising from their use. Always have an Accredited Service Provider (ASP) or a qualified UAE tax advisor validate your final invoices before you file.

Frequently Asked Questions

What is PINT-AE?

PINT-AE is the UAE's e-invoicing data format: a UBL 2.1-based XML structure, built on the international Peppol network, that the Federal Tax Authority (FTA) is mandating in place of PDF or Excel invoices. It defines a machine-readable structure for invoice header data, tax registration numbers, line items, and tax totals so invoices can be validated and exchanged automatically.

When is UAE e-invoicing mandatory?

Based on published FTA timelines, e-invoicing is voluntary from July 2026, mandatory from January 2027 for businesses with annual revenue of AED 50 million or more, and mandatory for all other VAT-registered businesses from July 2027.

Is there a free tool to check if an invoice is PINT-AE compliant?

Yes. Layerbit's UAE PINT-AE Compliance Checker is a free, browser-based tool that scores a CSV or Excel invoice export against the required PINT-AE fields and generates a UBL 2.1 / PINT-AE structured XML file, entirely client-side with no signup.

Get in touch

Found an error, have a suggestion, or building your own PINT-AE integration? Use the Contact Support button on the site.