All guides

SaaS true-up explained: what it is and how to avoid a surprise bill

A true-up is a charge for using more of a product than your contract covers. For example, if you bought 100 seats and 120 people used the software, the vendor bills you for the extra 20 at an agreed time. Terms vary a lot from one vendor to the next, so the clause in your own contract decides what you owe. The best defense is to count your own seats before the vendor counts them for you.

What is a true-up in a software contract?

A true-up is a reconciliation. You commit to a quantity, such as seats, users or devices. At set points the vendor compares that quantity with what you actually used. If usage went above the commitment, you pay for the difference.

It is different from a price increase. Your unit price may stay the same. What changes is the count of units you are billed for.

Many buyers first meet a true-up in a large enterprise agreement. But the idea shows up in smaller SaaS plans too, often under a different name such as “overage” or “reconciliation.”

How does a Microsoft Enterprise Agreement true-up work?

Microsoft’s Enterprise Agreement guidance (page read in 2026) describes the agreement as a three-year agreement with an annual true-up. The page says the true-up order “must be received by Microsoft in the period between 60 days and 30 days prior to the anniversary.” If nothing changed, it says an update statement must be submitted instead.

The page also says the reconciliation covers the qualified devices, users and processor units added or used by your organization. And it notes that adding or removing software, devices and users is available with the Enterprise Subscription Enrollment. So whether you can reduce counts depends on the type of enrollment you signed.

The practical lesson is the window. You have about 30 days between the 60-day and 30-day marks. That is not much time to find out how many seats you really use.

How does a usage-based true-up work at GitLab?

GitLab’s documentation on quarterly reconciliation (page read in 2026) shows a second model. It says that when a subscription “has more billable users than purchased seats, you are charged for the additional seats.”

GitLab describes two ways to bill that overage:

  • Quarterly reconciliation: you are billed per quarter, prorated for the rest of the term.
  • Annual true-up: you pay the full annual fee for users added at any point in the year.

GitLab’s own example uses 100 seats at $100 per extra seat, with usage peaking at 120. It shows $1,000 under quarterly billing and $2,000 under annual true-up. That example comes from GitLab’s page and is not a promise of what any vendor will charge you.

The page also says some customers are excluded from quarterly reconciliation, including those who buy through resellers or with purchase orders, and those on non-12-month terms. Those customers are reconciled annually. Whether you qualify depends on how you bought.

Why do true-ups catch teams off guard?

Four common causes:

  • Nobody owns the count. IT adds users, finance pays invoices, and no one compares the two.
  • The window is short. As the Microsoft page shows, the order is due in a narrow period before an anniversary.
  • Growth is quiet. New hires, contractors and trial accounts become billable users without a purchase request.
  • The terms are buried. The true-up rule sits in a clause or order form that nobody reread after signing.

How can you plan for a true-up?

These steps are general good practice, not a guarantee that you will avoid a charge:

  1. Find the clause. Search the contract and order forms for “true-up,” “overage,” “reconciliation” and “excess usage.” Note the date or trigger, the price per extra unit, and whether the price is the list price or your contracted price.
  2. Write down the dates. Put the reconciliation date on the same calendar as your renewal and notice dates. As a rule of thumb, start well before the window opens so you have time to act.
  3. Count your own usage. Pull the vendor’s admin report and compare it with your HR or identity list. Remove people who left.
  4. Compare buying seats with paying the overage. The GitLab page says you can reconcile overages by purchasing additional seats, and that turning on restricted access helps prevent them. Buying seats may cost less than a later charge, or it may not. Compare both.
  5. Ask about reductions. Find out whether the contract lets you lower the count at renewal, and when you must say so. The Microsoft page lists adding or removing software, devices and users as available with the Enterprise Subscription Enrollment.
  6. Keep your own record. If the vendor’s report and yours disagree, bring yours to the conversation.

What should you ask the vendor?

  • When exactly is usage measured, and who sees the report?
  • Is the extra unit price the same as my contracted price?
  • Is the charge prorated, or the full year?
  • Can I reduce the count at renewal, and what notice is needed?
  • Does the vendor offer a way to cap or restrict new users? GitLab’s page, for example, mentions a restricted-access setting that blocks adding new billable users once no seats remain.

Where Renewlark fits

Renewlark is being built to review your vendors, contracts and renewal dates, flag seats and spend worth a closer look, and keep a person in charge of approving every important action. Join the waitlist.

This article is general information about business software contracts, not legal, financial or tax advice. Check your own agreements and talk to a qualified professional about your situation.