UAE e-invoicing 2026–2027: the timeline and what your business must do

When does e-invoicing start in the UAE?

The short answer: UAE e-invoicing is being phased in by business size. A voluntary pilot opened on 1 July 2026. The mandate goes live on 1 January 2027 for businesses with revenue of AED 50 million or more, on 1 July 2027 for all other in-scope businesses, and on 1 October 2027 for government entities. The legal basis is Ministerial Decisions 243 and 244 of 2025, issued by the Ministry of Finance.

This is not about turning your PDF invoice into an email attachment. In the UAE model, an e-invoice is structured data that travels from your system to your buyer's system through accredited providers, while the tax-relevant data reaches the Federal Tax Authority. That is why the date that really matters is not go-live but the ASP appointment deadline that comes months earlier.

If you sell to other businesses through a website or app, or run a store that issues tax invoices to company customers, this guide is for you. If you are new to VAT itself, start with VAT for online sellers in the UAE.

With e-invoicing, your real deadline is the day you appoint a provider, not the day you go live.

The full timeline in one table

Here are the announced dates side by side. Find the row that applies to your business, then plan backwards from the ASP appointment date.

Smaller businesses are not exempt; they are simply in the second wave. A small online store selling to companies will most likely sit in the "below AED 50 million" group, which makes 31 March 2027 its real deadline for choosing a provider.

Who is in scope, and what about selling to consumers?

The current scope focuses on business-to-business (B2B) and business-to-government (B2G) transactions. Business-to-consumer (B2C) invoices are out of scope for now, although that could change in the future.

A store that sells to both households and companies, say an office supplies shop, needs to tell the two apart inside its system: who is the customer, do they have a Tax Registration Number (TRN), is this a B2B order? That small distinction in your database is what makes connecting to a provider straightforward later.

How does it work? The Peppol five-corner model

The UAE chose a model built on the Peppol network, often described as a "five-corner" model (four corners for the invoice exchange itself). Your invoice does not go straight to the customer's inbox; it passes through two accredited providers.

1. 1
   Corner 1: the supplier (you)

   Your accounting system or app creates the invoice data: seller, buyer, line items, tax and totals.

2. 2
   Corner 2: your ASP

   Receives the data from your system, validates it, converts it to the required format and sends it across the network.

3. 3
   Corner 3: the buyer's ASP

   Receives the invoice on behalf of the business customer and delivers it to their system.

4. 4
   Corner 4: the buyer

   Gets the invoice directly into their accounting system, with no manual re-typing.

5. 5
   Corner 5: the Federal Tax Authority

   Receives the tax data of the invoice via the providers, which is what makes the model five-cornered.

The practical upshot: you do not build a connection to the FTA yourself. Your job is to make your system produce correct, structured data and to have an accredited provider receive it. For the provider's role in detail, read what an Accredited Service Provider is.

What should you do now? A 6-step action plan

1. 1
   Confirm your group and dates

   Ask your accountant to confirm your revenue group, then put the ASP appointment date in the calendar with at least two months of buffer.

2. 2
   Map where invoices come from

   Accounting software, an online store, a custom app, Excel sheets? Every source needs a path to the provider.

3. 3
   Clean your customer data

   Legal company names, TRNs and addresses. Errors here will surface later as rejected invoices.

4. 4
   Choose an accredited provider

   Compare officially accredited providers on integration with your systems, support and Arabic, and sign before the deadline.

5. 5
   Connect and test

   Link your system to the provider through an API or ready-made connector, run real invoices in a test environment and use the voluntary pilot if you can.

6. 6
   Train the team and monitor

   Who follows up rejected invoices? Who fixes customer data? Write a simple procedure before go-live day.

What does this mean for your online store or app?

If your store or app sells to businesses, e-invoicing becomes a question of data quality more than a legal one. Your system must know who the customer is, store their TRN, calculate 5% VAT accurately per line and export invoice data in a form your provider can read.

• Customer type: a clear field separating individuals from companies, with a TRN field requested only when needed.
• Invoice numbering: a unique sequence that never repeats and is never reused after a cancellation.
• Credit notes: returns and post-sale discounts need documents linked to the original invoice.
• Delivery log: the status of every invoice at the provider (sent, accepted, rejected) visible in your dashboard.
• Export and integration: an API or webhook that pushes each invoice to the provider as soon as it is issued.

With Fanann you can build this logic by describing it: an invoicing module with calculated VAT, business-customer fields and a status dashboard. Fanann is not an accredited provider, but the app you build can connect to yours through integrations and APIs, and you keep full ownership of the code.

Common mistakes to avoid

• Waiting for go-live: the first deadline is appointing a provider, and integration and testing take weeks after that.
• Assuming small means exempt: businesses under AED 50 million are in the second wave, not outside the system.
• Relying on PDFs: a PDF sent by email is not an e-invoice in the new sense.
• Forgetting side sources: invoices issued from an Excel sheet or an old app get forgotten until go-live day.
• Copying Saudi Arabia literally: ZATCA's Fatoora system differs in design and phasing, so do not assume what works there works here.

Frequently asked questions

Terms in this article