PINT AE Fields Mapped to ERPNext: The UAE e-Invoice Guide

PINT AE is a rulebook, not software. It is the UAE profile of the Peppol PINT invoice standard, and the Ministry of Finance Data Dictionary is its official reference¹. Every e-invoice you send after your go-live date must be a structured XML file that follows it. OpenPeppol released PINT AE version 1.0.1 in July 2025, and the Ministry published its formal mandatory fields specification in February 2026².

If you run ERPNext, the question is not "what is PINT AE". The question is: which field in my system supplies each mandatory element, and which of those fields is currently empty or wrong. That mapping is this post.

What the classifications mean

The dictionary defines more than 135 data elements, each classified one of three ways¹:

Mandatory. Must be present and valid for that invoice scenario. A missing or malformed mandatory field is rejected by your Accredited Service Provider automatically. There is no manual override, and the invoice never reaches your customer or the FTA².

Conditional. Required only when a condition applies. Ship a zero-rated export and the export-related fields switch from optional to required. Conditional fields are where invoices die, because the team tested the standard case and never tested the edge cases.

Optional. Allowed, not required. Purchase order references, delivery details, notes.

For a standard tax invoice, roughly 51 mandatory fields must be present across six groups: invoice details (9), seller (11), buyer (9), document totals (5), tax breakdown (4), and line items (13)².

Two of those line fields exist only in the UAE profile: the VAT line amount in AED and the invoice line amount in AED, mandatory on every line. They do not appear in the European or Asia-Pacific Peppol specifications². If you invoice in USD, your system must convert and carry both AED values per line, automatically.

The mapping table

This is the asset. Six groups, the ERPNext source for each, the common gap, and the fix. Field references use the dictionary's business term codes where useful; the Invoice Type Code is BT-3 and the Tax Category Code is BT-151³.

The pattern in that table is worth stating plainly. Almost nothing on it is invoice-time data. It is master data: Company, Customer, Item, Address. Which means almost every validation failure is fixable weeks before go-live, at zero cost, by cleaning records.

The 16 use cases, and the five you actually hit

The dictionary defines 16 invoice scenarios, from the standard tax invoice through summary invoices, margin scheme, disclosed agent, self-billing, and exports³. The Invoice Type Code (BT-3) declares which scenario an invoice belongs to, and that code drives which conditional fields become required and which validation rules fire³.

A typical UAE SME touches five³:

1. Standard tax invoice. Routine 5% B2B sales. Your volume case.
2. Standard credit note. Returns and corrections. Must reference the original invoice, which is exactly how ERPNext return invoices behave when your team uses them properly.
3. Zero-rated invoice. Exports and other zero-rated supplies. Tax category Z, with the zero-rating reason required.
4. Reverse charge invoice. Imported services. Tax category AE.
5. Free zone invoice. If you sit in or supply designated zones.

Walk your last quarter of invoicing and count which scenarios appear. Most trading companies find four. Then test all four, not just the first.

Where ERPNext data usually fails validation

From implementation work on UAE systems, the failures cluster in the same places every time.

The recurring five: customer records with missing or malformed TRNs, free-text invoice lines with no item reference, items with no tax template so no category code can be derived, company addresses without an emirate, and credit notes issued standalone with no link to the original invoice.

None of these is an XML problem. All of them are data discipline problems that surface as XML problems.

How to test before your ASP rejects you

Do not let your first validation happen on a live invoice.

First, export your masters and audit them: TRN format on every active customer and supplier, tax template on every active item, complete addresses with emirate on every party you invoice.

Second, generate test invoices covering every scenario you identified, including a credit note and your ugliest real case, the multi-currency invoice with a discount and a zero-rated line.

Third, run them through validation in your ASP's sandbox before go-live. Our fta_compliance module runs field-completeness checks inside ERPNext before an invoice ever reaches the ASP, so rejections get caught where your team can fix them, on a draft.

FAQ

What is PINT AE in one sentence? The UAE profile of the Peppol PINT invoice standard: the data dictionary every UAE e-invoice must follow, published by the Ministry of Finance¹.

How many fields are mandatory? Around 51 for a standard tax invoice, across six groups. The full dictionary defines more than 135 elements, with conditional fields activating by scenario².

What happens if a mandatory field is missing? Your ASP rejects the invoice automatically. No manual override. It never reaches the buyer or the FTA².

Does ERPNext support PINT AE out of the box? ERPNext holds the data. The PINT AE XML generation and ASP transmission is integration work, which is what an implementation partner builds and maintains. The data quality underneath is yours either way.

Which fields are unique to the UAE? The VAT line amount in AED and invoice line amount in AED, required on every line even for foreign-currency invoices².

Do I need to handle all 16 use cases? No. Map which scenarios your business actually produces. Most SMEs hit four or five: standard, credit note, zero-rated, reverse charge, and sometimes free zone³.

Is JSON allowed instead of XML? The invoice moves as structured XML under the Peppol framework; some providers also reference JSON at the API layer¹. What is never valid is a PDF.

When did the specification become final? OpenPeppol released PINT AE v1.0.1 in July 2025; the Ministry published the mandatory-fields specification in February 2026. Check the MoF eInvoicing pages for the current version before you build².

Get ERPNext live fast, e-invoicing ready from day one

The Dxbitz Starter Package: AED 9,900, no per-user fees, free e-invoicing integration included. Priced in one call. WhatsApp us · See the Starter Package

References

1. Tax Star, "PINT AE Explained: UAE E-Invoicing Data Dictionary and Mandatory Fields," taxstar.app. (accessed July 2026) ↩ ↩² ↩³ ↩⁴

2. Asad Abbas & Co, "PINT-AE Format Explained: UAE E-Invoicing Data Standards and Mandatory Fields," asadabbastechnologies.com. (accessed July 2026) ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶ ↩⁷ ↩⁸

3. Orchida Tax, "The 16 Scenarios of UAE E-Invoicing | PINT AE Guide," orchidatax.com. (accessed July 2026) ↩ ↩² ↩³ ↩⁴ ↩⁵ ↩⁶