13-week rolling cash forecast template for RevOps teams

TL;DR: Cash surprises start when bookings, billing, collections, and outflows run on separate operating rhythms. A 13-week rolling cash forecast gives finance and RevOps a weekly view they can defend through reconciliation and stress testing. The model works best when teams connect every cash receipt assumption back to current bookings data.

For finance and revenue operations leaders, cash surprises happen when the board asks about runway and the forecast cannot trace its largest inflow line back to current bookings data. A credible 13-week cash flow forecast connects weekly inflows and outflows with one quarter of visibility, tied to that bookings data. That is the difference between a number finance can defend and a guess dressed up as a model.

The gap shows up fastest at the board level. The forecast gives the board a cash view finance owns, but its largest line depends on the sales pipeline, the CRM, and the billing tool, systems finance does not control. When teams contest the bookings number behind that line, they contest every week of the model.

Finance and revenue operations need a shared structure for the upstream data they both own before the forecast can withstand scrutiny.

What is a 13-week rolling cash forecast?

A 13-week rolling cash forecast is a weekly view of expected inflows and outflows that teams use for liquidity planning and covenant monitoring. Scenario analysis runs on the same weekly cadence.

On a weekly update cycle, when a week closes, it becomes actuals, the remaining weeks shift forward, and the team adds a new week 13. Thirteen weeks is one quarter out: far enough to see a covenant problem coming, close enough to stay concrete.

In B2B, close dates move, and billing triggers or collections timing can vary. A cash forecast that assumes stable invoicing and predictable collections can miss the connection between deal timing and cash timing. Finance owns the model, but its largest inflow line depends on a pipeline finance does not control.

The benefits of a defensible 13-week cash forecast

None of these benefits show up in a spreadsheet only finance touches. They depend on the RevOps data feeding it. Here are 5 benefits:

A liquidity problem shows up weeks before it becomes a covenant breach

A weekly cash view reveals a widening gap between projected and actual collections, while there is still time to act: renegotiate terms, delay discretionary spending, or draw on a credit line. The alternative is finding out at the board meeting that follows the miss.

Three competing cash numbers become one defensible one

When sales, RevOps, and finance each defend a different pipeline number, every planning conversation starts with an argument about whose number is right. One bookings source ends that argument before the meeting starts.

Collections slippage surfaces while there is still time to act

Collections curves built from actual DSO surface a slowing payer or stalled invoice in week three, not at quarter-end close, when the only options left are write-offs and hard conversations.

Hiring and spending decisions run on cash timing, not booked revenue

A booked deal and a collected dollar are not the same thing. Tying discretionary spend and hiring pace to the cash model, not the bookings number, keeps growth decisions funded by money the company has, not money it expects.

Finance and revenue operations get a shared stake in the same number

Once both teams build from the same bookings input and the same collections logic, the weekly forecast review becomes a conversation about what changed, not a negotiation over whose data to trust.

Why the cash forecast breaks down without RevOps data

Each failure below starts upstream, in pipeline and CRM data finance inherits but does not maintain.

The forecast assumes collections land on time, and they usually do not

An AR-driven inflow line assumes deals close on the CRM close date, invoice immediately, and pay on terms. Collection cycles have stretched since 2021, so cash lands later than terms promise and finance falls back on haircuts nobody can trace.

Nobody agrees on which pipeline number is the real one

Finance builds off one version of expected bookings, while revenue operations and sales may each use a different view. This is the three-clock problem: the CRM snapshot no longer matches the sales forecast or the board deck, and all three can technically be correct. The cash model inherits whichever number finance pulled.

A cash forecast built on stale pipeline data breaks the moment a deal moves

Most sales organizations miss their forecast by a material margin, and every slip carries a cash consequence: a pushed deal delays the invoice, a re-scope changes the amount. The bookings forecast is corrected; the cash model is not, because nobody tells finance that the invoice assumption has changed.

When trust breaks down, the forecast becomes a political document

Finance teams discount the forecasts they get from the revenue side, often without documenting the haircut. The revenue side pads in response, and reps who watch leadership override their inputs stop maintaining CRM fields. The data gets worse and the next override gets bigger.

How to build the 13-week rolling cash forecast

Each step below closes one of the failures described above, and skipping ahead before the bookings data is standardized just reintroduces the same problem. Follow these steps:

Step 1: Standardize the bookings forecast feeding the model

Before any cash math, get opportunity data to mean the same thing everywhere: consistent stages and forecast categories, with close dates and amounts governed the same way. One team treats a commit as 90 percent confidence, and another treats it as optimism, producing an invoice schedule that swings for no business reason.

That consistency has to be enforced somewhere every team is required to touch. Forecast and Plan, from Outreach, the only agentic AI platform for revenue teams, closes that gap. It gives finance one governed set of stages, forecast categories, and close dates that every team works from, rather than a spreadsheet roll-up where each team defines those fields on its own.

Step 2: Map bookings into an invoice schedule

Map every opportunity in the bookings forecast:

Where go-live gates billing, add a service delivery lag so the model counts only cash the company can invoice.

Step 3: Layer collections behavior on top of invoices

An invoice date and a receipt date differ, so build collections curves by segment or payment terms. Each curve uses historical payment behavior to record the percent of invoice value collected in week one, week two, and later weeks. Segment curves where historical payment behavior differs materially, rather than forcing every customer type into one curve.

A single blended curve applied to a 30-day enterprise payer and a 90-day mid-market segment overstates early-week cash for one group and understates it for the other. That gap compounds every week the curve stays unsegmented.

Step 4: Model fixed and semi-fixed outflows

These outflows are predictable and the easiest part of the model to get right, which is exactly why they get missed. Payroll, rent, taxes, and core vendor payments map to exact dates.

The schedule should include three-paycheck months and bonus runs; a company that misses the extra paycheck in one of those months can show a healthy 13-week balance right up until the week it is not. Employer taxes, employee-related payments, insurance premiums, and scheduled debt service dates go in the same way.

Step 5: Model variable and discretionary outflows

Commission costs move with the business, as do variable marketing and contractor spend. The commission line is easy to misplace. If a rep earns quota credit at booking but company policy makes payout contingent on invoice payment, the commission line follows that payout trigger, not the booking date.

Get this wrong and commission expense lands in the wrong week, understating cash exactly when the payout clears. Tie discretionary spend to cash headroom: when projected cash dips below a defined threshold, teams trim these lines first, by a rule they agreed to in advance.

Step 6: Roll the forecast forward weekly and reconcile actuals against projections

Every week, replace the oldest week with a new week 13 and reconcile what happened against what the team projected. Use variance analysis based on materiality, and attach a root cause and an owner to every breach. A collections variance traces to AR, a bookings variance traces to the sales forecast, and an outflow variance traces to whichever budget owner missed the date.

Without that routing, the same team absorbs the blame for every miss, regardless of where it started, and reconciliation discipline breaks down rather than sharpening the assumptions.

How to run base, conservative, and downside scenarios without breaking trust

Scenarios let the model intentionally absorb disagreement about the future before it surfaces as an unagreed override.

Agree on your three cases before a bad week forces the question

Agree on three cases up front: base, conservative, and downside. The base case carries the current collection and bookings assumptions unchanged. Many planning models use an upside case. For a cash model, put a conservative case where the upside would normally sit, since the operative question is how little cash arrives.

Conservative lowers collection rates and raises the slip rate on later-week deals. Downside stress-tests key deals falling out of the window and collections stretching further. Another week or two of delay materially changes the liquidity picture.

Keep every override visible

Put manual adjustments to bookings or collections assumptions in a separate scenario tab, separate from the base inputs. Document each with the metric affected, period, amount, rationale, and an expiration rule. A visible override layer keeps the base case as shared ground.

Review the conservative and downside cases together every week

Finance and RevOps should review the base, conservative, and downside cases together every week. A base case that holds steady while the downside deteriorates means an assumption is drifting.

Best practices for keeping the forecast reliable

Operating habits keep the model from decaying a month after teams build it.

Give finance and revenue operations one shared weekly forecast cut

Start with a weekly freeze: on Monday the revenue side publishes an updated 13-week bookings view that finance builds on. Same day and same time every week means both teams argue about one snapshot instead of three. One workable convention: let genuinely new deals land after the freeze, and hold off on reclassifications until the next cut.

Split ownership clearly

The revenue side owns the bookings forecast, opportunity hygiene, contract-type tagging in the CRM, and the deal-to-billing mapping rules. Finance owns the collection assumptions and outflows, as well as the cash model logic. Both share the scenario definitions and the board narrative, so neither can later claim the assumptions were the other team's problem.

Reconcile weekly, recalibrate quarterly

Weekly reconciliation covers actuals versus projections; quarterly recalibration covers DSO by segment, collection curves and mapping rules. Recalibrate off-cycle when collections repeatedly drift from the model's steady-state inflow.

According to the Outreach Insights Group's 2026 Agent Productivity Impact Report, AI-assisted workflows reclaim 7-8 hours per month otherwise spent on CRM upkeep, time better spent chasing reconciliation gaps.

Keep the model simple enough that people maintain it

A model that is too complicated to update every week stops being useful; one that lands close and refreshes quickly beats one that needs constant repair.

Build a cash forecast both sides can stand behind

A defensible 13-week rolling cash forecast still depends on revenue data finance and RevOps both trust. That trust holds only as long as the CRM fields, forecast categories, and deal changes feeding it stay current between reconciliation cycles.

Getting there is harder when that data lives in separate tools that nobody has full visibility into, and easier when the systems generating bookings, deal changes, and pipeline signals share a single source of truth.

Outreach, the only agentic AI platform for revenue teams, is a concrete example. Finance still owns the cash model, including collection curves, outflows, and covenant math, while RevOps owns the bookings input that feeds it, and neither side can defend the number on its own.

Frequently asked questions about 13-week rolling cash forecasts

What is a 13-week rolling cash flow forecast used for?

Its core jobs are liquidity planning and covenant monitoring, with scenario analysis on the same weekly cadence. It also earns its keep outside distress: the weekly view surfaces working-capital pressure that a monthly P&L smooths over, like a segment drifting past terms or a slipping go-live trigger. Without it, a cash crisis can build unnoticed.

How is a 13-week cash forecast different from a revenue or bookings forecast?

A bookings forecast predicts contract signatures; a cash forecast predicts bank deposits, and the gap can be enormous. For example, a customer might sign a three-year $360,000 deal in March, book the full amount immediately, but invoice only $120,000 in April. Deferred revenue bridges the two, and an unexpected move in that balance usually signals a billing error rather than a forecasting error.

How often should a 13-week cash forecast be updated?

Weekly, ideally on the same day, replacing the prior week's projections with actuals. A common cadence: treasury closes actuals, FP&A rebuilds the forecast, leadership reviews, then payments release. Keep the weekly package light, since the goal is a decision, not a report. Accuracy expectations tighten toward week one; weeks nine through thirteen can tolerate wider bands.

What data goes into a 13-week cash flow forecast template?

Opening bank balances from bank statements, reconciled to the penny. An AR aging report, aged from the due date, plus the AP schedule, payroll calendar, and debt and tax schedules. Add the weekly bookings cut, amount, close date, and forecast category, built on the same bottom-up forecasting logic used for revenue projections. Behavioral inputs matter too: historical payment behavior by segment, plus billing terms by contract type.

Why do 13-week cash forecasts often turn out to be wrong?

Unreliable pipeline inputs are the most common reason: the error shows up in cash numbers before anyone names it. Miscalibrated probability weighting compounds the problem, since many forecast deals never close, and close-date drift moves the invoice along with the deal. Assuming every invoice is paid in full on the day it is issued adds another layer of error.