Cabinet Decision No. 173 of 2026 is the UAE’s new penalty schedule for the e-invoicing system. It repeals Cabinet Decision No. 106 of 2025 and cuts the list of violations from six to four. The fine for failing to implement e-invoicing is now capped at AED 50,000 in any 12 consecutive months. The two fines for not reporting a system failure are gone. For the first time, a business can be fined as a recipient, not only as an issuer.
The decision was signed on 6 October 2026 and announced by the Ministry of Finance at the end of October. It takes effect the day after it is published in the Official Gazette. The timing is not a coincidence. Businesses with revenue of AED 50 million or more had to appoint an Accredited Service Provider by 30 October 2026 and must go live on 1 January 2027.
Cabinet Decision No. 173 of 2026: date, scope and repeal
| Full title | Cabinet Decision No. (173) of 2026 on Violations and Administrative Penalties for Violating the Legislation Regulating the Electronic Invoicing System |
| Signed | 24 Rabi Al-Akhir 1448 H (6 October 2026) |
| Legal basis | Federal Decree-Law No. 28 of 2022 on Tax Procedures |
| Repeals | Cabinet Decision No. 106 of 2025 |
| In force | The day after publication in the Official Gazette |
| Number of violations | Four (previously six) |
| Highest capped amount | AED 50,000 in any 12 consecutive months, for failing to implement the system |
| Who is covered | Issuers and recipients within the mandatory e-invoicing system |
| Who is excluded | Businesses using the system voluntarily |
What are the e-invoicing penalties in the UAE under Cabinet Decision 173 of 2026?
The decision sets four violations. Each has a fixed amount and a ceiling. The table below follows the official schedule annexed to the decision.
| No. | Violation | Administrative penalty |
|---|---|---|
| 1(a) | The issuer or the recipient fails to implement the e-invoicing system under Ministerial Decision No. 244 of 2025 and its amendments, including failing to appoint an Accredited Service Provider | AED 5,000 for the first violation, plus AED 5,000 for each month or part of a month that the non-compliance continues. Total for 1(a) and 1(b) together may not exceed AED 50,000 in any 12 consecutive months |
| 1(b) | A recipient that has implemented the system fails to keep meeting its obligations as a recipient under Ministerial Decision No. 243 of 2025 and its amendments | AED 5,000 for the first violation, plus AED 5,000 for each month or part of a month that the non-compliance continues. Shares the AED 50,000 cap with 1(a) |
| 2 | The issuer fails to issue and send an electronic invoice to the recipient through the e-invoicing system | AED 100 for each electronic invoice, up to AED 5,000 per calendar month |
| 3 | The issuer fails to issue and send an electronic credit note to the recipient through the e-invoicing system | AED 100 for each electronic credit note, up to AED 5,000 per calendar month |
| 4 | The issuer or the recipient fails to notify its Accredited Service Provider of any change to the data registered with the Federal Tax Authority | AED 250 for each day or part of a day of delay, up to AED 5,000 per calendar month |
Need Expert Advice?
Contact the team at Farahat & Co. for professional support and expert insights for businesses operating in the UAE.
What changed from Cabinet Decision 106 of 2025?
Decision 106 of 2025 listed six violations. Three of them carried open-ended fines with no ceiling. Decision 173 of 2026 removes two violations, caps every remaining one and widens the implementation fine to cover recipients.
| Obligation | Cabinet Decision 106 of 2025 (repealed) | Cabinet Decision 173 of 2026 |
|---|---|---|
| Failing to implement the system or appoint an ASP | Issuer only. AED 5,000 per month of delay, no cap | Issuer or recipient. AED 5,000 plus AED 5,000 per month, capped at AED 50,000 in 12 months |
| Recipient not maintaining its obligations after implementation | Not a separate violation | New violation, under the same AED 50,000 cap |
| Electronic invoice not issued and sent | AED 100 each, max AED 5,000 per month | No change |
| Electronic credit note not issued and sent | AED 100 each, max AED 5,000 per month | No change |
| Issuer not notifying the FTA of a system failure | AED 1,000 per day, no cap | Removed |
| Recipient not notifying the FTA of a system failure | AED 1,000 per day, no cap | Removed |
| Not notifying the ASP of a change to registered data | AED 1,000 per day, no cap | AED 250 per day, max AED 5,000 per month |
| Same person liable as both issuer and recipient | Not addressed | One penalty only |
The net effect is a lighter regime with a wider reach. The amounts are lower and predictable. But a business that only buys can no longer assume e-invoicing is its suppliers’ problem.
How does the AED 50,000 cap on e-invoicing fines work?
The cap applies only to violation 1, which covers failing to implement the system and a recipient failing to keep up its obligations. It does not limit the other three violations.
- It runs over any 12 consecutive months. It is not a calendar-year cap and not a lifetime cap. A business that stays non-compliant into a new 12-month window is exposed again.
- It covers 1(a) and 1(b) together. A business cannot be fined AED 50,000 under each.
- Invoice, credit note and data-change fines sit outside it. Each of those has its own AED 5,000 per calendar month ceiling.
On the monthly rate, 12 months without implementing the system would come to AED 60,000 (AED 5,000 for the first violation plus 11 months at AED 5,000). The cap holds it at AED 50,000. Under the repealed decision the same 12 months cost AED 60,000 and kept growing.
Can the recipient of an e-invoice be fined?
Yes. Under Decision 173 of 2026, a recipient can be fined in three ways:
- Not implementing the system (1(a)). A business in scope that receives invoices but has not appointed an ASP or gone live is in breach, even if all of its suppliers are compliant.
- Not maintaining its recipient obligations (1(b)). Going live once is not enough. The recipient must keep meeting its obligations under Ministerial Decision No. 243 of 2025.
- Not updating its ASP (violation 4). If the data registered with the FTA changes, the recipient must tell its ASP. Late notice costs AED 250 per day.
Article 3 adds one protection. If the same person holds both roles, issuer and recipient, for the same violation, only one penalty is imposed. A trading company that both buys and sells and has not implemented the system faces one violation 1 fine, not two.
Expert note, Farahat Tax Team: The most common gap we see in readiness reviews is on the purchasing side. Finance teams map their sales invoices to the new data fields and forget that their own accounts payable process has to receive structured e-invoices through an ASP. Under Decision 173, that gap now carries its own fine.
What happens if a business missed the 30 October 2026 ASP deadline?
Ministerial Decision No. 66 of 2026 moved the ASP deadline for businesses with revenue of AED 50 million or more to 30 October 2026. The go-live date for the same group stayed at 1 January 2027. Failing to appoint an ASP falls squarely within violation 1(a).
Decision 173 of 2026 applies from the day after its publication in the Official Gazette. It contains no transitional rule for failures that began before that date. A business that missed 30 October should not wait to see how the FTA applies the timing. The monthly fine runs for every month or part of a month that the failure continues, so each month of delay adds to the exposure.
The practical sequence for a late business is:
- Choose and appoint an ASP from the Ministry of Finance’s list of accredited providers.
- Map invoice and credit note data from the ERP to the required e-invoice fields.
- Set up the receiving side, so purchase invoices arrive and are processed through the ASP.
- Confirm the data registered with the FTA is current and passed to the ASP.
- Test end to end before 1 January 2027.
For the full timeline by business group, see our guide to the e-invoicing deadlines under Ministerial Decision No. 66 of 2026.
UAE e-invoicing deadlines by business group
| Group | Appoint an ASP by | Implement by |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities | 31 March 2027 | 1 October 2027 |
Businesses below the AED 50 million line have time, but not much. An ASP selection and ERP mapping project usually takes several months. If you want an outside view of where your business stands, our UAE e-invoicing advisory team runs readiness reviews against the Ministerial Decisions.
Worked examples of e-invoicing penalties in AED
Example 1: No ASP for a full year
A distribution company with AED 80 million revenue does not appoint an ASP and does not go live. On the monthly rate, 12 months comes to AED 60,000. The cap limits violation 1 to AED 50,000 for that 12-month window.
Example 2: Invoices not sent through the system
A contractor goes live but its billing team keeps sending 300 invoices a month by PDF email. At AED 100 per invoice that is AED 30,000, but the monthly ceiling applies. The fine is AED 5,000 for that month. If the same happens for six months, the exposure is AED 30,000, and credit notes are fined separately on top.
Example 3: Late notice of a data change
A business changes its registered address with the FTA and tells its ASP 30 days later. At AED 250 per day, that is AED 7,500. The monthly ceiling holds it at AED 5,000. Under the repealed decision the same delay cost AED 30,000.
Expert note, Farahat Tax Team: The caps make the fines predictable, but they are not a budget line. A business that stays non-compliant pays the capped fine every 12 months and still cannot issue valid invoices through the system. The fines also cover e-invoicing obligations only. Any penalty under the VAT legislation for the underlying tax invoice is a separate matter.
Who is outside the scope of the e-invoicing penalties?
Article 2 excludes any person who issues, sends, shares, exchanges or reports electronic invoices and electronic credit notes voluntarily, under the decisions issued under Federal Decree-Law No. 28 of 2022. A business that adopts e-invoicing early, before its mandatory date, is not penalised under Decision 173 for that voluntary use.
Once a business’s mandatory date arrives, the exclusion no longer helps. From that point it is a person in scope and every violation in the table applies.
What should finance teams do now?
- Check which group you are in. Revenue of AED 50 million or more means the ASP deadline has passed.
- Treat the receiving side as its own project. Recipients are now directly liable.
- Assign an owner for FTA data changes. Every change to registered data must reach the ASP. Late notice is fined daily.
- Stop parallel PDF invoicing after go-live. Every invoice and credit note outside the system is a separate AED 100 fine, up to the monthly ceiling.
- Update internal policies that quote Decision 106 of 2025. That decision is repealed.
For a plain explanation of the provider role itself, read what an Accredited Service Provider does in UAE e-invoicing.
Need Expert Advice?
Contact the team at Farahat & Co. for professional support and expert insights for businesses operating in the UAE.
