Updated November 2026 · 5 min read
Most UAE finance teams already issue tax invoices, so the jump to e-invoicing can look like a format change. It is more than that. The PINT AE mandatory fields set out exactly which pieces of data every structured invoice must carry, and an invoice that misses one of them can be rejected before your customer ever sees it. This guide walks through the main field groups, where businesses usually fall short, and how to clean up your data before your go-live date. If you want hands-on help, our e-invoicing services in Dubai cover readiness reviews and data mapping.
What PINT AE Actually Is
PINT stands for Peppol International Invoice. It is a shared invoice model used across the Peppol network, and each country adds its own rules on top. PINT AE is the UAE version, published by the Ministry of Finance as the data specification for the national e-invoicing system.
The UAE uses a decentralised “5-corner” model. The supplier sends invoice data through its Accredited Service Provider (ASP), the ASP passes it to the buyer’s ASP, and tax data is reported to the Federal Tax Authority along the way. Every handover depends on the invoice speaking the same structured language, and that language is PINT AE.
The legal framework sits in Ministerial Decisions 243 and 244 of 2025. The detailed field list lives in the technical documentation, which the Ministry updates from time to time, so always work from the latest published version.
The Main Groups of PINT AE Mandatory Fields
It helps to think of the PINT AE mandatory fields in five groups rather than as one long list.
Invoice header
This covers the invoice number, issue date, invoice type (for example a tax invoice or a credit note), the invoice currency and transaction flags that describe the nature of the supply. A credit note must also reference the original invoice it corrects.
Seller and buyer details
Expect legal names, addresses, Tax Registration Numbers where the party is registered, and an electronic address that identifies each party on the network. The electronic address is new for most businesses, and it is the field most often left blank in early testing.
Line items
Each line needs a description, quantity, unit of measure, net price, line amount and a VAT category with its rate. Free-text units such as “pcs” or “box” need to map to the standard code lists.
Tax breakdown
VAT must be totalled by category, showing taxable amount and tax amount. Where an invoice is issued in a foreign currency, the VAT amount still needs to be stated in AED, which mirrors the existing VAT invoicing rules.
Document totals and payment terms
Totals before and after tax, any allowances or charges, the amount payable and the due date all need to reconcile exactly with the lines above them.
Where UAE Businesses Usually Fall Short
In practice, the gaps are rarely about missing software features. They come from data that was never captured in a structured way.
A Dubai trading company might store customer TRNs in a notes field, sometimes with spaces, sometimes without. A Sharjah contractor might invoice in “lots” or “jobs” with no standard unit behind them. A free zone service business might use one generic VAT code for everything because the old PDF invoice never forced a choice between standard rated, zero rated, exempt and out of scope.
None of these problems show up on a printed invoice. All of them can fail a PINT AE validation check. The fix is a master data review, not a new template.
How to Map Your Data to the Specification
Start by exporting a sample of real invoices from the last quarter, including credit notes, foreign currency invoices and anything unusual. Then compare each field in your system with the PINT AE list and mark it as present, present but in the wrong format, or missing.
Next, decide where each missing field will come from. Some will sit in the customer master, such as electronic addresses and TRNs. Others belong in the item master, such as units of measure and VAT categories. A few, like transaction flags, may need logic in your ERP or a rule set inside your ASP’s platform.
Finally, agree who owns each field. Sales usually owns customer data, procurement owns supplier data and finance owns tax codes. Without clear owners, the same errors come back a month after go-live. If the work touches wider process changes, a business consultant in Dubai can help you redesign the order-to-cash steps around the new data.
Testing Before the Deadline
The phased timeline gives you limited room. A pilot runs from 1 July 2026. Businesses with revenue of AED 50 million or more must appoint an ASP by 31 July 2026 and go live from 1 January 2027. Others appoint by 31 March 2027 and go live from 1 July 2027, and government entities follow from 1 October 2027.
Once you have an ASP, run your sample invoices through its validation tools and fix every rejection at the source. Do not patch errors manually inside the ASP portal. If a field fails once, it will fail on every invoice that draws from the same master record.
Keep a simple log of each error, its cause and the fix. That log becomes your training material and your evidence trail if the FTA ever asks how you prepared. Our e-invoicing services in Dubai include structured test cycles of this kind, run alongside your chosen provider.
For background on how the wider Peppol model handles invoice formats, the OpenPeppol website explains the network and its specifications.
Getting Your Data Ready
The PINT AE field list is long, but it is predictable. Most of the work is cleaning customer records, standardising units and getting VAT categories right, and all of that can start today. Live Auditors is not an ASP. We help businesses prepare their data and processes, and we work with the ASP you appoint so the connection goes smoothly. Find out more about our e-invoicing services in Dubai and how we structure a readiness review.
Contact us on +971 56 227 3735 or email info@liveauditing.com to book a field mapping review before your go-live date.
Frequently Asked Questions
1. What is PINT AE in UAE e-invoicing?
PINT AE is the UAE data specification for structured e-invoices, based on the Peppol International Invoice model. It defines the fields, formats and code lists every e-invoice must follow so that Accredited Service Providers can exchange invoices and report tax data to the Federal Tax Authority under the national e-invoicing system.
2. How many mandatory fields are in a UAE e-invoice?
The exact number depends on the invoice type and the version of the specification the Ministry of Finance has published. Businesses should work from the latest PINT AE documentation rather than a fixed count, because fields can be added or clarified as the national e-invoicing system moves through its rollout phases.
3. Do I need my customer’s TRN on an e-invoice?
Yes, where the customer is registered for VAT in the UAE, its Tax Registration Number should appear on the e-invoice. Storing TRNs in a clean, consistent format in your customer master is one of the most useful preparation steps, because badly formatted numbers are a common cause of validation failures.
4. What happens if an e-invoice is missing a mandatory field?
An e-invoice missing a mandatory field is likely to fail validation at your Accredited Service Provider and will not be delivered or reported correctly. You would then need to correct the data and reissue it. Repeated failures can delay payments and create compliance risk, so fixing master data early matters.
5. Can my existing invoice template meet PINT AE requirements?
A visual template alone cannot meet PINT AE requirements, because e-invoices are structured data files rather than PDFs. Your system must capture each required field in a structured way so it can be converted to the PINT AE format. Many ERPs can do this once master data and tax codes are properly set up.
