Cost Visibility Across a Group: Why Savings Initiatives Fail When the Data Isn’t There

Cost reduction initiatives in multi-entity groups fail at a higher rate than the finance teams running them deserve. The failure is not analytical. The savings opportunities are real. The problem is upstream: the data used to identify them is inconsistent across entities, intercompany charges inflate the cost base in some business units and deflate it in others, and shared overhead allocation methods mean that optimising the cost line in one entity shifts costs to another without reducing them at group level. You cannot optimise what you cannot see. At group scale, cost visibility is a structural challenge before it is an analytical one.

Why group-level cost data is structurally unreliable without explicit remediation

In a group with entities that use different charts of accounts, different overhead allocation methods, and different treatments of intragroup charges, the consolidated cost base is not a reliable picture of where money is actually being spent. It is an aggregation of entity-level cost structures designed for local reporting, presented under group labels that imply comparability where none exists.

Consider the overhead allocation problem. When group-level functions - finance, IT, HR, legal, executive management - are charged to entities, the allocation method determines how the group's central cost base is distributed across the P&L. An allocation based on entity headcount produces a different cost profile for each entity than one based on entity revenue. A method that has changed between periods produces margin trends at entity level that reflect the methodology change rather than operational performance. When methodology changes are not disclosed to entity GMs - or when the methodology has been applied inconsistently for reasons that no longer exist - the entity-level margin picture is structurally unreliable as a basis for cost reduction decisions.

Consider the intercompany charge problem. In a group with significant intragroup activity, entity-level cost analysis that includes intercompany charges as if they were external costs identifies the wrong areas for reduction. The entity paying the highest management fee to the holding may appear cost-inefficient. The holding entity appears profitable. Both appearances are artefacts of the group's internal pricing structure. A cost reduction programme that attacks the management fee-paying entity is not reducing group costs. It is restructuring the allocation of costs that continue to be incurred at the same level.

PwC's 2023 finance benchmarking study found that in multi-entity groups with five or more entities, the average error rate in group-level cost comparisons - caused by inconsistent definitions, allocation changes, and unadjusted intercompany charges - was 18-22% of the cost variance being analysed. Cost initiatives launched on the basis of this data were, on average, 34% less effective than projected in their first year of execution.

Five components of an effective group cost reduction programme

Verify cost comparability before identifying savings opportunities. The standard starting point in a cost reduction programme is to identify where the largest costs are and where there is the most headroom versus benchmark. In a group, this step requires a prior verification: are the costs being compared actually defined the same way across entities? Before any analysis is trusted, the team must confirm that overhead definitions are consistent, intercompany charges have been stripped, the allocation methodology has not changed since the prior period, and the chart of accounts mapping from entity to group is clean. Only then does the cost comparison mean what it appears to mean. Skipping this step produces a savings target list built on an unreliable cost picture - and the savings programme will underdeliver accordingly.

Separate entity-level savings initiatives from structural group-level initiatives. These are different programmes requiring different governance and different decision-making authority. Entity-level cost reduction - renegotiating local supplier contracts, optimising entity headcount, improving local process efficiency - is owned by entity general managers and produces genuine savings visible in entity P&L. Structural group-level initiatives - procurement centralisation, shared service consolidation, group treasury optimisation, cross-entity platform rationalisation - require Group CFO authority to decide and Group CFO governance to execute. They produce savings that are invisible at entity level and must be tracked at group level to be measured. Conflating the two produces initiatives that lack either the authority or the accountability to deliver at the scale projected.

Define cost KPIs consistently before issuing targets. Cost KPIs - margin targets, overhead ratios, cost-per-unit benchmarks - are only meaningful across a group if they use the same definitions in every entity. An overhead ratio target of 22% means different things if overhead is defined differently in each entity. Entity-level finance managers who optimise their own local KPIs under inconsistent definitions are performing well by the metric they are being assessed against. They are not improving the number the Group CFO thinks they are improving. The group cost reduction programme must define the KPIs it will track, publish those definitions to all entities, and enforce consistency before targets are set.

Monitor savings with automated data flows, not monthly manual reporting. A cost reduction initiative tracked through monthly manual reporting is always 3-4 weeks behind the operational reality. By the time an entity finance team reports that savings are not materialising at the rate projected, the quarter may be over and the target is effectively missed. Group-level cost monitoring at the cadence required to intervene before the end of a reporting period requires automated data flows from entities - not the elimination of reporting, but the replacement of monthly manual extraction with automated weekly feeds that produce a current view of cost performance across the group without additional effort from entity finance teams.

Build financial literacy around the group cost framework at entity level. When entity GMs do not understand how group overhead has been allocated to their entity, they reject the numbers. When entity finance teams do not trust the group cost definitions, they produce local analyses that conflict with the group view and undermine the programme's credibility. Cost reduction initiatives stall not because the savings are not there, but because organisational trust in the data that identified them is insufficient. Building that trust requires transparency about methodology, consistency in its application, and a credible process for resolving legitimate disputes at entity level without diluting the group standard.

The EUR 250M industrial group: what cost visibility actually produced

A family-owned industrial group, EUR 250M revenue, 9 entities across four markets, launched a group cost reduction programme targeting EUR 12M in annual savings. The programme delivered EUR 4.1M in year one - 34% of target. The primary cause of underperformance: the cost data used to build the savings business case was assembled from entity-level reports that used different overhead definitions. The savings identified in two entities reflected an overhead allocation change rather than genuine efficiency improvement. The actual savings in those entities were EUR 1.1M rather than the EUR 3.8M projected.

A cost visibility rebuild preceded year two of the programme. It took 10 weeks: standardising the overhead allocation methodology, stripping intercompany charges from entity cost analyses, and implementing a weekly automated cost reporting flow from each entity. Year two savings delivery: EUR 9.8M - 82% of the original target on a corrected, trustworthy cost baseline.

The most durable cost savings in a multi-entity group come from structural decisions - shared services, procurement centralisation, group treasury - that require clean data to identify and clean governance to execute. The first investment is in the data foundation, not the savings programme. Without it, the savings programme is working with a map that does not match the territory. With it, the savings are visible, attributable, and manageable.

If you are planning a cost reduction programme across your group and the underlying cost data has not been verified for comparability across entities - talk to us about what cost visibility requires at group scale before the savings programme is scoped and committed.