Accreditation is not something your UAE e-invoicing ASP earns once — it is a status the Ministry of Finance can suspend or cancel, and your business remains liable for compliance the day it does.
Ministerial Decision No. 64 of 2025 sets Accreditation as valid for two years, with renewal applications due no later than seventy business days before expiry, and the Ministry retaining authority to suspend, cancel or terminate Accreditation where the prescribed requirements are no longer satisfied. Real-Time Tax Transformation (forthcoming) makes the governance point directly: most organisations record the ASP in the vendor master during implementation and rarely revisit the relationship afterward, treating accreditation as a one-time approval rather than a continuing regulatory relationship. Renewals, subcontracting arrangements, ownership changes and product migrations can all alter the operating characteristics of the ASP relationship over its life, and a vendor master that stays static while the underlying service model evolves creates a governance blind spot the business will not discover until something goes wrong.
The complication Ministerial Decision No. 56 of 2026 introduced makes this more than a renewal-date reminder. Under the amended framework, a Service Provider can satisfy required operational experience through a PSP Product it does not itself own, and can outsource elements of product development, operation or management while retaining full responsibility for the Electronic Invoicing Services delivered to end users. That means two accredited providers can carry genuinely different dependency profiles even though both cleared the same eligibility bar — one operating its own platform directly, another sitting on a third-party PSP Product with separate development, hosting and support arrangements one layer removed from the contracting entity. Understanding which of those two your ASP actually is — who owns the product, who controls the roadmap, who has administrative access to your data, what happens if the ASP changes its subcontractor — is part of evaluating the relationship, not a technicality to file away after signature.
None of that changes where the liability sits. Federal Decree-Law No. 8 of 2017 makes the Registrant liable for its VAT position — the accuracy of the tax treatment, the completeness of the invoice record, the defensibility of the classification behind every line — and nothing in Ministerial Decision No. 243 of 2025, No. 244 of 2025 or No. 64 of 2025 shifts that liability to the Service Provider. If an ASP's accreditation lapses mid-contract, the business's obligation to transmit compliant invoices does not lapse with it. The book's treatment of the accountability boundary is precise about this: an ASP whose accreditation is suspended has stopped meeting a regulatory threshold, but the enterprise's compliance clock keeps running regardless.
The practical consequence is that ASP selection needs continuity provisions negotiated before go-live, not in the middle of a crisis. A defined notice period if accreditation status changes. Data portability terms that let the business export its invoice history in a usable format on short notice. A pre-identified fallback — a second accredited provider the business has at least evaluated, even if not contracted — so a lapse does not leave the business with no transmission path at all. Business continuity and insurance sit alongside this: an ASP outage delays billing, disrupts supplier processing and creates uncertainty over reporting status well before accreditation itself is at issue, and the same continuity discipline that protects against an outage protects against the harder case of an accreditation withdrawal. The obligation that survives an ASP's failure is the business's own, and the contract is where that survival gets planned for rather than discovered.