L
O
A
D
I
N
G
Zoho, Odoo, ERPNext, Dynamics 365 and custom ERP, delivered by one accountable team.
A practical walk-through of the Ministry of Finance mandatory field list for electronic tax invoices and commercial invoices, and how to map each field to master data in your ERP.
The Ministry of Finance mandatory fields document of 23 February 2026 lists 51 fields for a UAE electronic tax invoice and 49 for a commercial electronic invoice. Tax invoice fields fall into groups such as invoice details, seller details, buyer details, document totals and tax breakdown, plus an eight-flag transaction type code. Each field should come from ERP master data rather than manual entry.
The UAE e-invoicing invoice fields are the data elements that every structured electronic invoice must contain before an Accredited Service Provider (ASP) will pass it on to your buyer and report it to the Federal Tax Authority. On 23 February 2026 the Ministry of Finance published a document titled UAE Electronic Invoice Mandatory Fields (version 1.0). It lists 51 mandatory fields for an electronic tax invoice and 49 for a commercial electronic invoice, and it is meant to be read alongside Ministerial Decisions No. 243 and 244 of 2025 and the Peppol PINT AE specification.
For a finance team this is the most practical part of the mandate. Your PDF invoice today may already show a TRN, a VAT amount and a total, but a PINT AE invoice is read by software, not by a person. Each field has a defined meaning, a code list or a format, and a missing or wrongly coded value means the invoice fails validation at the ASP. That is why most of the work sits in your ERP's customer master, item master, tax codes and invoice numbering, not in the transmission itself.
This page goes field group by field group and shows where each value should come from in an ERP. It does not repeat the scope and deadline rules, which are covered on the UAE e-invoicing requirements page, or the project plan, which is on the e-invoicing implementation page. It describes how systems are configured to support the rules; it is not tax advice, so confirm your position with your tax advisor and check the latest Ministry of Finance and FTA guidance, because documents are versioned and updated.
Key points from the Ministry of Finance mandatory fields document and the decisions it refers to. Field names below follow that document; always check the current version before configuring.
The 51 tax invoice fields fall into invoice details (9), seller details (11), buyer details (9), document totals (5), tax breakdown (4) and invoice line (13). The line group includes two UAE-specific values: VAT line amount in AED and invoice line amount in AED, which matter whenever you invoice in USD, EUR or another currency.
Your participant identifier is based on your Tax Identification Number, the first 10 digits of your 15-digit TRN. If you are in a VAT tax group, the document notes that your TIN is the first 10 digits of your own Corporate Tax TRN, not the group representative's. A person in scope that is not required to register for Corporate Tax must register with the FTA to obtain a TIN.
Seller electronic address carries the TIN, and seller electronic identifier is a fixed value of 0235 for UAE businesses. Together they form the endpoint that your ASP registers for you, so the buyer's ASP can find you on the network.
The highlights state that e-invoicing applies to any person conducting business in the UAE regardless of VAT registration, unless excluded under Article 4 of Ministerial Decision No. 243 of 2025. Non-tax (commercial) invoices therefore have their own 49-field list, where buyer legal registration details replace the buyer tax identifier fields.
E-invoicing does not replace your tax record obligations. Keep the structured invoice, ASP responses and the ERP audit trail for at least 5 years (7 for real estate) under Cabinet Decision 74 of 2023, and confirm the retention approach with your tax advisor.
General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.
A mapping view of the electronic tax invoice field list. The right-hand column is where a well-configured ERP should hold the value, so it flows to the invoice without retyping.
| Field group | Mandatory fields (MoF list) | Source in your ERP | Common gap we see |
|---|---|---|---|
| Invoice details (9) | Invoice number, invoice date, invoice type code, invoice currency code, invoice transaction type code, payment due date, business process type, specification identifier, payment means type code | Invoice numbering series, document type, currency, payment terms, payment method; last three are fixed or mapped values | Payment due date blank on cash or 'on receipt' terms; payment method not captured as a code |
| Seller details (11) | Seller name, electronic address (TIN), electronic identifier (0235), legal registration identifier and type, tax identifier (TRN), tax scheme code (VAT), address line 1, city, country subdivision, country code (AE) | Company or legal entity settings, trade license record | Trade name used instead of the registered legal name; emirate stored as free text |
| Buyer details (9) | Buyer name, electronic address, electronic identifier, tax identifier (TRN), tax scheme code, address line 1, city, country subdivision, country code | Customer master: legal name, TRN, Peppol endpoint, billing address | Missing or unverified TRNs; one customer record used for several legal entities |
| Document totals (5) | Sum of line net amounts, total without tax, total tax amount, total with tax, amount due for payment | Calculated by the invoice engine | Rounding at header instead of line level; advances not reflected in amount due |
| Tax breakdown (4) | Tax category taxable amount, tax category tax amount, tax category code, tax category rate | VAT tax codes mapped to PINT AE tax categories | Zero-rated, exempt and out-of-scope sharing one tax code |
| Invoice line (13) | Line identifier, invoiced quantity, unit of measure code, line net amount, item net price, item gross price, item price base quantity, item tax category code, item tax rate, VAT line amount in AED, line amount in AED, item name, item description | Item master, units of measure, price lists, discounts, exchange rates | Units like 'pcs' or 'box' not mapped to standard codes; line descriptions empty for services |
Field names follow the Ministry of Finance document UAE Electronic Invoice Mandatory Fields v1.0 (23 February 2026). The full PINT AE data dictionary also has conditional and optional fields for specific scenarios. Check the latest version before configuring.
One field deserves its own section. The invoice transaction type code is a sequence of eight flags, each set to 1 (applicable) or 0 (not applicable). Your ERP needs a rule for each flag rather than a person choosing it at invoicing time.
| Flag | When it is likely to apply | How to drive it in the ERP |
|---|---|---|
| Free trade zone | Supplies involving a free zone, for example designated zone goods movements | Customer or delivery address flagged by zone; confirm treatment with your advisor |
| Deemed supply | Goods or services treated as supplied for VAT, such as certain business gifts or own use | A dedicated invoice type or tax code used only for deemed supplies |
| Margin scheme | Second-hand goods and similar sales where VAT applies to the margin | Item category or sales channel flag |
| Summary invoice | One invoice covering several supplies to the same buyer in a period | A consolidated billing run linked to the source deliveries |
| Continuous supply | Rentals, retainers, maintenance contracts and other periodic supplies | Subscription, contract or recurring invoice templates |
| Disclosed agent billing | Invoices raised by an agent in the name of a principal | Agent contract record on the customer or project |
| Supply through e-commerce | Sales made through an online channel | Sales channel field populated from the web store or marketplace integration |
| Exports | Goods or services supplied outside the UAE | Customer country and delivery terms, linked to the zero-rated export tax code |
Descriptions in the middle column are our plain-English examples, not legal definitions. Confirm which flags apply to your transactions with your tax advisor.
Work through these items before you connect to an ASP. They sit underneath the wider UAE e-invoicing checklist, which also covers ASP selection and governance.
The fields are filled in your ERP, converted to PINT AE XML, then validated and exchanged by ASPs. The message-level detail is on our e-invoicing API integration page.
One shared database: every step updates stock, finance and reports in real time.
We implement all four platforms below. This is a general view of where the data sits; e-invoicing features are changing quickly, so confirm current capability for your edition and region with the vendor.
| Zoho | Odoo | ERPNext | Dynamics 365 | |
|---|---|---|---|---|
| Seller identity (TIN, TRN, license) | Organization profile and tax settings in Zoho Books | Company record and fiscal localization | Company doctype; extra fields usually added via custom fields | Legal entity setup and tax registration numbers |
| Buyer TRN and endpoint | Customer contact tax fields; endpoint may need a custom field | Partner record (VAT and Peppol-related fields in recent versions) | Customer doctype with custom fields for endpoint | Customer account tax registration; endpoint per localization or extension |
| Tax category mapping | Tax rates and tax treatments | Taxes linked to fiscal positions | Item tax templates and sales taxes templates | Sales tax codes and item sales tax groups |
| Unit of measure codes | Item units, mapping to standard codes may be needed | UoM records, map to standard codes | UOM doctype, map to standard codes | Units with external code mapping |
| Transaction type flags | Typically custom fields or rules on invoice | Typically configuration or custom module | Custom fields and server scripts | Typically extension or ISV solution |
| XML generation and ASP connection | See Zoho UAE e-invoicing | See Odoo UAE e-invoicing | App, custom integration or ASP connector | Electronic reporting framework or ISV connector to an ASP |
No ERP is itself an ASP. The ERP produces the data; the ASP you appoint validates and exchanges it. Check the Ministry of Finance list of accredited providers.
The two lists are almost identical. The differences are in how the seller and buyer are identified.
| Area | Electronic tax invoice (51 fields) | Commercial electronic invoice (49 fields) |
|---|---|---|
| Seller tax identity | Seller tax identifier: the TRN for sellers registered for tax | Seller tax registration identifier: TIN if the seller has no TRN |
| Buyer identity | Buyer tax identifier (TRN) and buyer tax scheme code | Buyer legal registration identifier and its type (TL, EID, PAS or CD) |
| Line amounts in AED | VAT line amount in AED and invoice line amount in AED are mandatory | Not in the commercial list |
| Transaction type flags | Same eight flags | Same eight flags |
| Typical ERP impact | Driven by VAT setup and customer TRNs | Needs trade license or other ID captured for buyers |
Published dates from Ministerial Decision No. 244 of 2025. Dates have been amended before, so check the latest Ministry of Finance / FTA guidance.
Durations are typical ranges; your plan is agreed after discovery.
Compare your invoice templates and master data with the field list. Our readiness assessment covers this step.
Collect customer TRNs and license data, split tax codes, map units of measure.
Field mapping should be tested with the ASP well before go-live.
Use the voluntary period from 1 July 2026 to test real invoices.
Suppliers to government should check buyer endpoint details early.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertThe Ministry of Finance mandatory fields document (v1.0, 23 February 2026) lists 51 mandatory fields for an electronic tax invoice and 49 for a commercial electronic invoice. The full PINT AE data dictionary adds conditional fields for specific scenarios. Check the current version, as documents are updated.
Not quite. The TIN is a 10-digit identifier: the first 10 digits of your 15-digit TRN. It is used as your electronic address for e-invoicing, while the full TRN still appears as the seller tax identifier on tax invoices.
The invoice currency code will be USD, but the tax invoice list also requires the VAT line amount in AED and the invoice line amount in AED. Your ERP needs reliable exchange rates and line-level conversion so these values are produced automatically.
You need their correct legal name, TRN and endpoint, and for commercial invoices their legal registration identifier. Trading companies with large customer lists usually start this collection first; see e-invoicing for trading companies.
Usually yes, once you define rules. Exports can follow customer country and tax code, continuous supply can follow recurring invoice templates, and e-commerce can follow the sales channel. Avoid leaving flags to manual selection, because errors are hard to spot.
No. It explains how ERP systems are configured to produce the required data. Confirm how the rules apply to your transactions with your tax advisor and check the latest Ministry of Finance and FTA guidance.
Related ERP Platforms
Related Guides
We compare your current invoices and master data with the mandatory field list and give you a clear fix list before you connect to an ASP.
Dubai, United Arab Emirates
