Multi-entity

Multi-entity ERP setup for growing business groups

How to set up legal entities, shared services, and intercompany controls without overengineering.

Confirm legal and tax reporting needs first, then design shared process templates across entities.

Automate intercompany entries where possible but keep reconciliation controls visible to finance.

Pilot with two entities before scaling to the full group.

Why this guide matters

• Confirm legal and tax reporting needs first, then design shared process templates across entities.
• Automate intercompany entries where possible but keep reconciliation controls visible to finance.
• Pilot with two entities before scaling to the full group.

What a good approach looks like

• Decide which processes must be standardised group-wide and which can remain entity-specific due to legal or market constraints.
• Establish shared-service boundaries for finance, procurement, and master data governance early in design.
• Design intercompany processes with explicit timing and reconciliation ownership to avoid period-end bottlenecks.
• Roll out in waves with entity readiness criteria covering data, controls, and local team capability.

Common mistakes to avoid

• Selecting software before agreeing the future operating model and decision criteria.
• Allowing one department to dominate the design while finance, operations, and IT assumptions remain untested.
• Using generic demos and partner promises instead of evidence from real scenarios, real data, and real reporting needs.

Practical next steps

• Document success metrics, owner accountabilities, and a realistic sequencing plan across finance, operations, and technology teams before committing budget.
• Use a weekly risk review with named owners, due dates, and mitigation actions so scope discussions do not restart every fortnight.
• Treat the guide as a working playbook and use it in steering meetings, partner workshops, and stage-gate reviews rather than leaving it as background reading.