E-Invoicing · UAE Tax & Compliance

UAE e‑Invoicing Penalties Are Now Confirmed, Is Your Business Actually Ready?

Cabinet Decision No. 173 of 2026 sets the fines behind the UAE's e‑invoicing mandate, replacing Cabinet Decision No. 106 of 2025, and now reaches businesses that receive invoices as well as those that issue them. For large businesses the ASP appointment deadline has passed and go‑live is 1 January 2027. Here's what the penalties cost, what has changed, and what to do now.

Key update

  • The ASP appointment deadline for businesses with revenue of AED 50 million or more passed on 30 October 2026 (extended in May 2026 from 31 July 2026). A large business with no ASP is now late and exposed to penalties.
  • Cabinet Decision No. 173 of 2026 replaced Cabinet Decision No. 106 of 2025, with new penalty amounts and a 12‑month cap.
  • From 1 October 2026, Ministerial Decision No. 168 of 2026 replaced the ASP rules in Ministerial Decision No. 64 of 2025: only fully accredited providers may now operate.
  • The Ministry of Finance published Guidelines v2.0 on 26 October 2026 and updated Mandatory Fields guidance (v1.1) on 28 October 2026.

Key takeaways

  • Large businesses go live on 1 January 2027. The ASP deadline has passed, so any large business without a provider should appoint one now and use the remaining weeks for integration and testing.
  • Non‑compliance has a published price tag. Under Cabinet Decision No. 173 of 2026, failing to implement e‑invoicing, including not appointing an ASP, costs AED 5,000 plus AED 5,000 a month, capped at AED 50,000 in any 12 months. Each missing e‑invoice or e‑credit note costs AED 100, up to AED 5,000 a month.
  • "Pre‑approved" no longer counts. Under Ministerial Decision No. 168 of 2026 only fully accredited ASPs may operate. Confirm your provider's accreditation in writing and against the Ministry's current list.

The UAE e‑invoicing timeline

E‑invoicing is mandatory for businesses conducting transactions in the UAE regardless of VAT registration status, subject to specific exclusions. Implementation rolls out in phases, and the first appointment deadline has now passed.

UAE e‑invoicing phases, ASP appointment deadlines, and go‑live dates (as of November 2026)
PhaseWho's impactedAppoint ASP byMandate go‑live
PilotSelected businesses invited by the Ministry–From 1 July 2026
Phase 1 — Large businessesRevenue ≥ AED 50 million30 October 2026 (passed)1 January 2027
Phase 2 — Other businessesRevenue < AED 50 million31 March 20271 July 2027
Government entitiesFederal and local government bodies31 March 20271 October 2027

Revenue is measured on your most recent accounting period with financial statements, entity by entity. Guidelines v2.0 show the Phase 1 date as 31 October 2026; we recommend working to 30 October, the earlier date.

1

1 Jul 2026

Voluntary pilot opened

2

30 Oct 2026

ASP deadline, large businesses (passed)

3

1 Jan 2027

Go‑live, large businesses

4

31 Mar 2027

ASP deadline, other businesses & government

5

1 Jul / 1 Oct 2027

Go‑live, other businesses then government

For large businesses, the window between the ASP deadline and go‑live is now a matter of weeks. For an enterprise with multiple billing systems, shared service centres, or a global ERP footprint, that is a tight runway to move from a signed ASP contract to a fully tested, production‑grade integration. Phase 2 businesses have more time, but the lesson from Phase 1 is to select a provider well before 31 March 2027.

Who's actually in scope

The most common misconception about the UAE mandate is that it only touches VAT‑registered businesses. It doesn't. E‑invoicing applies to anyone conducting business in the UAE, regardless of VAT registration status, unless specifically excluded.

Participation runs on a Tax Identification Number (TIN)

  • Businesses registered with the Federal Tax Authority for any tax use a TIN corresponding to the first 10 digits of their Tax Registration Number (TRN).
  • Businesses with no existing tax registration must register with the FTA to obtain a TIN before they can participate.
  • Inside a VAT Tax Group, each legal entity uses its own TIN, not the TIN of the group's representative member.
  • Transactions between members of the same Tax Group are excluded for 24 months from 1 January 2027 (Ministerial Decision No. 197 of 2026). Each member still onboards for its other transactions, and members may use different ASPs.

The transaction scope is wider than most finance teams expect

The regime captures the large majority of commercial activity, including:

  • Supplies to government entities (B2G)
  • Tax invoices issued by non‑UAE‑established persons where required
  • Intercompany recharges and management fees
  • Intra‑group commercial activity outside the Tax Group exclusion

Holding companies and shared service centres in particular should expect meaningful process redesign. Recharge and management‑fee flows that were previously handled with a manual journal entry or a simple debit note will need to be issued as compliant structured e‑invoices.

Defined exclusions cover sovereign government activity that does not compete with the private sector, international passenger air transport with an e‑ticket and related ancillary services, international air cargo (for 24 months), VAT‑exempt financial services, and transactions within a Tax Group (for 24 months from 1 January 2027). A holding company with only passive income and no business transactions is outside the system, but any recharge brings it in. Standard‑rated financial services remain in scope, business‑to‑consumer transactions are outside the system for now, and the Minister of Finance can designate further exclusions. Scope should be confirmed against the current guidance for each transaction type rather than assumed.

The format: structured data, not a digital PDF

The UAE has adopted a Peppol‑based "5‑corner" continuous transaction control (CTC) model, aligned with the direction of travel already seen in Saudi Arabia, the EU, and a growing list of jurisdictions worldwide. In practice, that means:

  • Invoices are issued as structured XML built on UBL 2.1, not as PDFs or scanned paper.
  • Data must conform to PINT AE (Peppol International Invoice – UAE), the UAE‑specific extension of the international PINT specification.
  • Transmission happens exclusively through an Accredited Service Provider (ASP), which also acts as the business's Peppol access point and reports the tax data to the FTA.
  • Invoices are validated against the schema before they're considered compliant; malformed or incomplete data is rejected, not silently accepted.
  • Unless VAT law sets a different timeline, e‑invoices must be issued and transmitted within 14 business days of the transaction (Ministerial Decision No. 197 of 2026).

51 mandatory fields — and the rules keep getting sharper

The Ministry's Mandatory Fields guidance (v1.1, 28 October 2026) sets out 51 required data points for a standard electronic tax invoice and 49 for a commercial electronic invoice, spanning seller and buyer identification, TINs, line‑level VAT treatment, tax summaries, and digital validation metadata. No custom or business‑specific fields are permitted outside this schema.

The guidance keeps evolving. Guidelines v1.1 (June 2026) added rules for linking advance payments to the final invoice and for retention billing common in construction and real estate. Guidelines v2.0 (26 October 2026) adds guidance on allocating advance payments across invoice lines, Tax Groups, healthcare and insurance claims, newly established businesses, and record storage. Businesses whose field mapping is based on the February 2026 documentation should check it against the current versions before testing.

There is now a real cost to getting this wrong

Cabinet Decision No. 173 of 2026 sets out the administrative penalties for e‑invoicing non‑compliance and repeals Cabinet Decision No. 106 of 2025. It now covers businesses receiving invoices as well as those issuing them, a clear signal that the UAE intends to enforce the mandate on both sides of every transaction.

Administrative penalties under Cabinet Decision No. 173 of 2026
ViolationPenaltyCap / frequency
Failure to implement e‑invoicing, including failure to appoint an ASP (issuer or recipient)AED 5,000First instance, then AED 5,000 per month or part month; capped at AED 50,000 in any 12 consecutive months
Failure to issue and transmit an e‑invoiceAED 100 per e‑invoiceCapped at AED 5,000 per calendar month
Failure to issue and transmit an e‑credit noteAED 100 per e‑credit noteCapped at AED 5,000 per calendar month
Failure to notify your ASP of changes to FTA‑registered data within 5 business daysAED 250Per day; capped at AED 5,000 per calendar month

Penalties apply only once a business's mandatory compliance date has passed, and businesses adopting voluntarily are outside the penalty regime. Where the same business is both issuer and recipient for the same violation, only one penalty applies. The separate system‑failure penalties in the old decision have been removed, but general VAT penalties for non‑compliant tax invoices still apply under Cabinet Decision No. 40 of 2017. The AED 5,000‑a‑month exposure for failing to implement remains a useful anchor for internal business cases: readiness spend should be framed against a known, published cost of inaction.

Choosing an ASP is a systems decision, not a procurement checkbox

Every business in scope must appoint one Accredited Service Provider for both sending and receiving e‑invoices, then onboard through EmaraTax. The ASP functions as its Peppol access point and handles validation, transmission, and FTA reporting on its behalf. From 1 October 2026, Ministerial Decision No. 168 of 2026 allows only fully accredited providers to operate. There is no longer a "pre‑approved" stage: pre‑approved providers had 30 days to complete accreditation or lose their status.

Disciplined evaluation matters more than ever. The Ministry's own criteria include:

  • Relevant experience and implementation track record
  • Ownership and control of the underlying technology platform
  • ERP and billing‑system integration capability
  • Information security and data protection controls
  • Ongoing compliance‑monitoring mechanisms
  • Customer support model and service‑level commitments
  • Pricing structure and scalability

Beyond the Ministry's checklist, businesses, particularly multinational groups, should weigh:

  • Compatibility with existing and planned ERP landscapes (SAP, Oracle, Microsoft Dynamics, Workday, and payment platforms such as Stripe are the systems most UAE finance teams are integrating today)
  • Multi‑jurisdiction capability, where the same group is also managing CTC mandates in Saudi Arabia, the EU, or elsewhere
  • Hosting and record retention: e‑invoices no longer have to be stored within the UAE (Ministerial Decision No. 197 of 2026), but the business stays responsible for keeping them for the required period
  • Contract terms: accredited ASPs must provide 100 free e‑invoices a year to each customer; white‑label platforms are allowed, but the accredited provider stays fully responsible and needs Ministry approval to switch platforms; and exit terms should cover the provider losing accreditation
  • Change‑management and implementation support, not just technical connectivity

Ask your provider for written confirmation of its accreditation, and check the Ministry's current list shortly before you sign rather than relying on a snapshot taken months earlier.

The practical sequencing problem

Large businesses that appointed an ASP late now have to fit ERP mapping, UAT, and staff training into the weeks before 1 January 2027, precisely the period ASPs and system integrators are busiest with every other large business doing the same thing. Phase 2 businesses can avoid this by contracting and integrating well before their 31 March 2027 appointment deadline.

What businesses should be doing now

  1. Large businesses with no ASP: appoint an accredited provider now and onboard through EmaraTax. Each month of delay adds a penalty.
  2. Confirm your phase and your TIN position, including for every legal entity inside a Tax Group, since each needs its own TIN.
  3. Map your transaction footprint against the mandate: not just standard sales invoices, but recharges, management fees, intra‑group billing, and government supplies.
  4. Map your 51/49 mandatory fields against current source data, using the October 2026 guidance, to find the gaps before testing rather than during it.
  5. Test end to end before go‑live, and agree with your ASP how errors and rejected invoices will be resolved.
  6. Phase 2 businesses: shortlist accredited ASPs now so you can appoint before 31 March 2027, and build the Cabinet Decision No. 173 penalty exposure into your business case.

Frequently asked questions

When does UAE e‑invoicing become mandatory?

Implementation is phased. A voluntary pilot opened on 1 July 2026. Large businesses (revenue ≥ AED 50 million) had to appoint an ASP by 30 October 2026 and must go live on 1 January 2027. Businesses below AED 50 million must appoint an ASP by 31 March 2027 and go live by 1 July 2027. Government entities must appoint an ASP by 31 March 2027 and go live by 1 October 2027.

Has the large‑business ASP deadline passed?

Yes. It passed on 30 October 2026, and the 1 January 2027 go‑live date has not changed. A large business without an ASP should appoint an accredited provider immediately, as penalties apply for failing to implement.

Does UAE e‑invoicing apply only to VAT‑registered businesses?

No. The mandate applies to businesses conducting transactions in the UAE regardless of VAT registration status, unless a transaction is specifically excluded. Participation is based on a Tax Identification Number (TIN), and businesses without a tax registration must obtain one from the FTA.

What format must invoices follow?

Invoices must be issued as structured XML compliant with the PINT AE (Peppol International Invoice, UAE) specification, built on UBL 2.1, and transmitted through an Accredited Service Provider under the Peppol 5‑corner model. PDFs and paper invoices do not qualify.

What happens if a business misses its deadline?

Under Cabinet Decision No. 173 of 2026, failing to implement e‑invoicing, including not appointing an ASP, costs AED 5,000 for the first instance and AED 5,000 per month after that, capped at AED 50,000 in any 12 months. Missing e‑invoices or e‑credit notes cost AED 100 each, up to AED 5,000 a month, and failing to notify your ASP of changes to registered data costs AED 250 a day, up to AED 5,000 a month. Penalties apply from each phase's mandatory compliance date.

How RSM UAE can help

From ERP readiness assessments and ASP selection advisory through technical integration, UAT, and post‑implementation compliance monitoring, RSM UAE supports businesses across every phase of the e‑invoicing mandate, combining local regulatory knowledge with the ERP and multi‑jurisdiction experience larger groups need.

Talk to our e‑invoicing team

Last reviewed 11 November 2026 by Haifa Balfaqih. Primary sources: UAE Ministry of Finance Electronic Invoicing Guidelines v2.0 (26 October 2026) and Mandatory Fields v1.1 (28 October 2026); Ministerial Decisions No. 243 and 244 of 2025, as amended by Ministerial Decision No. 197 of 2026; Ministerial Decision No. 168 of 2026 (ASP accreditation, replacing Ministerial Decision No. 64 of 2025); Cabinet Decision No. 173 of 2026 (penalties, replacing Cabinet Decision No. 106 of 2025).

Tax and compliance rules change frequently and deadlines may be revised further by the UAE Ministry of Finance or Federal Tax Authority. This article is for general informational purposes only and does not constitute tax or legal advice. Businesses should confirm their specific position with RSM UAE or the relevant authority before acting.

Contact us

Reach our E-Invoicing team at e-invoice-inquiry@rsm.ae, or send us a message using the form below.