Mandatory e-Invoicing Fields in UAE : What Businesses Must Include

Mandatory e-invoicing fields in the UAE are the data elements required in structured electronic invoices exchanged through Accredited Service Providers under the UAE Electronic Invoicing System.  These fields help validate invoices, support tax reporting, and ensure invoices are transmitted in the required machine-readable XML format.

Key Takeaways

• Mandatory e-invoicing fields are the required data points that must be included in a UAE electronic invoice.
• Mandatory fields UAE differ for Electronic Tax Invoices and Commercial Electronic Invoices.
• Electronic Tax Invoices have 51 mandatory fields and Commercial Electronic Invoices have 49 mandatory fields.
• Missing or incorrect mandatory fields may cause validation failure.

What Is Mandatory e-Invoicing Fields in UAE? 

Mandatory e-invoicing fields are the required data points that must be included in a UAE electronic invoice. These fields are prescribed by the Ministry and apply to structured invoice payloads exchanged through the e-invoicing system. They are not limited to what appears on a printable invoice. They include invoice identifiers, supplier details, buyer details, tax information, totals, line-level data, and electronic address information. The UAE system uses structured XML invoices based on Peppol PINT-AE specifications. Field requirements may change based on invoice type and transaction scenario.

Complete List of Mandatory e-Invoice Fields in UAE

The UAE Ministry of Finance has defined a detailed list of UAE e-invoice required fields for structured electronic invoices.

These include:

• 51 mandatory fields for Electronic Tax Invoices
• 49 mandatory fields for Commercial Electronic Invoices

The fields cover:

• Invoice-level details (invoice number, date, type, currency)
• Seller and buyer identifiers (TIN, TRN, legal identifiers, electronic address)
• Tax breakdown and totals
• Line-level quantity, pricing, and tax data
• Technical fields required for Peppol-based exchange

These fields are part of the structured XML invoice payload and are required for validation, exchange, and tax reporting.

Download the complete list of mandatory UAE e-invoicing fields

Mandatory Fields for B2B Invoices 

B2B invoices in UAE e-invoicing need to be understood in two ways.

1. B2B is a core transaction category under the UAE e-invoicing rollout. B2C transactions are not currently subject to the Electronic Invoicing System until a decision is issued by the Minister.
2. Under VAT invoicing, B2B often means the buyer may be a VAT registrant. This affects whether the buyer’s TRN is required.

B2B Tax Invoice

If the supplier is VAT-registered and must issue a tax invoice, the Electronic Tax Invoice fields apply. The invoice must include structured details such as:

• Supplier details
• Buyer details
• Seller TRN
• Buyer TRN where the buyer is registered
• Tax breakdown
• Invoice totals
• Line-level quantity, price, and tax details

As per rules, e-invoicing fields UAE VAT should include invoice number, issue date, supply date if different, description of supplies, unit price, quantity, VAT rate, tax amount in AED, discounts, gross amount in AED, and reverse-charge statement where applicable.

B2B Commercial Invoice

If the supplier is not VAT-registered and a tax invoice is not required, the Commercial Electronic Invoice fields apply. In this case, the invoice relies more on legal registration identifiers. Seller tax registration may use TRN if available, or TIN where TRN is not applicable.

Buyer Not Yet Onboarded

The UAE guidelines address cases where a buyer has not implemented e-invoicing and does not have a participant identifier. In such cases, the supplier must still include mandatory endpoint information using the predefined endpoint. This means seller systems must be able to populate buyer electronic address and buyer electronic identifier even when buyer master data is incomplete.

Scenario-Based Mandatory Fields

Some fields depend on the transaction scenario. The UAE guidelines include scenarios such as:

• Free zone
• Deemed supply
• Margin scheme
• Summary invoice
• Continuous supply
• Agent billing
• E-commerce supply
• Exports

Multiple scenarios may apply to one invoice. When that happens, the invoice must include the requirements for all applicable scenarios. 

The invoice transaction type code supports these scenarios through an 8-flag sequence.

Common Errors in Mandatory e-Invoice Fields & How to Fix Them

Errors in mandatory fields can cause validation failures at the ASP or Peppol exchange layer. These errors may delay invoice transmission and tax-data reporting.

How ClearTax Helps You Include Every Mandatory e-Invoice Field

ClearTax is listed by the Ministry of Finance as a pre-approved e-invoicing service provider in the UAE. The UAE e-invoicing model works through ASPs. This makes ASP support important for invoice validation, exchange, and reporting. ClearTax supports Peppol-based exchange, ERP integration, error management, dashboards, and business system integration. These capabilities help businesses manage mandatory-field compliance in the following ways:

• Check whether required fields exist before transmission
• Support structured field mapping from ERP and business systems
• Help manage seller and buyer identifier fields
• Support endpoint handling for e-invoice exchange
• Identify missing or incorrect mandatory fields
• Support validation and resubmission workflows
• Help reduce errors in invoice payloads
• Support compliance with PINT-AE-based e-invoicing requirements

Auto-Filling Mandatory Fields

Some mandatory fields can be auto-filled once configured.

These include stable master data fields such as:

• Seller name
• Seller address
• Seller electronic identifier
• Seller TIN
• Seller TRN
• Default tax scheme code
• Specification identifier

Other fields must be generated for each transaction.

These include:

• Invoice amount
• Tax breakdown
• Line-level quantity
• Line-level price
• Line-level tax details

Scenario-based fields need rules. For example, exports, deemed supplies, and other special cases may require specific flags or predefined endpoints.ClearTax can support auto-fill and validation patterns when source data, business rules, and master data are properly configured.

Conclusion

Mandatory e-invoicing fields in the UAE are required data elements in structured electronic invoices. They support invoice validation, Peppol-based exchange, and tax-data reporting.

B2B invoices require careful classification based on whether a tax invoice or commercial invoice applies. Buyer TRN, seller TRN, legal registration identifiers, electronic addresses, tax breakdowns, and line-level details must be mapped correctly.

Most field errors occur due to missing endpoints, wrong identifiers, incorrect invoice category, scenario flag errors, TRN mismatches, or calculation issues.