True-Up

What is True-Up?

A true-up is a periodic reconciliation, often annual, in which a customer reports actual software or service usage and pays for any growth beyond what was originally purchased.

Updated November 2026 · 5 min read


A true-up is the point in a contract when estimated usage is compared with actual usage and the difference is settled. In software licensing, it most often refers to the annual process in enterprise agreements where a customer counts the users, devices or processors it is actually using, compares that count with what it has paid for and buys licenses for any increase. The term is also used more broadly for any adjustment that brings estimated figures into line with actual ones, such as in budgeting or chargeback.

True-ups matter because they can produce large, unplanned costs if usage has grown without being tracked. They also create an opportunity: organizations that know their usage well can plan true-ups in advance, negotiate favorable terms and avoid paying for more than they need. For IT financial management, managing true-ups well is a practical test of how well an organization knows its software estate.

Definition of True-Up

A true-up is a contractual reconciliation in which a customer declares its actual consumption of licensed software or services for a period and pays for any consumption above its existing entitlement. True-ups usually occur annually on the anniversary of an agreement, although some contracts require them quarterly or at the end of the term.

True-up provisions allow organizations to add users or deploy software during the year without buying licenses at the moment of each change. Instead, growth is counted and paid for at the next true-up, often at the prices agreed in the original contract.

How True-Ups Work

Before the true-up date, the customer counts its usage under the license metric, such as named users, devices or processor cores. It compares this count with its current entitlement. If usage is higher, the customer orders additional licenses to cover the difference, usually paying for them as if they had been added partway through the year or, in some contracts, for the full year.

Many agreements only allow usage to go up at a true-up, not down. Reductions may only be possible at the end of the agreement term, which means overestimating at a true-up locks in higher costs for the remainder of the term.

True-Downs

Some agreements allow true-downs, where the customer can reduce its licensed quantity at an anniversary if usage has fallen. True-down rights are valuable for organizations whose headcount or usage may decline, but publishers often restrict them or charge more for agreements that include them.

Negotiating true-down rights, or at least flexibility to reduce at renewal, is an important consideration when entering multi-year agreements.

Importance of True-Ups in IT Financial Management

True-ups can create significant costs, and they often fall due at times that do not match budget cycles. Knowing what is coming, and how much, is essential for accurate budgeting.

They also reveal how well an organization tracks its software usage.

A surprising true-up is usually a sign that license tracking is not keeping pace with the organization's growth.

Budget Impact

Organizations that grow during the year, through hiring, acquisitions or new deployments, can face large true-up bills. If these are not anticipated, they create unfavorable budget variance and may require emergency funding.

Forecasting true-ups from headcount plans, deployment plans and current usage trends allows the cost to be budgeted in advance. It also gives time to decide whether growth should be covered by the existing agreement or by other options. Including expected true-ups in the IT budget at the start of the year avoids the need to find money mid-year.

Compliance and Cost Control

The true-up is the customer's declaration of usage, and it may be checked later through an audit. Under-declaring creates compliance risk, while over-declaring wastes money and may lock in costs for the rest of the agreement.

An accurate count, based on reliable data, protects against both. Documenting how the count was produced also helps if the declaration is later questioned in an audit. It also gives the organization a clear picture of where usage is growing, which may reveal opportunities to reharvest unused licenses before the true-up date.

How to Manage True-Ups

Managing true-ups well involves tracking usage throughout the year, preparing early and taking action to reduce unnecessary usage before counting.

The work is shared between IT, procurement and finance, since each holds part of the information needed. True-up management is a core activity of software license management.

Tracking and Preparing

Usage should be tracked continuously, not just at true-up time. Discovery tools, identity systems and admin consoles provide counts of users, devices and installations. Comparing these regularly with entitlements shows how the true-up position is developing.

Preparation should begin two to three months before the true-up date. This allows time to validate counts, investigate anomalies, remove unnecessary installations and confirm the figures with the publisher's definitions of the license metric.

Reducing Before Counting

Before declaring usage, organizations should remove licenses assigned to people who have left, uninstall software that is not being used and reassign spare licenses. Every license removed before the count avoids a cost that may continue for the rest of the agreement. This is often the single most valuable step in true-up preparation.

Organizations should also consider whether growth is best covered by the true-up or by alternatives, such as moving some users to different products or editions. Planning these choices alongside contract renewal strategy gives the most flexibility.

Examples of True-Ups in IT Financial Management

The examples below show how true-ups affect technology costs.

Both use illustrative figures from the same company in consecutive years.

In each, preparation before the count made a significant difference to the outcome.

An Unplanned True-Up

A company's enterprise agreement covers 8,000 users of a productivity suite at $400 per user per year. During the year, it acquires another business and grows to 9,500 users, but does not track the change.

At the true-up, it must pay for 1,500 additional users. Because its contract charges new users at half the annual price for the year in which they are added, the true-up costs $300,000, and the following year's cost rises by $600,000. Neither amount was in the budget, and the IT team had to find savings elsewhere to cover it.

A Prepared True-Up

The next year, the company tracks usage monthly. Three months before the true-up, it finds 9,900 assigned licenses but only 9,300 active employees. It removes 450 licenses from former employees and service accounts that do not need them.

Its declared count is 9,450 rather than 9,900, avoiding $90,000 in true-up charges and $180,000 a year in ongoing costs. The forecast it built from headcount plans had already put the true-up in the budget. The remaining 150 licenses above the employee count cover contractors and shared accounts that genuinely need access.

Conclusion

A true-up is a periodic reconciliation in which a customer declares actual usage and pays for growth beyond its entitlement, most often annually under enterprise software agreements. Some agreements also allow true-downs when usage falls.

In IT financial management, true-ups can create large, unplanned costs if usage is not tracked, and can lock in unnecessary costs if usage is overstated. Tracking usage continuously, preparing early, removing unneeded licenses before counting and forecasting true-ups in the budget help organizations control these costs.