Software true-up audits: the annual bill nobody checks

Executive Summary

A software true-up is the annual reconciliation invoice a vendor sends when actual usage exceeds a licensed baseline. Most companies route it straight to accounts payable because it looks like a routine renewal, not a bill that needs matching against a contract. That is the mechanism: a true-up invoice states a usage count and a rate, but rarely shows its own math, and the agreement that defines what counts as a "user" or an "instance" usually sits in a separate order form nobody pulls before paying.

The fix is not a new tool. It is treating the true-up invoice the same way a rate card or a labor timesheet gets treated elsewhere in indirect spend: pull the governing agreement, recompute the usage count against the contract's own definitions, and check the unit rate against the tier the contract actually specifies. This is invoice-to-contract matching applied to a category that AP teams tend to wave through because the vendor relationship feels settled.

The rest of this guide walks through where true-up drift actually enters the number, what to request before approving one, and how this category sits inside a broader review of indirect spend.

1. What is a software true-up and why does the invoice go unchecked?

A software true-up is the annual bill a vendor issues to reconcile licensed volume against actual usage, typically new seats, added instances, or consumption above a contracted tier. It goes unchecked because it arrives as a single summary figure, not a line-by-line invoice, and the underlying usage count is calculated entirely on the vendor's side with no independent count to compare it against.

A standard software agreement licenses a baseline: a seat count, a server instance count, or a consumption tier. Usage that exceeds the baseline during the contract year gets billed at renewal, in one lump figure labeled "true-up" or "reconciliation."

The invoice format is the first problem. Where a freight or maintenance invoice itemizes charges against a service performed, a true-up invoice states a number: additional users, additional instances, a rate, and a total. There is no line for the AP team to check against a purchase order, because there was no purchase order for growth that had not happened yet at signing.

The second problem is who counts. The vendor's own usage metering produces the number that becomes the bill. Unless someone on the buyer's side maintains an independent count of provisioned seats or active instances, there is nothing to compare the invoice against except the invoice itself.

This is why true-ups get paid on arrival more often than other indirect spend categories: the invoice looks final rather than negotiable, and nobody on the finance side owns a competing number. The agreement itself, not the vendor's summary, is the only reliable source for what should have been billed.

2. How does a true-up invoice drift from the license agreement behind it?

Drift enters a true-up through three mechanisms: counting the wrong population as a licensed user, applying a rate from an outdated price list instead of the contracted tier, and billing consumption that a deprovisioning step should have already removed. Each of these produces a number that looks internally consistent while contradicting the agreement it is supposed to reconcile.

The agreement defines what counts as a billable unit, and that definition rarely matches what a usage report counts.

A. Definition mismatch. A contract may define a "named user" as someone actively assigned a license, while the vendor's usage report counts every account ever provisioned, including accounts for employees who left the company. The invoice bills the larger number.

B. Stale rate application. Multi-year agreements often set true-up pricing at the same per-unit rate as the original order, sometimes with a cap or a volume-tier discount that applies once usage crosses a threshold. A true-up invoice generated from the vendor's current price list, rather than the contracted rate schedule, can bill above what the agreement allows.

C. Deprovisioning lag. When a company reduces headcount or retires a system, the license reduction has to be actioned, either automatically or through a change request. If nobody submitted that request, the vendor's usage count keeps billing seats that should have been removed months earlier.

Each mechanism produces an invoice that is internally coherent. The number adds up correctly against the vendor's own data. It just does not match what the contract obligates the buyer to pay, which is the only test that actually matters.

3. Where do true-up numbers actually come from, and who checks them?

A true-up figure originates from the vendor's usage telemetry or license management console, gets summarized into a renewal invoice, and typically passes through procurement or IT for budget approval before AP pays it. None of those steps routinely re-derives the number from the governing contract, so the vendor's count becomes the count of record by default.

The path a true-up takes before payment usually runs: vendor telemetry produces a usage figure, a renewal or account manager packages it into an invoice, procurement or the IT budget owner reviews it for cost against last year's spend, and AP releases payment once it is approved.

Each checkpoint asks a different question than the one that matters. Procurement typically checks whether the total is within budget range. IT typically checks whether the tool is still in use. Neither step recomputes the licensed population against the contract's own definition of a billable unit, and neither pulls the rate schedule to confirm the per-unit price matches what was negotiated.

The contract itself, not the vendor's usage dashboard, is the reference document. A true-up audit means retrieving the order form and any amendments, extracting the definition of a licensed unit and the applicable rate schedule, and rebuilding the invoice's arithmetic from those terms rather than accepting the vendor's summary total.

This is the same invoice-to-contract matching discipline applied elsewhere across indirect spend audit categories, just directed at a category that usually skips it because the bill looks administrative rather than negotiated.

4. What should you check before you approve a true-up invoice?

Before approving a true-up, pull the governing order form and amendments, independently count active licensed units from your own system of record, confirm the billed rate against the contracted price schedule, and request the vendor's line-level usage detail rather than accepting a single summary total. Each check targets one of the specific drift mechanisms described above.

None of these checks require special tooling. They require pulling the contract before the invoice gets coded for payment, which is the step that most commonly gets skipped because the renewal deadline creates pressure to approve quickly.

A true-up that fails any of these checks is not automatically wrong. It is unverified, and an unverified renewal invoice at this size deserves the same scrutiny a maintenance work order or a staffing timesheet gets elsewhere in indirect spend.

1. Pull the governing contract: Locate the current order form and every amendment, not just the original signature document. Rate schedules and unit definitions are frequently updated by amendment.
2. Count independently: Generate your own count of active users, provisioned instances, or consumption from your internal system before comparing it to the vendor's figure.
3. Match the rate to the tier: Confirm the per-unit rate applied matches the tier the contract specifies at your current volume, not the vendor's published list price.
4. Request line-level detail: Ask for the usage report behind the summary total. A vendor unwilling to provide it is asking you to accept a number you cannot verify.
5. Check deprovisioning timing: Confirm license reductions requested during the year were actually applied on the date requested, not the date the vendor processed the change.

5. Can a true-up invoice include charges you never actually owed?

Yes. A true-up can include units counted under the wrong definition, a rate pulled from the vendor's current price list instead of the contracted schedule, or consumption tied to accounts that should have been deprovisioned. None of these require bad faith on the vendor's side. They are the predictable result of a reconciliation process built on the vendor's own metering with no independent check.

The distinction that matters here is between an error and a dispute. A definitional mismatch, where the vendor counts inactive accounts as licensed users, is a factual error the contract language resolves directly once someone reads it. A rate discrepancy is usually a straightforward correction once the contracted schedule is produced.

Where a company chooses to raise these findings with a vendor, and any dispute over contract interpretation, is a commercial and potentially legal matter. This guide describes what to check in the invoice; it is general information, not legal advice, and any contested interpretation of contract language should go through appropriate legal review.

What an audit contributes is the finding itself: a specific line, a specific contract clause, and the gap between what was billed and what the clause supports. That finding is what makes a correction request credible rather than a generic pushback on cost.

6. How does a true-up audit fit into a broader indirect spend review?

Software true-ups sit inside IT and professional services spend, one of the six categories where contract terms and invoiced amounts routinely diverge. The audit method is identical to what applies elsewhere in indirect spend: retrieve the governing agreement, rebuild the charge from its terms, and compare that to what was actually billed, regardless of category.

The mechanism is the same across all four rows: an invoice states a number, a contract defines the rules that number should follow, and drift is the gap between the two. Software true-ups are simply the category where that gap is hardest to see, because the invoice arrives as a single annual total rather than itemized detail.

A company running a full review of indirect spend audit categories typically treats true-ups as a subset of IT and professional services review, applying the same contract retrieval and recomputation steps used for a professional services statement of work or a maintenance invoice.

The category-specific detail differs. A freight audit checks accessorial charges against a carrier's rate schedule. A true-up audit checks a licensed unit count against a definition buried in an order form. The underlying question, whether the invoice matches what was actually agreed, does not change.

How a true-up audit compares to related indirect spend audit disciplines.

For the wider pattern this sits inside, start with the margin drift guide.

7. Frequently Asked Questions (People Also Ask)

What is a software true-up in simple terms?

It is the invoice a software vendor sends, usually annually, to bill for usage that exceeded your licensed baseline during the contract term: more seats, more instances, or more consumption than you were originally licensed for. It reconciles actual usage against the contract rather than billing a new purchase.

Why don't AP teams catch errors in true-up invoices?

The invoice presents as a single summary total rather than itemized line charges, and the usage count behind it comes entirely from the vendor's own metering system. Without an independently maintained count of active licenses on the buyer's side, there is nothing internal to compare the vendor's number against.

What documents do I need before approving a true-up?

The current order form, every amendment signed since the original agreement, and the rate schedule that applies at your contracted volume tier. Renewal emails and the vendor's own invoice summary are not sufficient on their own; the order form and its amendments are the actual source of the billing terms.

Can deprovisioned accounts still show up on a true-up invoice?

Yes. If a license reduction request was submitted but not actually processed by the effective date, or if it was processed late, the usage count behind the true-up can still include those accounts. Confirming deprovisioning timing against the request date is one of the direct checks against this.

Is a true-up audit different from a general software spend review?

A true-up audit is narrower: it checks one specific annual reconciliation invoice against the contract that governs it. A broader software spend review would also cover license utilization, renewal negotiation, and whether the tool is used at all. The true-up audit is the invoice-to-contract matching component of that broader review.

What counts as a licensed user can vary between vendors, right?

Yes, and that variation is exactly where drift enters. One vendor's contract may define a licensed user as an actively assigned seat; another may count any provisioned account regardless of activity. The definition that governs your invoice is whatever your specific order form states, not a generic industry norm.

Should I dispute a true-up invoice myself or involve legal?

A factual discrepancy, such as a rate that does not match the contracted schedule, can usually be raised directly with the vendor's account team using the contract clause as support. Where the dispute involves interpreting ambiguous contract language, involve legal review. This is general information, not legal advice.

How often should a company audit its software true-ups?

Each true-up invoice deserves a check against the governing contract before payment, since each one is a separate reconciliation event with its own usage period and potential for definitional or rate drift. There is no dataset here to state a recommended review frequency across companies; the review point is the invoice itself, not a calendar cadence.

Where does software true-up drift fit within indirect spend audits generally?

It sits within IT and professional services spend, one of the categories where contract terms in a separate document, rather than the invoice itself, define what should have been billed. The audit method mirrors what applies to freight, labor, and maintenance invoices: retrieve the agreement and recompute the charge from its terms.

What is the single most useful thing to request from a vendor before paying a true-up?

The line-level usage detail behind the summary total: the actual list of counted users or instances, not just the aggregate number. A vendor's willingness to provide this detail is itself informative, and the detail is what lets you compare the count against your own records and the contract's definition.