Saltar al contenido
Volver al blog
UAEPublicado 3 de julio de 20268 min de lectura

PINT AE format explained: structure, tax categories and validation

PINT AE is the UAE’s Peppol International invoice format, built on UBL and EN 16931. How it is structured, the VAT categories it uses, how it differs from Peppol BIS, and how it is validated.

Every UAE e-invoicing conversation ends at one term: PINT AE. It is the format your invoices have to be in. Here is what it actually is, without the jargon.

What PINT AE is

PINT AE is the UAE’s profile of Peppol International (PINT), built on the UBL syntax and aligned with the EN 16931 semantic model — the same European core behind XRechnung and Peppol BIS. So if you have seen a Peppol invoice, PINT AE will look familiar: the same UBL backbone, with a UAE-specific rulebook and code lists on top.

How it is structured

At the core it is a UBL Invoice (or Credit Note) carrying the EN 16931 business terms: parties, references, lines, allowances and charges, a tax breakdown and totals. PINT AE narrows that — it makes certain fields mandatory, adds UAE identifiers (TRN with scheme, Trade Licence, emirate codes), a transaction-type marker, and item-level pricing and classification rules.

The tax categories

PINT AE handles UAE VAT at 5% through a set of categories: standard-rated, zero-rated, exempt, out-of-scope, reverse charge, and a margin-scheme category. Two of them — reverse charge and margin scheme — disclose a rate but collect no VAT, so the tax breakdown has to be handled carefully or it will not reconcile.

How it differs from Peppol BIS (and PINT OM / SG)

  • It uses UAE tax semantics (5% VAT, UAE categories) rather than EU VAT rules.
  • It requires UAE identifiers and an emirate code that Peppol BIS does not ask for.
  • It carries a transaction-type marker specific to UAE supplies.
  • It is a sibling of PINT OM (Oman) and PINT SG (Singapore) — same PINT family, different national rulebooks.

How it is validated

A PINT AE document is checked on two levels: XSD for structure (is it well-formed UBL), and Schematron business rules for the UAE requirements (are the mandatory fields present, do the VAT amounts reconcile, is the transaction type valid). A file can be perfectly well-formed XML and still fail the rules — which is why you validate before it reaches your Accredited Service Provider.

Generating and validating PINT AE

You do not author UBL by hand. Send the data you already export and request the PINT AE profile; get back a validated document, structure and rules checked:

curl -X POST https://api.myinvoice.llc/v1/convert \
  -H "X-API-Key: ek_live_..." \
  -F "[email protected]" \
  -F "format=csv" \
  -F "profile=pint-ae"

Buyer-issued invoice? The self-billing profile covers it (profile=pint-ae-sb) — same input, self-billing-compliant output.

Generate a UAE invoice in your browserRead the API docs