Subscription management on SalesforceThe guides: contracts, renewals, amendments, proration, co-terming and the metrics

Subscription management is the practice — and the category of software — that tracks what each customer is entitled to over time: the contract, the subscriptions under it, the assets, every mid-term amendment, and the renewal, with the recurring revenue metrics (MRR, ARR, net revenue retention, churn) rolled up from those records rather than rebuilt in a spreadsheet. It sits between CPQ, which sells the first term, and billing, which invoices it, and it is the part of the revenue system that decides whether recurring revenue compounds or leaks.

What subscription management is, and the records it keeps

Three functions get confused with each other because the same vendors sell all three. They are separable, and knowing which one you are missing is the first evaluation step.

Subscription management is the middle row. Its output is a living record of the entitlement, and the primer explains why B2B companies that sell subscriptions outgrow spreadsheets for it faster than for anything else: a spreadsheet can hold what was sold, but it cannot hold what was sold, then expanded in month seven, then partly cancelled, then renewed with an uplift, and still produce one number. The case for a platform lists the eight signs the spreadsheet has already broken; the most common is a renewal that finance learned about from the customer.

The record structure

Five records, and the relationships between them, are the whole model. Any platform — Salesforce-native or external — that does subscription management well has an equivalent of each.

Two design decisions follow from the table. First, the renewal opportunity is created at the start of the term, not near the end; a renewal that exists from day one is one the forecast can count and one that updates itself. Second, the subscription is a separate record from the order line that created it. The order line is history; the subscription is the current state, and it is what expansions and renewals read.

The lifecycle: new, expansion, renewal

Every subscription business runs three flows, and a good platform carries a record type through opportunity, quote and order so reports can separate them without a custom field.

New. An opportunity for a new agreement becomes a quote, then an order. Releasing the order creates the contract, the subscriptions for each recurring line, the assets for each tracked product, and the renewal opportunity dated at the end of the term. Nothing about the renewal has to be remembered later; it exists.

Expansion. The customer adds seats, a module or a tier mid-term. The rep opens an expansion from the account or the active agreement, adds the lines — pulling previously purchased items at their original price where the deal calls for it — and the platform co-terms and prorates every added line to the existing end date. On release, the contract roll-ups recalculate, the new subscriptions and assets are added, and the renewal opportunity is updated to the expanded footprint. The customer still has one term and one renewal date.

Renewal. As the term approaches its end, a notice goes to the buying contact, the renewal order is generated from the renewal opportunity with any uplift applied, and the customer accepts. Releasing the renewal order either extends the existing agreement or creates a new one — a configuration choice — adds the next term's subscriptions, and creates the following renewal opportunity. The cycle repeats. The step-by-step guide to subscription management in Salesforce walks each flow through the objects.

Renewals: notices, renewal orders, uplifts and the schedule

Renewal automation is five workflows, and the renewal automation guide treats each in depth. The first — renewal opportunity creation at the start of the term — was covered above. The other four run on a calendar.

Two rules make the schedule work. Run the jobs frequently — hourly rather than nightly — so a date that becomes due at 9 a.m. is acted on at 10, not tomorrow. And keep the renewal opportunity honest between notices: if an expansion order was released in month nine, the renewal order generated in month eleven must include it. That is the case for creating the renewal early and updating it on every amendment, rather than building it from scratch at day sixty.

Renewal quoting itself — which lines come across, how they are priced, what happens to retired products — is the subject of how CPQ renewals work. The short version: source lines from active subscriptions and renewable products, not from last year's quote; pick a pricing method (same price, list price, or uplift percent) and a price-protection rule, and write both into the agreement; substitute retired products by rule; and send the quote early enough that the customer's procurement cycle finishes before the term does.

Uplifts and renewal pricing

A renewal uplift is a percentage increase applied to the renewal price, and it is the most reliable source of expansion revenue a subscription business has, because it needs no new seats and no new module. It also causes the most friction when it is a surprise. Three practices keep it clean.

Set the uplift by rule, not by rep: a default percentage at the company level, overridable per account where the agreement says so, and applied automatically to the renewal opportunity's lines. Decide which products are subject to it — a support plan may carry an uplift where a fixed-price hardware line does not — and flag that at the product level. And honor price protection: if the agreement caps increases at a percentage or freezes the price for a term, the platform should apply the cap without someone remembering it. Renewal pricing then has three honest methods — same price, current list price, or last price plus uplift — and the agreement should name one.

Amendments: the six types

A subscription amendment is any change to an active subscription before its term ends. Six types cover nearly every request, and the amendments guide shows what each does to the invoice, the subscription value and the renewal.

The demo question every buyer should ask a vendor is the upgrade: "Add ten seats in month seven. What happens?" Count how many of the following change without a person touching them: the prorated invoice, the subscription quantity and end date, the contract ARR, MRR and TCV roll-ups, the renewal opportunity's lines and amount, the asset records, and the revenue schedule. On a platform where subscriptions live in a separate billing tool, automation stops at the sync and the rest is keyed by hand.

Proration and co-terming: the arithmetic, shown

Proration charges the customer only for the part of the term a change is in effect. The platform picks a unit of time — days or months — and multiplies.

Take the demo question. The term is twelve months starting January 1. The price is $100 per seat per month, which is $1,200 per seat per year, and on August 1 ten seats are added. In a non-leap year, August 1 through December 31 is 153 days of a 365-day term.

The two conventions differ by $30.14 on one amendment. Neither is more correct. What matters is that the method the platform uses is the method the agreement states, so the prorated invoice is explainable line by line to the customer's accounts payable team. A downgrade runs the same math in reverse to produce a credit — but whether the credit is issued at all is a contract term, not a calculation, and it should be decided once in the agreement rather than case by case in the support queue.

Co-terming: one renewal date per customer

Co-terming aligns the end date of anything added mid-term to the existing agreement's end date, so the customer keeps one term and one renewal. In the example above, the ten seats added on August 1 end on December 31 with the original hundred, the first invoice for them covers 153 days rather than a year, and the renewal in December is for 110 seats on one quote.

The alternative — a separate twelve-month term per add-on — produces a customer with two end dates after one expansion and, a year later, a contract nobody can summarize without a spreadsheet: several renewal conversations, several notice emails, several invoice cycles, and a forecast that never quite reconciles to ARR. Co-terming trades a slightly more complex first invoice for a permanently simpler relationship. For a subscription business it is the default; the separate-term case should require a deliberate exception, and a common written policy is to co-term when more than ninety days remain and otherwise to start a full term that becomes the new anchor date at renewal. Whatever the rule, write it down and configure it once. The mistake is deciding deal by deal.

The metrics, with formulas

Subscription metrics are only trustworthy if they are computed from the records above rather than assembled at month-end. The metrics guide covers the full set with benchmarks and review cadences; these are the ones that matter most.

For scale, SaaS Capital's 2025 survey of private B2B SaaS companies puts median NRR near 102% for companies whose typical deal is $25K to $50K a year, with the top quartile around 111%. Report every retention metric by acquisition cohort; blended numbers hide a cohort that churns at eighteen months behind one that churns at twelve. And segment opportunities by type — new, expansion, renewal — because expansion revenue carries no acquisition cost and a record type is the cheapest way to see it.

Revenue recognition sits beside these metrics rather than inside them. ASC 606 (FASB ASU 2014-09) treats an amendment as what the standard calls a contract modification, which changes the transaction price and the remaining performance obligations from the modification date; whether the effect is recognized prospectively or as a cumulative catch-up is a judgment for finance. What the subscription platform owes finance is a clean record of what changed, when, and for how much.

Subscription management in Salesforce

Standard Salesforce gives you Account, Opportunity, Contract and Asset. It does not give you a subscription object — a recurring line with its own quantity, price, start and end dates — or any of the logic above: no renewal opportunity created on release, no co-terming, no proration, no scheduled notices, no uplift by rule. Three ways to add it, from subscription management in Salesforce:

Building it yourself in Flow is a fourth option for the simplest cases — one product, annual terms, no amendments — and becomes a maintenance project the first time a customer adds seats in month seven. Salesforce CPQ's own subscription object (SBQQ__Subscription__c) still works for existing customers, since Salesforce CPQ is end of sale rather than end of life, but it is in a maintenance phase with no new features.

Common mistakes

• Discovering renewals instead of scheduling them. A renewal found in a report thirty days out is already late. Create it at the start of the term.
• Separate terms per add-on. Every add-on with its own term is a future renewal conversation. Co-term by default.
• Re-keying amendments into a billing tool. The rep amends the deal in the CRM; someone types it into billing; the two drift, and the customer sees the drift on the invoice.
• Forgetting to update the renewal after an amendment. The renewal quote then offers last year's footprint.
• Leaving the proration method and the downgrade policy out of the agreement. If the number on the invoice cannot be reproduced from the agreement — $5,030.14, say — it will be disputed.
• Blended metrics. NRR across all customers hides the cohort that is failing. Report by cohort.
• Treating involuntary churn as churn. A declined card is a collections task, not a lost customer; the payments guide covers dunning.

How Kugamon handles it

Kugamon Subscription Management is one Salesforce-native implementation of the model above. It adds New, Expansion and Renewal record types to Opportunity, Quote and Order, and a Subscription object beside the standard Contract and Asset. Releasing a New order creates the Contract, the Subscriptions for service lines, the Assets for product lines, and a Renewal Opportunity dated at the end of the term; the Contract rolls up ARR, MRR, subscription count and dates. An Expansion order opened from the Account or the Contract pulls previously purchased items at their original price, co-terms and prorates every added line to the Contract End Date, and on release updates the Contract and the Renewal Opportunity. Three scheduled jobs, recommended hourly, send the renewal notice, generate and email the renewal order, and keep each Subscription's active flag current; the uplift percent is set in Kugamon Settings, overridable per account, and applied to the Renewal Opportunity's lines; and a renewal can extend the existing Contract or create a new one. Cancelling a Subscription decrements the renewal, and cancelled records are retained for churn reporting. All of it is native Salesforce data, so ARR by cohort is a standard report. The Subscription Management edition is $95 per user per month and Subscription Billing adds invoicing and payments at $125; typical implementation is four to eight weeks.

Keep reading

Seven articles and one glossary term make up this topic. The index that follows lists them with the rest of the glossary.

• What is subscription management? — the definition, the five-stage lifecycle, and how to evaluate a platform.
• Why you need subscription management software — the eight signs the spreadsheet has broken.
• Subscription management in Salesforce — what the standard objects give you and the three ways to add the rest.
• Subscription amendments explained — the six types, the proration math, co-terming, and what should change automatically.
• How to automate subscription renewals in Salesforce — the five workflows, the metrics, and a weeks-long rollout.
• How CPQ renewals work — renewal models, the anatomy of a renewal quote, uplift and price protection.
• How to measure subscription metrics — MRR, ARR, NRR, GRR, CAC payback and LTV, with formulas and benchmarks.
• Co-terming — the definition, a worked example, and when not to co-term.