Key Takeaways

• Cotermination aligns end dates, not start dates. The second subscription starts whenever the customer buys it and simply stops on the date the first one already had.

• The partial stretch between the add-on date and the shared end date is a stub period, and it bills at a prorated rate rather than the full term price.

• A $6,000 annual add-on bought on 1 May against a term ending 31 December covers 245 days and prorates to $4,027.40.

• Stripe implements cotermination through the billing_cycle_anchor parameter, which sets the reference date every future billing period aligns to.

• Co-terming concentrates renewal risk. Every dollar a customer spends comes up for renegotiation on the same day instead of spreading across the year.

How does a coterminous subscription work?

Cotermination works by pinning the new subscription's end date to the existing one and charging only for the days in between. The sequence looks the same across most billing systems:

1. Read the end date on the customer's existing term. That date becomes the anchor.

2. Set the new subscription's end date to match it, which produces a stub period shorter than a full term.

3. Divide the new subscription's list price by the days in its normal term to get a daily rate.

4. Multiply the daily rate by the days in the stub and invoice that amount.

5. Let both lines renew together at full price on the shared date.

Here's the arithmetic on a real shape of deal. A customer pays $12,000 a year on a term ending 31 December. On 1 May they add a second subscription listed at $6,000 a year and want it coterminous.

Platforms expose this as a date anchor, not a "coterminate" button. Stripe's billing cycle documentation calls billing_cycle_anchor the reference point that aligns future billing period dates, and Stripe auto-creates a prorated invoice covering the gap before the first full invoice. Salesforce CPQ groups subscription products by end date instead, so amendments inherit the parent contract's term. Either way you're moving a billing period boundary.

What breaks when you align subscription end dates?

Cotermination trades daily convenience for a set of edge cases that surface at renewal and at month-end close. The ones I see cause real damage:

Renewal concentration is the one teams underestimate. Cotermination sells as a customer-experience win, and it is, but it also hands the buyer one annual moment to renegotiate everything at once. Co-term aggressively and renewal conversations get larger, not simpler.

The metering issue is narrower and nastier. Co-term a metered line into a 60-day stub and the monthly commitment still expects a full month of consumption, so the first invoice either overcharges or triggers overage charges nobody agreed to. Prorate the commitment with the price, or keep metered lines off cotermination.

Related terms

These neighbouring pages cover the date and renewal mechanics cotermination depends on.

• Anniversary Billing anchors each customer to their own signup date, which is what cotermination overrides for the second subscription.

• Calendar Billing aligns every customer to a fixed date such as the 1st, a fleet-wide version of the same alignment idea.

• Billing Period defines the window a stub period shortens.

• Subscription Lifecycle maps the amendment and renewal states a date change has to pass through.

• Auto-Renewal determines what happens on the shared end date once both lines reach it.

FAQ

Is co-terming the same thing as a coterminous subscription?

Yes, co-terming is the verb for creating a coterminous subscription. Sales and CPQ teams say "co-term this add-on" to mean aligning its end date with the existing contract. The adjective comes from contract law, where coterminous describes an obligation running for the same term as another.

How does a coterminous subscription differ from anniversary billing?

Anniversary billing sets the recurring date from a subscription's own start date, while cotermination forces one subscription to adopt another's end date. A customer can hold several anniversary-billed subscriptions on different dates, and co-terming collapses them onto one, usually the earliest existing term end.

Can you make a subscription coterminous after it has already renewed?

You can, but it costs a credit. Moving the end date backward on a term the customer already paid for means issuing a credit memo for the unused days, then rebilling the shortened period. Stripe's docs warn that resetting the anchor without proration overcharges the customer.

Should usage-based lines ever be coterminous?

Only when the commitment prorates with the term. A metered line dropped into a short stub keeps its full-term thresholds unless you scale them down, so the customer hits tiers early. Scale the commitment, the included quantity, and the price to the stub together.