Adding or removing a legal entity from a cash pool changes bank sweeps, intercompany funding and local account liquidity, so the move requires more than a bank configuration request. This guide explains the mechanics, evidence, failure points and controls a UK business should understand before relying on the process.
What this means in practice
Adding or removing a legal entity from a cash pool changes bank sweeps, intercompany funding and local account liquidity, so the move requires more than a bank configuration request. For a UK business, the important point is when that concept changes cash availability, lender compliance, settlement or operating authority.
The cutover should coordinate legal agreements, account mandates, sweep parameters, target balances, intercompany accounting, tax or local restrictions and the entity's first or final operational payment cycle. Management should separate external permissibility from internal policy because an action can be technically available yet still fall outside delegated authority.
How the process works
The operating sequence should move from identification to validation, approval, external action and then confirmation. For this topic, the critical mechanics are: The cutover should coordinate legal agreements, account mandates, sweep parameters, target balances, intercompany accounting, tax or local restrictions and the entity's first or final operational payment cycle.
Timing should be planned backwards from the required result. Notice periods, value dates, processing windows and internal approval deadlines can make a correct instruction operationally late, so the workflow needs a repair margin.
The data and evidence that matter
A defensible record includes participant legal entity, account, pool agreement, sweep direction, target balance, effective date, intercompany account, local restrictions, final sweep and cutover confirmation. This is more useful than a generic 'checked' status because it shows what was tested and against which source.
The record should distinguish internal intention from external outcome. An approved request proves what the company intended; a bank acknowledgement, lender consent, statement entry or counterparty confirmation proves what actually happened.
Where the process can fail
An entity can be removed from the pool while payroll or supplier payments still assume automatic funding from the header account. The problem usually becomes harder and more expensive to fix as the settlement, testing, maturity or payment date gets closer.
Automation changes the shape of the risk rather than removing it. A wrong threshold, reference or bank detail can be processed consistently at scale, which makes pre-release validation and independent exception reporting essential.
Worked example: test the mechanics
A subsidiary is sold on Friday and leaves the cash pool. Its account normally starts each morning near zero because the pool funds payroll. If offboarding disables the sweep before the subsidiary receives standalone liquidity, Monday payments can fail despite a clean legal separation.
The figures are illustrative rather than universal terms. In a live case the team should replace every amount, date and threshold with current source evidence, then repeat the test before treating cash, consent or coverage as available.
Governance and control design
Use a participant cutover checklist that proves local funding, sweep cessation and intercompany balance settlement before the effective date. The procedure should also identify an independent reviewer and fallback owner so the control does not depend on one person being available.
A practical dashboard should monitor participants joining or leaving, cutover dependencies, final intercompany balances and post-change payment exceptions. Ageing and threshold trends show where risk is building before a single high-profile failure occurs.
The procedure should also explain what happens when the normal route fails. If the primary bank channel, approver or data source is unavailable, staff need a tested fallback that still preserves the core evidence and control.
Ownership should survive absence and staff turnover. The procedure for cash-pool participant onboarding and offboarding should state who acts, who reviews, where evidence is stored and how unresolved items are escalated when the normal owner is unavailable.
Documentation should be short enough to use under pressure. A one-page operating checklist can point staff directly to participant legal entity, account, pool agreement, sweep direction, target balance, effective date, intercompany account, local restrictions, final sweep and cutover confirmation while the full policy keeps the legal, technical or scheme background.
A separate control review should ask whether participants joining or leaving, cutover dependencies, final intercompany balances and post-change payment exceptions still predicts the real exposure after changes in volume, banking structure or financing terms. A dashboard can remain visually stable while risk migrates into an unmonitored field.
A strong control can also reduce unnecessary conservatism. Once participant legal entity, account, pool agreement, sweep direction, target balance, effective date, intercompany account, local restrictions, final sweep and cutover confirmation is reliable, treasury can distinguish genuine restrictions from assumptions and may release excess buffers, shorten manual review or use available funding more efficiently.
Editorial Verdict
BanksGB's editorial view is that cash-pool participant onboarding and offboarding should be managed as a practical cash-and-control issue. Adding or removing a legal entity from a cash pool changes bank sweeps, intercompany funding and local account liquidity, so the move requires more than a bank configuration request. The best process ties the rule to the actual amount, entity, timing and external status instead of relying on shorthand.
The final test is reproducibility. A second person should be able to explain what triggered the action, which evidence was used, who approved it, what happened outside the company and what remains outstanding. If that chain is not visible, the control around cash-pool participant onboarding and offboarding is weaker than it appears.
Sources
- Association of Corporate Treasurers, treasury resources: https://www.treasurers.org/
- Bank of England, Payment and settlement: https://www.bankofengland.co.uk/payments/payment-settlement