Why this matters
The work behind How to prepare for a software license true-up starts with one rule: own your numbers before the vendor asks for them. A true-up is a scheduled reconciliation of what you own against what you use. It often lands at contract renewal, after a merger, or when a vendor asks for a deployment report. The bill can include back maintenance, new licenses, and a move to a higher tier. The vendor works from the contract metric, not from your rough sense of headcount.
Prepare early so the number you give the vendor is yours. Build an effective license position, often shortened to ELP. That is a table with entitlement on one side, deployment and usage on the other, and the gap in the middle. If you cannot explain a gap, you cannot defend it. The same work makes renewal quotes cleaner and gives finance a number it can plan around.
Before you start
Pick one owner. That person runs the calendar, chases evidence, and speaks to the vendor. Include procurement, finance, and the technical teams that run servers, endpoints, and cloud accounts. Write down the true-up date, any notice window in the contract, and the date you want your internal baseline finished. Aim to finish the baseline two to four weeks before the vendor meeting.
Collect paper before you touch tools. Pull the master agreement, order forms, entitlement certificates, renewal quotes, reseller invoices, and any volume license or cloud subscription records. Note the license metric for each product: per user, per device, per core, per processor, per server, or named user. Note the rules for virtual machines, disaster recovery, test and development, and subsidiaries. Those rules decide whether a server counts once or many times.
Set a scope boundary. List legal entities, sites, data centers, and cloud accounts in play. Include home offices and contractor access only if the contract says so. Open a shared evidence folder with read-only copies of exports, screenshots, and contract clauses. Keep the raw files. A screenshot is weak if you cannot say when it was taken and what it covers.
How to do it
Run the work in two passes. First count from paper and tools. Then walk every gap with the owner of that system. Keep one register with columns for product, metric, entitlement, deployment, gap, owner, evidence, and next action. A flat spreadsheet works if the links are consistent. A database or a software asset management tool works better when you have many products.
Freeze a count date. A user list pulled on Monday and a server report pulled on Friday will not reconcile. Do not wait for a perfect count. A clean first pass with named gaps is stronger than a late spreadsheet with no owners. The steps below are the order that keeps the work honest.
- Read the contract and lock the metric. Pull the master agreement, order form, and product terms. Write one sentence per product that states how the vendor counts it, such as per named user, per core, or per device. Mark clauses on virtual machines, disaster recovery, and test environments.
- Build an entitlement register. List every purchase, renewal, and transferred license with date, quantity, contract number, and reseller. Keep the source file next to each line. Mark expired or retired entitlements so nobody counts them twice.
- Discover deployments with tools and exports. Pull user lists from Active Directory, the Microsoft 365 admin center, Adobe Admin Console, and other admin consoles. Pull server inventories from vSphere Client, hypervisor reports, and SQL Server inventory queries. Run network discovery for the rest, then check the output against purchase records.
- Normalize counts by the contract metric. Convert users, devices, cores, and instances into the unit the vendor uses. Group production, test, disaster recovery, and sandbox separately. Add virtual hosts and clustered nodes if the contract counts physical cores or processors.
- Build the effective license position. Put entitlement and deployment side by side for each product. Flag each gap as under-licensed, over-licensed, or unclear. Add the owner, evidence link, and next action for every unclear line.
- Close easy gaps before the meeting. Remove unused accounts, reassign licenses, and retire software you no longer need. Keep a dated record of each change. Do not uninstall software or delete evidence just to change the count.
- Prepare the evidence pack and the readout. Make a short deck and a spreadsheet that show scope, method, entitlement, deployment, and open questions. Bring contract clauses for any rule you rely on. Agree who speaks in the meeting and who takes notes.
- Agree remediation and update the renewal plan. Ask the vendor or reseller to confirm each gap in writing. Decide what to buy, what to remove, and what to renegotiate. Put the dates and owners into the renewal calendar so the next true-up is smaller.
How to check it worked
Run a second count from a fresh export after you close the easy gaps. Compare the new numbers to the baseline and explain every change. If a gap closed because you uninstalled software, keep the removal record. If a gap closed because you bought licenses, keep the order form.
Tie the register back to finance. The entitlement quantities should match invoices and the general ledger or subscription records. Ask the vendor or reseller to confirm the contract metric in writing for each product you are unsure about. A short email is enough.
Run a mock vendor call. Have someone outside the project ask the questions a vendor would ask: which entities are in scope, how did you count virtual hosts, where is the evidence for this user list. Fix the weak answers before the real meeting.
Mistakes to avoid
Do not treat the true-up as an IT chore. Finance, procurement, and the system owners each hold part of the proof. A count without invoices is hard to defend. A contract review without deployment data is just paper.
Do not count installs when the contract counts users, or count users when it counts cores. Read the metric for each product. Watch virtual hosts, clusters, disaster recovery, and test environments. Those are common places where a small physical footprint turns into a large license gap.
Do not delete software, users, or evidence to lower the number. Normal cleanup is fine when it is dated and documented. A sudden drop in usage after the vendor notice invites questions. Build the renewal calendar and check it each quarter.
If your device and license records are thin, the Cloudverg Hardware and endpoint review at $4,500 fixed price is one option among others to build a clean inventory before the true-up. It covers endpoints, servers, network gear, and licenses, and it ends with a written report and a readout. It is not a substitute for contract review, but it gives you a stronger base.
Frequently asked questions
What is a software license true-up?
A true-up is a reconciliation between the licenses you own and the software you actually use. It is usually tied to a contract date or a vendor request. The result is a bill, a credit, or a confirmed position, depending on the gap.
When should we start preparing for a true-up?
Start at least four to six weeks before the contract date or vendor meeting. That gives you time to pull contracts, run discovery, and explain gaps to the system owners. If the vendor has already asked for data, start the same day.
Can we remove unused software before a true-up?
Yes, if removal is normal housekeeping and you document it. Uninstall unused copies, remove stale user accounts, and reassign licenses. Do not delete evidence or wipe systems after a vendor notice just to change the count.