Subscription metrics case study

Subscription Metrics (ARR/MRR/NRR) GL Reconciliation Case Study

A $75M ARR SaaS company's board pack consistently showed ARR numbers different from the audited revenue line. We reconciled subscription metrics (ARR, MRR, NRR, gross retention, churn) to GL revenue with documented bridge logic — making operating reporting and financial reporting tell the same story.

Client profile: Composite case study based on a $75M ARR vertical SaaS company with subscription + usage revenue mix, NetSuite GL, Salesforce CRM with custom MRR fields, RevOps team owning operating metrics. Annual external audit; investor-driven board cadence.

See measured results Talk through your situation

Company context Before — what was actually broken What Ledger Summit implemented Subscription metric mechanics — the canonical bridges Implementation timeline Measured results

Company context

The client is a $75M ARR vertical SaaS company. The RevOps team produced ARR/MRR/NRR/churn metrics from Salesforce monthly. Accounting produced revenue from NetSuite per ASC 606. Board packs showed both. The numbers disagreed — typically by $1–3M annually. Investors noticed; board pack credibility eroded; CFO needed alignment.

The disagreement wasn't one issue but five: (1) ARR included committed-but-not-yet-started contracts; (2) revenue excluded non-recurring services; (3) discount treatment differed between operating and accounting; (4) modification effective dates differed; (5) churn timing differed.

$75M ARR SaaS, mostly subscription with usage component
Salesforce CRM with custom MRR fields
NetSuite GL with ASC 606 revenue recognition
RevOps team produces ARR / NRR metrics
Annual external audit
Board pack with both operating and audited numbers — $1–3M annual disagreement

Before — what was actually broken

Two parallel metric pipelines: RevOps produced operating metrics from Salesforce; Accounting produced revenue from NetSuite. No reconciliation. No documented bridge. Investors raised the gap as a credibility issue.

No documented bridge between ARR and revenue
ARR included not-yet-started contracts
Revenue excluded services (treated separately)
Discount methodology differed (gross vs. net)
Modification timing inconsistent
Board pack disagreement of $1–3M annually

What Ledger Summit implemented

A documented bridge between subscription metrics and GL revenue, with monthly reconciliation, methodology documentation, and unified reporting framework.

ARR definition: contracted MRR × 12 for active subscriptions only (not pending starts)
MRR definition: aligned to billing entity for subscription contracts
NRR (Net Revenue Retention): cohort-based with documented logic
Gross retention: separate from NRR, documented exclusions (e.g., logo churn vs. expansion)
Churn: dollar churn per period, with timing aligned to ASC 606 recognition
Bridge from ARR to revenue: ARR × (months elapsed / 12) + non-recurring + usage − deferred revenue impact
Monthly reconciliation report: ARR ↔ MRR ↔ recognized revenue ↔ deferred revenue
Documented methodology for board pack
Disclosure consistency: same metrics in board pack and audited disclosures
Investor / auditor walkthrough script

Subscription metric mechanics — the canonical bridges

Metric	Definition	Reconciliation to revenue
ARR	Contracted MRR × 12 for active subs	ARR is annualized run-rate, not recognized revenue. Bridge through recognition methodology.
MRR	Recurring monthly revenue in current month	MRR for active customers; aligns to invoice cycle
NRR	Cohort revenue this year ÷ cohort revenue last year	Includes expansion, contraction, churn within same cohort
Gross retention	Cohort revenue this year (excluding expansion) ÷ cohort revenue last year	Pure churn measure
Logo retention	Active customers this year ÷ active customers last year	Customer count metric
Dollar churn	Lost ARR / starting ARR	Inverse of gross retention
Recognized revenue	GAAP revenue per ASC 606	Bridge from ARR via recognition pattern
Bookings	Total contract value signed	Future revenue commitment, not current
Billings	Invoiced amount	Often ≠ recognized revenue (deferred)
Deferred revenue	Billed not earned	Balance sheet liability; works backward to ARR

Implementation timeline

Weeks 1–2: Discovery: definition audit; identify all 5 disagreements; quantify each
Weeks 3–4: Build: bridge engine pulling from Salesforce + NetSuite; reconciliation logic
Weeks 5: Calibrate: 12 months of historical bridge; identify and document remaining differences
Weeks 6: Documented methodology with worked examples; auditor concurrence on bridge
Week 7: Cutover: first month with reconciliation; board pack alignment
Week 8: Hypercare and reconciliation discipline operationalized

Measured results

Metric	Before	After	Delta
Board pack ARR vs. revenue disagreement	$1–3M / yr	$0	−100%
Documented methodology	None	Per-metric	—
Investor confidence	Eroded	Restored	—
Reconciliation lag	Annually at audit	Monthly	—
Disclosure consistency	Inconsistent	Aligned	—
Audit walkthrough — operating metrics	None	Documented	—

Alternatives considered

Option	Time	Cost band	Strengths	Weaknesses
ChartMogul	3 months	$120K–$180K / yr	Subscription metrics platform	Doesn't fix GL bridge
Mosaic	3–4 months	$180K–$280K / yr	FP&A platform with subscription	Over-scoped
Calibrate (subscription analytics)	3 months	$80K–$140K / yr	Modern	Newer
Build on existing stack (selected)	7 weeks	$60K–$110K	Right-sized; produces audit-ready bridge	Maintenance load

When this approach fits

SaaS / subscription companies $20M–$200M ARR
Salesforce + NetSuite (or comparable)
Active board / investor cadence with metrics expectations
Annual external audit requiring revenue cycle controls
Existing RevOps team owning operating metrics
Disagreement between operating and audited metrics surfaced

Lessons learned

Definitions first, calculation second. Most metric disagreements are definitional, not arithmetic.
Bridge, don't merge. ARR and revenue answer different questions. The right answer is a documented bridge, not forcing them to be the same.
Auditor concurrence on methodology. Worth 1–2 weeks of conversation; saves quarterly disagreement.
Monthly cadence beats annual. Catch drift in real time; fix definitions before they compound.
Same metrics in board pack and disclosures. Disclosure should match what investors see; that's the credibility test.

Frequently asked questions

What's the standard ARR definition?

Most common: contracted MRR × 12 for active subscriptions, excluding pending-start and one-time. SaaS Capital and OpenView publish reference definitions.

How do you handle pending-start contracts?

Best practice: exclude from ARR (not yet earning); separate "pending ARR" or "ending ARR" metric for those. Document the choice.

Why does ARR disagree with revenue?

ARR is annualized run-rate at a point in time; revenue is what you actually earned during a period. They answer different questions.

What about non-recurring revenue (services, setup fees)?

Excluded from ARR. Services revenue typically tracked separately (ASR — Annual Services Revenue) or excluded entirely from subscription metrics.

How does NRR include or exclude expansion?

NRR includes expansion (upsell, cross-sell). Gross retention excludes expansion. Both metrics; both useful; different signals.

What's the right churn timing?

Aligned to revenue recognition timing — when the customer no longer has the right to use the service. Documented per company.

How do you handle multi-year contracts?

ARR = annualized contract value (TCV / years). Recognized revenue allocated per ASC 606 over service period.

What about usage-based revenue?

Best practice: separate "Usage ARR" or include in MRR with disclaimer. Document the choice.

Does this support the public-company disclosure?

Yes — public companies often disclose ARR, MRR, NRR. Documented methodology required for SEC reporting.

What about M&A diligence?

Documented bridge between operating metrics and audited revenue is essential for diligence. Buyer's tax, accounting, and valuation teams all need to see the same numbers.

Board pack ARR not matching audited revenue?

A 30-minute call walks your metric definitions and tells you where the bridge breaks.

Book a free call