Multi-entity groups
Bring structure to spending across entities, brands and business units.
Map programme ownership, funding responsibilities and oversight before cards are introduced across a corporate group.
Programme design, not a predetermined feature list. Final scope depends on the business, intended use, participating entities, jurisdictions and approval by the relevant providers.
Multi-entity groups
Make each entity visible inside the group programme.
A shared structure still needs explicit participation, funding and governance at entity level.
- 01 / Group
Participating companies
- Legal entities and brands
- Operating markets
- Proposed user groups
- 02 / Governance
Central and local roles
- Programme ownership
- Funding responsibility
- Administration and escalation
- 03A / Centre
Group programme view
Shared requirements and central responsibilities are defined for the proposed structure.
- 03B / Entity
Local participation
Each entity has its own users, funding role and onboarding requirements documented.
- 04 / Assessment
Entity and market review
No group-wide availability is assumed; each proposed entity and market is assessed.
- 05 / Oversight
Group and entity records
Programme reporting returns to the central and local owners defined in the model.
Model snapshot
Make the operating model visible.
These three questions establish the structure that the rest of the programme needs to support.
- Who uses it
- Approved teams across participating entities or business units
- Who funds it
- Participating entities or a central group entity, as approved
- Who controls it
- Group and entity-level administrators within agreed roles
Design considerations
Questions to settle before implementation.
The programme brief should explain purpose, responsibility and exceptions in terms the business and programme providers can assess.
Participating entities
Identify the legal entities, brands or business units proposed for inclusion and the role of each one.
Funding model
Clarify whether funding is intended to sit centrally, locally or through an approved combination of both.
Role boundaries
Define what group administrators, entity administrators, managers and cardholders should each be responsible for.
Market requirements
Assess every intended entity and operating market rather than assuming one approval applies across the group.
Operating flow
Turn the concept into a programme path.
Map the group
Document ownership, participating legal entities, operating locations and intended user groups.
Trace funding
Describe which entity provides funds and how budgets and responsibilities are expected to move through the group.
Set governance
Define central and entity-level administration, oversight, escalation and record requirements.
Review feasibility
Assess the proposed entities, markets and structure for eligibility and programme approval before implementation.
Programme outcomes
A clearer basis for review and delivery.
An entity participation map
The proposed role, users and funding responsibility of each participating entity are made explicit.
A governance model
Central and local responsibilities are defined before administrators or cardholders are onboarded.
A realistic feasibility plan
Each entity and market is considered within the relevant approval and implementation requirements.
Common questions
Before you begin.
Can one programme cover companies in different markets?
Every intended entity and market must be assessed. Availability cannot be assumed and depends on the business, jurisdiction, use case and required approvals.
Can subsidiaries share the same programme structure?
A common structure may be considered, but each entity's role, eligibility, funding and onboarding requirements must be addressed in the approved design.
Who should own the programme?
Programme ownership depends on the legal and operating structure. Discovery is used to identify the appropriate proposed owner and participating roles.
Programme discovery
Discuss this business model with us.
Tell us how your company operates, who needs to pay or get paid and what the solution should achieve.
Map your group structure