Say 'centralized liquidity' and most people picture a Fortune 500 treasury: notional pooling, offshore subsidiaries, a department to run it. The principles underneath scale down further than that. A business with three subsidiaries, three currencies and three separate banking relationships is already paying hidden liquidity costs that centralisation would remove.
The problem with silos
Mid-market companies growing internationally tend to end up siloed by default: every legal entity has its own bank accounts and its own liquidity position. The CFO can see each entity. Nobody can see the group in real time. Three costs follow from that.
- Dead cash. Every entity keeps its own buffer, and the sum of those buffers is larger than the group would need if it held one. That is idle capital earning nothing, often while the group pays interest somewhere else on the same balance sheet.
- FX friction. Moving liquidity between entities in different currencies means converting, which costs money and takes time. A centralised structure lets you hold the currency natively and deploy it across entities without converting for no reason.
- Visibility. Without one view of the position, a treasurer cannot make good decisions about internal deployment, external facilities, conversion timing or which supplier gets paid when.
What centralisation actually involves
For a mid-market business this needs no treasury subsidiary and no notional pooling complexity. Three elements are enough.
- Consolidated view. One platform showing balances across every entity and currency, updated in real time. Everything else depends on having this first.
- Sweep mechanism. The ability to move surplus liquidity from operating entities into a central pool automatically, on a schedule or on demand, and push it back out again. This can run as physical cash movement or as a notional accounting structure.
- Intercompany framework. Documented rules for moving funds between entities: interest terms, governance, regulatory compliance. This is the element that gets the least investment and causes the most audit and tax trouble when it is missing.
None of that is a product you buy. It is an architecture, and what it returns depends far more on how well it was designed for your business than on how sophisticated the technology is.
What it is worth
The impact is measurable. Industry benchmarks from treasury advisory practices put dead-cash reduction in mid-market silo structures at fifteen to twenty-five percent of aggregate cash holdings. For a business holding ten million euros across its entities, that is €1.5 to €2.5 million freed up for something productive.
FX savings are harder to put a number on without knowing the flow patterns, but they are material for any business regularly moving liquidity between currency zones, both from converting less and from being able to choose when to convert.
Where to start
The implementations that go well start with mapping rather than with technology. Three things need to be on paper:
- How funds actually flow between entities: volumes, currencies, timing.
- The regulatory constraints on intercompany lending and cash pooling in each jurisdiction involved.
- The tax position in each of those locations.
Once that exists the structure design is fairly straightforward. The difficulty sits in the jurisdictional analysis, not the build. A partner who can design the intercompany framework as well as supply the technology is worth considerably more here than one selling a pooling product.
This is an ordinary treasury principle that happens to be described in language that makes it sound like a large-company tool. One caveat: everything above is structural rather than tax advice, and any specific intercompany or pooling structure should be reviewed with qualified legal and tax counsel in each jurisdiction it touches.
SQF Editorial · Treasury & Infrastructure