Aller au contenu
Retour au blog
UAEPublié le 5 juillet 20269 min de lecture

PINT AE mandatory fields: a field-by-field guide for UAE e-invoices

The mandatory fields a UAE PINT AE e-invoice must carry — TRN and scheme identifiers, emirate codes, the transaction-type profile, line-level pricing and the 5% VAT breakdown — plus the fields that trigger rejections.

Your ERP already holds most of an invoice. PINT AE — the UAE’s Peppol International format — insists on a specific set of mandatory fields, and missing one means your Accredited Service Provider, or the validation rules, bounce the document. Here is the field-by-field picture of what a UAE e-invoice must carry.

What PINT AE adds on top of a “normal” invoice

PINT AE is built on UBL and the EN 16931 semantic model, then narrowed with UAE-specific rules. So it demands more than a plain invoice: identifiers with the right scheme, an emirate on the address, a transaction-type marker, and a VAT breakdown that reconciles to the fils. The data usually exists in your system — it just is not shaped or labelled the way the rules require.

Seller and buyer — mandatory identity fields

  • Tax Registration Number (TRN) for the seller — and for the buyer in B2B — carried with the correct scheme identifier, not as a plain string.
  • Legal registration name and the company’s legal identifier (e.g. Trade Licence), with its scheme/agency attributes.
  • Full postal address including the emirate as a country-subdivision code (Abu Dhabi AUH, Dubai DXB, Sharjah SHJ, Ajman AJM, Umm Al Quwain UAQ, Ras Al Khaimah RAK, Fujairah FUJ).
  • Electronic endpoint identifiers so the document can be routed on the network.

The most common miss here is a TRN without its scheme, or an address with no emirate code — both fail validation even though the value “looks” present.

The transaction-type profile (easy to overlook)

PINT AE encodes what kind of supply this is in a transaction-type marker (a profile-execution identifier). It flags things like free-trade-zone, deemed supply, margin scheme, summary invoice, continuous supply and exports. Get the wrong flag — or omit it — and an otherwise valid invoice is rejected. Credit notes additionally carry a reason code.

Line-level mandatory fields

  • Item name, quantity and the unit of measure as a valid UN/ECE code.
  • Net price and the line net amount.
  • A price base quantity, and a line allowance/charge where a gross price applies.
  • The VAT category for the line, and a commodity/nature classification where required.

VAT and the tax breakdown (5%)

UAE VAT is 5%. Every line needs the correct category — standard-rated, zero-rated, exempt, out-of-scope, reverse charge, or the margin-scheme category — and the document needs a tax breakdown per category that reconciles: the taxable base and tax amount must add up to the totals, to the fils. Reverse-charge and margin-scheme lines disclose a rate while collecting no VAT, which trips teams that assume “rate present = tax collected.”

The fields teams miss most

  • TRN present but without its scheme identifier.
  • No emirate country-subdivision code on the address.
  • Missing or wrong transaction-type flag.
  • A VAT breakdown off by a fils, so totals do not reconcile.
  • Item price extension or base quantity omitted on the line.

How MyInvoice fills and checks these

You send the data you already export — CSV, Excel, UBL, CII or EDIFACT — and request the PINT AE profile. MyInvoice maps it into an EN 16931-aligned UAE document, applies the 5% VAT categories, reconciles the breakdown with exact decimal arithmetic, and validates against XSD and the PINT AE rules before you get it back — so the mandatory-field gaps surface here, not at your ASP.

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"
Generate a UAE invoice in your browser

Always confirm the exact mandatory-field list against the current PINT AE specification and Federal Tax Authority guidance — the rulebook is still maturing.

Read the API docs