13 Week Cash Flow Forecast: Build One You Can Trust

TL;DR: A 13-week cash flow forecast is a rolling, weekly projection of cash in and cash out over the next quarter, built with the direct method. In a B2B tech company the outflows are mostly known weeks ahead, so the forecast succeeds or fails on customer receipts. Build that line invoice by invoice from how each customer actually pays, then review the variance with your collections team every week.

A 13-week cash flow forecast is a weekly projection of the cash a business expects to receive and pay out over the next 13 weeks, starting from the cash it holds today. It uses the direct method, so it tracks actual receipts and payments rather than accounting profit, and it rolls forward one week at a time.

Most templates treat customer receipts as one line, driven by days sales outstanding (DSO) or by invoice due dates. That is the weakest assumption in the model. Payroll and rent land on dates you already know. What your customers pay, and when, is the part you are guessing, and in a B2B tech company it is usually the biggest number on the page. This guide shows how to build the receipts line from invoice-level AR data and real payment behavior, and how to run the weekly review that keeps it honest.

What is a 13-week cash flow forecast?

It is a short-term liquidity tool. Each column is a week, each row a source or use of cash, and the bottom line is the cash you expect to hold at the end of each week.

The difference from the monthly forecast your FP&A team already runs is granularity. A weekly view catches the payroll Friday that falls before a large customer payment, which a monthly total hides. Because it is built on the direct method, non-cash items such as depreciation never appear.

The format grew up in restructuring. Wall Street Prep still describes it as a tool used “in the context of corporate restructuring”, where lenders and courts want weekly proof of liquidity. That history explains why so many templates look the way they do. It does not mean you need to be in trouble to use one. Advisory firm Cherry Bekaert argues that running it proactively, before any distress, is what prevents the liquidity crunch in the first place.

Why 13 weeks?

Thirteen weeks is one quarter. It is short enough that most of the inputs are things you already know, such as invoices already issued and payroll already scheduled, and long enough to arrange financing or change spending before a shortfall arrives.

Precision falls off across the horizon. The first four weeks should be close to exact, while the last few are directional. That is fine, as long as everyone reading the forecast knows which weeks are commitments and which are estimates.

The appetite for this kind of visibility is not limited to companies in distress. In the 2026 AFP Treasury Benchmarking Survey, based on 425 treasury practitioners, cash and liquidity forecasting was both the most challenging treasury activity (49%) and the top priority overall (63%).

What goes into a 13-week cash flow model?

The layout is simple. Keep receipts split by source, because each source behaves differently.

How do you forecast customer receipts accurately?

Forecast each open invoice on the date that customer is likely to pay it, not on its due date and not from an average. Then adjust for the two things that take cash out of the base case: open disputes and payments you have already received but not yet matched.

The usual approach spreads receivables with DSO. Take $6.0M of open AR and a DSO of 52 days, and the model collects about $808,000 every week. The number is smooth and easy to defend in a meeting. It is also wrong in almost every individual week, because DSO is an average across customers who behave very differently. Your largest enterprise account may pay three weeks after due date as a matter of AP policy. Your mid-market customers on card autopay pay on the day. The average describes neither. Our guide to accounts receivable forecasting covers the methods behind this in more depth.

The scale of late payment makes this more than a rounding issue. Atradius found in its 2026 US survey that late payments affect an average of 22% of US B2B receivables, and that about seven in ten companies still face them. In Upflow’s own research across thousands of B2B tech finance teams, published in From Zero to Collected, the median company would have a DSO of 23 days if every customer paid on the due date, against an actual median of 52. That 29-day difference is time your forecast has to place somewhere, and due dates put it nowhere.

A DSO of 52 days is the median in Upflow’s research, so the first question is where your own sits. Our free DSO calculation spreadsheet gets you the number in minutes.

Here is the method.

1. Start from open invoices, not the aging total. Pull every open invoice with customer, amount, due date and status. Remove credit notes and anything written off, since they clear a receivable but bring in no cash.
2. Give each customer a payment profile. For each customer, take the median number of days between due date and payment across their last six to twelve paid invoices. For customers with too little history, use the profile of their segment.
3. Set an expected payment date for each invoice. Due date plus the customer’s typical days late. If the customer has given a promise to pay, use that date instead.
4. Take disputed invoices out of the base forecast. A disputed invoice will not pay on its normal pattern. Hold it in a separate row, and only move it back once the dispute has an owner and a resolution date.
5. Remove unapplied cash. Payments received but not yet matched to invoices still show as open AR. That cash is already in your opening balance, so forecasting it again counts it twice.
6. Forecast future billings with a collection curve. For invoices you have not issued yet, use the share of each billing month historically collected by week. In tech companies with annual upfront billing, map renewal invoices to their actual dates, because January and fiscal year ends can concentrate a quarter’s receipts in a few weeks.

If you run Upflow, Upflow Insights covers the inflow side of this. It forecasts cash based on how customers really pay, informed by promise-to-pay dates and detected disputes, and layers in upcoming billings to forecast past your current AR.

A worked example: six invoices, two weeks

Take a B2B tech company with $40M in annual recurring revenue. Here are six items from its AR ledger that fall due in weeks 1 and 2 of the forecast. The figures are illustrative.

The due-date view expects $1,080,000 from these items in weeks 1 and 2. The invoice-level view expects $197,000: customer B’s $85,000 plus $112,000 from the long tail.

The other $883,000 has not disappeared. $608,000 moves later inside the horizon (customer A to week 4, customer C to week 3, $48,000 of long tail to weeks 3 to 6). $210,000 waits on a dispute. $65,000 is already in the bank. But if week 2 is a payroll week and your minimum cash threshold is tight, those two views lead to very different decisions.

How do you forecast disbursements?

Keep this part simple, because it is the part you control. Payroll comes from the payroll calendar, vendor payments from your AP aging and payment run schedule, and fixed obligations from their contracts. One-off items, such as annual bonuses or a large software renewal, need a named owner who confirms them each week. Most disbursement errors trace back to items nobody told finance about.

How to build a 13-week cash flow model step by step

1. Reconcile opening cash. Use cleared bank balances on the first day of week 1, not the general ledger.
2. Load open AR at invoice level and apply the receipts steps above.
3. Add future billings with a collection curve built from the last four to six billing months.
4. Add disbursements by category, each on its own row.
5. Calculate closing cash for each week and compare it with your minimum cash threshold or covenant.
6. Save a copy of this version before you change anything next week. You cannot measure variance against a forecast you have overwritten.

How do you roll the forecast forward each week?

Rolling forward is two jobs: replace last week’s forecast with actuals and add a new week 13. Then compare what you expected with what happened, line by line, before you touch any assumption.

Measure receipts accuracy as the absolute variance divided by actual receipts for each week, and track it for weeks 1 to 4 over time. There is no widely accepted independent benchmark for 13-week forecast accuracy at mid-market scale, so set your own tolerance band and tighten it as the model improves.

The more useful habit is a 30-minute weekly meeting between whoever owns the forecast and whoever owns collections. Bring the ten largest receipts variances by customer and label each one: paid later than profile, dispute, broken promise to pay, billing error, or unapplied cash. Each label has its own owner and fix. A broken promise goes back to the collector that week. A billing error goes to billing operations. A customer whose days late keep growing goes to their account owner before the renewal conversation.

This is where the forecast becomes a collections tool. From Zero to Collected treats promises to pay kept and accounts paying later than before as live signals to check every week, while there is still time to act. The forecast variance is the same signal expressed in cash. Christina Liu, CFO at Sigma Computing, put the cross-team point plainly when talking about how finance and sales work together: “The transparency and the visibility drives accountability, which is the common language between finance and sales.”

This shared ownership is the core of Financial Relationship Management (FRM), the discipline of managing the financial relationship with a customer, from the moment payment terms are agreed until cash is collected and reconciled. Applied to a 13-week forecast, it means the receipts line belongs to finance and collections together.

What mistakes make a 13-week forecast drift?

• A DSO plug for receipts. It hides customer concentration and timing.
• Due dates treated as payment dates. With late payments touching more than a fifth of US B2B receivables, this is optimism built into a formula.
• AR balance confused with cash. Credit notes and write-offs clear a receivable but bring in nothing, and unapplied cash is already in the bank.
• No saved versions. Without last week’s forecast, there is no variance and nothing to learn from.
• One owner. A forecast built by FP&A alone misses what the collections team heard on this week’s calls.

Do you need a 13-week cash flow template or software?

A spreadsheet is fine for the model itself, especially for disbursements, which are known in advance. The problem is the receipts input. If someone exports an aging report every Monday and rebuilds payment profiles by hand, the forecast is only as fresh as that export.

The PwC 2025 Global Treasury Survey of 350 treasurers points the same way: poor data quality (76%) was the most cited obstacle to better forecasting, ahead of a lack of effective tools (53%). Among companies with more than $1 billion in revenue, 38% to 52% still collect forecast data manually, which PwC links to low satisfaction scores (2.9 out of 5, against 3.3 for integrated or system-based forecasting).

So keep the template, but feed the receipts rows from your AR system at invoice level, refreshed weekly. Upflow syncs two ways with ERPs such as NetSuite and Sage Intacct and with CRMs such as Salesforce and HubSpot, so open invoices, promises to pay, disputes and account owners sit in one place. Upflow Collections is where the team works the gaps the forecast exposes, and Upflow’s MCP server brings that receipts view into Claude, ChatGPT or Copilot to build the wider cash picture.

For a broader view of forecasting methods beyond the 13-week format, see our guide to cash flow forecasting.

Before changing the process, it helps to see how your receivables behave today. Connect your ERP or billing tool to Upflow Discover and see your DSO and other AR metrics for free.