Direct vs Indirect Cash Flow Forecasting for Treasury
Direct forecasting builds cash bottom-up from expected receipts and payments — accurate, short-term, operational. Indirect derives it from projected financials — longer-term, strategic. Which to use, over what horizon, and how to combine them.
Direct cash flow forecasting builds cash bottom-up from expected receipts and payments; indirect forecasting derives it top-down from projected financial statements. Direct is accurate over short horizons and built for operational liquidity decisions — it works from concrete flows like collections, payroll and debt service. Indirect suits longer-term strategic planning — it starts from projected profit and balance-sheet movements, trading day-to-day precision for reach. Most treasuries use both, at different horizons.
Direct forecasting: bottom-up
Direct forecasting adds up the actual cash movements you expect: receipts from customers, payments to suppliers, payroll, tax, interest, dividends, treasury flows. Because it's built from concrete, near-term items, it's accurate over short horizons and speaks the language of operational treasury — it tells you when a gap appears next week and how big it is, so you can fund or invest with confidence.
Its limits are effort and reach: forecasting individual flows gets impractical the further out you go, and its quality depends directly on the source data (AR, AP, payroll) and the discipline of the people feeding it.
Indirect forecasting: top-down
Indirect forecasting starts from the projected financials — the forecast P&L and balance sheet — and works cash out from them (profit, adjusted for non-cash items and changes in working capital, debt and capital). It's the natural method for longer horizons and strategic questions: funding needs over the year, covenant headroom, the cash impact of the plan. It's less precise about timing — it won't tell you Thursday's position — but it reaches where a direct forecast can't.
Comparison
| Direct | Indirect | |
|---|---|---|
| Built from | Actual expected receipts & payments | Projected P&L and balance sheet |
| Direction | Bottom-up | Top-down |
| Horizon | Short (days to weeks/months) | Medium to long (quarters+) |
| Accuracy / timing | High, precise timing | Lower timing precision |
| Best for | Operational liquidity, funding decisions | Strategic planning, funding, covenants |
| Effort | High per period, data-dependent | Leverages existing financial plans |
Which method for which horizon
- Short term (days–weeks): direct. You need timing and accuracy to manage liquidity and funding.
- Medium to long term (quarters–year+): indirect. Forecasting individual flows isn't feasible; derive cash from the financial plan.
- The overlap: in the medium term the two coexist, and their views should broadly reconcile — a large gap between them is a signal worth investigating.
Combining them
The strongest treasury forecasting runs both and joins them up: the direct short-term forecast anchors to today's actual cash position and drives operations; the indirect long-term forecast frames funding and strategy; and they meet in the middle, where a reconciliation between the bottom-up and top-down views exposes errors in either. Comparing what you forecast against what actually landed — forecast accuracy — is how you learn which horizons and categories to trust.
What usually goes wrong
- Using one method for everything. Forcing direct forecasting out to a year (impractical, low quality) or judging short-term liquidity on an indirect view (no timing).
- No reconciliation. Running direct and indirect in isolation, so nobody notices when they disagree.
- Ignoring data quality. A direct forecast is only as good as the AR/AP/payroll data feeding it; garbage in, confident-looking garbage out.
Match the method to the horizon, reconcile them where they overlap, and measure accuracy so you know where the forecast earns trust.
Part of the Corporate Cash & Liquidity Management guide. See also cash positioning vs forecasting and measuring forecast accuracy. The newsletter sends one finance-systems pattern every two weeks.