UAE E‑Invoicing Mandatory Fields Explained: What the FTA’s 51 Requirements Mean for Your ERP

UAE E‑Invoicing Mandatory Fields Explained: What the FTA’s 51 Requirements Mean for Your ERP

The UAE’s digital tax transformation accelerated sharply on 23 February 2026, when the Federal Tax Authority (FTA) released its most detailed technical publication to date: a full specification of mandatory data fields required for UAE electronic tax invoices under the new e‑invoicing system. These mandatory fields form the backbone of the UAE’s structured invoicing framework and align fully with the country’s adoption of the Peppol PINT‑AE specification.

The release of this 16‑page document is a significant milestone, giving businesses and software vendors crystal‑clear visibility into what a compliant UAE e‑invoice must contain — and what ERP systems must support before the mandate goes live in 2027.


Why Mandatory Fields Matter

Global e‑invoicing frameworks — from Europe to Singapore — rely on structured, machine‑readable data that tax authorities can validate, compare, and process. The UAE has taken the same approach by defining strict, standardised data elements for every electronic tax invoice, whether B2B or B2G.

According to the FTA’s technical guidance:

  • All invoices must follow the PINT‑AE XML format, the UAE‑specific Peppol billing specification.
  • Manual PDFs, email‑sent invoices, or scanned documents will not meet compliance once mandatory phases begin.

This ensures consistency, auditability, and real‑time validation across the entire supply chain.


Breakdown of the 51 Mandatory Fields

The FTA categorises the mandatory fields into several structured blocks. Here’s what each section includes.


1. Invoice Details

This section establishes the identity and classification of the invoice.

Key fields include:

  • Invoice number
  • Invoice issue date
  • Invoice type code (e.g., standard, credit note, self billing)
  • Currency code
  • Payment due date
  • Specification identifier, which signals the use of UAE‑specific PINT‑AE standards
  • Transaction type flags and payment means type code

2. Seller Details

The UAE e‑invoicing structure requires a standardised seller identity with specific fields such as:

  • Seller name
  • Electronic address (the Peppol endpoint ID)
  • The seller identifier “0235”, indicating a UAE‑registered business
  • Legal registration details
  • TRN/TIN (Tax Registration Number / Tax Identification Number)
  • Address elements

Importantly, the UAE mandates the use of TIN as the primary e‑invoicing participant identifier. The TIN equals the first 10 digits of the corporate tax TRN.


3. Buyer Details

Similarly structured to seller fields, buyer information must include:

  • Buyer name
  • Electronic address and identifier
  • Buyer TRN (if applicable)
  • Address elements
  • Legal identifiers

These fields ensure both sides of the transaction can be validated across ASPs under the Peppol model.


4. Document Totals

A UAE e‑invoice must present structured numeric data for:

  • Total line net amounts
  • Total amounts with and without VAT
  • Total tax amounts
  • Gross payable amount

These totals must be system‑generated and consistent with line‑level and tax‑level data.


5. Tax Breakdown

This includes:

  • Tax category code
  • Applicable rate (5%, 0% etc.)
  • Taxable amount
  • Tax amount

6. Invoice Line Item Requirements

Each invoice line must include:

  • Line ID
  • Quantity
  • Unit of measure
  • Item price
  • Tax category
  • Tax rate
  • AED equivalent amounts where relevant

Key Implications for Businesses and ERPs

1. ERP systems must support structured XML (PINT‑AE)

Traditional invoice layouts must now be supplemented — or replaced — with compliant XML generation capabilities. PDFs alone will not suffice.

2. TIN becomes the universal identifier

Every business issuing e‑invoices must obtain a TIN from the FTA, even if not required to register for corporate tax.

3. ASP integration becomes mandatory

Peppol‑based Accredited Service Providers (ASPs) must validate, route, and secure invoices under the UAE’s five‑corner model.

4. Data consistency becomes a compliance issue

Master data quality — item descriptions, customer information, tax codes — becomes a regulatory requirement, not just an accounting hygiene task.


Timeline Reminder

Per Ministerial Decision 244 of 2025:

  • Voluntary Phase: July 1, 2026
  • Mandatory (≥ AED 50M revenue): January 1, 2027
  • Mandatory (< AED 50M revenue): July 1, 2027

How Fynamics Helps UAE Businesses Comply

Fynamics supports businesses with a complete UAE e‑invoicing compliance suite:

  • PINT‑AE–compliant invoice generation
  • Direct ASP connectivity
  • ERP‑agnostic integration
  • Automated mapping for all 51 mandatory fields
  • Future‑ready support for upcoming FTA updates

Early adoption ensures seamless transition and avoids operational or regulatory disruption.

Fynamics is a PEPPOL Certified AP & SMP and currently undergoing accreditation process with UAE FTA. For Fynamics UAE details, pl visit https://www.fynamicstax.com/uae/