$198.8M IBM claim. Closed at $12.4M.

A leading New York financial institution faced a $198.8 million IBM claim across Passport Advantage, sub capacity, and middleware, and closed it at $12.4 million inside the renewal envelope.

Who was the client and what did IBM claim?

The client is a leading New York financial institution running WebSphere, MQ, DB2, and Cloud Pak workloads across a large distributed estate. The IBM audit opened with a sub capacity continuity challenge and matured into a $198.8 million claim within ninety days.

The claim rested on full capacity PVU counts under the Passport Advantage agreement terms. Where sub capacity reporting evidence was missing, the auditors priced every core in the cluster.

Why did the sub capacity gap create a $198.8M number?

IBM sub capacity pricing requires continuous eligible reporting under the License Metric Tool documentation. A reporting gap lets the auditor revert the affected estate to full capacity, pricing every physical core rather than the virtual slice actually used.

In this estate, an ILMT migration left disputed quarters without clean reports across two data centers. The arithmetic of full capacity across clustered financial middleware did the rest.

How the defense rebuilt sub capacity treatment

The team reconstructed core counts from virtualization manager logs, change records, and capacity reports for every disputed quarter. The position was simple: the deployment never changed, only the reporting tool did, and the contemporaneous evidence proved it.

What defense sequence compressed the claim?

The defense ran four moves in sequence over sixteen weeks. Each move cut a layer off the claim before settlement talk started.

1. Communication freeze: one channel, no ad hoc data flowing to the auditors.
2. Entitlement archaeology: two decades of Passport Advantage records, acquisitions included.
3. Sub capacity reconstruction: virtualization evidence for every disputed quarter.
4. Renewal aligned settlement: the corrected exposure traded into the renewal envelope.

What the entitlement archaeology recovered

Acquired entities held entitlements never merged into the main Passport Advantage site. Recovering them removed entire product lines from the claim before the PVU argument even started.

What was the outcome and what does it teach?

The audit closed at $12.4 million inside the renewal envelope, a 94 percent compression, with sub capacity treatment restored going forward. The settlement bought corrected baselines and a clean reporting posture rather than a penalty receipt.

The lesson generalizes: IBM audit claims are constructed positions, not findings. They compress in proportion to the evidence you can rebuild and the commercial event you can attach them to.

• Evidence beats argument: contemporaneous logs settled what negotiation alone could not.
• History is money: old entitlement records are recoverable value, not archive clutter.
• Timing is leverage: the renewal date converted a penalty into a commercial trade.

Where the common advice on IBM audit claims is wrong

The standard advice treats an IBM opening claim as a negotiation anchor you talk down 20 or 30 percent. We disagree. In roughly 30 to 40 IBM defenses Fredrik Filipsson advised in 2024 to 2025, claims built on sub capacity gaps compressed 85 to 96 percent once the reporting evidence was reconstructed, because the full capacity number was never a finding, only a default. The buyer side move is to treat the claim as a hypothesis to be disproved with virtualization logs and entitlement records, not a bill to be discounted. Negotiating before the evidence is rebuilt locks in the auditor's arithmetic.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Verify ILMT coverage and report continuity across every virtualized IBM estate now.
2. Archive Passport Advantage entitlement records, including acquired entity sites.
3. Freeze audit communication into one channel the day a notice arrives.
4. Reconstruct disputed quarters from virtualization logs before conceding full capacity.
5. Build the corrected exposure model before any number goes back to IBM.
6. Map your next renewal or Cloud Pak decision as the settlement vehicle.

Related advisory: Start with our IBM audit defense playbook, engage the IBM audit defense service, and prepare for IBM audit negotiations before the settlement phase.

White Paper · IBM

IBM Audit Defense Guide

The buyer side framework we use with Fortune 500 clients defending IBM software audits. Read it free.

Read the white paper

Frequently asked questions

How big was the IBM claim and where did it land?

The opening claim was $198.8 million and the audit settled at $12.4 million, a 94 percent compression. The settlement closed inside the renewal envelope after sixteen weeks of defense work.

What caused the IBM audit exposure?

An ILMT migration left disputed quarters without clean sub capacity reports across two data centers. IBM's auditors reverted the affected WebSphere and MQ estate to full capacity PVU counts, pricing every physical core.

How was sub capacity treatment restored?

The defense reconstructed core counts from virtualization manager logs, change records, and capacity reports for every disputed quarter. The evidence showed the deployment never changed, only the reporting tool, and sub capacity treatment was restored for most of the estate.

Why did old entitlement records matter?

Acquired entities held Passport Advantage entitlements never merged into the main site, and recovering them removed entire product lines from the claim. Entitlement archaeology recovered 15 to 35 percent of claimed exposure in comparable financial services estates.

Should an IBM audit settle standalone or at renewal?

At renewal whenever dates allow. Settlements aligned with a renewal or Cloud Pak transition closed 30 to 60 percent cheaper than standalone settlements across our 2024 to 2025 file, because IBM values the forward commitment more than the penalty.

How long does an IBM audit defense take?

This engagement ran sixteen weeks from intake at week twelve of the audit to a signed settlement. Defenses that start at the audit notice rather than mid audit typically run shorter and compress claims further.