13-week cash flow forecast planning gives a small business a week-by-week view of when money is expected to arrive, when bills must be paid and how low the bank balance could fall. Build it from actual cash dates rather than invoice or accounting dates, update it every week, and use cautious scenarios so a shortfall appears early enough to act.
This guide explains the complete process with a worked example and a practical review routine. It is general financial education, not accounting, tax, legal or lending advice; local rules and the right response to a cash shortage depend on your business and jurisdiction.
Table of Contents
What a 13-week cash flow forecast shows
A profit-and-loss statement answers whether the business earned more than it spent during an accounting period. A short-term cash forecast answers a different question: will enough cleared money be available on a particular day to pay employees, suppliers, rent, tax and loan installments?
The distinction matters because revenue is not cash. A completed project may be recognized as revenue now while the customer pays 30, 60 or 90 days later. Inventory, annual insurance or a tax payment can consume cash before the related expense appears clearly in a monthly performance report. The UK Insolvency Service notes that even a business trading effectively can run into trouble when it lacks ready cash to pay bills, and advises businesses to factor possible payment delays into planning.
Thirteen weeks is roughly one quarter: long enough to expose several payroll cycles, recurring bills and many customer payment terms, yet short enough for specific estimates. Canada’s Business Development Bank offers a 13-week cash flow calculator for this same short-term planning horizon. Thirteen is not a magic number. If the cash cycle is longer, extend the model; the British Business Bank recommends forecasting at least as far ahead as that cycle lasts.
Set up a simple weekly worksheet
Use one column per week and one row per cash category. A spreadsheet is sufficient for many small businesses because formulas recalculate after an assumption changes. Accounting or forecasting software can help when transaction volume, entities or currencies make a spreadsheet hard to control, but the underlying structure stays the same.
- Opening cash: usable balances in operating accounts at the start of the week.
- Cash receipts: customer collections, cash sales and dependable non-sales inflows.
- Cash payments: payroll, suppliers, rent, tax, debt service, software, marketing, equipment and other outflows.
- Net cash movement: total receipts minus total payments.
- Closing cash: opening cash plus net movement.
- Minimum threshold: the lowest balance management is willing or permitted to carry.
Keep inputs separate from formulas. For example, record each unpaid invoice with its amount, due date, expected payment week and confidence level on an assumptions tab. Summarize those records into the weekly forecast. This makes an estimate traceable and prevents someone from replacing a formula with a convenient number.
Build the forecast in seven steps
1. Confirm the opening bank balance
Start with reconciled, accessible cash. Exclude customer funds held in trust, restricted grants, deposits you cannot spend and unused credit limits. Account for checks or transfers already issued but not yet cleared. If separate accounts are genuinely available for operations, include them on distinct rows so a transfer is visible rather than counted as new income.
2. Schedule customer receipts
Place money in the week it is realistically expected to clear, not the invoice date and not automatically the due date. Review the customer’s payment history, approval process, purchase order requirements and any dispute. A large invoice labeled “net 30” may belong in week six if that customer usually pays two weeks late.
Separate confirmed receivables from pipeline sales. A signed order with an agreed billing milestone is more dependable than a proposal under discussion. Probability-weighting an uncertain deal can produce false precision; a clearer approach is to omit it from the base case and add it to an upside scenario.
3. Add dependable non-sales inflows
Include a loan draw, owner contribution, grant, tax refund or asset-sale proceeds only when the amount and timing are sufficiently reliable. Do not use an unsigned financing application as if it were cash. Label financing separately from trading receipts so management can see whether operations are supporting themselves.
4. Map operating payments by due date
Begin with payroll, supplier commitments, rent, utilities, insurance and recurring subscriptions. Then add variable spending tied to expected work: materials, shipping, contractors, card processing and commissions. Use the actual payment calendar. A monthly total can hide a problem when payroll leaves on Monday and a customer transfer arrives Friday.
Review purchase orders, contracts, card statements and the accounts-payable ledger rather than relying on memory. If approved automation sends reminders or moves invoice data, apply the permissions, logging and rollback controls described in Globe Onward’s secure workflow automation guide.
5. Include debt, tax and owner transactions
Add loan principal and interest when they leave the account, along with sales, payroll, income or other tax payments required in your jurisdiction. Include owner draws, dividends or distributions as cash outflows even when they are treated differently in the accounts. Ask a qualified accountant which amounts and dates apply; a generic model should never guess a tax obligation.
6. Calculate net movement and closing cash
For each week, subtract total payments from total receipts. Add the result to opening cash to obtain closing cash, then carry that closing balance into the next week’s opening row. Include a formula check: next week’s opening balance must equal the prior week’s closing balance. A difference signals a broken reference or an unrecorded transfer.
7. Mark the decision threshold
A forecast is more useful when it triggers action. Set a minimum cash threshold that reflects near-term payroll, essential supplier commitments and any lender requirement. Highlight the first week that falls below it. Also show available headroom separately; an overdraft or revolving facility is a financing resource, not part of the bank balance.
Read a worked four-week example
Suppose a small service company starts with 18,000 in its home currency and wants to keep at least 8,000 available. The first four weeks of its base case look like this:
| Cash line | Week 1 | Week 2 | Week 3 | Week 4 |
|---|---|---|---|---|
| Opening cash | 18,000 | 15,500 | 15,000 | 6,500 |
| Customer receipts | 7,000 | 12,000 | 4,000 | 15,000 |
| Other inflows | 0 | 0 | 0 | 0 |
| Total payments | 9,500 | 12,500 | 12,500 | 9,000 |
| Net movement | -2,500 | -500 | -8,500 | 6,000 |
| Closing cash | 15,500 | 15,000 | 6,500 | 12,500 |
The company never reaches zero, but week three breaches its 8,000 threshold. That warning is the point of the model. Management can investigate the 12,500 of payments, follow up on invoices due before week three, seek a deposit on new work or discuss a financing buffer before the shortage becomes urgent. It should not simply move a committed payment to a later column without agreeing new terms.
Test base, downside and upside scenarios
The base case should represent the most supportable timing, not the most hopeful outcome. Copy it into a downside case and change a few material assumptions: a major customer pays two weeks late, sales are lower, a supplier requires a deposit or equipment needs repair. Use an upside case for signed work that may start sooner or a receivable that may clear early.
Avoid changing every line by the same percentage. Cash risk is usually driven by specific events and dates. Stress the largest receipts, payroll, tax deadlines, inventory purchases and single-source suppliers first. Record each changed assumption next to the scenario so the result can be explained.
When a downside case crosses the threshold, rank responses by speed, cost and operational effect. Faster invoicing, fixing rejected invoices, collecting a deposit or pausing discretionary purchases may be less damaging than expensive emergency credit. If borrowing may be needed, early discussion gives a lender more context and gives the owner time to compare terms. The U.S. Small Business Administration’s business finance guidance also emphasizes proper bookkeeping, available cash, accounts receivable, accounts payable and bank reconciliation as core financial controls.
Turn the forecast into a weekly operating habit
Choose one review day and assign one owner. Replace last week’s estimates with actual receipts and payments, reconcile the opening balance, add a new week at the far end and revise future timing from current evidence. Keep the horizon at 13 weeks rather than letting it shrink.
- Reconcile bank and payment-platform balances.
- Compare forecast receipts and payments with actual results.
- Explain material differences by timing, amount or omission.
- Update customer collection dates and supplier commitments.
- Roll the model forward by one week.
- Review the lowest projected balance and threshold breach.
- Assign actions, owners and deadlines for material risks.
Track forecast accuracy without punishing honest updates. A large variance can expose a weak billing process, stale sales assumptions or missing expense approvals. The aim is to improve decisions, not force actual results to resemble an old forecast. Small teams may connect approved reminders or accounting exports using tools discussed in Globe Onward’s guide to small-business automation tools, but a responsible person should still approve assumptions and investigate exceptions.
Avoid common forecasting mistakes
- Using invoice dates as receipt dates: schedule the cash when it is realistically expected to clear.
- Mixing profit with cash: depreciation is not a payment, while loan principal and asset purchases do consume cash.
- Counting sales pipeline as certain: keep unsigned or timing-sensitive deals in a separate scenario.
- Forgetting irregular outflows: annual insurance, tax, bonuses, equipment and renewals can create the lowest week.
- Hiding transfers or borrowing in revenue: label them separately so operating performance remains visible.
- Ignoring access control: the file may contain payroll, customer and bank information; restrict sharing and protect version history.
- Updating only during a crisis: stale forecasts lose credibility precisely when decisions become urgent.
- Silently delaying bills: changing a spreadsheet date does not change a contractual due date.
The British Business Bank’s forecasting guide stresses that the model should be updated regularly as estimates become more exact. Treat that revision as a control, not an admission that the first version failed.
Use this implementation checklist
- Choose the 13 weekly column dates and one consistent week-ending convention.
- Reconcile opening cash and exclude restricted balances.
- List invoices individually with realistic collection weeks.
- Separate confirmed receipts from sales opportunities.
- Map payroll, suppliers, tax, debt, owner transactions and irregular costs.
- Calculate net movement, closing cash and the week-to-week roll-forward.
- Define and highlight a minimum operating threshold.
- Create named base, downside and upside assumptions.
- Assign a weekly owner, review date and variance process.
- Limit file access and preserve an auditable version history.
- Agree actions before the first projected shortfall.
- Ask an accountant or adviser to review material tax, financing or solvency concerns.
Make the forecast useful before it is perfect
A credible short-term forecast does not predict every transaction exactly. It makes timing assumptions visible, identifies the lowest cash week and gives the business time to change course. Start with the largest receipts and unavoidable payments, then improve detail as the weekly review reveals where estimates are weak.
The key discipline is simple: forecast cash dates, compare them with reality and act before the balance reaches the danger point. When the model is reconciled, scenario-tested and owned by a named person, it becomes a practical operating tool rather than a spreadsheet opened only when money is already tight.


