IBM software audit defense — processor metrics, sub-capacity, and the audit playbook.

What actually triggers an IBM audit.

IBM software audits are dispatched by IBM Audit Services or by a third-party auditor (Deloitte, KPMG, EY are the rotating roster) on a roughly 3–5 year cadence per customer. The triggers are predictable: a Passport Advantage renewal cycle, a hardware refresh that touched a virtualization platform, a material reduction in support spend, or an M&A event that brought new entitlements into scope. Less commonly, a deal that fell through can produce an audit motion within 12–18 months.

In our experience across 340+ engagements, the customers with the highest audit exposure are those running IBM software on VMware or AIX virtualization, those who have lapsed on ILMT reporting for any period inside the 24-month look-back window, and those with material M&A or divestiture activity that hasn't been formally tied off in Passport Advantage records. For those estates, structured IBM software license audit defense begins before the audit letter — validating ILMT history and PVU mapping while the data is still yours to correct.

The PVU metric and processor counting

IBM's processor-value-unit (PVU) metric assigns a per-core multiplier that varies by processor type. The deployed PVU calculation is then compared against entitlements. The first source of compliance gap is processor-type misalignment — IBM's PVU table updates and the customer's deployed processors don't always match what the entitlements assumed.

Sub-capacity and the ILMT requirement

Sub-capacity licensing — paying only for the cores allocated to the IBM workload, rather than the full hardware — requires continuous IBM License Metric Tool (ILMT) reporting. Any gap in ILMT history during the audit look-back window collapses sub-capacity entitlement to full-capacity, multiplying the deployed PVU count by a material factor. ILMT compliance is the single most common audit-claim driver.

IASP, IFL, and the AIX-specific mechanics

IBM Authorised Sub-Processor (IASP) rules, IFL (Integrated Facility for Linux) on z/OS, and AIX-specific virtualization treatment each carry their own sub-capacity mechanics with their own evidence requirements. The audit team will request specific documentation for each; missing documentation collapses to full-capacity.

The first 30 days of an IBM audit.

The first 30 days of an IBM audit are disproportionately important. The audit scope is set, the data request is structured, the evidence approach is negotiated, and the timeline cadence is established — and these decisions shape the eventual claim. Common first-30-day mistakes are accepting an over-broad data request, agreeing to direct ILMT access for the auditor, and conceding scope on infrastructure that should be out of scope under the audit clause.

The defensive first-30-days script: acknowledge the notice in writing, request the audit clause reference and scope definition, push back on any out-of-clause requests, establish a single point of contact, and engage independent counsel before the data exchange begins. The audit team will press for speed; the defence is process discipline.

The IBM audit defence moves that consistently work.

1. ILMT history integrity. Verify continuous ILMT reporting across the look-back window. If gaps exist, document them and prepare the sub-capacity defence per workload.
2. Re-baseline PVU calculations. Verify processor types against the current PVU table. Mismatches are common and material.
3. Scope discipline. Hold IBM to the contractual audit clause scope. Refuse out-of-scope requests in writing.
4. Evidence over volume. Don't volunteer data the auditor hasn't formally requested. Each piece of data either supports compliance or introduces gap.
5. Negotiate retroactive vs forward. When a gap is real, the better commercial outcome is usually a forward-looking entitlement uplift rather than a retroactive claim payment.
6. Co-term audit settlement with renewal. Where Passport Advantage renewal is imminent, settle the audit and renew together — IBM's flexibility is materially higher inside a renewal motion.
7. Document everything. Every conversation, every data exchange, every concession. Audit settlement is a commercial negotiation; the documentation is what protects the buyer position.