What changes on invoices with e-invoicing, field by field

The mandatory fields document lists 41 fields for a tax invoice. Commercial invoices, used where a tax invoice is not required, have their own list of roughly fifty. Many of these are things you already show: invoice number, date, seller and buyer names, TRNs, line amounts and VAT.

What changes is precision. A buyer name typed four different ways across your customer list was harmless on a PDF. In a structured field it can trigger a rejection or a mismatch.

Both seller and buyer now need an electronic address and an electronic identifier, which tell the network where to deliver the invoice. The mandatory fields document gives a fixed scheme value of 0235 for the seller's electronic identifier for UAE businesses.

Your provider will explain how to obtain and record these. The practical point is that every business customer record needs one more set of details than it does today.

Several fields take codes rather than free text. The invoice type is a code. Currency is a currency code. Each line has a tax category code and a rate. Each quantity has a unit of measure code: a box, a kilogram, an hour.

Example: an Abu Dhabi cleaning company invoices '3 visits deep clean' today. Under e-invoicing, that line needs a quantity of 3, a unit of measure code, a VAT category code for standard rate and a 5% rate. Its service list needs a one-off clean-up so every service has a unit and a category.

• Invoice type code
• Invoice currency code
• Tax category code and rate on each line
• Unit of measure code on each line
• Seller and buyer electronic address and identifier

Businesses invoicing in USD or EUR already have to show VAT in AED on tax invoices. The mandatory fields list includes AED line amounts and VAT in AED, so the exchange rate you apply needs to be consistent and traceable to your accounting records.

A Dubai freight forwarder invoicing a client USD 12,000 at an exchange rate of 3.6725 shows AED 44,070 and VAT of AED 2,203.50 where VAT applies. The same rate should flow into the ledger.

The commercial invoice field list allows a seller tax identification number as a fallback where the seller has no TRN. That reflects the scope of Ministerial Decision No. 243 of 2025, which applies to persons conducting business, not only VAT registrants. A non-registered business supplying other businesses should not assume e-invoicing passes it by.

Before you talk to providers, pull last quarter's invoices and check them against the field list. Take twenty invoices at random and ask, for each one: is the buyer's legal name exactly as on its licence, is the TRN present and correct, does each line have a quantity and a unit, is the VAT category right for the item?

In most SMEs this exercise turns up the same three problems: customer names that are trading names, services billed as a single lump with no quantity, and zero-rated export lines coded as standard. Each is a master data fix, not an invoicing fix.

HelloBooks already stores most of what the fields need: customer legal names, TRNs and addresses, line quantities, VAT treatment per line, currency and exchange rates with AED equivalents. The AI agent drafts invoices from those records and can list products without a unit or VAT category, or customers without a TRN.

It does not generate or transmit the e-invoice itself; your accredited provider does that. If you need extra fields such as buyer electronic identifiers stored on customer records, or a custom invoice layout while you transition, ask the team at /book-a-demo.