The Challenge

The client — a global automotive group headquartered in Japan, with manufacturing and logistics operations across Asia-Pacific, Europe, and North America — had deployed IBM middleware extensively across its production environment. WebSphere Application Server, IBM MQ, and DB2 formed the backbone of its factory automation and supply chain integration platforms across 14 countries.

IBM's Software License Review team issued a formal audit notification citing non-compliance totalling ¥1.8 billion (approximately $12 million USD). IBM's claim rested on three assertions: failure to deploy IBM License Metric Tool (ILMT) across all virtualised environments within the mandatory 90-day window; sub-capacity rights forfeited at several major facilities as a result; and full-physical-capacity PVU calculations applied retroactively across those servers. IBM had applied full-capacity pricing to an estimated 340 processor cores, producing an astronomical shortfall — compounded by disputed entitlement figures across six regional procurement channels where IBM contended maintenance renewals had lapsed.

"IBM's opening position was that we owed ¥1.8 billion. We were confident that number was wrong — but we needed expert help to prove it. Redress had the ILMT forensics capability and IBM-side experience to dismantle the claim systematically." — VP of IT Governance, leading Japanese automotive group (anonymised)

The client's internal IT team had no prior experience defending an IBM audit at this scale. With IBM pressing for a response timeline of 45 days and internal legal counsel unfamiliar with IBM's sub-capacity licensing framework, the client engaged Redress Compliance within the first week of receiving the audit notification letter.

The Approach

Phase 1: Rapid Evidence Gathering and ILMT Forensics

Redress Compliance began with a full extraction of all available ILMT data — audit snapshot reports, agent deployment logs, and software scan histories across every virtualised server in scope. The initial discovery revealed that ILMT had in fact been deployed across the majority of environments cited in IBM's non-compliance finding. However, gaps existed in three facilities: a German manufacturing plant that had undergone a VMware infrastructure upgrade eighteen months prior, a logistics co-location site in Singapore, and a recently acquired subsidiary in the Czech Republic whose IBM licences had never been fully integrated into the parent group's entitlement records.

Critically, the ILMT data confirmed that peak PVU consumption across all covered environments was substantially lower than IBM's calculations. IBM's audit team had applied PVU counts based on physical socket configurations rather than the allocated virtual core counts evidenced in ILMT — a systematic error that inflated the apparent exposure by more than 60% before even accounting for legitimate sub-capacity rights.

Phase 2: Entitlement Recovery and Legacy Credit Identification

Redress conducted a comprehensive entitlement reconciliation across IBM Passport Advantage records, regional reseller purchase orders, and three legacy IBM Enterprise Licence Agreements. Multiple PVU-to-VPC licence transitions processed over the preceding three years had not been reflected in the audit baseline. Entitlements from a 2019 group-level ELA — consolidating the client's regional IBM agreements — had not been credited against the audit claim for five of the fourteen facilities. Once formally evidenced, the legitimate exposure narrowed considerably. The ¥1.8 billion headline ignored approximately ¥900 million in valid licence credits that IBM's audit team had simply not applied.

Facing an IBM audit or Software License Review?

Redress Compliance has resolved IBM audit claims across 50+ engagements. Get expert advice before responding to IBM.
Download IBM Audit Defence Guide →

Phase 3: Formal Dispute Submission and Structured Negotiation

With the evidence base complete, Redress submitted a formal point-by-point dispute addressing each IBM claim: demonstrating ILMT coverage for environments marked as untracked, presenting corrected PVU calculations based on virtual core allocations in ILMT audit snapshots, and providing documented entitlement histories IBM had overlooked.

IBM's initial response accepted a portion of the corrections but maintained a revised exposure of approximately ¥420 million. Redress escalated to IBM's regional compliance leadership, presenting vCenter logs and Kubernetes metrics disputing IBM's server capacity assumptions for the three facilities with genuine ILMT gaps. The argument — supported by industry precedent — was that ILMT gaps created by infrastructure migrations and M&A activity should be treated as administrative deficiencies subject to remediation, not grounds for full-capacity penalty pricing applied retroactively. IBM agreed to settle on the basis of licences required going forward, with no retroactive penalties, no backdated maintenance fees, and a 24-month audit forbearance period.

The Outcome

The final settlement was agreed at ¥90 million — representing a 95% reduction on IBM's opening claim of ¥1.8 billion and a 79% reduction on IBM's revised claim following the initial dispute submission. The settlement covered only net-new licence entitlements required to address the verified deployment gaps at the three facilities where ILMT coverage had genuinely lapsed.

Beyond the immediate financial outcome, the engagement delivered lasting structural improvements for the client. Redress worked with the client's IT governance team to deploy ILMT comprehensively across all 14 facilities, establish quarterly ILMT audit snapshot procedures compliant with IBM Passport Advantage requirements, and document entitlement positions centrally to prevent the procurement fragmentation that had created unnecessary audit exposure in the first instance.

The ¥1.71 billion reduction in IBM's claim — equivalent to approximately $11.4 million USD — translated directly to preserved capital that the client redirected to planned production technology investments. The 24-month audit forbearance period provided the IT governance team with the runway to remediate residual ILMT gaps and build a defensible compliance position before any future IBM review.

  • ¥1.71 billion reduction from IBM's initial ¥1.8 billion claim
  • Zero retroactive fees or penalties in the final settlement
  • ¥900 million+ in legacy entitlements recovered and credited against the audit
  • 14 facilities brought into full ILMT compliance post-engagement
  • 24-month forbearance negotiated as part of the settlement agreement
  • Centralised entitlement register established for all IBM Passport Advantage accounts

IBM audit claims are routinely inflated by 40–70%.

Independent expert representation is the single most effective way to reduce your exposure.
View IBM Services →

Key Lessons for IBM Customers

IBM's initial claim is a negotiating position. Across Redress Compliance's IBM audit engagements, the final resolved amount averages 25–35% of the opening claim. IBM's audit team applies conservative assumptions that favour IBM on every disputed point — independent review routinely surfaces PVU calculation errors, unrecognised entitlements, and misapplied sub-capacity rules that IBM will not correct without formal challenge.

ILMT gaps do not automatically trigger full-capacity pricing. IBM's framework allows good-faith remediation of coverage gaps caused by infrastructure migrations, acquisitions, or administrative oversight. Treating every gap as grounds for full-capacity billing retroactively is IBM's opening position — not its invariable contractual right.

Entitlement fragmentation is the hidden risk. Most large IBM customers hold entitlements across multiple Passport Advantage agreements, regional reseller contracts, and legacy ELAs. IBM's audit team will not proactively credit entitlements they have not been formally notified of — and in this engagement, entitlement recovery accounted for more than half the total claim reduction.

Engage experts before responding. The client engaged Redress within the first week of the audit notification, before any data had been submitted to IBM. This timing prevented premature disclosure that could have strengthened IBM's position and allowed the defence strategy to be built before IBM's timelines constrained the client's options.