How true-ups work
In a typical enterprise agreement you license a baseline, then deploy more as you grow. At the true-up date, you report the additional usage and pay for it, often retroactively. Microsoft Enterprise Agreements true-up on an annual cycle; Oracle, Adobe, and SAP each have their own mechanics and their own audit posture. Many teams track these dates in spreadsheets, separately from renewal dates, which is exactly how they get missed.
Why true-ups catch teams off guard
Three reasons. Usage grows incrementally, so no single moment signals that you have crossed a licensed threshold. True-up dates live apart from renewal dates, so they fall outside the renewal review. And login-based tools do not capture the real picture, because a license can be consumed without obvious activity. By the time the reconciliation lands, the exposure is already built in.
True-up rules by vendor: Microsoft EA, Adobe, Oracle, SAP, and VMware
The vendors that drive most mid-market true-up exposure each run their own true-up process, on their own schedule, with their own audit posture. The table below summarizes how each one works, and the paragraphs that follow add the detail.
| Vendor | What triggers the true-up | When it is counted | Typical cost driver | How to prepare |
|---|---|---|---|---|
| Microsoft EA | Deploying more users or devices than the licensed baseline | Annual, on the enrollment anniversary | M365 seat creep from headcount growth | Reconcile the Entra user count to the EA baseline 90 days out |
| Adobe | Named-user assignments above the VIP or ETLA count | At the anniversary, sometimes quarterly | Contractors and inactive named users still holding seats | Reclaim unused named users before the reconciliation |
| Oracle | Deployment beyond licensed processors or named users | Through a formal license review, not a fixed date | Cores, options, and packs counted more broadly than expected | Treat every deployment change as a licensing event |
| SAP | Named users and indirect or digital access above entitlement | After the annual system measurement | Third-party systems reading or writing SAP data | Map indirect access before the measurement run |
| VMware | Subscription core counts above the contracted quantity | Annual reconciliation under the Broadcom subscription | Core-based licensing across the whole cluster | Count cores per host and align to the subscription 90 days out |
Microsoft
Microsoft Enterprise Agreements true-up on an annual cycle. You report the users and devices added during the year and pay for that growth, often retroactively to when the seats were provisioned. Microsoft reviews are common and increasingly data-driven, so the number you report needs to match what your deployment data actually shows. For a step-by-step walkthrough, see our Microsoft true-up preparation guide.
Adobe
Adobe VIP and ETLA agreements reconcile named-user licenses against actual assignments, with overages typically billed at the anniversary. Because Adobe has moved most customers to named-user licensing, deployment is straightforward to measure, but license reassignment hygiene matters: an inactive named user still counts until you reclaim the seat.
Oracle
Oracle carries the heaviest audit reputation of the four. True-ups often surface through a formal license review rather than a routine annual report, and Oracle's metrics (processor cores, named users, options and management packs) are complex enough that unintentional non-compliance is common. Treat any change to an Oracle deployment as a licensing event.
SAP
SAP measures consumption through its own system tools and reconciles named users plus, increasingly, indirect or digital access. True-ups follow the annual system measurement, and indirect access (other systems touching SAP data) is the exposure most teams underestimate. SAP audits tend to be thorough and document-heavy.
VMware
Since the Broadcom acquisition, VMware has moved to subscription bundles priced by core, and the true-up reconciles the cores you are running against the subscription you committed to. Because licensing is core-based across the whole cluster rather than per virtual machine, a hardware refresh or a denser host can push you over the count without adding a single workload. Reconciliation is annual, so count cores per host and align them to the subscription well before the anniversary.
How to manage true-ups well
- Track true-up dates alongside renewals. Put them in the same view, not a separate spreadsheet, so nothing falls through the gap between the two calendars.
- Maintain a current deployed-versus-licensed position. Know where you stand against each agreement continuously, not once a year.
- Watch the high-exposure vendors. Microsoft, Oracle, Adobe, and SAP carry the most true-up and audit risk and deserve closer monitoring.
- Forecast before the date. Estimate the likely true-up cost early enough to budget for it or to act, rather than absorbing a surprise.
- Use tooling built for it. A spreadsheet does not scale across vendors and reconciliation dates. When you evaluate options, compare the best SAM tools for mid-market so the tracking runs itself.
How StackIQ helps
StackIQ tracks true-up dates alongside renewal dates in one place, so the two calendars stop competing for attention. It keeps your stack visible continuously rather than at a single annual checkpoint, and it looks beyond login events at how licenses are actually consumed, which is where true-up exposure hides. For an enterprise SAM function managing large Microsoft, Oracle, Adobe, and SAP agreements, that means seeing exposure build in time to act. For a leaner team, it means a category of surprise bills simply stops happening. Either way, value lands in days with no IT implementation. True-ups are one piece of broader SaaS spend management, which brings renewals, overlap, and pricing into a single program.