To explain a mid-term upgrade in the deal amount, split the term at the upgrade date and value each part at its own price.
Key takeaways
- split the term at the upgrade date before you compare the old and new totals.
- write both prices beside the number of days each one covers.
- check which price the credit uses, and note any discount on that price.
- treat a term reset as a separate decision that you confirm with the customer.
- keep the dates, prices and invoice together for the forecast call.
Stripe's example shows the split: the customer receives 20 days of service with the 90 USD monthly subscription (60 USD in value) and 10 days of service with the 120 USD monthly subscription (40 USD in value), according to Stripe. Your explanation then shows which part of the term carries each price, before anyone debates the new total.
What changes when a customer upgrades mid-term
Stripe's example is one method for explaining one change, not a rule for every billing system. You should match the unit to your own invoice before presenting the split as settled.
A mid-term upgrade changes the amount because one term can contain two prices. In Stripe's example, the customer upgrades on April 21 to a subscription that costs 120 USD. The days before the upgrade still count in the example, so the explanation has to describe them too. Keep those two parts in view when someone asks why the number moved.
Describe the upgrade as two periods rather than one price change on one date. The first period is the time before the upgrade, and the second is the time after it, with each period carrying its own price. Write both periods in plain terms before you mention a total, a credit or a term reset. A reader can then check each period against the invoice without needing the rest of the deal history.
The date is the hinge of the split, so do not round it to the month. Stripe's example counts days of service, which is the unit to match against your own records. A short note with the dates and invoice reference is easier to defend than a recollection of the call.
Your notes should hold the upgrade date, the old price and the new price in one place before the call. You can add the day count for each part once the invoice is in hand. Your explanation stays with the amount and its causes, and forecast opinions about the customer can wait until the split is agreed.
Step 1: Record the upgrade date
Your deal notes should show the date the upgrade takes effect, which may differ from the day the customer first asked about it. Stripe's example generates an invoice for the upgrade that accounts for the remaining 10 days of the month, according to Stripe. Use that same date in every place the change is recorded, so the split starts from one fixed point.
Write the day count beside the date, with the days before the upgrade on one line and the days after it on another. Keep the count tied to the invoice reference, so a reviewer can trace each day back to the bill. Use one date format across all your deals, since a shared format makes upgrades easier to compare side by side. If the effective date differs from the date on the signed order, record both dates and the reason in the same entry.
Check your count against the invoice before you rely on it. If the invoice shows a different number of remaining days, check the upgrade date first, since the split depends on that date.
Label the upgrade date and signed-order date separately in the file. A reader who sees only one date cannot tell which date started the new price. Use the label your team already uses for each event, so the names match across deals. For a record of how dates moved, see the close date change log.
Read the recorded date back to the person who will present the split before the call. Ask them to confirm that it matches what the customer was told and what the invoice shows. Note who confirmed it and when, so the confirmation can be found later.
Step 2: Value each part of the term at its own price
Write each part of the term as its own line in your notes, with its days, its monthly price and its value. Separate lines let a reader see where the amount moved without reading the whole term at once. Keep the line order the same as the dates, starting with the period before the upgrade and ending with the period after it. This keeps the comparison with the invoice simple, since each line has one price and one set of days.
Do not combine the two values into one figure until each line matches the invoice.
Stripe's documentation also includes a separate example for a 3-month subscription canceled after the first month. Keep that case in its own note rather than in the upgrade split, so the two examples are not mixed. Write its start date, cancellation date and invoice reference in that note, so it can be checked on its own.
Compare each line's value with the matching invoice line before you add the lines together. If the values do not match, the dates and day counts are the first place to look, because the split depends on them. Recheck the price on each line as well, since a mismatch can come from the price rather than the dates. For checks on quoted amounts before they reach the forecast, see the quote approval checklist.
When every line matches, describe the change as a move from one value to the other. A reader can follow a move between two values more easily than a single new number that appeared without a stated cause. Use the wording from your own lines in that description, so the explanation stays tied to the invoice. Save the finished lines with the invoice reference, so the call can start from the same figures.
Illustrative example: splitting one upgrade
Suppose your notes show an illustrative credit of 40 USD and an illustrative charge of 60 USD. Subtract the credit from the charge: 60 USD minus 40 USD leaves 20 USD. Keep both lines visible so a reviewer can follow the calculation. These figures illustrate the arithmetic only; check the day counts and prices against your own invoice before using them.
Step 3: Check which price the credit uses
Confirm which price the credit used before you explain the credit line. Your explanation should name the discount, if there is one, along with the original price.
Leave the proration lines as they appear on the invoice when you rebuild the amount.
Compare the credit line with the price you showed the customer. This check is separate from the credit amount itself, so give it its own line in your notes. If the credit looks wrong, check the discount on the subscription first, then the price on each line, before you change the total.
Keep the original price in your notes beside the discounted price. Label each one clearly, so a reader can see which price the credit used without guessing. Store both values with the subscription's dates, so the discount can be matched to the period it covered.
When you present the credit, name the price it uses first and then the discount that changed it. A listener who hears the discount first may assume the original price was used. Write this order into your notes so the same sequence is used on every call. Close the credit section by pointing to the invoice line it matches, so the claim can be checked in one step.
Step 4: Decide whether the term resets
A term reset is a separate decision from the upgrade itself, so it deserves its own line in your notes. You can note whether the customer asked for it, and when, without changing the split.
GitLab's handbook says that if a customer wishes to reset the subscription term in the middle of their term, for example to reset it for 12 months starting on the date of upgrade, a new subscription is needed, according to GitLab. Read that as a condition that depends on what the customer wants. Your notes should therefore record the wish itself, not the upgrade alone.
Ask the customer about the reset during the upgrade conversation, and write down the answer with the date you asked. A recorded answer shows the decision was checked rather than assumed. If the answer is no, note that too, so the file shows the question was raised.
If the customer does not want a reset, your explanation rests on the two parts of the term and their prices. If the customer does want a reset, record the decision and keep the earlier split on file as the history of the change.
Note in the file which subscription the reset replaces, so a reviewer can follow the change from the old record to the new one. Keep the upgrade date on both records so the sequence stays readable. Describe the new term in plain words on the call, stating its start date and length, so the reader hears what the customer agreed to. Compare that description with the subscription record before the call ends.
What to keep on file for the forecast call
Your file should hold the upgrade date, both prices, the day count and the discount note together in one record. A reviewer should be able to rebuild the split from that record. Keep the invoice reference beside the split. Store the note where the person presenting the forecast can open it before the call. For how forecast categories are named, see pipeline, best case and commit categories.
GitLab's handbook describes its own timing: reconciliation is performed 7 days after opportunity creation by committing an amendment to the subscription in Zuora and generating an invoice. That timing belongs to GitLab's process, so use it as a model for your notes rather than as a rule.
GitLab's handbook also says that, in most cases, if a QSR opportunity is opened but is not closed within 14 days after creation, that means the QSR failed and the opportunity should be closed as Closed Lost. You should treat that rule as GitLab's, written for QSR opportunities, and not as a rule for other vendors or for deals that are not QSR.
If you rebuild the split in a script, the Python decimal documentation says the quantize() method rounds a number to a fixed exponent. You should compare the rounded result with the invoice before sharing the figures. You can write the source name and the date you read each page in your notes, so the references can be checked later.
Related guides
Your next step
Your next step is to take your latest mid-term upgrade and split its amount by days at each price, then compare the result with the invoice.
Questions
How is a mid-month upgrade valued?
In Stripe's example, the days on each side of the upgrade are valued at the price that applied to them, according to Stripe. Other billing systems may differ. Take the dates from your own invoice and compare the split with it before presenting the amount as settled.
Which price do proration credits use?
Stripe's proration documentation says the discounted price is the one used for credits or debits, not the original price, according to Stripe. The original price can stay on file as a reference. Check the discount on the subscription before you total the credit. This answer reflects Stripe's documented rule, so confirm your own billing system's rule before applying it.
Do discounts apply to proration lines?
Stripe's documentation says that no further discount is applied to the proration line items, since they are marked discountable=false, according to Stripe. Keep a separate note for the proration lines, apart from the subscription discount note. Check the subscription discount separately from those lines when you reconcile them.
What does a term reset require?
Confirm the customer's wish to reset the term before changing the subscription record. Settle the question with the customer while the upgrade is still being discussed. Because the wish comes from the customer, record the reset as a decision the customer made.