Cash forecast variance analysis: learn why the forecast was wrong before rebuilding it

Variance analysis compares forecast cash movements with what actually reached the bank, then explains the difference rather than simply replacing the old forecast. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What cash forecast variance analysis means in practice

Variance analysis compares forecast cash movements with what actually reached the bank, then explains the difference rather than simply replacing the old forecast. This matters operationally because an internal plan can still fail when the external bank, lender or counterparty applies the governing rule.

Useful analysis separates timing differences from permanent value differences because a late £1 million receipt creates a different decision problem from a receipt that will never arrive. That wording should be translated into a short internal test showing the trigger, deadline, decision owner and evidence required for the business to proceed.

How cash forecast variance analysis works from start to finish

Start by assembling forecast date, actual value date, expected amount, actual amount, currency, business owner, variance reason, revised date and whether the cause is recurring. These fields define the actual transaction and reveal whether a missing approval, timing condition or data point can stop the process before cash moves.

Next, identify the last safe decision point rather than only the formal deadline. A rejected file, missing consent or data query can consume hours or days, and a business that plans to the final cut-off has no recovery margin. For cash forecast variance analysis, the specific checkpoint is this: Review material variances weekly, assign causes to business owners and feed recurring timing patterns back into the next forecast model.

The data and evidence that matter

Evidence should show both the decision and the external outcome. For cash forecast variance analysis, retaining only an approval email is weak if the important fact is a bank status, lender consent, value date or counterparty confirmation that arrived later.

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 cash forecast variance analysis, that distinction prevents a temporary workaround from becoming an undocumented permanent practice. In this workflow, the supporting record should cover forecast date, actual value date, expected amount, actual amount, currency, business owner, variance reason, revised date and whether the cause is recurring.

Where the process can fail

Without reason codes, management sees that the forecast missed by £4 million but cannot tell whether sales collections are deteriorating, payroll timing changed or a one-off acquisition payment moved. The financial exposure can grow quickly when the issue is discovered close to settlement, drawdown or payment day.

Automation introduces a different failure mode. A system can process an incorrect instruction consistently and at scale, so validation should occur before transmission and exception reporting should be independent of the originating process.

Worked example: test the mechanics

Treasury forecast Friday closing cash of £6.2 million but actual cash is £3.9 million. A £1.5 million customer receipt moved to Monday and £800,000 of tax paid one day earlier than forecast. The £2.3 million gap is mostly timing, so the corrective action is different from a permanent £2.3 million 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 cash forecast variance analysis

Review material variances weekly, assign causes to business owners and feed recurring timing patterns back into the next forecast model. The procedure should identify the primary owner, reviewer and escalation contact so an absence does not suspend a material payment or funding decision.

Exception data should feed back into process design. Repeated repairs, late approvals or unexplained differences are evidence that the operating model needs attention, not just isolated mistakes.

Contingency planning should be proportional to the amount and time sensitivity. Treasury should know the alternate approver, payment route, funding source or bank contact before a live cash forecast variance analysis issue becomes urgent.

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 cash forecast variance analysis is safest when the difference is explicit before the transaction proceeds. The reason for that discipline is concrete: Without reason codes, management sees that the forecast missed by £4 million but cannot tell whether sales collections are deteriorating, payroll timing changed or a one-off acquisition payment moved.

A useful challenge question is whether the transaction would still be safe if without reason codes, management sees that the forecast missed by £4 million but cannot tell whether sales collections are deteriorating, payroll timing changed or a one-off acquisition payment moved. Where that answer is uncertain, review material variances weekly, assign causes to business owners and feed recurring timing patterns back into the next forecast model.