The Quietest Obligation in Cabinet Decision No. 106
Violation 6 in the table annexed to Cabinet Decision No. 106 of 2025 is easy to overlook because it does not involve issuing anything. It penalises failure by the Issuer or the Recipient to notify their appointed Accredited Service Provider of changes to the data registered with the Authority, within the timeline the Minister prescribes. The penalty is AED 1,000 for each day of delay or part thereof — the same uncapped daily structure as the system-failure notification violations, and just as unforgiving of a slow internal process.
What Counts as Registered Data
The obligation covers changes to the data a business has registered with the Authority — the information the FTA holds against a business's Electronic Invoicing System participation, which underpins how its Electronic Invoices and Electronic Credit Notes are identified, validated, and matched to the correct Person on the Peppol network. Legal entity name changes following a corporate restructuring, updates to a Tax Registration Number following an amendment, and changes to the details tied to a business's Participant Identifier are the kind of registered-data movements that trigger this obligation regularly. These are routine administrative changes that accompany growth, restructuring, or simple corrections to records the Authority already holds — common events in an active business.
Why the ASP Sits in the Middle
The obligation runs to the ASP directly. This reflects the architecture of the Electronic Invoicing System: the ASP is the party responsible for validating and transmitting a business's Electronic Invoices and Electronic Credit Notes on its behalf, and it can only do so correctly if the data it holds about the business matches what the Authority has on record. A business that updates its trade licence or amends its Tax Registration Number with the Authority but never tells its ASP has created a mismatch between the two records the entire system depends on staying aligned. The penalty exists because that mismatch, left uncorrected, threatens the accuracy of every subsequent Electronic Invoice the business issues or receives through that ASP.
The Compounding Risk of Treating This as Low Priority
Because the obligation attaches to routine administrative events rather than to invoice-by-invoice transaction activity, it is the kind of duty that falls through the gaps between departments. A legal or company-secretarial team handling a name change or licence renewal has no natural reason to think about ASP notification unless that step is built into the change-management process itself. AED 1,000 a day with no cap means a change that takes three weeks to reach the ASP after being registered with the Authority — not an unusual timeline if no one owns the handoff — costs the business roughly AED 21,000 in penalty exposure for a single administrative update.
Building Notification Into the Change Process
The fix is procedural rather than technical: any internal process that updates data with the Authority — TIN amendments, address changes, trade licence renewals, legal name changes — needs a corresponding step that notifies the ASP within the prescribed window, treated as part of the same change. Businesses that have mapped their FTA-facing administrative changes to a parallel ASP notification checklist are the ones least likely to discover this violation the way most businesses do: after the penalty has already been accruing for weeks.