Platform · Multi-entity management
Multi-entity management for holding companies and subsidiaries
Each company in the group runs as its own organisation, configured the way that company actually operates.
Multi-entity management gives the holding company a view across its direct subsidiaries — their contracts, suppliers, parts, purchase orders and obligations — while each subsidiary keeps its own approval routing, sourcing policy and locations.
- Sourcing threshold
- Low — most things go to market
- Supplier documents
- A long certification list before first use
- Routing conditions
- Value, category, requester role, urgency
- Set by
- Its own administrators
- Sourcing threshold
- Higher — and a different award mode
- Supplier documents
- A much shorter list
- Routing conditions
- Contingent labour, contract type, budget
- Set by
- Its own administrators
Each company is its own organisation, not a department of one.
One group. Companies that do not work alike.
A single process written at the centre rarely survives contact with how each company actually buys.
How a group is arranged
What each company keeps. And what the group sees.
Every company in the group is its own organisation. It configures itself, and the holding company has a view across its direct subsidiaries.
A configurable approval graph per organisation, with conditions on value, category and its parent categories, requester role, urgency, sourcing method, line type, budget utilisation, contract type and contingent labour.
The threshold above which a sourcing event becomes mandatory, the minimum number of bids, how a supplier off the approved list is handled, and the award mode — each scoped by category or spend type.
Which onboarding documents and which certifications a supplier has to provide before it can be used, set per organisation rather than handed down.
Plants, warehouses, sites, storage locations and docks — each with an address, a manager, a currency and a timezone, and transactions that point at them.
A subsidiary reads the parent’s shared code lists and its contract clause and template libraries, so a new company starts from what the group already wrote rather than from nothing.
A subsidiary can work with the holding company’s suppliers, and the holding company with a subsidiary’s, rather than every company rebuilding the same records.
Registers that span the direct subsidiaries — contracts and their obligations, the supplier base, parts, purchase orders, part-approval submissions, worklists and bills of materials.
A card for each one carrying its open purchase order value and its pending requisitions, and analytics putting each entity’s spend next to the others with top suppliers merged across them.
Where this already runs
In operations like yours. Not vendor scenarios.
A diversified group ends the manual handoff between sourcing and contracting
Multiple business units, central category procurement and a shared services centre 3procurement groups working from one source-to-contract workflow0systems of record replaced; the workflow runs across the ones already there1route from sourcing event to signed contract Read the story
An industrial group unifies procurement across 18 operating companies
18 operating companies under one group 18operating companies on one procurement view1record per supplier, across the whole group0systems of record replaced Read the storyHow it works
Six things that are true of every group on the platform.
Not a hierarchy of rules cascading downward. A set of companies configured for themselves, with a holding company that can see across them.
-
01
System
Each company is its own organisation
A holding company and its direct subsidiaries, each one a separate organisation with its own legal entity name, currency, timezone and financial year start. Not departments of one system pretending to be separate.
-
02
Human
Its own administrators configure it
Approval routing, sourcing policy, supplier document requirements, locations and cost centres are set by the people who run that company, because they are the ones who know what its buying actually looks like.
-
03
System
It draws on the group’s libraries
A subsidiary reads the holding company’s shared code lists and its contract clause and template libraries, and can work with the holding company’s suppliers. The group writes something once.
-
04
Rule
Two things hold in every company
A sole-source or single-source requisition always picks up a chief procurement officer approval step. A supplier barred from transactions cannot be put on a new contract, purchase order or sourcing invitation. Neither is a setting.
-
05
System
The holding company sees across them
Group registers for contracts, obligations, suppliers, parts and purchase orders, and a dashboard with a card for each subsidiary. From the contract register you open the contract itself.
-
06
Human
A new subsidiary joins the view
Once it is linked to the holding company, which we do as part of bringing it on, it appears in the group pages straight away — with zeros against it until it has activity of its own.
Core capabilities
What multi-entity management has to get right.
Configuration that belongs to the company using it
Not a central template every subsidiary has to be an exception to
- An approval graph per organisation, built by its own administrators
- Conditions on value, category and parent category, requester role, urgency and budget utilisation
- Further conditions on sourcing method, line type, contract type and contingent labour
- And, on an intake request, new supplier, supplier risk tier, cross-border, renewal and data classification
- Changing one company’s routing changes that company’s routing and nothing else
A sourcing policy per company
The rules that decide when something has to go to market, set where they apply
- The value above which a sourcing event becomes mandatory
- The minimum number of bids an event has to attract
- How a supplier off the approved list is handled
- The award mode, scoped by category or by spend type
Libraries the group writes once
So the tenth company does not start from the blank page the first one did
- Shared code lists, read by the subsidiaries from the holding company
- The contract clause library and contract templates, the same way
- A supplier master that works in both directions between parent and subsidiary
- Industry defaults that preload modules and compliance settings when a company is created
Places that transactions point at
Plants, warehouses, sites, storage locations and docks, as records rather than labels
- Each one with an address, a manager, a currency and a timezone
- Requisitions, purchase orders, sourcing events, goods receipts, invoices, budgets and cost centres all reference them
- A location can be marked as requiring approval, which adds a step to an intake request shipping there
- Locations import from a file rather than being typed in one at a time
A holding-company view that is live
Not a pack someone assembles at month end
- Group registers for contracts, obligations, suppliers, parts and purchase orders
- A card for each subsidiary with its open purchase order value and pending requisitions
- Each entity’s spend shown next to the others, with top suppliers merged across them
- Open a contract from the group register and you are in the contract itself
Features
Multi-entity management that keeps companies apart.
Five groups of features, and not one of them depends on someone remembering the policy.
The few things that are true in every company
Not handed down by a parent. Built into the platform, so nobody has to remember to configure them.
- A sole-source or single-source requisition always picks up a chief procurement officer step
- A supplier barred from transactions cannot be added to a new contract, purchase order or invitation
- A requester overriding the suggested sourcing path has to write a justification
- That justification is recorded with the decision it belongs to
- Approval steps, and who actioned each one, are recorded
An approval graph each company builds for itself
Configured by the administrators of the company it applies to.
- Conditions on value, on category, and on a category’s parent categories
- On requester role, urgency and emergency, and budget utilisation
- On sourcing method, line type, contract type and contingent labour
- On an intake request: new supplier, supplier risk tier, cross-border, renewal and data classification
- Changing one company’s routing changes that company’s routing and nothing else
When something has to go to market, set where it applies
A sourcing policy belongs to the organisation that has to live with it.
- The value above which a sourcing event becomes mandatory
- The minimum number of bids an event has to attract
- How a supplier off the approved list is handled
- The award mode, scoped by category or by spend type
- Which onboarding documents and certifications a supplier must provide
Libraries a subsidiary reads rather than rebuilds
What the centre is genuinely useful for.
- Shared code lists, read by a subsidiary from the holding company
- The contract clause library, written at the group and used by the companies
- Contract templates, the same way
- A supplier master that works in both directions between parent and subsidiary
- Industry defaults that preload modules and compliance settings when a company is created
What the holding company can open
Live registers rather than a pack somebody assembles at month end.
- Group registers for contracts and their obligations across the direct subsidiaries
- Suppliers, parts, purchase orders, part-approval submissions, worklists and bills of materials
- A card for each subsidiary with its open purchase order value and pending requisitions
- Analytics putting each entity’s spend beside the others, top suppliers merged across them
- Open a contract from the group register and you are in the contract itself
What holds everywhere
Four things. The same in every company.
- A sole-source or single-source requisition always picks up a chief procurement officer approval step.
- A supplier barred from transactions cannot be added to a new contract, purchase order or sourcing invitation.
- A requester who overrides the suggested sourcing path has to write a justification, and it is recorded with the decision.
- A location marked as requiring approval adds an approval step to an intake request shipping there.
- Approval steps, and who actioned each one, are recorded.
Three companies. Three different answers.
The one that buys mostly engineered parts
A components subsidiary sets a low threshold above which a sourcing event becomes mandatory, demands a long list of certifications before a supplier can be used, and routes anything over its value band through engineering before procurement sees it. None of that is imposed on anybody else in the group, and none of it has to be argued for as an exception.
The one that buys mostly services
A services company in the same group has a contingent-labour condition on its approval routing, a different award mode, and a much shorter document list. It reads the holding company’s contract clause library rather than writing its own, which is the part it genuinely wanted from the centre.
The holding company looking at both
The group opens one page and sees a card for each subsidiary — open purchase order value, pending requisitions — and an analytics view putting each entity’s spend beside the others with the top suppliers merged. From the group contract register it opens any contract in either company.
Platform fit
It sits beside the systems each company runs. It replaces none of them.
Each company connects to its own system
Connectors are configured per organisation, each with its own address and credentials, so a group running different systems in different companies connects each one where it belongs.
What the connectors read
SAP S/4HANA reads suppliers, materials, purchase orders, goods receipts and supplier invoices. Oracle Fusion and Microsoft Dynamics 365 read suppliers, items, purchase orders and invoices.
Synchronisation is yours to start
A person triggers a sync, or an inbound message from the connected system does. Nothing runs at the system’s own initiative.
Locations line up by code
A location code in the connected system is matched to the location code in the organisation it belongs to.
Connects to Integrations · Intake & orchestration · Contract lifecycle management
Bring the company that never fits the central process.
The one that always ends up as an exception. We will configure it the way it actually buys, and show you the group still seeing across it.
Security, compliance and recognition
Checked by auditors. Judged by the industry.
Where each compliance programme stands, and what the procurement industry has given us so far.
Security and compliance
Awards
Five, presented on stage at three industry events.
- Autonomous Procurement Platform of the Year
- Procurement Technology Innovation Award
- Unified Procurement and Supplier Management Platform
- Procurement Startup of the Year
- AI in Procurement or Supply Chain Award — Solution Provider
Before you book anything. Answered honestly.
What is multi-entity management?
It is how a group of companies runs on one platform without being forced into one process. Each company — the holding company and each of its direct subsidiaries — is its own organisation, with its own legal entity name, currency, timezone, financial year, approval routing, sourcing policy, supplier requirements and locations. The holding company gets a view across the subsidiaries: their contracts, obligations, suppliers, parts and purchase orders, and a card for each one.
How is a group structured?
As a holding company with its direct subsidiaries beneath it. Each one is a separate organisation rather than a department of a shared configuration, which is why a subsidiary can be set up the way it actually buys rather than as an exception to somebody else’s process.
Does each company configure itself, or does the centre?
Each company. Approval routing, sourcing policy, supplier document requirements, locations and cost centres belong to the organisation they apply to, and are set by its own administrators. What the group provides instead of a mandate is a set of libraries — shared code lists, the contract clause library, contract templates and a supplier master — that a subsidiary can read rather than rebuild.
What can the holding company see?
Group registers for contracts and their obligations, suppliers, parts, purchase orders, part-approval submissions, worklists and bills of materials across the direct subsidiaries. A group dashboard carries a card for each subsidiary with its open purchase order value and pending requisitions, and group analytics puts each entity’s spend next to the others with top suppliers merged across them. From the group contract register you open the contract itself.
What happens when we acquire a business?
It becomes another organisation in the group, set up the way any company is set up — its own approval routing, sourcing policy, supplier requirements and locations — and it can read the holding company’s libraries from the start rather than building them. Once it is linked to the holding company it appears in the group pages immediately, with zeros against it until it has activity.
Does each entity need its own connection to its own system?
Connectors are configured per organisation, and one organisation can hold more than one, each with its own address and credentials. A group running different systems in different companies sets each connector up under the company it belongs to, which is also what keeps the data attributed to the right one.
Two companies. One view across them.
No slides. Configure two subsidiaries differently in front of you, then open the group register and see both.
Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.
Not ready to talk to anyone?
Fair enough. Both of these work without giving us your email.
Explore the next step
Intake & orchestration
The approval routing each company configures for itself
Contract lifecycle management
The clause library and templates a subsidiary reads from the group
Supplier management
The supplier master that works in both directions
Integrations
A connector per organisation, with its own address and credentials