UAE eInvoicing data checklist: what your records must hold before go-live
The PINT AE data checklist for UAE eInvoicing: what your business, customer, item and tax records must hold, the eight transaction scenarios, and how to prepare Zoho Books before go-live.
Most eInvoicing projects in the UAE start with the wrong question: what will our invoice look like? Under the new system, the invoice you see is only the output. What gets validated, exchanged and reported is the structured data behind it, and that data comes from records most businesses have not reviewed in years.
The Ministry of Finance publishes exactly what that data must contain. Its list of mandatory fields runs to 51 fields for an electronic tax invoice, and your Accredited Service Provider validates every invoice before it goes anywhere. This article is the practical version of that list: what each group of fields means for your records, where UAE businesses get caught out, and what to fix first.
If you need the background first, including who is in scope, the deadlines and the role of Accredited Service Providers, start with our guide to UAE eInvoicing requirements.
Every invoice becomes structured data
A traditional invoice is designed for a person to read. An eInvoice is structured data designed for systems to exchange, validate and process, in the PINT AE format, the UAE implementation of the Peppol international invoice specification.
That changes what your accounting system has to hold. It is no longer enough for the right details to appear somewhere on a PDF. Your business, your customers, your items, your tax treatment and each transaction all need to exist as separate, correctly filled fields.
It also applies more widely than many businesses assume. The Ministry's eInvoicing Guidelines state that eInvoicing is mandatory for any person conducting business in the UAE regardless of their VAT registration status, unless specifically excluded. Invoices for exempt or out-of-scope supplies, and invoices from businesses that are not registered for VAT, become electronic Commercial Invoices, with their own list of mandatory fields.
1. Your business details
Beyond your name and address, the seller section of every eInvoice carries:
- Electronic address
- Electronic identifier
- Legal registration identifier, and its type
- Tax identifier
- Tax scheme
- Address line, city, country subdivision and country code
The first two are where the UAE model becomes specific. Your electronic address is your Tax Identification Number (TIN), which is the first 10 digits of your TRN. Your electronic identifier is a fixed value, 0235, for every business registered in the UAE. Together they form the endpoint your ASP registers for you on the network. A business in scope that is not required to register for any tax must register with the FTA to obtain a TIN.
Two more details are worth checking now:
- Tax groups. If you are part of a tax group, your TIN comes from your own TRN, not from the tax group representative's.
- Legal registration type. The legal registration identifier must be declared as one of four types: TL (commercial or trade licence), EID (Emirates ID), PAS (passport) or CD (Cabinet Decision).
The point is that your business identity has to be held as structured data, not just printed in the invoice header.
2. Your customer data
This is where most businesses have the most work to do. For each customer, the eInvoice needs:
- Electronic address and electronic identifier
- Tax identifier, which is their TRN where they are registered
- Tax scheme
- Address line, city, country subdivision and country code
So a customer record that holds "ABC Trading LLC" and an email address is not enough. It has to contain what the network needs to identify the customer and route the invoice to them.
Three situations need particular care:
- Customers not yet on eInvoicing. Until a buyer has implemented eInvoicing and has a participant identifier, the Guidelines require you to include the predefined endpoint
0235:9900000098on the eInvoice, and to issue a regular tax invoice, for example a PDF, as well. - Customers outside the UAE. For exports where the buyer has no Peppol ID, the predefined endpoint is
0235:9900000099. - Customers in a tax group. Their TIN comes from their own TRN, not the group representative's. If the TRN in your records belongs to the group, the address you derive from it will be wrong.
The cleanup is unglamorous and specific. Every UAE customer should carry a 15-digit TRN that belongs to that entity and matches their tax registration certificate. Remove duplicates, fix legal names that differ from the trade licence, and complete the city and emirate fields. A wrong TRN is no longer a typo on a PDF. It is a wrong delivery address.
3. Your item master
Every invoice line carries its own structured data:
- Item name and description
- Quantity and unit of measure code
- Item net price, item gross price and price base quantity
- Tax category code and tax rate
- Line net amount, plus the VAT line amount and the line amount in AED
The unit of measure travels as a code rather than free text, so units typed freely into item records ("Pcs", "pcs", "Nos") will need mapping. Gross and net price are separate fields: the gross price is before any item discount, the net price after it.
Ask four questions of your item master:
- Is every item classified correctly?
- Is its VAT treatment correct?
- Is the unit of measure consistent?
- Are duplicate or outdated items still being used?
The tax category is where this stops being a tidiness exercise and becomes a compliance one. The Guidelines define six categories: standard rate, exempt, outside the scope of VAT, reverse charge, zero rated and margin scheme. Domestic reverse charge, which covers goods such as electronic devices, precious metals and stones, and metal scrap traded between registrants, has its own rule: the eInvoice carries no VAT, states why the reverse charge applies, and references the type of goods.
4. Your tax breakdown and totals
The eInvoice also carries a structured tax summary and the document totals:
| Tax breakdown | Document totals |
|---|---|
| Taxable amount per tax category | Sum of invoice line net amounts |
| Tax amount per tax category | Total amount without tax |
| Tax category code | Total tax amount |
| Tax category rate | Total amount with tax |
| Amount due for payment |
Your system is therefore not simply calculating a VAT amount. It has to produce data in which the lines, the tax treatment and the totals tie together, category by category, in a form that passes validation. If you invoice in USD or EUR, remember that the VAT on each line is also required in AED.
5. It is not only master data: the eight scenarios
Some transactions carry extra requirements. Every eInvoice includes an invoice transaction type code, a string of eight flags, each set to 1 or 0, that declares whether the invoice involves any of these scenarios:
| Scenario | What changes |
|---|---|
| Free zone | Where the customer is a free zone entity, the beneficiary, meaning whoever ultimately uses or owns what is supplied, is recorded alongside the customer |
| Deemed supply | The buyer electronic address is always 0235:9900000097 |
| Margin scheme | The VAT amount is shown as 0 |
| Summary invoice | A negative total must be issued as an electronic credit note |
| Continuous supply | Retention calculations go on a separate commercial document, not on the eInvoice |
| Disclosed agent billing | The supplier stays responsible even when the agent issues the invoice |
| E-commerce supply | The supplier stays responsible even when the platform issues the invoice |
| Exports | A buyer without a Peppol ID gets the endpoint 0235:9900000099 |
More than one scenario can apply to a single invoice, and the requirements of each then apply together.
So the question is not "is my invoice template ready?" It is "have we identified every type of transaction our business actually performs?" A trading company that bills free zone customers, holds retention on contracts and sells online already has three scenarios to configure before its first invoice validates.
Where Zoho Books fits
None of this should be typed by hand on every invoice. In a properly configured accounting system it lives in the records each invoice draws from:
- Organisation setup: your business and tax details, held once.
- Customer master: identification, tax and electronic details for each customer.
- Item master: item, unit, pricing and tax information.
- Transactions: each invoice inherits all of the above.
Zoho Books supports UAE eInvoicing in the PINT AE format, and Zoho is on the Ministry of Finance's list of accredited service providers. According to Zoho's eInvoicing help, the organisation side is set up under Settings, E-Invoicing (in Taxes & Compliance): registered business name, TIN, TRN, organisation address and the FTA-registered email you use for EmaraTax. Each invoice then shows its eInvoicing status, Yet To Be Pushed, Pushed or Failed, with any validation errors on the transaction itself.
That last detail is the operational reality. Someone has to own the Failed invoices. Configure the masters correctly once and that list stays short, which is why our Zoho Books implementation work for eInvoicing starts with the data audit, not the settings screen.
Prepare the data before the invoice
Do not wait for the first eInvoice to find out what is missing. In order:
- Clean your masters. Customers first, then items.
- Review your tax configuration. Tax categories, reverse charge, zero rated and exempt supplies.
- Identify your transaction scenarios. Which of the eight apply to your business.
- Configure your accounting system. Organisation, customer and item records, once.
- Test before you go live. With your ASP, on real transactions.
The Ministry's own readiness checklist, Appendix 2 of the Guidelines, runs to 17 questions, from choosing an ASP to agreeing how errors will be resolved. Two of them are about data: identifying the data points an eInvoice requires, and changing your systems so they can produce them. In our experience, those two take longer than the other fifteen combined.
eInvoicing is not just a new way to send an invoice. It is a new way of structuring invoice data.
If you want to know how far your records are from ready, book a free eInvoicing readiness review with our team. We will go through your customer master, item master and tax configuration with you and show you exactly what needs fixing.
Official sources
- UAE Electronic Invoice Mandatory Fields, V1.0, Ministry of Finance (23 February 2026)
- UAE Electronic Invoicing Guidelines, V1.1, Ministry of Finance (1 June 2026)
- Ministry of Finance, eInvoicing portal
- Accredited Service Providers, the official MoF list
- Zoho Books, eInvoicing help for the UAE (Zoho)
Related services