13-Week Cash Flow Forecast: A Step-by-Step Guide

The 13-week cash flow forecast is the most useful document most finance teams do not produce. It answers one question the monthly management accounts cannot: will we have enough money in the bank on any given Friday for the next three months? Profitable businesses fail on that question, and the ones that survive tight periods are almost always the ones that could see the pinch coming six weeks out. This guide sets out how to build a 13-week rolling forecast properly — the structure, the weekly discipline, the mistakes that make forecasts useless, and who in a finance team should own it.

Why thirteen weeks

Thirteen weeks is a quarter, expressed in the unit that matters for cash: weeks, not months. The horizon is long enough to see a problem while you can still do something about it — chase a debtor, delay a purchase, arrange facility headroom, talk to a lender before you need to — and short enough that the numbers can be built from actual knowledge rather than assumption. Beyond thirteen weeks, weekly cash forecasting becomes guesswork dressed as precision; inside it, a well-built forecast is close to a factual document. The rolling part matters equally: each week you drop the week just completed and add a new week thirteen, so the horizon never shortens and the discipline never lapses into an annual exercise nobody trusts by March.

Cash is not profit — the reason this exists

The distinction every founder eventually learns the hard way: profit is an accounting measure of performance over a period; cash is money in the bank on a date. A business can invoice £200,000 in a strong month, book the profit, and be unable to pay wages because the invoices are on sixty-day terms and the payroll is on the 28th. Timing is the whole game, which is why a cash forecast is built from when money actually moves rather than when revenue is recognised. If your management accounts show a healthy month and your bank balance disagrees, the gap between them is working capital — and the 13-week forecast is how you manage it deliberately rather than reactively.

Step 1: Start with the bank, not the ledger

Open the forecast with the actual cleared bank balance at the start of week one, across every account. Not the ledger balance, not the balance including uncleared items — the money genuinely available. Everything downstream builds from this number, and starting from a ledger figure that includes cheques not yet cleared or transfers in transit introduces an error that compounds through the whole forecast. Where the business has a facility, note the headroom separately: available cash and available funding are different things, and the forecast should show both.

Step 2: Build receipts from the debtor ledger, not from sales

This is where most forecasts go wrong. Cash receipts are not next month’s sales — they are the collection of invoices already raised, plus a realistic estimate of new invoices raised and collected within the window. Take the aged debtor listing, and for each significant invoice put the cash in the week you genuinely expect it, not the week the terms say it is due. Those are different weeks for most customers, and the difference is the single largest source of forecast error. Two disciplines help: track each major customer’s actual payment behaviour (a customer who has paid at day 52 for two years will not pay at day 30 because the invoice says so), and split the ledger — large customers modelled individually, the long tail estimated in aggregate from historical collection patterns.

Step 3: Build payments from commitments

Payments divide into three kinds, and the reliability differs sharply. Fixed and known: payroll, PAYE and NIC, VAT, rent, loan repayments, insurance — these are diarised and near-certain, and they should be entered on the actual payment dates, including the awkward ones (a quarterly VAT payment landing in week seven changes the picture entirely). Committed but variable: supplier payments from the aged creditor listing, entered by expected payment week. Discretionary: capital expenditure, recruitment, marketing — the payments you can move, which is precisely why they should be identified separately, since they are the levers you will pull if a week looks tight. A forecast that mixes all three into one row is much less useful than one that shows what is fixed and what is choosable.

Step 4: Lay out the thirteen weeks

The structure is simple and should stay simple: opening balance, receipts by category, payments by category, net movement, closing balance — carried forward as the next week’s opening balance, across thirteen columns. Add two rows underneath that do most of the useful work: facility headroom (closing balance plus available facility) and lowest point in the week if intra-week timing matters — a business that closes Friday at £40,000 but dips to £5,000 on Wednesday when payroll clears has a Wednesday problem the weekly closing balance conceals. Keep the categories few enough to maintain: six receipt lines and a dozen payment lines is plenty for most businesses, and a forecast with sixty rows will be abandoned within a month.

Step 5: Make it roll — the weekly routine

The forecast earns its value in the weekly update, not the initial build. Each week, ideally on the same day: enter the actual receipts and payments for the week just gone; compare them to what you forecast and note the variances; update the following twelve weeks with what you now know; and add a new week thirteen. The variance step is what turns a spreadsheet into a discipline — a forecast that is never compared to actuals never improves, and the pattern of misses is where the learning sits (a particular customer always a fortnight late, a category consistently understated). The whole routine should take a competent finance person an hour or two once the model is built. If it takes a day, the model is too complicated and will be quietly dropped.

Step 6: Add scenarios — but only two

Scenario analysis in cash forecasting has a strong tendency toward elaborate uselessness. Two variants are enough for most businesses. A downside case: your largest customer pays thirty days late, or a major receipt slips a month — the specific, plausible thing that would hurt, not a generic percentage haircut. And a stress case: what combination of events would take the business below zero, and in which week? The value of the second is not the number but the answer to the follow-up question — what would we do, and how much notice would we need? A business that knows its breaking point and its response is in a fundamentally different position from one that does not, which is the argument our guide to cash flow management in a downturn develops in more depth.

The mistakes that make forecasts useless

Five recur constantly. Forecasting receipts from sales rather than collections — the error that produces optimistic forecasts and unpleasant Fridays. Using due dates instead of expected dates — the same error in a different costume. Omitting the lumpy items — VAT, corporation tax, annual insurance, the bonus payment; these are known months in advance and are exactly what sinks an otherwise sound week. Too much detail — a model with a row per customer and per supplier is unmaintainable, and unmaintained forecasts are worse than none because they carry false authority. And no variance review — producing the forecast without ever asking why last week was wrong, which guarantees it stays wrong. A sixth, subtler failure: treating the forecast as a finance document rather than a management one. It should be discussed weekly with whoever can act on it, or it is arithmetic nobody reads.

Who should own it

This is the question the software vendors never answer, and it matters more than the tooling. In a small business the forecast is typically owned by the Finance Manager or the fractional finance lead — and where a founder is doing it personally in a spreadsheet at weekends, that is usually the clearest signal the business has outgrown its finance resource. In a mid-sized business it sits with the Financial Controller, who owns working capital alongside the close. Where the business is investor-backed, covenant-reporting or under genuine cash pressure, the forecast becomes a board-level artefact and the Finance Director owns its presentation while the FC owns its construction. In every case, one named person should be accountable for the weekly update — forecasts owned by committee are updated by nobody. If your business needs this discipline and has no one with the time or experience to run it, that is a hiring conversation rather than a software one: an interim or fractional finance professional can build the model and establish the routine in a matter of weeks, and hand over something the team can maintain.

Spreadsheet or software?

For most businesses, a well-built spreadsheet is entirely adequate and preferable — it is transparent, cheap, and everyone can interrogate it. Dedicated cash forecasting tools earn their cost when the business has multiple entities or currencies, high transaction volumes making manual entry impractical, or a need to integrate directly with the accounting system and bank feeds so the actuals populate themselves. The honest test is whether the weekly update is taking too long: if a competent person can run it in an hour, stay in the spreadsheet; if the manual data-gathering has become the bottleneck, automate. Whichever route, build it so someone other than its author can pick it up — the cash forecast is precisely the wrong model to have a bus-factor of one, as our guide to forecasting systems for controllers covers.

A worked structure

For clarity, here is the shape of a simple thirteen-week model — the categories most businesses need and no more. Each column is a week; the closing balance carries into the next week’s opening.

Line	Source	Notes
Opening bank balance	Cleared bank	Week 1 actual; thereafter prior week closing
Receipts — existing debtors	Aged debtor listing	By expected week, not due date
Receipts — new invoicing	Sales pipeline	Only where raised and collected inside 13 weeks
Receipts — other	Grants, refunds, asset sales	Include VAT refunds and R&D credits
Payments — payroll and PAYE	Payroll calendar	Actual payment dates, including the 22nd PAYE
Payments — suppliers	Aged creditor listing	By expected payment week
Payments — VAT and tax	Filing calendar	The lumpy items that sink good weeks
Payments — loans and finance	Facility agreements	Capital and interest separately
Payments — discretionary	Management decision	Capex, recruitment, marketing — the levers
Net movement	Calculated
Closing bank balance	Calculated	Carries to next week
Facility headroom	Closing + available facility	The number the board should watch

Using it: what the forecast is actually for

A forecast that is produced and filed has failed regardless of its accuracy. The output should drive four conversations. Collections: the debtor rows tell you exactly which invoices matter this month and who to chase first — a far better prioritisation than chasing the largest or the oldest indiscriminately. Payment timing: knowing which week is tight lets you sequence discretionary payments deliberately rather than by whoever shouts loudest. Funding: if the model shows a facility drawdown in week nine, week two is when to have the conversation with the lender, and lenders respond very differently to a forecast presented early than to a request made late. Commercial decisions: the hire, the equipment purchase, the marketing push — each can be tested against the forecast before commitment rather than justified afterwards. The businesses that get the most from a 13-week forecast treat it as a weekly management meeting agenda item, not a finance deliverable.

Frequently asked questions

How is a 13-week forecast different from a three-way forecast? The 13-week is short-horizon and cash-only; a three-way (or 3-statement) forecast projects P&L, balance sheet and cash together over a longer horizon and is a planning rather than a liquidity tool — most businesses need both, for different purposes. Should VAT be shown gross or net? Gross — cash forecasting tracks money moving, so receipts and payments include VAT, with the VAT settlement shown as its own payment line. How accurate should it be? Week one should be near-exact, weeks two to four close, and the back end directionally right; if week two is regularly wrong by a wide margin the inputs need attention. Who should see it? The management team weekly, the board monthly, and lenders or investors where covenants or facilities are in play. How long does it take to build? A competent finance professional can build a working model for a straightforward business in two to three days, with a week or two of iteration before it settles.