Compliance model

The UAE uses a five-corner compliance model where your Accredited Service Provider (ASP) validates and sends invoices and simultaneously reports tax data to the FTA in near real time. The FTA receives and acknowledges the reported tax data. It doesn't clear or approve individual invoices.

An invoice is legally valid after it has been exchanged and reported through accredited service providers.

The five-corner model actors are these:

Corner 1: Supplier

The business that issues the invoice. Sends invoice data to their ASP for validation and transmission.

Corner 2: Access Point, Sender (Sovos ASP)

The ASP acting on behalf of the supplier. Validates the invoice against the UAE PINT standards, sends it through the PEPPOL network, and reports tax data to the FTA.

Corner 3: Access Point, Receiver (Buyer ASP)

The ASP acting on behalf of the buyer. Receives the invoice, validates it, makes it available to the buyer, and reports purchase tax data to the FTA.

Corner 4: Buyer

The business that receives the invoice. Accesses it through their ASP.

Corner 5: Federal Tax Authority (FTA)

The supervisory authority. Receives tax data from both the sender ASP and receiver ASP in near real time for tax reporting and input tax credit validation.

E-invoicing mandate

The UAE introduced VAT in 2018. Federal Decree-Law No. 16 of 2024 formally recognized electronic invoices as valid tax documents. The MoF then issued Ministerial Decision No. 243 and Ministerial Decision No. 244 of 2025 to set up the full framework. In June 2026, the MoF published the UAE Electronic Invoicing Guidelines (V1.1), which confirmed the operational details of the mandate.

A pilot phase begins on July 1, 2026 and is open on a voluntary basis to any business that wishes to participate early, regardless of revenue, ahead of its required phase.

For the most current implementation timeline, see the MoF e-invoicing page.

Tax authority

The FTA administers UAE tax compliance. The MoF governs the e-invoicing framework and accredits service providers. Use the following resources to access the official portals and regulatory documents for UAE e-invoicing:

• Mof e-invoicing portal

• UAE electronic document specifications

Key concepts

Transaction type flags

The UAE mandate needs every invoice to include a binary transaction type code in the SovosExtension block. This code tells the FTA which of several special transaction types applies: Free trade zone, margin scheme, deemed supply, summary invoice, continuous supply, agent billing, e-commerce supply, or exports. Validators reject invoices that omit or misconfigure this field.

Five-corner compliance model with parallel FTA reporting

The UAE model adds a fifth corner to the standard PEPPOL four-corner model by requiring both the supplier ASP and the buyer ASP to independently report tax data to the FTA. A transaction isn't complete until Sovos has both delivered the invoice (DELIVERED) and received FTA confirmation of the TDD submission (REPORTED).

Tax Registration Number (TRN)

Tax Registration Number. 15-digit alphanumeric number, needed if VAT-registered.

Accredited Service Provider (ASP)

A service provider accredited by the MoF to validate, send, and report invoices on behalf of businesses.

Critical concepts unique to UAE

Message Disposition Notification (MDN)

A confirmation message sent over the UAE e-invoicing network to acknowledge receipt of a document.

EmaraTax ASP appointment

Before you can send or receive invoices, you must appoint an ASP through EmaraTax, the FTA portal. This isn't just a platform setup step. It's a regulatory act that creates your PEPPOL Participant ID and links your Tax Identification Number (TIN) to Sovos in the UAE network. Switching ASPs also goes through EmaraTax.

Message Level Status (MLS)

A confirmation message sent over the UAE e-invoicing network to acknowledge receipt and validation of a document.

PEPPOL International Invoice for UAE (PINT-AE)

The UAE mandate uses an XML invoice format. It extends the global PINT standard with UAE-specific fields and validation rules. All invoices exchanged between UAE PEPPOL participants must use the PINT-AE format.

Tax Data Document (TDD)

As part of every transaction, the Sovos ASP automatically generates a TDD from your invoice and reports it to the FTA. You don't need to generate or submit the TDD. Sovos handles this. The TDD has three sections:

• Metadata identifying the parties and roles

• Extracted tax-relevant data

• Complete invoice in extended XML

How the outbound flow works

1. The supplier sends invoice data to Sovos Compliance Network.

2. Sovos validates the document, converts the data to PINT-AE XML, and passes it to the Sovos ASP.

3. Sovos ASP sends the invoice over the PEPPOL network to the buyer ASP.

4. In parallel, the Sovos ASP generates a TDD and reports it to the FTA.

5. The buyer ASP validates the invoice, delivers it to the buyer, and also reports a TDD to the FTA.

6. The FTA sends confirmation to both the Sovos ASP and the buyer ASP.

7. Sovos forwards the final status confirmation to you.

In addition to the outbound flow, Sovos handles an inbound flow (receiving invoices from your suppliers) through the PEPPOL network. Both flows run through a single ASP. See Send invoice flow for details.