Join our Newsletter — 33% off our NHI Course
Governance, Ownership & Risk

True Up

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Governance, Ownership & Risk

A true up is an agreement record for licenses or services added after the original contract was signed. It captures mid-term expansion separately from the base agreement, which preserves auditability and gives renewal teams a clearer view of how demand changed over the contract lifecycle.

What a true up record does

A true up is not the original contract itself, but an add-on record that captures changes in scope after signature. It gives procurement, finance, and vendor management a separate place to record incremental licenses or services so the base agreement stays intact while the commercial history stays traceable.

Why true ups matter in contract and license management

True ups matter because mid-term growth is easy to misstate if it is folded into the base deal or handled only in email threads. A separate record helps preserve an auditable chain from the initial purchase through later expansion, which is especially important when renewal pricing, usage commitments, or entitlement counts need to be reconciled later.

They also reduce ambiguity around what was bought when. That clarity matters for internal chargeback, forecast accuracy, supplier reconciliation, and disputes about whether additional capacity was authorised as a formal contract change or only as a temporary exception.

How a true up changes the commercial lifecycle

In practice, a true up acts as the bridge between the signed baseline and the evolving reality of consumption. It records expansion separately from the original order form or master agreement, so the contract lifecycle shows both the starting point and the delta that followed.

That separation is useful when the organisation is managing recurring licenses, subscription counts, or service volumes. It helps teams see how demand changed over time, which can inform future sizing, renewal negotiation, and internal approval workflows.

Where true ups are commonly used

True ups are most common where entitlement is expected to change during the term of the agreement. Software licensing, cloud subscriptions, managed services, and other usage-linked contracts often need a mid-cycle record when usage rises above the originally contracted level.

They are less about security control than about clean administration, but the administrative quality still matters. If the record is incomplete or informal, organisations can lose visibility into what was actually approved, consumed, and owed at renewal.

For governance-heavy environments, the distinction between the base deal and later expansion can also support NIST Cybersecurity Framework 2.0 style asset and risk visibility, because contract records often need to align with the services and licenses actually in use.

When the subject touches access to platforms, tools, or services, the record should also support control expectations reflected in NIST SP 800-53 Rev 5 Security and Privacy Controls, especially where entitlement growth affects authorisation, account review, or audit evidence.

Risk and Threat Considerations

A weak true up process can hide shadow expansion, make renewal disputes harder to resolve, and leave organisations unable to prove what was approved versus what was merely used. In contract-heavy environments, that gap can become a financial, audit, and governance problem even when the underlying service is legitimate.

Failure mechanism: Mid-term additions are recorded inconsistently, merged into the base contract, or left undocumented, so the organisation loses a reliable record of entitlement growth and cannot reconcile actual consumption against authorised terms.

Impact: Renewal pricing can be misstated, overuse may go unnoticed until late in the cycle, and audit trails can fail to show how the agreement changed over time.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0ID.AM-01 — Physical devices and systems within the organization are inventoriedTrue ups depend on knowing what assets and services have expanded over time.
Recommendation — Maintain an accurate inventory so contract expansions can be reconciled to actual services and licenses.
NIST SP 800-53 Rev 5AU-10 — Non-repudiationA true up creates a traceable record of contract change that supports later dispute resolution.
Recommendation — Preserve change evidence so additions to agreements remain attributable and auditable.
ISO/IEC 27001:2022A.5.9 — Inventory of information and other associated assetsAgreement changes often track the assets, services, or licenses being governed.
Recommendation — Tie commercial records to the underlying asset inventory that drove the expansion.

Practitioner Guidance

Why practitioners should care: A true up should be treated as a controlled commercial record, not as a clerical afterthought. If it is not linked cleanly to the original agreement and the corresponding change approval, downstream teams may inherit an incomplete version of the contract history.

Governance implication: Keep the base agreement, the add-on record, and the renewal view aligned so that procurement, finance, and service owners are all working from the same lifecycle evidence. That makes later reconciliation much easier and reduces disputes over what was authorised.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org