Fifty-one fields. Your ERP
probably holds about forty.
The UAE has published exactly what an electronic invoice must contain. It is not a long list by mandate standards — and it is not the length that causes trouble. It is four specific fields most ERP estates have never held, and an identifier almost everyone gets wrong on the first attempt.
It is 51 fields. The count is the easy part.
The Ministry of Finance publishes the definitive list — UAE Electronic Invoice Mandatory Fields, version 1.0, dated 23 February 2026 — to be read alongside the Electronic Invoicing Guidelines, Ministerial Decision No. 243 of 2025, Ministerial Decision No. 244 of 2025 and the PINT-AE specification.
For an electronic Tax Invoice the 51 mandatory fields fall into six groups: Invoice Details (9), Seller Details (11), Buyer Details (9), Document Totals (5), Tax Breakdown (4) and Invoice Line (13). For a commercial Electronic Invoice — the Ministry's term for an invoice that is not a Tax Invoice — the list runs to 49.
The two fields that exist only on the Tax Invoice are the ones worth knowing about before you scope anything: VAT line amount in AED and invoice line amount in AED. Both are line-level. We come back to those below, because they are where an otherwise clean integration turns into a piece of engineering.
Nothing on this list is unreasonable. Most of it — invoice number, date, currency, party names, addresses, totals, tax breakdown, line quantities and prices — already exists in any functioning ERP. Which is precisely why field coverage is the wrong thing to worry about in aggregate and the right thing to worry about specifically.
- Invoice Details — 9 fields, including the transaction type flags, business process type and specification identifier
- Seller Details — 11 fields, including electronic address, electronic identifier, legal registration identifier and its type
- Buyer Details — 9 fields, including buyer electronic address and tax identifier
- Document Totals — 5 fields
- Tax Breakdown — 4 fields per tax category
- Invoice Line — 13 fields, including both AED line amounts
Counted from the Ministry of Finance field list, version 1.0 (23 February 2026). Last verified 29 July 2026. Specifications are revised; check the primary document before relying on a count.
Your participant identifier is not your VAT number.
This single point causes more rework than the other fifty fields combined, because it is wrong at the level of master data rather than at the level of mapping — and because a plausible wrong answer is available.
0235 — for businesses registered in the UAE. Together with the
electronic address it forms the endpoint your accredited service provider registers on the
network. Two fields, one registration, and it has to match what the FTA holds.
Why this is a master-data problem, not an integration one
An identifier error does not fail loudly at mapping time. It produces a well-formed document addressed to the wrong endpoint, or a registration that collides with a sibling entity's. That is the failure shape we describe in the identity essay: a registered identifier is binary and external, so it either resolves or it does not — there is no confidence score to tune and no partial credit for nearly right.
Four fields your ERP has never held.
Out of 51, these are the ones that turn a configuration exercise into a build. If your plan does not name them, it has not been scoped.
1. Invoice transaction type code — eight flags in one string
A single mandatory field carrying an eight-character string, each position independently 1 or 0:
- Free trade zone
- Deemed supply
- Margin scheme
- Summary invoice
- Continuous supply
- Disclosed agent billing
- Supply through e-commerce
- Exports
Read that list as a set of questions about every invoice you issue, because that is what it is. Very few ERP estates hold these as structured, per-invoice, reportable attributes. Free zone status might live in a company code, margin scheme in a tax code, e-commerce in a sales channel, exports inferred from a ship-to country. Producing a correct eight-flag string means deriving it from evidence scattered across the estate, and then defending that derivation when an auditor asks why position four was zero.
This is the field we would look at first on any UAE scoping call. It is also the one most
likely to be quietly hard-coded to 00000000 by an integrator under deadline
pressure, which is a compliance exposure dressed as a delivery win.
2 and 3. AED amounts, per line, whatever you invoiced in
Two of the 51 are VAT line amount in AED and invoice line amount in AED. Note the level: per line, not per document. If you invoice in USD, EUR or SAR, every line of the outbound Tax Invoice must also carry its AED equivalent.
That is not a mapping. It requires a rate, a rate source, a rate date convention, rounding rules that reconcile line-level AED sums against document totals, and a decision about what happens when your ERP's exchange-rate table disagrees with the rate you are obliged to use. Rounding is where this bites: independent per-line conversion routinely produces a sum that does not match a converted document total, and validation does not care which of the two you think is right.
Worth noting that these two fields are exactly the difference between the 51-field Tax Invoice list and the 49-field commercial list. If someone has told you the requirement is 49 fields, they have scoped you as issuing commercial invoices only.
4. Seller legal registration identifier type
Mandatory, and it must be one of four coded values: TL for a commercial or
trade licence, EID for an Emirates ID, PAS for a passport, or
CD for a Cabinet Decision. Straightforward for a single trade-licensed company.
Less so across a group holding a mixture — a free-zone entity, a mainland LLC, an
establishment registered against an individual — where the correct code differs per
entity and nobody has ever recorded which is which, because until now nothing asked.
"We are not VAT registered" is not an exemption.
The Ministry's own highlights are unambiguous: electronic invoicing is mandatory for any Person conducting business in the UAE, regardless of VAT registration status, unless specifically excluded under Article 4 of Ministerial Decision No. 243 of 2025.
Scoping the programme by VAT registration is one of the more common and more expensive misreadings of this mandate. It produces a project that covers part of the group, misses entities that turn out to be in scope, and discovers the gap after the appointment deadline has passed rather than before.
The correct first step is therefore not technical. It is an entity-by-entity scope determination against Article 4, producing a list of which legal entities are in scope, which are excluded and on what basis, and which need to register with the FTA to obtain a TIN they do not yet have. Everything else waits on that list.
For the phased timeline itself — who has to be live when, and the accredited-service-provider appointment deadline — see the UAE mandate briefing, which we keep date-stamped rather than restating dates here where they would go stale in two places at once.
The cost of appointing late
Worth holding next to the scoping work: failure to implement the Electronic Invoicing System, including failure to appoint an accredited service provider within the prescribed timeline, is the first listed violation in Cabinet Decision No. 106 of 2025, at AED 5,000 for each month of delay — accruing whether or not you have issued a single invoice. A scope determination that takes three months is not free if it delays the appointment. The full penalty schedule →
- Own Corporate Tax TRN, and therefore own TIN
- Correct legal registration identifier and its type code
- Own address block, down to country subdivision
- Whether Article 4 excludes it, and the basis recorded
A field-coverage audit you can run yourself.
This is deliberately not a product pitch. You can do most of it with a data extract and a spreadsheet, and you will learn more from it than from any vendor demo.
- 1. Scope by entity, against Article 4. List every legal entity that invoices. Record in-scope or excluded, and the basis. Note which have a Corporate Tax TRN and which need to register for a TIN.
- 2. Map the 51 to your ERP, field by field. For each, record whether the value exists, is derivable, or is absent. Do not aggregate to a percentage — a 94% coverage figure with the transaction type flags in the missing 6% is worse than useless.
- 3. Test the four hard fields explicitly. Can you produce the eight-flag string for last month's invoices? Can you produce per-line AED for a foreign-currency invoice, and does the sum tie to the document total? Do you hold the right registration identifier type per entity?
- 4. Validate the identifiers you already hold. Every seller TIN against the FTA record, every buyer tax identifier you will be asked to carry. This is the step most often skipped and most often the cause of rejections.
- 5. Sample rather than theorise. Take a hundred real invoices spanning your awkward cases — free zone, export, credit note, foreign currency, intercompany — and check those against the list. Edge cases are where the fields are missing, which is exactly why a clean-case demo proves nothing.
If you would rather start with a scored view of where you stand, the E-Invoicing Readiness Assessment covers mandate coverage, data custody and master-data readiness in about five minutes, and the Data Maturity Assessment goes deeper on the governance side.
Asked on most UAE data calls.
How many mandatory fields does a UAE electronic invoice have?
51 on an electronic Tax Invoice, 49 on a commercial Electronic Invoice, per the Ministry of Finance field list version 1.0 dated 23 February 2026. The two extra are the AED line-level amounts.
Is my participant identifier my VAT TRN?
No. It is your TIN — the first 10 digits of your 15-digit Corporate Tax TRN. And if you sit inside a Tax Group it is still your own, not the group representative's. The Ministry spells this out explicitly, which is usually a sign that people were getting it wrong.
We are not VAT registered. Are we out of scope?
Almost certainly not. The requirement applies to any Person conducting business in the UAE regardless of VAT registration status, unless excluded under Article 4 of MD 243 of 2025. Check Article 4 entity by entity rather than assuming.
We invoice in USD. Do we really need AED per line?
On a Tax Invoice, yes — both the VAT line amount and the invoice line amount in AED, at line level. Budget for the rate source, the rate-date convention and the rounding reconciliation, not just the conversion.
Can our ASP fix our master data for us?
No, and be wary of one that says otherwise. A provider can validate, reject and report; it cannot know that an entity's registration identifier type is EID rather than TL, or which supply-type flags apply to a given transaction. Content is yours. A good provider tells you that early — it is one of the things we score in the ASP scorecard.
How long does the data work take?
Honestly: it depends almost entirely on how many entities you have and how consistent their master data is, and we would be guessing before seeing an extract. The useful shape is that identifier and scope work is measured in weeks and has a hard external dependency (FTA registration), while field derivation is measured in weeks of engineering. Neither compresses well, which is the argument for starting the audit before the platform decision rather than after.
Sources.
Everything on this page is taken from UAE primary material. Last verified 29 July 2026.
- UAE Electronic Invoice Mandatory Fields, version 1.0, 23 February 2026 — the field lists, group structure, TIN rule, transaction type flags and registration identifier types. Published by the Ministry of Finance — mof.gov.ae
- UAE Electronic Invoicing Guidelines, version 1.1, 1 June 2026 — Ministry of Finance eInvoicing
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System — scope, and the Article 4 exclusions
- Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System — the phased plan
- Cabinet Decision No. 106 of 2025 — violations and administrative penalties, including the ASP appointment failure
- PINT-AE — the Peppol UAE electronic document specification and its Data Dictionary
If you hold a later version of the field list than 1.0, or believe a count here is wrong, tell us — we would rather correct the page than defend it.
The rest of the UAE picture.
UAE mandate briefing GCC penalties ASP scorecard Data Practice Readiness assessment
Deadlines move. We will tell you when.
Short, source-checked notes when a GCC mandate actually changes — a wave announced, a specification revised, a date moved. Written by the people doing the implementations. No sequence, and you can leave in one click.
We use it to send mandate updates and nothing else. See our privacy policy.
Start with thirty minutes.
Tell us how many UAE entities you invoice from, which currencies, and whether any sit in a free zone or a Tax Group. We will tell you which of the 51 fields you are likely to be missing and what the remediation looks like — with a written fixed-fee quote within 24 hours.