Optimized Sales Optimized Marketing Target Accounts For CROs For CFOs For CMOs Blog News Glossary Compare Tools About Schedule a Demo
Revenue Operations

How to Build an ARR Waterfall That Reconciles Every Month

Pete Furseth 6 min read
ARR waterfallARR bridgerevenue metricsrevenue operationssaas metricssales operations metrics
How to Build an ARR Waterfall That Reconciles Every Month
Home/ Blog/ How to Build an ARR Waterfall That Reconciles Every Month

An ARR waterfall turns a pile of contract changes into an auditable explanation of why revenue moved. Beginning ARR, every categorized movement, ending ARR, and the requirement that they tie exactly. Companies that run this monthly can defend every retention number they report. Companies that do not are estimating. This guide covers the structure, the classification rules, and the edge cases that break the tie-out.

What lines belong in an ARR waterfall?

Eight lines: beginning ARR, three loss categories, three gain categories, and ending ARR.

ORM structures gross and net retention on exactly this schedule, run by month:

LineDirectionDefinition
Beginning ARRBasePrior month's ending ARR, always
Churned customer ARRContractionAccount cancelled entirely
Churned product ARRContractionAccount retained, one product dropped
Product decrease ARRContractionAccount retained, quantity or tier reduced
New customer ARRExpansionLogo acquired this month
New product ARRExpansionExisting account added a product
Increased product ARRExpansionExisting account added seats or upgraded tier
Ending ARRResultSum of the above
The critical rule sits in the first line. Beginning ARR equals the prior month's ending ARR with no exceptions and no restatements. The moment you allow beginning ARR to be recalculated from the contract table, the series stops being a reconciliation and becomes twelve unconnected snapshots.

The split between churned customer, churned product, and product decrease is what makes the schedule diagnostic. Three very different failures produce three different lines, and each one points at a different owner.

Put this to work on your numbers
Run your own numbers with the free Sales Capacity Planner, then see how ORM builds it into a custom model.

How do you classify each movement?

Classify by what changed for the account, and apply the rule the same way every month.

Work through the decision in order:

1. Did the account cancel entirely? Churned customer ARR. The full contracted ARR moves out. 2. Did the account drop a product but keep others? Churned product ARR, valued at the dropped product's ARR. 3. Did the account reduce quantity or tier on a product it kept? Product decrease ARR, valued at the reduction only. 4. Was this the account's first contract? New customer ARR, at full contracted value. 5. Did an existing account add a product it did not have? New product ARR. 6. Did an existing account increase quantity or tier on an existing product? Increased product ARR.

A worked month, starting at $8,400,000:

LineAmountRunning total
Beginning ARR$8,400,000$8,400,000
Churned customer ARR($96,000)$8,304,000
Churned product ARR($28,000)$8,276,000
Product decrease ARR($41,000)$8,235,000
New product ARR$54,000$8,289,000
Increased product ARR$103,000$8,392,000
New customer ARR$265,000$8,657,000
Ending ARR$8,657,000
Gross revenue retention for the month is $8,235,000 over $8,400,000, or 98.0 percent. Net revenue retention is $8,392,000 over $8,400,000, or 99.9 percent. Ending ARR grew 3.1 percent on the strength of new logos while the existing base shrank. The waterfall is the only view that shows all three facts at once.

Which edge cases break the tie-out?

Backdated amendments, one-time fees, and mid-month changes, in that order of frequency.
Edge caseHandling rule
Contract amended after the month closedPost the change in the current month, never restate a closed period
Implementation or services feesExclude from ARR entirely, they are not recurring
Mid-month start or cancellationRecognize the full ARR change in the month it takes effect
Upgrade and downgrade on the same productNet within the product, record the single resulting movement
Product swapTwo lines, churned product ARR and new product ARR
Renewal at a higher rateIncreased product ARR, not new customer ARR
Signed contract with a future start dateBacklog, enters ARR when the service period begins
Ramped multi-year contractStep up in the month the new rate takes effect
Never use a plug line. A balancing entry hides one misclassification in month one and eleven by December, and every retention rate derived from that series inherits the error.

Why does the waterfall matter more than the retention rates it produces?

Because the rates are outputs and the classification is the actual work.

Gross and net retention are two divisions performed on the waterfall. If the categories are right, both rates are right and comparable across every period. If the categories are inconsistent, the rates are precise numbers built on shifting definitions, which is more dangerous than no number at all because it invites confident decisions.

Consistency also beats perfection in the underlying data. Most revenue teams believe their CRM data is uniquely bad and that this prevents accurate measurement. It rarely does. As long as the classification is applied consistently, imperfect records still support accurate prediction. What breaks prediction is changing the rules between periods.

How does the waterfall feed forecasting?

It gives you three separate empirical rates instead of one growth assumption.

Once you have twelve or more months of clean waterfall, you can model churn, contraction, and expansion as independent series with their own seasonality rather than as a single net retention percentage. That matters because they behave differently. Contraction lands mid-term without a renewal trigger. Cancellation clusters at renewal dates. Expansion follows product adoption curves.

Seasonality shows up in all three. Q2 and Q4 typically run stronger than Q1 and Q3, and the third month of a quarter runs stronger than the first two. A model that assumes flat monthly movement will consistently miss the shape of the year even when the annual total is close.

For how the retention side joins new business in a single number, see how to forecast revenue and net revenue retention. For the discipline that keeps the forecast itself honest, see forecast accuracy.

Frequently Asked Questions

What is an ARR waterfall?

An ARR waterfall, sometimes called an ARR bridge, is a monthly schedule that starts with beginning ARR, lists every categorized movement in and out, and ends with ending ARR. Its purpose is reconciliation: if the movements do not tie beginning to ending exactly, something is misclassified or missing.

What lines belong in an ARR waterfall?

Beginning ARR, churned customer ARR, churned product ARR, product decrease ARR, new customer ARR, new product ARR, increased product ARR, and ending ARR. That structure separates full account loss from partial loss and separates new logos from cross-sell and upsell, which is the level of detail retention analysis requires.

How do you classify a customer who upgrades and downgrades in the same month?

Net the movements within the same product, and record them separately across different products. A customer who adds 40 seats of product A and drops 15 seats of product A is one increase of 25 seats. A customer who adds product B and drops product A records both a new product ARR line and a churned product ARR line.

Should the waterfall be built monthly or quarterly?

Monthly. A quarterly bridge hides offsetting movements inside the quarter, so a month of heavy contraction covered by a month of heavy expansion looks like a quiet quarter. Monthly resolution is also what makes mid-term contraction visible before a renewal conversation.

What does it mean when the waterfall does not tie out?

It means a movement is uncategorized, double counted, or a contract change was backdated after the prior close. The most common causes are contracts amended retroactively and one-time fees mixed into recurring revenue. Do not force the balance with a plug line, since the plug will grow every month and take the retention metrics with it.

PF
Pete Furseth
ORM Technologies
Pete has built custom revenue forecast models for B2B SaaS companies for over a decade.

See how ORM turns these insights into action

ORM builds custom revenue forecast models for B2B SaaS companies. Not dashboards. Prescriptive analytics that tell you what to do next.

Schedule a Demo