research

Auditing the completeness of software licence entitlement records

A method for matching purchases, subscriptions, and deployed seats to a single entitlement record, so a renewal is negotiated from evidence instead of a vendor count.

Short answer

Use this benchmark to size repeatable IT work, set the review cadence, and decide what stays with the technical owner before assigning the workflow to an IT virtual assistant.

Research playbook

MeasureVolume and handling time
OwnerTechnical manager validates
Risk ruleName sensitive access
RefreshQuarterly benchmark review
On this pageJump to section

Key stats

Sample groups3 spend tiersStudy protocol
Gap states3 categoriesStudy protocol
Review cadenceBefore renewalStudy protocol

Key takeaways

A licence renewal usually starts with a vendor's count and a scramble to find the purchase records. The count may include seats that were never used, while a team subscription bought on a card is missing from the inventory. This audit builds one entitlement record from purchases and deployments. The result gives the budget owner a defensible number before the renewal conversation begins.

Question and scope

This audit asks whether every software subscription and perpetual licence in scope has a current entitlement record, and whether the recorded seats match what is deployed. The unit is one product entitlement, such as a named subscription, a maintenance contract, or a perpetual licence with a support term. The population is the software the company pays for or deliberately uses without payment. The result describes that portfolio on the audit date.

Freeze the product list and the audit date before collecting invoices. Include products bought by a department, on a corporate card, or through a reseller. Exclude open-source tools unless the company pays for support or a commercial edition. Record the exclusion rule and the product count. A list built only from the central procurement system will miss the subscriptions that matter most.

Define entitlement and deployment

Define entitlement as the right to use a product, supported by a purchase record, contract, or written approval. Record the quantity, the licence metric, the start date, and the end date. Define deployment as the seats or installations that are actually assigned or installed. The two numbers answer different questions and should be stored in separate fields.

Name the licence metric precisely, because a seat, a device, a core, and a monthly active user are not interchangeable. Record whether the metric counts named users, concurrent sessions, or processed transactions. A mismatch between the metric and the vendor's definition is a common source of overpayment. Write the definition beside the record so the next reviewer uses the same one.

Build the licence frame

Create one row per product with the vendor, the contract owner, the purchase route, the quantity, the term, and the renewal date. Add the cost centre and the budget owner. Link the row to the invoice or contract file rather than copying the number without a source. A record without a source document is a claim, not an entitlement.

Add the deployment source, such as the identity provider, the endpoint console, or the vendor admin portal. Record the date the deployment count was taken. Note any product that has no reliable deployment source, because that gap limits the reconciliation. The frame should make the missing evidence visible rather than filling it with an estimate.

Reconcile purchases to records

Export the software spend from the accounting system for the audit period and match each line to a licence row. Include renewals, true-ups, and one-time purchases. Flag any payment that has no matching row and any row that has no payment. Investigate the flagged items before calculating totals.

Check the reseller invoices as well as the vendor's own billing, because a purchase can appear in both with different descriptions. Match on the product name, the quantity, and the term rather than on the invoice number alone. Record the matches and the unresolved items. A renewal that was paid twice is easier to find here than after the contract ends.

Test a sample

Select a sample of products across the largest spend, the most users, and the smallest departmental purchases. Confirm the entitlement quantity from the contract and the deployment quantity from the admin portal. Record both numbers and the difference. Include at least one product that is expected to be over-licensed and one expected to be under-licensed.

Ask the product owner to explain any difference before it is classified as waste or risk. A spare seat may support a contractor pool, and a lower deployment count may reflect a seasonal team. Record the explanation beside the figure. The audit is meant to find the truth, not to produce a savings target from an unexplained gap.

Estimate the gap

Calculate the difference between entitled and deployed seats for each product, then group the products by over-licensed, under-licensed, and unknown. Report the count of products in each group and the spend attached to them. Do not net an over-licensed product against an under-licensed one unless the licences are transferable and the vendor agrees. Keep the gross figures visible so the budget owner can see both sides of the portfolio.

For products with an unknown deployment count, report the spend and the missing evidence rather than guessing. A conservative estimate is more useful than a precise number built on assumptions. Note the direction of the likely error so the budget owner can read the range. The gap is a prompt for a review, not a final invoice adjustment.

Report the licence metric beside every gap figure, because a seat gap and a transaction gap are not comparable. Group the products by metric before adding the totals. Note any product whose metric changed during the term. A total that mixes metrics creates a number that looks precise but cannot be acted on.

Compare with renewal dates

Sort the products by renewal date and mark the ones that renew within the next quarter. For each, note whether the audit found a gap that should be resolved before the renewal. A renewal is the natural point to right-size a subscription, but only if the evidence arrives before the negotiation starts. Add the renewal date to the audit report so the owner sees the deadline without opening the contract.

Check the notice period in each contract, because some renewals require a cancellation or change notice weeks before the end date. Add the notice date to the licence record. A product with a gap and a short notice period is the most urgent item on the list. The budget owner should see that date, not only the renewal date.

Ask the vendor for a current entitlement statement before the renewal meeting and compare it with the audit record. A vendor statement is a claim that should be checked against the contract and the purchase history. Note any difference and the evidence behind the company figure. The meeting starts from a shared record instead of two competing counts.

Report to the owner

Lead with the number of products audited, the spend covered, and the products with the largest unexplained gaps. Show the over-licensed and under-licensed groups separately. Add one example of a departmental purchase that was missing from the central record. Keep individual names out of the summary and use product and cost-centre labels.

Ask for a decision on the products that renew soonest, including whether to reduce, hold, or investigate further. Name the owner and the date by which the decision is needed. If the decision is to keep the current quantity, record the reason and the next review date. A documented choice prevents the same question from returning at the next renewal.

Limits and next use

The audit covers products that appear in the purchase records or the deployment sources. It may miss a subscription paid from a personal card and reimbursed, a free tier that became paid, or a product bundled into another contract. It also cannot confirm that a deployed seat is actively used. State those limits so the result is read as an entitlement review rather than a full software asset management programme.

Repeat the audit before each major renewal cycle and compare the same product groups. If the unknown group grows, the purchase or deployment records are getting worse rather than better. Record the audit date and the contract files used. The record becomes a budget tool when it is maintained between audits, not rebuilt from scratch each time.

Sources and next step

Use the NIST Cybersecurity Framework 2.0 and the CISA Cross-Sector Cybersecurity Performance Goals as primary references for the identity, platform support, request intake, data export, and licence inventory controls discussed here. The NIST SP 800-53 Rev. 5 supports the access and audit record checks, and the GAO data reliability guidance supports the sampling and verification approach used in these methods. Apply your own policies, contracts, and system documentation when adapting the method.

Compare this study with the access revocation measurement and the software licence entitlement audit before combining them into one review cycle. If the measurement work is recurring and your technical owner can define the scope, review the service areas and contact ITVirtualAssistant to discuss a limited pilot.

Benchmark brief

What this research page must produce

Working number

A practical estimate for volume, review time, escalation rate, and assistant capacity.

Operating boundary

A clear split between routine support, preparation work, and technical ownership.

What the auditing the completeness of software licence entitlement records data shows

Treat this as a planning benchmark, not a universal number. Compare the benchmark against your ticket volume, SaaS stack, documentation backlog, and support risk before assigning recurring work.

The useful output is a decision about capacity, not a static statistic. If the workflow is high volume and low judgment, an IT virtual assistant can absorb coordination and upkeep. If the workflow is low volume but high risk, keep it with the technical owner and use the assistant only for preparation, reminders, and documentation.

Workflow

Recommended operating workflow

1

Collect a baseline

Pull the last 30 to 90 days of examples related to auditing the completeness of software licence entitlement records, including completed work and unresolved exceptions.

2

Classify the work

Tag each item by routine admin, manager approval, technical decision, security risk, or vendor dependency.

3

Set the operating number

Use the median weekly volume and review time to decide how many assistant hours the workflow deserves.

4

Refresh the benchmark

Recheck the numbers quarterly so tool growth, new systems, and security requirements do not silently change the scope.

Decision rules

MetricUse it to decideManager action
Weekly volumeWhether the workflow is worth assigning as recurring assistant work.Approve a weekly capacity target and backlog threshold.
Access sensitivityWhether the assistant can work directly or only prepare review notes.Set least-privilege permissions and removal dates.
Escalation rateWhether the workflow is stable enough to delegate.Rewrite the SOP when exceptions exceed the agreed threshold.

Consolidated statistics

StatisticFigureSource
Sample groups3 spend tiersStudy protocol
Gap states3 categoriesStudy protocol
Review cadenceBefore renewalStudy protocol

Sources

  1. NIST SP 800-128, Guide for Security-Focused Configuration ManagementSoftware inventory and configuration baseline practices for the deployment count.
  2. NIST SP 800-53 Rev. 5Software inventory, licence management, and acquisition controls.
  3. CISA Cross-Sector Cybersecurity Performance GoalsAsset inventory and software management goals for small organizations.
  4. NIST Cybersecurity Framework 2.0Asset management outcomes that support a maintained software inventory.
  5. GAO Assessing Data ReliabilityReconciliation and sampling checks for entitlement and deployment counts.

Measurement checklist

FieldWhat to captureOwner
VolumeWeekly request count, backlog age, and repeat issue patternsAssistant prepares, manager reviews
RiskAccess level, customer impact, security sensitivity, and approval needsTechnical owner
CadenceDaily, weekly, monthly, or quarterly review rhythmManager
EvidenceSample tickets, logs, screenshots, and before-after examplesAssistant collects, owner validates
EscalationTriggers, approval path, response time, and stop-work rulesTechnical owner

How to read the result

A good research page should leave the manager with a working number and a clear boundary: what the assistant can do every week, what the assistant can prepare for review, and what must never move without the accountable technical owner.

Source and refresh note

This planning page is dated for 2026 and should be refreshed quarterly as tool stacks, ticket patterns, and security expectations change.

How should teams use this benchmark?

Use it to define task volume, access limits, review cadence, and escalation rules before assigning work.

Get free benchmark review