Local vs central treasury bank accounts: decide which cash should stay near the business

Local operating accounts support day-to-day business activity, while central treasury accounts concentrate liquidity, funding and group-level banking control. 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

Local operating accounts support day-to-day business activity, while central treasury accounts concentrate liquidity, funding and group-level banking control. Treasury should turn the idea into a repeatable operating rule because the practical consequence normally appears in liquidity, compliance or control.

The right design balances payment timing, regulatory or tax restrictions, local customer needs, banking services and cash concentration rather than moving every balance centrally by default. Current transaction facts matter because a small change in entity, date, notional or service setup can change the result.

How the process works

The operating sequence should move from identification to validation, approval, external action and confirmation. For this topic, the critical mechanics are: The right design balances payment timing, regulatory or tax restrictions, local customer needs, banking services and cash concentration rather than moving every balance centrally by default.

Timing should be planned backwards from the required result. Notice periods, value dates, processing windows and internal approval deadlines can make a correct action operationally late, so the workflow needs a repair margin.

The data and evidence that matter

The working file should contain legal entity, account purpose, local payment needs, collections, regulatory restrictions, sweep ability, overdraft, treasury funding route and target operating balance. Keeping those fields together lets another reviewer reproduce the decision without relying on memory.

The record should distinguish internal intention from external outcome. An approved request proves what the company wanted to do; a bank acknowledgement, lender confirmation, statement entry or reconciled transaction proves what actually happened.

Where the process can fail

Over-centralisation can create local payment failures, while excessive decentralisation leaves idle cash and weakens group visibility. The problem normally becomes harder and more expensive to fix as the payment, settlement, test date or financing deadline approaches.

Repeated emergency workarounds are evidence that the design is weak. If the same override appears every month, management should repair the process instead of normalising the exception.

Worked example: test the mechanics

A subsidiary needs £600,000 each Monday for local payroll and tax but otherwise collects surplus cash. Leaving £3 million permanently local is inefficient, while sweeping to zero can create Monday funding risk. A target balance and scheduled central funding can balance the two objectives.

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 hedge coverage as available.

Governance and control design

Classify accounts by operating purpose and set documented local liquidity buffers before applying central concentration rules. The evidence should sit beside the transaction so later review can distinguish an approved exception from a missed control.

Useful oversight includes cash held locally versus approved operating needs and surplus cash available for concentration. This turns the policy into an operating discipline with a measurable escalation point.

A post-event review should identify whether an exception came from data, timing, authority, system design or misunderstanding of the external rule, then assign remediation that can be tested in the next cycle.

Ownership should survive absence and staff turnover. The procedure for local vs central treasury bank accounts should state who acts, who reviews, where evidence is stored and how unresolved items are escalated.

Documentation should be short enough to use under pressure. A one-page operating checklist can point staff directly to legal entity, account purpose, local payment needs, collections, regulatory restrictions, sweep ability, overdraft, treasury funding route and target operating balance while the fuller policy keeps the legal, technical or product background.

The business should set an escalation trigger around cash held locally versus approved operating needs and surplus cash available for concentration. Reporting becomes useful only when a threshold leads to a named decision, owner and deadline rather than another number in a monthly pack.

Repeated overrides should not be normalised. If the same workaround appears month after month, the issue is no longer exceptional; it is evidence that the timetable, data model, authority design or bank setup needs to change.

Follow-up should be driven by the subject's actual control measure, cash held locally versus approved operating needs and surplus cash available for concentration, rather than by a generic ageing note. If the measure is outside tolerance, the case should remain visible until remediation is complete.

The control owner should review the case again before the next external deadline and confirm that the amount, legal entity, approval status and latest external evidence still agree with the intended treatment.