PINT AE Mandatory Fields and Validation Rules
Last updated:
A UAE electronic tax invoice has 51 mandatory fields in six groups, and a commercial e-invoice has 49, according to the Ministry of Finance mandatory fields list (v1.1, 28 October 2026). The fields are defined in PINT AE, the UAE version of the Peppol invoice specification, and every e-invoice is checked against it before it reaches the buyer.
It applies from your go-live date: 1 January 2027 for businesses with revenue of AED 50 million or more, 1 July 2027 for businesses below that, and 1 October 2027 for government entities (Ministerial Decision No. 66 of 2026). Timeline and scope: UAE e-invoicing hub.
This is general guidance, not tax or technical advice. Confirm requirements with the UAE Ministry of Finance (MoF) and Federal Tax Authority (FTA).
Quick answers
- What is PINT AE?
- PINT AE is the UAE version of the Peppol International invoice specification, published by OpenPeppol (Billing v1.0.4 as of November 2026). It defines the structure of every UAE e-invoice, and invoices are validated against it before they reach the buyer.
- How many mandatory fields does a UAE e-invoice have?
- 51 for an electronic tax invoice, in six groups: invoice details (9), seller (11), buyer (9), document totals (5), tax breakdown (4) and invoice lines (13). A commercial e-invoice has 49. Source: Ministry of Finance mandatory fields list v1.1, 28 October 2026.
- What does conditional mean in PINT AE?
- A field that is optional in general but required in a specific case under the UAE validation rules. For example, a free zone supply needs the beneficiary ID, and a reverse-charge line needs the buyer's TRN.
- Why do UAE e-invoices fail validation?
- Mostly for data reasons: a conditional field left empty, a code that is not on the published list, line amounts that do not add up to the stated total, or a TRN in the wrong format (15 digits, starting with 1 and ending with 03).
- Do I need to implement PINT AE myself?
- Only if you are building your own integration. If you use invoicing software, your provider maps your data to the specification. What stays with you is capturing the underlying data, such as the buyer's TRN and emirate.
How many mandatory fields does a UAE e-invoice have?
51 for an electronic tax invoice, in the six groups below, and 49 for a commercial e-invoice (one that is not a tax invoice).
| Group | Mandatory fields | What it covers |
|---|---|---|
| Invoice details | 9 | Invoice number, date, type code, currency, transaction type code, payment due date, business process type, specification identifier, payment means code |
| Seller details | 11 | Name, electronic address (your TIN) and identifier (0235), legal registration identifier and its type, TRN and tax scheme, address line, city, emirate, country code |
| Buyer details | 9 | Name, electronic address and identifier, TRN and tax scheme, address line, city, emirate, country code |
| Document totals | 5 | Sum of line net amounts, total without tax, total tax, total with tax, amount due |
| Tax breakdown | 4 | Taxable amount, tax amount, category code and rate, per tax category |
| Invoice lines | 13 | Line ID, quantity, unit of measure, line net amount, net and gross price, price base quantity, tax category and rate, VAT and line amount in AED, item name and description |
A commercial e-invoice keeps the same groups but drops the two AED line amounts, and asks for the buyer's legal registration identifier and its type instead of the buyer's TRN and tax scheme. A seller without a TRN gives its TIN instead. For the invoice rules that sit behind these fields, see tax invoice vs simplified tax invoice.
What do mandatory, optional and conditional mean in PINT AE?
Every field in PINT AE has a cardinality: 1..1 means it must appear, 0..1 means it may, and the UAE validation rules then make many optional fields required in specific cases. Those “conditional” fields are where implementations usually go wrong, because a field you never fill in for ordinary sales becomes required for an unusual one. Examples from the PINT AE v1.0.4 rules:
- A free zone supply (transaction type flag 1XXXXXXX) needs the beneficiary ID (ibr-007-ae).
- A reverse-charge line needs the buyer's TRN and a code for the type of goods or services from the reverse-charge list (ibr-103-ae, ibr-166-ae).
- An e-commerce supply needs the delivery address line, city and emirate (ibr-142-ae).
- A summary invoice needs the invoicing period (ibr-138-ae).
- A disclosed agent billing invoice needs the principal's ID (ibr-137-ae).
The full invoice model defines about 200 business terms. The 51 on the Ministry's list are the ones every tax invoice needs.
What are business terms like ibt-001?
They are the identifiers PINT AE gives each field: ibt-001 is the invoice number, ibt-002 the issue date and ibt-003 the invoice type code, while UAE-only fields use btae codes, such as btae-02 for the transaction type code. The ibt codes come from the Peppol International (PINT) model that PINT AE is built on.
This matters when you map your own system: your ERP field is matched to a business term, not to a label. Two systems calling a field "invoice date" may be populating different business terms, and that discrepancy only surfaces at validation.
Which code lists does PINT AE use?
Currency codes follow ISO 4217 and units of measure follow UN/ECE Recommendation 20, while VAT categories, transaction types and exemption reasons come from UAE-specific lists in the PINT AE code lists. A value outside the list fails validation even when it looks right, such as a unit of measure typed as free text.
For a UAE business, the electronic identifier is the fixed value 0235 and the electronic address is your TIN: the first 10 digits of your 15-digit TRN. A TRN on the invoice must be 15 digits, starting with 1 and ending with 03 (ibr-132-ae).
The transaction type code is an eight-character string of 1s and 0s. Each position flags one feature, in this order: free trade zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent billing, supply through e-commerce, and exports. Nothing derives it for you: your system has to recognise the feature before it can set the flag, which means the classification logic sits upstream of invoice generation.
Why do UAE e-invoices fail validation?
Mostly for ordinary data reasons: a conditional field left empty, a code that is close but not on the list, a sum of line amounts that does not equal the stated total (ibr-co-10), or a TRN in the wrong format.
Validation happens twice. Your accredited service provider validates your invoice data and converts it to the UAE XML format before sending it. The buyer's provider validates it again on arrival; if that fails, it confirms the failure electronically to your provider and to the FTA (MoF Electronic Invoicing Guidelines v2.0).
None of these is difficult to fix. All of them are difficult to find after the fact, which is the argument for validating in a provider's test environment before go-live rather than discovering the pattern in production.
Which version of the specification is current?
As of 13 November 2026: PINT AE Billing v1.0.4 (Peppol PDK 1.4.4, released 29 July 2026) and the Ministry of Finance mandatory fields list v1.1 of 28 October 2026.
Both have been revised since first publication, and further revisions should be expected as the mandate progresses. Any field list published outside the Ministry and OpenPeppol, including a summary like this one, can fall behind. Before implementation work, take the current version from those two sources.
Do you need to implement PINT AE yourself?
No, unless you are building your own integration. If you use invoicing software rather than writing your own XML, your provider maps your data to the specification.
What remains yours is the data. A specification cannot invent a buyer TRN you never captured, or an emirate you never recorded, or a unit of measure your catalogue does not hold. The most common reason a business fails validation on day one is not a technical gap — it is that the fields were never collected in the first place. What to collect from each customer: customer details an e-invoice needs.
How Fatura Go helps with PINT AE mandatory fields
1. Keep the records
UAE VAT law requires invoices and VAT records to be kept for at least five years. Fatura Go keeps issued invoices, credit notes, expenses and bills in one place, with each receipt attached to its expense.
2. Prepare for e-invoicing
Invoices keep supplier and buyer TRNs, addresses, emirate, line-level VAT with the rate category on each line, and totals that reconcile. The e-invoicing checklist shows which business and client details are still missing.
3. Get help
Need an accountant to check your records before e-invoicing starts? Leave a request with Fatura Go support and say what you need. If you already work with an accountant, invite them to your account with their own login.
Generating PINT AE XML and transmitting invoices is done through an accredited service provider. Fatura Go is preparing for the UAE 2027 e-invoicing rollout, integrating with accredited providers.
Frequently asked questions
How many mandatory fields does a UAE e-invoice have?
51 for an electronic tax invoice, in six groups: invoice details (9), seller (11), buyer (9), document totals (5), tax breakdown (4) and invoice lines (13). A commercial e-invoice has 49. Source: Ministry of Finance mandatory fields list v1.1, 28 October 2026.
What is the PINT AE data dictionary?
The PINT AE semantic model: every data element a UAE e-invoice can carry, with its business term code (such as ibt-001 for the invoice number), definition and cardinality. It is published by OpenPeppol at docs.peppol.eu; the Ministry of Finance publishes the list of fields that are mandatory.
What does conditional mean in PINT AE?
A field that is optional in general but required in a specific case under the UAE validation rules. For example, a free zone supply needs the beneficiary ID, and a reverse-charge line needs the buyer's TRN.
What format is a UAE e-invoice?
Structured XML in the UBL syntax, conforming to the PINT AE specification. A PDF is not an e-invoice under the mandate.
What happens if a mandatory field is missing?
The invoice fails validation. Your accredited service provider validates the data before sending, and the buyer's provider validates it again on arrival; if that fails, it confirms the failure electronically to your provider and to the FTA (MoF Electronic Invoicing Guidelines v2.0).
Where do I get the field list?
From the Ministry of Finance (UAE Electronic Invoice Mandatory Fields, v1.1 of 28 October 2026) and the PINT AE specification on docs.peppol.eu. Both are revised periodically, so a list copied from a secondary source can be out of date.
Do I need to implement PINT AE myself?
Only if you are building your own integration. If you use invoicing software, your provider maps your data to the specification. What stays with you is capturing the underlying data, such as the buyer's TRN and emirate.