Structured E-Invoice in the UAE: Format, Rules, and How It Works

February 23, 2026
UAE e-invoicing requirements checklist for finance teams showing master data, PINT AE mapping, VAT logic, and go live planning

Key Takeaways

  • A practical UAE e-invoicing requirements checklist for finance teams. Learn what counts as an e-invoice, what data must be ready, how PINT AE mapping works, and what to prep before onboarding an Accredited Service Provider

A structured e-invoice in the UAE is an electronic invoice that is created with a specific structure and is exchanged and reported electronically. The structure is a standard format that allows systems to process it automatically. Unlike the traditional PDF or scanned invoice, structured e-invoices are designed for machine-to-machine processing.

Now, what does this definition mean?

The UAE is introducing the e-invoicing framework, which means invoices now have to be made electronically and contain structured data, following the required UAE specifications. Businesses need more than just a digital invoice copy for their B2B or B2G transactions. This new framework requires invoice data that can be read, validated, and processed by the systems in the e-invoicing network.

In this guide, we’ll explain what makes an e-invoice structured, which data needs to be on it, how the UAE e-invoicing works with this data, and how you can prepare your business.

‍

What Does “Structured” Mean in a UAE E-Invoice?

A structured e-invoice means the invoice data is organized in a standard format that relevant software can read, validate, and process automatically. It’s not just a digital version of a paper invoice. 

Based on the UAE e-invoicing framework, e-invoices are issued in XML format, based on the PINT AE (Peppol International Invoice - UAE) specification. The UAE Ministry of Finance specifically announced that PDFs, Word documents, scanned copies, and emails are not considered e-invoices, and here is why:

‍

Format Structured e-invoice? Why?
XML e-invoice Yes The invoice data is structured so systems can process it automatically
PDF invoice No It is a visual document rather than structured data.
Word document No The information is not provided in the required structured format.
Scanned invoice/image No The information is stored as an image rather than machine-readable invoice data.
Invoice sent by email No Email is a delivery method, not a structured e-invoice.

‍

So, why does this “structure” matter so much? The e-invoicing network must be able to read and process individual data fields automatically, and for that your invoices need to be structured. This doesn’t mean that you need to create a special-looking invoice. All you have to do is make sure the underlying invoice data follows the required structure and specifications.

‍

The UAE’s E-Invoicing Model: Five-Corner Peppol Network

The whole reason behind the structured e-invoice in the UAE is the Five-Corner Model. UAE is using this decentralized model built on the Peppol network, which connects the supplier and buyer and allows them to exchange e-invoices while the relevant tax data is automatically reported to the Federal Tax Authority (FTA).

The five corners are:

  • Supplier: The business that issues the invoice in its ERP or accounting system.
  • Supplier’s ASP: The supplier’s Accredited Service Provider that validates and sends the structured invoice through Peppol.
  • Buyer’s ASP: The buyer’s ASP that receives and validates that invoice before delivering it to the buyer.
  • Buyer: The business that receives the structured e-invoice in its ERP or accounting system.
  • FTA: The Federal Tax Authority that receives the relevant tax data from the supplier and buyer’s ASPs for electronic tax reporting.

The structured e-invoice (UAE) can easily be created, exchanged, validated, and read throughout this whole process.

‍

Structured E-Invoice UAE Mandatory Fields and Data Structure

To be identified and processed correctly, e-invoices must contain specific information. The UAE e-invoicing specifications and PINT AE data model define these required data. There are four classes and mandatory fields:

Invoice Identity Fields

These fields identify the invoice and provide the key information about the transaction itself:

  • Invoice number: A unique identifier for the invoice.
  • Invoice date: The date the invoice is issued
  • Invoice type code: Identifies the document type, invoice or credit note.
  • Currency code: Specifies the currency used for the transaction.
  • Transaction type code: Identifies the relevant transaction scenario.
  • Payment due date: States when the invoice payment is due.
  • Specification and business process identifiers: Identify the e-invoicing specification and process being used.

Supplier and Buyer Fields

In the e-invoice, you must identify both parties and provide the necessary information for routing and tax purposes:

Supplier fields

  • Legal name
  • Electronic address and electronic identifier
  • Legal registration identifier
  • Tax identifier and tax scheme
  • Address and country details

Buyer fields

  • Legal name
  • Electronic address and electronic identifier
  • Tax identifier and tax scheme, where applicable
  • Address and country details

The most important of these fields are the electronic addresses and identifiers because they help the Peppol network route the invoice to the correct recipient.

Line Item and Amount Fields

Each item (product or service) is also added to e-invoices as structured data in mandatory fields rather than plain text:

  • Item name and description: Identifies what was supplied.
  • Quantity and unit of measure: Shows how much was supplied and how it’s measured.
  • Unit price: The price used to calculate the line amount.
  • Line net amount: The value of the line before tax.
  • VAT category and rate: Identifies the applicable VAT treatment.
  • VAT amount: The tax calculated for the line.
  • Summary totals: Total amount before VAT, total VAT, total amount including VAT, and amount due.

Reference and Control Fields

These additional fields connect the invoice to its transaction and support processing and validation:

  • Purchase order or contract references: Connect the invoice to the underlying business transaction.
  • Previous invoice references: Link a credit note or other adjustment to the original invoice.
  • Payment information: Provides information needed to process the payment.
  • Tax breakdown: Summarizes taxable amounts, VAT categories, rates, and tax amounts.
  • Scenario-specific information: Any additional data for specific transactions, like exports, free zone transactions, or other defined scenarios.

Bear in mind that not all fields are mandatory for every invoice. You can check the Ministry of Finance’s e-invoicing documentation to understand which fields apply to which invoice type and transaction.

‍

Is Structured E-Invoicing (UAE) Mandatory? Rollout Timeline

Yes. The UAE e-invoicing framework is becoming mandatory for B2B and B2G transactions that are in scope of the program. The UAE introduced a pilot phase on July 1, 2026, which is voluntary to participate in, and the mandatory implementation phases are beginning in 2027:

‍

Business or entity ASP appointment deadline E-invoicing implementation
Businesses with annual revenue over AED 50 million October 30, 2026 January 1, 2027
Businesses with annual revenue below AED 50 million March 31, 2027 July 1, 2027
Government entities March 31, 2027 October 1, 2027

Important note: The mandatory framework currently covers B2B and B2G transactions. B2C transactions are outside the mandatory framework.

‍

How to Create a Structured E-Invoice in the UAE

To create a structured e-invoice (UAE), you need to prepare the required invoice data, convert it into the required format, validate it, and then send it through the e-invoicing network:

  1. Prepare the invoice data

To begin, gather the accurate information and create your invoice: supplier, buyer, transaction, tax, line-item, payment, and reference information. Ensure your data is complete and consistent with the applicable invoice requirements.

  1. Connect your accounting or ERP system

You must connect your existing ERP or accounting systems to an Accredited Service Provider (ASP). This integration lets your invoice data move through the e-invoicing process without manual re-entry.

  1. Map the data to PINT AE

Your ASP maps the invoice data to PINT AE. The result is an XML- structured invoice that can be processed by other systems.

  1. Validate the e-invoice

The ASP will then validate your e-invoice against the required technical and business rules. This validation spots any errors, including missing or incorrect information, before the invoice is transmitted.

  1. Transmit and report the invoice

The validated structured e-invoice is then exchanged through the Peppol network between your ASP and the target company’s ASP. Meanwhile, the required tax data is reported to the FTA.

‍

Choosing a Structured E-Invoicing Solution or ASP

To create, validate, exchange, report, and store structured e-invoices in the UAE, you need an ASP. The right solution should turn your existing invoice data into compliant e-invoices without creating unnecessary manual work. Here is a list of things to check before committing to an ASP:

  • Supports PINT AE: The ASP must generate invoices in the UAE’s required structure format.
  • Connects to existing systems: The ASP should be compatible with your existing ERP or accounting systems.
  • Uses Peppol: Check that the provider is Peppol-certified and supports transmission through the UAE’s e-invoicing network.
  • Validates invoice data: The system should identify missing or incorrect information before an invoice is transmitted.
  • Supports required reporting: Review how the provider handles the required tax data sent to the FTA.
  • Stores invoice records: You should be able to access all invoices and relevant records when needed.
  • Service Accreditation: The provider you choose must be accredited by the Ministry of Finance to offer e-invoicing services and Peppol connectivity.

‍

FAQs

What is the required format for e-invoices in the UAE?

The new framework requires e-invoices to be drafted using XML data based on the PINT-AE specification. Considering this, PDFs, Word documents, images, or scanned invoices do not qualify as structured e-invoices in the UAE.

Can a PDF be used as an e-invoice?

No. A PDF file can be used as a visual presentation of an e-invoice, but cannot be used, exchanged, or reported as an e-invoice under the UAE framework.

Is e-invoicing mandatory for all UAE businesses?

No. E-invoicing is mandatory for in-scope B2B and B2G transactions. B2C transactions are currently outside the e-invoicing mandate.

What is PINT AE?

PINT AE, Peppol International Invoice - UAE, is the invoice specification in the UAE used to structure and exchange invoice data through the Peppol network.

What happens if an e-invoice is missing mandatory fields?

If any mandatory fields are missing from your invoice, your invoice may be rejected or require correction before being transmitted successfully. That’s why it's important for your ASP to validate invoice data and find any incorrect or missing mandatory fields before transmission.

Ready to Automate Your Corporate Tax Calculations?