13-Week Cash Flow Forecast:How to Build One(2026 Method + Template)

A 13-week cash flow forecast is a weekly projection of every dollar entering and leaving your bank account over the next quarter, built from actual expected receipts and payments rather than from your P&L. It is the single most useful financial document a founder can maintain, and most companies only build one when a lender, an investor, or a near-miss on payroll forces them to.

It answers one question your accounting system cannot: on which specific week does cash get tight?

This guide covers what the forecast is, why the window is 13 weeks, how to build one line by line, a worked example you can copy, and the five mistakes that make most 13-week models useless within a month.

---

What Is a 13-Week Cash Flow Forecast?

A 13-week cash flow forecast projects your cash position week by week for one quarter ahead. Each week shows an opening balance, cash in, cash out, and a closing balance that becomes the next week's opening.

The critical distinction: it is built on the direct method. You forecast actual cash movements — this invoice collects in week 4, payroll runs in weeks 2, 4, 6 — rather than starting from net income and adjusting for non-cash items.

That distinction is why the tool works. Your income statement can show a profitable month while your bank account empties, because revenue is recognized when earned and cash arrives when customers decide to pay. A 13-week forecast ignores accounting and tracks money.

Why 13 weeks and not 12 or 26?

Thirteen weeks is exactly one quarter. That matters for three practical reasons:

It matches how the business already reports. Board packs, investor updates and covenant tests run on quarters. A 13-week window lines up with the cycle everyone is already looking at.

It is long enough to act. Most cash problems have a fix with a four-to-eight week lead time — accelerating collections, delaying a hire, drawing on a facility, renegotiating payment terms. A four-week forecast tells you about a problem you can no longer solve. Thirteen weeks gives you room.

It is short enough to be accurate. Beyond about a quarter, receipt timing becomes guesswork. The forecast's authority comes from being specific about weeks, and specificity decays fast past week 13.

The format is long-established in restructuring and asset-based lending, which is why it is instantly recognizable to anyone reviewing your finances — a lender or an investor will know exactly what they are looking at.

Direct method vs indirect method

Most companies' statutory cash flow statement uses the indirect method — both IAS 7 and ASC 230 permit either, and indirect is the common choice. Your 13-week forecast should not follow suit. If someone builds you a 13-week model that starts from EBITDA and works down, they have built a reporting document wearing a forecasting costume.

---

When Founders Actually Need One?

You do not need a 13-week forecast forever. You need it when the answer to "will we be fine" stops being obvious. In practice, that is:

• Runway under 12 months. Below a year, weekly resolution starts to matter. Below six months it is not optional.
• Lumpy revenue. Enterprise contracts, milestone billing, seasonal demand — anything where a single late payment moves the month.
• You are raising. Investors ask for it, and arriving with one already maintained signals a level of control that changes the conversation.
• You have debt. Lenders with covenants frequently require a rolling 13-week as a condition. Venture debt and asset-based facilities almost always do.
• You just had a scare. If payroll was ever close, build it that week.

Out of the 40 companies I've built financial models for, 80% did not have a working cash forecast when I arrived. Ten of those had built one at some point and stopped updating it within two months.

---

How To Build a 13-Week Cash Flow Forecast?

Step 1 — Set the structure before you enter a number

Columns are weeks. Use the week-ending date, not "Week 1" — labels drift and dates do not. Thirteen forecast columns, plus a column for each completed week so actuals sit beside the forecast.

Rows group into four blocks:

1. Opening cash — one line, per bank account if you hold several
2. Cash receipts — money in
3. Cash disbursements — money out
4. Net movement and closing cash

Keep it to one sheet. The most common failure in a first model is over-engineering — a 40-tab workbook nobody updates is worth less than a one-page forecast someone refreshes every Monday.

Step 2 — Start from the bank balance, never the ledger

Week 1 opening cash is the cleared balance in your bank account this morning. Not the balance in your accounting system, which includes uncleared items and timing differences.

This sounds pedantic. It is the difference between a forecast people trust and one they quietly stop opening.

Step 3 — Map receipts from the AR aging, customer by customer

Do not forecast revenue and assume a collection lag. Take your accounts receivable aging report and place each open invoice in the week you genuinely expect it to land.

The phrase doing the work is actual historical payment behavior. A customer on net-30 terms who has paid on day 52 for six consecutive quarters pays on day 52. Forecasting them at day 30 is not optimism, it is a known error.

Step 4 — Map disbursements from the AP aging and the calendar

Disbursements are easier because most are known. Split them into committed and discretionary — this is what lets you model levers later.

Committed (contractual, hard to move quickly):

• Payroll and payroll taxes — use the actual pay calendar, including the months with three pay runs
• Rent and lease payments
• Debt service — principal and interest, on the exact due dates
• Insurance premiums
• Software and infrastructure on annual renewal

Discretionary (movable under pressure):

• Vendor payments from the AP aging
• Marketing spend
• Contractors and agencies
• Travel
• Capital expenditure

Two lines founders routinely omit and then get caught by: quarterly tax payments and annual software renewals. Both are large, both are predictable, and neither appears in a monthly average.

Step 5 — Build the roll-forward

The arithmetic is trivial and the discipline is not:

Closing cash (week N) = Opening cash (week N)
                      + Total receipts (week N)
                      − Total disbursements (week N)

Opening cash (week N+1) = Closing cash (week N)

Every week links to the last. One hardcoded balance in the middle of the roll-forward breaks the model silently, and it will not be obvious which week is wrong.

Step 6 — Add the variance column, which is the whole point

At the end of each week, enter what actually happened next to what you forecast. Compute the variance by line.

$000s. Ties to week 1 of the worked example below.

Without this column you have a projection. With it you have a forecast that gets better every week, because you can see which assumptions are systematically wrong. Most models fail here — built once, admired, never reconciled.

---

Example

A B2B services company: $520,000 in the bank, payroll of $82,000 per run on a biweekly cycle, and three large receivables outstanding.

$000s. Week 4 "other out" includes a quarterly VAT payment; week 8 includes annual insurance and software renewals.

Read the closing row rather than the total. Cash never goes negative, so a monthly view would show no problem at all. But the trough at week 8 — $370k against a biweekly payroll of $82k and a $95k renewal cluster — is under five weeks of cover. That is the week that needs a decision, and it is invisible in any monthly report.

That is the entire value of the tool. Not the ending balance. The shape.

---

The Weekly Cadence

The forecast is a habit, not a document. The rhythm that works:

Monday morning, 30 minutes.

1. Pull the cleared bank balance
2. Enter last week's actuals beside the forecast
3. Review variances over your materiality threshold — explain each one in a sentence
4. Roll the window forward one week, adding a new week 13
5. Update receipt timing for anything you learned — a customer confirming a date, an invoice disputed
6. Circulate the closing-cash row and the three largest variances

Thirty minutes. The roll-forward is what makes it rolling — you always have a full quarter of visibility rather than a window that shrinks until it is useless.

---

Five Mistakes That Break Most 13-Week Models

1. Forecasting revenue instead of collections. The most common and most damaging. Revenue is an accounting event; collection is a cash event. On net-45 terms with typical slippage they are two months apart.

2. Using monthly averages divided by 4.33. Payroll does not run evenly. Rent lands on the 1st. Tax is quarterly. Averaging destroys the timing information that is the only reason to build a weekly model.

3. Forgetting the three-payroll month. A biweekly payroll (every two weeks, 26 runs a year) produces three runs in two months of every year. Founders discover this in the week it happens.

4. Building it once. A model without weekly actuals and variance analysis is a projection, and it decays immediately. The forecast's accuracy comes from reconciliation, not from the initial build.

5. Modeling only the base case. If cash gets tight at week 8 in the base case, it gets tight at week 5 if your largest customer pays late. Run a downside where the top two receipts slip by three weeks. That is the scenario you actually need a plan for.

The one I see most

Across the forecasts I review, the most common error isn't in the formulas — it's forecasting collections off invoice terms instead of observed payment behavior. Roughly two-thirds of the models I see put net-30 customers at 30 days when their actual average is closer to 50.

On a company collecting $400k a month, that's a three-week hole in the forecast that stays invisible until the week it isn't. It's also the easiest thing on this page to fix: pull twelve months of payment dates per customer and use the median, not the terms.

---

How The 13-Week Fits With Your Other Financial Tools

These are complements, not alternatives. The 13-week is the only one operating at the resolution where payroll decisions are actually made.