A Shared View Before a Shared ERP

A newly acquired business does not immediately inherit the reporting definitions of its parent. Account structures, product records, operating calendars and local practices remain embedded in its systems.

Leadership nevertheless needs to understand performance, cash and integration priorities. Establishing that view begins with comparability.

Choose the questions first.

Start with the decisions the group needs to make. A liquidity review, inventory comparison and sales-performance discussion require different records and definitions.

Trying to harmonize every source at once can expand the work before the first useful view exists. A defined decision scope creates a practical boundary for the initial integration.

Agree the meaning.

Two fields with the same name may describe different events. Revenue may follow different recognition or reporting conventions. Inventory may include different locations, statuses or valuation treatments.

Mappings should therefore have accountable owners. Where two measures cannot yet be compared, show the difference rather than concealing it inside a consolidated figure.

Preserve the route back to the source.

A group view needs supporting records, update times and a visible history of relevant mappings or adjustments. This allows local teams to investigate discrepancies and finance or operations to review the interpretation.

Federation creates a shared view but does not repair every source-system problem. Poor data quality and inconsistent local processes still require ownership and correction.

Use visibility to guide consolidation.

Once leadership can see the operating constraints, it can make more informed decisions about which systems to retain, connect or replace. Some migrations remain necessary. Others can be sequenced around business priorities rather than the absence of reporting.

The first shared view should help the organization decide what to do next, while making its own limitations clear.