Sao Paulo corporate district office towers
IBM

Brazilian retailer IBM audit. 94 percent off the claim.

Full capacity PVU counts met two trading cycles of capacity records and four countries of entitlement archaeology. The claim did not survive.

Contact Us IBM Advisory
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

A leading Brazilian retail group cut its IBM audit exposure 94 percent by rebuilding PVU counts, restoring sub capacity evidence, and settling the corrected position against the renewal.

Key takeaways

  • 94 percent exposure reduction: the defended settlement closed at a fraction of the auditor's opening position.
  • PVU counting was the battleground: full capacity counts across virtualized retail systems drove the opening claim.
  • ILMT evidence was rebuilt: reporting gaps from a data center consolidation were closed with virtualization records.
  • Passport Advantage records recovered value: entitlements from regional purchasing sites offset claimed shortfalls.
  • Seasonal capacity mattered: retail peak provisioning patterns were documented to correct the deployment baseline.
  • The renewal carried the settlement: the corrected exposure traded into forward commitments, not a penalty check.

Who was the client and what did the audit claim?

The client is a leading Brazilian retail group operating across Latin America with WebSphere, DB2, and MQ workloads on a heavily virtualized estate. An IBM audit opened with a standard data request and matured into a nine figure exposure position built on full capacity PVU counts.

The claim leaned on two gaps: ILMT reporting continuity lost during a data center consolidation, and entitlement records scattered across regional purchasing entities that the auditors never consolidated under the Passport Advantage program.

The engagement at a glance

DimensionPosition
SectorRetail, Brazil and Latin America
ProductsWebSphere, DB2, MQ
Claim basisFull capacity PVU after ILMT gaps
Outcome94 percent exposure reduction
Settlement vehicleRenewal aligned commitment

Why did full capacity PVU counting inflate the claim?

IBM prices distributed middleware in Processor Value Units, and sub capacity treatment under the License Metric Tool rules requires continuous eligible reporting. Where the consolidation broke reporting continuity, the auditors priced every physical core in every cluster.

Retail made it worse. The estate provisioned peak capacity for seasonal trading events, so full capacity counting priced infrastructure that ran a few weeks a year as if it ran always.

How seasonal capacity was put back in its place

The defense documented provisioning patterns across two trading cycles: capacity reports, change records, and virtualization manager exports. The corrected baseline separated steady state deployment from seasonal burst, cutting the disputed core count materially.

What did the defense actually do?

The defense ran the standard sequence: freeze, reconstruct, model, then settle. The work split between evidence rebuilding in the infrastructure and entitlement archaeology in procurement records across four countries.

  1. Single channel communication, with no raw tool exports going to the auditors.
  2. ILMT history rebuilt around the consolidation window from virtualization records.
  3. Regional Passport Advantage sites consolidated into one entitlement baseline.
  4. Seasonal provisioning documented across two full trading cycles.
  5. Corrected exposure model presented with the renewal as the settlement vehicle.

Why the regional entitlements mattered

Brazilian and regional subsidiaries had bought IBM software through separate purchasing entities for years. Consolidating those records offset a meaningful slice of the claimed shortfall before the PVU argument was even joined.

What was the outcome and what should retailers copy?

The audit settled 94 percent below the opening exposure, inside a renewal that restored sub capacity treatment and consolidated entitlements going forward. The retailer exited with a cleaner licensing position than it entered.

The copyable lesson for retail estates: document seasonal provisioning as a routine discipline. The same elasticity that serves peak trading reads as permanent deployment to an auditor unless the records say otherwise.

  • Keep ILMT continuous: consolidations and migrations are when reporting breaks and claims are born.
  • Consolidate entitlements: regional purchasing sites hide recoverable value.
  • Paper the peaks: seasonal capacity needs contemporaneous documentation, not retrospective argument.

Where the common advice on IBM audits in retail is wrong

The standard advice treats IBM audit claims as fixed findings and budgets for a negotiated discount of 20 or 30 percent. We disagree. In roughly 30 to 40 IBM defenses Fredrik Filipsson advised in 2024 to 2025, the claims were constructed defaults that compressed 85 to 96 percent when the evidence was rebuilt, and retail estates compressed furthest because seasonal provisioning inflated the starting number most. The buyer side move is to spend the first eight weeks on virtualization records and entitlement archaeology, not on settlement meetings. The claim shrinks fastest in the evidence room, not the negotiation room.

Retail group technology operations center with analysts monitoring systems
Two trading cycles of capacity records separated seasonal burst from steady state, removing cores the claim had priced as permanent.

What the engagement data shows

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

94%
Exposure reduction achieved
8 of 10
Sub capacity positions rebuilt in our file
20-40%
Claim value tied to seasonal capacity

Source: Redress Compliance advisory engagement file, 2024 to 2025.

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 reporting continuity, especially around past consolidations.
  2. Consolidate Passport Advantage records across all regional purchasing sites.
  3. Document seasonal provisioning patterns as a standing discipline.
  4. Freeze audit communication into one channel at the first notice.
  5. Rebuild disputed periods from virtualization records before responding.
  6. Position the renewal as the settlement vehicle for any corrected exposure.
Cover of the IBM Audit Defense Guide white paper from Redress Compliance

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 much was the IBM audit exposure reduced?

The Brazilian retail group settled 94 percent below the opening exposure. The reduction came from rebuilt sub capacity evidence, consolidated entitlements, and a corrected seasonal capacity baseline traded into the renewal.

What created the IBM audit exposure at this retailer?

A data center consolidation broke ILMT reporting continuity, letting auditors revert virtualized WebSphere, DB2, and MQ estates to full capacity PVU counts. Seasonal peak provisioning then inflated the core counts further.

How does seasonal capacity affect an IBM audit?

Capacity provisioned for peak trading reads as permanent deployment unless contemporaneous records prove otherwise. Seasonal burst accounted for 20 to 40 percent of claimed exposure in comparable retail estates in our file.

Can entitlements from subsidiaries offset an IBM claim?

Yes. Regional purchasing entities held Passport Advantage entitlements never consolidated into the main site, and merging those records offset 10 to 30 percent of claimed shortfalls in multi country estates we defended.

What is the right first response to an IBM audit notice?

Freeze communication into a single channel and send no raw tool exports. The first eight weeks belong to evidence reconstruction and entitlement archaeology, because the claim compresses in the evidence room before the negotiation room.

Why settle an IBM audit at the renewal?

The renewal converts a penalty demand into forward commitments IBM values more than the check. Renewal aligned settlements closed 30 to 60 percent cheaper than standalone settlements across our 2024 to 2025 engagement file.

Free Download

The full IBM Audit Defense Guide framework from the IBM Advisory.

The PVU framework, the ILMT evidence list, and the settlement moves that compress IBM claims.

Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.

No spam. We will only email you about this download. Privacy.
Run a software spend health check against your IBM estate in under five minutes.
Open the Tool →
94%
Exposure reduction achieved
8 of 10
Sub capacity positions rebuilt in our file
20-40%
Claim value tied to seasonal capacity

The same elasticity that serves peak trading reads as permanent deployment to an auditor. The records you keep decide which story wins.

Fredrik Filipsson
Co Founder and Group CEO. Ex Oracle, IBM, SAP.
Deep Library

More on this topic.

IBM Advisory →
Financial district towers at dusk
IBM
NY Financial IBM Audit
A $198.8M claim closed at $12.4M.
8 min read
Retail technology team in a planning session
IBM
Italian Retailer IBM Audit
A European retail estate defended.
7 min read
License compliance dashboard on a laptop
IBM
IBM ILMT and Sub Capacity
The eligibility rules and reporting discipline.
8 min read
Editorial boardroom interior

The advisor your vendors do not want.

500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.

Stay ahead of IBM licensing changes.

One buyer side briefing a week. Pricing moves, audit signals, and the levers that work. No vendor spin.