OBLYTECH Logo
OBLYTECH Logo

ServiceNow License Compliance: Audit vs True-Up Readiness

ServiceNow license compliance means showing, from your own records, that the rights you hold match the way the platform is really used. An audit is a formal check of that match, and a true-up is the commercial adjustment that follows when the match is off. The stress in either case often comes from records that are scattered, out of date or produced at different times, so the work that helps most happens before anyone sends a notice.

True-up and audit are different processes

A true-up is usually a commercial step. You report the quantities consumed over an agreed period and buy the extra rights needed to cover them, often at renewal or on a schedule written into the agreement. Growth can trigger one under many agreements, so nothing has to be wrong for a true-up to happen. An audit is a verification exercise. Your deployment and usage are checked against the contract, and the outcome can be a clean report, a finding of shortfall, or a disagreement about how a term should be read. The practical difference is that a true-up can be planned for, while an audit has to be prepared for. Your contract and order documents define which mechanism applies and how notice is given, so read those before assuming either one.

What usually sets off a review

The triggers depend on your agreement, so check the terms that apply to your own contract. In practice the common ones are a renewal or a scheduled review date, a large change in the number of users or the scope of a module, a product or plugin switched on in an instance that did not use it before, and a second instance brought under the same contract through a merger or integration. Some of these show up in your own data. Others, such as a change in who counts as a user under your terms, tend to show up when someone reads the contract closely. You cannot remove every trigger, but you can know which ones would start a conversation and be ready to answer quickly. For background on the wider set of optimisation topics, see the ServiceNow license optimization guides. If you hold the Software Asset Management Professional product, its own pages cover how software records are kept, and that is where many of the answers an auditor asks for are stored: ServiceNow Software Asset Management Professional.

How usage is measured often decides disputes

This is a question that often causes disagreement, and the honest answer is that it depends on the licence terms. Some agreements measure a peak within a period, some measure an average over time, and some count distinct named people regardless of how often they log in. A consumption model may bill against actual activity in a way a fixed subscription does not. Before you build any readiness process, find out in writing which measure your agreement uses, which period it covers and how the platform reports it. If you cannot find that, ask the account team for the definition rather than working it backwards from the numbers you can see. Two reports that look similar can give different totals because one uses a peak and the other an average, and that gap alone can turn into a dispute.

Check the licence type before you compare totals

The licence type on each entitlement changes how it is counted, so check it before comparing totals. A perpetual licence grants indefinite use without maintenance rights, and subscription compliance is primarily driven by the user subscriptions pulled from the subscription portal. Those differences can explain a gap before any dispute starts.

Maintenance and Software Assurance entitlements need a link to their base perpetual licence. ServiceNow does not reconcile them unless that link is in place, so check it before you trust the result.

Build the evidence pack before anyone asks

An audit goes much more smoothly when the documents can be produced quickly and agree with each other. A workable pack has four parts: the order and contract documents with every amendment, a current entitlement record listing what you hold by product and quantity, the usage reports for the period under review together with the settings used to produce them, and a short note that explains any unusual items, such as a test instance that was active for a time or a trial that was later converted. Keep the pack in one shared location with a named owner. A common failure is a set of reports pulled at different times with different filters, so the totals often fail to match. Produce every figure from one run, date it, and store the settings next to it. The approach to organising the underlying records is covered in the patterns for connecting license data to other systems, and the workflow side of keeping software records current is in the compliance workflows for software assets.

Read the entitlement fields that set the count

The software entitlement record sets much of what a reconciliation counts. The licence metric decides the unit being counted, purchased rights record the number you bought, and allocations record which users or devices use them. Allocations available is calculated as active rights minus the sum of allocation quantities, so an allocation nobody has recorded shows up as available.

The metric group fills in from the software model, so check that link first. Thresholds for acting on unused rights are covered in the software reclamation rules guide.

Run a quarterly self-review and avoid the usual exposure

A self-review every quarter helps catch problems while they are still small. Give one person ownership and three inputs: the current entitlement record, the latest usage report, and a list of changes in the period, such as new users onboarded, modules switched on, or instances cloned. Compare usage with entitlement line by line. Where usage is above entitlement, decide whether to buy, reduce, or document why the gap is temporary, and record the decision with the date and the person who made it. Several habits make a true-up or audit more expensive than it needs to be. Leaving a product active in a test instance because it seems to cost nothing is one. Letting named user assignments drift away from the people who really log in is another. Assuming that a discount on an earlier order carries over to new quantities without checking the new order is a third. Asset ownership that is unclear makes it hard to say who should be counted, which is why the asset lifecycle management with clear ownership approach matters here. The review fits inside the broader software license governance model, where it becomes a standing agenda item rather than a one-off effort.

Connect audit readiness to renewal readiness

The same evidence serves both. A renewal conversation is easier when you can show what you use, what you hold and where the difference sits. An audit response is easier when the renewal file is already current. Before any renewal, ask the account team to explain the consumption-based items on your order and what they will bill against. Ask which report they will use to calculate a true-up, and whether you can run the same report yourself. If their figures differ from yours, resolve the difference before you sign, not after.

Let the scheduled reconciliation give you a dated position

ServiceNow’s software reconciliation runs weekly by default and can also be run on demand for specific publishers, groups or subgroups. Its results show the compliance status of each product against discovery and entitlements, which gives you a dated position to set against your quarterly review.

Frequently asked questions

Is a true-up the same as a licence audit?

No. A true-up is a commercial adjustment that buys rights for usage that already happened or is expected. An audit verifies your deployment and usage against your contract. A true-up can follow an audit, but it can also happen with no audit at all.

What should we do first when an audit notice arrives?

Read the notice and the clause it refers to before replying. Confirm the period, the products and the measurement method it names. Then take a dated copy of your current reports so the figures you send are the ones you checked, and bring the evidence pack into one place for review.

How often should entitlements be reviewed?

Quarterly is a sensible starting point, with an extra review before each renewal and after any large change in users, modules or instances. Your contract may set its own schedule, so check that first.