Usage analytics & the true-up.

What the true-up actually does.

A ServiceNow true-up is the annual reconciliation that compares an organisation's actual usage against its contracted entitlement and bills the difference. Admodum is an independent, buyer-side software licensing advisory firm; this page explains the true-up because it is the single moment when a year of unmanaged drift becomes a number on an invoice, and the moment buyers are least prepared for.

The reconciliation counts on two axes. It measures active fulfilment users — the licensed agents who work records in the platform — against the package quantities the organisation has bought, and it measures consumption against the subscription-unit pools that meter integrations and metered capabilities. Where actual usage on either axis exceeds entitlement, the excess is billed as overage. The fulfilment-user definition that drives the first axis is set out at fulfilment, requester and approver users, and the package structure it counts against at ITSM, ITOM, CSM and HRSD package tiers.

Why overage surfaces all at once.

The defining feature of the true-up is its timing. Usage drifts upward continuously through the year — a role assigned here, an integration scaled there, a custom app reaching into a package table — but the reconciliation happens once. The buyer experiences a year of small, individually unremarkable decisions as a single large bill, with no intervening signal that the position was moving.

This is what makes the true-up feel like an ambush even when nothing improper has occurred. Each decision that grew the count was reasonable in isolation; only in aggregate, and only at the annual reckoning, do they read as a cost event. The buyer who waits for the vendor's count to arrive is therefore always reacting, and reacting to a number assembled by the party whose revenue it represents. Custom builds are a common contributor here, for the reasons set out at custom tables, Creator and app-based licensing.

The structural fix is to make the true-up boring. An organisation that monitors its own usage continuously, reclaims and remediates as it goes, and forecasts consumption against its pools arrives at the annual reconciliation with no surprises — because it has already seen, and already corrected, everything the count will show. The true-up stops being an event and becomes a confirmation.

Reading the same data the vendor reads.

ServiceNow provides usage analytics within the platform that report active fulfilment users by package, role assignments and consumption against metered entitlements. This is, in substance, the same data the vendor uses to build the true-up. The buyer's information parity comes from reading it first.

An independent usage analysis run in the weeks before the reconciliation produces the buyer's own version of the count. It shows which licences are genuinely active and which are assigned to leavers or dormant accounts; which users hold roles that pull them into a higher package than their work requires; and how each consumption pool stands against forecast. That analysis is the difference between negotiating from knowledge and reacting to a bill, and it is the foundation Admodum builds on across the ServiceNow knowledge hub and the ServiceNow blog cluster. The optimisation method that acts on its findings is at entitlement optimisation and shelfware recovery.

Reducing the bill before it lands.

A true-up bill is reducible, but only before the count closes. Three levers do most of the work: reclaim inactive fulfilment-user licences held by leavers and dormant accounts; correct over-provisioned roles that pull users into a higher-priced package than their actual work needs; and right-size consumption pools to a realistic forecast rather than carrying over-bought capacity. Each reduces the counted position the true-up bills against.

The constraint is timing, and it is unforgiving. The same clean-up performed after the count is locked saves nothing for the period just billed; it only reduces next year's baseline. This asymmetry is why true-up preparation is a calendar discipline, not a reactive one — the work has to be scheduled to complete before the reconciliation window, which means starting it well before the vendor's count is due. Where the true-up sits adjacent to a renewal, the two should be run as one exercise, because the remediated, accurate position is also the right baseline for the renewal negotiation treated at ServiceNow renewal and negotiation.

One further point protects the buyer's standing. Remediation must be real — licences genuinely reclaimed, roles genuinely corrected — not a cosmetic adjustment reversed the day after the count. A reconciliation built on a defensible, documented position holds up; one built on temporary suppression invites scrutiny and erodes trust for the next cycle. The engagement that runs this properly opens at the ServiceNow practice or directly at contact.

Building the true-up calendar.

Because timing is the only lever that works, the true-up should be governed by a calendar rather than a reaction. Work backwards from the reconciliation date: the count closes on a fixed day, remediation must complete before it, and remediation itself takes weeks to identify, approve and execute. A true-up that arrives unscheduled finds the buyer with no time to act; a true-up that has been on the calendar for a quarter finds the buyer already remediated.

A workable rhythm runs on three checkpoints. The first, well ahead of the count, is the independent usage analysis that establishes the buyer's own position. The second is the remediation window, in which inactive licences are reclaimed, over-provisioned roles are corrected and consumption pools are right-sized, each change documented so it holds up to scrutiny. The third, immediately before the count closes, is the verification pass that confirms the remediation has taken effect in the platform's own analytics — because a correction that was approved but not applied saves nothing.

Treating the true-up this way changes its character entirely. It stops being an annual shock administered by the vendor and becomes a managed checkpoint the buyer runs to its own schedule. Where the true-up sits near a renewal, the same calendar feeds both, since the remediated position is the baseline the renewal is negotiated from, as set out at ServiceNow renewal and negotiation and the optimisation method at entitlement optimisation and shelfware recovery.