Methodology Guide
13-Week Cash Flow Forecast Guide: How to Build One
A 13-week cash flow forecast is the standard treasury rhythm finance teams use to spot cash gaps weeks ahead of payroll Friday. You build it as a direct-method model: opening cash, weekly expected inflows weighted by accounts-receivable aging behavior, weekly required outflows separated by fixed and variable, and a rolling closing balance. The point isn't to predict the future. It's to surface tight weeks early enough to act on them cheaply.
Data you need
Starting cash position
Today's operating bank balance, minus uncleared or reserved cash. Not your line of credit.
Expected weekly inflows
Customer payments by week, weighted by AR aging behavior and historical payment timing. Include processor payouts and scheduled deposits.
Expected weekly outflows
Payroll, rent, debt service, recurring vendors, taxes. Treat fixed obligations separately from variable spend.
Known one-time events
Quarterly estimated taxes, insurance renewals, equipment purchases, large client deposits.
AR aging by bucket
Current (0-30), 31-60, 61-90, 90+ days. Each bucket has a different collection probability.
Decision this guide helps produce
Closing cash by week (weeks 1-13)
Opening balance plus expected inflows minus expected outflows. Becomes next week's opening balance.
Minimum projected balance and the week it occurs
The tightest point in the next quarter. If it dips below your operating floor, you have a known gap to plan around.
Named risks
Specific drivers behind any tight weeks (a major customer slipping, a quarterly tax payment, a payroll cycle landing on a slow week).
Confidence band
Wider when data is thin or volatile. A new business with three months of history runs a wider band than a five-year business with a stable customer base.
Decision model
The 13-week format is a direct-method forecast: take opening cash, add expected inflows, subtract expected outflows, end with closing cash. That closing balance becomes the next week's opening balance, which is why the model is rolling rather than static. Treasury teams across industries use this same structure ([Atlar overview](https://www.atlar.com/learn/what-is-the-13-week-cash-flow-forecast), [Wall Street Prep template](https://www.wallstreetprep.com/knowledge/demystifying-the-13-week-cash-flow-model-in-excel/)). The reason it's 13 weeks: long enough to spot quarterly events (estimated taxes, insurance, payroll cycles), short enough to act on what shows up. For inflows, the strongest method is to start from your AR aging schedule and weight each bucket by historical collection probability. A $50K invoice from a customer who reliably pays at day 35 counts very differently from $50K aged 90+ days. Tesorio's 2025 guidance recommends at least 12 months of payment history when possible, segmented by customer type ([Tesorio](https://www.tesorio.com/blog/dso-countback-method-how-finance-teams-can-accurately-forecast-cash-flow)). For receipt timing, finance teams use mean payment lag plus variance — not a single average. The Allianz Trade Payment Practices Barometer reports U.S. businesses now wait roughly 59 days on average to be paid in B2B transactions ([Allianz Trade](https://www.allianz-trade.com/en_US/insights/challenges-of-late-paying-customers.html)), which is why a simple due-date assumption usually misses by weeks. Fixed costs (payroll, rent, debt service, insurance, taxes) get their own treatment in a 13-week model. They're the obligations that fail a cash test even when the P&L looks healthy. Variable spend can be modeled against recent run rate. Every week, you replace last week's estimates with actuals and roll the model forward. The forecast-vs-actual variance is the signal — if your inflow estimates were off by 20%, the next week's forecast should reflect that.
Worked example
TL;DR
A 13-week cash flow forecast is the standard treasury rhythm. Long enough to see quarterly events coming, short enough to act on them.
Build it as a direct-method model: opening cash, weekly inflows, weekly outflows, closing cash. Roll forward each Monday.
Inflows get weighted by AR aging behavior, not just invoice due dates. U.S. B2B customers now average 59 days to pay. (Allianz Trade)
Fixed costs (payroll, rent, debt, taxes) get treated separately from variable spend. They’re the obligations that fail a cash test even when profit looks healthy.
The point isn’t to predict the future. It’s to surface the tight weeks before you hit them.
A finance director at a $3M agency once told us: “I look at the bank balance every morning. I still get surprised by Friday.”
The bank balance is a snapshot. It tells you what’s there right now, not what’s coming. Last quarter’s estimated tax. Payroll Friday. Two customers slipping from 30 days to 45. The mortgage on the new equipment. All of it lands sometime in the next 13 weeks. The balance you’re looking at today doesn’t tell you which week is going to be the tight one.
That’s what the 13-week cash flow forecast solves. It’s the standard treasury rhythm used by finance teams everywhere, and it works just as well for a $1M services business as it does for a $500M company. Below is how it works, what it actually looks like in practice, and what you’d need to keep it running every week without it becoming a second job.
What is a 13-week cash flow forecast?
A weekly-rolling forecast of cash in, cash out, and ending cash position, for the next 13 weeks. Each week’s closing balance becomes the next week’s opening balance, so the model is always looking 13 weeks ahead from today.
The format is called the “direct method” because it builds from actual cash movements rather than from the income statement. Wall Street Prep’s template (WSP) and Atlar’s overview (Atlar) both lay out the structure the same way: opening balance at top, line items by category, closing balance at bottom, columns are weeks 1 through 13.
Treasury teams chose 13 weeks for a reason. It’s one quarter. It captures every weekly payroll cycle, every monthly fixed cost, and every quarterly event (estimated taxes, insurance renewals, debt service balloons) inside the window. Long enough to see what’s coming. Short enough that the math stays grounded in real customer behavior.
How do you weight inflows by AR aging?
This is where most homemade forecasts go wrong.
The naïve method is to look at every open invoice’s due date and treat each one as a guaranteed payment on that date. In a healthy business with disciplined customers, that’s about 70% accurate. In a normal business, it overstates near-term cash by 15 to 30%.
The treasury method is to start from the AR aging schedule and apply collection probability by bucket:
| Aging bucket | Typical collection rate within bucket |
|---|---|
| Current (0–30 days) | 90–95% |
| 31–60 days | 80–90% |
| 61–90 days | 70–80% |
| 90+ days | 50–70%, falling fast |
These are starting numbers — your own business’s collection curve almost certainly differs. Tesorio’s 2025 guidance recommends at least 12 months of payment history when possible, segmented by customer type, geography, or product line (Tesorio). The deeper the history, the tighter the model gets.
For each open invoice, the weighted expected receipt = invoice amount × collection probability of its bucket, placed in the week when historical timing says it’s most likely to land.
How do you estimate payment timing?
Mean payment lag plus variance, not a single average.
For each customer with at least three prior payments, calculate their average days-to-pay and the spread around that average. A customer with average 35 days and tight variance (32–38 day spread) is forecasted with high confidence. A customer with average 35 days and wide variance (20–60 days) gets a wider band — and probably gets a conversation about tightening terms.
If you don’t have customer-specific history yet, the next-best signal is the aging bucket itself, blended with the broader benchmark. The Allianz Trade Payment Practices Barometer reports U.S. businesses now wait roughly 59 days on average to be paid in B2B transactions (Allianz Trade), which is why “they said net-30” isn’t a usable forecast input on its own.
Finance teams sometimes call this the “DSO countback method” or a “collection curve” approach. The exact name varies. The principle doesn’t: real receipt timing is a distribution, not a single date.
How do you treat fixed costs?
Fixed obligations get their own category, separate from variable spend. The reason is simple: when cash gets tight, fixed costs are what makes a P&L-profitable business fail. They don’t flex.
Standard fixed-cost categories in a 13-week model:
- Payroll (weekly or biweekly, including employer taxes and benefits)
- Rent and occupancy (monthly)
- Debt service (loan payments, interest, lease obligations)
- Recurring software and subscriptions
- Insurance (often quarterly or semi-annual)
- Tax remittances (sales tax, quarterly estimated income tax, payroll tax deposits)
McCracken Alliance’s treasury overview (McCracken Alliance) and DebtBook’s forecasting guide (DebtBook) both emphasize this separation: list every recurring obligation by week, with timing and amount, before you touch variable spend.
Variable spend (marketing, travel, contractors, discretionary purchases) gets modeled against recent run rate, with explicit scenarios for upcoming campaigns or hires.
Stop building this by hand every Monday. Start a 14-day free trial. Connect your bank and books and let Fynso build the 13-week forecast for you, refreshed daily.
What’s the weekly maintenance look like?
Monday morning, 15–30 minutes:
- Replace last week’s estimates with actuals. Pull cleared bank transactions, update AR, mark which invoices paid and which slipped.
- Update the variance line. If last week’s forecast said $42K of inflows and you collected $36K, the next 12 weeks need to absorb the $6K gap somewhere.
- Adjust assumptions where reality has shifted. A customer who slipped this week probably slipped the pattern.
- Note the new minimum balance and the week it occurs. Compare to last week.
- One action. What’s the highest-leverage move this week to improve the trajectory?
Done well, the forecast turns from a static spreadsheet into a living management system. Treasury sources consistently emphasize this rolling discipline — DebtBook and Treasury4 both make the same point: the forecast is only valuable if forecast-vs-actual variance is reviewed weekly (DebtBook, Treasury4).
When is this overkill?
For a business under ~$500K of revenue with simple customer payment timing, a 13-week forecast can be more discipline than the data warrants. A simpler 4-week view, updated weekly, is often enough.
The transition point usually shows up around $500K–$1M when one or more of these become true:
- AR aging starts getting heavier than current
- Quarterly events (taxes, insurance, debt service) get large enough to swing a week
- Payroll cycles start landing on inconsistent weeks vs. inflows
- You’re making real decisions on hires, lease, or equipment that depend on a 30–90 day view
At that point, the 13-week format pays for itself in the first month — usually by surfacing one tight week early enough to handle it cheaply.
What we built at Fynso
Fynso runs a 13-week forecast for you every day. It reads your bank balance through Plaid, pulls AR and AP from QuickBooks, factors in payment processor settlement timing from Stripe and Square, and applies the customer-level payment timing model behind the scenes. No spreadsheet, no Monday-morning rebuild.
The forecast comes with named risks (specific customers or events driving any tight weeks), a confidence band that widens when data is thin, and three ranked actions ordered by what would close the biggest gap first.
It also stays honest about what it can and can’t see. A forecast is only as good as the data it has, and Fynso shows you which numbers are high-confidence versus assumed.
Related reading
- Cash Runway for Small Business Owners — the forward-looking number a 13-week forecast computes.
- Cash Flow vs. Profit: The Difference That Decides Whether You Survive — why your P&L profit and your bank balance often disagree.
- How to Read Your Bank Balance Like a CFO — the three numbers behind the balance, including the 13-week view.
- The Payroll Pressure Timeline — the early-warning indicators that show up in a well-maintained 13-week model.
The 13-week forecast you stop having to maintain.
Start a 14-day free trial — connect your bank and QuickBooks, get your live 13-week forecast within 24 hours. No credit card required.
Frequently asked questions
- Why 13 weeks, not 12 or 26?
- Thirteen weeks is one quarter. It captures every weekly payroll cycle, every monthly fixed cost, and every quarterly event (estimated taxes, insurance renewals) within the window. Long enough to spot what's coming, short enough that the math stays grounded in real customer behavior rather than guesses. It's the standard treasury rhythm used by finance teams across industries.
- How accurate is a 13-week forecast really?
- Accuracy depends entirely on data quality. Recent payment history, current AR aging, and known fixed obligations make the model tight. Stale data, missing customer payment patterns, and unmodeled one-time events widen the confidence band. A well-built forecast for a $2M business typically lands within 5–10% of actual for weeks 1–4, and 10–20% for weeks 5–13.
- What's the difference between this and QuickBooks' Cash Flow Planner?
- QuickBooks' Cash Flow Planner is a useful built-in tool for short-horizon visibility based on historical transactions and custom entries. The 13-week treasury method adds AR-aging-weighted receipts, customer-specific payment timing, and explicit scenario modeling. The Planner is good for 'here's what's coming.' The 13-week format is built for 'here's what to do about it.'
- How often should the forecast update?
- Weekly at minimum. The whole point of the rolling format is that last week's estimates get replaced with actuals, and the forecast learns from variance. A 13-week forecast that hasn't been updated in three weeks is no longer a 13-week forecast.
- Can I build this in a spreadsheet?
- Yes, and most finance teams do. The mechanics are straightforward: weeks across columns, line items down rows, opening balance at top, closing balance at bottom. The discipline isn't building it once. It's updating it every Monday with the previous week's actuals, then maintaining the customer payment timing assumptions over time. That's where Fynso replaces the spreadsheet work.
Want Fynso to apply this with your connected data?
See your live forecast in FynsoSources
- https://www.atlar.com/learn/what-is-the-13-week-cash-flow-forecast
- https://www.wallstreetprep.com/knowledge/demystifying-the-13-week-cash-flow-model-in-excel/
- https://www.tesorio.com/blog/dso-countback-method-how-finance-teams-can-accurately-forecast-cash-flow
- https://www.allianz-trade.com/en_US/insights/challenges-of-late-paying-customers.html
- https://www.mccrackenalliance.com/blog/13-week-cash-flow-forecast-how-cfos-gain-visibility-control-and-confidence
- https://www.debtbook.com/blog/a-complete-guide-to-cash-flow-forecasting-methods-for-treasury-teams