Entitlements
Mid-Cycle Upgrades: Change Access and Billing Together
By the Orvlin team · · 2 min read
Mid cycle plan upgrades: what to decide
A customer upgrades to get a feature immediately, then support discovers access waits until the next month. Another account gets new limits today but is charged the full month unexpectedly. Both problems start with an undefined transition.
Specify the effective time, proration policy and treatment of allowances already consumed. Usage charges can remain on the old rate before the transition and use the new rate afterward, or follow another agreed policy. Record the choice instead of inferring it during close.
A concrete scenario
An account moves from a 10,000-unit allowance to 20,000 halfway through its period after consuming 8,000. Granting another full 20,000 differs from increasing the period’s total allowance to 20,000. Either calculation must be made explicit.
A detail teams often miss
Do not use a payment webhook alone as proof that every access update succeeded. Retries and ordering can leave access and commercial state out of sync without an end-to-end check.
Before you put this into production
- Show the effective date before confirmation.
- Define allowance and rate transitions separately.
- Record the old and new plan versions.
- Test an upgrade when usage is already above the old allowance.
Frequently asked questions
- Must upgrades always be prorated?
- No. Proration is a commercial choice influenced by the contract and billing platform. Disclose the policy rather than assuming every buyer expects the same treatment.