Renewal seat overage becomes a true-up line that someone must price, approve and put on the quote before the forecast can count it. For a revenue leader, that change is where forecasts go wrong. A customer may have run more seats than it paid for across the whole term, yet the revenue from those extra seats often shows up only when the renewal is being papered. If the true-up was never modeled, the forecast misses it, and the miss tends to land in the period when the renewal closes.
Key takeaways
- Overage may be payable when the subscription term expires, under the clause in the customer's own agreement.
- Show each true-up as a line for the same product, using the SKU that applies on the renewal date.
- Overage can surface late, so collect seat usage across the whole term rather than relying on the renewal figure.
- Carry a low case and a high case, and record the clause, SKU, usage source and date.
Why forecasts miss it
This matters more when the true-up is a large share of the renewal. A forecast that treats it as a footnote can make a healthy renewal look flat, or make a flat renewal look like a miss. Either way, the revenue leader ends up explaining a gap that could have been planned for months earlier.
This post covers three renewal overage facts that should shape how you forecast a true-up before the renewal call. Each fact is backed by a public source, and each one changes what belongs in the model. The goal is not to predict every contract. It is to make sure the forecast asks the right questions early enough to matter.
We will use one example throughout. Customer A bought a 100-user SaaS - Premium subscription. At renewal, Customer A tells the seller it overused the subscription before the renewal by 10 seats. That case comes from the example in GitLab's Deal Desk Handbook, which walks through how overage is added to a renewal. The handbook describes one company's process, so read its wording as an illustration of the mechanics. The terms that govern your own deal live in your own contract and quote.
Before going fact by fact, fix the dates. Write them in the forecast header. Much of the confusion about which period a true-up belongs to traces back to a date that was never written down.
Fact one: overage may be payable when the subscription term ends
The clearest statement of when overage becomes payable comes from the GitLab handbook, which quotes its subscription agreement this way: "In accordance with Section 6 of the GitLab Subscription Agreement, customers may be required to pay for Overage Users upon the expiration of a Subscription Term in order to renew the Software." (GitLab Deal Desk Handbook)
Two parts of that sentence matter for a forecast. The first is timing. The payment is tied to the expiration of the subscription term and to the renewal that follows it. That places the revenue at the renewal, not in the months when the extra seats were used. A model that spreads overage across the term puts the money in the wrong period, even when the seat count is right.
The second part is the word "may." The quote says customers may be required to pay, not that they always must. Whether overage is due, and on what terms, depends on the agreement that governs the customer. A forecast should therefore carry the true-up as an expected amount tied to a specific clause, and the revenue leader should know which clause that is before the number goes into a board deck.
For Customer A, the practical reading is simple. The 10 extra seats are a renewal item. The forecast should show the true-up in the renewal period, with a short note that the amount depends on the confirmed usage count and on the terms that govern the renewal. If the account team cannot point to the clause, treat that as a gap to close before the forecast is locked, not as a detail to fill in later.
The forecast also needs a view of what happens if the renewal does not close on schedule. If signature slips past the planned date, the overage question moves with it, and the true-up may land in a later period than the model assumes. Put a slip case next to the on-time case, so the cost of delay is visible in the same place as the overage itself.
Write the note in plain words that a finance reviewer can check without asking you. For example: "Customer A true-up for 10 Premium seats, payable at renewal under the clause named in the agreement, pending confirmed usage." A note like that tells the reviewer what the number is, when it lands, and what would change it.
Finance teams often ask why overage cannot be booked the moment it happens. The honest answer is that the overage is only certain once the customer confirms it and the contract makes it payable. Recording it earlier than the documents support creates a forecast that may have to be reversed later, and reversals erode trust in the rest of the model. A better habit is to keep two figures side by side: the overage you expect from usage, and the amount the renewal documents actually support. The gap between them is a risk you should be able to explain in a sentence.
Timing also affects the deal desk. The earlier the revenue leader and the deal desk agree on how the overage will appear on the quote, the less likely the number is to shift in the final week. A late change to the quote moves the forecast, and it can move it into a different period. Ask for the draft quote before the renewal call, not after it. For a related check on quote lines, see quote checks before the forecast call.
Account teams sometimes ask whether the true-up can be handled as a note on the renewal rather than as a separate line. Whether the deal desk accepts that is the deal desk's decision, not the forecast's. Ask the question early, record the answer, and forecast the line the deal desk will actually build, because that is the line the quote will show.
Fact two: the true-up line must match the SKU rules in force at renewal
The handbook shows how overage is written into a renewal quote. For Customer A, the example is direct: "you will need to add an Annual True Up SKU for SaaS - Premium for 10 users." (GitLab Deal Desk Handbook) For a forecast, that wording matters because it tells you what the revenue line should be called and what it should be tied to. The forecast should not show a generic "overage" bucket. It should show a true-up for the same product that was purchased, for the number of users that were over.
SKU structure is not fixed. The same handbook records an earlier change: "Effective 2021-11-15, the “True-up” SKU has been deprecated and replaced with 6 new annual True-Up SKUs, each of which ties to the related subscription SKU." In plain terms, one generic true-up code gave way to a set of annual codes, each linked to the subscription it belongs to. A model that still points to the older structure can show a true-up that matches no code the deal desk can actually use.
The excerpt describes one company's catalog, so the specific codes will differ elsewhere. The lesson for a revenue leader is about structure. Confirm that every true-up line in the forecast maps to a code that exists under the rules in force on the renewal date, and that the code ties to the subscription line it extends. For related checks on annual codes, see SKU rules for annual and multi-year deals.
The handbook also records a later change: "You will need to remove standard SKUs, given the process change effective 2025-08-06." This post will not guess what that change covers or which products it touches. If your renewal falls under a similar process change, ask the deal desk what it means for the line items on your quote before you finalize the forecast.
A simple test helps. For each true-up line, ask three questions: which subscription does this extend, which code does the deal desk use for it, and does that code apply to the renewal date? If any answer is unclear, the line is not ready to forecast, even if the dollar figure looks reasonable.
Fact three: overage can surface late, so the forecast needs usage data from the term
The handbook's second example shows when the seller hears about overage. The customer reports it at renewal, after the term has already run. In the Customer A case, the 10 extra seats come up in that conversation, which is the same moment a revenue leader is asked to put a number on the forecast. (GitLab Deal Desk Handbook)
That timing creates a planning problem. If the only time you see the number is at renewal, the forecast is built too late to plan around. A forecast assembled the week before signature is closer to a count than a forecast. The fix is to use usage data collected during the term, so the number is known before the renewal conversation begins and the team has time to check it.
Microsoft's guidance on forecasting in Excel makes a related point in a different setting. It says: "Using all of your historical data gives you a more accurate prediction." (Microsoft Support) A spreadsheet is a planning aid, and a seat forecast built in one is a planning estimate, not a contract. The principle still carries over. A forecast built from the full usage history is more likely to be accurate than one built from the last snapshot a customer shares.
For Customer A, that means pulling seat counts across the whole term rather than relying on the number the customer quotes at renewal. The customer's figure is a useful check, but it should not be the only input. If the two numbers disagree, find out why before the renewal call. The gap may be a definitional issue, a timing issue, or a real difference in how seats were counted.
A practical step is to share the seat count with the customer before the renewal window opens. Framing it as a usage review rather than an invoice gives the customer time to confirm or question the count, and gives the revenue leader a number that has already been checked. Whether the customer agrees is a commercial question, but if there is a disagreement, having it early leaves time to resolve it before the forecast is final.
Definitions matter here. Many disputes about overage come down to what is counted. Some agreements count assigned seats, others count active users, and some use a different measure entirely. Confirm that the usage measure matches the definition in the agreement before you trust a seat count. A clean number from the wrong measure is still a wrong forecast.
Collect usage on a regular cadence during the term, not in one pull at the end. A monthly record of seat counts against entitlement lets you see the trend, spot a rising count early, and show the account team a pattern rather than a surprise. A short log, with the date and source of each count, is enough to make the forecast defensible when someone asks how the number was reached. For a related case, see seat overage after a mid-term upgrade.
Putting the three facts together for Customer A
Run Customer A through the steps in order, so that each fact shows up in the model.
- Start with the subscription. Customer A has 100 seats of SaaS - Premium, and that is the entitlement the usage count is compared against.
- Pull usage for the whole term. The usage data should confirm or refine the 10-seat figure the customer reports at renewal.
- Map the 10 seats to the true-up SKU for SaaS - Premium that applies to the renewal date. Do not use a generic overage code, and do not assume the older structure still applies.
- Place the revenue in the renewal period, tied to the expiration of the term and the renewal, and record the clause that makes it payable.
- Carry a range. If the confirmed count could move before signing, show a low case and a high case rather than one point.
The dollar value comes from multiplying the seat count by the rate the contract gives for that product. This post does not assume a rate. Use the rate in the contract or quote. If you cannot find the rate for the true-up line, ask the deal desk before you put a dollar value in the model.
Sensitivity is what leaders most often want and least often get. If usage shows fewer than 10 extra seats, the true-up line shrinks in step. If it shows more, the line grows. Showing that relationship in the model lets a reviewer see which assumption drives the result. Once the rate is fixed, the seat count is the variable to verify hardest, and it is the number the account team should be asked about first.
Illustrative example: a 100-seat renewal
Assume a subscription covers 100 seats, and the usage pull over the term shows 10 seats above entitlement. Map those 10 seats to the true-up SKU that applies on the renewal date, and place the line in the renewal period under the clause in the governing agreement. Carry a low case of 5 extra seats and a high case of 15 extra seats until usage is confirmed. This example is illustrative only and uses no rate.
Checks to run before the renewal call
Before you lock the number, work through these checks. None of them needs a special tool.
- Pull monthly seat counts for the full term and compare them with the entitlement.
- Confirm that the usage measure matches the agreement's definition of a user or seat.
- Identify the clause that makes the overage payable, and note it next to the forecast line.
- Confirm which true-up SKU applies to the renewal date, and that it ties to the subscription.
- Ask the deal desk how the overage will appear on the quote, and whether anything else on the quote is changing.
- Record the date you pulled the data and the source of each count.
- Keep a low case and a high case for the overage count.
Where this leaves the forecast
True-up revenue is hard to forecast because it is decided late, through a contract and a quote. Three facts help. The true-up line has to match the SKU rules in force on the renewal date. For Customer A, those facts turn a surprise 10-seat line into a planned renewal item with a clause, a SKU, a usage source, and a range.
The sources in this post describe one company's process and one set of dates. The terms that apply to your deal are in your own paperwork, and the people who can confirm them are your deal desk and your legal team. Read them before the number goes into the forecast, and keep the forecast open to revision until they have.
Next step
Before the renewal call, pull monthly seat counts for the full term and compare them with the entitlement. Then ask the deal desk for the draft quote, so the forecast uses a checked count and a confirmed SKU.
Frequently asked questions
When is seat overage payable?
Overage may become payable when the subscription term expires and the customer renews, under the clause that governs the customer's agreement. Check that clause before the number goes into the forecast.
Which SKU should a true-up line use?
Use the true-up SKU for the same product that was purchased, for the users over the entitlement, provided it applies on the renewal date. A generic overage bucket is not enough.
Why does overage surface late?
Overage often surfaces at renewal, because the customer reports it then. Usage collected during the term lets you know the number before the renewal conversation starts.