Skip to Content
ZATCA Phase 2: get Odoo connected to Fatoora before your wave.See how

UAE e-invoicing 2027: deadlines, who must comply and how to get ready

What changes, the dates for your revenue band, and a five-step plan to start this week.
November 12, 2026 by
UAE e-invoicing 2027: deadlines, who must comply and how to get ready

From 2027, most invoices between businesses in the UAE can no longer be sent as a PDF by email. They have to travel as structured e-invoices through a provider accredited by the Ministry of Finance. If you issue B2B or B2G invoices, this changes how your invoices leave your system. Here is what applies to you, by when, and what to do this month.

What is changing

Under the UAE e-invoicing mandate, invoices in scope are exchanged over the Peppol network. Your system sends the invoice to your accredited service provider (ASP). The provider passes it to your customer's provider, and the tax data is reported to the Federal Tax Authority (FTA). A PDF can still go to your customer as a copy, but it is no longer the legal invoice.

Invoices to individual consumers (B2C) are not part of the current phases.

The deadlines, by revenue

  • Annual revenue of AED 50M or more: the deadline to appoint a provider was 30 October 2026, and e-invoicing becomes mandatory on 1 January 2027.
  • Annual revenue below AED 50M: appoint a provider by 31 March 2027. E-invoicing becomes mandatory on 1 July 2027. Most UAE SMEs are in this group.
  • Suppliers to government entities: must be live by 1 October 2027 to keep invoicing them.

If you are in the first group and have not appointed a provider yet, treat it as urgent.

Why "appoint a provider" is not the whole job

Signing with a provider takes a day. Getting invoices accepted takes longer, because the data inside them has to be right. The three things that most often cause rejected invoices:

  1. Customer records. Missing or wrong TRNs, duplicate customers, and addresses that do not match.
  2. Tax setup. Products and services mapped to the wrong VAT treatment, or tax codes that were fine on paper but do not map to the e-invoice format.
  3. Credit notes and corrections. These follow the same rules as invoices and are often forgotten in testing.

That is why a realistic setup takes a few weeks: most of it is data checks and testing real invoices, not the connection itself.

A five-step plan you can start this week

  1. Confirm your phase. Check your annual revenue against the thresholds above and note your two dates.
  2. Count your invoices. Add the invoices you send and the ones you receive in a month. This decides the package size you need.
  3. Clean your customer list. Export customers with their TRNs and fix the gaps first. It is the single biggest source of rejections.
  4. Choose how you connect. If you use Odoo, invoices can go straight from Odoo to the provider. Other systems such as Zoho, Tally, QuickBooks or SAP connect through an API. If you issue only a few invoices, a provider web portal is enough.
  5. Test before your go-live date. Send real invoices and credit notes in a test run and fix what comes back rejected.

What it costs

Provider packages are priced by yearly invoice volume. With Cloudmen, packages start from AED 220 a year plus a one-time setup, and include the provider fees, data readiness, testing, training and monitoring of rejected invoices. See the packages and check your deadline.

Common questions

Do I need to switch to Odoo? No. Odoo makes it simplest, but any system can connect, and a portal works for low volumes.

Do received invoices count? Yes. Packages count the invoices you send and the ones you receive.

What happens if an invoice is rejected? It has to be corrected and sent again. Monitoring rejections in the first weeks is part of a good setup.

Not sure where you stand? Check your readiness in two minutes and we will reply within one working day with your deadline and the package that fits.

Share this post