Working Capital Across a Group: Why Cash Disappears When You Have Multiple Entities

Working capital looks manageable in the group view. It frequently is not. In a multi-entity business, cash is rarely distributed where it is needed - it accumulates in entities with structural surplus while entities under operational pressure run on overdraft facilities that carry material interest cost. The pooling illusion is one of the most consequential and least visible finance risks in a group structure, and it persists precisely because the consolidated view is designed to obscure it.

The pooling illusion and its operational consequences

The mechanics of the pooling illusion are straightforward. A group P&L that consolidates cleanly can conceal severe liquidity stress at entity level. When Entity A holds EUR 14M in cash and Entity C is running a EUR 3M overdraft to fund its receivables cycle, the group net position appears manageable. What is invisible in the consolidated view: Entity A's cash is locked in a local market with informal capital movement constraints; Entity C's overdraft carries an 8% interest rate; the intercompany loan that theoretically connects them was never properly structured and now sits on the balance sheet as a liability without a repayment schedule.

This configuration is not unusual. It is the standard condition of groups that have grown through acquisition or cross-border expansion without establishing a centralised treasury function. Managing group working capital from the consolidated DSO alone is not conservative practice. It is structural blindness.

The EY 2023 CFO survey found that 58% of multi-entity Group CFOs reported discovering unexpected entity-level liquidity events that were not visible in the prior month's consolidated working capital figures. The average time between the problem beginning and the Group CFO becoming aware of it was 47 days - long enough, in most cases, for the entity to have drawn down available facilities before treasury could respond.

Three invisible liquidity risks specific to multi-entity groups

Receivables aging that is healthy at group level and distressed in specific markets. A consolidated DSO of 47 days is consistent with a DSO of 91 days in an Iberian entity and 28 days in a German entity. The German entity's discipline masks the Spanish entity's collection problem until the overdraft materialises. By the time the group-level number reflects the deterioration, the problem has been running for months and the cost - in interest, in customer relationships, and in management time - has already been incurred.

The issue is not just operational. It is structural. If the group's DSO calculation includes intercompany receivables - the EUR 8M owed by a sibling entity, which is not subject to the same collection risk as external receivables - then the group DSO is wrong by construction. A group that does not strip intercompany from its DSO calculation is managing to the wrong metric and does not know it.

Intercompany balances inflating the apparent working capital position. Intercompany payables and receivables are not neutral. An entity owed EUR 8M by a sibling carries that as a receivable - it inflates its working capital position even though the receivable carries no real credit risk and may have no agreed repayment timeline. At group level, these net to zero only if they are properly identified, reconciled, and eliminated. When they are not, the consolidated working capital position is systematically overstated. Finance decisions made on that basis carry embedded error that compounds each period the reconciliation is not performed.

FX exposure creating liquidity events invisible in functional currency reporting. A group that consolidates in EUR may hold significant operating cash in PLN, CZK, or GBP. Functional currency balances look stable in the consolidated view. FX movements create liquidity events at entity level - sometimes quickly - that do not surface in the consolidated P&L until they are material. An entity that appeared well-funded in EUR terms in Q1 may be managing a material shortfall by Q3 if the zloty has moved 6-8% against expectation. The group weekly cash report, if it exists, may not capture this until the entity's finance team reports it manually.

What genuine group cash visibility requires

True group cash visibility is not a treasury system purchase. It is a data governance problem with three structural requirements that precede any technology investment.

Entity-level cash reporting on a consistent definitional basis. The same cash definition, the same timing, the same account categories across all entities. This sounds simple. In practice, the German entity reports available cash in its primary current account; the Spanish entity reports bank account balance including a EUR 1.2M overdraft facility that it treats as available. These are different numbers reported under the same label. Consolidating them produces a figure that overstates available liquidity. Standardising the definition requires a policy decision and a governance process to enforce it - neither of which is complex, but both of which require the Group CFO to own them explicitly.

Intercompany positions stripped and reconciled before consolidation. A group with EUR 40M of intercompany balances that has not been through a formal intercompany reconciliation in the last quarter is working with a distorted picture of its own liquidity. The reconciliation must happen before the group view is assembled - not as a monthly manual adjustment, not as a quarterly clean-up exercise. The IC positions must be live and clean as a prerequisite for a reliable group cash view.

A weekly cash position from entities - automated, not manual. A monthly cash view, extracted manually from entity-level systems, is always 3-4 weeks behind the operational reality. By the time the Group CFO receives it, the entity-level positions it describes have changed materially. Weekly automated feeds - not elaborate treasury platforms, simply structured entity submissions against a defined template - produce a current view without heroic effort from treasury.

What good looks like: EUR 200M industrial group

A family-owned industrial group, EUR 200M revenue, 7 entities across three markets, rebuilt its cash visibility function after a working capital crisis in one entity was not detected until it had drawn down EUR 5M in uncommitted banking facilities over six weeks. By the time the Group CFO was informed, the entity's relationship bank had already raised pricing on the facility.

The rebuild had three components. A standardised weekly cash reporting template, submitted by each entity on Thursday by noon, covering operating account balances, overdraft utilisation, material receivables due in the next 14 days, and IC loan positions outstanding. An intercompany reconciliation protocol that cleared IC balances before each weekly group view was assembled - the process took two hours per week across the group. A simple group treasury dashboard showing entity-level positions, IC loan schedules, and a rolling 13-week forward view by entity, updated weekly from entity submissions.

No new treasury system was purchased. The infrastructure to support the process existed in each entity's ERP. What did not exist was the governance discipline to use it consistently. Within one quarter, the Group CFO had moved from reactive - discovering problems after the cost had been incurred - to anticipatory, with sufficient visibility to address entity-level mismatches before they triggered unplanned facility drawdowns.

The Group CFO's working capital mandate

Working capital management at group scale is not a treasury function. It is a Group CFO mandate. The treasury team can execute a cash pooling arrangement, manage the 13-week rolling view, and escalate entity-level problems. What they cannot do is define the data standards, enforce the IC reconciliation cadence, or own the consequence when an entity-level crisis is invisible until it has become expensive. Those responsibilities belong at Group CFO level.

Groups that have addressed this systematically share one characteristic: the Group CFO treats working capital data as a governance requirement, not a reporting output. The weekly cash view is not produced because the board asked for it. It is produced because a Group CFO who cannot see entity-level cash positions on a weekly basis cannot manage treasury risk across a complex group structure. The cost of the process is trivial. The cost of discovering a EUR 5M overdraft six weeks after it happened is not.

If your consolidated working capital looks healthy while individual entities are managing overdraft facilities - or if your intercompany positions have not been formally reconciled this quarter - talk to us about building group cash visibility that reflects the operational reality.