A software license true-up is a contractual reconciliation process that compares existing license entitlements with the quantities required under an agreement’s licensing rules. It identifies additional licenses or charges due for a defined period, using verified records, agreed pricing, and the applicable reporting requirements.
The practical question is: Do the licenses you have cover the users, devices, deployments, or consumption your contract requires you to license?
True-up in accounting and finance. Outside software licensing, a true-up is any adjustment that brings an estimate or provisional amount into line with the actual figure, such as accrued expenses, sales commissions, or insurance premiums. This page covers software license true-ups.
Why do software agreements include true-ups?
An organization’s software requirements can change during a contract. New employees join, additional systems are deployed, or teams adopt more services.
Some agreements permit eligible additions to be reconciled at scheduled intervals instead of requiring a separate purchase for every change. This flexibility applies only within the agreement’s rules.
For example, Microsoft describes its Enterprise Agreement true-up as an annual reconciliation of eligible additions. Its guidance specifies an order submission window of 30–60 days before the enrollment anniversary, and the final year of the agreement follows a different window. That is a program-specific requirement, not a universal true-up deadline. Microsoft Enterprise Agreement guidance
The relevant measure comes from the contract. It may involve named users, qualified devices, processor cores, deployments, or another defined unit.
Active usage and licensing requirements are not always the same. A person who rarely logs in may still require a license under the applicable rules. Conversely, multiple activity records do not necessarily represent multiple licensable users.
Microsoft’s guidance, for example, defines “Qualified Users” and “Qualified Devices” for applicable licensing arrangements. Those definitions matter when establishing the required count. Microsoft licensing definitions
A reliable reconciliation therefore connects three things:
The following fictional clause illustrates a simple named-user arrangement. It is not a vendor’s standard provision or a ready-to-use legal template.
The Customer may provision additional named-user licenses during the annual subscription term and shall report those additions within 15 days after each quarter-end. Additional licenses will be charged at USD 30 per license per month, from the first day of the month in which they are provisioned through the end of the subscription term. Each reported addition becomes committed through term-end. Reductions require a separate agreement or a permitted renewal adjustment.
This example establishes the reporting schedule, price, charging period, and treatment of reductions.
Actual agreements may use different measurement dates, pricing methods, reservation processes, or minimum commitments. Do not assume this example applies to a particular supplier.
How a true-up calculation works
Assume a company has 100 purchased licenses. It provisions 20 additional licenses on July 1 for a term ending December 31.
Under the fictional clause, the additions are chargeable for six months:
Calculation
Illustrative result
Existing licenses
100
Verified requirement after additions
120
Additional licenses
20
Monthly price per additional license
USD 30
Chargeable period
6 months
Additional charge
USD 3,600
20 × USD 30 × 6 months = USD 3,600
This calculation assumes the original 100 licenses are already paid for and no other adjustments apply. It uses the example’s explicit monthly charging rule; proration is not universal.
How true-ups can leak value
The count is wrong. Duplicate records, incorrect product mappings, or entities outside the agreement’s scope can distort the assessment.
Previously purchased licenses are missed. Incomplete entitlement records may cause the team to purchase coverage it already holds.
The wrong rate is applied. A reconciliation uses list prices instead of the applicable negotiated schedule, overlooks an amendment, or applies a renewal price increase before it takes effect.
Dates are inaccurate. Incorrect provisioning dates or charging periods can change the amount owed where the agreement makes them relevant.
Low activity is mistaken for a reduction right. Removing an account does not necessarily eliminate a commitment or a charge already incurred.
The team starts too late. An approaching deadline leaves insufficient time to validate quantities, resolve discrepancies, and approve the order.
The goal is an accurate obligation, not the lowest count a dashboard can display.
How to monitor a software license true-up
Start well before the contractual reporting window and keep an evidence trail. For large agreements, gathering and validating records can take several months.
What to check
Evidence to retain
Licensing rules
Applicable agreement, product terms, enrollment, and amendments.
Existing entitlements
Purchase records, license statements, and earlier reconciliations.
Required quantities
Validated user, device, deployment, or consumption records.
Relevant dates
Addition history, measurement periods, and reporting deadlines.
Pricing
Negotiated rates, discounts, and charging rules.
Final reconciliation
Approved calculation, submitted order, invoice, and updated entitlement record.
Software asset managers often call the result an effective license position (ELP): a reconciliation of what you are entitled to use against what is deployed or required.
IT or software asset management should validate the technical records. Procurement should confirm the commercial terms, and finance should check charges and approvals. Escalate ambiguous licensing interpretations before submission.
After reconciliation, update the baseline so the next review does not count the same additions again.
True-up vs. true-down vs. renewal
A true-up reconciles additional licensing requirements under the agreement.
A true-down reduces licensed quantities or commitments where the contract permits it. A true-up process does not automatically provide that right.
A renewal continues the agreement into another term. It may provide an opportunity to revise quantities, but notice periods, minimum commitments, and program rules still apply.
Keep these events separate in the contract calendar, even when they occur near the same anniversary.
Where does ObligaAI fit?
A true-up review starts with understanding the relevant agreement: what is licensed, how additions are treated, and which commitments apply.
ObligaAI’s published use cases include software licensing, contract expiry and renewal tracking, and contract storage with source-referenced Q&A. These are relevant starting points for reviewing licensing terms.
Verified operational records are also essential. Contract documents alone cannot establish actual deployment or usage, and a contract answer does not replace a complete licensing reconciliation.
Is a software license true-up the same as an audit?
No. A true-up is a reconciliation process defined by the agreement. An audit is a separate verification of software license compliance under applicable audit rights. Completing a true-up does not necessarily prevent an audit.
Does every software agreement require an annual true-up?
No. Some arrangements use other reporting intervals or require purchases before additional deployment. Check the agreement’s specific process.
Can unused licenses offset additional requirements?
Only where the licensing rules permit it. Product, edition, assignment, transfer, and timing restrictions may prevent an apparent spare license from covering another requirement.
Can a true-up reduce my software bill?
Do not assume so. Reductions depend on the agreement’s true-down, renewal, or other adjustment provisions. Identifying unused licenses (shelfware) can inform a future decision without changing an existing payment obligation.
Can true-up terms be negotiated?
Usually at renewal or when a new agreement is signed, rather than mid-term. Terms worth reviewing include whether additions are priced at the negotiated rate, any grace threshold before a true-up applies, caps on true-up charges, and whether a true-down is permitted.
Related terms: License entitlement · Software license true-down · Effective license position · Software license audit · Minimum commitment · Contract renewal · Rate card · Audit rights clause
General business information. Licensing obligations depend on the applicable agreement and product terms.