---
title: "Making usage-based revenue and multi-year bookings reportable on one spine"
type: case-study
evidence_type: proof
category: "Reporting, Forecasting & Board Metrics"
publisher: "LeanScale"
date_modified: 2026-08-08
word_count: 305
topics: ["forecasting", "revenue-operations"]
canonical_url: https://knowledge.leanscale.team/customers/unifying-usage-based-revenue-and-multi-year-bookings-in-the-crm/
source: "LeanScale Knowledge Hub — https://knowledge.leanscale.team"
license: "Free to quote and cite with attribution to LeanScale."
---

# Making usage-based revenue and multi-year bookings reportable on one spine

**Evidence type:** proof (what happened)

A late-stage AI company earned revenue three different ways — subscription, metered consumption, and cloud-marketplace usage — and none of it reconciled in the CRM. LeanScale built the pipeline and the bookings math that put consumption revenue, multi-year contracts and renewals on a single reportable spine.

## The challenge

Revenue arrived through three separate feeds — a usage-based billing platform plus two cloud-marketplace channels — in multiple currencies, and none of it reconciled inside Salesforce. Multi-year and committed contracts did not fit standard bookings and ARR math, so the reported number flattened deals that had actually been signed for years. Currency drift was quietly distorting renewal figures, which meant leadership reporting and compensation reporting were both arguing with the same unreliable data.

## The approach

Consumption revenue pipeline
Built the pipeline that lands subscription, metered-consumption and cloud-marketplace usage into Salesforce, including a flexible usage rollup that summarizes spend by product line, account and period — with month-end batch processing, currency conversion and duplicate handling hardened until it ran unattended.

Multi-year bookings and ARR mechanics
Extended the bookings and ARR infrastructure to carry first- through sixth-year MRR, bookings and ARR across the total-contract-value, contract and order automations, so multi-year and committed deals report correctly instead of collapsing into year one.

Separating currency drift from real change
Added an FX-exposure field and antecedent-exchange-rate stamping so movement in renewal numbers caused by currency drift is separated from real contracted change, plus GRR and NRR fields and proof-of-concept-to-committed conversion handling.

## Outcomes

Three feeds, one reportable spine
Subscription, metered consumption and cloud-marketplace usage all now flow into Salesforce behind a single usage rollup; the first month-end close on the hardened pipeline ran with very few errors, confirmed by the customer on the sync call.

Six-year bookings horizon
Bookings and ARR now carry out to six contract years across the total-contract-value, contract and order automations, so multi-year and committed deals no longer distort the reported number.

Currency drift isolated from contracted change
An FX-exposure field plus antecedent-rate stamping isolated a block of currency-driven variance in renewal ARR that had previously been read as real contracted change, cleaning up both leadership reporting and compensation reporting.

## Quotes

> Oh, this is awesome. Thank you so much. This looks great.
>
> — Customer, Revenue Operations leader


## Canonical

https://knowledge.leanscale.team/customers/unifying-usage-based-revenue-and-multi-year-bookings-in-the-crm/