Getting one view of data after acquisitions
Agree group definitions, map identifiers and establish data ownership before forcing acquired businesses onto a single system.
A group can begin reporting consistently before every acquired business uses the same software. The first requirement is agreement on what the group needs to know, how each measure is defined and how records from different businesses relate.
System consolidation may still be worthwhile. It should follow the operating model and the evidence, rather than becoming a prerequisite for answering every cross-group question.
Separate group visibility from shared operations
Some businesses need to operate as one: common purchasing, stock allocation, service delivery or financial controls may require coordinated processes. Others can remain operationally distinct while leadership needs a comparable group view.
Make that distinction before choosing a data architecture. A reporting layer can combine measures from separate applications. It does not by itself create a common ordering process or resolve inconsistent operational controls.
Record which decisions require immediate information and which can use an agreed reporting cycle. This prevents a reasonable need for group visibility from turning into unnecessary real-time integration everywhere.
Agree definitions before combining totals
An acquired business may count an active customer by recent purchases, while another counts any open account. Combining those totals gives a number with no consistent meaning.
Start with a small set of measures used in real decisions. Define inclusions, exclusions, reporting period and treatment of later corrections. Give each measure an owner authorised to resolve disagreements.
Keep the original meaning available where it matters locally. Group consistency need not erase useful distinctions; the mapping should explain how local records contribute to the group measure.
Map identities without losing source context
List customer, supplier, product, asset and site identifiers in each business. Decide which records can be linked, what evidence supports a match and who reviews uncertain cases.
A register of links may be sufficient initially. In another case, a shared master record may be appropriate. Choose the amount of centralisation from the work that needs a common record, including who is allowed to update it.
Preserve source identifiers and history. An investigator should be able to trace a group figure back to the contributing records and understand which transformation was applied. The same transparency helps a later system migration.
Deliver a small group view first
The sequence below is a planning example, not a guaranteed 90-day delivery timetable. Access, source quality and the complexity of the group will determine the effort.
| Stage | Main decision | Evidence produced |
|---|---|---|
| Define | Which decisions and measures matter first? | Agreed definitions and accountable owners |
| Map | Which sources and identifiers support them? | Source register and documented matching gaps |
| Validate | How will users know the information is complete? | Quality checks, reconciliations and refresh status |
| Publish | Who can use the view and change its logic? | An accepted report and controlled change process |
Resist widening the report until the first measures are trusted. Track missing sources and unresolved matches openly instead of allowing an apparently complete dashboard to conceal them.
Keep the example and the claim proportionate
The Suntory PepsiCo story shows a governed reporting foundation across enterprise and operational sources, with ownership and master data practices included in the programme. It is relevant to the data problem, without being presented as an acquisition case study.
For a group considering its next step, produce one report that leadership can trace and explain. Use what that reveals about definitions and dependencies to guide any later consolidation. If the disagreement concerns the meaning of “customer”, the report definitions article provides a more detailed starting point.