Two accredited service providers can satisfy every eligibility requirement the Ministry sets and still leave you exposed to entirely different failure modes, because one owns its platform and the other rents it.

Ministerial Decision No. 56 of 2026 recognises that an Accredited Service Provider may use a third-party PSP Product while retaining full responsibility for the Electronic Invoicing Services delivered to End Users. That is a valid arrangement, and it makes product ownership and service accountability two related but different questions. With the 30 October 2026 appointment deadline compressing due diligence into weeks, enterprises are signing with providers whose underlying platform, hosting and support arrangements they have never examined.

The Invisible Platform Problem

Many enterprises believe they are selecting a single technology provider when they are entering a relationship involving several organisations. The contracting ASP, the PSP Product owner, the hosting provider and specialist support teams may all influence service delivery. Unless those relationships are understood, product changes, release schedules, data portability and migration planning become difficult to govern. Nothing has been concealed; the enterprise simply never asked who sat behind the name on the contract.

Chapter 6 of the forthcoming Real-Time Tax Transformation calls this Two ASPs, Two Different Risks. Two providers may both satisfy the Ministry’s eligibility requirements yet expose the enterprise to different operational risks. One owns and operates its platform directly. Another depends on a third-party PSP Product with separate development, hosting and support arrangements. Both are accredited; the dependency profile is different, and the difference surfaces only when something needs to change.

Eight Questions That Belong in Governance, Not in an Annexe

During ASP evaluation, implementation teams should establish who owns the PSP Product, who operates the production platform, who controls the product roadmap and release cycle, who owns the data export capability, who is responsible for defect resolution, who provides day-to-day support, who has administrative access to enterprise data, and what happens if the ASP changes its subcontractor or underlying PSP Product.

These questions sit alongside the accreditation and explain the operating model behind the accredited service. Answered properly, they tell an enterprise how quickly a defect affecting its tax determination can be fixed, whether a roadmap decision taken by a party it has no contract with can change its integration, and whether it can leave with its own data intact. Third-party PSP Products belong in enterprise dependency governance for that reason, rather than in a contractual disclosure schedule.

What Is Flowing Through the Chain

The dependency question sharpens once the content of the data is taken seriously. Invoice data is more than evidence for indirect tax; it represents a concentrated view of how an enterprise operates commercially. A structured invoice may reveal customer and supplier relationships, pricing, discounts, payment terms, product and service classifications, sales volumes, purchasing patterns and tax treatments. Once every B2B transaction is structured and routed through an accredited provider, that view becomes continuous and machine-readable.

Administrative access to production data therefore carries more weight here than in a payroll or printing contract. Where that access sits with a hosting provider or a support team employed by a party the enterprise has no relationship with, the question is whether control over the information still matches its own risk appetite. The objective is to know how commercially sensitive information is stored, accessed and governed across the service lifecycle.

What to Do With the Answers

Two of the eight questions decide how much room the enterprise keeps: data export capability, and what happens if the subcontractor or PSP Product changes. An enterprise that can export its structured invoice data in a usable form, and that knows which party can change the platform underneath it, retains the ability to move. One that cannot has made a longer commitment than the contract term suggests.

Ask the eight questions before signing and treat any that cannot be answered as a governance finding. The same discipline applies wherever exchange runs through certified providers under a PEPPOL-based regime; the UAE framework has simply put a date on it.