When IBM opens a software audit, the first number is almost always a full-capacity reading of an environment that should qualify for sub-capacity. We defend the customer side only: re-establishing sub-capacity eligibility with corrected ILMT data, contesting full-capacity PVU assumptions, and scoping bundled Cloud Pak and middleware deployment to the contract. Across our 340+ engagements that work cuts the initial IBM compliance claim by 68% on average — and keeps the audit on the contract instead of IBM's default interpretation.
IBM audit defence is the independent, buyer-side management of an IBM software audit — whether run by IBM directly or by a third party such as Deloitte or KPMG on IBM's behalf — from the engagement letter to the final settlement. We take over the technical and commercial response so IBM cannot set the measurement, the timeline, or the price. We do not act for IBM, resell its licences, or take vendor fees — we represent the customer alone, which is exactly what lets us contest a finding rather than rationalise it. The objective is simple: pay for genuine gaps, and nothing for IBM's worst-case assumptions.
Most of the claim IBM presents is interpretation, not entitlement. Where ILMT is missing or non-compliant, IBM defaults to full-capacity PVU licensing for the entire physical estate — often several times true usage. Their position also counts every installed Cloud Pak component and bundled middleware product as deployed. In our experience the difference between IBM's opening position and the defensible number is consistently large — the 68% average reduction is not an outlier, it is what disciplined challenge of the measurement produces.
Do not submit ILMT exports yet. We validate the data first. Talk to us before you respond.
The claim shrinks finding-by-finding, not through a single concession. This is the pattern we see most often across IBM audits — IBM's opening read on the left, the defensible position after review on the right.
| Finding area | IBM's opening position | Defensible position | Driver of the reduction |
|---|---|---|---|
| PVU capacity basis | Full-capacity across the whole environment | Sub-capacity where eligibility is re-established | Corrected ILMT evidence applied |
| ILMT compliance | Non-compliance triggers full-capacity penalty | Historic sub-capacity reconstructed where allowed | Reporting reconstruction & policy reading |
| Cloud Pak components | Every installed component counted as used | Only deployed components in scope | Usage evidence vs. install evidence |
| Bundled middleware | Supporting programs licensed standalone | Restricted-use entitlements applied correctly | Bundle/restricted-use terms read |
| Virtualisation / containers | Entire host or cluster licensable | Scoped per sub-capacity virtualisation rules | Eligible-technology mapping |
The sub-capacity eligibility model, the ILMT reconstruction framework, and the audit response checklist we use in live audits.
We run a controlled, buyer-side process from the moment the audit notice lands. Every step is designed to keep the measurement on the contract and the timeline on your terms.
We defend the claim and negotiate the deal as one motion — IBM uses both as leverage, so we do too.
For the mechanics behind each finding above, read our IBM software audit defence guide, the sub-capacity & ILMT defence breakdown, the Passport Advantage teardown, and the IBM licensing guide pillar. For the wider methodology, see our audit defence service and the cross-vendor vendor audit defence guide. Negotiating a renewal at the same time? Start with IBM negotiation.
An IBM audit is rarely just a compliance exercise — it is leverage for the next ELA. Treating it as both, with independent buyer-side defence, is how the 68% average reduction turns into a settlement that protects the renewal as well as the claim.
From single-product reviews to enterprise-wide PVU audits, we defend the buyer side only.
Weekly compliance intelligence for IT leaders.