Proration & Lifecycle Charges
Last updated 12 Oct 2026
At a glance
Every mid-cycle change produces a number on an invoice: a prorated first charge, a credit for a downgrade, a final charge on cancellation. The method behind each number (how days are counted, when a downgrade takes effect, what a suspension costs) is a product decision. It belongs in the catalog and must be applied the same way in CPQ, billing, rating and self-care.
The picture
An upgrade on day 15 of 30. Each plan is charged only for the days it was held.
1 · Change
Upgrade €30 → €40
Effective day 15, recorded by fulfilment
Cycle: 30 days, billed in advance
2 · Split the cycle
days 1–15
Old plan
€30 × 15/30 = €15
days 16–30
New plan
€40 × 15/30 = €20
Method is a product decision: actual days in the month, a fixed 30-day month, or none (change from the next cycle)
3 · Cycle total
€35
with proration
- Old plan only€30
customer got the upgrade free
- Both plans in full€70
customer charged twice
How it works
The assumptions
All figures here are illustrative: a 30-day cycle, recurring charges billed in advance, daily proration. Real operators differ on each of those, and each is a product decision recorded in the catalog. None of them should be a billing-system default.
Worked examples
| Event | Example | Calculation | Result |
|---|---|---|---|
| Activation | €30 plan, active from day 11 | €30 × 20/30 | €20 first charge |
| Upgrade | €30 → €40 on day 15 | €30 × 15/30 + €40 × 15/30 | €35 for the cycle |
| Downgrade | €40 → €30 on day 21, €40 billed in advance | credit €40 × 10/30, charge €30 × 10/30 | €3.33 net credit |
| Add-on | €10 add-on added on day 16 | €10 × 15/30 | €5 |
| Termination | Cancelled on day 10, €30 billed in advance | credit €30 × 20/30 | €20 credit, plus any early termination fee |
| Adjustment | Three-day outage on a €30 plan | €30 × 3/30 | €3 credit with a reason code |
What each example hides
- Activation: the charge starts on the activation date recorded by fulfilment. Ordering on day 5 and activating on day 11 must not produce a €25 charge.
- Upgrade: without proration the customer sees €30 or €70. Both are wrong and both generate calls.
- Downgrade: many operators apply downgrades at the next cycle boundary instead. That avoids credits, but the customer pays the higher price until then, so the policy must be stated in the product terms.
- Add-on: billing prorates the price, but rating or the OCS applies the allowance. Does the customer get the full 10 GB, or 5 GB for half a cycle? If the two follow different rules, the customer is charged for one thing and given another.
- Termination: an early termination fee is a one-time charge from the contract terms. The recurring charge must stop; a missed termination event is the classic "still billed after cancelling" complaint.
- Adjustment: it corrects the account and leaves the cause in place. A high adjustment volume on one product usually points to a catalog, proration or integration defect for Revenue Assurance to trace.
Suspension: why matters as much as when
| Type | Example | Typical charging |
|---|---|---|
| Voluntary | Customer abroad for two months keeps the number | Reduced fee, say €5 a month |
| Involuntary | Barred by dunning (6.12) | Contract continues, so the recurring charge often continues |
Which applies depends on the contract and local regulation. Billing must know why the service is suspended, not only that it is.
Three proration methods
| Method | How a day is valued | Effect |
|---|---|---|
| Actual days in the month | Monthly price ÷ days in that month | A February day is worth more than a March day |
| Fixed 30-day month | Monthly price ÷ 30 | Same daily value all year |
| No proration | Full-month charges from the next cycle | No partial charges or credits; changes wait for the cycle |
Each method gives a different number for the same change. The method must be consistent across billing, the quote in CPQ and the self-care app, or the customer is shown one figure and billed another.
Who owns what
| Entity | System of Record | System of Engagement | System of Reference | Notes |
|---|---|---|---|---|
| Proration method, downgrade timing, suspension charging | Product Catalog | — | Billing, CPQ, Self-care, Rating / OCS | TMF620. Product decisions stated in the product terms. |
| Effective dates of lifecycle changes | Product Inventory / Subscription Management | — | Billing | TMF637. Activation date comes from fulfilment, not the order. |
| Prorated charges and credits | Billing | Self-care, CRM | — | Calculated by billing from catalog rules and effective dates. |
| Allowance for a part-cycle add-on | Balance management (Rating / OCS) | — | Product Catalog | Must follow the same rule as the prorated price. |
| Adjustments and reason codes | Billing | CRM (agent desktop) | Revenue Assurance | Reason codes make adjustment volumes traceable to their cause. |
In practice
Proration logic can exist in three places: the billing engine, the CPQ quote and the self-care app's "what will I pay" screen. Where each was built separately, they disagree at the edges: month length, the day of change itself, rounding.
Adjustments are where these defects become visible. Agents raise credits to settle complaints, and the volume of credits per product is often the first signal that a rule is wrong.
The trade-off
What it solves
Explicit, catalog-held proration rules give every mid-cycle change one correct number, the same in the quote, the app and the invoice.
What it does not solve
- Wrong effective dates from fulfilment or SLM, which prorate correctly to the wrong day.
- An allowance applied by rating under a different rule from the price applied by billing.
- Customers already billed under an older rule.
What it adds
- Every channel that shows a price must implement or call the same proration logic.
- Credits and refunds need their own approval, reporting and revenue treatment.
- Suspension types need reason codes carried from dunning and CRM into billing.
Architecture decision
When should a downgrade take effect?
Immediately, with a prorated credit
Choose when the customer expects the lower price at once, and billing, CPQ and self-care can all show the credit the same way.
At the next cycle boundary
Choose when credits are costly to process or explain, and the product terms state clearly that downgrades wait for the cycle.
Breaks if the policy is not written into the product terms, or channels apply different rules. The customer is then promised one figure and billed another.
Takeaways
Key Takeaways
- Every mid-cycle change produces a calculated charge or credit, and each calculation rests on product decisions
- Proration method, downgrade timing and suspension charging belong in the catalog
- The same rule must be applied in billing, CPQ, self-care and, for allowances, rating
- Billing must know why a service is suspended, because voluntary and involuntary suspension charge differently
- High adjustment volumes on one product point to a defect worth tracing
Check yourself
A customer upgraded on day 15 and was billed €70 for the cycle. What went wrong?Show answerHide
No proration: both plans were charged in full. With daily proration on a 30-day cycle the total is €15 for the old plan plus €20 for the new, €35.
Customers who add a 10 GB add-on mid-cycle pay half price but get the full 10 GB. Is that a billing defect?Show answerHide
It is a mismatch between two rules: billing prorates the price, rating or the OCS grants the full allowance. Either can be the intended policy, but both must come from the same catalog rule.
The CPQ quote for a plan change differs from the next invoice by a few cents. Where do you look?Show answerHide
At the proration method and rounding in each system. CPQ and billing are applying different rules (month length, the day of change, rounding), which should both be read from the catalog.