E-invoicing in Dubai and the UAE: obligations, deadlines and what changes on your invoices

1. What e-invoicing actually is

The term is widely misunderstood. An e-invoice under the new rules is not a PDF sent by email, and not a scanned document. From the authority’s perspective both are static images that cannot be processed by machine.

What is meant is a structured data record in XML format whose fields follow a defined schema — the UAE’s PINT AE data dictionary. Every field has a defined meaning, so the invoice can be read, validated and posted by systems without anyone re-keying it.

The five-corner model

The UAE has adopted the international Peppol network and added a fifth station to it. The path an invoice takes:

• Corner 1 — the supplier. Generates the invoice data in its own accounting or ERP system.
• Corner 2 — the supplier’s accredited service provider (ASP). Converts the data into the prescribed format, validates it for completeness and plausibility, and forwards it.
• Corner 3 — the buyer’s service provider. Receives the invoice, validates it again and delivers it.
• Corner 4 — the buyer. Receives the invoice in processable form.
• Corner 5 — the Federal Tax Authority. Receives the tax-relevant data for every invoice from the service providers, in near real time.

That fifth corner is the real substance of the reform. The tax authority will see transactions not when the quarterly return arrives but almost at the moment the invoice is created. The technical term is continuous transaction control.

The accredited service provider

Without an Accredited Service Provider (ASP) participation is technically impossible. Both the supplier and the buyer must appoint one. Accreditation of these providers is governed by a separate ministerial resolution; the Ministry of Finance maintains the list.

One point on expectations: an ASP is a technical transmission provider, not a tax adviser. It checks whether a field is populated — not whether the content is correct for tax purposes. Section 9 returns to this.

3. Who is in scope

The system covers everyone conducting business in the UAE — mainland and free zone, large enterprises and sole traders alike. Free zone status creates no exception. Foreign companies registered for VAT in the UAE are also caught.

In scope are transactions between businesses (B2B) and with government bodies (B2G).

What is excluded for now

• Transactions with private consumers (B2C) — not in scope until further notice
• Government bodies acting in a sovereign capacity and not competing with the private sector
• International passenger air transport where an electronic ticket is issued, and associated ancillary services
• International air freight where an airway bill is issued — limited to 24 months from the effective date
• Financial services that are exempt from VAT or zero-rated

Transactions within a VAT group have a 24-month transitional period from 1 January 2027; they remain in scope in principle.

A word on framing: the B2C exclusion applies expressly "until further notice". A retail or hospitality business should not plan on it being permanent.

4. Timeline and thresholds

On the revenue threshold: what counts is gross income for the most recent accounting period per the financial statements. For the large majority of owner-managed businesses in the UAE, that means the second wave — system live from 1 July 2027.

5. What changes on the invoice itself

The simplified invoice disappears

At present a simplified tax invoice may be issued where the recipient is not registered, or where the consideration to a registered recipient does not exceed AED 10,000. For businesses inside the e-invoicing system that concession falls away. Every invoice in scope must carry the full data set.

Credit notes and corrections

Cancellations, reductions, refunds and error corrections are handled through an electronic credit note that travels the same path as the invoice. An informal correction by email, or a handwritten amendment, is not possible.

Deadline for issuing

The invoice must be issued within 14 days of the taxable event. That deadline already applies today, but it acquires teeth in the new system: transmission is logged and visible to the authority.

Storage

Electronic records must be stored so that they remain complete, unaltered and retrievable by the tax authority. Version 1.1 of the guidelines now also permits storage outside the UAE or in the cloud, provided the authority’s access is assured.

6. Domestic invoices

Here the system applies in full. Both sides — supplier and recipient — must be connected to an accredited service provider. The invoice travels via both providers to the recipient, and the tax-relevant data goes to the authority in parallel.

Where the recipient is registered, the recipient’s TRN is a mandatory field. Where a trading partner is not yet connected, the rules provide predefined identifiers so the invoice can still be processed and reported.

The practical consequence: connecting your own outgoing side is not enough. If you receive invoices, you need access too — otherwise incoming invoices do not arrive in usable form, which puts input tax recovery at risk.

7. Invoices to customers abroad

This is the point most often stated wrongly in public discussion. The common assumption is that exports are unaffected because the customer is not on the network anyway. That is not correct.

Export supplies are within the system. A supplier in the UAE must generate the invoice in the prescribed format and report it to the tax authority through its service provider even where the recipient is in Europe, the United States, Asia or anywhere else outside the UAE.

How this works in practice

• The invoice is generated in the prescribed data format and reported to the tax authority through the service provider.
• Where the overseas customer has no Peppol identifier, a predefined substitute identifier for export cases is used.
• The commercial document still reaches the customer the usual way — as a PDF by email or through a portal.

For your customer abroad, nothing changes. They do not have to join a network or buy software. The transition affects only the supplier side in the UAE.

Note that the tax treatment has to be reflected correctly in the data record — an export at the zero rate requires different fields from a domestic supply at 5 per cent. This is exactly where the typical errors arise.

Separately, many countries operate their own e-invoicing or digital reporting requirements — the EU, several Latin American and Asian jurisdictions among them — which follow their own local rules and are not aligned with the UAE system. If you supply customers in those markets, their requirements should be clarified separately; this guide covers UAE law only.

8. Penalties

The penalty framework comes from Cabinet Decision No. 106 of 2025 and applies only to businesses required to participate. Voluntary participants are outside it.

The first item is the dangerous one, because it continues monthly until the connection is actually live. The second looks small but adds up quickly at volume: at 300 outgoing invoices a month, a faulty interface produces AED 30,000 before anyone notices it.

On top of that sits the general penalty framework for non-compliant invoices under Cabinet Decision No. 129 of 2025. And above everything is the real consequence: a customer who cannot recover input tax from a defective invoice will withhold the amount.

9. Why this belongs in expert hands

The technical connection is handled by the accredited service provider. What it does not handle is the tax assessment of the data it transmits. An ASP checks whether a mandatory field is populated — not whether the content is right.

Between your accounting system and the report to the authority sits precisely the work that requires professional judgement:

• Classifying the transaction. Domestic supply, export, reverse charge, advance payment, continuous supply, deemed supply — each requires its own representation in the data record.
• Tax treatment. Standard rate, zero rate or exemption must be set correctly and supported. A supply wrongly treated as an export is now immediately visible.
• Master data maintenance. Customer tax numbers, network identifiers, address data, substitute identifiers for overseas cases.
• Reconciliation with the return. The reported invoice data and the VAT return must agree. Discrepancies generate queries.
• Error handling. Rejected invoices, system outages with a reporting obligation, subsequent corrections through electronic credit notes.

Then there is the ongoing correspondence with the tax authority: queries on individual reports, clarification of discrepant data, voluntary disclosure where errors are identified, and responses to audit requests. This correspondence is conducted in English and requires knowledge of the procedural rules.

A clear division of labour is therefore sensible: the accredited service provider supplies the pipe, and your accountant makes sure the right data flows through it — and handles the correspondence with the authority.

10. What to do now

For businesses in the second wave — below AED 50 million of revenue — 1 July 2027 is the date. That sounds distant but is not: ahead of go-live sit provider selection, software integration, master data clean-up and a testing phase.

• By the end of 2026: check whether your accounting system supports the required connection. Older or purely spreadsheet-based setups generally do not.
• Early 2027: select an accredited service provider and sign the contract. The appointment deadline is 31 March 2027.
• First half of 2027: clean up master data — complete customer tax numbers, correct addresses, item masters with the right tax codes.
• Before 1 July 2027: run a test phase with real documents, reconcile the reports, and train the people involved.

Voluntary participation has been open since July 2026 and carries one practical advantage: errors during testing do not trigger penalties, because the penalty framework applies only to businesses required to participate.

11. Frequently asked questions