ERP harmonisation is the work of bringing a group of companies onto a consistent financial and operating model: a shared chart of accounts, aligned processes and one way of producing group reporting. It matters most in holding groups and diversified organisations that grew through acquisition or by letting each business choose its own systems.

The symptoms are familiar to any group finance team. Consolidation takes too long because every company codes the same transaction differently. Comparing the performance of two subsidiaries requires manual mapping. Shared services cannot scale because each entity follows its own procedure. The problem is rarely the software itself; it is the absence of a common model underneath it.

What harmonisation actually means

Harmonisation is not the same as forcing every company into an identical process. A group that sells construction services and a group company that runs retail outlets should not work the same way on the shop floor. What they should share is the structure that lets the group see them side by side.

In practice that usually means four layers: a group chart of accounts and financial structure; common master data for customers, suppliers and items where they are shared; aligned core processes where the business model is genuinely the same; and one reporting and consolidation model. Everything outside those layers can remain local by design rather than by accident.

Decision criteria

  • Standardise where the group needs comparability. Chart of accounts, reporting calendars, intercompany rules and key performance definitions should be common. These are the things group leadership reads.
  • Keep local where the business model differs. Operational processes that reflect a different kind of business should not be flattened to fit a template.
  • Decide the template before choosing the rollout order. A group template agreed upfront prevents each company from reopening the design during its own implementation.
  • Judge platforms against the target model. Oracle Fusion, Odoo and comparable platforms can each support multi-company structures. The right choice depends on scale, complexity and the group's operating model, not on the platform itself.
  • Plan for the companies you will add next. A model that cannot absorb the next acquisition will need to be redesigned sooner than expected.

Common pitfalls

  • Treating harmonisation as a software migration. Moving each company's existing habits onto a new platform reproduces the inconsistency in a more expensive system.
  • Designing the chart of accounts late. When it is agreed after configuration starts, reporting is rebuilt more than once.
  • Letting the largest company define the template. The template then fits one business well and every other business poorly.
  • Underestimating master data. Duplicate customers, suppliers and items across entities undermine consolidation even when the processes are aligned.
  • Ignoring the systems around the ERP. Project, asset and industry-specific tools that stay outside the programme need deliberate integration, or they become the new source of inconsistency.

Implementation considerations

Large harmonisation programmes are commonly delivered in waves: the template and a pilot group of companies first, then the remaining entities in groups that share a business model. Each wave should reuse the template rather than extend it, and changes to the template should go through a single design authority.

Integration deserves early attention. Project-management and asset-management systems often remain in place alongside the ERP, and the interfaces between them determine whether group reporting can be trusted. Testing should cover consolidation and intercompany scenarios, not only each company's daily transactions.

Programmes of this size are frequently delivered by more than one partner. Clear ownership of the template, the integrations and each wave matters as much as the platform choice.

Where to start

Start with the reporting the group actually needs and work backwards to the structure that produces it. That conversation usually shows quickly which differences between companies are genuine and which are historical. Launch Soft Solutions works through that question as part of a Business Technology Assessment before any platform or rollout plan is fixed.