Revenue waterfall

A revenue waterfall is a report that projects how contracted revenue is expected to be recognized across future periods, laying out how much will be earned in each period based on the service dates in each contract. Rather than showing a single revenue figure, it shows when that revenue is expected to be delivered over time.

Revenue waterfalls matter for subscription businesses because so much of their revenue is deferred at the point of sale and recognized gradually as the service is delivered. A subscription contract billed annually but recognized monthly, for example, has revenue that will be earned across twelve future periods, and a waterfall report shows how much of that revenue is expected to be recognized in each of those periods. A subscription platform such as Recurly can generate this projection from revenue recognition data, giving finance teams a transparent trail from contract to expected revenue rather than a single opaque number.

Why the revenue waterfall matters for subscription businesses

Under standard revenue recognition rules, a subscription business often cannot recognize the full value of a contract the moment it is billed. Revenue is recognized over the period the service is delivered, which means a chunk of every new contract sits in deferred revenue until it is earned. A revenue waterfall makes that future recognition visible, showing how much of the currently contracted revenue is expected to be recognized in each upcoming period based on the service dates.

This visibility matters for accurate financial reporting, for audit readiness, and for forecasting. Without a clear waterfall, it is easy to lose track of how a change in bookings this quarter will show up in recognized revenue several quarters from now. Finance teams also rely on waterfalls to explain revenue movements to auditors and leadership in a way that ties cleanly back to underlying contracts.

How a revenue waterfall works

A revenue waterfall is built from the recognition schedule of each active contract, then aggregated so finance can see expected revenue period by period.

1. Take each active contract and the contracted or deferred amount on it that has not yet been recognized.

2. Spread that amount across future periods according to the service dates and the recognition method for the contract, so each period is assigned the portion of revenue expected to be earned then.

3. Aggregate those per-contract schedules into a single view that shows total expected revenue recognition for each upcoming period.

4. Refresh the projection as contracts change, since new bookings, renewals, modifications, and cancellations all shift how much revenue is expected in future periods.

This is why a waterfall reads as a forward-looking schedule of expected revenue delivery rather than a single balance.

Consider a hypothetical, illustrative example. A business has 120,000 dollars of contracted revenue still to be recognized on an annual subscription that runs from July through the following June, recognized evenly each month. The waterfall spreads that 120,000 dollars across the twelve months of service at 10,000 dollars per month, so the report shows 10,000 dollars of expected recognition in July, another 10,000 in August, and so on until the contract is fully recognized the following June. If a second contract adds 6,000 dollars of expected recognition per month over the same window, the waterfall shows 16,000 dollars of expected recognition in each of those overlapping months.

How to use a revenue waterfall

A revenue waterfall is most useful when it is built into the regular financial close process rather than assembled only when a question comes up.

• Reconcile the revenue actually recognized each period against what the waterfall projected for that period, so any drift is caught early.

• Break the waterfall down by product line or contract type when the business has multiple offerings with different recognition patterns.

• Use the waterfall to forecast future recognized revenue, since the amounts scheduled in later periods represent revenue that is already contracted and simply waiting to be earned.

• Share the waterfall with auditors as supporting evidence for how the recognized revenue figure on the income statement was derived.

• Review adjustments in the waterfall closely, since a pattern of large refunds or contract modifications can signal issues elsewhere in the business.

Benefits and examples

A well maintained revenue waterfall gives a subscription business several concrete advantages:

• A transparent, auditable trail from contracted revenue to the periods in which it is expected to be recognized, which simplifies both internal review and external audit.

• A forward-looking view of revenue already under contract but not yet recognized, which supports more reliable forecasting.

• Early visibility into unusual activity, such as a spike in refunds or contract modifications, that a single revenue total would not reveal.

• A consistent framework for explaining revenue changes to stakeholders who need to understand not just the number but how it got there.

Frequently asked questions

What is a revenue waterfall? A revenue waterfall is a report that projects how contracted revenue is expected to be recognized across future periods, laying out the amount expected to be earned in each period based on the service dates in each contract.

Why do subscription businesses need a revenue waterfall? Because subscription revenue is often billed up front but recognized gradually as service is delivered, a waterfall shows how much of that contracted revenue is expected to be recognized in each future period.

How does a revenue waterfall relate to deferred revenue? Deferred revenue is the balance still to be recognized, and the waterfall is the report that projects how that balance will be recognized as revenue across future periods.

Is a revenue waterfall the same for every subscription business? The underlying projection logic is consistent, but the specific components, such as how contract modifications or multi-year deals are handled, can vary based on the business's contract structures and its revenue recognition policies.

Who typically uses a revenue waterfall? Finance and accounting teams build and review revenue waterfalls as part of the close process, and auditors rely on them to verify that recognized revenue is properly supported by underlying contract activity.