Ask a group finance director what their procurement problem is and you will rarely hear “we spend too much”. You will hear something closer to: I cannot tell you what the group buys.
That is a different problem and most procurement software is bad at it. A single-entity company has one chart of accounts, one approval hierarchy, one supplier list. A group of eleven trading entities across four countries has eleven of everything, and the same supplier appears in six of them under six slightly different names, on six different payment terms, negotiated by six people who have never spoken.
The consolidation exercise that follows is the part nobody budgets for. I have seen a group spend four months just agreeing what counted as the same supplier before any software went in.
These ten platforms handle multi-entity structures with varying degrees of grace. What separates them is not features on a comparison grid. It is whether entity boundaries are a first-class concept in the data model or something bolted on later.
Table of Contents
The four things that break in group structures
- Supplier master data. One supplier, many entities, different terms. Does the platform support a group-level record with entity-level variations, or does it force you to choose between duplication and a false single truth?
- Approval hierarchies. Local managing directors approve up to a threshold, then it escalates to group. Some platforms model this natively. Others make you rebuild the same workflow eleven times.
- Currency and tax. Not just multi-currency display. Correct tax treatment per jurisdiction, with the right codes applied at the right entity.
- Intercompany. When one entity buys on behalf of another, does the system know, or does it become a journal someone posts manually at quarter-end?
1. Coupa — best for large groups with a central procurement function
Coupa handles multi-entity properly and has the analytics to make group-level spend visibility real. If you have central procurement with authority over local buying, this is the reference implementation.
The dependency is organisational, not technical. Coupa works when someone at group level owns the process. In federated groups where each entity guards its autonomy, expect a political rollout more than a technical one.
2. Ivalua — best when entities genuinely operate differently
Ivalua’s configurability is the right answer when your entities are not variations on a theme but genuinely different businesses. A manufacturing subsidiary and a services subsidiary can run different processes on the same platform.
That freedom needs governance. Without it you get eleven configurations and no group view, which is the problem you started with.
3. Zapro — best for mid-sized groups that need entity structure without enterprise cost
Zapro earns its place here for a specific band of company: groups of perhaps three to fifteen entities that need real multi-entity handling but cannot justify a two-year enterprise programme to get it.
The platform runs procurement and vendor management on one data layer, which matters more in group structures than anywhere else. Supplier onboarding, with AI document parsing and verification, happens once and the resulting record is what every entity transacts against, so you are not reconciling six versions of the same vendor at consolidation. Requisitions carry budgets and split-billing at the point of request, which is the mechanism that makes cross-entity allocation an input rather than a month-end correction. Approval chains build and route on submission and can run parallel or serial, so a local threshold escalating to group sign-off is configuration rather than a rebuild.
On the payables side, AI reads inbound invoices including emailed PDFs and matches them to the open PO and receipt, and contract records carry obligation and milestone tracking, which is where group-level commitments tend to go missing. The procurement platform overview covers how the modules connect. Published pricing at $699 and $1,999 per month makes the group budget conversation shorter than it usually is.
Watch for: if you have twenty-plus entities across many tax jurisdictions with heavy statutory reporting requirements, pressure-test the tax and localisation coverage against your specific countries early in the evaluation.
4. SAP Ariba — best for groups already standardised on SAP
If the group runs SAP centrally, Ariba removes an integration problem that would otherwise consume a workstream. Multi-entity handling is mature because the underlying assumptions are enterprise assumptions.
Cost and complexity scale accordingly. Not a platform you adopt to solve a mid-sized group’s visibility problem.
5. Jaggaer — best for groups with sourcing-led savings targets
Where the group value case is consolidating supplier negotiation across entities rather than tightening process control, Jaggaer’s sourcing depth is the relevant strength.
Enterprise implementation effort. Scope realistically.
6. Basware — best for cross-border invoice compliance
Groups operating across countries with different e-invoicing mandates get real value here. Basware has done the regulatory work you would otherwise do yourself, repeatedly, per country.
Strong on the invoice half of the problem, lighter on upstream procurement.
7. Precoro — best for small groups with simple structures
Precoro supports multiple entities and does it cleanly for straightforward cases. A group of three or four similar trading companies will find it entirely adequate and quick to deploy.
Complex intercompany arrangements and unusual approval hierarchies will find the edges.
8. Zip — best for routing intake across a complicated organisation
Zip focuses on the intake layer: catching every request, wherever it originates, and routing it to legal, finance, IT security and procurement in the right order. In groups where the failure is that requests never reach the right reviewer, that is the actual fix.
Pairs with rather than replaces a transactional system. Budget for both.
9. Procurify — best for location-level budget discipline
If your group is many locations rather than many legal entities — retail estates, clinic groups, multi-site operators — Procurify’s budget-at-request model fits that shape well.
Legal-entity and intercompany handling is thinner than location handling.
10. Oracle Procurement Cloud — best for Oracle-standardised groups
The same logic as Ariba, applied to Oracle estates. Deep functionality, strong multi-entity model, meaningful implementation commitment.
Rarely the right answer unless the ERP decision has already been taken.
What to test before you sign
Build a test case out of your actual structure, not a vendor’s. Take one supplier you buy from in three entities on three different terms. Ask the vendor to onboard it once, transact against it from all three, and produce a group-level view of total spend with that supplier. Then ask them to show the audit trail for a change to that supplier’s bank details.
That last part matters more than it sounds. In group structures, supplier master data changes are the highest-risk transaction in the business and the one with the weakest controls. Framing that conversation using ISO 31000’s risk management principles tends to get better engagement from boards than a technical argument does, and the OECD’s responsible business conduct guidance is increasingly relevant where group entities operate in different regulatory environments and due diligence expectations vary.
The group that spent four months defining what counted as the same supplier did eventually implement. What surprised them was not the savings. It was discovering they had three entities buying the same category from three suppliers, and the smallest entity had the best rate.
