When a business adds subsidiaries, acquisitions or international entities, the finance problem changes. Separate ledgers may preserve local autonomy, but they can also create duplicated master data, manual intercompany reconciliations, inconsistent close processes and delayed group reporting. A multi-entity ERP should reduce that friction without forcing every legal entity into an unsuitable operating model.
The important distinction is between multi-entity accounting and multi-entity operations. Some platforms are strongest in financial consolidation and reporting; others also support shared inventory, purchasing, order fulfilment and intercompany supply chains. This guide compares six systems by the problem they are designed to solve. It is not a ranking: suitability depends on entity structure, local statutory requirements, operating model and implementation scope.
What multi-entity ERP needs to handle
- Legal-entity structure: parent, subsidiaries, branches and ownership relationships, with appropriate access and controls.
- Local finance: entity-specific base currencies, tax registrations, statutory books, fiscal calendars and reporting requirements.
- Group reporting: consolidated statements, currency translation, eliminations and management reporting across entities.
- Intercompany activity: cross-charges, loans, shared services, sales and purchases, inventory transfers and settlement.
- Shared operations: central procurement, common customer and supplier records, inventory visibility and order processing where appropriate.
- Auditability: clear transaction ownership, approvals, period close controls and traceable adjustments.
Before comparing products, decide whether each subsidiary needs a separate operational company, a separate ledger, or simply a reporting dimension. These are not interchangeable designs.
Six multi-entity ERP platforms to evaluate
1. Oracle NetSuite OneWorld
Best fit: growing international groups that want multiple subsidiaries managed within one NetSuite account.
Oracle documents OneWorld as supporting multiple subsidiaries, tax jurisdictions and currencies, with subsidiary-level financials and consolidated reporting. Its intercompany capabilities include transactions between subsidiaries and automated elimination workflows. Oracle also notes that subsidiaries are structured in a hierarchy and that the model is most straightforward where entities share broadly similar processes and group ownership.
Evaluate carefully: subsidiary hierarchy, local tax and statutory needs, shared versus entity-specific master data, intercompany flows and the implications of enabling or upgrading to OneWorld. Confirm the configuration required for your ownership structure; affiliates and joint ventures may need more specialised accounting treatment. Oracle OneWorld overview · Automated intercompany management.
2. Microsoft Dynamics 365 Finance
Best fit: larger organisations with complex finance governance, multiple legal entities and a Microsoft application estate.
Dynamics 365 Finance should be evaluated where the group needs configurable financial controls and cross-company processes. The design conversation should cover legal entities, shared services, intercompany accounting, consolidation approach, localisations and the relationship with other Dynamics applications. Do not assume that every operational process is automatically shared across entities simply because the group uses one platform family.
Evaluate carefully: entity setup, chart-of-accounts strategy, financial dimensions, intercompany policies, local compliance, reporting architecture and licence scope. Ask the implementation partner to demonstrate the close process across a parent and at least two subsidiaries using realistic transactions.
3. SAP S/4HANA
Best fit: large or complex groups that need enterprise-wide finance, supply-chain and operational integration.
SAP S/4HANA can support complex group structures and intercompany processes, with consolidation and elimination capabilities depending on the selected architecture and SAP products. SAP’s documentation describes consolidation processes that include data collection, validation, currency translation and interunit eliminations. The exact scope differs across SAP S/4HANA editions and Group Reporting or other consolidation components.
Evaluate carefully: whether consolidation is in scope of the core ERP design or a separate group-reporting component, the data model across company codes, local accounting requirements, and the level of process standardisation expected across subsidiaries. SAP consolidation-unit configuration · SAP intercompany processing.
4. Sage Intacct
Best fit: finance-led groups that prioritise multi-entity accounting, consolidation and reporting over a single operational system for every department.
Sage Intacct is frequently considered by organisations that need structured financial management across entities. In a selection process, establish the number of entities, consolidation requirements, currency and dimensional reporting needs, and which operational systems will remain outside the finance platform.
Evaluate carefully: intercompany transaction handling, local statutory requirements, entity onboarding, consolidation workflow, integrations and whether operational teams need deeper inventory, manufacturing or distribution capabilities than the proposed architecture provides.
5. Acumatica Cloud ERP
Best fit: mid-market organisations looking for a configurable cloud ERP and a connected operational model across companies.
Acumatica is worth evaluating when finance, distribution, project or manufacturing processes need to be considered together. The important question is how the proposed configuration handles company boundaries, intercompany transactions, shared data and reporting—not simply whether the product supports multiple companies.
Evaluate carefully: the exact multi-company features included in the proposed edition, intercompany automation, currency handling, consolidation, permissions, and the impact of customisations or connected applications.
6. Microsoft Dynamics 365 Business Central
Best fit: smaller groups or subsidiaries with relatively standard processes that need connected finance and operations, particularly in a Microsoft ecosystem.
Business Central can be a practical fit where entities have manageable complexity and the group can standardise processes. However, buyers should distinguish between multiple companies within an environment, consolidation capabilities and more advanced group-wide intercompany requirements. Complex legal structures, high transaction volumes or demanding consolidation policies may call for a different architecture or additional applications.
Evaluate carefully: company and environment strategy, intercompany setup, consolidation, localisations, extensions, permissions and how group reporting will be maintained as the organisation grows.
Comparison by group requirement
| Platform | Evaluation emphasis | Typical shortlist reason |
|---|---|---|
| NetSuite OneWorld | Subsidiary hierarchy, currencies, intercompany and consolidation | One account for a multi-subsidiary group |
| Dynamics 365 Finance | Enterprise finance controls and legal-entity processes | Complex finance in a Microsoft estate |
| SAP S/4HANA | Enterprise operations, group reporting and intercompany design | Large, standardised global operating model |
| Sage Intacct | Multi-entity financial management and reporting | Finance-led entity consolidation |
| Acumatica | Mid-market operational and financial processes | Configurable cloud ERP across companies |
| Business Central | Standardised subsidiary processes and group reporting | Smaller or less complex entity structures |
Architecture questions to settle before selecting software
- What is a legal entity in your design? Map every registered company, branch, tax registration and reporting unit before configuration begins.
- Where will the chart of accounts be standardised? Decide which accounts are global, which are local and how mappings will support consolidation.
- Which transactions cross entity boundaries? Document shared services, inventory transfers, intercompany sales, loans, royalties and cost allocations.
- How will local compliance work? Confirm country-specific tax, e-invoicing, statutory reporting, audit and retention requirements with qualified local advisers.
- Who owns master data? Define governance for customers, suppliers, products, currencies, dimensions and intercompany counterparties.
- What does group close require? Set targets for reconciliation, elimination, currency translation, review and reporting timelines.
Multi-entity ERP TCO: costs that are easy to miss
Build a five-year model that includes licences by entity and user, implementation and localisation, data migration, intercompany automation, integration middleware, reporting or consolidation tools, testing, training, support and ongoing administration. Include the cost of maintaining parallel ledgers or manual reconciliations if the selected system does not cover the required workflow.
For a practical starting point, use our guide to ERP implementation cost and TCO. If your group is comparing broader platforms, see cloud ERP options for growing businesses.
How to test a multi-entity ERP in a demo
Do not accept a demonstration limited to consolidated dashboards. Ask the vendor to post a purchase in one subsidiary, record an intercompany sale or recharge, settle the payable and receivable, translate the foreign-currency balance, run the elimination and produce both local and consolidated statements. Then introduce a late adjustment and show how the audit trail and close controls behave.
A system that produces a consolidated balance sheet but cannot explain how the underlying intercompany balances are created, reconciled and eliminated may not solve the group’s actual problem.
Conclusion
The right multi-entity ERP depends on whether your primary requirement is consolidated finance, shared operational processes or both. NetSuite OneWorld, Dynamics 365 Finance and SAP S/4HANA belong on many complex-group shortlists; Sage Intacct, Acumatica and Business Central may fit narrower or more standardised operating models. Validate the legal-entity design, intercompany scenarios and local compliance requirements before comparing headline features or licence costs.
