Cash Forecast Operating Model & Ownership
A cash forecast is a process, not a spreadsheet. Who owns it, who contributes, at what cadence, and how the forecast-to-actual loop is run — the operating model behind a forecast people trust.
A cash forecast that nobody trusts is almost always a forecast that nobody owns — a spreadsheet updated from sources of unknown reliability, by people who don't feel accountable for it. Treasuries pour effort into forecast methodology — direct vs indirect, the 13-week horizon, variance metrics — and comparatively little into the operating model that produces it: who contributes what, when, and who's accountable when it's wrong. Yet that's what decides whether a forecast is a trusted decision input or a number people quietly work around. This is how to run the forecast as a process, not a document.
The forecast is a process with many owners
The first reframe: treasury owns the forecast; treasury doesn't own the inputs. The receivables view comes from credit and collections. The payables from procurement and AP. Capex, payroll, tax, financing — each from its own owner. The revenue picture from the business. Treasury owns the model, the consolidation and the outcome, but the raw material comes from people treasury doesn't manage.
That split is the whole problem and the whole solution. The failure is treasury being held accountable for a forecast built entirely from numbers it can't control and nobody else feels responsible for. The fix is an operating model that makes each contributor accountable for their own input — so accuracy is owned where it can actually be improved, not pooled into a treasury total nobody outside treasury cares about.
The forecast operating model, as a table
An operating model answers four questions for every input: who provides it, at what cadence, in what form, and who's accountable for its accuracy. Written down, it looks like this:
| Element | The decision it fixes |
|---|---|
| Contributors | Who provides each input (receivables, payables, capex…) |
| Cadence | How often each input is refreshed, and by when |
| Format & horizon | The categories and time buckets everyone submits against |
| Consolidation | Who assembles the whole and owns the model |
| Use | Which decisions the forecast drives (and at what cadence) |
| Feedback loop | Who compares forecast-to-actual and routes it back |
| Accountability | Who owns the accuracy of each input, not just the total |
The row that's almost always missing is the last one. Without named input-level accountability, "the forecast is wrong" has no owner — it's everyone's problem and therefore no one's, and it never gets better.
Treasury owns the total; the contributors own the parts. A forecast where treasury is accountable for numbers it can't control, and the people who can control them aren't accountable, is broken by design — no methodology fixes that.
The forecast-to-actual loop: the engine of accuracy
An operating model without a feedback loop is just an org chart. The loop is what makes the forecast improve: each period, compare forecast against actual, broken down by category and contributor, and route the variance back to the person accountable for that input.
This is the operating side of measuring forecast accuracy: the metric tells you where the error is; the operating model decides what happens next. Two things make the loop work:
- Attribution. The variance has to be traceable to a contributor and a category, or "the forecast was off" can't be acted on. A pooled error number improves nothing.
- Routing. The feedback goes to the person who can fix the input, not just into a treasury report. A contributor who never sees their own bias never corrects it.
Persistent bias — a contributor reliably optimistic, a category reliably late — is the easiest error to fix once it's visible and owned. The loop is what makes it both.
Cadence: match the forecast to the decisions
A forecast's cadence should follow the decisions it drives, not a habit. The short-horizon 13-week forecast that drives funding and liquidity decisions needs a weekly rhythm; a longer strategic view moves more slowly. The operating model sets each contributor's refresh cadence to the decision cadence, so the forecast is current when a decision is made — not perpetually a week behind because inputs arrive late.
The anti-pattern is a single monthly forecast cycle serving decisions that happen weekly, so treasury is always managing a stale picture and patching it manually between cycles.
What usually goes wrong
- Treasury owns everything. Held accountable for a forecast built from inputs it can't control, with no contributor accountability.
- No named contributors. Inputs arrive from "the business" — unreliably, in different formats, whenever.
- No feedback loop. Variance measured (maybe) but never routed back, so the same errors recur every cycle.
- Pooled error. "The forecast was 8% off" with no attribution, so nobody can or does improve their piece.
- Cadence mismatch. A monthly cycle feeding weekly decisions, so the forecast is always stale.
What I would decide
Run the forecast as a named process, not a spreadsheet someone owns by default. Make each contributor accountable for their own input's accuracy — that single move does more for forecast quality than any methodology change, because it puts accountability where the error can actually be fixed. Build the forecast-to-actual loop with real attribution and routing, so bias becomes visible to the person who can correct it. And set cadence to decisions, not to the calendar. A trusted forecast isn't a better spreadsheet; it's an operating model where everyone who touches it owns their part of it.
Part of the Corporate Cash & Liquidity Management guide. See also how to measure cash forecast accuracy and the 13-week cash flow forecast. The newsletter sends one finance-systems pattern, product decision or build lesson every two weeks.
Frequently asked questions
Who owns the cash forecast?
Treasury owns the forecast as a whole — its accuracy, its process and its use — but treasury rarely owns the inputs. The receivables forecast comes from credit/collections, the payables from procurement/AP, the capex and payroll from their owners, the revenue view from the business. So ownership is layered: treasury owns the model and the outcome; each contributor owns their input and its accuracy. The failure mode is treasury 'owning' a forecast built from numbers it can't control and nobody else feels accountable for — which is why the operating model has to make each contributor accountable for their piece, not just treasury accountable for the total.
What is a cash forecast operating model?
It's the defined process behind the forecast: who contributes which inputs, at what cadence, in what format; who consolidates and owns the whole; how the forecast is used to make decisions; and how forecast-to-actual variance is measured and fed back to improve the inputs. A forecast without an operating model is a spreadsheet someone updates when they remember, from sources of unknown reliability, that nobody quite trusts. With one, it's a repeatable process with named contributors, a real cadence, and a feedback loop that makes it better over time — the difference between a number people act on and one they quietly work around.
How do you improve cash forecast accuracy over time?
By running a forecast-to-actual loop as part of the operating model, not as an occasional audit. Each period, compare what was forecast against what actually happened, broken down by category and contributor, so you can see where the error is and whose input it came from. Persistent bias — a contributor always optimistic, a category always late — is the easiest thing to correct once it's visible and owned. The key is that the feedback goes back to the contributor accountable for that input, not just into a treasury report nobody outside treasury reads. Accuracy improves when the person who can fix an input sees their own error and owns it.