Skip down to the research record

Seat overage after a mid-term upgrade: 3 figures

Quota Forecast Editorial Team · Published · 11 min read

In GitLab's example, a mid-term upgrade with 48 max billable users and 25 paid seats immediately shows a seat overage of 23.

Key takeaways

  • Check the usage record dated to the upgrade day.
  • Match the paid seat count to the signed amendment.
  • Keep a dated record of each new usage peak.
  • Confirm the renewal date before the deal review.

One deal, followed from start to finish

Consider a single customer. It holds a premium license for 50 users. Partway through the term it upgrades to a higher tier, and on the upgrade date it has 48 maximum billable users. At the same time it decides to cut its paid seat count to 25 on the new order.

The numbers come from the worked example in the GitLab Deal Desk Handbook. That page describes a customer with a premium license for 50 users and 48 max billable users as of the upgrade date, and a customer who upgrades to Ultimate but reduces seat count to 25. The handbook figures describe this customer; the separate what-ifs below are illustrative.

As a revenue leader, your question is simple to state. After an upgrade and a seat cut, how many seats sit over the paid count, and how do you record that so the deal review can follow it?

Three figures set that number. The sections below take them in order, then cover how to record the change in the subscription and how to present it in a deal review. The method is general enough to use even if your product, price, or contract differs from the example, but the specific figures belong to this one case.

Figure 1: the maximum billable users on the upgrade date

The first figure is the highest number of billable users the customer has when the upgrade happens. In the example the customer was licensed for 50 users, but it had 48 max billable users as of the upgrade date. That 48 is the starting point for the overage, not the 50 on the original license.

This distinction matters because the license count and the usage count answer different questions. The license count tells you what was sold. The billable count tells you what the customer was actually using on a given day. The handbook's overage calculation starts from the billable figure, so a deal review that starts from the license figure will reach a different answer.

A quick check helps here. Compare the billable figure you plan to use with the license count. In the example the two differ by 2, since 50 were licensed and 48 were billable. If the difference is zero, confirm that the usage record is real and not simply copied from the order. If the difference is larger than you expect, look for users who were added or removed during the term, and confirm that each change has its own date in the record.

If your billing system reports a monthly count, check whether that count is the peak for the month or the count on one specific day. Those two can differ, and a reviewer will ask which one you used. Write the figure down with its date attached. "48 as of the upgrade date" is an answer a reviewer can check. "About 50" is not.

Figure 2: the new paid seat count

The second figure is the number of seats the customer pays for after the change. In the example, the customer "upgrades to Ultimate but reduces seat count to 25." The new paid seat count is therefore 25, and it is the number the amendment has to state.

The gap between the two figures creates the overage. Subtract the paid count from the peak billable count and you get 48 minus 25, which leaves 23. The handbook's wording is specific about the timing: the overage shows as 23 "until the next renewal." Do not present it as cleared before the renewal date.

Check that the paid seat count in the amendment matches what the customer agreed to in writing. A mismatch between the quote and the subscription record is a direct route to an overage that nobody planned for. In an illustrative what-if, if the sales conversation said 25 and the order says 26, the review will show an overage of 22 and the team will spend the meeting explaining the difference. Read the order line by line before it is filed. For related checks, see quote acceptance checks.

There is also a question of sequence. The handbook's example handles the upgrade and the seat reduction together, with one set of figures. That is why this post treats them together. If your team records the upgrade and the cut as two separate changes on different dates, the figure from the upgrade date may no longer match the paid count, and the gap has to be rebuilt from both records.

Figure 3: the peak seat count until renewal

The third figure is the highest seat count the customer reaches between the upgrade and the next renewal. The handbook's example is conditional. The overage is 23 "unless the customer then goes above 48 seats, in which case the overage will increase." So 48 is a floor for the peak, not a ceiling.

Illustrative example: a higher usage peak

In this illustrative what-if, usage climbs to 50 before renewal while the paid count stays at 25. Subtract 25 from 50 to get an overage of 25. Record the new peak and its date beside the paid count.

This is the figure most likely to change after the deal is signed, so it needs the most attention in the record. A deal review held after the upgrade should show the current peak, not the peak on the upgrade date. Keep the peak in a running record, and note the date each new high was reached. When someone asks why the overage moved, the answer should be a date and a number.

A practical habit is to check the peak on a fixed schedule, such as at the start of each month, and write down the result even when nothing has changed. A flat line in the record is evidence that the team looked. Without it, a reviewer has no way to tell a stable overage from one nobody has checked since the upgrade.

What happens at the renewal is a matter for the renewal terms on the contract. Confirm the renewal date and the seat count that will apply after it before you describe the overage as settled. If the renewal date is close, that changes how urgent the conversation with the customer is.

Prorating the change on the order

A mid-term change can affect the amount billed for the period, not only the count of seats. The GitLab handbook says amounts on add-on/amendment order forms are prorated based on calendar days, illustrating this with an addition of 10 users to an existing subscription. Its example counts "177 days (7 Apr 2022 - 1 Oct 2022 in this example)" for the add-on period.

Those numbers belong to the handbook's add-on example, which adds 10 users. They are not the figures for a reduction to 25 seats, and this post does not apply them to our case.

For the deal review, ask your billing or deal desk team to confirm which days count as the changed period on your order form. Get the day count from them, the total from the order, and keep both in the deal file. A reviewer who asks how a figure was calculated should be able to see the day count and the formula without a second meeting.

Do not assume that proration works the same way for every vendor or every contract. The handbook is one company's internal guidance, and it describes its own order forms. Your order form may calculate the partial period differently, so check the wording on your own form before you copy the method.

Recording the seat change in the subscription

If your deal is a licensed subscription, check how Stripe defines it. The Stripe documentation on revenue recognition describes licensed subscriptions as "subscriptions that generate invoices for a service offered in an upcoming service period." That page covers how subscriptions are recognized in revenue, not seat overage, so use it for the definition only. Check your own subscription and invoice records before deciding how a seat-count error affects later invoices.

The handbook records this kind of change through an amendment. It says to "Create an 'Amend Subscription' quote by following the steps in Section 2 (A) above." The steps in that section are the handbook's own, so follow your company's version of them. The principle is the one that matters: keep the original subscription, attach an amendment that carries the upgrade and the seat change together, and avoid two records that disagree about the same customer.

A record for this deal should hold the following items, each with its date:

  • the upgrade date and the premium license held before it
  • the max billable users on that date, which is 48 in the example
  • the new paid seat count, which is 25 in the example
  • the overage at the time of the review, which is 23 in the example
  • the highest peak reached since the upgrade
  • the next renewal date

Keep the record in one place. If the sales system, the billing system, and the deal review each hold a different version of the paid count, the review will argue about the data before it discusses the customer. For related record checks, see deal change records.

Name an owner for each item in the record. In most teams that means sales owns the reason for the cut, the deal desk owns the amendment, billing owns the invoice and the day count, and finance owns the question of how the overage is reported. When each item has a named owner, a question in the review has a clear person to answer it, and the answer does not wait for a follow-up thread.

Presenting the overage in the deal review

A deal review asks three things: what changed, what the number is now, and what happens next. Answer them in that order, and keep each answer to the figures in the record.

On what changed, state the facts plainly. The customer moved from a premium license to Ultimate and set its paid seats at 25. The customer had 48 max billable users when the upgrade took place. Say both numbers and the date they apply to. A reviewer who sees a 48 and a 25 side by side will understand the gap before you explain it.

On the number now, show the arithmetic. Mention the usage date you used and whether the peak has risen since. If the peak has not moved, say so, because it tells the reviewer the overage is stable. If the peak has moved, give the new figure and the date it was reached, and recalculate the overage using the same formula.

On what happens next, tie the answer to the renewal date. The review should therefore name the renewal date, the current peak, and the action the team proposes.

Frame the overage as the result of a decision the customer made, not as an error. The customer chose the upgrade and chose the cut. The review's job is to show the arithmetic, the date, and the next step, so the room can decide what to do about it without arguing over whether the number is right.

Reviewers tend to ask the same few questions. Prepare answers to them before the meeting:

  • Which usage date produced the 48, and where is that record kept?
  • Does the paid count of 25 match the signed amendment?
  • Has the peak passed 48 at any point since the upgrade?
  • When is the next renewal, and what seat count applies after it?
  • Who confirmed the day count used for any partial-period amount?

If you can answer all five from the record without going back to the customer, the deal review will move quickly. If you cannot, the gap in the record is the thing to fix before the meeting, not something to explain during it.

Where this approach stops

The example covers one customer, one upgrade, and one seat cut. Real deals often include several changes in one term, more than one product, and renewal terms that differ by line item. Each extra change adds another figure to track. The three-figure method still works, but you need a separate record for each change, and the overage has to be recalculated at every point where a figure moves.

The method also depends on the definitions in your own contract. The handbook's example uses "max billable users" and "new paid seat count" as its labels for the two figures. Your contract may define billable users by a different test, count seats on a different date, or treat a reduction differently from an upgrade. Read the definitions in your agreement before you copy any calculation from a published example.

Involve the right people early. A seat change that reaches the deal review with no billing check, no usage date, and no renewal date tends to need a second review, which can cost more time than the first one saved. Ask for the data before the meeting, not during it.

Your next step today

Build your record from your own usage data and your own signed order, and use the three figures to check that the record is complete.

Related guides: Mid-term upgrade deal amount: 4 steps to explain it · Access log checks: 4 steps after a shared login changes · CRM seat prices to check before adding a seat: 5 steps.

Questions about the seat change

Where should I get the upgrade-day usage figure?

Pull this number from usage records dated to the upgrade day, not from the original order form.

Can I call the overage a bill or a credit?

Do not describe the 23 seats as billed, credited, or waived unless the signed order says so.

Sources