UAE e-invoicing penalties under Cabinet Decision 173 of 2026

What are the UAE e-invoicing penalties today?

Cabinet Decision No. 173 of 2026 sets the administrative penalties for breaking the e-invoicing rules in a table annexed to the decision (Art. 3(1)). The table has the four rows shown above, and the Ministry's Guidelines V2.0 (§11.2) point to this decision for the e-invoicing penalties. The issuer is the person that must issue and send e-invoices and electronic credit notes; the recipient is the person that must receive them through the system (Art. 1).

Row 1 is the one most businesses ask about. It covers two failures: not implementing the system under MD 244/2025, which expressly includes not appointing an accredited service provider; and, for a recipient that has implemented it, not keeping up its obligations as a recipient under MD 243/2025. One of those obligations is to process e-invoices and credit notes through the system (MD 243/2025, Art. 6(3)).

Rows 2 and 3 count documents: each e-invoice or electronic credit note the issuer fails to issue and transmit through the system. Row 4 counts days of delay in telling your ASP about a change to your data registered with the Federal Tax Authority. MD 243/2025 (Art. 5(3)) sets the time for that written notice: five business days from the Authority's confirmation of the change.

Sources: ^[1][4][7]

What changed from Cabinet Decision 106 of 2025?

Cabinet Decision No. 173 of 2026 repeals Cabinet Decision No. 106 of 2025 (Art. 4) and comes into force the day after its publication in the Official Gazette (Art. 5). Row by row:

CD 173/2026 has no penalty for failing to report a system failure, and the duty behind it is gone too. MD 197/2026 deleted the definition of System Failure (Art. 1(3)) and repealed Article 12 of MD 243/2025 (Art. 3), which required issuers and recipients to notify the Federal Tax Authority of a system failure within two business days.

Some articles and older pages still quote CD 106/2025. Check which decision a figure comes from before you rely on it.

Sources: ^[1][2][3][4]

Is there a cap on e-invoicing penalties?

Yes, on every row. Row 1 stops at AED 50,000 within any period of 12 consecutive months. Rows 2 and 3 are each capped at AED 5,000 per calendar month, so a month with both missing e-invoices and missing credit notes can reach AED 10,000 under these two rows. Row 4 is capped at AED 5,000 per calendar month. CD 106/2025 stated no cap for its first row or for any of its per-day rows.

These caps are for the e-invoicing penalties only; other tax penalties are separate (see below).

Sources: ^[1][2]

When do penalties start for my business?

From your mandatory date, not before. The Guidelines V2.0 (§8.2) say administrative penalties apply only from the date a person must implement e-invoicing on a mandatory basis, and CD 173/2026 (Art. 2(2)) excepts anyone who issues, sends or reports e-invoices voluntarily. Your mandatory date depends on your group: see the deadlines page.

One question is open. Row 1 names the failure to appoint an accredited service provider, and for revenue of AED 50 million or more the appointment date was 30 October 2026, while the go-live date is 1 January 2027 (MD 244/2025, Art. 5(1)(a), as amended by MD 66/2026). Neither CD 173/2026 nor the Guidelines say whether a business that missed 30 October is exposed from 31 October 2026 or only from 1 January 2027. Ask your ASP or tax adviser, and appoint a provider now either way.

We do not print the date CD 173/2026 itself took effect. The English PDF on the Ministry of Finance website leaves the issue date blank, and the decision comes into force the day after its publication in the Official Gazette (Art. 5), a date we have not verified.

Sources: ^[7][1][5][6]

We are both issuer and recipient. Can we be fined twice?

Not for the same violation. If the same person acts as an issuer, a recipient or both in respect of the same violation, only one administrative penalty for that violation is imposed on it (CD 173/2026, Art. 3(2)). This matters for row 1, which covers issuers and recipients, and for row 4, where both must keep their ASP informed. CD 106/2025 had no such rule.

Sources: ^[1][2]

Are these the only penalties that can apply?

No. The Guidelines V2.0 (§11.1) note that administrative penalties under the tax laws can also apply where tax invoicing obligations are not met, for example failing to issue or keep compliant tax invoices under the VAT law and the Tax Procedures Law. Those penalties are in Cabinet Decision No. 40 of 2017 and its amendments, not in CD 173/2026. This page covers only the e-invoicing penalties.

Sources: ^[7]

How do the amounts add up? A worked example

Example, with invented figures: a business whose mandatory date has passed. In one calendar month it fails to issue and transmit 32 e-invoices and 3 electronic credit notes, and it tells its ASP about a changed address 4 days late.

This shows only the arithmetic of the annexed table. How the Federal Tax Authority counts documents, days and months in a real case is for the Authority, and these figures are not an estimate of what any business owes.

• Row 2: 32 × AED 100 = AED 3,200, below the AED 5,000 monthly cap.
• Row 3: 3 × AED 100 = AED 300.
• Row 4: 4 days × AED 250 = AED 1,000.
• Total for that month: AED 4,500.
• With 70 missing e-invoices instead of 32, row 2 would stop at the AED 5,000 cap, not AED 7,000.
• Row 1, for a business that had not implemented the system at all: AED 5,000 for the first instance, then AED 5,000 for each month or part of a month it continues. After the first instance and nine more months the total reaches AED 50,000, the cap for any 12 consecutive months.

Sources: ^[1]

How do we avoid e-invoicing penalties?

Each step below answers one row of the table.

• Know your group and its two dates, and appoint an ASP from the Ministry's list by the first one (MD 244/2025, Art. 5(1); MD 243/2025, Art. 5(2)).
• Complete onboarding with your ASP and meet the technical requirements before your go-live date (MD 244/2025, Art. 5(3)).
• Send every in-scope invoice as an e-invoice, and issue an electronic credit note when a sale is cancelled, its price is reduced, the consideration is returned in full or in part, or there is an administrative or numerical error (MD 243/2025, Art. 6(2)).
• When your data registered with the Federal Tax Authority changes, tell your ASP in writing within five business days of the Authority's confirmation (MD 243/2025, Art. 5(3)).
• As a buyer, make sure your ASP receives and processes e-invoices for you from your own date (MD 243/2025, Art. 6(3)).

Sources: ^[5][4]

Where Vattora fits, and when you do not need it

Vattora cannot cancel a penalty or act as your ASP: it is connector software, not an accredited service provider. Its part concerns rows 2 and 3: it reads each posted invoice and credit note from your accounting system, checks it against PINT AE, hands it to your ASP and shows the status of every document, so one that was not sent stands out. Vattora connects to the ASP you choose through that provider's API; each link is built and tested in the provider's test environment before your first real invoice. You do not need Vattora if your accounting system or your ASP already sends every invoice and credit note for you.