Nothing in the UAE framework stops two companies in the same group appointing two different accredited service providers — which is exactly why groups end up with a multi-ASP operating model no one ever chose.

With the 30 October 2026 appointment deadline approaching, UAE groups with several legal entities are letting each entity procure independently. Each decision is defensible on its own terms. The aggregate is a landscape nobody designed.

Two Questions That Get Conflated

Whether an organisation should adopt a single Accredited Service Provider or several depends on the level at which the decision is being made, and the two levels have different answers.

At entity level, the current UAE Electronic Invoicing framework onboards each End User or Person with an Accredited Service Provider through the prescribed onboarding process. The Ministry’s Guidelines describe onboarding in the singular — choose an ASP and onboard with that ASP — and the Central Register maintains the list of End Users onboarded by those ASPs. The framework should therefore not be interpreted as permitting multiple concurrent ASPs for the same onboarded UAE End User unless future guidance expressly provides otherwise. Enterprises planning on the assumption that they can run two providers in parallel for one registered entity are planning against a permission the framework does not currently give.

At group level the position is different. Nothing in the current UAE framework prevents different legal entities, each being a separate Person, from appointing different Accredited Service Providers. A group may legitimately use one ASP across all legal entities, different ASPs for different entities, or different ASPs across jurisdictions as part of a global operating model. The strategic design decision therefore sits at group architecture rather than at individual entity level.

The Risk Is the Unmanaged Model, Not the Multiplicity

The governance risk sits in how a multi-ASP model arrives. It emerges through isolated entity-level procurement decisions taken without a common governance strategy, and by the time anyone looks at it whole, the commitments are already signed.

That distinction matters most for UAE corporate groups and VAT Groups, where local procurement decisions gradually create fragmented operating models, inconsistent integrations, duplicated governance activities and higher support complexity. A deliberate multi-ASP strategy can be entirely appropriate for a multinational organisation with genuinely different regional requirements. An unmanaged multi-ASP landscape increases operational complexity, support overhead, reconciliation effort, vendor dependency management and governance risk — and it arrives without anyone having accepted those costs as the price of a decision.

The Governance Framework a Group Needs Either Way

Where multiple ASPs exist across a group, management should establish a common governance framework covering architecture principles, onboarding standards, integration standards, data ownership, support and escalation, monitoring and reporting, security and business continuity, and migration and exit planning.

Read that list against a group that let each entity buy separately and the gaps are usually immediate. Integration standards differ by entity, so a change in one ERP instance cannot be applied across the group. Data ownership was settled a different way in every contract. Escalation paths run to as many support desks as there are entities, each with its own hours and severity definitions. Exit planning was not addressed anywhere, because no individual entity procurement was large enough to make it feel material. Every one of those gaps traces to the same cause: nobody set the standards the providers were selected against.

Where the Decision Belongs

Treat ASP strategy as a group operating model decision, aligned with the current UAE regulatory framework. The objective is governance consistency across the enterprise, not vendor standardisation for its own sake — a group can run three providers well and one provider badly. What it cannot do is govern an arrangement it never decided to enter.

For groups that have already let entity-level procurement run ahead of a group position, the remaining weeks are better spent writing the eight-item framework and applying it to the contracts still unsigned than on trying to consolidate providers before 30 October. The same logic holds for groups operating across EU and GCC PEPPOL-based regimes, where jurisdictional differences make a single provider unlikely and a common governance standard essential.