Group Financial Planning: Why Single-Entity Planning Logic Breaks Down Across Multiple Business Units

The Group CFO knows how to build a budget. The problem is not planning methodology. The problem is building a group plan when entities run on different planning cycles, use different assumptions, and produce forecasts in incompatible formats that require manual reconciliation before a consolidated view can be assembled. By the time the group plan is complete, the entity plans it is built from are already stale. This is not a failure of FP&A capability. It is a failure of planning infrastructure - and it is the infrastructure, not the methodology, that must change.

The five structural failures of group financial planning

Most groups that struggle with financial planning recognise the symptoms: a planning cycle that runs too long and produces a consolidated plan that is already outdated when it is presented to the board; entity plans that are internally consistent but not comparable across the group; variance commentary at quarter-end that cannot distinguish between operational underperformance and planning assumption error. The root causes are structural, and they repeat across ownership structures and geographies.

Challenge 1: Planning cycle misalignment across entities. In groups built through acquisition or multi-market expansion, entities often have different fiscal years, different planning start dates, and different board approval timelines. A group that attempts to assemble a consolidated plan from entity submissions made on different calendars is aggregating views of different points in time, not a coherent group view of a single planning horizon.

The problem is compounded post-acquisition. An acquired entity with a March fiscal year, consolidated into a December group, produces a plan that covers a 12-month period that only partially overlaps with the group's planning horizon. The finance team bridges the gap with assumptions - typically reasonable ones - but those assumptions are not documented in the consolidated plan and create reconciling differences at year-end that nobody can explain cleanly.

Challenge 2: Assumption inconsistency that produces incompatible entity plans. FX rates, inflation assumptions, intercompany pricing, shared service cost allocations - all of these must be set centrally before entity-level planning begins. If each entity uses its own assumptions, the consolidated plan is not a group plan. It is an aggregation of entity plans that happen to produce a number - but that number cannot be used to understand the group's actual forward trajectory, because the components are based on different starting assumptions.

A VC-backed technology group, EUR 65M ARR, 5 entities across three currencies, assembled a group plan where two entities used a EUR/GBP rate of 0.84 and two used 0.87. The difference produced a EUR 2.1M variance in projected group revenue that was discovered only when the plans were consolidated - at which point the planning cycle was effectively over. The correction required four entities to resubmit. The resubmission took three weeks. The consolidated plan was delivered to the board two weeks late.

Challenge 3: Intercompany flows not eliminated in the forecast. Group-level planning must account for intercompany revenue and cost flows that net to zero at group level but inflate individual entity P&Ls. Most entity-level planning tools and FP&A platforms do not handle this automatically. The intragroup management fee that Entity A charges Entity B appears in Entity A's revenue plan and Entity B's cost plan - but unless it is eliminated before consolidation, the group plan overstates both group revenue and group cost by the value of the intercompany activity. The overstatement is symmetric, so EBITDA appears correct. But every margin ratio in the plan is wrong, and the entity-level profitability picture is distorted in ways that affect capital allocation decisions.

Challenge 4: The annual plan as a planning tool in a fast-moving group. In a complex multi-entity group, the annual budget is frequently outdated before the fiscal year begins. An entity underperforms in Q1. An acquisition closes later than planned. A currency moves 8% in the first quarter. The annual plan, assembled from entity submissions at the end of the prior year, has limited relevance to the management decisions being made in Q3. Rolling forecasts - maintained on a 12 to 18 month horizon, updated monthly from entity-level actuals and revised assumptions - are a more honest planning tool for groups with dynamic entity portfolios. They require the same infrastructure as a reliable annual plan, but the cadence is different: rolling forecasts force a monthly reassessment of assumptions rather than a once-annual exercise that is treated as authoritative long after it has ceased to be.

Challenge 5: Planning governance - who owns the group plan, not just who assembles it. Group financial planning requires clear governance on three questions: who sets the central assumptions that all entity plans must use; who has the authority to challenge an entity plan that is inconsistent with group targets; and who is accountable for the quality of the consolidated plan - not just its assembly, but the integrity of the data and assumptions it contains. Without clear answers to these questions, group planning produces an aggregation of entity-level optimism rather than a coordinated group view. Entities plan locally. The group plan is a sum, not a strategy.

What planning infrastructure looks like at group scale

Groups that have resolved these challenges share one practice: they treat planning as an infrastructure question before they treat it as a methodology question. The infrastructure - common definitions, central assumption setting, automated IC elimination in the planning model, a single group forecast model rather than entity-level spreadsheets aggregated manually - is what makes any planning methodology produce reliable outputs. Without the infrastructure, the methodology produces a well-formatted version of the same unreliable plan.

McKinsey's benchmarking of finance function planning processes across European mid-market groups finds that groups with a rolling forecast capability - supported by automated data flows from entities, a single group model, and central assumption governance - produce group forecasts that are 2.8 times more accurate at the quarterly level than groups using annual plans supplemented by quarterly manual reforecasts. The accuracy gain is not primarily a modelling gain. It is an infrastructure gain: cleaner, more current data, processed through a consistent methodology, with assumptions that are updated rather than frozen.

If your group planning process produces a consolidated view that is out of date before it reaches the board, or if entity-level plan quality varies enough to make the consolidated plan unreliable as a management tool - talk to us about what planning infrastructure looks like for your group's specific structure and entity portfolio.