Intraday liquidity management for corporates: the closing balance does not show the whole day

Intraday liquidity is the cash available during the business day to meet payments before later receipts or sweeps replenish the account. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What intraday liquidity management means in practice

Intraday liquidity is the cash available during the business day to meet payments before later receipts or sweeps replenish the account. The safest approach is to treat the concept as a live control point rather than as terminology understood only by specialists.

A company can finish the day with a healthy positive balance and still suffer failed or delayed payments if large outflows occur before incoming funds arrive. A practical procedure should say exactly who checks the condition, when it is tested and where the supporting record is retained.

How intraday liquidity management works from start to finish

Operationally, the team needs opening balances, timed payment queues, expected receipt windows, intraday overdraft limits, sweep times, high-value payment cut-offs and emergency funding routes. That information links the commercial requirement to the bank or lender outcome and to the eventual accounting entry.

Sequence matters. Treasury should know what must happen before commitment, what can happen in parallel and what evidence proves completion, because reversing an external payment or contractual commitment may be difficult or impossible.

The data and evidence that matter

Auditability is strongest when the internal case number links the source data, approval, instruction and final response. That avoids the common problem of reconstructing a material cash event from separate inboxes after the original staff have moved roles.

An effective record should also make the exception path visible. If the normal rule cannot be met, the team should capture who approved the deviation, how long it applies and what evidence will close it. For intraday liquidity management, that distinction prevents a temporary workaround from becoming an undocumented permanent practice.

Where the process can fail

Payroll, tax or acquisition payments can hit early while customer receipts or intercompany funding arrive later, temporarily pushing the account below its usable limit. The financial exposure can grow quickly when the issue is discovered close to settlement, drawdown or payment day.

Another common weakness is status confusion: teams treat 'submitted', 'approved', 'accepted' and 'settled' as if they mean the same thing. For cash control, those states must remain distinct until the final outcome is evidenced.

Worked example: test the mechanics

An account opens with £3 million. A £5 million tax payment is due at 10:00, while £4 million of customer receipts normally arrives around 14:00. The projected closing balance is positive, but the company still needs at least £2 million of intraday funding or a different payment sequence to avoid the morning shortfall.

This example is a method rather than a universal rule. The business should replace every illustrative figure with its own contractual terms, bank data and dates, then test the result before assuming that cash or authority is available.

Governance and controls for intraday liquidity management

For time-critical days, build a time-of-day cash view rather than relying only on opening and closing balances. A reviewer should be able to see the rule, the data used and the final status in one case file without rebuilding the chronology from emails.

Controls should be reviewed when the business changes size or complexity. What was acceptable for one entity and a handful of transactions may be weak once the group has multiple banks, currencies and approval layers.

Training should use real examples from the company's own workflow. Staff remember why a control exists more reliably when they can see how a missing field, late notice or wrong status could affect actual cash.

Decision records should separate three layers: what the governing document or payment scheme allows, what the bank or counterparty operationally supports, and what internal policy permits. Those layers can produce different answers, and intraday liquidity management is safest when the difference is explicit before the transaction proceeds. For intraday liquidity management, the specific checkpoint is this: For time-critical days, build a time-of-day cash view rather than relying only on opening and closing balances.

Where that answer is uncertain, for time-critical days, build a time-of-day cash view rather than relying only on opening and closing balances. This makes the control decision-focused: staff know what evidence is sufficient, what is still unresolved and which person can accept an exception. The resulting record should be short enough to use during a live deadline but detailed enough for finance, audit or a replacement treasury colleague to reconstruct the reasoning later. Before approving a material intraday liquidity management action, the reviewer should challenge the assumption most likely to change the cash outcome rather than merely confirm that every box has been ticked.