🧠 Introduction "cash forecasting" is two different jobs
Cash forecasting gets overloaded. Sometimes you need control (what will our bank balance be next Friday?). Other times you need explanation (why is cash down even though profit is up?). Direct and indirect approaches solve different problems, which is why teams argue about which is “right.”
Direct forecasting is the operational view: it builds a cash projection model from receipts and payments. It’s naturally aligned with near-term liquidity and payment decisions. Indirect forecasting is the financial performance view: it translates forecast P&L into cash via working capital, capex, and financing. It’s naturally aligned with management reporting and longer-term planning.
If your team is already building receipts and payments logic,this article will help you place it in the right horizon and governance model so it stays reliable under weekly pressure.
🧭 Framework pick the method using the "T-D-D" test (timing, data, decisions)
Use the T-D-D test:
- Timing: Do you need to manage when cash moves (not just how much)? If yes, direct forecasting is usually required.
- Data: Do you have reliable operational inputs (invoice aging, payroll calendar, AP schedule, inventory buys)? If yes, direct can be accurate. If not, indirect may be safer until you improve data discipline.
- Decisions: What decision is the model serving payment prioritisation, runway, budgeting, or value creation? Indirect is great for “why” and planning; direct is great for “when” and control.
Most teams land on hybrid: direct for near-term, indirect for mid/long-term. The quality bar is reconciliation: your methods should be consistent, not competing. Hybrid works best when it fits into a broader statement logic (so cash, working capital, and profit narratives stay aligned).
🛠️ Step-by-step implementation
Step 1: 🎯 Define the cash question (runway, timing risk, or cash generation?)
Start by naming the cash question. Examples:
- “Will we breach our minimum cash buffer in the next 8–12 weeks?”
- “Can we fund growth without raising capital?”
- “Why is cash down despite revenue growth?”
If the question is runway or near-term liquidity, build (or prioritize) a direct weekly cash flow forecast model. If the question is cash generation drivers, build an indirect monthly view that explains changes via working capital, reinvestment, and taxes.
This step prevents the most common mistake: teams build an indirect model, then try to use it to manage timing risk. That’s how you end up surprised by payroll, vendor batches, or delayed collections.
If you’re operating with tight buffers, make runway a first-class output. It forces discipline around timing and creates an action-oriented discussion (collections, spend gates, funding options).
Step 2: 🧾 Assess input readiness (what you can forecast reliably today)
Direct forecasting needs operational inputs. Before building, confirm you can refresh:
- AR aging and expected collection timing,
- AP schedule and payment terms,
- Payroll calendar, tax payments, and recurring charges,
- Inventory and major purchase orders (if relevant).
If those inputs are unreliable, direct forecasting becomes “best guesses weekly,” which damages trust quickly. In that case, start with an indirect cash flow projection model and improve operational inputs in parallel.
Indirect forecasting needs financial forecast discipline: consistent revenue/margin forecasts and a credible working capital and capex bridge. The biggest failure is treating working capital as a plug.
Collections are usually the swing factor. If you need one operational upgrade that improves both direct and indirect forecasting, start with a structured way to forecast collections from invoices (terms + ageing buckets + payment behavior).
Step 3: 💸 Build the direct method for near-term control (receipts and payments)
Direct forecasting is a driver-based cash forecasting model: cash in and cash out, by week (often 13 weeks). Build it in layers:
- Base balance (current cash),
- Receipts (collections, other inflows),
- Disbursements (payroll, vendors, taxes, debt service),
- Net movement and ending balance.
The strength is timing: you can see “cash cliffs” weeks in advance. The risk is data quality. Keep categories simple at first (top 10–20 drivers) and expand only when accuracy improves.
If your cash outflows include inventory buys, the timing logic can dominate accuracy. Modeling inventory cash timing (PO timing, lead times, reorder cycles) is often the difference between a forecast that “looks right”and one that prevents surprises.
Step 4: 🧠 Build the indirect method for mid/long-term insight (profit → cash bridge)
Indirect forecasting translates forecast performance into cash. A simple structure:
- Start with operating profit,
- Apply tax assumptions,
- Adjust for non-cash items (if needed),
- Model working capital changes (AR, AP, inventory),
- Subtract capex and add financing as applicable.
The value is explanation: it helps leadership understand why cash is moving and what operational levers drive it (payment terms, inventory turns, margin). It also scales better across horizons because it’s tied to forecast drivers.
But indirect can hide timing risk. A monthly indirect view can show “positive cash this quarter” while you still have a payroll-driven dip next week. That’s why many teams pair indirect monthly with a direct weekly overlay. If you need to bridge horizons cleanly, standardize how monthly assumptions translate into weekly timing.
Step 5: ✅ Run hybrid without duplication (one set of assumptions, two decision views)
Hybrid is the practical end state: a direct weekly cash flow forecast model for control and an indirect monthly view for steering. The non-negotiable requirement is consistency: shared assumptions, clear ownership, and a reconciliation habit (weekly review + monthly roll-up).
Avoid “two spreadsheets, two truths.” Centralize key assumptions (payment terms, collection curves, major spend gates) so updates flow to both views. That keeps leadership from choosing the forecast they like best.
This is where Model Reef can support the workflow subtly: instead of maintaining separate files for direct and indirect views, a structured modeling layer can keep one set of drivers feeding multiple outputs (weekly liquidity and monthly performance-to-cash), reducing version sprawl and making the cash flow modeling process easier to audit.
🏢 Real-world use case scaling from "cash anxiety" to controlled visibility
A fast-growing services business starts with an indirect monthly cash flow forecast model because they have strong P&L forecasting but limited AR timing discipline. Leadership understands why cash is tightening (working capital drag), but they still get surprised by weekly timing.
Finance then builds a direct 13-week view focused on the biggest swing items: collections from top customers, payroll cycles, and vendor batches. Over time they improve invoice aging discipline and add a collection curve model, which increases accuracy without adding complexity.
The hybrid setup changes behavior: weekly meetings focus on actions (collections outreach, payment timing, spend gates), while monthly reviews focus on structural improvements (terms, billing policies, inventory practices). As seasonality becomes visible, they layer in seasonal adjustments so the forecast reflects reality instead of “average months”.
🚫 Common mistakes choosing a method based on preference, not purpose
The most common mistake is using indirect forecasting to manage near-term timing risk. It explains cash, but it doesn’t control timing unless you explicitly model it. The second mistake is building direct forecasting without reliable inputs creating a fragile weekly cash projection model no one trusts.
Teams also fail to reconcile hybrid views, which creates leadership confusion (“which one is right?”). And many models ignore working capital reality, turning the indirect bridge into a plug.
Finally, some teams treat forecasting as separate from budgeting, so their cash view and their plan diverge. Aligning cash forecasting cadence and assumptions with budgeting/reforecast rhythm reduces contradictions and makes decisions faster.
🚀 Next steps choose your method, then standardize reconciliation
If you need near-term control, prioritize a direct weekly cash forecasting model focused on receipts and payments. If you need longer-term insight, build an indirect monthly view that explains profit-to-cash conversion and highlights structural levers like working capital and reinvestment. In most operating businesses, hybrid becomes the steady state.
Next, tighten the operational driver models that improve both approaches. For direct forecasting, start with receipts and payments logic that reflects real timing. For indirect forecasting, make the working capital bridge defensible and consistent.
To keep building, use the operational-driver guide for receipts and payments forecasting and the cadence selection guide so your weekly and monthly views stay aligned.
Back