Glossary · Licensing
This ServiceNow transaction based license definition explains in two sentences what the metric means and why it matters at renewal. A transaction based license charges by counted events the platform processes, such as automated actions or integration runs, rather than by named users, so your cost scales with usage volume and capping that volume is the buyer side control point.
A ServiceNow transaction based license is a metric that bills you for the number of qualifying transactions the platform executes over a term, instead of for the number of people who log in. A transaction can be an automated workflow run, an integration call, a message processed, or a metered assist action, and the contract defines exactly which events count.
This sits alongside the more familiar named user and fulfiller metrics. Where a ServiceNow named user license ties cost to identities, a transaction model ties cost to throughput, which behaves very differently as your automation footprint grows.
The defining commercial risk is that transaction volume is rarely flat. Once a workflow is automated it tends to run more often, and integrations chatter in the background, so a metric that looked cheap at signature can drift well above plan inside a single year. Under the 2026 commercial model this matters most for metered assists, where large agentic actions consume materially more units than a simple lookup, and overage triggers top up charges at rates that are far less negotiated than your base.
Buyer side, three controls decide whether a transaction metric works for you. First, secure a written definition of what counts as one transaction, because vague definitions inflate the count. Second, negotiate a generous included pool with the right to true down, not only a path to true up. Third, fix the overage rate in the contract so an unplanned spike is not repriced at list. We cover the wider picture in the ServiceNow transaction based licensing guide and the ServiceNow license true up mechanics.
At renewal the vendor reconciles your actual transaction volume against your entitlement. If you have grown, that gap is presented as a true up plus a higher base for the next term. Treat both numbers as opening positions. Bring your own metering data, challenge any events that should not have counted, and fold the settlement into the renewal rather than paying it as a standalone bill. The contracted version of this work is our ServiceNow licensing advisory.
NowNegotiations Advisory Team. Independent ServiceNow negotiation advisors with benchmark data from real enterprise renewals, buyer side in hundreds of enterprise software negotiations. Last updated July 18, 2025.
In practice they overlap. A transaction metric is one form of consumption pricing where the counted unit is a defined event rather than a user. The key is which events the contract says count.
A named user license charges per identity with access. A transaction based license charges per processed event, so cost scales with automation and integration volume rather than headcount.
Uncapped overage. If volume exceeds the included pool, top up charges apply at rates that are often far less negotiated than your base, so capping the rate in writing is essential.