Skip to main content

Market-neutral small-business guide

How to Build a 13-Week Cash-Flow Forecast

Prepare, reconcile, run and refresh a dated 13-week cash-flow forecast without treating it as an accounting profit statement.

Prepare one consistent 13-week basis

Record-to-review sequence

  • Name the decision, Week 1 cut-off, 13-week horizon, currency and indirect-tax treatment. (not complete)
  • Reconcile available opening cash to bank and ledger records; exclude unavailable balances. (not complete)
  • Map each receipt to its realistic bank date and label its evidence state or confidence assumption. (not complete)
  • Map payroll, suppliers, tax, debt and other payments separately; do not hide timing by netting. (not complete)
  • Add funding only as an explicit scenario action, never as an assumed rescue. (not complete)
  • Roll all 13 weeks and record first negative week, first buffer breach and peak gap. (not complete)
  • Compare the baseline, a downside receipt date and one available action without silently changing other inputs. (not complete)
  • Reconcile forecast to actual, explain variance, roll the horizon and assign an action owner and review date. (not complete)
Map records to scenario inputs
Record or evidenceForecast inputCheckpoint
Bank and ledger reconciliationOpening available cashSame cut-off date; unavailable cash excluded
Invoice, order, contract and current correspondenceReceipt amount, week and confidenceExpected bank date is explicit; uncertain receipts remain visible
Payroll calendar, supplier bills, tax and debt schedulesPayment amount and weekEach obligation appears once on a realistic date
Approved facility or documented commercial actionFunding or timing actionAvailability, cost and authority checked outside the forecast

Read the engine-derived default scenario

Selected weeks from the public 13-week fixture

The fixture starts with 65,000 currency units, uses a 25,000-unit buffer and moves a 2,000-unit receipt from Week 3 to Week 5. All displayed outputs below are generated by the same forecast engine as the tool.

Selected weekly roll-forward rows
WeekOpening cashExpected receiptsPaymentsClosing cashBuffer gap
Week 165,00011,4009,20067,2000
Week 355,4009,4009,20055,6000
Week 557,10011,6009,20059,5000
Week 745,9009,60027,20028,3000
Week 1310,7009,6009,20011,10013,900
Engine summary: Week 13 closing cash 11,100 currency units; first negative week None; first buffer breach Week 10; peak buffer gap 14,300 currency units.
Forecast-versus-actual rolling checkpoints
CheckpointCompareRecord the outcome
Opening cashPrior closing forecast versus reconciled bank cashVariance and reconciliation owner
ReceiptsExpected date and confidence versus bank receipt dateTiming or amount variance; revised evidence state
PaymentsForecast amount/date versus settled amount/dateCause, recurrence and next-week effect
Horizon rollRemove completed week and add a new Week 13Updated first breach, peak gap and action owner

Route the finding without duplicating the calculator

Choose the next owner from the identified driver
FindingNext workflowBoundary
Exact weekly dates create the gap13-Week Cash-Flow ForecastCalculates the scenario; does not predict payment
Receivables, inventory or payables consume cashWorking Capital PlannerBalance-date scenario, not a weekly schedule
Collection-day assumptions drive receivablesReceivables Collection Impact PlannerAggregate scenario, not invoice-level collection advice

13-week forecast questions

Is receipt confidence a probability forecast?
No. It is a user-controlled scenario label or weighting. Preserve the underlying evidence and also run a clear downside date rather than presenting the percentage as predictive certainty.
Should several assumptions change at once?
Start with one change against the reconciled baseline so its effect remains visible. Add combined scenarios only after retaining each intermediate result.
When should the forecast be refreshed?
Refresh it when actual cash, receipt evidence, payment dates or an approved action changes, and at the chosen rolling-review cadence. Do not invent a future receipt merely to remove a gap.

Methods and supporting context

Change history

  1. โ€” Initial public release of the article after pre-launch factual, editorial, source and presentation review.