The 13-week cash flow forecast is one of those tools that most finance professionals have heard of but far fewer have actually built and maintained. It is associated primarily with distressed situations and turnarounds, which is why healthy businesses tend to avoid it. That is a mistake.
A 13-week forecast is not a sign of financial difficulty. It is a sign of financial discipline. Banks want to see it. Boards should want to see it. And any business with meaningful cash flow variability, which includes most project-based companies, seasonal businesses, and growing companies with working capital intensity, benefits from having one.
This article explains the mechanics of building it, what to include, how to keep it current, and how to use it.
Why 13 Weeks
The 13-week horizon is not arbitrary. It is long enough to identify a cash problem before it becomes a crisis and short enough that the forecast can be built with meaningful precision.
A 12-month cash flow forecast for most businesses is reasonably accurate for the first quarter and increasingly speculative thereafter. The assumptions about revenue timing, client payment behaviour, and cost phasing become less reliable the further out you project. A 13-week forecast concentrates the work where it produces the most reliable output.
Thirteen weeks is also approximately one quarter, which aligns naturally with the business planning cycle. The quarterly re-forecast produces an updated full-year view. The 13-week cash forecast provides the granular near-term liquidity picture that the full-year view cannot.
The Architecture: Three Tabs
A well-built 13-week forecast in Excel has a clean three-tab structure: inputs, calculations, and a dashboard. Keeping these three elements separate is the most important structural decision, because it determines whether the model can be updated efficiently each week or requires a rebuild.
Tab 1: Inputs. This tab contains all the raw data that feeds the forecast. Cash inflows are entered by week and by source. Cash outflows are entered by week and by category. Nothing in this tab should be a calculated result. Everything should be a direct entry or a formula that pulls from a source system or another input cell.
The inflow section should list every expected receipt individually, not aggregated by category. Each client payment gets its own row with the expected week of receipt. Each milestone payment gets its own row. This granularity is what makes the forecast actionable: when a payment slips, you update that specific row and see the impact immediately.
The outflow section can be more aggregated for predictable fixed costs, but variable or project-specific outflows should still be entered individually.
Tab 2: Calculations. This tab aggregates the inputs into a weekly summary and calculates the cash position. The calculation is simple: opening cash plus total inflows minus total outflows equals closing cash. The closing cash of week N is the opening cash of week N+1.
This tab also produces the comparison between current forecast and prior week forecast, and between forecast and actuals for completed weeks. These comparisons are the management information that makes the model useful.
Tab 3: Dashboard. A one-page view showing the weekly cash balance across the 13-week horizon, the minimum cash position within the horizon, the distance between the minimum projected balance and the defined minimum threshold, and a summary of the largest single inflows and outflows expected in the next four weeks.
What to Include: Inflows
Map every expected cash receipt for the 13-week period, by week.
For businesses with contracted or invoiced revenue, this means going through the current accounts receivable ledger and assigning each outstanding invoice to the week it is expected to be collected, based on the invoice due date, the client’s payment terms, and the client’s historical payment behaviour. Not when it should be paid. When it will be paid. That distinction matters enormously. A client who consistently pays 15 days after the due date should be forecast 15 days after the due date, not on the due date.
For businesses with project milestone payments, list each milestone, the expected approval and payment date, and the amount. Include only milestones that have been formally agreed or invoiced, not pipeline items.
For businesses with recurring revenue, the collection timing should follow the standard pattern adjusted for any known exceptions.
Do not include revenue that has not been invoiced unless there is a specific contractual basis for expecting it. Forecast optimism on inflows is one of the most reliable predictors of cash shortfalls.
Also include any non-operating inflows expected in the period: drawdowns on credit facilities, asset disposal proceeds, tax refunds, and any other identified cash receipts.
What to Include: Outflows
Outflows are generally more predictable than inflows, which is both an advantage and a discipline. The advantage is that you can map them with precision. The discipline is that you cannot be optimistic about them the way you might be tempted to be with inflows.
Payroll is typically the largest single outflow and has a fixed payment date. Include gross payroll, and include the associated social contributions separately on their payment dates. In Switzerland, AHV/IV/EO/ALV contributions are typically paid monthly, BVG contributions depend on the pension fund arrangement, and SUVA/accident insurance follows its own schedule.
Rent and lease payments are fixed amounts on fixed dates.
Loan repayments and interest are scheduled, so they can be entered for the full 13-week period at the start.
Supplier payments require a review of the accounts payable ledger. For each outstanding invoice, assign it to the week it will be paid based on payment terms and cash availability. For ongoing supplier relationships, estimate the invoices that will arrive and be paid during the 13-week period.
Tax payments in Switzerland include MWST (VAT) quarterly remittances, direct federal tax installments, and cantonal tax installments. Map each payment to its due date.
Discretionary and project-specific outflows should be entered individually if they are material: a planned equipment purchase, a consulting contract payment, a marketing campaign spend.
The Weekly Update Discipline
The forecast only works if it is updated every week. The update process has four steps and should take no more than 60 minutes.
Step 1: Record actuals. Lock week 1 by replacing the forecast figures with the actual cash movements for the completed week. This step creates the variance history.
Step 2: Review and update weeks 2 through 13. Go through the inflows line by line. Has any expected receipt slipped? Has a new receipt been confirmed? Are there any changes to amounts? Then review the outflows. Any changes to timing or amounts?
Step 3: Add week 14 as the new week 13. The forecast always covers 13 weeks forward. As one week closes as actuals, add a new week at the far end. This requires extending the outflows that are known (loan repayments, rent) and making initial estimates for the inflows in the new week.
Step 4: Review the dashboard. After the update, spend five minutes looking at the dashboard. What is the projected minimum cash balance? When does it occur? How far is it from the minimum threshold? Are there any weeks where a cluster of large outflows creates a temporary trough that warrants attention?
The output of the weekly update is not just a number. It is a set of decisions: are any inflows at risk of not arriving? If so, what action is needed to accelerate collection? Are there any outflows that can be deferred if needed? What is the minimum buffer and is it sufficient?
Variance Analysis: The Learning Tool
The comparison between forecast and actual for completed weeks is not bookkeeping. It is the feedback mechanism that improves forecast accuracy over time.
Every week, calculate the variance between what you forecast and what actually happened, for both inflows and outflows. If inflows are consistently coming in 10 percent below forecast, you have a systematic collection problem or a systematic optimism bias in the way you are forecasting. Either way, the variance history tells you to adjust your forecasting methodology, not just the numbers.
Common patterns to look for:
If payroll is consistently slightly over forecast, you probably have overtime or variable components that are not being captured in the base estimate. Add them.
If specific client payments are consistently 5 to 10 days later than the invoice due date, build that delay into their individual forecast rows permanently.
If supplier payment outflows are consistently higher than forecast, you may have invoice volumes arriving faster than expected, or payment terms that are shorter than you assumed.
The goal is not a perfect forecast. It is a consistently calibrated one that identifies material deviations in time to act on them.
What to Show the Bank
When presenting a 13-week forecast to a bank, the format should be clean and the narrative should be direct.
Banks want to see three things: the forecast weekly cash balance, the minimum projected balance within the horizon and when it occurs, and the assumptions behind the key inflows. A brief written summary alongside the Excel output, explaining the two or three largest inflows expected in the period and the basis for expecting them, is worth more than a detailed model that requires interpretation.
If the forecast shows the cash balance approaching the minimum threshold at any point, present that proactively with the planned response. Banks do not object to companies having periods of lower liquidity. They object to being surprised by them.
Struggling with cash visibility? Book a free 30-minute call to discuss your situation.
Alessandro Ratzenberger is a fractional CFO and business controller based in Zurich, with 15 years of operational finance experience at Dufry Group and Bomi (UPS Group).