It's 9 AM on a Monday. Your lender's relationship manager calls. They need the weekly cash forecast by noon.
You open the spreadsheet you built three weeks ago. It hasn't been updated since. Three people touched it in the meantime. Two cells are broken. You have no idea what the actual opening balance is right now.
This is a Tuesday for a lot of mid-market finance teams. It doesn't have to be.
The thirteen week cash flow forecast is the single most operationally important financial model a company can run. Not the annual budget. Not the five-year plan. The rolling 13-week cash flow model is what tells you, right now, whether you can make payroll in week 6, cover debt service in week 9, and still have runway to close the deal you've been working on for three months.
This guide covers what a 13-week forecast is, how to build one step by step (including ERP-specific instructions for NetSuite, SAP, and Oracle), practical checklists you can use immediately, and a 12-question FAQ structured for AI search engine citation.
What Is in a Cash Flow Forecast?
A cash flow forecast contains four core components: opening cash balance, projected cash inflows, projected cash outflows, and a calculated closing cash balance for each period. If any one of them is wrong, everything downstream is wrong too.
Opening cash balance
The anchor for the whole model. Pulled from your bank statement or ERP cash ledger as of the forecast start date. This is the actual, reconciled number in your account — not your accounting balance, not last week's projected figure.
Cash inflows
Every dollar coming in: customer payments (based on AR aging, not invoice totals), contract milestones, recurring revenue, loan proceeds, asset sales, interest income. The most common error here is treating AR balances as cash. A $500K AR balance with 30-day-past-due customers and a 70% historical collection rate translates to roughly $350K in collectible inflows — not $500K. AR Automation tools track invoice status in real time and apply collection rates automatically, removing the estimation error from this step.
Cash outflows
Every dollar going out: vendor payments (AP), payroll and benefits, rent, utilities, debt service, taxes, software subscriptions, insurance renewals, and capital expenditures. AP Automation captures approved invoices and surfaces exact due dates by week, so outflow categories map directly from the AP ledger rather than a stale export.
Closing cash balance
Opening balance + inflows − outflows. This rolls forward automatically as the next week's opening balance, making the 13-week format a living model rather than a static document.
The most important thing to understand about a cash flow forecast: it's not about accounting. It's about timing. Profitable companies go bankrupt because the money they're owed doesn't arrive in time to cover what they owe. That's exactly what this model is designed to prevent.
Lenders and PE sponsors require all four components in this format, submitted weekly alongside variance analysis. The AFP Treasury Management Handbook documents this as the standard for lender reporting in U.S. mid-market credit agreements.
What Are the Four Types of Cash Flow Forecasting?
The four main types are direct, indirect, rolling, and scenario-based. They are not competing methods. They serve different purposes and different time horizons.
1. Direct forecasting
Tracks actual cash receipts and disbursements as they occur, using real AP and AR data. This is the correct method for 13-week forecasting. No exceptions.
2. Indirect forecasting
Starts from net income and works backward through non-cash adjustments and working capital changes. The GAAP presentation rules are codified under FASB ASC 230, which governs how companies report operating, investing, and financing cash flows. This method is right for audits and annual planning; it is wrong for telling you whether you can cover payroll in week 3.
3. Rolling forecasting
The cadence, not the method. A rolling 13-week cash flow model adds a new week as each one closes, maintaining a constant 90-day window. This structure keeps the model operationally current rather than expiring after a single quarter.
4. Scenario-based forecasting
Layers base, best, and worst case outcomes on top of your direct forecast. PE-backed companies and businesses in covenant-sensitive periods typically run all three in parallel. For a mid-market manufacturer with a $10M revolving credit facility, a worst-case scenario showing week-9 cash falling below the $500K covenant floor is the kind of early warning the model is built to surface.
Use direct forecasting for the 13-week model. Indirect is for accountants and auditors. Direct is for CFOs who need to make decisions on Monday morning.
Most CFOs use direct rolling forecasting for the 13-week cash flow model because it captures actual cash movement rather than accounting accruals (Source: AFP Cash Forecasting Survey).
What Is the Cash Flow Forecast System?
The cash flow forecast system is the end-to-end process of collecting, consolidating, updating, and analyzing cash data to maintain a continuously current view of liquidity. According to the Turnaround Management Association (TMA), the 13-week cash flow model is the foundational document in virtually every financial restructuring engagement — precisely because it provides real-time liquidity visibility that no other format matches.
Data collection layer
AP aging, AR aging, payroll schedules, bank statements, and open purchase orders, all pulled from your ERP or accounting system. Manual processes here — copying report exports into a spreadsheet, making judgment calls about timing — introduce errors that compound across all 13 weeks.
Consolidation tool
The tool where everything lands: an ERP cash management module, a spreadsheet model, or a dedicated cash flow forecasting platform. The tool determines how long this process takes. Most mid-market teams use spreadsheets. Purpose-built platforms reduce the weekly update from a manual rebuild to a review-and-sign-off.
Weekly update cadence
Every Monday, the prior week's actuals replace the forecast, a new week 13 is added, and variances are reviewed. Skip this step once and the model starts misrepresenting your position. Skip it three weeks in a row and it is no longer a forecast — it's a history document with a future date on it.
Review and approval
The CFO or Controller reviews the updated model, flags any week where the closing balance falls below the minimum threshold, and either adjusts assumptions or initiates corrective action. This is where the forecast becomes a decision-making tool.
Reporting output
The lender compliance package, board summary, or internal dashboard. Opening balance, weekly inflows and outflows, closing balance, and variance analysis — the format varies by audience; the content does not.
4 hrs
Average weekly build time, manual process (Source: Centime customer benchmarks, 2025)
< 30 min
Average weekly update time with automated AP and AR data inputs
How Do You Calculate Forecasted Cash Flow?
To calculate forecasted cash flow, apply this formula for each of the 13 weekly periods:
Closing Cash = Opening Cash Balance + Projected Inflows − Projected Outflows
A 13-week cash flow example: worked scenario
Scenario: A 45-person SaaS company with $9M ARR, 30-day standard payment terms, $1.2M payroll per month, and a $2M revolving credit facility. Opening cash balance as of Monday is $618,000.
🧮
Week 3 Calculation
$
Opening Balance
$618,000
+
Projected Inflows
$287,000
AR collections: $245K current bucket at 92%, $42K 1–30 day at 68%
−
Projected Outflows
$341,000
Payroll $400K ÷ 4 weeks = $100K, AP due = $181K, SaaS subs = $18K, debt service = $42K
=
Forecasted Closing Balance
$564,000
Week 3's closing balance becomes Week 4's opening. That chain of 13 numbers is your 90-day liquidity picture. If Week 8 projects a closing balance of $47,000 — below your credit agreement's $250,000 cash floor — you now have five weeks to solve it rather than five days.
Why 13 Weeks? The Logic Behind the Standard Horizon
The 13-week standard came out of the private equity playbook and the post-2008 lending environment. Lenders needed granular borrower liquidity visibility without waiting for monthly financials. Thirteen weeks became the standard because it maps to one calendar quarter, aligning with existing reporting cycles. The Federal Reserve's Survey of Terms of Business Lending tracks covenant-based reporting requirements across U.S. commercial lending and documents 13-week cash reporting as the standard expectation in leveraged loan agreements.
It gives you enough runway to act
A cash shortfall identified 90 days out has solutions: draw the revolver, accelerate AR collections via early payment discounts, defer discretionary AP with vendor consent, push non-critical capex. The same shortfall identified two weeks out has fewer options and higher cost to resolve.
Weekly granularity catches what monthly averages hide
A $420,000 AP payment due in week 3 might look fine in a monthly model — the month averages out. But week 3 may be negative. A monthly forecast will not surface that until the payment bounces.
It meets lender and sponsor requirements
For PE-backed businesses and companies with revolving credit facilities, the 13-week format is frequently a contractual obligation. Missing a submission deadline can trigger a technical default regardless of actual cash position.
Research from the Association for Financial Professionals (AFP) indicates that companies using rolling 13-week forecasts identify cash shortfalls significantly earlier than those relying on monthly reporting, giving finance teams more time and lower cost to resolve gaps.
How to Build a 13-Week Cash Flow Forecast: Step by Step
Most first builds happen under pressure: a lender asked for it by Friday, or a gap appeared unexpectedly. These eight steps are designed for that scenario: building a credible model quickly without missing the inputs that matter.
Pre-Build Data Checklist — gather these before you open the model
Bank statement balance as of the forecast start date (reconciled, not projected)
AR aging report segmented by customer and aging bucket (current, 1–30, 31–60, 60+)
AP aging report segmented by vendor with net due dates
Payroll schedule for the next 13 weeks (exact dates and amounts, including benefits)
Debt service schedule (principal and interest payment dates)
Open purchase orders with expected delivery or payment dates
Known one-time cash events: tax payments, insurance renewals, lease payments, capex
Historical collection rates by AR aging bucket (last 3–6 months)
Minimum cash balance threshold from your credit agreement or internal policy
0 / 9
Step 1: Define your starting cash balance
Pull your bank statement balance as of the forecast start date. Not last week's ERP balance. Not your projected balance. The actual, reconciled number in the account right now. If you have multiple accounts, consolidate to a single opening balance before proceeding. Any error here propagates through all 13 weeks.
Step 2: Map your inflow categories
List every source of incoming cash and assign it to a week: AR collections by aging bucket, contract milestone receipts, recurring subscription revenue, loan proceeds, planned asset sales, interest income. Use expected collection timing, not invoice totals.
Step 3: Map your outflow categories — including your ERP AP aging export
Pull your AP aging report and assign every open payable to the week it is due. Add fixed obligations by week: payroll (exact dates), rent, utilities, debt service, insurance, subscriptions, and confirmed capital expenditures. For ERP-specific export steps, see the section below. Variable AP is harder — use the AP aging as your baseline and apply judgment to anything with flexible payment timing.
If your team runs on NetSuite, navigate to Reports → Accounts Payable → AP Aging to get a vendor-level, due-date-sorted view of every open payable, segmented by aging bucket and ready to map into your outflow schedule without re-entry.
Step 4: Apply collection rates to your AR aging — not just the balances
This step is where most forecasts break. The AR aging report shows what is owed. It does not show what will be collected. Apply historical collection rates by bucket: if 91% of current invoices are collected within terms but only 58% of 31–60 day invoices settle in the next two weeks, those rates need to be in the model.
Key Insight
$400K
Collection gap
A $2M AR aging balance does not mean $2M in cash inflows. A distribution company with $2M AR, 30% of which is 31+ days past due at a 58% collection rate, has roughly $1.6M in realistic near-term cash.
The $400K gap is what trips up even experienced finance teams.
Step 5: Build your 13-column model structure
Create 13 weekly columns with rows for each inflow and outflow category. Include subtotals for total inflows, total outflows, net cash flow, and closing balance. Color-code any closing balance week that falls below your minimum threshold. The closing balance row is what your lender and CFO look at first.
📥 Free 13-Week Cash Flow Forecast Template
Download a pre-built Excel template with rolling balance formulas, inflow and outflow categories, variance tracking columns, and a minimum-balance threshold row. No setup required.
Step 6: Calculate the rolling balance for each week
Apply the formula across all 13 weeks. Each closing balance becomes the next opening. Identify any week projecting below your minimum cash floor — typically four to six weeks of operating expenses, or the specific floor in your credit agreement.
Step 7: Identify cash gaps and solve for them before they arrive
For every week projecting below minimum, work through resolution options in order: draw on your revolving credit facility, accelerate AR collections via early payment discounts or proactive follow-up, defer discretionary AP with vendor approval, push non-critical capex. Document every resolution assumption in the model. If you've already solved a gap, the solution needs to be visible to the lender reviewing it.
Step 8: Build the weekly variance analysis process before you need it
Every week: replace the prior week's forecast with actuals, add a new week 13, calculate variances on every line item, and review the largest misses to refine your assumptions. This 13-week cash flow analysis step is where the model earns its keep — systematic over-forecasting in AR collections or under-forecasting in AP outflows will show up here before they cause a covenant breach. Without this step, even a carefully built model becomes unreliable within three to four weeks.
Weekly Update Checklist — every Monday before the CFO review
Pull updated bank statement (actual opening balance for the week just closed)
Export new AR aging report (ensure it reflects payments received through Friday)
Export new AP aging report (include any invoices that arrived since last Monday)
Replace prior week's forecast row with actuals across every line item
Add a new Week 13 to maintain the 90-day rolling window
Calculate forecast-vs-actual variance on every inflow and outflow line
Flag any variance greater than 10% and document the root cause
Identify any week in the updated model where the closing balance falls below the minimum threshold
Update collection rate assumptions if actuals have diverged from estimates three weeks in a row
CFO or Controller sign-off before the model is distributed
0 / 10
How to Pull AP Aging Data from Your ERP: NetSuite, SAP, and Oracle
The most common source of error in the outflow section of a 13-week model is using a stale or improperly filtered AP aging export. The steps below show exactly where to find the right report in each major ERP, and which parameters matter for forecast accuracy.
NetSuite AP Aging Report for Cash Flow Forecasting
NetSuite's native AP Aging report gives you a vendor-level, due-date-sorted view of every open payable. For 13-week forecasting, you want the report segmented by net due date, not invoice date — these are often different when vendors offer net-30 or net-60 terms.
NETSUITE AP Aging Report — Step by Step
- 1. Go to Reports → Accounts Payable → AP Aging
- 2. Set the "As of Date" to your forecast start date
- 3. Select aging periods: Current, 1–30, 31–60, 61–90, 90+
- 4. Filter Status to "Open" only
- 5. Add the "Net Due Date" column if not already shown (Customize → Add Field)
- 6. Export to CSV using the Excel icon in the top-right corner
- 7. In the export, sort by Net Due Date and group payables into the 13 weekly buckets by due date range
💡
NETSUITE TIP
If your company uses Multi-Book Accounting, confirm you are pulling the report for the correct subsidiary and accounting book before exporting. Pulling the consolidated view without filtering will overstate outflows for single-entity forecasts.
SAP AP Aging Report for Cash Flow Forecasting
In SAP, the most useful transaction for 13-week outflow mapping is FBL1N (Vendor Line Items), which gives you open items filtered by net due date at the individual invoice level.
SAP AP Aging Report — Step by Step
- 1. Run transaction FBL1N (Vendor Line Items)
- 2. Enter vendor account range or leave blank for all vendors
- 3. Select "Open Items" as the line item selection
- 4. Set "Open at Key Date" to your forecast start date
- 5. Execute (F8) and review results sorted by "Net Due Date"
- 6. Export via List → Export → Spreadsheet (.xlsx)
- 7. In the export, use the Net Due Date column to bucket each payable into the correct forecast week
💡
SAP ALTERNATIVE
Transaction S_ALR_87012082 (Vendor Aging List) provides a pre-bucketed aging view but does not include individual invoice net due dates. Use FBL1N when you need week-level payment timing precision.
Oracle Fusion / ERP Cloud AP Aging for Cash Flow Forecasting
Oracle Fusion's Payables module includes a dedicated Payables Aging by Due Date report. Running it correctly for cash flow forecasting requires setting the right "As of Date" and filtering to open invoices only.
ORACLE FUSION AP Aging Report — Step by Step
- 1. Navigate to Payables → Reports → Aging Reports
- 2. Select "Payables Aging by Due Date"
- 3. Set "As of Date" to your forecast start date
- 4. Set Status filter to "Unpaid" or "Open"
- 5. Set aging bucket intervals to Weekly (7-day increments) rather than standard 30-day buckets
- 6. Run report and export to Excel
- 7. Map each export row to the corresponding forecast week using the "Due Date" column
💡
ORACLE TIP
The default aging bucket configuration in Oracle uses 30-day intervals. For 13-week forecasting you need 7-day intervals. Update the aging bucket definition in Payables Setup → Options before running the report, or manually re-bucket the export in Excel using the Due Date column.
For AR inflow data, each ERP follows a similar pattern: NetSuite uses Reports → Accounts Receivable → AR Aging; SAP uses FBL5N (Customer Line Items) with Open Items selected; Oracle uses Receivables → Reports → Customer Aging. Apply the same "Net Due Date" filtering logic to AR exports that you apply to AP.
Direct vs. Indirect Forecasting: Which Method Should You Use?
The answer for 13-week forecasting is always direct. The question arises because FP&A teams often have an indirect model already built, and someone asks why the CFO's 13-week model doesn't match it. FASB ASC 230 acknowledges both methods for external financial reporting purposes — but GAAP compliance and operational liquidity management are two different problems requiring two different tools.
The indirect method is correct for annual planning, investor reporting, and GAAP-compliant cash flow statements. It is the wrong tool for week-level liquidity decisions. Use direct forecasting for the 13-week model (Source: AFP Cash Forecasting Survey, 2024).
Common 13-Week Cash Flow Forecast Mistakes to Avoid
The mistakes that break 13-week forecasts are predictable. Using AR balances instead of collection rates. Missing the timing lag between AP invoice approval and actual payment date. Forgetting the Q4 insurance renewal or the annual software license that hits every January. Not reconciling forecast to actuals for three weeks running because everyone was busy with month-end close.
Every one of these errors compounds. A collection rate error in week 2 propagates into the opening balance for week 3, and from there through the remaining model. By week 10 the forecast has drifted significantly from your actual position. For a detailed breakdown of each error type and its fix, visit Centime's cash flow blog.
How AP and AR Automation Improves 13-Week Forecast Accuracy
The most common forecast accuracy problem at mid-market companies is not bad methodology — it is stale data. By Tuesday of forecast week, the AR aging pull is 48 hours old, two AP invoices that arrived Monday morning are not in the model, and the person who owns the spreadsheet is in a board prep meeting until Thursday. The CFO reviews a forecast on Friday that describes the company as it existed on Monday.
This is a data freshness problem, not a modeling problem.
What AP automation changes for outflows
AP automation captures every approved invoice as it enters the system, applies vendor payment terms automatically, and surfaces the exact due date for each payable. When the AP aging export feeds directly into the forecast model, outflow projections reflect all invoices — including the three that arrived after last week's manual pull.
What AR automation changes for inflows
AR automation tracks invoice status in real time and applies historical collection rates by customer and aging bucket. Instead of projecting inflows from a static aging report pulled on Thursday, the model draws from data that updates as customers pay. At-risk receivables are flagged before they miss their collection window, allowing the AR team to follow up proactively rather than reactively.
4 hrs
Manual weekly forecast update (Source: Centime customer data, 2025)
30 min
With integrated AP and AR automation
The accuracy improvement matters more than the time savings. A 13-week forecast model built on automated, real-time inputs is a decision-making tool. One built on week-old manual exports is a historical artifact with a future date on it. For teams evaluating purpose-built forecasting tools, Centime's cash flow forecasting platform integrates AP, AR, and banking data into a single model that updates automatically. For teams staying with spreadsheets, the ERP export steps in the section above will get you as close to real-time as a manual process allows.
Lender Submission Checklist — before sending the weekly forecast package
Opening balance reconciles to bank statement (not ERP projected balance)
AR inflow projections use collection rates by aging bucket, not gross AR balances
AP outflow projections match AP aging net due dates, not invoice dates
Payroll, debt service, and fixed obligations are in the correct weeks
Variance analysis included: forecast vs. prior week actuals, every line item
Any week projecting below minimum balance threshold is flagged with resolution assumption
Material changes from prior week's forecast are documented in the cover note
Model reviewed and signed off by CFO or Controller before distribution
0 / 8
Forecast cash with confidence
Get a 13-week cash forecast built from your AP and AR.