Short answer. Cabinet Decision No. 173 of 2026 caps one e-invoicing fine: failing to implement the system, which tops out at AED 50,000 over any twelve consecutive months. The per-document fines stay as they were. Each invoice or credit note you fail to send through the system costs AED 100, up to AED 5,000 a month for each kind. Being late to connect now has a known price. Connecting badly does not.
The headline everyone ran on 30 October was that the UAE capped e-invoicing fines at AED 50,000. Read the table annexed to the decision, and you will find four lines, and the cap sits on one of them. The fine for each late invoice has no annual cap, and over a year it can reach AED 60,000. That is more than the fine everyone called capped.
The provider in all of this is an Accredited Service Provider, a company the Ministry of Finance licenses to carry your e-invoices to the buyer and the tax authority. Say you run a company under AED 50 million in revenue, and you wonder if choosing one can wait until March. Then plan around the line that keeps counting after you connect.
What did Decision 173 change?
It put a ceiling on the implementation fine, deleted the fine for not reporting a system failure, and cut the fine for not updating your provider. The two fines per document stayed the same.
Decision 173 repeals and replaces Cabinet Decision No. 106 of 2025. The Ministry of Finance announced the old one on 8 December 2025, so the comparison is clean.
| № | What was violated | Decision 106 of 2025 | Decision 173 of 2026 | Limit now |
|---|---|---|---|---|
| 1 | Not implementing the system, including not appointing a provider | AED 5,000 a month | AED 5,000, then AED 5,000 a month | AED 50,000 in any 12 consecutive months |
| 2 | An e-invoice not issued and sent through the system | AED 100 each | AED 100 each | AED 5,000 a calendar month |
| 3 | An e-credit note not issued and sent | AED 100 each | AED 100 each | AED 5,000 a calendar month |
| 4 | Not telling your provider about changes to data held by the FTA | AED 1,000 a day | AED 250 a day | AED 5,000 a calendar month |
| Gone | Not reporting a system failure to the FTA | AED 1,000 a day | Removed | None |
Line 4 is worth a second look, because the coverage missed it. Gulf News wrote that the ministry's announcement did not identify changes to that fine. The decision's own table sets it at AED 250 a day with a monthly ceiling, a quarter of the old rate.
The system failure line went because the concept went. Ministerial Decision No. 197 of 2026, published by the ministry on 19 October, deleted the definition of "System Failure" from the main e-invoicing decision and repealed its Article 12 outright.
What does the AED 50,000 cap cover?
Line 1 and nothing else: not implementing the system on time, and a recipient that implemented and then stopped meeting its obligations.
"AED 5,000 for the first instance in which the Issuer or Recipient commits the violation provided for in Paragraph (a) or Paragraph (b), or both; and AED 5,000 for each month or part thereof during which non-compliance continues following the commission of the violation provided for in Paragraph (a) or Paragraph (b), or both; provided that the total fines imposed do not exceed AED 50,000 within any period of (12) twelve consecutive months."
Under Decision 106, a business that stayed unconnected for a year could run up AED 60,000. Under Decision 173 the same year stops at AED 50,000. The government did not cut the monthly rate. It put a lid on how far it can climb.
Now do the same arithmetic on line 2. Say you are connected but keep sending invoices late. You can reach AED 5,000 every month, which makes AED 60,000 over twelve months, and no annual ceiling applies. Line 3 runs the same way for credit notes. On its own, line 2 can cost more in a year than the line everyone called capped.
The decision does not answer one question, so I will not answer it either. Do lines 1 and 2 apply to the same company in the same month? Article 3.2 answers a smaller question. If your company sent the invoice and also received it, and one violation covers both sides, you pay one fine. Beyond that, ask your tax adviser before you build a plan on stacking or on its absence.
Which deadlines apply under AED 50 million?
Appoint a provider by 31 March 2027 and go live on 1 July 2027. Those dates come from Ministerial Decision No. 244 of 2025, as the Ministry of Finance announced it on 29 September 2025.
| Who | Appoint a provider by | Go live |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue under AED 50 million | 31 March 2027 | 1 July 2027 |
| Government entities in scope | 31 March 2027 | 1 October 2027 |
The first row moved once already. Ministerial Decision No. 66 of 2026 pushed the appointment deadline for large businesses from 31 July to 30 October 2026, and left 1 January 2027 where it was. If you are in that row and have not appointed, you have been exposed to line 1 since 31 October.
Three details change who is in scope and when:
- Recipients appoint too. The ministry's own summary says issuers and recipients both appoint a provider, and recipients process every e-invoice through the system. A company that mostly buys still has a deadline.
- Tax groups get a pause. Decision 197 excludes transactions between members of the same VAT tax group for 24 months starting 1 January 2027.
- Volunteers are outside the penalties. Article 2.2 of Decision 173 exempts anyone issuing e-invoices voluntarily, before they are obliged to.
Where does the risk sit once you are connected?
In two places: the fourteen business days you have to issue each invoice, and every invoice that leaves your business some other way.
"The Electronic Invoice or Electronic Credit Note referred to under Clauses 1 and 2 of this Article, must be issued and transmitted by the Issuer through the Electronic Invoicing System within fourteen (14) Business Days from the Date of Business Transaction."
That text comes from Decision 197, which rewrote the clause. I have not compared it with the first version of Decision 243, so I am not telling you the window got longer or shorter. Fourteen business days is the rule you plan against now.
Your provider carries the document. What goes in it, and when it is created, is yours. In a typical small company, late invoices come from a handful of familiar places. Treat this list as a checklist to test, not data from the FTA:
- an invoice raised in a second system, a CRM or a project tool, and keyed into accounting after someone approves it
- a monthly retainer billed on the first for work that started mid-month
- a credit note that sales promises on a call and finance issues weeks later
- a branch, or a sister company, still invoicing from its own spreadsheet
Credit notes deserve their own line in your plan, because the law gives them one. The ministry lists when one is required: a cancelled transaction, a reduced price, a full or partial refund, and an administrative or arithmetic error. Every one of those starts somewhere other than the invoicing screen.
The decision also rewrote storage. You keep every e-invoice, credit note and associated data for the period the Tax Procedures Law sets, and you must be able to produce them on request.
What should you check before choosing a provider?
Where your invoices come from, how many of them leave late today, and who issues credit notes. One week with last quarter's history answers all three.
Take the last three months of sales invoices and work through them in order:
- Count the systems. List every place an invoice or credit note is created. Accounting, billing, CRM, a branch spreadsheet. Each one is an integration.
- Measure the lag. For each invoice, compare the transaction date with the date it was issued. Count how many took longer than fourteen business days. That number is your line 2 exposure today.
- Find the credit notes. Who raises them, in which system, and how long after the event. This is the line people forget.
The answers price your connection better than any provider's quote, because they tell you how much work sits on your side of the provider.
I would keep AI out of most of this job. Rules decide every step of sending an invoice. The format follows the OpenPeppol standard, the window and the route are fixed, and each mistake costs AED 100. We wrote about when automation needs no agent, and this is a clear case. A model has one narrow job before go-live. It can read your historical invoices and item lists and propose how your fields map to the required ones, then help sort the queue of rejected documents. A person confirms every mapping. Nothing reaches the FTA because a model guessed.
This is not tax advice, and I am not your adviser. I quoted the decisions so you can take them to one, with the table above and your three numbers.
On an integration project we start with the inventory and the lag. We choose the provider last, because by then you know what it has to connect to.
Danil Ivanov
Founder, KAIVIX
Builds AI systems for companies in the UAE and beyond.