How subscriptions and renewals work
How an accepted CRM quote starts a subscription, how each renewal becomes a Billing invoice, what happens when payment fails or is refunded, and how long a customer keeps access while a renewal waits.
- Applies to
- Monetization 3.0 and later
- Who can do this
- Administrator, Team member
On this page
In short
A subscription is one customer on one plan, sold by one of your businesses. It starts when the customer accepts a CRM quote for the plan. At the end of each period, Monetization asks Billing for an invoice for the next one, and the subscription moves into that period once the invoice is paid.
If payment doesn't arrive, the customer keeps access for a grace period while Monetization waits and retries. Only then does access end.
How it works
How a subscription starts
When a customer accepts a CRM quote, Monetization looks for a line that adds a plan. If there is one, it starts a subscription:
- In the business that sold the quote. The subscription belongs to that business for good.
- For the customer's billing account. Billing finds or creates the account from the quote's party. The subscription's Account column shows that account's reference.
- At the price on the quote line, whatever the plan's list price is. The subscription keeps that amount and its currency, and every renewal charges the same.
- Active straight away. The first period starts at acceptance.
In Monetization 3.0.0 a subscription started from a quote always renews monthly, whatever interval the plan's price has, because the quote doesn't pass the interval on. It also takes the line's unit price before any line discount, and ignores the line's quantity.
Only the first plan line on a quote starts a subscription. A customer holds one current subscription with each business, so further plan lines are skipped. If the customer already has a current subscription with that business, the new one replaces it: the old one stays on the list with its history, and shows Superseded in the Current column.
A quote that's accepted again, or delivered twice, never starts a second subscription.
Monetization starts nothing when the quote has no plan line, the plan has been deleted, Billing isn't available, or the quote doesn't say which business sold it. The quote stays accepted and Billing still records the order. Monetization 3.0.0 records the reason but shows it on no screen. See A subscription didn't start or renew.
Three dates
Each subscription has three dates, and they answer different questions:
| Column | Answers | For a healthy subscription |
|---|---|---|
| Renews | When Monetization next raises an invoice. Empty once the subscription is canceled. | The end of the current period. |
| Period ends | When the paid period runs out. Hidden by default: add it from the columns menu. | The same as Renews. |
| Access ends | When the customer actually loses access. | Empty. |
A subscription canceled at the end of its period has no Renews date and an Access ends date equal to Period ends. It stays Active until then. See Cancel, resume or end a subscription.
Each renewal
Every day, mon:renew- picks up current subscriptions whose Renews date has passed and makes a renewal attempt for each one. You see them under Monetization › Renewals.
- A free plan (amount 0) renews at once. The attempt is Succeeded and the subscription moves into its next period.
- A priced plan gets a draft invoice in Billing, on the customer's billing account, with one line: the plan's name and the subscription's amount. The attempt stays Pending.
- The invoice is issued and paid in Billing. When its balance reaches zero, the attempt becomes Succeeded and the subscription moves into its next period. A part-paid invoice doesn't move it.
Every 15 minutes, mon:reconcile- asks Billing about attempts that are still Pending, and completes any whose invoice was paid, in case the payment notice was lost.

When a subscription moves into its next period, its failed-payment count goes back to 0, and it gets its plan's current entitlements. Changes to a plan reach subscribers at this point, not before.
Billing creates renewal invoices as drafts, and someone must issue each one under Billing › Invoices. No add-on in this release offers customers a way to pay an invoice through a gateway, so a priced renewal completes only if your own integration takes the payment. See Issue an invoice and How payment gateways work.
When a renewal can't go ahead
| What happened | The attempt | The subscription |
|---|---|---|
| Billing isn't installed or enabled. | Blocked: Billing is not available, so this renewal could not be charged. … | Unchanged. It keeps working on its grace. Blocked attempts don't count against the customer. |
| Billing refused to raise the invoice. | Failed, with Billing's reason. | Past due, and Failed payments goes up by 1. The customer keeps access. |
Each day, mon:run-dunning looks at Failed and Blocked attempts. It schedules a retry after the next delay in the retry schedule, which is 1, 3, 5 and 7 days by default, and shows it in Next retry. When the schedule runs out, the subscription ends at once with Payment failed after all 4 scheduled retries. A blocked attempt doesn't use up a retry: it's always retried after the first delay. See Monetization permissions and server settings.
Nobody can retry an attempt by hand. Retrying a card that was declined minutes ago looks like card testing to banks.
In Monetization 3.0.0 a retry doesn't raise a new invoice or try Billing again, because each period can be claimed only once. The attempt becomes Abandoned, the retry schedule never reaches its end, and the subscription stays as it is until its grace ends. If a renewal is Failed or Blocked, raise a ticket before the grace runs out.
Grace
A subscription whose period ended without a successful renewal isn't cut off at once. The reason may be on your side, such as Billing not being installed, rather than the customer's.
It keeps working until its Period ends date plus the grace, which is 17 days with the default settings: 7 days, raised so it outlasts the whole retry schedule. Then mon:expire- marks it Expired, with the reason The paid period ended and no renewal succeeded within the grace window.
This includes a renewal still Pending because its invoice hasn't been paid.

Refunds
When Billing confirms a refund of a payment that paid for a renewal:
- A full refund of that period ends the subscription at once. It becomes Cancelled, with the reason Refunded in full (…). The customer was un-sold the period, so they don't keep the rest of it.
- A partial refund changes nothing. It's treated as a goodwill adjustment, and access stays.
See Refund a payment.
What the customer can use
When a subscription starts or renews, Monetization writes down what its plan includes for that period, such as 10 seats or 5,000 API calls. Other add-ons, or your own integration, can ask Monetization whether a customer's plan includes a feature and how much of a metered feature is left. A customer with no active subscription is told nothing is included yet.
In this release no add-on asks Monetization this yet, so what a plan includes doesn't switch anything on or off in your Laramin by itself.
How it relates to
- Billing: raises, numbers and collects the renewal invoices.
- Payment Gateway: takes the money for an invoice, when a checkout uses it.
- Plans: give a subscription its features. The price comes from the quote.
Next steps
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.bsscn.com. The online article may have changed since.