Financial Judgment · 5 min read

How to Build a 13-Week Cash Flow Forecast

Start with reconciled usable cash, then show receipts and payments in the week the money is expected to move. Roll each closing balance into the next opening balance. Label uncertain assumptions and compare the forecast with actual bank movements every week before extending the horizon.

Use cash movements rather than accounting profit

A cash forecast answers whether the business can make dated payments. It does not replace the profit and loss statement. An invoice can create revenue before the customer pays, and a prepaid expense can consume cash before the accounting cost is recognized. Build the forecast around receipts and payments, not recognized revenue and expense totals. Keep the accounting view beside it for context, but do not substitute profit for the bank balance when deciding whether an obligation can be met.

Establish a trustworthy opening balance

Reconcile the bank accounts you intend to include and note any uncleared transactions. Separate restricted cash or customer funds the business cannot freely spend. Use one consistent cutoff for the forecast so a payment is not included in both the opening adjustment and the first week. State the date of the balance visibly. A forecast can be carefully calculated and still wrong from its first row if the opening cash figure is stale or includes money unavailable for operations.

Build the receipts schedule from actual collection evidence

List receivables by customer, amount, expected receipt date, and the basis for that date. Check purchase-order requirements, invoice disputes, and approval steps that could delay collection. Add expected receipts from future work separately, with explicit assumptions about winning the work, delivery, invoicing, and payment. An unsigned proposal is not the same as an approved invoice. Keep uncertain inflows distinguishable so a reviewer can test the forecast without rebuilding the whole model.

Map payments by obligation and timing

Include payroll and related payments, suppliers, rent, debt service, taxes, equipment commitments, refunds, and owner distributions where applicable. Use actual due dates and payment terms. Distinguish committed obligations from spending that can be changed, while avoiding the assumption that every discretionary label means a payment can immediately disappear. Review notice periods and dependencies before modeling a saving. Your bookkeeper or finance lead can help reconcile the schedule to records and identify obligations that a simple bank export might miss.

Make the arithmetic simple enough to inspect

For each week, calculate opening cash plus receipts minus payments to get closing cash. Carry that balance into the following week. Keep transfers between included accounts out of operating receipts and payments so cash is not counted twice. Show totals and a control that reconciles the first actual week to the bank. Avoid hiding assumptions inside complex formulas. A forecast the team can inspect and update consistently is more useful than a sophisticated model maintained by only one person.

Show uncertainty through a few explicit scenarios

Build a base case from the most supportable current assumptions, then test specific changes such as a delayed major receipt or a slower sales conversion. Do not randomly reduce every line and call it a downside case. Each scenario should answer a decision question and identify what would make it more or less plausible. Compare the lowest cash balance and its timing across cases. That gives the team a basis for action without pretending the forecast can eliminate uncertainty.

Turn the low point into an action plan

An illustrative forecast might show $60,000 opening cash, $20,000 in receipts, and $35,000 in payments in the first week, leaving $45,000. That arithmetic says nothing about whether week eight is safe; follow the rolling balances through the whole horizon. When a low point appears, identify actions that change a specific receipt or payment before that date. Assign an owner and check that solving one week does not simply create a larger obligation just beyond the visible forecast.

Roll forward and explain the miss

At the weekly review, replace the completed week's estimates with actual cash movements. Separate timing differences from permanent changes: a receipt one week late is different from an invoice that will not be collected. Update future assumptions and add a new week at the end. Keep prior versions or a variance log so repeated forecasting mistakes remain visible. The forecast becomes a management tool when it improves decisions and collection evidence, not when it is rebuilt from scratch only during a crisis.

Try the decision

Use this fictional example to test the decision framework. All amounts and business details are illustrative; choose the action supported by the information provided.

Questions operators ask