UAE E-Invoicing Penalties: What CD 173 Really Charges

A finance director in Dubai opened her budgeting spreadsheet last week and typed in a number she had taken from a penalties page: AED 60,000 a year for failing to implement e-invoicing, plus AED 1,000 a day if her system broke down and she was slow to tell the FTA. The numbers looked precise. They were footnoted, tabulated, and repeated in the page's key takeaways. They were also eleven days out of date when she read them, because the decision they were built on had been repealed. Her budget was pricing a corpse.

That is the quiet way a reference page goes wrong. It does not get one figure wrong. It gets its foundation wrong, and every figure underneath it goes with the foundation. The page in question is a major tax platform's e-invoicing penalties guide, published on 24 December 2025 and never updated since. Its headline is its own obituary, printed in the present tense: "Penalties Under UAE e-Invoicing – Cabinet Decision No. 106 of 2025". Cabinet Decision No. 106 of 2025 no longer exists. Cabinet Decision No. 173 of 2026 replaced it, announced on 30 October 2026. The page did not notice, and its readers are still budgeting on a dead decision.

UAE E-Invoicing Penalties: The Page, in Its Own Words

Start with what the page actually says, because the scale of the problem is in the repetition. A single wrong line can be a slip. This page states its dead framework in four places, each time in the present tense, each time as if it were live law.

Its key takeaways promise companies that miss a system-failure notification "will incur a daily penalty of AED 1,000 until notification is made", and that a daily AED 1,000 penalty "will also apply" to late data-change notifications. Present tense, both times. Not "used to apply". Will incur. Will also apply.

Its violations table prices both at AED 1,000 "Per day until notification", and adds the headline figure the page is really selling: "Failing to implement the system entirely can incur AED 60,000 annually". That AED 60,000 is the number a finance team carries into a board paper. It is a full year of uncapped daily fines, added up and presented as the annual exposure.

Then a whole section, "System Failure Notification to the FTA", instructs businesses to report a system failure within two business days, with notification templates and a subject-line format, and prices late notification at "AED 1,000 per day (or part thereof)". A finance team that follows this section builds an incident-response protocol around a duty the October amendments repealed and a fine the replacement decision removed. The templates are ready. The duty is gone.

None of this is a small page. It is a penalties reference from a platform businesses actually use, and its structure is exactly what makes it dangerous: heading, takeaways, table, section, templates. Every layer agrees with every other, so a reader who checks the table against the takeaways finds consistency, and consistency feels like verification. It is not. It is the same dead decision, quoted four times.

What Actually Happened on 30 October 2026

On 30 October 2026, the Ministry of Finance announced a new Cabinet Decision on e-invoicing violations and administrative penalties: Cabinet Decision No. 173 of 2026. It replaces Cabinet Decision No. 106 of 2025, and it repeals it in full, together with any provision that conflicts with it. The new decision enters into force on the day following its publication in the Official Gazette.

The replacement was not a tidy-up. It changed the shape of the penalty regime in three ways that matter to any business budgeting for e-invoicing, and it removed one duty entirely. The old decision's fines were daily and uncapped. The new decision's fines are capped, per violation, per month or per twelve months. The old decision fined you for not telling the FTA your system had broken. The new decision does not fine you for that at all, because the duty to tell them is gone.

The timing matters as much as the content. The announcement landed on 30 October, the same day the Phase 1 ASP appointment deadline fell due for businesses with revenue of AED 50 million or more. Those businesses must now go live on 1 January 2027. The page that still prices the old fines was published ten months before the replacement and has not been touched since.

The Live Penalty Table Under Cabinet Decision No. 173 of 2026

Here is the table as it stands now, under the replacement decision. Every figure below is from the careful accounts' published readings of Cabinet Decision No. 173 of 2026, and each one can be checked against the decision's text on the Ministry of Finance e-invoicing portal.

Failing to implement the system, including failing to appoint an Accredited Service Provider: AED 5,000 for the first instance, plus AED 5,000 for each further month, or part of a month, that non-compliance continues — capped at AED 50,000 in any 12 consecutive months. This is the figure the old page gets most wrong. Its AED 60,000 annual bill was built by running an uncapped daily fine for a full year. The new decision caps the same breach at AED 50,000 in any rolling twelve months. A business budgeting from the old page over-provisions by AED 10,000 a year, and worse, it provisions against a structure — daily, uncapped — that no longer exists, so its monthly accruals are wrong as well as its annual total.

Failing to issue and transmit an e-invoice or e-credit note: AED 100 per document, capped at AED 5,000 per calendar month. This is the per-document fine the old page never priced, because the old framework's headline was the daily failure-to-notify fine. Under the new decision, the invoice itself carries the fine, per document, with a monthly ceiling. A business that issues a hundred non-compliant invoices in a month does not pay a hundred fines. It pays AED 5,000.

Failing to notify your Accredited Service Provider of changes to data registered with the FTA: AED 250 per day, capped at AED 5,000 per calendar month. The old page priced this at AED 1,000 a day with no cap. The new decision cuts the daily rate to a quarter and caps the month at AED 5,000. A data change left unreported for twenty days costs AED 5,000 under the new decision. The old page would have priced it at AED 20,000.

Failing to notify the FTA of a system failure: no fine at all. The old decision's AED 1,000-a-day system-failure notification fine was removed entirely by the replacement decision. The duty to report the failure within two business days, with its templates and its subject-line format, is gone with it. A business that still runs that protocol is spending staff time and building escalation chains around a notification nobody is waiting for.

Read the four rows together and the shape of the change is clear. The new regime is narrower, capped, and per-document where the old one was daily and open-ended. The old page's numbers are not slightly out of date. They describe a different penalty system, one that stopped existing on 30 October.

What Budgeting From the Old Page Actually Costs

The cost of a stale penalties page is not the embarrassment of quoting the wrong number in a meeting. It is the money and the decisions that follow the number, and both run in directions the reader never sees.

First, the provision. A finance team that budgets AED 60,000 a year for a bill now capped at AED 50,000 has AED 10,000 sitting in a provision that will never be called. The larger cost is the monthly shape: a team accruing AED 1,000 a day for a system failure will show a growing liability every day the system is down, and will escalate the incident as a financial event. Under the new decision there is no such liability at all.

Second, the incident protocol. The old page's two-business-day notification section, with its templates and subject line, is the kind of thing a compliance officer turns into a runbook. Runbooks survive. They get pasted into onboarding packs, printed on the wall of the finance room, and followed at 2 a.m. when a system actually breaks. A runbook built on a repealed duty does not just waste the two hours spent writing the notification. It trains the team to treat the FTA as the first call when a system fails, instead of treating the Accredited Service Provider and the fix as the first call. The new regime's first call is the provider, not the regulator.

Third, the board paper. A penalties page that prices AED 60,000 annually is the kind of number that gets a project approved, a budget signed, and a timeline compressed. A board that approves an e-invoicing budget on the old figures is approving the wrong project. The new decision's caps make the worst case smaller and the per-document fines make it more predictable. A business that knows the real ceiling can spend the difference on the implementation itself, instead of on a provision for a fine that will never arrive.

How to Check Any E-Invoicing Penalties Page Before You Budget From It

Here is the working method we use with clients when an e-invoicing provision or a board paper is being built on a page someone found online. It takes one sitting, and it catches more than the dead decision.

First, read the decision number in the headline, then look it up. A penalties page that names its decision is a page that can be checked in seconds. Cabinet Decision No. 106 of 2025 is repealed. Cabinet Decision No. 173 of 2026 is the live penalty source, announced 30 October 2026, in force from the day after its publication in the Official Gazette. Any page whose headline, takeaways or table still cite Decision 106 is a page to quarantine, not a page to budget from. Our analysis of the VAT penalty ladder that died in April shows the same habit on the VAT side: a penalty table that outlives the decision it was built on, and a business that pays for the gap.

Second, check the publication date against the Ministry's announcements. A page published in December 2025 cannot describe a decision announced in October 2026. That sounds obvious, and it is, which is why it gets missed: the page looks current because it is well written, well formatted, and ranks well. None of those things is a date. If the page's last update predates 30 October 2026, treat every penalty figure on it as unverified until you have checked it against the Ministry of Finance e-invoicing portal.

Third, check the caps. The new decision's signature is the cap: AED 50,000 in any 12 consecutive months on the implementation fine, AED 5,000 per calendar month on the per-document and data-change fines. A page that prices an e-invoicing fine as a daily amount with no cap is a page built on the old decision, whatever its update stamp says. The cap is the fingerprint. Look for it first.

Fourth, diarise the live timetable, not the page's countdown. Phase 1 businesses, 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. Phase 2 businesses appoint by 31 March 2027 and go live on 1 July 2027. Penalties apply from your mandatory date, and voluntary adopters are protected in the pilot phase. Our e-invoicing delivery analysis walks through what your ERP can and cannot do on that timetable: the system that generates your invoices is not the system that delivers them, and the penalties attach to delivery, not generation. Our VAT daily-meter analysis covers the same pattern on the VAT side, where a AED 1-a-day meter kept running in guides long after the schedule that created it was replaced.

Do those four steps and a dead decision has nowhere to hide. Either the page names Cabinet Decision No. 173 of 2026 and prices the capped table, or the page comes off your budget.

The Bottom Line

The decision this page is built on died eleven days ago. The page did not notice, and its readers are still budgeting on a corpse. Cabinet Decision No. 173 of 2026 repealed Cabinet Decision No. 106 of 2025 in full: the implementation fine is now AED 5,000 for the first instance plus AED 5,000 a month, capped at AED 50,000 in any twelve consecutive months; the per-invoice fine is AED 100 a document, capped at AED 5,000 a month; the data-change fine is AED 250 a day, capped at AED 5,000 a month; and the AED 1,000-a-day system-failure notification fine is gone entirely, with the duty it punished. A business that budgets AED 60,000 a year and builds a two-business-day notification protocol from the old page is provisioning for a bill that will never arrive and staffing a duty that no longer exists.

Check the decision number in the headline before you check the figures underneath it. A penalties page is only as live as the decision it cites, and this one's decision died on 30 October. If you want your e-invoicing exposure priced on the live table — the capped implementation fine, the per-document fines, the real go-live dates for your revenue band — with the ASP appointment and the delivery setup handled before 1 January 2027, that is exactly the work our VAT and FTA compliance service is built for. Escrow is led by a Chartered Accountant (UAECA, CPA and FCCA). Book a consultation at escrowconsultinggroup.com and bring the penalties page. We will start with the decision number in its headline.

Sources and honesty note: the "Penalties Under UAE e-Invoicing – Cabinet Decision No. 106 of 2025" heading, the "will incur a daily penalty of AED 1,000 until notification is made" and "A daily penalty of AED 1,000 will also apply" key takeaways, the "Per day until notification" table entries, the "Failing to implement the system entirely can incur AED 60,000 annually" figure, and the "System Failure Notification to the FTA" section instructing reporting "within two business days of occurrence" are one named platform's published positions, quoted from its e-invoicing penalties page published 24 December 2025. The replacement position is the named careful accounts' published reading of Cabinet Decision No. 173 of 2026, announced 30 October 2026, and of the Ministry of Finance's e-invoicing guidelines. The corporate tax and VAT positions are the Federal Tax Authority's own framework, published at tax.gov.ae. This post does not tell any named business its penalty exposure. Check your own position against the replacement decision's text in the Official Gazette, the Ministry of Finance e-invoicing portal, and your own Accredited Service Provider appointment record.