A monthly recurring revenue waterfall explains how opening MRR becomes closing MRR through movements such as new, expansion, reactivation, contraction, and churn. Stripe and subscription analytics systems document recurring-revenue concepts, but exact classifications can vary by system settings and business model. The useful practice is to define the movements, preserve customer-level evidence, and make the waterfall reconcile.

VISUAL LESSON

What you will learn

  1. 01Define MRR and movement categories.
  2. 02Build a customer-level movement ledger.
  3. 03Reconcile the monthly waterfall.
Recurring revenue rises through new and expansion blocks and falls through contraction and churn into closing MRR
A reconciled MRR waterfall makes every recurring-revenue movement visible between two period-end balances.

ILLUSTRATIVE WORKED EXAMPLE

Reconcile an illustrative monthly MRR waterfall

Opening MRRPrior period close
$78k
New + expansion + reactivationPositive movements
+$18k
Contraction + churnNegative movements
−$9k
Closing MRRMust reconcile
$87k
Illustrative example—not a benchmark. Replace the sample values with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Move from subscription events to a reconciled waterfall

Define01Freeze recurring-revenue rules

Document included products, recurring amount, discounts, currency, taxes, annual plans, pauses, credits, and period boundary.

Classify02Build customer-level movements

Compare opening and closing MRR, then assign new, expansion, reactivation, contraction, churn, or data adjustment.

Reconcile03Bridge opening to closing

Sum movements, resolve residuals, review system settings, and publish both value and customer counts.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Opening MRR + gains − losses ± adjustments = closing MRR

OpenPrior recurring balance
MoveCustomer-level changes
CloseReconciled balance

THE LEAD ATLAS METHOD

Lead Atlas Data can research business contacts for the growth campaign's exact market, categories, and locations; cohorting those outreach batches keeps any new recurring revenue traceable to the right acquisition work.See how custom list research works ↗
01

Freeze the MRR definition

Document which recurring products and statuses count, how annual or multi-period contracts are normalized, when trials enter, how discounts, coupons, taxes, usage, credits, refunds, pauses, delinquency, cancellations, and one-time charges are treated, and which time zone closes the month.

State the currency and conversion policy. MRR is an analytical recurring-revenue measure, not cash collected, invoice value, booked contract value, or generally accepted accounting revenue. Keep those reports separate and reconciled through their own rules.

02

Create opening and closing snapshots

Take customer- or subscription-level MRR snapshots at consistent period boundaries using stable identifiers. Preserve source records, plan, quantity, unit amount, discount, currency, status, and effective timestamps. Rebuildable snapshots are safer than an overwritten current-state table.

Check that the prior month's closing MRR equals the current month's opening MRR under the same definition. If not, isolate backfills, currency changes, migrations, and rule changes as explicit adjustments.

03

Classify each movement once

New MRR begins from a customer with no prior recurring MRR under the definition. Expansion increases an active customer's MRR; contraction decreases it without reaching zero; churn reduces it to zero; reactivation returns a previously churned customer. System-specific treatment can differ, so align labels to documented settings.

Build a movement ledger with customer, subscription, event time, opening MRR, closing MRR, delta, class, source event, reason, and rule version. Prevent the same delta from appearing in two movement categories.

04

Reconcile the waterfall

Calculate opening MRR plus new, expansion, and reactivation, minus contraction and churn, plus or minus explicit data adjustments, to closing MRR. Review both value and customer counts. Investigate every residual rather than hiding it in an other category.

Create a customer-level bridge and a summarized chart. Test upgrades and downgrades, cancellation and same-month restart, plan migration, quantity changes, discount start and end, paused accounts, backdated events, negative invoices, and currency movement.

05

Use movements for diagnosis

Segment movements by acquisition cohort, product, plan, market, customer size, owner, and reason only when the definitions and sample sizes support the decision. Expansion cannot automatically offset a concentrated churn problem, and positive MRR does not by itself prove healthy cash or retention.

Deliverable: MRR policy and rule version, period snapshots, movement-class definitions, customer ledger, opening-to-closing formula, residual report, exception test cases, currency and adjustment log, value-and-count waterfall, segment diagnosis, and a documented growth, retention, pricing, data, or billing action.

THE TAKEAWAY

Freeze the MRR definition, classify each customer movement consistently, reconcile opening plus movements to closing, and explain timing, currency, discounts, pauses, and data adjustments.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.