Under UAE e-invoicing, an invoice is only valid if it carries the right data in the right fields, and the Ministry of Finance has now published exactly which fields those are. This is the concrete detail behind the reform: not a vague call to modernise, but a specific list of mandatory data elements every electronic invoice must contain. Knowing them, and making sure your systems hold the data behind them, is the heart of being ready. Here is what the mandatory fields specification requires.
A defined set of fields, not a layout
The Ministry of Finance reference on mandatory fields, to be read with the e-invoicing guidelines and Ministerial Decisions No. 243 and 244 of 2025 and the PINT-AE technical specification, lists the exact data elements an electronic invoice must carry. Where a paper invoice is a layout you design, an electronic invoice is a structured set of named fields. The specification sets out mandatory fields for an electronic tax invoice and a larger set for a full commercial electronic invoice in XML.
| Field group | What it holds |
|---|---|
| Invoice details | Number, date, type and transaction codes, currency, payment due date, specification identifier |
| Seller details | Name, electronic address and identifier, legal registration and tax identifiers, address |
| Buyer details | Name, electronic address, registration and tax identifiers, address |
| Totals and tax | Document totals and the tax breakdown |
| Line items | The individual lines of the invoice |
The TIN and the electronic identifier
Two identifiers sit at the centre. Each participant is identified by a Tax Identification Number, the first ten digits of a Corporate Tax registration number. And UAE businesses carry a fixed seller electronic identifier value, 0235, with the electronic address and identifier together forming the business end point registered by an accredited service provider. These are not fields a business invents; they are assigned and registered, and they have to be correct for an invoice to route and be accepted.
An electronic invoice is a set of named data fields, not a page you design. Every mandatory field has to be present and correct, because the system checks them, and a missing or wrong field can stop the invoice.
The data has to exist before the invoice can
The practical consequence is that an invoice can only carry correct fields if the data already lives in your systems. The buyer's tax identifiers and electronic address have to be in your customer records, the tax codes and totals have to reconcile from your pricing, and your own identifiers have to be registered. This is why readiness is largely a data exercise: the fields are only as complete as the master records that feed them, and gaps in those records become rejected invoices.
Number of fields, and why it matters
The specification is precise about how many fields apply, with a defined set for a tax invoice and a larger set for a full commercial invoice. The exact count is less important than the principle: this is a checklist your systems must satisfy in full, not a rough target. Validation happens automatically at exchange, so a field a person would have overlooked can cause an electronic invoice to fail.
What to do about it
Map the mandatory fields against what your systems actually hold, and close the gaps before your phase begins. Make sure customer records carry the right tax identifiers and electronic addresses, that your products and tax codes are clean, and that your own TIN and electronic identifier are registered through an accredited service provider. Treat the mandatory fields list as a data checklist for your master records, because when the data behind the invoice is complete, the electronic invoice largely takes care of itself.
This article is general information and is not technical advice. The mandatory fields are set by the Ministry of Finance and read with Ministerial Decisions No. 243 and 244 of 2025 and the PINT-AE specification, which continue to develop. We would be glad to help you map your data to the standard.