E-Invoicing Penalties UAE: The Deleted Fine Still Listed

A finance director in Dubai sent us a penalty table on Monday. Her team was pricing e-invoicing risk two days before the ASP appointment deadline, and the table looked official enough to budget from. Six rows, neat numbers, a Cabinet Decision cited at the top. Two of those rows charged AED 1,000 a day for failing to tell the Federal Tax Authority about a system failure. One problem. The duty behind those two rows was deleted on 1 October. The Ministry of Finance repealed it, announced the repeal, and removed the article that created it. Her table had not noticed. Neither have most of the tables still circulating this week, which is why e-invoicing penalties UAE searches right now lead finance teams to at least three different versions of what failure costs.

This post reads those tables against each other and against the decisions themselves. One set of guides is still selling a fine for silence after the duty to speak was repealed. One widely read guide invents figures that appear in no decision at all. And underneath the noise sits a short, real table that is much smaller than either version suggests. If your business appoints its Accredited Service Provider by Friday 30 October, the table you budget from matters more than the table you found first.

E-Invoicing Penalties UAE: The Six Rows Everyone Copies

Start with the table the careful accounts agree on, because it is the baseline everything else drifts away from. Cabinet Decision No. 106 of 2025 sets six administrative penalties for the e-invoicing system, as summarised by EY and reproduced in a widely read deadline guide updated this month. Failing to implement the system or appoint an ASP on time costs AED 5,000 for each month, or part of a month, of delay. Failing to issue and transmit an e-invoice costs AED 100 per invoice, capped at AED 5,000 in a calendar month. Failing to issue and transmit an e-credit note costs the same, AED 100 per note, capped separately at AED 5,000 a month. Then come three daily rows at AED 1,000 per day: an issuer not notifying the FTA of a system failure, a recipient not notifying the FTA of a system failure, and a business not telling its ASP about changes to its registered data.

Read that table once and a pattern jumps out. The per-document exposure is deliberately small and capped. A business that mishandles a hundred invoices in its first live month faces AED 5,000 on that row, not a six-figure shock. The serious money in the real table is in delay and in silence: months of missed appointment at AED 5,000 each, and days of unreported problems at AED 1,000 each. That design tells you what the system actually wants. It wants you appointed, transmitting, and talking to your provider. It is not trying to bankrupt anyone over a malformed invoice file.

Hold that baseline in mind. It is the version supported by the decision the guides themselves cite, and it is the version a business should provision against, subject to the one large question the next section opens.

The Duty Was Deleted on 1 October. The Fine Stayed in the Tables.

On 19 October, the Ministry of Finance announced Ministerial Decision No. 197 of 2026, amending Ministerial Decision No. 243 of 2025 with effect from 1 October. Among its three changes, the Ministry's own announcement states plainly that the decision removes the provisions relating to system failure, including the requirement to notify the FTA of a system failure within two business days, through the repeal of Article 12 and the deletion of the related definition. There is no longer a two-day clock. There is no longer a notification to miss.

Now go back to the tables in circulation this week. The deadline guide above, updated days ago, still prints rows four and five exactly as they stood before the repeal: AED 1,000 per day for an issuer, and separately for a recipient, not notifying the FTA of a system failure. An audit firm's regulations guide, crawled within the last day, still lists AED 1,000 per day for failing to notify the FTA of a system malfunction within the required timeframe, with no mention that the timeframe no longer exists. A major platform's penalty page still builds its downtime preparation around notifying the FTA within the two-business-day limit. Another penalties round-up prices an unreported failure at AED 1,000 per day and calls the exposure unlimited. A business following those pages in good faith would this week be writing an outage procedure, drafting notification templates, and training staff to meet a deadline the Ministry deleted almost four weeks ago.

An orphaned penalty is a question, not a number

Here is where we slow down, because precision matters more than drama. The repeal removed the notification duty in the system rules. The penalty table lives in a different decision, Cabinet Decision No. 106 of 2025, and the careful recent accounts are honest about the gap. One readiness guide that did notice the repeal prints the shorter table, notes that the original decision also set fines for failing to report a system failure, states that Ministerial Decision No. 197 repealed that requirement, and then tells readers to ask their adviser how this affects the related penalties before relying on it. A detailed provider guide goes a step further and notes that the Ministry has not said the penalty text itself was amended. In other words, the duty is gone, the penalty wording may still sit in the older decision, and no public account we found settles whether that wording could still be applied to a duty that no longer exists.

We are not going to settle it in a blog post, and you should be suspicious of anyone who does. What we can say is practical. A penalty for failing to perform a repealed duty is, at minimum, an open question that deserves advice before it deserves a budget line. A business that provisions AED 1,000 a day, uncapped, for a notification nobody is owed may be over-reserving against a phantom. A business that deletes its incident logging altogether because the FTA notification died would be making the opposite mistake: operational records, supplier escalation and evidence of what failed and when remain sensible controls, and other obligations in the system still run. The repeal killed a filing. It did not kill the need to know your system broke.

E-Invoicing Penalties UAE: The Figures That Exist Nowhere

If the orphaned rows are a lag problem, the next set is worse. A current B2B VAT guide from a well-known spend platform, updated this month, publishes a top-seven penalties list that many finance teams will land on this week. In that list, e-invoice failure is priced at AED 10,000 for non-issuance and AED 20,000 for validation errors. Search the real table for either figure. They are not there. Cabinet Decision No. 106 of 2025, on every careful account, prices a missing e-invoice at AED 100, capped monthly. There is no AED 20,000 validation-error penalty in the six rows at all. The invented figure is two hundred times the real per-document rate, presented without the cap that defines the real one.

The same list prices late VAT payment at 2 percent a month, capped at 100 percent of the amount due. That is a description of an older regime. The late-payment position current accounts state is interest at 14 percent per annum on unpaid tax. A reader budgeting from that one page would overstate e-invoicing exposure by multiples, understate nothing, and walk into an ASP negotiation believing the cost of a formatting error rivals the cost of missing the appointment itself. It does not. On the real table, missing the appointment for a month costs fifty times a single failed invoice, and the failed invoice row caps out no matter how many documents fail.

Why does this matter beyond embarrassment? Because penalty tables drive real decisions in deadline week. They set provisions in the month-end close. They shape the risk slide in the board pack. They decide how much a business will pay an ASP for indemnities and service credits, and how hard it negotiates clauses about outages. Price the risk from an invented table and every one of those decisions is distorted in the same direction: too much fear spent on document errors, too little attention on the appointment and data duties that carry the real daily and monthly rates. It is the same discipline we applied last week to the 100 free invoices that turned out to be three different allowances: a number repeated confidently across sales pages is not a number verified against its source.

The One Daily Fine That Definitely Survived

Buried in the argument about the deleted rows is the daily penalty nobody should lose sight of. The sixth row of the real table, AED 1,000 per day for not telling your ASP about changes to your registered data, was not touched by the October amendments. The duty it attaches to is alive: when data registered with the Authority changes, your provider has to hear about it, promptly, because the provider transmits and validates against that data. A licence renewal, a changed trade name, a new address, a revised registration detail that reaches your ASP late is a live daily exposure, not an orphaned one.

This is where a monthly close earns its keep. Registered-data changes usually surface inside ordinary bookkeeping events: a renewed licence lands in the inbox, an amended memorandum is filed, a bank mandate is updated. If those documents move through the business without anyone asking whether the ASP record still matches, the gap opens quietly and the daily rate runs quietly. Our monthly bookkeeping work treats the ASP record as one more reconciliation: licence, registration and address details agreed to the provider's file at each close, differences notified the same week. It sits comfortably alongside the wider record discipline we set out in how long each class of UAE tax record has to be kept, and the supplier-data checks in why your bookkeeping app cannot verify your suppliers for you.

What to do with your outage procedure now

Do not bin it. Rewrite it. The version built from the stale tables has your team racing to notify the FTA inside two business days. The version the current rules support looks different: detect the failure, log it with timestamps, escalate to your ASP, preserve the evidence trail, and keep issuing through whatever fallback your contract provides, because the per-document rows for invoices you fail to issue and transmit are very much alive. The audience for your incident record changed on 1 October. It is now your provider, your auditor and your own file, rather than a two-day FTA notification. And keep the timing rules separate in your head: as we explained in the two-clocks problem, the e-invoicing transmission window and the VAT tax-invoice deadline are not the same clock, and an outage does not pause either of them automatically.

Price Your Exposure From the Decision, Not the Round-Up

Two days before the appointment deadline, here is the working method we use with clients, and it takes less time than reading three conflicting guides.

• Start from the decision, not the summary: build your exposure table from Cabinet Decision No. 106 of 2025 as the careful accounts print it, six rows, with caps shown. Any figure that cannot be traced to a row does not enter the provision.
• Mark the orphaned rows as a question: show the two system-failure rows separately, flagged as attached to a duty repealed by Ministerial Decision No. 197 of 2026, with advice taken on the point. Do not present them to a board as either certainly payable or certainly dead.
• Delete invented figures on sight: AED 10,000 for non-issuance and AED 20,000 for validation errors appear in no decision table we can find. If a provider or guide quotes them, ask for the article. The conversation that follows is usually short.
• Protect the live daily duty: diarise registered-data changes to your ASP as a standing close task. That AED 1,000-a-day row survived October intact.
• Rewrite the outage SOP: notification templates for the FTA come out; detection, logging, ASP escalation and evidence retention stay in.
• Price the commercial risk honestly: the sharper guides make a point worth repeating: the bigger cost of a failed e-invoice may be a customer whose system accepts only compliant documents delaying your payment. That risk never appears in a penalty table, and for many businesses it is larger than every capped row combined. It belongs in the cash forecast, which is where our CFO advisory work puts it.

An honesty note to close, in the same spirit as the rest of this post. Every figure above is presented as its source states it: the six-row table as Cabinet Decision No. 106 of 2025 accounts print it, the repeal as the Ministry announced it, the open question about the orphaned penalty rows as the careful guides leave it, and the AED 10,000 and AED 20,000 figures strictly as one guide's list, against the decision. Nothing here asserts what the FTA would assess in any individual case. Penalty application depends on your phase, your dates and your facts.

But the headline habit is safe to adopt today. The fine for silence died with the duty to speak, and half the internet is still selling both. Before Friday, let Escrow rebuild your e-invoicing exposure from the current decisions: the real table, the orphaned rows flagged for advice, your ASP contract clauses tested against the repealed duty, and the live data-change duty diarised inside your monthly close. Start with a free VAT compliance health check at escrowconsultinggroup.com, and bring the penalty table your team is currently budgeting from. The first thing we will do is cross out two of its rows.