Cash Flow Forecasting Is Broken. Here's How to Rebuild It.

Ask ten finance teams how they forecast cash and you'll get ten versions of the same broken process: a spreadsheet, updated when someone remembers, producing a single number for the end of the month that's already wrong by the second week. When cash is comfortable, nobody notices. When cash is tight—exactly when the forecast matters most—the spreadsheet becomes a source of anxiety rather than insight.

The fix isn't a fancier model. It's a different structure entirely.

Direct beats indirect when cash is tight

The first decision is method. Indirect forecasting starts from projected net income and works back to cash through balance sheet changes. It's fine for long-range planning, but it's useless for managing the next eight weeks because it abstracts away the actual timing of money moving.

When liquidity matters, you want a direct forecast: actual expected receipts and disbursements, by week, by category. When is that big customer's payment actually going to land—not when is it due, but when does that customer actually pay? When does payroll hit? When are the tax payments, the debt service, the large vendor disbursements? The direct method forces you to confront real timing, which is the only thing that matters when you're managing to a minimum cash balance.

Thirteen weeks is the right horizon

The 13-week rolling forecast has become the standard for a reason. It's long enough to see the cliffs coming—a quarterly debt payment, a seasonal working capital swing—and short enough that the assumptions are still grounded in reality. Beyond 13 weeks, you're guessing. Inside it, you can actually plan.

"Rolling" is the operative word. Each week you drop the week that just closed, add a new week 13, and reforecast. The discipline of doing this weekly is what keeps the forecast honest. A 13-week model you build once and abandon is worse than no forecast, because it gives you false confidence.

Build it on drivers, not on last month plus a guess

The forecasts that hold up are driver-based. Instead of guessing total collections, you model collections off your AR aging and historical payment behavior by customer. Instead of guessing payables, you model disbursements off your open POs and payment terms. Revenue receipts trace back to your sales pipeline and billing cadence.

When you build on drivers, two things happen. The forecast gets more accurate because it's grounded in operational reality. And when leadership asks "what if our largest customer slips 30 days," you can answer in minutes by flexing one assumption instead of rebuilding the whole model.

The feedback loop is what makes it learn

Here's the step almost everyone skips: comparing the forecast to what actually happened, every week, and asking why they diverged. Did collections come in slower than modeled? Your payment-behavior assumptions need tightening. Did a disbursement land in a different week? Your timing logic needs work.

This variance analysis is where forecasting stops being a chore and becomes an instrument that gets sharper over time. After a few cycles of disciplined comparison, your forecast accuracy inside the first four weeks should be tight enough to manage real decisions against. This is also where machine learning genuinely helps—payment-timing prediction off historical behavior is exactly the kind of pattern-matching that models do well, layered on top of, not instead of, your driver logic.

What good looks like

A finance team with a healthy cash forecast can answer three questions on any given day: what's our cash position going to be each week for the next quarter, what are the specific risks to that picture, and what happens to it under a downside scenario. They can answer because the forecast is direct, driver-based, rolled weekly, and tuned against actuals.

That's not a fancier spreadsheet. It's a discipline supported by the right structure. Get the structure right and cash forecasting stops being the thing you dread and becomes the thing that lets you sleep.