---
title: How to forecast deferred revenue release for 12 months
description: Build a 12-month deferred revenue release forecast from your existing schedule, add renewals and new bookings, and use it in cash and revenue planning.
canonical: https://www.scalexp.com/blog/deferred-revenue-release-forecast/
---
# How to forecast deferred revenue release for the next 12 months

Build a 12-month deferred revenue release forecast from your existing schedule, add renewals and new bookings, and use it in cash and revenue planning.

Key takeaways

- The existing deferred revenue schedule already tells you how much of today's balance will be recognized in each of the next 12 months.
- Expected renewals and new bookings add a second and third layer, each released over its own service period.
- Separating contracted release from expected release shows how much of the revenue forecast depends on future sales.
- Billings drive cash and release drives revenue, so the same contracts produce two different monthly profiles.
- The forecast is only as good as the schedule behind it, so reconcile the schedule to the ledger before forecasting from it.

**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.

## What a deferred revenue release forecast shows

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:

- **Contracted release.** The remaining deferred revenue balance today, released over the remaining service periods.
- **Expected renewals.** Contracts due to renew in the next 12 months, multiplied by the expected renewal rate, released from each renewal date.
- **Expected new bookings.** New contracts the sales plan expects, released from their expected start dates.

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.

## Building the waterfall from the existing schedule

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.

1. Start from the schedule at the latest month-end, and confirm that its total agrees to deferred revenue in the general ledger.
2. For each contract, list the release in each remaining month of its service period.
3. Sum the releases by month for the next 12 months, and separately for anything beyond 12 months.
4. Check that the 12-month total plus the later amounts equals today's balance.

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](https://www.scalexp.com/blog/deferred-revenue-reconciliation-why-it-breaks-and-how-to-fix-it/) covers the usual causes.

## Adding expected renewals and new bookings

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.

## An illustrative 12-month release waterfall

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.

## Using the forecast in cash and revenue planning

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](https://www.ifrs.org/issued-standards/list-of-standards/ifrs-15-revenue-from-contracts-with-customers/) 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:

- **Revenue plan:** total forecast release, plus monthly-billed revenue.
- **Billings plan:** renewal and new booking invoices by month, at full contract value.
- **Cash plan:** the billings plan shifted by expected collection timing.
- **Deferred revenue balance:** opening balance plus billings less release, month by month.

Our article on [cash versus accrual accounting](https://www.scalexp.com/blog/cash-vs-accrual-accounting/) explains why the two views differ.

## Common mistakes when forecasting deferred revenue release

- **Forecasting from an unreconciled schedule.** If the schedule does not agree to the ledger, the contracted layer is wrong from the first month.
- **Blending contracted and expected revenue.** One total hides how much of the forecast depends on assumptions.
- **Releasing renewals from the invoice date.** Renewal invoices raised before the term starts should release from the start of the new term.
- **Ignoring billing frequency in new bookings.** A pipeline of monthly-billed deals adds revenue but little deferred revenue.
- **Leaving out cancellations and contraction.** Expected churn and downgrades reduce the renewal layer and should be explicit.

## How ScaleXP supports deferred revenue release forecasting

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](https://www.scalexp.com/deferred-revenue/) 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](https://www.scalexp.com/revenue-forecast/).

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.

![ScaleXP forecast: invoiced revenue running off and new sales in progress, October to December 2026](https://www.scalexp.com/wp-content/uploads/2026/10/scalexp-forecast-invoiced-runoff-and-new-sales-demo.webp)

## Conclusion

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.

## Frequently asked questions

### How do you forecast deferred revenue?

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.

### What is a deferred revenue waterfall?

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.

### Why does cash differ from revenue for annual SaaS contracts?

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.

### Should expected renewals be included in a deferred revenue forecast?

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.

### How often should a deferred revenue release forecast be updated?

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](https://www.ifrs.org/issued-standards/list-of-standards/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](https://www.scalexp.com/deferred-revenue/)
