Cabinet Decision No. 173 of 2026 replaces the earlier UAE e-invoicing penalty framework. The revised schedule covers implementation and ASP appointment failures, invoice and credit-note transmission, and certain delays in notifying the appointed service provider of registered-data changes.
Cabinet Decision No. 173 of 2026 replaces the earlier UAE e-invoicing penalty framework. It covers implementation and ASP appointment failures, failures to transmit electronic invoices and credit notes, and delays in notifying the appointed ASP of certain registered-data changes.
The decision does not postpone the phased implementation timetable. Finance teams should confirm their applicable phase, document the ASP appointment, review invoice data and test both outgoing and incoming e-invoicing processes.
The UAE has replaced its earlier electronic invoicing penalty framework.
On 30 October 2026, the Ministry of Finance announced Cabinet Decision No. 173 of 2026, which repeals Cabinet Decision No. 106 of 2025. The revised schedule covers failure to implement the Electronic Invoicing System or appoint an Accredited Service Provider, failure to transmit electronic invoices and credit notes, and failure to notify the appointed service provider of certain changes to information registered with the tax authority.
For businesses in the first mandatory phase, the Accredited Service Provider appointment deadline was 30 October 2026, while mandatory implementation begins on 1 January 2027. Other businesses within scope generally have later implementation dates.
The new penalty decision does not change those implementation deadlines.
For finance teams, the immediate priority should therefore be practical: confirm which phase applies to the business, document the ASP appointment, review the underlying invoice data and test both outgoing and incoming e-invoicing processes.
Cabinet Decision No. 173 of 2026 identifies four main violation categories.
The amounts below come from the official decision and are not estimates by EMARK.
| Violation | Administrative penalty |
|---|---|
| Failure by an issuer or recipient to implement the Electronic Invoicing System as required, including failure to appoint an Accredited Service Provider; or failure by a recipient to continue meeting the applicable obligations after implementation | AED 5,000 for the initial violation, plus AED 5,000 for each month or part of a month that the non-compliance continues. Maximum AED 50,000 within any 12 consecutive months for this category. |
| Failure by an issuer to issue and transmit an electronic invoice through the system | AED 100 per electronic invoice, subject to a maximum of AED 5,000 per calendar month. |
| Failure by an issuer to issue and transmit an electronic credit note through the system | AED 100 per electronic credit note, subject to a maximum of AED 5,000 per calendar month. |
| Failure by an issuer or recipient to notify its appointed Accredited Service Provider of changes to data registered with the Authority | AED 250 for each day of delay or part of a day, subject to a maximum of AED 5,000 per calendar month. |
One distinction is particularly important.
The AED 50,000 ceiling applies to the first implementation-related violation category over a twelve-month period. It should not be read as a general AED 50,000 cap covering every e-invoicing violation.
Electronic invoice, electronic credit note and ASP data-change violations have their own monthly limits.
The previous administrative penalty schedule was issued under Cabinet Decision No. 106 of 2025.
Cabinet Decision No. 173 of 2026 expressly repeals that earlier decision.
This matters because businesses may still have internal implementation documents, adviser notes or online checklists referring to the older framework.
Three areas deserve particular attention.
The revised penalty schedule expressly refers to both issuers and recipients.
It also addresses the situation where a recipient implements the Electronic Invoicing System but subsequently fails to maintain the obligations applicable to recipients.
For many businesses, the e-invoicing project may initially be approached as an accounts-receivable or sales-invoicing exercise.
That would be too narrow.
Finance teams should also look closely at their accounts-payable process.
Practical questions include:
These are practical control questions rather than separate statutory requirements. They help a business understand whether its process is actually ready to operate.
A company should be able to demonstrate how an electronic invoice moves through its own finance workflow—not merely state that its software provider has enabled e-invoicing.
The revised penalty schedule no longer contains the previous penalty relating to failure to notify the Federal Tax Authority of a defined system failure.
This follows Ministerial Decision No. 197 of 2026, which repealed the earlier system-failure notification provision.
That does not mean businesses should stop managing system failures.
A failed transmission can still create practical problems.
For example:
Businesses should therefore maintain an internal incident process covering unsuccessful transmissions and recovery.
The procedure could record:
This is an operational control recommendation, not a continuation of the repealed two-business-day FTA notification requirement.
This point requires careful wording.
Article 5 of Cabinet Decision No. 173 of 2026 states that the decision becomes effective on the day following its publication in the Official Gazette.
The Ministry of Finance announced the decision publicly on 30 October 2026.
However, the date of the Ministry’s announcement should not automatically be treated as the legal commencement date.
As of the regulatory review for this article on 4 November 2026, the relevant Official Gazette publication date had not been independently confirmed for this article.
Businesses dealing with a possible violation around the transition between the old and new penalty frameworks should therefore verify:
A missed regulatory deadline does not, by itself, tell a business the exact administrative penalty that will ultimately apply.
That assessment depends on the applicable legislation and the actual facts.
The penalty decision does not replace the UAE’s phased e-invoicing implementation timetable.
For businesses within scope, the applicable phase remains important.
| In-scope category | Deadline to appoint an Accredited Service Provider | Mandatory implementation |
|---|---|---|
| Revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| Revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| In-scope government entities | 31 March 2027 | 1 October 2027 |
The first-phase ASP appointment deadline has therefore already passed.
Businesses subject to that phase should not treat 1 January 2027 as the first date on which they need to take action.
Provider appointment, onboarding, accounting-system configuration, master-data review, testing and internal process preparation need to happen before mandatory implementation.
The definition of Revenue and the detailed scope rules also need careful assessment.
A business should not determine its phase from:
The underlying legislation and the business’s specific position should be checked.
For broader preparation steps, EMARK’s UAE E-Invoicing Readiness Checklist can be used alongside this penalty review.
The following examples are deliberately simplified.
They are illustrative calculations only. They are not actual FTA assessments and do not determine whether a particular event legally constitutes a violation.
Assume a business is within scope and that 18 electronic invoices each independently meet the conditions for the relevant violation during one calendar month.
The calculation would be:
18 invoices × AED 100 = AED 1,800
The illustrative penalty would therefore be:
AED 1,800
Now assume the number of affected electronic invoices was 62.
The simple calculation would be:
62 × AED 100 = AED 6,200
However, the relevant penalty category is capped at AED 5,000 per calendar month.
The illustrative amount would therefore be:
AED 5,000
That does not mean every batch failure automatically creates the maximum penalty. Whether a violation exists and how it is counted requires assessment against the decision and the specific facts.
Assume a business is required to notify its Accredited Service Provider of a relevant change and the notification is delayed by four days.
At AED 250 for each day or part of a day:
4 × AED 250 = AED 1,000
The illustrative amount would therefore be:
AED 1,000
This category is subject to a maximum of AED 5,000 per calendar month.
Before assigning any actual liability, the business should establish:
Businesses should not simply add every possible penalty in the table together.
Decision No. 173 contains an important provision relating to the same violation.
Where the same person acts as an issuer, recipient, or both in relation to the same violation, only one administrative penalty is imposed on that person for that violation.
That should not be interpreted as saying that a business can only ever receive one e-invoicing penalty.
Different violations may still need to be considered separately.
For example, an implementation-related violation and a separate failure involving electronic credit notes would not automatically become one single event merely because they involve the same company.
The facts and the relevant provisions need to be reviewed.
The decision includes an exclusion for a person issuing, transmitting, sharing, exchanging or reporting electronic invoices or electronic credit notes on a voluntary basis in accordance with the relevant decisions.
That is important for businesses testing e-invoicing before their mandatory implementation date.
However, voluntary participation should not be confused with an indefinite exemption.
Once mandatory requirements become applicable to the business, the position changes.
A useful internal implementation plan should therefore distinguish between:
Voluntary preparation period
and
Mandatory compliance period
The changeover date should be clearly documented so that finance, IT and the Accredited Service Provider are working from the same timeline.
Before assuming a penalty applies—or assuming everything is compliant—start with evidence.
The following checklist is an operational recommendation from EMARK. It is not a separate penalty schedule.
| Review area | What to check | Suggested owner |
|---|---|---|
| Scope and deadline | Legal entity, Revenue assessment, relevant transactions and implementation phase | Finance / Tax |
| ASP appointment | Appointment confirmation, agreement and onboarding evidence | Project lead |
| Outgoing invoices | Successful invoice transmission, credit notes, rejected transactions and re-transmission | Finance systems |
| Incoming invoices | Receipt, matching, rejection handling and status monitoring | Accounts payable |
| Registered-data changes | What changed, date ASP was informed and evidence of notification | Tax / Administration |
| Exception handling | Failed transmissions, owner, corrective action and closure evidence | Finance / IT |
The important word here is evidence.
A project status saying “ASP appointed” should be supported by the relevant appointment or contractual evidence.
A status saying “testing completed” should be supported by actual test results.
A statement such as:
“Our software provider is taking care of e-invoicing”
does not necessarily establish that the company’s own finance process is ready.
A short implementation review should identify:
A common testing mistake is to prove that one normal sales invoice can move successfully through the system and consider implementation complete.
Finance teams should consider a broader test set.
Depending on the business, this might include:
The purpose is not to create an unnecessarily complex test environment.
It is to make sure the accounting process works when a transaction does not follow the simplest possible route.
An Accredited Service Provider may manage significant technical parts of the e-invoicing process.
That does not remove the need for internal ownership.
Businesses should understand which responsibilities belong to:
For example, the ASP may provide the transmission infrastructure, while the company remains responsible for the accuracy of customer master data entered into its own accounting system.
Similarly, a provider may report a rejected invoice, but someone within the company still needs responsibility for investigating and correcting it.
The implementation plan should make those responsibilities visible.
A technically successful integration can still produce poor results when the underlying finance data is incomplete or inconsistent.
Before mandatory implementation, review relevant master data such as:
Where errors are identified, record the correction and test the updated data.
E-invoicing should not be treated solely as a software project.
It is also a finance-data project.
For the specified implementation and recipient-continuity violation category under Cabinet Decision No. 173 of 2026, the penalty starts at AED 5,000.
A further AED 5,000 applies for every month or part of a month during which the non-compliance continues.
The maximum is AED 50,000 within any twelve consecutive months for this category.
That cap does not apply as one overall ceiling for every other e-invoicing violation.
Yes.
Decision No. 173 provides a separate AED 100-per-document penalty for electronic invoices and electronic credit notes where the respective violation conditions are met.
Each category is subject to a maximum of AED 5,000 per calendar month.
The new penalty framework does not retain the former system-failure notification penalty.
The underlying system-failure notification provision was also repealed under Ministerial Decision No. 197 of 2026.
Businesses should nevertheless maintain reliable internal procedures for detecting, investigating and resolving unsuccessful transmissions.
Not necessarily.
The first-phase ASP appointment deadline has passed, but an actual administrative penalty assessment depends on the applicable legislation, commencement date, business scope and facts.
A business that has missed an applicable deadline should verify its position promptly and take documented corrective action rather than assuming either that no consequence exists or that a particular fine automatically applies.
For the same violation, Decision No. 173 provides that where the same person acts as issuer, recipient or both, only one administrative penalty is imposed on that person.
Different violation categories may still require separate assessment.
Cabinet Decision No. 173 is a penalty decision. It does not itself postpone the phased implementation timetable.
Businesses should continue planning against the dates applicable to their category unless a subsequent official decision changes those dates.
The penalty framework matters, but avoiding a fine should not be the only reason for preparing properly.
E-invoicing affects how a business creates invoices, receives supplier documents, manages credit notes, maintains master data, investigates failed transmissions and keeps evidence of what happened.
A technically connected system can still create problems when the underlying accounting process has not been tested.
A useful readiness review should therefore answer practical questions:
EMARK Accounting and Auditing L.L.C. supports UAE businesses with e-invoicing readiness reviews, finance-process assessments and accounting-system preparation.
If your organisation needs to understand its current position before the applicable implementation date, contact EMARK to review the finance process, accounting data and implementation gaps that need attention.
For the broader changes to the UAE e-invoicing framework announced in October 2026, also refer to EMARK’s article:
UAE E-Invoicing Changes in 2026: What Businesses Need to Review
EMARK supports UAE businesses with e-invoicing readiness reviews, finance-process assessments and accounting-system preparation. Review your finance process, accounting data and implementation gaps before the applicable mandatory date.
1. Cabinet Decision No. 173 of 2026
Official UAE Ministry of Finance decision on violations and administrative penalties relating to the Electronic Invoicing System.
2. UAE Ministry of Finance — 30 October 2026
Updated Administrative Penalties Related to the UAE eInvoicing System to Enhance Clarity and Support Business Compliance.
3. Federal Tax Authority — 25 October 2026
Official reminder concerning prescribed e-invoicing compliance deadlines and administrative penalties.
4. UAE Ministry of Finance — 19 October 2026
Official announcement concerning amendments to the Electronic Invoicing System under Ministerial Decision No. 197 of 2026.
5. UAE Ministry of Finance E-Invoicing Portal
Official source for Ministerial Decisions No. 243 and 244 of 2025 and subsequent amendments.
This article is provided for general information. Regulatory information was reviewed as of 4 November 2026. The legal commencement of a decision, applicable implementation phase, exclusions, administrative procedures and the circumstances of a particular business require case-specific verification. Businesses should obtain qualified UAE tax or legal advice before making decisions based on a possible administrative penalty.