Trapped cash is money held within a subsidiary that the wider group cannot freely move or use despite showing the balance in consolidated cash reporting. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.
What this means in practice
Trapped cash is money held within a subsidiary that the wider group cannot freely move or use despite showing the balance in consolidated cash reporting. The finance team therefore needs a clear trigger, responsible owner and evidence standard before the concept can be relied on in a live transaction.
Restrictions can arise from local law, regulatory capital, debt documents, minority shareholder rights, tax consequences, dividend capacity, exchange controls or operational banking limits. A concise checklist is useful only if it points to the authoritative source and does not turn a nuanced rule into an oversimplified yes-or-no box.
How the process works
The operating sequence should start with the trigger, move through validation and approval, and end only when the external result is confirmed. For this topic, the critical mechanics are: Restrictions can arise from local law, regulatory capital, debt documents, minority shareholder rights, tax consequences, dividend capacity, exchange controls or operational banking limits.
Planning should work backwards from the required result rather than from the internal submission date. A correct instruction can still fail operationally if the company misses a notice period, scheme window, bank cut-off or response deadline.
The data and evidence that matter
A reproducible record includes cash by legal entity, restricted amount, reason for restriction, expected release route, tax or legal conditions, local debt terms and realistic upstreaming date. This is stronger than a generic note saying the item was checked because it shows which condition was checked and against what source.
Where several systems participate, one transaction reference should connect the source record, approval, transmitted instruction and final response. Without that link, exception handling becomes an exercise in searching inboxes and spreadsheets after the deadline has already passed.
Where the process can fail
A group liquidity report can show £25 million of cash while only a much smaller amount is available to meet parent-company debt or a central tax payment. The exposure usually becomes more expensive to fix as the company gets closer to payment, settlement, testing or maturity.
Fragmented ownership can hide the problem. One team sees the contract, another sees the bank message and a third posts the accounting entry; without a named case owner, each can believe someone else has resolved the exception.
Worked example: test the mechanics
The consolidated dashboard shows £18 million. £6 million belongs to a regulated subsidiary, £3 million is subject to local debt restrictions and £2 million cannot be distributed until statutory accounts are approved. Treasury should not present the full £18 million as immediately fungible liquidity.
The figures are illustrative, not universal terms. In a live case the company should replace every amount, date and threshold with the current bank, scheme or contractual evidence, then rerun the decision before cash is committed.
Governance and control design
Tag cash by availability category and require local legal or finance confirmation before treating restricted balances as part of central headroom. Management should see unresolved exceptions before the deadline, not only after they appear as failed payments, covenant breaches or reconciliation differences.
The control owner should track total cash split into freely available, operationally constrained and legally or contractually restricted balances. A stable headline volume can otherwise hide growing concentration, ageing or dependence on manual repair.
Periodic review should challenge controls that never produce exceptions. A zero-exception process may be excellent, but it may also mean the rule is not actually being tested or the data is too coarse to reveal problems.
Ownership should also survive absence and staff turnover. The procedure should say who acts, who reviews, where evidence is stored and what happens if the normal owner cannot complete the step. For trapped cash in subsidiaries, undocumented expert knowledge is itself an operational dependency. The key mechanics here are topic-specific: Restrictions can arise from local law, regulatory capital, debt documents, minority shareholder rights, tax consequences, dividend capacity, exchange controls or operational banking limits. That is the point the local procedure should test rather than relying on a generic treasury checklist.
A quarterly or event-driven control review should compare the documented procedure with what staff really do. Where the live workflow has diverged, the business should either update the policy deliberately or restore the intended control rather than allowing an undocumented middle ground. For this article, the deciding evidence is cash by legal entity, restricted amount, reason for restriction, expected release route, tax or legal conditions, local debt terms and realistic upstreaming date; the control is incomplete if those fields cannot be tied to one dated case.
The final operational safeguard is a tested fallback. The company should know which parts of cash by legal entity, restricted amount, reason for restriction, expected release route, tax or legal conditions, local debt terms and realistic upstreaming date are required to execute safely if the preferred system, approver or communication channel is unavailable, and where a trusted copy can be obtained.
Editorial Verdict
BanksGB's editorial view is that clarity beats complexity here. Trapped cash is money held within a subsidiary that the wider group cannot freely move or use despite showing the balance in consolidated cash reporting. A short, well-evidenced operating rule is more useful than a technically accurate policy that staff cannot apply before a payment, drawdown or settlement deadline.
The final test is reproducibility: a second person should be able to explain what triggered the action, which data was used, who approved it, what the bank or lender did and what remains outstanding. If that chain is not visible, the control is weaker than the policy suggests. The exposure specific to this process is visible in total cash split into freely available, operationally constrained and legally or contractually restricted balances, so that measure should be reviewed before the next external deadline rather than after reconciliation.
Sources
- Association of Corporate Treasurers, treasury and loan documentation resources: https://www.treasurers.org/
- Loan Market Association, documentation and market resources: https://www.lma.eu.com/