Cash Flow Forecast Template: Inputs, Scenarios and Review Cadence

A cash flow forecast template converts expected receipts and payments into a dated view of liquidity. It helps decision-makers see when cash may tighten, which assumptions drive the position and what actions require authorization before a shortfall becomes urgent.

The forecast is a planning model, not a bank balance guarantee. Customer behavior, payment timing, operational changes and financing availability can differ from assumptions. Use controlled source data, label uncertainty and keep treasury, finance and authorized leaders responsible for judgment and decisions.

Set the purpose, horizon and level of detail

Start with the decision the forecast must support: routine liquidity monitoring, payment planning, a financing discussion, growth investment or a recovery plan. Name the entities, bank accounts, currencies and restricted balances in scope. Do not combine cash that cannot legally or operationally be used as if it were freely available.

Choose a horizon that reaches beyond the relevant commitments. Near-term periods usually need transaction-level or category-level timing, while later periods may use broader drivers. A rolling weekly view can expose immediate pressure; a monthly extension can show seasonality and larger obligations. The right structure depends on volatility, data quality and governance.

Record the model owner, input owners, reviewer and authorized decision-maker. Define the cutoff time for updates and the version that will be discussed. One stable current version is more useful than several privately edited copies.

Copy this cash flow forecast template

CASH FLOW FORECAST CONTROL SHEET

Entity / accounts / currencies:
Forecast start / horizon / time buckets:
Model owner / reviewer / decision owner:
Version / data cutoff / update cadence:
Minimum liquidity threshold and authority:

PERIOD FORECAST
Period:
Opening available cash:

RECEIPTS
Customer collections — committed / expected / owner:
Other operating receipts — basis / timing:
Asset, tax or financing receipts — authorization / timing:
Total receipts:

PAYMENTS
Payroll and people costs:
Suppliers and operating costs:
Tax, interest and debt service:
Capital expenditure:
Other approved payments:
Total payments:

Net movement:
Closing available cash:
Headroom above threshold:

ASSUMPTION AND ACTION LOG
Assumption / source / owner / confidence / review date:
Scenario change / affected periods / impact:
Variance / explanation / corrective action:
Decision needed / options / owner / deadline:
Approval / date / evidence link:

Keep categories stable enough for comparison, but preserve enough detail to trace a number to its source. Add fields required by your treasury policy and remove lines that are genuinely irrelevant.

Establish the opening cash position

Reconcile opening cash to controlled bank or treasury records at the model cutoff. Separate available operating cash from restricted, pledged, trapped or otherwise unavailable balances. If accounts are in different currencies, preserve the native-currency figures and identify the approved exchange-rate source used for consolidation.

Timing matters. A ledger balance may include transactions not yet settled, while an online bank balance may exclude known obligations. Document how deposits in transit, outstanding payments, overdrafts and cash sweeps are treated. A reviewer should be able to bridge the opening forecast balance to the underlying records.

Use an audit evidence log template when source files, confirmations and approvals are distributed across controlled locations. Link to restricted evidence rather than copying sensitive account data into an open planning sheet.

Forecast receipts from observable drivers

Separate committed receipts from probability-weighted or judgmental expectations. For customer collections, begin with approved invoices, contractual terms, disputed amounts, recent payment behavior and account-owner input. A revenue target is not automatically a cash receipt forecast, and a signed order may still have delivery, acceptance or invoicing dependencies.

Group receipts by a driver that can be reviewed: customer cohort, invoice due date, recurring contract, tax refund, asset sale or approved funding event. Record the source, expected date, owner and uncertainty. Avoid false precision when the available evidence only supports a range.

Where sales discussions affect timing, keep the financial assumption traceable to the current commercial record. The client status report template shows a useful pattern for separating confirmed status, changes, risks and requested decisions.

Forecast payments with ownership and authorization

Build payments from payroll calendars, supplier due dates, tax schedules, debt agreements, approved purchase commitments and operating plans. Distinguish unavoidable contractual obligations from discretionary or not-yet-approved spending. Do not omit a valid liability merely because management hopes to defer it.

Assign an input owner to each material payment category. Confirm whether amounts include relevant taxes, fees, currency effects and settlement timing. For one-time items, preserve the approval and payment trigger. For recurring items, review whether the run rate remains reasonable rather than repeating the prior period automatically.

Connect unusual supplier or delivery uncertainty to a documented exception process. A delivery exception report template can help state what changed, the potential cash effect, the response owner and the next decision point.

Separate timing, amount and probability assumptions

Every forecast difference comes from some combination of timing, amount or occurrence. Keep these dimensions distinct. A receipt moving by two weeks is different from a customer paying only part of an invoice, and both differ from a deal no longer expected to close.

Maintain an assumption register with a source, owner, last-reviewed date and confidence label. Use ranges or scenarios where uncertainty is meaningful. Labels such as confirmed, evidence-based estimate and management judgment can be useful if the organization defines them consistently.

Do not hide a balancing adjustment in a miscellaneous line. If the model requires an explicit plug or unresolved amount, label it, explain why it exists and assign a deadline for resolution. Use a decision log for material choices about payment sequencing, financing actions or assumption overrides.

Build base, downside and action scenarios

A base case should reflect the current approved view, not the outcome people prefer. A downside case should change identified drivers such as collection delays, demand, costs or financing timing. An action case can then show the effect of authorized responses, such as rescheduling discretionary spend or pursuing approved funding options.

Avoid changing many variables without recording them. Create a scenario bridge listing each changed assumption, affected periods and incremental cash effect. Do not imply that an action is available until the responsible owner confirms feasibility, authority, cost and dependencies.

Assess both the lowest projected balance and the duration of pressure. A single positive closing figure can hide an intra-period payment problem, currency mismatch or restricted-cash issue. Treasury specialists should decide whether more granular modeling is required.

Compare forecast to actual cash movement

At each update, lock the prior forecast before replacing it. Compare actual receipts and payments with the version that was genuinely used for decisions. Classify variances by timing, amount, scope change, data error or assumption error, then assign follow-up where the cause may recur.

The budget variance report template provides a related structure for documenting baseline, actual result, explanation, owner and action. Keep cash variance analysis focused on settlement and liquidity rather than confusing it with accounting performance.

Repeated optimism in collection dates or underestimation of payments should lead to assumption changes, not just fresh explanations. Record forecast bias carefully, using enough observations to support a conclusion and preserving relevant context.

Set thresholds, triggers and decision rights

Define liquidity thresholds through the organization’s approved policy and financing arrangements. Pair each threshold with a clear action: enhanced monitoring, payment review, leadership escalation, lender engagement or another authorized response. Numeric triggers do not replace qualitative escalation where an event threatens continuity, compliance or trust.

Record who can approve payment timing changes, draw financing, move funds between entities or communicate externally. The model owner should not be assumed to hold those powers. Escalations should state the projected date, amount, assumptions, available options and latest useful decision time.

Treat financing capacity as conditional until confirmed under the relevant agreement and authorization. Qualified finance and legal reviewers should assess covenants, restrictions and disclosures where applicable.

Run a disciplined review cadence

Set a recurring forecast cutoff, owner submission time, model refresh, challenge review and decision meeting. Increase frequency when cash headroom narrows or major assumptions change. Event-driven updates may be needed after a delayed receipt, unexpected payment, operational disruption or financing decision.

Review meetings should focus on changed assumptions, threshold breaches, decisions and overdue actions rather than reading every row aloud. Capture only what is authorized and necessary, particularly where customer, payroll, bank or financing information is discussed.

For an authorized cash review with clear participant notice, Kuno can help produce draft notes and action items for human verification. It does not validate balances, approve assumptions or make treasury decisions. Explore Kuno

Protect the model and verify the output

Control edit access, formulas, source imports and version history. Separate input cells from calculations, use visible checks for broken formulas and prevent silent overwrites of approved assumptions. Sensitive payroll, customer and banking details should remain in appropriately restricted systems.

Before distribution, reconcile opening cash, test totals, inspect sign conventions and verify that scenario switches affect the intended periods. Confirm the reporting currency, timestamp, version and audience. A second qualified reviewer should challenge the largest and most uncertain drivers.

Use meeting follow-up practices to issue one reviewed action record after the forecast discussion. Archive the approved version and decision evidence under applicable retention rules.

Turn authorized liquidity discussions into a reviewable action trail. Kuno can support consented meeting capture and draft follow-ups, while finance owners remain responsible for source data, judgment and approvals. See Kuno

FAQ