UAE e-invoicing: deadlines, how it works and a go-live checklist

What UAE e-invoicing is

On 29 September 2025 the Ministry of Finance (MoF) published Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System and Ministerial Decision No. 244 of 2025 on its implementation. Together they require businesses to issue and receive invoices and credit notes as structured electronic data, exchanged through accredited service providers, instead of paper or PDF.

The system covers business-to-business (B2B) and business-to-government (B2G) transactions. According to KPMG, it applies to businesses and government entities operating in the UAE whether or not they are registered for VAT, unless the legislation excludes them. Check Ministerial Decision No. 243 for the transactions it excludes.

Deadlines: who goes live when

The amendment announced on 10 May 2026 gave large businesses three more months to choose an ASP but kept their 1 January 2027 go-live date. That leaves less time between appointing a provider and going live, so integration and testing have to run in parallel.

How an e-invoice travels: the five-corner model

The UAE uses a decentralised five-corner model built on the Peppol network:

1. 01

   Corner 1: the supplier

   Creates the invoice in its ERP or accounting system.

2. 02

   Corner 2: the supplier’s ASP

   Validates the invoice against the UAE rules and sends it over Peppol.

3. 03

   Corner 3: the buyer’s ASP

   Receives the invoice and delivers it to the buyer.

4. 04

   Corner 4: the buyer

   Receives the invoice as structured data in its own system.

5. 05

   Corner 5: the FTA

   Receives the tax data reported by the ASPs.

Both sides need an ASP, so the rules change what you receive as well as what you send. Invoices use PINT AE, the UAE version of the Peppol International (PINT) invoice specification, exchanged as XML. A PDF or a scanned invoice is not an e-invoice under the system.

Choosing an accredited service provider

Only providers accredited by the Ministry of Finance can exchange e-invoices and report tax data. The Ministry publishes its list of pre-approved providers and its considerations for selecting one. Ask each provider on your shortlist about:

• Connectors for your ERPs, and who maintains them
• Validation errors: how they come back to you and how fast
• Volumes, availability and support hours around month end
• Receiving supplier invoices, not only sending your own
• Archiving, data residency and exit terms, so you can change provider later

Penalties under Cabinet Decision No. 106 of 2025

The decision also fines other violations, such as not telling the FTA about a system failure. Voluntary participants are outside its penalties.

What your ERP has to do

Your ASP exchanges and reports the invoice, but the data starts in your ERP. Every invoice and credit note in scope needs the mandatory PINT AE fields, the right tax treatment and the buyer’s Peppol identifier. There are three common routes:

• Native ERP features: for example, SAP S/4HANA customers can use SAP Document and Reporting Compliance to connect to an ASP.
• A connector or add-on from the ASP for each ERP.
• An integration layer between all your ERPs and your ASP, which maps, validates and tracks invoices in one place.

Groups with many legal entities or several ERPs feel the difference most. Each entity has its own TRN, Peppol ID and invoice data to map and test, and every rejected invoice delays payment until it is fixed and sent again.

Go-live checklist

1. 01

   Confirm each entity’s phase

   List every legal entity, its revenue band and its go-live date.

2. 02

   Appoint your ASP

   Sign with a pre-approved provider for every entity that issues or receives invoices, before your deadline.

3. 03

   Register identifiers

   Set up each entity’s Peppol participant ID with your ASP, and collect your customers’ and suppliers’ IDs.

4. 04

   Clean master data

   Check TRNs, addresses, tax codes, units and item data in the ERP: errors here cause rejections.

5. 05

   Map to PINT AE

   Map every invoice type you issue, credit notes included, to the mandatory fields.

6. 06

   Build and test the integration

   Test with your ASP: rejections, corrections, credit notes and high-volume days.

7. 07

   Prepare to receive

   Route supplier e-invoices into accounts payable and match them to purchase orders and goods receipts.

8. 08

   Bring suppliers on board

   Share your Peppol ID with suppliers and agree when PDFs stop for invoices in scope.

9. 09

   Reconcile and keep records

   Check that what the ERP issued matches what your ASP delivered and reported, and keep the records.

10. 10

    Plan for failures

    Agree who tells the FTA if your system or your ASP fails, and how invoices catch up afterwards.

Where Qantara fits

Qantara (قنطرة) is Birbal AI’s e-invoicing integration platform. It sits between SAP or any other ERP and the ASP you appoint: it maps every invoice to PINT AE, validates it before it leaves, tracks each message and its tax data status, matches supplier invoices to the purchase order and goods receipt, and reconciles what was reported to the FTA. Qantara is not an ASP. It works with yours, and you can change ASP without touching your ERP. See Qantara.

Questions and answers

Sources

1. Ministry of Finance: Cabinet Decision No. 106 of 2025 on e-invoicing violations and penalties (PDF)
2. WAM: MoF announces targeted amendments to eInvoicing system decisions (10 May 2026)
3. EY: UAE Ministry of Finance publishes Ministerial Decisions on e-invoicing (September 2025)
4. EY: Cabinet Decision on penalties for noncompliance with e-invoicing (December 2025)
5. KPMG: phased implementation of UAE e-invoicing beginning 1 January 2027 (July 2026)
6. BDO: UAE appointment deadline for e-invoicing ASPs extended (May 2026)

Birbal AI is an independent company based in Abu Dhabi. Facts about third parties come from the sources above; check them for the latest position.