See how ScaleXP works with Xero or QuickBooks.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.
Key takeaways
Short answer: To forecast deferred revenue release for the next 12 months, start with the existing deferred revenue schedule and list how much of today's balance will be recognized in each future month. Then add the release from expected renewals and new bookings, each spread over its service period from the month it starts. The result is a release waterfall that shows how much forecast revenue is already contracted and how much still depends on future sales.
For a SaaS company that bills annually or quarterly in advance, this waterfall is one of the most reliable inputs to the revenue forecast, because a large part of next year's revenue is already on the balance sheet. It also explains why cash and revenue move on different timelines.
A release forecast shows, month by month, how much revenue will be recognized from amounts that have been billed or will be billed in advance. It answers a question that a pipeline report alone cannot: how much of next year's revenue is already contracted and invoiced.
The forecast is built in layers:
Revenue from contracts billed monthly in arrears, or monthly in the same month as the service, passes through deferred revenue briefly or not at all. It belongs in the wider revenue forecast but not in the release waterfall.
The first layer comes straight from the deferred revenue schedule. For each customer contract, the schedule holds the contract value, the service period and the amount released to date. The remaining balance is released over the months left in the service period.
The last step is a useful control: if the layers do not add back to the balance, a contract is missing service dates or has been released over the wrong period. If the schedule has not been reconciled recently, our guide on why deferred revenue reconciliation breaks covers the usual causes.
The second and third layers are estimates, so they should be shown separately from contracted release rather than blended into it.
Renewals. List the contracts with a renewal date in the next 12 months. Apply an expected renewal rate, ideally by customer segment or contract size rather than a single company-wide figure, and include expected price changes or expansion. Each renewed contract starts releasing from its renewal date over its new term.
New bookings. Take expected new contracts from the sales plan or the CRM pipeline, by expected start month, billing frequency and term. Only the portion billed in advance flows through deferred revenue; monthly-billed contracts go straight to the revenue forecast.
Keep the assumptions visible: renewal rate, expected start dates and average contract term. When the forecast is reviewed, these are the numbers that change, while the contracted layer moves only as time passes and new invoices are raised.
Illustrative example: a SaaS company has deferred revenue of $2,400,000 at December 31, 2026, mostly from annual contracts billed in advance. The table below shows its release forecast for 2027 by quarter, split into the three layers.
| Layer | Q1 2027 | Q2 2027 | Q3 2027 | Q4 2027 |
|---|---|---|---|---|
| Release of existing balance | $1,100,000 | $700,000 | $400,000 | $200,000 |
| Release from expected renewals | $150,000 | $350,000 | $550,000 | $700,000 |
| Release from expected new bookings | $50,000 | $150,000 | $250,000 | $350,000 |
| Total forecast release | $1,300,000 | $1,200,000 | $1,200,000 | $1,250,000 |
Source: illustrative figures prepared for this article, not outside data.
Two points stand out. First, the existing balance covers most of Q1 and falls away through the year, which is the normal shape for annual contracts. Second, by Q4 more than 80% of forecast release depends on renewals and new bookings, so the renewal assumption is the one the board should challenge most.
The same contracts produce two different monthly profiles. Billings, and the cash collected from them, arrive when invoices are raised and paid. Revenue arrives as service is delivered, under ASC 606 in the US or IFRS 15 internationally.
In the example above, renewals billed annually in advance bring cash in the quarter they are invoiced, but their revenue is spread over the following twelve months. A company with renewals concentrated in one quarter will see a cash peak in that quarter while revenue stays relatively level. Planning that uses only the revenue line will understate cash in renewal-heavy months and overstate it in the others.
A combined view is straightforward to build from the waterfall:
Our article on cash versus accrual accounting explains why the two views differ.
ScaleXP builds month-by-month deferred revenue schedules from invoices in Xero or QuickBooks, by customer, product and contract, with service dates from the invoice or from CRM data in HubSpot, Salesforce or Pipedrive. Opening, movement and closing balances reconcile to the journals in the ledger, which gives the contracted layer of the waterfall a reconciled starting point. ScaleXP prepares the deferred revenue journals, and they are posted once finance approves them. See how the deferred revenue schedules are built.
For the forward-looking layers, ScaleXP brings pipeline, renewals, billing schedules and actuals from CRM and accounting data into one forecasting workflow, and forecast revenue can be compared with accounting actuals. Read more about building a revenue forecast from CRM and ledger data.
In the ScaleXP demo company below, the forecast shows revenue from invoices already raised falling from $854,689 in October 2026 to $722,890 in December, with new sales in progress adding $20,554 a month.
A deferred revenue release forecast starts with the existing schedule, reconciled to the ledger, and adds expected renewals and new bookings as separate layers. Keeping the layers separate shows how much of next year's revenue is already contracted, and setting billings beside release explains the gap between the cash plan and the revenue plan.
Start with the closing deferred revenue balance and the customer-level schedule behind it. Release each contract's remaining balance over the months left in its service period. Then add forecast billings for renewals and new bookings and release each over its own term. The forecast closing balance each month is the opening balance plus billings less revenue released.
A deferred revenue waterfall is a table that shows, for each future month or quarter, how much revenue will be recognized from amounts billed in advance. It is usually split into layers: release of the existing balance, release from expected renewals and release from expected new bookings. The layers show how much forecast revenue is contracted and how much depends on future sales.
Cash arrives when an annual invoice is paid, usually near the start of the contract, while revenue is recognized evenly as the service is delivered over the year. The unearned part sits in deferred revenue in the meantime. A company with renewals concentrated in a few months will therefore see cash peaks in those months while revenue stays relatively level.
Yes, but as a separate layer from the existing balance. Renewals are an estimate, so apply an expected renewal rate, ideally by customer segment, and release each renewed contract from its new start date over its new term. Showing renewals separately lets the board see how much of the forecast depends on that assumption.
A monthly update after the close is a practical cadence, once the deferred revenue schedule has been reconciled to the ledger. The contracted layer rolls forward as time passes and new invoices are raised, while the renewal and new booking assumptions are reviewed against the latest CRM data. A quarterly review of the renewal rate assumption is a useful minimum.
Sources (checked October 2026): IFRS Foundation, IFRS 15 Revenue from Contracts with Customers.
How ScaleXP does this
ScaleXP calculates deferred revenue from your invoices and contracts and keeps the balance sheet reconciled every month. See ScaleXP’s deferred revenue automation →
Close-time estimator
Your accounting system
How long does your close take today? Working days, roughly
Which of these do you still do manually? Select all that apply
Which of these takes the most time? Pick one
Your estimate
Your 3–5 day Xero or QuickBooks close could be closer to 2.5 days
Deferred revenue is where you would feel it first. ScaleXP prepares the schedules and journals for each task you selected from your live Xero or QuickBooks data. What stays with your team is the review and the posting decision.
Cue Technology saves 3–5 finance-team days a month. Xero customer
““Making the month-end revenue recognition process simplified.”
Revenue recognition
See how ScaleXP builds revenue schedules and journals from your invoice data.
In a 15- or 30-minute demo, we’ll show the relevant workflows using example data and discuss how they could apply to your finance process. Complex requirements? Discuss them with us first.