A true-up is a periodic reconciliation where a customer reports actual software usage and pays for any licenses used beyond what was purchased.
A true-up is a periodic reconciliation built into many volume software agreements: the customer counts its actual usage - seats, users, or endpoints - reports the number to the vendor, and pays for anything consumed beyond what was originally purchased. The mechanism exists so growing companies can deploy software first and settle later, instead of stopping to buy a license every time someone is hired. Deploy freely during the year; true the numbers up at the anniversary.
How a true-up works
The classic shape is a multi-year enterprise agreement with an annual cycle:
- Baseline - at signing, the customer buys licenses for its current count of users or devices.
- Deploy freely - during the year, new hires and new machines get the software without individual purchases.
- Count and report - at the agreement anniversary, the customer counts actual usage and submits the number.
- Pay for growth - the difference between the report and the baseline is invoiced at the rates fixed in the contract, and the reported number becomes the new baseline.
What gets counted depends on the metric in the agreement: named users, devices, processor cores, or installations. Getting the metric right matters as much as getting the number right.
A worked example
A firm signs a three-year agreement covering 200 users. Over the first year it hires steadily and reaches 236 people using the software. At the anniversary it reports 236, pays for the additional 36 users at the per-user rate agreed at signing, and 236 becomes the baseline for year two. No purchase orders were needed during the year, and the vendor never had to chase individual transactions - that is the trade both sides signed up for.
True-up vs true-down
Most agreements ratchet one way. Counts go up at each true-up, but a true-down - reducing the count after layoffs or a tool migration - is usually only allowed at renewal, if at all. The practical consequence: reclaim unused seats before the count date. A leaver whose seat is still assigned on paper gets counted, paid for, and baked into next year’s baseline.
Preparing for a true-up
The annual count is only painful when the records are not live. The habits that make it routine:
- Keep one register of license assignments - who holds which seat - and update it as part of onboarding and offboarding, not as an annual archaeology project.
- Reconcile the register against HR headcount a month before the count date, while there is still time to reclaim seats.
- Watch for shadow IT installs of the same product outside the agreement - they belong in the count and are better declared than discovered.
- Apply the same discipline you would to hardware asset management: every assignment recorded at the moment it happens.
AMPthilly keeps software licenses and their seat assignments in the same register as physical equipment, with per-person checkout history and CSV export, so the annual count becomes a filtered export rather than a spreadsheet hunt.
Related terms
- Shadow IT - unapproved installs that surprise you at count time
- Endpoint - a common counting metric in device-based agreements
- MDM - device-management tooling often used to verify what is installed where
- BYOD - personal devices that complicate device-based license counts
- Hardware Asset Management - the same who-holds-what discipline applied to equipment
FAQ
Is a true-up the same as a license audit?
No. A true-up is cooperative and scheduled - you count your own usage, report it, and pay for growth at prices agreed in the contract. An audit is vendor-initiated and adversarial - the vendor or its audit firm verifies your numbers, and any shortfall is usually settled at list price. Honest, well-documented true-up reporting is the best protection against being audited in the first place.
Can a true-up reduce the license count?
Usually not mid-term. Most agreements are a one-way ratchet - the count goes up at each true-up but can only come down at renewal, and some contracts do not allow reductions at all until the full term ends. That is why reclaiming unused seats before the count date matters - any seat still assigned on paper gets reported, paid for, and locked in as the new baseline.
When does a true-up happen?
Typically once a year, on the anniversary of a multi-year volume agreement, with the report due a set number of days before or after the anniversary date. Some subscription agreements true-up monthly or quarterly instead, and consumption-based cloud agreements reconcile continuously - the annual model is the classic one from on-premises enterprise licensing.