Cash Flow Forecasting

Build direct and indirect cash forecasts for liquidity decisions.

D3 · Financial Modeling

Cash Flow Forecasting

Build direct and indirect cash forecasts for liquidity decisions.

Architecture Inputs Formula logic Worked example Controls Common errors Q&A

Model architecture

Use a 13-week direct cash forecast for near-term liquidity.
Use a monthly indirect forecast for medium-term planning.
Separate committed and probability-weighted flows.
Reconcile actual cash weekly.

A professional model should make the decision logic visible. Inputs belong in a controlled assumption area; calculations should be formula-driven; outputs should state units, dates and scenarios; checks should be obvious and actionable.

Core inputs

Bank balances
Collection forecast
Payroll and vendor runs
Taxes and debt service
Capex and financing

Evidence rule: historical figures should reconcile to approved financial statements or management data. Forecast assumptions should show an owner, date, source and rationale.

Formula logic

Relationship	Use
`Closing cash = Opening cash + Receipts − Payments`	Model formula / relationship
`Liquidity headroom = Cash + Undrawn committed facilities − Minimum cash`	Model formula / relationship

Use the formulas as design relationships, not as substitutes for the accounting policy, contract definition or transaction facts relevant to the model.

Practical example

The cash forecast flags a week-7 shortfall after a tax payment and inventory build, allowing the CFO to accelerate collections or draw a facility.

How to implement

Load the historical base and reconcile it.
Put assumptions in dedicated cells.
Build the schedule from operational drivers.
Link outputs to financial statements and dashboards.
Run base, upside and downside checks.

Control checks

Opening cash agrees with bank
Receipts map to customer ageing
Payments map to approved obligations
Restricted cash is excluded
Forecast-to-actual variance is reviewed

Finin2min crux: the model is credible only when a reviewer can trace a conclusion to evidence, assumptions and formula logic without guessing.

Common modeling errors

Relying only on EBITDA
Ignoring tax and debt dates
Treating uncommitted facilities as available cash
Not modelling downside collection delays
Failing to reconcile bank balances

Practical Q&A

Should the model contain all possible detail?

No. It should contain enough detail to answer the decision question and explain material risks. Excess detail can hide the drivers.

Should a formula ever contain a hardcoded number?

Only for constants that are genuinely universal or immaterial. Business assumptions should be linked to visible input cells.

What is the minimum review standard?

Reconcile historical data, test key formulas independently, scan for hardcodes and errors, verify scenario switches, and review outputs under downside assumptions.

Source framework: ICAI Ind AS resources, notified accounting standards, Schedule III presentation principles, transaction documents and approved management data. The linked workbook templates are educational starting points, not valuation opinions.