The AED 5,000-a-Month Clock That Starts Before Go-Live
Cabinet Decision No. 106 of 2025 treats the failure to implement the Electronic Invoicing System as the most fundamental of the six violations it penalises, and it prices that judgement into the penalty structure. Violation 1 in the table annexed to CD 106 covers "failure by the Issuer to implement the Electronic Invoicing System including the failure to appoint an Accredited Service Provider within the timeline prescribed by the Minister." The penalty is AED 5,000 for each month or part thereof that the failure continues.
The phrase "or part thereof" is the detail that catches businesses out. A business that appoints an ASP on the second day of a calendar month has still triggered a full month's penalty for that month, because the decision does not pro-rate. There is no partial-month discount. Delay by a single day into a new month and the AED 5,000 resets.
Why Appointment, Not Onboarding, Is the Trigger
The obligation is framed around appointing an Accredited Service Provider within the timeline the Minister prescribes, not around completing technical integration or issuing a first live invoice. This matters for how a business sequences its compliance programme. A business that has signed an ASP agreement but has not yet completed its technical build has satisfied the appointment obligation, even if invoices are not yet flowing through the system. Conversely, a business that has evaluated ASPs, run a tender, and still not signed with one by its prescribed deadline is exposed to the monthly penalty regardless of how advanced its internal readiness work is.
This creates a clear sequencing priority for any business approaching its mandatory phase date. Appointing an ASP is a contractual and administrative step that can be completed independently of, and ahead of, the technical integration work. Businesses that leave ASP selection until integration planning is well underway are treating the lowest-effort compliance obligation as though it were the highest-effort one, and exposing themselves to a penalty stream that has no ceiling.
No Monthly Cap, Unlike the Document-Level Penalties
Violations 2 and 3 in the same annexed table — failure to transmit invoices and credit notes — carry a maximum of AED 5,000 per calendar month regardless of how many documents are affected. Violation 1 carries no such cap. Every month of non-appointment adds another AED 5,000, indefinitely, for as long as the business has not appointed an ASP. A business that delays ASP appointment by six months after its mandatory go-live date has accumulated AED 30,000 in this single penalty stream, on top of whatever separate exposure it has for failing to issue and transmit invoices during the same period, since it cannot process Electronic Invoices through the required system without an ASP in place.
The Practical Read for Programme Planning
Cabinet Decision No. 106 gives Violation 1 the position of first item in the table for a reason: appointing an ASP is the precondition for compliance with every other obligation in the framework. A business cannot issue and transmit a compliant Electronic Invoice, notify the FTA of a system failure through the prescribed mechanism, or maintain accurate registered data with an ASP that does not yet exist as a counterparty. Treating ASP selection as an early, standalone milestone — decoupled from the rest of the integration timeline — is the direct way to avoid a penalty stream that compounds every month with no upper limit.