Licensing glossary

What is a software license audit?

A software license audit is a vendor's check of your deployments against the licenses you hold, under the audit terms of your agreement, to recover fees for any shortfall.

How it works

Audits are not random. Vendors have a limited number of auditors and point them where the expected recovery is highest. The usual triggers: a renewal or true-up within a year, a drop in spend, a merger or acquisition, an infrastructure change the vendor can see, and telemetry such as JDK downloads or Adobe activations.

The vendor collects deployment data, often with its own scripts, and sets it against what it believes you own. Oracle's audit report, for one, is raw script output and not a bill: reconciling it against what you own comes before any reply.

Worked example

Illustrative numbers. In an Oracle review, reconciliation against entitlements and real usage typically removes a third to two thirds of the initial finding:

Initial finding
$900,000
After reconciliation
$300,000 to $600,000

An audit notice six to twelve months after a deal closes is standard practice, so build the position before the letter arrives.

What to watch

  • Replying before reading. Reconcile every finding before the first line of the reply.
  • Indirect access. Users or systems that reach a licensed application through an integration or API are the finding auditors look for first.
  • Cutting spend without a position that shows the remaining deployment is licensed.
  • Platform changes. Each one changes the counting rules, and customers rarely re-baseline after.

Related terms