Cash Flow Forecasting

Your P&L showed a $200K profit in March. Your bank balance dropped by $180K, and the CFO wants to know why. The answer: a large customer paid late, a vendor was paid early, and two payroll runs landed in the same week. Cash flow forecasting exists because profit and cash are different problems, and confusing them is expensive. Cash flow forecasting is the process of projecting the timing of cash inflows and outflows over a defined future period, usually weekly, monthly or on a rolling 13-week horizon. A P&L forecast estimates revenue and expense on an accrual basis; a cash flow forecast tracks when money actually moves into and out of the bank account. A company can be profitable on paper and still run out of cash, particularly when customers pay 60 or 90 days after the invoice date while vendors and employees are paid much sooner. Cash flow forecasting lets treasury and finance manage that timing gap before it turns into a liquidity problem. It is one of the most operationally important forecasts in finance, and one of the most underbuilt, because it needs data from AR, AP, payroll and banking systems that often don't connect to each other.

How cash flow forecasting differs from P&L forecasting

A P&L forecast records revenue when it is earned and expense when it is incurred, regardless of when cash changes hands. A cash flow forecast records inflows when customers pay and outflows when the company pays, which almost never line up with the accrual entries. Three timing gaps cause most of the surprises. The first is the AR timing gap: revenue is recognized on invoice date, but cash arrives 30, 60, or 90 days later depending on payment terms and customer behavior. The second is the AP timing gap: expenses are recorded when a bill is received, but cash goes out when the bill is paid, which may be 30 or 45 days later if the company manages its own payment timing. The third is the payroll timing gap: payroll is a large periodic outflow that doesn't line up with revenue cycles, and months with three payroll runs instead of two produce visible cash dips that the P&L doesn't show. A well-built cash flow forecast captures all three gaps explicitly. It starts from the accrual forecast and applies payment timing assumptions, usually based on historical days sales outstanding for AR and DPO for AP, to translate the income statement into an expected cash position.

What makes a cash flow forecast reliable

A cash flow forecast is only as reliable as the inputs from the three contributing systems. The AR aging report drives inflow timing: if it is stale, or if large customer payments are expected but not confirmed, the forecast overstates inflows. AP data drives outflow timing: if the AP team is holding invoices or paying early outside normal terms, the forecast loses accuracy unless those decisions are reflected. Payroll is usually more predictable, but it adds variability when bonuses, commissions or off-cycle runs aren't planned for in advance. The most common structural problem is a forecast built in a spreadsheet that is updated by hand from each system instead of connected to live data. A CFO reviewing a 13-week cash forecast on Tuesday afternoon may be looking at AR aging from the prior Friday, and if a large customer paid on Monday, the forecast is wrong before it's presented. If you want a reliable cash forecast, either connect your forecasting tool to live system data or set a disciplined weekly refresh with a named owner for each data feed.

How platforms handle it

Treasury management systems and FP&A forecasting platforms both advertise cash flow forecasting, but they approach it differently. Treasury platforms focus on the short term, usually 13 weeks or less, and prioritize bank connectivity and real-time cash position. FP&A platforms focus on the medium term, monthly and quarterly, and prioritize integration with the income statement forecast and budget. A 'connected' cash flow forecast in either case means changes to the operational forecast (revenue, payroll headcount, capital spending) flow through to the cash projection automatically instead of being keyed in by hand. In practice, 'connected' often means connected to the spreadsheet version of the operating plan, not to live AR aging and AP data. When you evaluate platforms, ask specifically: when a large invoice is paid in the AR system, does the cash forecast update automatically? When payroll is finalized in the HRIS, does that outflow appear without manual entry? The answers tell you whether the forecast is actually connected or depends on an analyst's weekly data refresh.

Questions to ask

• Is the cash flow forecast connected to live AR aging data, or based on a manual weekly pull?
• How are large one-time outflows (capex purchases, tax payments, debt service) captured in the forecast?
• Does the forecast separate operating, investing, and financing cash flows, or does it show a single net cash position?
• What is the refresh cadence, and who owns the data inputs from AR, AP, and payroll?
• Is the short-term (13-week) cash forecast reconciled against the longer-term (quarterly) forecast to ensure they don't contradict each other?
• How are scenario assumptions handled? Can the team model a 'slow pay' scenario where DSO extends by 15 days?

The mistakes that undermine cash flow forecasts

The most common cash flow forecasting mistake is building the forecast in a spreadsheet disconnected from the AR aging report. When customer payment timing is estimated from historical averages instead of the actual open invoice aging, the forecast misses the most important variable: which specific invoices are about to be paid and which are at risk of slipping. The second mistake is not separating operating, investing and financing cash flows. When all outflows are lumped together, you can't tell a cash dip caused by a one-time capital purchase from a structural decline in operating cash generation, and those two situations call for very different responses. The third mistake is not stress-testing the forecast against late payments. If the business's three largest customers all pay 30 days late in the same period, is there enough liquidity? Forecasting only the expected case leaves the CFO without a plan for the scenario most likely to cause trouble.

Direct against indirect method

The direct method builds the forecast from expected receipts and payments, which is what treasury needs for weekly liquidity decisions. The indirect method starts from forecast profit and adjusts for non-cash items and working capital movements, which is how annual and statutory cash flow views are produced. The two answer different questions and will not reconcile line by line.

Comparing planning platforms

Planning platforms separate on who can maintain the model after go-live, which is a staffing question as much as a software one. Once cash flow forecasting is settled as a requirement, read the Forecasting Software category guide for how the market splits, then weigh the Anaplan profile against the Pigment profile on that requirement rather than on the feature list. Our Anaplan pricing breakdown records what the vendor publishes and what is quote-based. The Anaplan against Pigment comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the forecasting ROI calculator so the business case is written down before a vendor writes it for you.

Cash Flow Forecasting questions

Related terms

Budget vs Actual Variance, Capital Expenditure (CapEx), and Driver-Based Planning come up in the same workflow as cash flow forecasting, and the rest of the planning platforms cluster is indexed in the finance operations glossary.