
A 13-week cash flow forecast shows the bank balance a business expects at the end of each week for roughly the next quarter. It starts with cash available, adds receipts expected to reach the bank and subtracts payments expected to leave. The weekly view helps an owner see a shortfall while there is still time to act.
The forecast is a management tool. It does not replace the profit and loss statement, balance sheet or statutory cash flow statement.
Why use 13 weeks?
Thirteen weeks is long enough to include several customer collection cycles, payroll runs and supplier payment dates. It is also short enough for the first few weeks to be based on invoices, payment schedules and known commitments.
A monthly forecast can hide timing pressure inside the month. A business may appear comfortable at month-end even though salaries, rent and a large supplier payment fall before a major customer receipt. Weekly columns make that gap visible.
Start with a reconciled opening balance
Choose the first day of the forecast and reconcile the opening cash figure to the bank records. Include only funds the business can actually use. If an account is restricted, pledged or maintained for a separate purpose, show it separately.
List each bank account when this helps the team understand where the money sits. The final summary can combine available balances, provided transfers between accounts are not counted as external receipts or payments.
Build the receipts schedule
Use expected collection dates, not invoice dates. Start with the receivables ageing and review each material invoice with the person responsible for collection.
Classify receipts by confidence:
- Confirmed receipts supported by a payment commitment
- Expected receipts based on normal customer behaviour
- Uncertain receipts that need follow-up
- New sales that have not yet been invoiced
Keep uncertain amounts visible, but do not let them support the base forecast without a reasonable collection assumption. A large overdue invoice may deserve its own line so that the owner can see the effect of a further delay.
Other receipts might include advances, refunds, asset sales or financing that is sufficiently certain. Record each amount in the week it is expected to reach the bank.
Add payments by the week cash will leave
Build the payments section from the payables ledger, payroll records, contracts and the compliance calendar. Useful groups include:
- Supplier payments
- Salaries, incentives and reimbursements
- Rent, utilities and recurring subscriptions
- Loan instalments and finance costs
- Tax and statutory payments
- Capital expenditure
- Owner withdrawals or distributions, where relevant
- One-off professional, legal or project costs
Separate committed payments from amounts that the business may reschedule. The distinction helps when the forecast shows a low point. Any change to a supplier date should still respect the contract and applicable payment requirements.
Avoid spreading a large payment evenly across several weeks unless the agreement actually permits instalments. The forecast should show the timing risk as it exists.
Calculate the weekly closing balance
For each week, use a simple structure:
Opening cash + receipts − payments = closing cash
The closing balance becomes the next week’s opening balance. Add a minimum operating buffer if the business needs one. The forecast should flag the first week that falls below that buffer, even if the balance remains positive.
A compact table may use these rows:
| Forecast row | Week 1 | Week 2 | Week 3 |
|---|---|---|---|
| Opening cash | |||
| Customer collections | |||
| Other receipts | |||
| Total receipts | |||
| Supplier payments | |||
| Payroll and overheads | |||
| Tax and other commitments | |||
| Total payments | |||
| Closing cash |
Continue the same format through week 13.
Test a base case and a downside case
The base case should reflect the team’s best current estimate. Add a downside case for risks that could materially change the lowest cash week.
Examples include:
- A major customer paying later than expected
- Sales collections falling below the base estimate
- A supplier requiring earlier settlement
- An unplanned repair or project cost
- A financing receipt moving to a later week
Change a few meaningful assumptions instead of reducing every receipt by an arbitrary percentage. The downside case should answer a practical question: how much cash would the business need, and by which week, if the identified risk occurs?
Decide what action follows from the forecast
When the model shows pressure, record the action beside the affected week. The response may include collecting a specific overdue invoice, adjusting discretionary spending, changing the timing of an approved purchase or discussing payment timing with a supplier.
If additional funding may be required, the forecast helps define the amount and timing before the need becomes urgent. Funding decisions need their own assessment of cost, terms and repayment capacity.
Assign each action to one person with a date. Otherwise the forecast becomes a report that describes a problem without changing it.
Update the forecast every week
After the week ends:
- Replace the forecast figures with actual receipts and payments.
- Explain material differences.
- Update the assumptions for the remaining weeks.
- Add a new week at the end so the model stays at 13 weeks.
- Reconfirm the lowest projected balance and open actions.
Keep the prior version or a change log. Forecast accuracy improves when the team can see whether errors came from late collections, missing payment information or unrealistic assumptions.
Common mistakes
A forecast becomes unreliable when it starts with an unreconciled bank figure, uses invoice dates as collection dates, omits irregular payments or counts unapproved finance as available cash.
Another common problem is excessive detail. A small business can group routine low-value items while listing large and uncertain cash movements separately. The model should be detailed enough to support a decision and simple enough to update every week.
How ProTax can help
ProTax’s Financial Reporting & MIS service can support the reporting structure behind cash planning, including management reports, cash views and variance analysis. The business still needs an internal owner for collection dates, purchase commitments and operating decisions.
Prepare the latest bank balances, receivables ageing, supplier schedule, payroll estimate and known one-off payments before the first review. These records provide a usable starting point for the forecast.
Frequently asked questions
Is 13 weeks compulsory?
No. It is a practical short-term planning horizon. A business with seasonal or long project cycles may also need a longer monthly forecast alongside the weekly model.
Should GST or other taxes appear in the forecast?
Include tax payments expected to leave the bank during the forecast period. Use the business’s current compliance calendar and reviewed calculations rather than a generic estimate.
Can a spreadsheet handle the forecast?
A spreadsheet is often sufficient for a small business if the inputs have clear owners and the file is updated consistently. Software becomes more useful when the business has many bank accounts, entities or transactions and needs automated data feeds.
