Here's an uncomfortable number: according to a U.S. Bank study, 82% of small businesses that fail do so because of cash flow problems — not because they were unprofitable. A company can show a healthy profit on its year-end income statement and still miss payroll in March, because profit is an accounting opinion and cash is a fact. You can be profitable on paper for an entire quarter and still run out of money next Thursday.
That gap between "profitable" and "solvent" is exactly what a 13-week cash flow forecast is built to close. It's the tool professional CFOs and turnaround consultants reach for first when a company is under stress, but you don't need to be in distress to benefit from it. Any owner who has ever stared at a bank balance and wondered "can I make payroll in three weeks?" is asking a question that a spreadsheet, not a hunch, should answer.
This guide walks through how to build a 13-week forecast, the two working-capital metrics that make it accurate, and the habits that keep it useful instead of abandoned by week four.
Why 13 Weeks, Specifically?
Cash forecasting exists on a spectrum. Daily forecasts are too granular to sustain — nobody has the bandwidth to update every account balance every morning. Annual forecasts are too vague to act on; by the time next October's cash crunch shows up in a 12-month model, you've long since lost the ability to do anything about it.
Thirteen weeks — roughly one fiscal quarter — sits in the sweet spot. It's long enough that you can actually see a cash gap coming and do something about it: renegotiate a vendor term, delay a purchase, call a line of credit. It's short enough that near-term weeks are grounded in real, known transactions (this week's payroll, this week's rent, that customer's invoice due date) rather than guesswork. And it's become a standard format — banks, lenders, and outside advisors recognize it on sight, which matters if you ever need to show one to a lender mid-crunch.
The model is also meant to roll. Each week, you drop the week that just ended, add a new week 13 to the far end, and true up your projections against what actually happened. A forecast that isn't updated weekly against actuals stops being a forecast and becomes a guess with a spreadsheet around it.
Building the Forecast: Six Steps
1. Lay out the grid
Structure is simple: weeks across the columns, categories down the rows. Three sections do the work — Cash Inflows, Cash Outflows, and a Net Cash Flow summary row that carries a beginning and ending balance for every week. For any week with a large, date-specific disbursement (a loan payment, a tax deposit, a big payroll run), break that week down by day so you're not caught by timing within the week.
2. Establish your starting position
Total up everything genuinely accessible right now — checking, savings, money-market, and any line-of-credit availability — net of holds or fees. This is your week-zero cash balance, and every following week builds on it.
3. Forecast inflows and outflows by category
Inflows are collections from receivables, projected new sales converted to cash based on your actual collection pattern, and anything else hitting the bank (tax refunds, asset sales, loan draws).
Outflows are your known obligations: payroll and payroll taxes, rent, vendor payments, debt service, capital expenditures, insurance premiums, and owner draws. Pull the last 6–12 months of bank statements, invoices, and payment records to ground these numbers in what your business actually does, not what you hope it does.
The single most common mistake here is optimism. It's tempting to book revenue the moment an invoice goes out. Don't. Book cash into the forecast when it's realistically expected to clear the bank, based on how your customers actually pay — not on your payment terms. If your invoices say "Net 30" but your average customer pays in 42 days, your forecast should say 42, not 30.
4. Identify improvement opportunities
Once the grid is built, it usually reveals a few pressure points on its own: a week where receivables are thin and payroll lands on the same day, a stretch where a large vendor payment could be resequenced. Common levers: accelerating collections on slow-paying accounts, renegotiating vendor payment terms, or liquidating excess or slow-moving inventory.
5. Strengthen your capital structure
If the forecast shows a gap you can't close through timing alone, that's information you want weeks in advance, not days. Lining up a line of credit, diversifying financing sources, and communicating early and transparently with creditors is far more effective than doing it once you're already short.
6. Build in a second set of eyes
A bookkeeper, fractional CFO, or accountant who reviews the forecast monthly will catch assumptions you're too close to see — a customer concentration risk, a seasonal pattern you've normalized, an expense that's crept up quietly.
The Two Metrics That Make Your Forecast Accurate: DSO and DPO
A 13-week forecast is only as good as its assumptions about when cash actually moves — and that's where two working-capital metrics come in.
Days Sales Outstanding (DSO) measures the average number of days it takes to collect payment after a sale. The formula:
DSO = (Accounts Receivable ÷ Total Credit Sales) × Number of Days in PeriodIf your DSO is 45 days, an invoice issued in week 1 shouldn't show up as cash in your forecast until roughly week 7 — not week 5, because that's what the invoice terms say.
Days Payable Outstanding (DPO) is the mirror image: the average number of days it takes you to pay your own bills.
DPO = (Accounts Payable ÷ Cost of Goods Sold) × Number of Days in PeriodA higher DPO (within reason, and without damaging supplier relationships) means you're holding onto cash longer before it goes out the door.
Together with Days Inventory Outstanding (DIO — how long inventory sits before it sells), these three numbers combine into the Cash Conversion Cycle (CCC):
CCC = DIO + DSO − DPOThe CCC answers one question in a single number: how many days is cash tied up in the business — in unsold inventory and uncollected invoices — before it comes back as usable cash, net of what you owe suppliers? The shorter the cycle, the less working capital your operations require to run, and the more slack you have when something goes wrong.
This is precisely why healthy businesses still fail: it's entirely possible to have strong sales and solid margins while cash sits trapped in receivables and inventory for 60+ days. On a trailing-twelve-month income statement, that business looks fine. On a rolling 13-week cash forecast built from real DSO and DPO figures, the gap is visible weeks before it becomes a payroll problem.
Common Mistakes That Sink a Forecast
- Treating it as a one-time exercise. A forecast built once in January and never revisited is a snapshot, not a tool. It needs weekly updates against actuals to stay trustworthy.
- No clear owner. Forecasts without an assigned owner get abandoned during the exact busy periods when they matter most. Assign it to one person — even if that's you — and put it on the calendar.
- Using invoice terms instead of actual collection behavior. As above: if customers pay late, your forecast should assume they'll keep paying late until you have evidence otherwise.
- Ignoring scenario planning. A single-case forecast tells you what you expect. A best-case/worst-case/likely-case model tells you how much runway you actually have if a big customer pays late or a large order falls through.
- Losing the underlying transaction detail. A forecast is only as auditable as the records behind it. If "vendor payments" in week 6 is a single lump number with no ledger trail back to actual bills, you can't sanity-check it three months later — or explain it to a lender.
Keep the Ledger Behind Your Forecast Just as Disciplined
A 13-week cash flow forecast is only as trustworthy as the bookkeeping data feeding it — accurate, current accounts receivable and accounts payable balances are what make DSO and DPO real rather than guessed. If your books are a patchwork of spreadsheets, bank exports, and a bookkeeping app's black-box categorization, reconciling actuals against your forecast every week becomes its own chore.
Beancount.io offers plain-text, version-controlled accounting that keeps every transaction transparent and auditable, so pulling accurate receivables and payables data for your rolling forecast — or handing it to an advisor — is never a guessing game. For teams that want a visual, real-time read on cash position alongside the plain-text ledger, the Fava dashboard turns the same data into the kind of at-a-glance view a 13-week forecast depends on. Explore the docs to see how the underlying ledger structure works, or check pricing to get started.