A physical cash pool creates intercompany balances when participant accounts sweep to or from a header account, so groups need a policy for allocating interest and economic benefit. 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
A physical cash pool creates intercompany balances when participant accounts sweep to or from a header account, so groups need a policy for allocating interest and economic benefit. Treasury should turn the concept into a repeatable decision because the consequence normally appears in cash timing, funding capacity or control.
The in-house bank or treasury centre may apply internal debit and credit rates, spreads or service charges, but the method should reflect legal ownership, transfer-pricing policy and the actual balance history. The team should use the current source document or bank configuration rather than copy a conclusion from a previous period that may have had different facts.
How the process works
The operating sequence should move from identification to validation, approval, external submission or notice, and then confirmation. For this topic, the critical mechanics are: The in-house bank or treasury centre may apply internal debit and credit rates, spreads or service charges, but the method should reflect legal ownership, transfer-pricing policy and the actual balance history.
Timing should be planned backwards from the required result. Notice periods, value dates, bank cut-offs and internal approval windows can make a technically correct action late, so the process needs enough recovery time to repair data or obtain another consent. For this subject, the file should specifically reconcile daily participant balances, intercompany positions, external bank interest, internal debit rate, internal credit rate, treasury spread, tax policy and settlement frequency. Those fields are not interchangeable with a generic approval record because they are the facts that determine whether this particular transaction remains inside the agreed rule.
The data and evidence that matter
The review file should contain daily participant balances, intercompany positions, external bank interest, internal debit rate, internal credit rate, treasury spread, tax policy and settlement frequency. Keeping those items together allows a second person to reconstruct the decision without searching multiple inboxes or relying on memory.
The record should distinguish internal intention from external outcome. An approved instruction proves what the company wanted to do; a bank acknowledgement, lender consent, statement entry or counterparty confirmation proves what happened outside the company.
Where the process can fail
A group can centralise cash efficiently but create unexplained value transfers if profitable subsidiaries receive no credit for surplus cash or borrowers are charged inconsistent rates. The financial cost of the problem usually increases as the payment, settlement, test date or financing event gets closer.
Repeated emergency fixes are evidence of weak process design. If users regularly need manual overrides, management should repair the timetable or configuration rather than normalise the exception.
Worked example: test the mechanics
Subsidiary A contributes an average £6 million surplus while Subsidiary B borrows £4 million from the pool. If treasury earns 4% externally but pays A 2% and charges B 6% without policy support, the retained spread needs a clear economic and transfer-pricing rationale.
The example is intentionally simplified. In a live case the business should replace every illustrative amount, date and threshold with current source evidence, then repeat the test before treating cash, consent or hedging capacity as available.
Governance and control design
Document the internal pricing methodology and reconcile allocated interest to daily intercompany balances and external bank economics. Evidence should sit beside the transaction so later review can separate a deliberate approved exception from a control that was simply missed.
Useful oversight includes internal interest by participant, treasury spread and unexplained differences versus the approved pricing policy. This turns policy into an operating discipline with a measurable trigger for management attention.
Change control matters as much as daily operation. When a bank changes a service, a facility is amended, an entity joins the group or a system is migrated, the company should retest the process from source data through final reconciliation. The management signal for this topic is internal interest by participant, treasury spread and unexplained differences versus the approved pricing policy. That indicator should have an owner and escalation threshold so treasury can intervene while the exposure is still manageable rather than discovering the problem only after the external deadline.
Contingency planning should be proportionate to value and urgency. The team should know the alternate approver, funding route, bank contact or manual fallback before a live cash-pool interest allocation issue becomes time-critical.
Documentation should be short enough to use under pressure. A one-page operating checklist can point staff to daily participant balances, intercompany positions, external bank interest, internal debit rate, internal credit rate, treasury spread, tax policy and settlement frequency while the fuller policy keeps the legal, technical or scheme background.
The company should also define a clear escalation trigger around internal interest by participant, treasury spread and unexplained differences versus the approved pricing policy. Reporting becomes useful only when a threshold leads to a named decision, owner and deadline rather than producing another number that nobody acts on.
Repeated overrides should not be normalised. If the same workaround appears each month, the issue is no longer exceptional; it is evidence that the timetable, data model, authority design or bank configuration needs to change.
Editorial Verdict
BanksGB's editorial view is that cash-pool interest allocation should be managed as a practical cash-and-control issue. A physical cash pool creates intercompany balances when participant accounts sweep to or from a header account, so groups need a policy for allocating interest and economic benefit. The best process links the rule to the amount, entity, timing and external status rather than 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 the external party did and what remains outstanding. If that chain is not visible, the control is weaker than it appears. The control should also be tested against the article's core failure scenario: A group can centralise cash efficiently but create unexplained value transfers if profitable subsidiaries receive no credit for surplus cash or borrowers are charged inconsistent rates. A practical review should demonstrate how the company would recognise that condition early, stop or redirect the transaction, and preserve evidence of the decision.
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