Source
Plans, pricing models & subscription lifecycle — found from sitemap — Lago
Checked for Lago on 26 Oct 2026
- Page
- https://knowledge.getlago.com/articles/5572912843-pro-rating-behavior-when-upgrading-a-subscription-mid-cycle
- Checked
- 26 Oct 2026, 16:51 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:1734984b7cb234be1dfd18359f7b022c090379c453e36847b91871b55485574e
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Proration formula Report an error
“Lago calculates the prorated charge as days remaining in the period, divided by total days in the period, multiplied by the plan's monthly fee.”
-
Proration example Report an error
“a customer who starts a new $29/month plan on day 9 of a 30-day period is charged about $21.27 for the rest of that period (22 / 30 x $29), before tax.”
-
Calendar billing renewal Report an error
“For calendar billing, the renewal date is always anchored to the first of the month regardless of when the new plan was activated. A subscription activated April 9 renews May 1.”
-
Anniversary billing new external id Report an error
“For anniversary billing, a new subscription created mid-cycle anchors to its own creation date, so a subscription created April 9 renews May 9, and the anchor does not carry over from the previous plan — but only when a different external_id is used.”
-
Same external id upgrade Report an error
“If the same external_id is used, Lago treats the request as an upgrade and preserves the original anniversary date.”
-
Same external id no explicit termination Report an error
“If you use the same external_id, Lago automatically handles the transition and you do not need to explicitly terminate the old subscription first.”
-
Different external id concurrent Report an error
“If you use a different external_id, Lago creates a separate subscription and does not automatically terminate the old one; both run concurrently until the old one is explicitly terminated, which may generate a final invoice or credit note.”
-
Pay in advance credit note condition Report an error
“For pay-in-advance plans, terminating issues a credit note for unused days only if a prior invoice exists for that subscription. A backdated subscription that never generated an advance invoice won't produce a credit note.”
-
Termination day counts as used Report an error
“The day of termination counts as used, and the credit covers the days after that.”
-
Avoid proration method Report an error
“To charge the full monthly fee from a specific date instead, terminate the current subscription and create a new one on the desired plan starting today. This sets a clean billing anchor and charges the full fee from day one.”
-
Documentation status Report an error
“This article reflects guidance drawn from customer case resolutions. It is not officially supported documentation and may not apply to all situations.”
Scores citing this record
- The Billing Engineer Plans, pricing models & subscription lifecycle
- The Billing Engineer Plans, pricing models & subscription lifecycle
- The Finance Lead Plans, pricing models & subscription lifecycle
- The Finance Lead Plans, pricing models & subscription lifecycle
- The SaaS Founder Plans, pricing models & subscription lifecycle
- The SaaS Founder Plans, pricing models & subscription lifecycle
- The Service-Business Owner Plans, pricing models & subscription lifecycle
- The Service-Business Owner Plans, pricing models & subscription lifecycle
- The Skeptic Plans, pricing models & subscription lifecycle
- The Skeptic Plans, pricing models & subscription lifecycle
- The Tax Adviser Plans, pricing models & subscription lifecycle
- The Tax Adviser Plans, pricing models & subscription lifecycle