How do you measure cash flow forecast accuracy?

Compare each forecast to what actually happened, per period and category. Common metrics are forecast variance (actual minus forecast, in currency and %), MAPE (mean absolute percentage error) across periods, bias (whether you systematically over- or under-forecast), and hit rate (how often you land within a tolerance). Track them over time and, crucially, break them down by horizon and category so you know exactly where the forecast is reliable.

What is a good cash forecast accuracy?

There's no universal number — it depends on horizon and business. Short-horizon direct forecasts should be quite accurate (low single-digit percentage error); longer horizons will be looser by nature. Rather than chase a target percentage, aim for a forecast that is unbiased, improving over time, and accurate enough at each horizon to support the decisions it drives.

Why measure cash forecast accuracy?

Because a forecast you don't measure is a forecast you can't trust or improve. Measuring accuracy tells you which horizons and categories are reliable (so you know when to act on the forecast), surfaces systematic bias, and points to the specific inputs — a particular entity, a category like collections — that need fixing. It turns forecasting from a ritual into a discipline that gets better.

How to Measure Cash Forecast Accuracy

Measure cash forecast accuracy by comparing each forecast to what actually happened, per period and category, using metrics like variance, MAPE, bias and hit rate — then break the results down by horizon and category. That breakdown is the point: an overall accuracy number is nearly useless, but knowing that your one-week forecast is tight while your collections forecast is chronically optimistic tells you exactly what to trust and what to fix. A forecast you don't measure is one you can neither trust nor improve — which is why forecast accuracy sits among the core treasury KPIs.

Why measure it at all

Two reasons. First, trust: if you don't know how accurate the forecast is, you can't know when to act on it — and treasury making funding decisions on an unmeasured forecast is guessing with extra steps. Second, improvement: measurement points at the specific inputs that are wrong, so forecasting becomes a discipline that gets better over time instead of a monthly ritual nobody believes.

The metrics

Forecast variance. The basic building block: actual minus forecast, in currency and as a percentage, for each period. Positive and negative variances tell different stories.
MAPE (mean absolute percentage error). The average of the absolute percentage errors across periods. Because it uses absolute values, offsetting errors don't cancel out, so it measures real dispersion, not luck.
Bias. The average signed error — are you systematically over- or under-forecasting? Bias is the most fixable problem: a forecast that's consistently 10% high can be corrected; one that's randomly wrong is harder.
Hit rate. How often the forecast lands within an agreed tolerance (say ±5%). An intuitive, decision-oriented view: "we're inside tolerance four weeks in five."

Break it down by horizon and category

This is where measurement earns its keep. A single "our forecast is 88% accurate" hides everything useful. Break it down:

By horizon. Accuracy should be high at one week and looser at three months. Measuring per horizon tells you how far out the forecast is still decision-grade — and stops you judging a long-range view by short-range standards (or vice versa).
By category. Split collections, supplier payments, payroll, tax, treasury flows. Almost always, one or two categories drive most of the error — often collections, because customer timing is hard. Now you know precisely where to invest.
By entity / region. In a group, one entity's poor inputs can dominate the total. Per-entity accuracy points at who needs help.

Turning measurement into improvement

Measurement is only worth it if it changes something:

Find the biggest contributor. Which horizon, category or entity accounts for most of the error?
Diagnose it. Bias (fixable with a correction and a root cause) or noise (fix the input data or process)?
Fix the input, not the number. If collections are always optimistic, the fix is better collections data or assumptions — not a fudge on the total.
Re-measure. Confirm the change actually improved accuracy, and move to the next contributor.

Run that loop for a few cycles and the forecast quietly becomes something treasury can act on.

What usually goes wrong

Only tracking a headline number. No horizon or category breakdown, so you know you're wrong but not where.
Chasing a target percentage. Fixating on "95% accurate" instead of "unbiased, improving, and good enough at each horizon for the decisions it drives."
Not closing the loop. Measuring accuracy and filing the report, without feeding it back into better inputs.
Ignoring bias. Living with a forecast that's systematically off because the average error "looks small" — when a consistent bias is the easiest thing to correct.

Measure against actuals, break it down by horizon and category, fix the inputs behind the biggest errors, and your forecast stops being a number people quietly distrust.

Part of the Corporate Cash & Liquidity Management guide. See also cash positioning vs forecasting and direct vs indirect forecasting. The newsletter sends one finance-systems pattern, product decision or build lesson every two weeks.