.svg)
13-week cashflow forecast for SME CFOs: complete guide (2026)
The instrument for short-term liquidity steering: a weekly-updated view of cash inflows and outflows based on AR/AP-aging, not accrual accounting. Practical for SME CFOs, scaleups, and PE portcos.
.png)
13-week cashflow forecast: weekly cash in/out for the coming quarter. AR/AP-aging as the basis. For liquidity steering, covenant and runway tracking. On multiple levels of detail.
13-week cashflow forecast for SME CFOs: complete guide (2026)
What it is, when you need it, how it’s built, how to run the weekly cycle, and how it fits alongside the other forecast types.
TL;DR
The 13-week cashflow forecast works differently from budget, rolling forecast, or LE. Cadence: weekly (daily in tight periods). Basis: cash transactions — AR-aging with a DSO assumption, AP-aging with a DPO assumption, fixed monthly costs, planned variable expenses. Purpose: short-term liquidity steering. Critical in cash tightness, covenant tracking for PE portcos, runway monitoring for VC portcos and scaleups, and around major cash events. For SME groups with multiple entities: consolidated, per entity, or per cost center. Don’t mix it with rolling forecast — that runs on accrual basis with a different job-to-be-done.
What is a 13-week cashflow forecast?
A 13-week cashflow forecast is a weekly-updated projection of cash inflows and outflows for the coming 13 weeks (one quarter). The instrument has one job: short-term liquidity steering. The question it answers is not “how much profit are we making?” but “will we have enough cash on the bank next week, next month, the coming quarter?”.
Three properties make the 13-week cashflow forecast fundamentally different from the three accrual forecast types (budget, rolling forecast, latest estimate). Cadence: weekly updates are standard, daily in tight periods — whereas budget/rolling/LE typically run monthly or quarterly. Basis: built on actual cash transactions — open AR with expected receipt dates, open AP with planned payment dates, fixed monthly costs with their bank-deduction dates, planned variable expenses — rather than on the accrual accounting underlying the other forecast types. Scope: cashflow only, no P&L and no balance sheet.
It’s a different instrument for a different job-to-be-done. A rolling forecast answers “how are our numbers developing operationally over the next 12-18 months?” and does so on accrual basis. A 13-week cashflow forecast answers “what does our bank account look like week-by-week for the next 13 weeks?” and does so on cash basis. The two are complementary: rolling forecast for strategic steering, 13-week cashflow for tactical liquidity steering.
For the broader context of forecasting in SMEs — including the other three forecast types the 13-week cashflow sits alongside — see the main forecasting guide for SME CFOs. For the operational rolling forecast that runs on accrual basis: see the complete guide to rolling forecast.
When is a 13-week cashflow forecast essential?
Not every SME runs a weekly 13-week cashflow forecast all the time. Four typical situations where it shifts from “nice to have” to “non-negotiable”.
Cash tightness or liquidity crisis
When the cash position gets tight — through revenue shortfall, loss of a major customer, cost spike, or delayed financing — cash monitoring shifts from a reporting activity to a steering activity. A weekly 13-week cashflow becomes the standard; in the week before cash-out, daily updates are normal. The instrument doesn't just tell you whether you'll make it — it gives early warning with enough time to act: draw on credit, defer payments, line up financing, cut costs.
Covenant tracking for PE-financed portcos
Nearly all PE-financed SME portcos carry covenants on leverage ratio, interest coverage, and often a minimum-liquidity clause. A weekly 13-week cashflow with covenant tracking is the standard finance discipline: weekly monitoring of headroom against agreed covenant limits, daily monitoring and early warning to internal management and the PE firm when a breach approaches. For the PE firm, this is the critical input for portfolio management; for the portco CFO, it's the instrument to talk about covenant risk proactively rather than reactively.
Runway tracking for VC portcos and SaaS scaleups
For growth-stage businesses with substantial cash burn — VC portcos in growth phase, SaaS scaleups, businesses in a business-model transition — runway (months until cash-out at current burn) is the most-tracked metric. The input for the runway calculation comes directly from the 13-week cashflow forecast: actual cash burn per week and month based on current AR/AP and planned expenses. Weekly update is standard; with significant burn changes or in the run-up to a fundraise cycle, daily.
Major upcoming cash event
A large one-off cash inflow or outflow deserves its own liquidity monitoring: an acquisition, a major investment (machinery, real estate, software), a dividend payout, a funding round. A 13-week cashflow forecast in the weeks leading up to the event shows whether the liquidity holds, what buffers exist for unexpected delays, and when you return to normal. For the CFO, this is the instrument to take to the CEO and board: can we do this, and if so, under what conditions?
For businesses without one of these situations: monthly cash reporting is often sufficient and cheaper to maintain. But the moment one of these situations hits, the 13-week cashflow forecast is the difference between proactive steering and reactive crisis management.
How is a 13-week cashflow forecast structured?
In practice a 13-week cashflow forecast has a three-layer architecture. How these three layers work together determines whether the weekly update cycle is sustainable.
Layer 1: Raw AR/AP data from the accounting system. Open invoices at transaction level — per debtor and creditor: invoice number, amount, invoice date, and due date. Manual approach: weekly export from the ERP, paste into a source tab. Automated approach: direct ERP connection that syncs every 3 hours — no manual paste work.
Layer 2: Per-invoice allocation to week columns. For each open invoice, determine the week in which the cash is expected to come in or go out. The calculation: Expected date = Due date + Days overdue. “Days overdue” is a DSO/DPO buffer per customer or segment — the average payment delay above the contractual payment term. For SME debtors, 14-30 days overdue is typical; key accounts often shorter, long tail often longer. Based on the expected date, the invoice amount gets placed in the right week column.
Layer 3: Weekly aggregation in cashflow rows. On the cashflow master sheet, the allocated AR/AP amounts are summed per week alongside fixed monthly costs (payroll, rent, lease, quarterly VAT, corporate tax) and variable expenses (capex, dividend, ad hoc). Result: per week an inflow total, outflow total, net cashflow, bank balance (rolling from the previous week), required credit buffer, and available cash as the bottom line. That last one — available cash = bank balance − blocked accounts − required credit buffer — is what you can actually deploy, not just what shows on the bank.
This three-layer architecture is what makes a 13-week cashflow forecast practically sustainable. Without layer 2 (per-invoice allocation with DSO/DPO buffer), you get an over-optimistic picture because all invoices look like they arrive on the due date — a fundamental error in SME practice. Without layer 3 (available cash), you see the bank balance but don’t know what’s actually deployable.
How much AR/AP-level detail? Two approaches
Not every SME needs the same detail level in a 13-week cashflow forecast. In practice, two approaches run alongside each other with different setup cost and different precision.
Approach 1: Aggregated estimation. For SMEs with a manageable debtor portfolio and a limited number of invoices per month. You split open AR into 3-5 buckets (by customer segment or by due-date category) and manually project the expected receipt per bucket per week. Setup time: 30 minutes. Weekly update time: 30-60 minutes of manual work. Upside: quick to set up, intuitive for the CFO who has to hold the model in their head. Downside: less precision, sensitive to estimation errors. Works well with a few dozen open invoices and a stable customer mix.
Approach 2: Per-invoice formula distribution. For SMEs with hundreds of open invoices, a complex AR/AP portfolio, or high dependence on debtor payments. Each invoice gets an expected date (due date + DSO buffer per customer) and is automatically placed in the right week. Setup time: 2-4 hours initially — requires an AR/AP export template, due-date field, DSO assumption per customer, and the week-distribution formula. Weekly update time: 15-30 minutes with automated ERP export, longer with manual pasting. Upside: higher precision, suitable for scenario stress-testing, transparent per debtor. Downside: requires export discipline (or an automated ERP feed) and the formula architecture has to be maintained somewhere.
Which approach fits your situation? Small SME with simple AR/AP and a comfortable bank balance: approach 1. Mid-SME with debtor risk, scenario stress needs, or PE/VC context with covenant or runway pressure: approach 2. Many SME CFOs start with approach 1 and migrate to approach 2 as their AR portfolio or stress level justifies it. For those who want to skip the ERP-export work: a tool with direct AR/AP integration delivers approach 2 without the manual export-paste discipline.
What data do you need?
A 13-week cashflow forecast lives on five data sources. The more accurate and current those sources, the more usable the forecast.
- Open accounts receivable (AR aging) with expected receipt dates. The practical approach: take your AR-aging report at transaction level (per invoice, per customer), apply a DSO assumption per customer or customer segment, and project when each invoice is expected to come in. For key accounts: per customer; for the long tail: per segment with average DSO.
- Open accounts payable (AP aging) with planned payment dates. Same logic but for outgoing payments. Per creditor or segment, the DPO assumption combined with the actual open invoices gives the outflow projection per week.
- Fixed monthly costs with their actual bank-deduction dates. Payroll, rent, lease payments, subscriptions, fixed suppliers, VAT cycle (monthly or quarterly), corporate tax payments. These items are predictable but the exact dates vary per month (the 25th for payroll, first working day for rent).
- Variable expenses with date and amount. Planned purchases, one-off capex, dividend payouts, planned marketing spend, debt repayments. These items are less predictable but for the next 13 weeks often concretely known.
- Opening cash position from bank balances at the start of the forecast, plus available credit lines (current accounts, revolving credit) and any blocked accounts that are not freely available.
Without an automated data feed this is hand-precision work: AR/AP export from the ERP, manual DSO/DPO assumptions, fixed costs manually tracked, bank balances pulled. Per weekly cycle that adds up quickly to 3-5 hours per update — and across a 13-week cycle that’s 50-65 hours per quarter on data work that adds zero decision value.
With an automated actuals feed via a tool like Finstack: AR/AP data flows in at transaction level every 3 hours from the ERP. Bank balances via bank connections. Fixed costs configured as recurring items in the cash model. Only variable expenses and DSO/DPO assumptions need human attention. The weekly update becomes 30-45 minutes instead of 3-5 hours.
The weekly update cycle
A 13-week cashflow forecast that isn’t updated weekly loses its value. The practical cycle has a fixed slot in the finance team’s week, typically Monday or Tuesday.
Refresh bank balances and AR/AP aging
First step: pull current bank balances and the current AR/AP-aging snapshot. With Finstack integration: this happens automatically via the ERP sync (every 3 hours) and bank connection. The forecast shifts by one week: week 1 (the just-closed week) drops out and becomes actual; week 14 gets added at the far end. Critical in this step: reconcile the forecast bank balance against the actual bank balance — without that check, the model drifts structurally after a few weeks.
Review DSO and DPO assumptions
Are there customers where actual receipts deviate from the DSO assumption? Are there creditors where payment terms have shifted? For key accounts: review per customer. For the long tail: review at segment level. Update DSO/DPO assumptions where it makes a material difference for the coming 13 weeks. A DSO assumption of 45 days that turns out to be 65 days in practice gives you a far too optimistic cashflow picture — this is where to fix that.
Update variable expenses and one-off events
Any new planned purchases, capex, dividend payouts, or marketing spend? Have planned events shifted in timing or amount? Update the variable-expense rows in the forecast. For PE portcos: update covenant tracking in parallel. For multi-entity groups: update each entity’s variable items and consolidate at group level (consolidated, per entity, or per cost center — depending on what the stakeholder needs).
Review with CFO and report
The updated forecast is discussed by the controller or cash manager with the CFO. Focus: what changed since last week, are there weeks of tight available cash, what actions are needed? For PE portcos: covenant status reported. With tight weeks: action items with deadlines. The forecast is then presented to management and/or investor in the standard cadence (weekly for PE portcos and crisis mode, monthly otherwise).
Total weekly cycle with well-tooled finance: 30-45 minutes for model work plus 15-30 minutes for the CFO review. Without an automated actuals feed: 3-5 hours for model work — almost always the difference between sustaining a weekly cycle or not.
Specific application: covenant tracking for PE portcos
For PE-financed SME portcos, the 13-week cashflow forecast is almost always tied to covenant tracking. The typical covenants are leverage ratio (net debt / EBITDA), interest coverage (EBITDA / interest expense), and for growth businesses often a minimum-liquidity clause.
The practical setup: in parallel to the cashflow forecast runs a covenant monitor that shows week-by-week where you stand against the covenant limits. With comfortable headroom, weekly monitoring suffices. With an approaching breach (typically <15% headroom), daily monitoring and escalation to both internal management and the PE firm.
For the PE firm, this is the critical input for portfolio management: which portco is at risk, how far ahead, and what proactive actions are available? For the portco CFO, it’s the tool that turns an uncomfortable covenant-breach conversation with the bank into a prepared, proactive amendment discussion with built-up argumentation.
Finstack supports covenant tracking in parallel to the 13-week cashflow forecast: covenant formulas can be configured per scenario, and the monitor moves with the weekly cashflow update. For PE firms with multiple portcos in the portfolio: the partner portal gives consolidated visibility across all portcos on one dashboard, plus per entity and per cost center where relevant.
One practical nuance: covenants are formally tested by the lender quarterly or semi-annually, but PE firms expect continuous internal monitoring between test dates. The 13-week cashflow forecast is precisely the instrument that delivers that between-test visibility — you see not only the current covenant standing but where it’s heading in the run-up to the next formal test. For the portco CFO, that’s the difference between a covenant breach landing as a surprise and a prepared amendment with built-up argumentation.
Specific application: runway tracking for VC portcos and scaleups
For VC portcos, SaaS scaleups, and growth-stage businesses in a burn phase, runway is the standard CFO metric. Runway = current cash position / average monthly cash burn = months until cash-out. It’s one number for board, investor, and CEO communication (“we have 14 months of runway”).
The input for the runway calculation comes directly from the 13-week cashflow forecast: actual expected cash burn per month based on current AR/AP and planned expenses. Without a 13-week cashflow forecast, runway is typically calculated on the average monthly burn over the past 3-6 months — a historical number that ignores planned changes in cost base or revenue ramp.
With a 13-week cashflow forecast, runway becomes dynamic: it reflects planned hires, planned marketing spend, planned customer acquisition, and the actual conversion from AR to cash. For scaleups actively reducing burn (cost measures, price increases, customer-mix shift), this makes a material difference.
Weekly runway update is standard for scaleups; in the run-up to a fundraise cycle, daily, because the pitch deck has to reflect current cash position and burn every day. For scaleups with multiple entities (production BV, sales BV, holding): runway at consolidated level plus per entity, so entity-specific burn rates stay visible.
A practical pitfall we often see in scaleup practice: runway communicated as the average monthly burn over recent months, while the 13-week cashflow forecast shows that burn materially changes in the coming months (planned hires, marketing bursts, AR-to-cash conversion). What works: calculate runway based on planned burn over the next 6-9 months from the 13-week forecast plus the projected burn beyond — not on the historical average. For the board and investors that delivers a better-grounded story: this is what we expect to spend, here’s why, here’s where the cash goes.
What your tool needs to do for 13-week cashflow forecasting
The 13-week cashflow forecast works best as a combination of spreadsheet (for model structure and flexibility) and a tool like Finstack (for automated data feeds and consolidation). Three tool requirements.
1. AR/AP data at transaction level. Trial-balance balances for debtors and creditors are not usable for cashflow forecasting — you need the individual open invoices with their actual due dates. Finstack connects natively at transaction level with Exact, AFAS, Twinfield, Yuki, Pennylane, Nmbrs for NL plus Xero, QuickBooks Online, and Microsoft Dynamics 365 BC for international entities. Sync every 3 hours; AR/AP aging is always fresh in the forecast model.
2. Bank connection for current cash position. The opening position of your forecast must reflect actual bank balances, not last month-end. Finstack supports bank integrations for the standard NL and international banks; current bank balances are available daily for reconciliation of the forecast balance against actual.
3. Cash Overview functionality for continuous monitoring. For weekly — and in tight periods daily — monitoring, a one-page overview is essential: current cash position, the next 4-6 weeks in detail, the 13-week horizon, plus covenant tracking where relevant. Finstack’s Cash Overview feature is built for this: AR/AP aging at transaction level, working-capital views, and multi-entity consolidation. For the full documentation: see the Finstack Help Center page on Cash overview.
And — specifically for multi-entity groups — central consolidation of per-entity cash forecasts. Each entity has its own AR/AP, bank balances, and payment dates; the group view requires consolidation without double-counting (intercompany cash flows must eliminate). Finstack supports this natively via the consolidation engine at transaction level — consolidated, per entity, or per cost center. From EUR 39/month per entity, 14-day free trial.
If you don’t yet run a weekly 13-week cashflow forecast, start small. Week one: AR aging plus AP aging plus fixed monthly costs plus one bank account, for the next 4 weeks (not yet 13). Test whether the cycle is sustainable and whether the numbers reconcile against actual receipts and payments. Then expand to 13 weeks, multi-bank, and covenant tracking where relevant. Start with the 14-day free Finstack trial to experience the AR/AP feed and Cash Overview firsthand.
Explore Finstack.
Free trial for 14 days.
Access to all features. No credit card required.
.png)
Three common mistakes with 13-week cashflow forecasting
Not reconciling forecast bank balance against actual bank balance
The most common structural mistake: the forecast bank balance gets rolled forward week after week without checking against the actual bank balance. Within one quarter, the model drifts 5-15% from reality due to missing or double-booked transactions, wrong DSO assumptions, or unrecorded ad-hoc payments. What works: add a reconciliation row where the forecast bank balance is set against the actual balance every Monday. The difference is a signal for wrong assumptions or unrecorded transactions — fix before modeling further, or you build each week on an unreliable basis.
Modeling only on due date, without a per-customer delay buffer
Debtors rarely pay exactly on the due date. The SME average delay is 14-30 days past due, often shorter for key accounts and longer for the long tail. Modeling purely on due date makes your projected cash inflow run 2-4 weeks ahead of reality — exactly the window the 13-week cashflow forecast is built for. What works: a DSO buffer per debtor or segment (days overdue above contract term) in the model, re-evaluated weekly against actual receipts. Same principle for creditors with a DPO buffer per supplier segment.
Mixing the 13-week cashflow forecast with a rolling forecast
Two different cadences (weekly vs. monthly), different bases (cash vs. accrual), and different purposes (liquidity steering vs. strategic projection). A combined model becomes too coarse for liquidity steering and too detailed for rolling-forecast cadence. What works: keep them separate — rolling forecast in its monthly accrual cycle, 13-week cashflow forecast in its weekly cash cycle. Different jobs, different instruments, different stakeholders. In practice: rolling forecast for the board and annual planning cycle, 13-week cashflow for the weekly CFO/treasury review.
Frequently asked questions
Haven't found your answer? Let us know
What is a 13-week cashflow forecast?
A 13-week cashflow forecast is a weekly-updated projection of cash inflows and outflows for the coming quarter. Built on cash transactions: AR-aging with a DSO assumption, AP-aging with a DPO assumption, fixed monthly costs, and planned variable expenses — not on accrual accounting. Purpose: short-term liquidity steering. Answers “will we make it through next month?” and “how much runway do we have?”.
What is the difference between a 13-week cashflow forecast and a rolling forecast?
Three differences. Cadence: 13-week updates weekly, rolling forecast monthly after the close. Basis: 13-week on cash transactions (AR/AP aging with DSO/DPO assumptions), rolling forecast on accrual accounting (P&L, balance sheet, cashflow statement). Scope: 13-week shows only cash, rolling forecast shows all three statements. Complementary, not interchangeable — different jobs, different cadence, different stakeholders.
When is a 13-week cashflow forecast essential?
Four situations. Cash tightness or liquidity crisis: weekly is standard, daily when cash-out is near. Covenant tracking for PE portcos: monitor leverage ratio and minimum liquidity. Runway tracking for VC portcos and scaleups: how long at the current burn rate? Major cash event: acquisition, funding round, dividend payout. Monthly numbers are too coarse — you need weekly visibility.
What data do you need for a 13-week cashflow forecast?
Five sources. AR aging at invoice level with expected receipt dates (DSO assumption per customer or segment). AP aging at invoice level with planned payment dates (DPO assumption). Fixed monthly costs with actual bank-deduction dates (payroll, rent, lease, VAT, corporate tax). Variable expenses with date and amount (capex, dividend). Opening cash position from bank balances and available credit lines.
How often should I update a 13-week cashflow forecast?
Weekly is standard, typically Monday or Tuesday: the just-closed week drops out, a new week is added at the far end, AR/AP aging and bank balances are refreshed. In tight periods or near covenant breaches: daily. A monthly cadence kills the instrument — you lose the early-warning value the 13-week forecast is built for.
What is the difference between a 13-week cashflow and a runway calculation?
Runway is a derivative of the 13-week cashflow forecast. Runway = current cash position / average monthly cash burn = months until cash-out. One number for stakeholders (“14 months of runway”). The 13-week forecast provides the input — weekly cash burn based on current AR/AP and planned expenses. For scaleups: both are critical — 13-week for steering, runway for board communication.
What is available cash in a 13-week cashflow forecast?
Available cash = bank balance − blocked accounts − required credit buffer. Per week, the amount you can actually deploy, not just what shows on the bank. For SME CFOs, this matters more than total bank balance: a EUR 2M balance with EUR 1.5M blocked gives only EUR 500K of available cash. A standard concept in any 13-week cashflow forecast.
What tool fits best for 13-week cashflow forecasting?
A spreadsheet for model structure plus Finstack for the data feeds. Finstack delivers AR/AP at transaction level from Exact, AFAS, Twinfield, Yuki, Xero, QuickBooks, and MS Dynamics 365 BC, plus the Cash Overview feature and bank connections. Multi-level: consolidated, per entity, or per cost center. From EUR 39/month per entity, 14-day free trial.
CFO turned Founder - Finstack
Sources and provenance
- Finstack Help Center — Cash overview — AR/AP aging at transaction level, working-capital views
- Finstack Help Center — Sources & connections — ERP connections and sync frequency (3 hours)
- finstack.io — Reporting & insights — cashflow dashboards and continuous monitoring
- finstack.io — Spreadsheet sync — 2-way Excel and Google Sheets integration
- finstack.io — Integrations — native ERP connections at transaction level
- finstack.io — Pricing — pricing plans and trial
Last reviewed: 19 June 2026 · Next review: September 2026
Consolidated reporting and forecasting.
