The short answer
A true-up is a periodic reconciliation between the number of software licenses your organization has paid for and the number it is actually using. If usage has grown beyond what the contract covers, you owe the vendor for the additional licenses at the rate locked into your agreement.
True-ups are most common in enterprise agreements with Microsoft, Adobe, Oracle, and SAP, where contracts are signed assuming a baseline license count and usage is reconciled quarterly or annually.
The key difference from a renewal: you cannot negotiate the rate during a true-up. The rate was set when the contract was signed. You are simply paying for what you used.
Why true-ups matter for mid-market companies
For mid-market companies (roughly 200 to 5,000 employees), true-ups are often the largest unexpected line item of the year. The reasons:
- Headcount grows faster than anyone updates the license count. New hires get provisioned into systems, but nobody adjusts the contract baseline until the true-up lands.
- Mergers and acquisitions add users overnight. An acquisition can double your Microsoft 365 seat count before the IT team even knows it happened.
- Shadow provisioning. Department leads spin up new seats without going through procurement. Perfectly rational for the business, invisible to the contract.
- Nobody owns the number. The person who signed the contract may have left the company. The auto-renewal notification goes to an inbox nobody checks.
The result: a true-up bill that arrives as a surprise, with no negotiation leverage and no budget allocated.
True-up vs. renewal: what is the difference?
| True-up | Renewal | |
|---|---|---|
| When it happens | During the contract term (quarterly or annually) | At the end of the contract term |
| What you are paying for | Additional usage beyond the contract baseline | The next contract period |
| Can you negotiate the rate? | No, the rate is locked in | Yes, this is your negotiation window |
| Can you reduce usage? | Not retroactively; you owe for what was used | Yes, you can right-size at renewal |
| Leverage | Very little; you owe the delta | Full leverage; you can switch vendors |
The distinction matters because asset management teams often focus all their energy on renewals and treat true-ups as an accounting exercise. In reality, true-ups represent the same or greater financial exposure, especially for Microsoft Enterprise Agreements where seat creep compounds over 12 months.
The four vendors that drive most mid-market true-up exposure
Microsoft
The most common and most expensive mid-market true-up. Microsoft Enterprise Agreement (EA) true-ups reconcile your M365, Azure, and Windows Server usage against the original commitment. If your company added 50 employees since the last count, you owe for 50 E3 or E5 licenses at the locked-in rate.
Common trap: Microsoft Entra (Azure AD) shows the real seat count, but nobody compares it to the EA baseline until the true-up notice arrives.
Adobe
VIP and ETLA (Enterprise Term License Agreement) true-ups for Creative Cloud, Acrobat, and Document Cloud. Often quarterly, depending on the agreement structure.
Common trap: Marketing teams add freelancers and contractors to Creative Cloud seats without procurement visibility. The true-up bill reflects contractors who may have already finished their engagement.
Oracle
ULA (Unlimited License Agreement) true-ups are uniquely painful because Oracle audits the deployment to determine usage, and the definition of "deployment" is broader than most companies expect.
Common trap: Running Oracle on VMware can trigger licensing obligations for every physical host in the cluster, not just the VMs running Oracle.
SAP
Indirect access true-ups for SAP are triggered when third-party systems (CRM, e-commerce, middleware) read or write SAP data. The named user reconciliation can catch organizations that have more SAP-touching users than they licensed.
Common trap: A new integration between Salesforce and SAP can create indirect access obligations for every Salesforce user who triggers a data exchange.
How to prepare for a true-up (the 90-day approach)
The difference between a painful true-up and a manageable one is knowing it is coming 90 days out. Inside that window, you can:
- Audit your actual seat count against the contract baseline. Compare your SSO/identity provider user list to the license count in the agreement.
- Identify seat creep sources. Which departments added users? Were any added for contractors who have since left? Can any seats be deprovisioned before the reconciliation date?
- Calculate the financial exposure. Multiply the delta by the per-seat rate in the contract. This is the number your CFO needs to see before it lands as an invoice.
- Coordinate with the vendor account team. In some cases, you can negotiate a partial credit for seats that were provisioned but never actively used. This is not guaranteed, but it is more likely if you surface the conversation proactively.
- Budget for it. If the true-up is unavoidable, getting it into the forecast early prevents the surprise and the scramble.
The connection between true-ups and renewals
Smart asset management teams treat true-ups and renewals as two events on the same calendar. Here is why:
- True-up data informs your renewal negotiation. If your true-up shows 20% seat creep, that tells you something about your growth rate that should factor into the renewal commitment.
- Cleaning up before the true-up reduces the renewal baseline. If you deprovision 50 unused seats before the true-up, those seats do not carry into the renewal baseline.
- The vendor knows your true-up number. When you walk into a renewal negotiation, the vendor has already seen your usage data. Knowing your own number before they present it gives you leverage.
This is why platforms like StackIQ track both on the same 90-day calendar with overlap and utilization context attached. The true-up and the renewal are not separate workflows; they are two views of the same financial relationship.
Key takeaways
- A true-up reconciles actual usage against your contract baseline. You pay for the delta at a rate you cannot negotiate.
- Microsoft, Adobe, Oracle, and SAP drive the majority of mid-market true-up exposure.
- The biggest risk is not the true-up itself; it is the surprise. Knowing the number 90 days out changes the conversation entirely.
- True-ups and renewals should be managed on the same calendar because the data from one directly informs the other.
If your team is managing true-ups in spreadsheets or finding out about them when the invoice arrives, there is a better way. See how StackIQ tracks renewals and true-ups on one calendar.