IBM Audit Defence Negotiation: ILMT, Sub-Capacity and License Compliance

This guide is the long form of the workflow NoSaveNoPay applies inside paid audit-defence engagements. The commercial model is 25% gainshare against the gap between IBM's opening claim and the settled figure — the mechanics are documented on the audit defence service page and the IBM negotiation service page. The full reference for the gainshare model itself lives on the gainshare pillar.

What an IBM software audit actually is

IBM audits are formal compliance reviews triggered by IBM's Software Asset Management (SAM) or, more commonly, an IBM-engaged third party — Deloitte and KPMG are the most frequent. The audit is contractually authorised by the customer's Passport Advantage Agreement or specific licence agreement. The auditor's task is to compare deployed and accessible IBM software against current entitlement. The output is a compliance gap report, which then forms the basis of a settlement claim.

Two structural facts shape every IBM audit. First, IBM's commercial team is almost always involved in the settlement, even when the audit is nominally a compliance exercise. Second, the auditor's findings — particularly around PVU sub-capacity and ILMT — are easier to dispute than IBM's commercial team admits in opening conversations. Both facts matter for defence strategy.

Why audits are triggered (in order of frequency)

The risk-scoring signals IBM uses to prioritise audits are documented across multiple published sources. In our deal data, the most frequent triggers, in order:

1. Missing or non-compliant ILMT reports. Sub-capacity entitlement is contractually conditional on quarterly ILMT reports retained for two years. Customers who cannot produce nine months of report history are the highest-probability audit targets.
2. Dropped IBM maintenance. Customers who recently terminated S&S on previously licenced products draw audit attention because the move suggests internal pressure on IBM spend.
3. End-of-support migrations. WebSphere, Db2, and MQ end-of-support events trigger audits because customers commonly run unlicenced "transitional" deployments.
4. M&A activity. Acquisitions create entitlement-transfer questions IBM uses as audit predicates.
5. Mid-cycle ELA review. Long ELAs (5+ years) almost always face an audit at year three or four.

ILMT — the pivot point in any sub-capacity defence

The IBM License Metric Tool is the only IBM-approved tool to measure sub-capacity processor value unit consumption in virtualised environments. Sub-capacity entitlement allows the customer to licence PVU products based on actual core consumption rather than the full physical capacity of the underlying hardware. On a VMware cluster with 256 physical PVUs that allocates 32 PVUs to a single Db2 VM, sub-capacity entitlement reduces the required licence from 256 PVUs to 32 — an 8x difference. On a 16-node cluster, that gap easily exceeds 20x.

The contractual condition for sub-capacity entitlement is the production of quarterly ILMT reports retained for two years. Customers who cannot produce nine consecutive months of ILMT history forfeit sub-capacity entitlement under audit and are recalculated at full physical capacity. This is the single largest financial swing in most IBM audits.

Three ILMT remediation moves that work even mid-audit:

• Backfilled deployments. ILMT can be deployed during an audit and the resulting reports begin to accrue immediately. Most audits run six to twelve months — long enough for nine months of ILMT history to be produced. IBM typically accepts forward-looking ILMT remediation in exchange for settlement concessions, even where the historical position was non-compliant.
• Discoverable PVU re-counting. Auditors regularly count PVUs on hardware that does not actually run the audited software. Each questioned core saves between 70 and 120 PVUs depending on chip family. A thorough re-count typically removes 15–25% of the initial PVU claim before any commercial negotiation.
• Bundle credit application. IBM Cloud Pak entitlements include sub-capacity rights that are often missed by auditors comparing legacy entitlements. Cross-referencing Cloud Pak entitlement against allegedly under-licenced legacy products can absorb 10–40% of an opening claim.

The four phases of an IBM audit and where leverage sits

Audits run on a predictable cadence. Knowing which phase you are in determines which moves are available.

Phase 1 is the single most underused leverage moment. Customers who push back on auditor selection, scope, and methodology in the first three weeks routinely close out at a fraction of those who accept IBM's default terms. Phase 4 is where the majority of dollars are decided — and where the audit can be converted into a renegotiated ELA that materially improves forward economics.

The settlement is always a renewal

The single largest defence mistake we see is settling an IBM audit as a standalone compliance bill. IBM's commercial team has more discount headroom on a forward ELA than on a back-dated compliance settlement, so converting the audit liability into a credit against new spend usually produces the lowest net outcome. A $4.2M opening claim settled as a lump-sum becomes $4.2M (sometimes negotiated to $2.8M). The same exposure settled as part of a forward five-year ELA becomes $1.4M of credit against $14M of new commitment — at terms that include capped escalators, sub-capacity bandwidth, and audit rights that are themselves materially better than the prior agreement. Settle the audit and the renewal together, in the same document, in the same week.

Contractual changes to demand at resolution

Every IBM audit settlement is an opportunity to rewrite the underlying agreement. The contractual changes that produce the largest forward savings:

• Escalator cap. CPI or 3%, whichever is lower, across all entitlement categories.
• Sub-capacity entitlement codified for the entire estate — not just the products under audit.
• Audit cooling-off period. No further audits for 36 months following settlement; reasonable two-year notice on subsequent audits.
• Right to use IBM's own data. The customer's ILMT environment becomes the source of truth in any future compliance dispute.
• True-down rights at renewal. Headcount or core reductions produce proportional fee reductions.
• MFN on PVU pricing against customers in the same industry and entitlement band.
• Cloud Pak portability. Existing PVUs convert to Cloud Pak entitlement at a stated ratio.

What NoSaveNoPay does inside an IBM audit defence engagement

The workflow above is what we execute inside paid engagements. The team is led by former vendor executives and former enterprise CIOs who have themselves been on the customer side of IBM audits. The commercial model is gainshare — 25% of verified savings, where savings are the verified gap between IBM's opening claim and the settled figure plus the present value of forward ELA improvements. The methodology behind savings verification is in methodology; the full how-it-works is at how it works; the contract structure is at pricing. The model is contrasted with hourly and fixed-fee in gainshare vs hourly and gainshare vs fixed-fee.

Related reading

• IBM negotiation service (full scope)
• Software audit defence service
• Oracle license review 2026 — what it teaches IBM customers
• All NoSaveNoPay negotiation services
• The gainshare model — complete reference

Frequently asked questions