Growth rarely produces a tidy bank account structure. Acquisitions add subsidiaries, lenders insist on separate accounts and property or fund structures create special-purpose vehicles. Over time, cash becomes dispersed across legal entities and banks while the finance function still relies on portals, spreadsheets and manual exports to understand the group position.

In a recent press release, Balance Cash, a treasury and cash management platform focused on multi-entity organisations, argues that corporate structure can often expand faster than treasury infrastructure. As cash spreads across more entities and banks, treasury’s ability to see, forecast and control it struggles to keep pace.

The pressure is sharpest in real estate, private equity-backed groups, franchises and holding companies, where lender covenants, tax rules and entity-level reporting keep accounts and banking relationships separate.

Growth creates fragmented bank estates

In a multi-entity group, cash sits across legal entities, accounts and banks that each hold only part of the picture. The structure builds account by account through acquisitions, lender requirements and decentralised management. Each addition appears manageable on its own. The strain only becomes visible when finance has to assemble the whole position.

Cash data can arrive through different portals and formats, often requiring manual downloads before it can be reconciled. By the time the figures are assembled, the group position may already be stale.

Often, the finance function is left without a dependable group-wide view of what is available, restricted or idle. An apparently healthy aggregate can also conceal cash trapped in one vehicle while another entity approaches a shortfall.

The hidden cost of idle cash

Locating idle cash has become more urgent as higher interest rates increase its opportunity cost. A better return on one account has limited value if the wider organisation cannot establish where liquidity sits or whether it is genuinely available for use.

Stan Markuze, chief executive officer at Balance, said: “When you are running thirty or forty entities, the question stops being where do I get a slightly better rate and becomes where is all of my cash, across everything, right now. Visibility has to come first. You cannot optimise what you cannot see. Once you can see it, optimisation follows naturally.”

Once balances are visible, the choices become clearer: which funds are restricted, what the business needs and what can be swept, invested or redeployed.

Conversely, a headline cash total rarely answers those questions. Funds may be tied to a lender covenant, reserved for a property or held within an entity that cannot transfer them freely. Classification therefore matters as much as aggregation.

The same blind spots weaken forecasts. A consolidated position may look comfortable while one subsidiary faces a shortfall. Local teams may also hold larger buffers because they cannot rely on group-level visibility or timely internal funding.

Treasury needs a view that can be filtered by entity, bank, property, fund or business unit, with enough detail to explain how the position has changed and where action is required.

A group-wide view across ringfenced cash

Group-wide visibility can sit above cash that remains legally ringfenced. Accounts stay with existing banks and under separate tax identifiers, while balances, transactions and forecasts feed into a common view. Balance applies this model through connections to existing banks, leaving accounts and relationships in place. For many groups, the first workable step is to bring balances, classifications and controls into one place.

Centralising information can precede physical pooling. A common view gives finance more control over a decentralised structure while preserving lender requirements, account ownership and entity-level reporting.

Businesses whose banking arrangements reflect genuine operating constraints can simplify the information feeding decisions while leaving the underlying treasury structure intact.

Spreadsheets create continuity risks

For firms with an active approach to M&A, each new entity taken on adds another portal, export and reconciliation step. The risk builds with this growth: a missed balance, an incorrect formula or a delay can leave yesterday’s cash position guiding today’s strategic decision-making.

Rebuilding the same view each reporting period also absorbs time that could be spent analysing movements or preparing for upcoming needs. As the account estate expands, the process becomes harder to review and more dependent on undocumented workarounds.

Those processes also concentrate knowledge in particular people. Access credentials, reporting routines and explanations for unusual balances may sit with a small number of employees. When those people change roles or leave, the organisation can lose both efficiency and institutional memory.

A central view reduces that dependency and can make unusual activity easier to spot across a group, particularly where no single bank sees the full pattern.

Automation still inherits the quality of the data and rules beneath it. Poorly designed automation can move errors faster or obscure assumptions, so controls must develop alongside the technology.

Between bank portals and a full TMS

Balance contrasts specialist multi-entity platforms with individual bank portals and enterprise treasury management systems. The comparison exposes a practical gap in the market. Bank portals provide depth within one institution and stop at its perimeter. Enterprise treasury systems offer broader functionality, though implementation cost and complexity can be difficult to justify for mid-sized groups whose immediate need is better visibility.

Bank-agnostic platforms occupy the space between those options, bringing multi-bank data together for groups with many legal entities. Companies needing deeper accounting integration, transaction execution or wider controls may still require a full treasury system.

“Generic treasury software tends to assume a tidy, centralised company with one or two bank accounts,” Markuze commented. “Most multi-entity organisations are anything but. The infrastructure has to reflect how they actually operate, with many entities, many banks and many constraints, and bring all of it into one place without asking them to re-paper their banking relationships.”

Operating structure should dictate the choice. A property group managing separate special-purpose vehicles may need something different from a multinational with complex funding, hedging and in-house banking requirements.

The control case for visibility

Fragmentation weakens liquidity planning, reconciliation, forecasting and fraud detection, while slowing the response to emerging shortfalls. A group-wide view can show where buffers are excessive, which receipts have failed to arrive and where a local cash gap is forming.

During acquisitions or rapid expansion, those sightlines become part of integration. When new entities and accounts outpace reporting processes, control weakens as the business scales. Treasury infrastructure belongs in the integration plan from the outset.

The starting point is a map of every entity, account, restriction and data flow. That map shows whether the next step is better bank connectivity, a specialist visibility layer, a full treasury system or a combination of the three.

Growth will continue to add entities, accounts and constraints. Good infrastructure keeps that complexity visible and manageable, allowing finance to find the cash, understand its availability and act before a fragmented structure starts dictating the company’s decisions.