E-invoice mandatory fields UAE: what each invoice must carry

Section 4.1 of the Ministry document lists 41 fields for an electronic tax invoice:

• Invoice details (fields 1 to 9): number, date, type code, currency, transaction type flags, payment due date, business process, specification identifier and payment means.
• Seller (10 to 20): name, electronic address and identifier, legal registration, tax identifier, address, city, subdivision and country.
• Buyer (21 to 29): name, electronic address and identifier, tax identifier, address, city, subdivision and country.
• Document totals (30 to 34): net line total, totals with and without tax, tax total and amount due.
• Tax breakdown (35 to 38): taxable amount, tax amount, tax category code and rate.
• Lines (39 to 41): line identifier, quantity and unit of measure.

The seller tax identifier is your 15-digit TRN for VAT-registered sellers, and the buyer tax identifier is the customer's TRN where they are UAE-registered. The electronic address is built from the TIN with the fixed scheme 0235. Field 5 carries eight yes-or-no flags: free trade zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent billing, e-commerce supply and exports. Your system needs to know which of those apply to each sale.

A commercial electronic invoice has its own table of about 49 fields, adding item names, prices and line-level AED amounts. The Ministry's numbering in that section is not fully consistent, so read it with the PINT AE data dictionary.

Take a sample of 50 recent invoices and check each field group. Most gaps cluster in buyer details and in the transaction flags, because paper invoices never needed them. A Ras Al Khaimah building supplier, for example, may find that half its customers have no emirate stored and that margin-scheme or export sales are not marked.

HelloBooks keeps TRNs, customer addresses, currencies and line-level VAT categories on every invoice, which covers much of the list. The AI agent flags invoices missing a buyer TRN or with a VAT category that conflicts with the customer type. Generating and transmitting the XML is your ASP's job, not HelloBooks'. If you need extra fields such as a transaction flag stored on invoices, request it through hello@hellobooks.ai.