The True-Up: Where Enterprise Software Licensing Overcharges

Short answer: an enterprise software licensing audit compares what an organization pays Oracle, Microsoft and other large software vendors, in license fees, annual support and maintenance, and enterprise agreement true-ups, against what it actually deploys and uses. The overcharges cluster in four places: support and maintenance paid on unused licenses (shelfware), compounding annual support uplifts, true-up counts that only ever go up, and license compliance audit findings priced at list.

Most software spend has become subscription spend, and subscriptions are at least honest about their shape: you pay for seats, the seats are visible, and a seat nobody logs into is easy to find. The large on-premises and enterprise agreements, the Oracle databases and Microsoft enterprise agreements that sit underneath most mid-size and large organizations, do not work that way. They bill for what you were entitled to, and entitlement and usage drifted apart years ago.

That is not a pricing error anyone made. It is what happens when a contract measures the past and a business keeps changing. This guide is about where that gap turns into money, and what can be done about each piece of it.

Oracle and Microsoft support costs: the bill is support, not the license

A perpetual license is paid for once. The annual support and maintenance attached to it is paid every year, and on most enterprise agreements it is priced as a fixed percentage of what the license originally cost. After a handful of years, an organization has paid for the license several times over in support alone, and the license fee is no longer the interesting number.

Three things follow from that structure, and each is worth checking against your own invoices.

Paying support and maintenance on shelfware

Software bought for a project that ended, a system that was replaced, or an acquisition that was integrated still carries support for as long as nobody cancels it. The license itself costs nothing to keep. The support does. Build a list of every product carrying support and, next to each, the system that actually runs it today. The rows with nothing in the second column are the finding.

The annual support uplift

Support renewals typically rise every year by a contracted or customary percentage, applied to a base that already includes every previous rise. Compounded over a decade, it is the largest single contributor to enterprise software cost that nobody decided on. The mechanic is the same one described in Vendor Fee Creep, with a larger base.

Why you cannot just cancel unused licenses: the repricing trap

Here is the trap. Some vendors' support policies say that if you drop support on part of a license set, the support on what remains is repriced, often to list, because the original discount was granted on the full quantity. A business that cancels half its unused licenses can end up paying close to what it paid before, for half the software. Read the technical support policy that governs your agreement before canceling anything, because the obvious move is sometimes the expensive one.

The way through is usually not cancellation at all. It is migrating the shelfware into a different deal, retiring whole license sets rather than partial ones, or using the renewal to restructure what is covered. Those are negotiations, and they only start once someone has the list.

Microsoft enterprise agreement true-ups only go one way

Microsoft enterprise agreements, and agreements built on the same model, include an annual true-up: once a year you report how many users, devices or cores you added, and you pay for them. The model is reasonable. The asymmetry inside it is not obvious until you look.

• Additions are counted. Reductions usually are not. Within an agreement term, the count you true up to is the count you keep paying for. A headcount that rose in year one and fell in year two is billed at the year one peak until the next renewal.
• The count is often an estimate. True-up figures are frequently pulled from a directory or an inventory tool and rounded up for safety. Disabled accounts, service accounts, test machines and devices that left the building all inflate it.
• The wrong edition is the expensive mistake. Licensing everyone at the top suite tier because a few people need its features is common, and the difference between editions is large per user.

The fix is a reconciliation done before the true-up is submitted, not after the invoice arrives: active users and devices from the systems that actually authenticate them, matched against what is about to be declared.

Unused enterprise agreement benefits you already paid for

Enterprise agreements bundle entitlements alongside the licenses: upgrade rights, training days, deployment planning services, support incidents, cloud credits and the right to move licenses between environments. They are priced into the agreement whether or not anyone uses them, and many of them expire at the end of each year.

Nobody bills you for an unused benefit, so this is not a fee to dispute. It is value already purchased and left on the table, and it belongs in the renewal conversation because it is evidence the bundle is larger than the organization needs.

An Oracle or Microsoft license compliance audit is also a pricing event

Large vendors reserve the right to audit how their software is deployed, and they exercise it. An audit that finds a shortfall ends in a bill, and the bill is calculated at list price unless something is negotiated.

Virtualization is where most of the surprises come from. Some licensing rules count the entire physical host or cluster that a virtual machine could run on, not the machine itself, so a single database placed in a large shared cluster can produce a licensing requirement many times what anyone expected. Disaster recovery copies, development environments and cloud deployments each have their own rules and their own ways of being counted twice or not at all.

The defense is the same document that powers every other finding in this guide: an accurate inventory of what is deployed where, reconciled against what is owned, kept current rather than assembled in a panic once the audit letter arrives.

How to run a software license audit

Start with paper, not systems. Collect the order documents, the master agreement, the support renewals for the last several years and the most recent true-up. From those, build one table: every product, the quantity owned, the support paid on it this year, and the year-over-year change in that support.

Then add one column from the operational side: what each line is actually used for today. That column is where the findings are, and it is the one only your own organization can fill in.

Enterprise software licensing, including Oracle and Microsoft, is one of the categories AIME audits. It reads the invoices and renewals in whatever format they arrive, lays every line out next to its history and its contracted terms, and keeps watching after the first pass, so an uplift or a support line that should have ended is caught at the next renewal rather than the one after. As with every AIME engagement, there is no switching vendors and no integration, and if nothing is found there is no fee. You can run an audit here.

Frequently asked questions

What is shelfware?

Shelfware is software an organization owns and still pays support or subscription fees on but no longer runs, or never deployed. On perpetual licenses it costs nothing to keep the license and a recurring percentage every year to keep the support, which is why it is the first thing a software license audit looks for.

How often should software licensing be audited?

At minimum before every support renewal and before every enterprise agreement true-up, because those are the two dates when the numbers are set for the next year. Continuous monitoring catches uplifts and expired benefits between those dates; see why a fee audit has to be a subscription.

Will raising this with the vendor trigger a compliance audit?

Asking for a support reduction does not create an audit right that did not already exist; the agreement already grants one. What helps is entering any conversation with an accurate inventory, so that whichever direction the discussion goes, your numbers are the ones on the table.

Is third-party support an option?

For some products, independent support providers maintain software at a lower cost than the original vendor. It can be a real saving on stable systems, and it comes with trade-offs: you typically give up updates and new versions, and some vendors restrict returning to their own support later. It is a decision for IT and legal together, not a billing fix.

Does this apply to cloud subscriptions from the same vendors?

Partly. Cloud agreements still carry committed spend, annual escalators and unused entitlements, but usage is metered and visible in a way perpetual licensing never was. The audit questions shift from what you own to what you committed to and did not consume.