# The 13-Week Cash Flow Forecast: A Practical Guide

*Alex Tapio · 2026-06-13 · 13 min · Model Deep-Dives*

Canonical: https://finamodel.com/blog/13-week-cash-flow-forecast

A practical guide to building a 13-week cash flow forecast in Excel - the short-term, weekly liquidity model used in treasury and turnaround situations. Learn why 13 weeks, the direct-method receipts-and-disbursements build, a fully worked 13-week example, the roll-forward and variance formulas, and the mistakes to avoid.

**A 13-week cash flow forecast is the short-term liquidity model every treasurer, CFO, and turnaround manager relies on: a weekly, direct-method schedule of cash in and cash out across the next quarter that tells you - with enough warning to act - whether you can make payroll, pay suppliers, and service debt in every single week. This guide shows you how to build a 13-week cash flow forecast in Excel from scratch: why 13 weeks, the receipts-and-disbursements build, a fully worked 13-week example with real numbers, the roll-forward and variance formulas that keep it honest, and the mistakes that turn a forecast into false comfort.**

Most businesses run out of cash not because they are unprofitable, but because they cannot see a short-term gap coming. Profit is an accrual concept; cash is what clears payroll on Friday. The 13-week cash flow forecast - sometimes called the short-term cash flow forecast or simply the "13-week" - exists to close that visibility gap. It zooms in on the next 91 days at weekly resolution, where the lumpy, dangerous outflows live: a quarterly tax payment, a debt amortisation date, a seasonal inventory build, a big payroll that does not wait for a slow collection month.

It is the model of choice in treasury management and, above all, in turnaround and restructuring. When a business is under liquidity stress, lenders and restructuring advisors do not ask for the annual budget - they ask for the 13-week, updated weekly against actuals. If you can build and defend one, you can manage a cash crisis instead of being managed by it.

```mermaid
flowchart TD
    A["Opening Cash: this week's bank balance"] --> D["Net Cash Flow per Week"]
    B["Forecast Weekly Receipts: collections by week"] --> D
    C["Forecast Weekly Disbursements: payroll, suppliers, tax, debt"] --> D
    D --> E["Roll Forward: closing cash becomes next week's opening"]
    E --> F{"Closing Cash above Minimum?"}
    F -->|Yes| G["Adequate Liquidity"]
    F -->|No| H["Funding Gap: draw revolver and act now"]
    G --> I["Compare Forecast vs Actual at week close"]
    H --> I
    I --> J["Roll the 13-week window forward one week"]
```

*The 13-week forecast is a weekly loop: forecast receipts and disbursements, roll each week's closing cash into the next opening balance, test it against a minimum-cash floor, then reconcile to actuals and roll the window forward one more week.*

---

## Why 13 Weeks?

Thirteen weeks is exactly one calendar quarter: 13 × 7 = 91 days, just over three months. That horizon is deliberate, and it is a balance between two opposing pressures.

- **Long enough to catch the lumpy outflows.** The cash events that actually cause breaches are not the steady weekly payroll - they are the quarterly tax payment, the semi-annual interest date, the annual insurance premium, the seasonal stock build. A 13-week window almost always contains at least one of these, so the forecast surfaces the air-pocket before you hit it.
- **Short enough that weekly estimates stay honest.** You can credibly estimate which customers will pay in week 3 and which supplier invoices come due in week 7. Push the same weekly precision out to week 30 and it becomes guesswork. Beyond the quarter, a monthly [cash flow forecast](/blog/cash-flow-forecast-excel) is the better instrument.

The 13-week window also matches how lenders and restructuring professionals review a stressed borrower, so it has hardened into a market standard. When a credit agreement requires a "short-term cash flow forecast," it almost always means the 13-week.

---

## 13-Week vs. Monthly Forecast vs. Annual Budget

These three tools are often confused, but they answer different questions at different resolutions. Picking the wrong one for the job is itself a common mistake.

| | 13-Week Forecast | Monthly Forecast | Annual Budget |
| :--- | :--- | :--- | :--- |
| **Question it answers** | Can we survive the next quarter, week by week? | How does cash trend over 12–24 months? | What is the plan for the year? |
| **Granularity** | Weekly | Monthly | Monthly / annual |
| **Method** | Direct (receipts and payments) | Direct or indirect | Accrual |
| **Primary use** | Liquidity, treasury, turnaround | Budgeting, covenant planning | Target-setting, performance |
| **Updated** | Weekly, rolled forward | Monthly | Annually, with re-forecasts |

The key insight is **granularity reveals risk**. A monthly forecast can show a comfortable month-end balance while hiding a mid-month trough - payroll clears on the 1st but the big customer pays on the 25th. The 13-week's weekly buckets expose exactly that dip. The tighter your liquidity, the more granular your forecast needs to be. For a fuller treatment of the monthly direct-and-indirect build, see our guide to [building a cash flow forecast in Excel](/blog/cash-flow-forecast-excel); this post drops down to the weekly view that liquidity management demands.

---

## The Direct Method: Receipts and Disbursements

A 13-week forecast is built on the **direct method** - you list the actual cash coming in and going out, by category, in the week it lands. There is no net-income starting point and no non-cash add-backs; those belong to the indirect method used inside a [3-statement financial model](/blog/3-statement-financial-model). The 13-week cares about one thing: when does money hit the bank account?

### Receipts: collections, not revenue

The hardest line is receipts, because a sale and its collection happen in different weeks. If you invoice $200,000 in week 2 on 30-day terms, almost none of it arrives in week 2 - it lands around weeks 5–7. Build receipts from two sources:

1. **Opening accounts-receivable aging.** Take the AR ledger as it stands today and schedule each invoice into the week you expect it to be paid, based on the customer's actual payment behaviour (not the stated terms).
2. **Collections on future sales.** Apply a collection pattern to forecast sales - what fraction is collected in the week of sale, the following week, and so on.

At weekly granularity, **collection timing dominates the forecast**. Days Sales Outstanding (DSO) is the single most important driver: stretch DSO by ten days and a chunk of every week's expected receipts slides into the following week, which is often the difference between clearing the minimum-cash floor and breaching it. Days Payable Outstanding (DPO) works the other way - the longer you take to pay suppliers, the more of your cycle they finance. Use the calculator below to see how DSO, inventory days, and DPO combine into a net working-capital requirement, then translate that timing into your weekly receipt and payment lines.

<!-- tool:working-capital-calculator -->

### Disbursements: mostly known, occasionally lumpy

Disbursements are easier because most are contractual or scheduled. Break them into clear categories so nothing is missed:

- **Payroll and payroll taxes** - usually the largest and most rigid outflow; weekly, biweekly, or semi-monthly. It does not wait for a good week.
- **Supplier / COGS payments** - driven off purchases and your DPO; these lag the expense.
- **Rent and fixed overhead** - flat, predictable monthly amounts.
- **Taxes** - lumpy. Quarterly estimated tax or VAT/sales-tax remittances create the classic mid-quarter air-pocket.
- **Debt service** - scheduled interest and principal amortisation; often monthly or quarterly.
- **CapEx and one-offs** - equipment, deposits, severance, professional fees in a restructuring.

The danger is never the steady lines - it is the **lumpy** ones. A single quarterly tax payment dropped into the wrong week is the most common cause of a forecast breach, which is exactly why a 13-week window (long enough to contain it) at weekly granularity (precise enough to place it) is the right tool.

---

## Structuring the Model in Excel

Lay the forecast out as one horizontal grid: **rows are line items, columns are the 13 weeks.** Label the columns with the week-ending date, not just "Week 1," so the model stays anchored to the calendar as you roll it. Stack the sheet in blocks:

1. **Receipts** - collections from AR aging plus collections on new sales.
2. **Operating disbursements** - payroll, suppliers, rent, overhead, tax.
3. **Non-operating disbursements** - debt service, CapEx, one-offs.
4. **The roll-forward** - opening cash, net cash flow, closing cash, and the test against your minimum-cash floor.

The roll-forward logic is the spine of the model:

```
Opening Cash (this week)
+ Total Receipts
- Total Disbursements
= Net Cash Flow
+ Opening Cash
= Closing Cash  ->  becomes next week's Opening Cash
```

The golden rule is the same as in any model: **every assumption lives on a dedicated `Assumptions` sheet** - collection percentages, payroll amount, DPO, the minimum-cash threshold, tax dates - and every cell in the grid is a formula that references it. That is what lets you re-run a downside scenario in seconds instead of editing 13 columns by hand.

---

## A Fully Worked 13-Week Forecast

Let's build a direct-method 13-week forecast for a mid-sized distributor heading into a tight quarter. **Opening cash is $250,000**, and the revolving credit facility carries a covenant requiring a **minimum cash balance of $150,000** at all times. All figures are in thousands.

The receipts line reflects slow collections early in the quarter (a couple of large customers stretched their terms) recovering later. The disbursements line includes biweekly payroll, weekly supplier payments, monthly rent, scheduled debt service - and a **$70,000 quarterly tax payment that lands in Week 6.**

| Week | Receipts | Disbursements | Net Cash Flow | Opening Cash | Closing Cash | Headroom vs $150k |
| :--- | :---: | :---: | :---: | :---: | :---: | :---: |
| W1 | $180k | ($175k) | $5k | $250k | $255k | $105k |
| W2 | $165k | ($200k) | ($35k) | $255k | $220k | $70k |
| W3 | $150k | ($165k) | ($15k) | $220k | $205k | $55k |
| W4 | $140k | ($195k) | ($55k) | $205k | $150k | $0k |
| W5 | $135k | ($175k) | ($40k) | $150k | $110k | ($40k) |
| W6 | $160k | ($230k) | ($70k) | $110k | $40k | ($110k) |
| W7 | $175k | ($160k) | $15k | $40k | $55k | ($95k) |
| W8 | $185k | ($200k) | ($15k) | $55k | $40k | ($110k) |
| W9 | $190k | ($160k) | $30k | $40k | $70k | ($80k) |
| W10 | $200k | ($170k) | $30k | $70k | $100k | ($50k) |
| W11 | $210k | ($165k) | $45k | $100k | $145k | ($5k) |
| W12 | $205k | ($185k) | $20k | $145k | $165k | $15k |
| W13 | $215k | ($170k) | $45k | $165k | $210k | $60k |

The disbursement total is just the sum of the category lines for each week. Here is the build behind the worst week - **Week 6**, where the quarterly tax payment collides with still-weak collections:

| Week 6 Disbursement | Amount |
| :--- | :---: |
| Supplier / COGS payments | $75k |
| Payroll (biweekly run) | $65k |
| Rent and fixed overhead | $20k |
| Quarterly tax payment | $70k |
| **Total disbursements** | **$230k** |

Now read the story the grid tells. On an operating basis the business is fundamentally fine - by Week 13 it has rebuilt cash to $210k. But the **timing** is brutal. Cash touches the $150k covenant floor exactly in Week 4, breaches it in Week 5, and then the Week 6 tax payment drives the balance to **$40k - a full $110,000 below the covenant.** The gap does not close until Week 12. This is not a one-week dip; it is a **sustained ~7-week shortfall with a peak funding need of about $110,000** at the Weeks 6 and 8 troughs.

That distinction is the entire value of the forecast. A monthly view might have shown a comfortable quarter-end balance and missed the breach entirely. The 13-week view says, in Week 1: *you need roughly $120,000 of additional liquidity arranged before Week 5, and you will carry that draw for about two months.* Management can now act while it has options - negotiate a temporary revolver increase, ask the tax authority for an instalment arrangement, accelerate collections on the two slow accounts, or defer the discretionary spend - rather than discovering the problem when a payment bounces in Week 6.

---

## Making It Roll: Opening Cash, Closing Cash, and Funding Flags

The model is only useful if it rolls forward automatically and flags trouble without you hunting for it. Four formulas do the work.

**1. Opening cash equals last week's closing cash.** Never retype it - link it, so a change in any week cascades down the whole quarter:

```excel
// Week 2 opening cash (cell D20) = Week 1 closing cash (cell C30)
= C30
```

**2. Closing cash is opening plus the net of receipts and disbursements:**

```excel
= Opening_Cash + Total_Receipts - Total_Disbursements
```

**3. A minimum-cash flag turns the model into an early-warning system.** Conditional-format this red so a breach is impossible to miss:

```excel
= IF(Closing_Cash < Assumptions!$B$5, "FUNDING GAP", "OK")
```

**4. The peak funding need - the single most important output - is the lowest closing balance across the whole window, compared to the floor:**

```excel
// Lowest closing cash across the 13 weeks
= MIN(C30:O30)

// Peak shortfall vs the covenant floor (a positive number = the gap to fund)
= MAX(0, Assumptions!$B$5 - MIN(C30:O30))
```

That last formula is what you take to the lender: "our trough is $40k against a $150k floor, so we need to arrange at least $110k of headroom." Rather than build all of this from a blank sheet, you can start from a ready-made structure with the operating, investing, and financing sections and roll-forward already wired up - download the free [cash flow model template](/templates/cashflow) and preview it live below.

<!-- template:cashflow -->

---

## Forecast vs. Actual: The Variance Discipline

What separates a credible 13-week from a wishful one is the **weekly reconciliation against actuals.** At the close of each week you drop in what actually happened, compare it to what you forecast, and explain the gap:

```excel
// Weekly variance, by line
= Actual_Cash - Forecast_Cash

// As a percentage of forecast
= (Actual_Cash - Forecast_Cash) / Forecast_Cash
```

This discipline does two jobs. First, it is the **integrity check**: a persistent receipts variance almost always means your collection-timing assumption (DSO) is wrong, so you correct it and the next forecast sharpens. Second, in lender and restructuring contexts the variance report is a **governance document**. A borrower that consistently lands within a few percent of its forecast keeps the lender's trust and a lighter touch; large, unexplained variances trigger tighter oversight, weekly calls, and sometimes a default notice. The forecast is only as good as its track record against the bank statement.

After reconciling, you **roll the window**: drop the week that just closed, add a fresh thirteenth week at the end, and re-anchor opening cash to today's actual bank balance. Done every week, the model always looks a full quarter ahead and never drifts from reality.

---

## Stress-Testing the Forecast

Because the whole grid is driven from the `Assumptions` sheet, scenarios are cheap - and in a liquidity context the downside is the only one that matters:

- **Base case:** your honest best estimate of collection timing and outflows.
- **Downside case:** push DSO out by 10–15 days, assume your largest customer pays two weeks late, and add a contingency outflow. This is the scenario that reveals your *true* peak funding need and how many weeks the gap lasts.
- **Upside case:** useful context, but never the case you manage liquidity against.

The question a 13-week must answer is not "what do we expect?" but "**what is the worst week, and do we survive it?**" If the downside breaches the covenant, you arrange the financing now - while you still can. For early-stage companies where the broader runway question dominates, our [startup financial model guide](/blog/startup-financial-model-guide) covers burn rate and runway in depth.

---

## Common Mistakes to Avoid

1. **Forecasting revenue instead of collections.** The number one error. A 13-week is a cash document - model when invoices are *paid*, off the AR aging and a realistic DSO, not when sales are booked.
2. **Smoothing lumpy outflows.** Spreading a quarterly tax payment or debt amortisation evenly across 13 weeks hides the exact air-pocket that causes the breach. Put every lumpy item in the week it actually clears.
3. **Ignoring the AR aging.** Starting receipts from forecast sales alone, while ignoring the invoices already outstanding today, mis-times the first month of cash - the most important weeks in the whole forecast.
4. **No minimum-cash floor.** Forecasting to a zero balance is forecasting to insolvency. Always test closing cash against the covenant or a self-imposed buffer, and flag breaches automatically with conditional formatting.
5. **Hardcoding the roll-forward.** Typing opening balances by hand breaks the chain - change one week and the rest no longer reconcile. Opening cash must always be a formula linked to the prior week's closing balance.
6. **Never reconciling to actuals.** A 13-week that is built once and never compared to the bank statement quietly drifts from reality. The weekly forecast-vs-actual variance loop is not optional; it is what makes the model trustworthy.
7. **Only modelling the base case.** The 13-week exists for the bad weeks. Without a downside scenario you do not know your real peak funding need - or whether your revolver is big enough to cover it.

---

## Key Takeaways

- **The 13-week is a liquidity tool, not a budget.** It exists to answer one question at weekly resolution - can we cover every payment in every week of the next quarter? - and it is the standard instrument in treasury and turnaround work.
- **Thirteen weeks is the right window.** A full quarter is long enough to contain the lumpy tax and debt outflows that cause breaches, and short enough that weekly estimates of collections and payments stay honest.
- **Build it on the direct method.** List actual receipts and disbursements by category in the week they land; collection timing (DSO) is the single biggest driver, so model it explicitly off the AR aging.
- **Roll it forward with formulas.** Closing cash becomes next week's opening balance automatically; a `MIN()` across closings and an `IF()` flag turn the grid into an early-warning system that surfaces the peak funding need at a glance.
- **Reconcile to actuals every week.** Forecast-vs-actual variance tracking is both the integrity check that sharpens your assumptions and the governance document that keeps lenders' trust. A 13-week is only as credible as its track record.
- **The downside case is the point.** Stress collection timing and lumpy outflows to find the true trough, then arrange financing before the tight week - not during it.

A reliable 13-week cash flow forecast is a living model, refreshed every week against the bank statement. Start from the free [cash flow model template](/templates/cashflow), centralise your assumptions, wire up the roll-forward, and let the weekly variance loop keep it honest.


## Frequently asked questions

### What is a 13-week cash flow forecast?

A 13-week cash flow forecast is a short-term, weekly schedule of every cash receipt and disbursement a business expects over the next quarter. It is built on the direct method - listing actual money in and money out by category - and rolls forward one week at a time, with each week's closing bank balance becoming the next week's opening balance. Its single job is liquidity: to tell a treasurer or CFO, week by week, whether there is enough cash to cover payroll, suppliers, taxes, and debt service, and to surface any funding gap far enough ahead that there is still time to act. It is the standard tool in treasury management, lender reporting, and turnaround or restructuring situations.

### Why 13 weeks specifically?

Thirteen weeks is exactly one calendar quarter (13 × 7 = 91 days, ~3 months), which makes it the natural near-term planning horizon. It is long enough to capture the lumpy outflows that wreck liquidity - a quarterly tax payment, a debt amortisation date, a seasonal inventory build - but short enough that weekly estimates of collections and payments stay reasonably accurate. Beyond 13 weeks, weekly precision degrades and a monthly forecast becomes the better tool. The 13-week window also aligns with how lenders and restructuring advisors review borrowers, so it has become the de facto standard for short-term cash visibility.

### How is a 13-week forecast different from a monthly cash flow forecast or an annual budget?

They answer different questions at different resolutions. A 13-week forecast answers "can we survive the next quarter, week by week?" - it is a liquidity and survival tool, almost always built on the direct method at weekly granularity. A monthly cash flow forecast answers "how does cash trend over the next 12–24 months?" and is used for budgeting and covenant planning. An annual budget answers "what is the plan for the year?" on an accrual basis and is rarely about timing of cash at all. A monthly view can hide a mid-month air-pocket - payroll due on the 1st while a big receipt lands on the 25th - that a weekly view exposes immediately. When liquidity is tight, you drop down to the 13-week.

### Why is the 13-week forecast always built on the direct method?

Because the direct method lists actual cash receipts and payments by category - collections from customers, payroll runs, supplier payments, tax dates, debt service - which is precisely what a treasurer watches and acts on. The indirect method starts from accrual net income and adjusts for non-cash items and working capital; it is excellent for reconciling cash to the P&L inside a 3-statement model, but it obscures the weekly timing of money actually leaving the bank account. For a 13-week liquidity forecast you care about when the cash moves, not when the accountant recognises it, so the direct method is the only sensible build.

### How often should you update and roll a 13-week forecast?

Weekly. At the close of each week you replace that week's forecast with the actual cash result, compare the two (variance analysis), update the assumptions that drove any miss, and add a new thirteenth week to the end so the window always looks a full quarter ahead. This "rolling" discipline is what makes the model trustworthy: a forecast that is never checked against actuals quietly drifts from reality, while a rolled, reconciled forecast gets sharper every week. In an active turnaround, some treasuries refresh key receipt lines daily and re-roll the full model every Monday.

### What is forecast-vs-actual variance tracking, and why does it matter?

Variance tracking is the weekly comparison of what you forecast for each line against what actually happened in the bank account, expressed as a dollar and percentage difference. It matters for two reasons. First, it is the integrity check: persistent variances reveal which assumptions - usually collection timing - are wrong, so you can fix them. Second, in lender and restructuring contexts the variance report is a governance document: a borrower that consistently hits its forecast keeps the lender's trust, while large unexplained variances trigger tighter oversight. The forecast is only as credible as its track record against actuals.