Japanese Automaker. IBM audit closed 89 percent down.

A Japanese automotive group faced an IBM audit that compared global deployment against one region's entitlements. Consolidating fragmented Passport Advantage records closed the claim 89 percent below the opening number.

Why did IBM audit the Japanese automotive group?

IBM audited the group because deployment growth was visible while the entitlement picture looked thin from the publisher's side. Decades of regional purchasing had spread Passport Advantage entitlements across country level sites that nobody had ever consolidated.

The estate ran Db2, WebSphere, and MQ under manufacturing, logistics, and dealer systems across three continents. The deployment was real; so were the entitlements, just not in one place.

• Audit trigger: apparent gap between visible deployment and the regional entitlement record.
• Publisher position: global deployment licensed only by one region's purchases.
• Customer reality: sister subsidiaries held the missing entitlements in separate site records.

What did the entitlement reconstruction find?

The reconstruction found entitlements in regional records covering a large share of the asserted gap. Purchases made in different currencies, under different agreement numbers, for the same products, had never been mapped to the global deployment.

Why had the entitlements never been consolidated?

Because nothing forces it. Each region bought what it needed under its own site number, the group never ran a global ledger, and the fragmentation stayed invisible until an auditor exploited it.

How was the IBM audit claim defended?

The defense ran two tracks in parallel: a global entitlement consolidation across every regional Passport Advantage site, and ILMT remediation to restore sub capacity eligibility on the consolidated estate.

1. Inventory every Passport Advantage site number held by any group entity worldwide.
2. Map each regional entitlement to the global deployment it actually covers.
3. Present the consolidated baseline and require the auditor to re run the gap analysis.
4. Remediate ILMT and evidence sub capacity for the residual estate.
5. Settle the residual gap on forward terms, not retroactive penalties.

Did IBM accept entitlements held by different group entities?

Yes, with documentation. Demonstrating common ownership and internal use within the group made cross entity recognition a matter of evidence and persistence, and it removed the largest block of the claim.

What was the commercial outcome for the group?

The audit closed 89 percent below the opening claim. Consolidation covered most of the asserted gap, sub capacity evidence repriced the rest, and the small residual settled as a forward purchase the group needed anyway.

• Claim reduction: 89 percent off the opening position at close.
• Entitlement recognition: regional purchases now count against global deployment.
• Forward posture: one global entitlement ledger, maintained quarterly, owned by group IT.

What is the durable lesson for multinational IBM customers?

Run the global ledger before IBM runs it for you. A consolidated entitlement baseline turns an audit from an existential claim into a reconciliation exercise.

Where the common advice on IBM entitlement gaps is wrong

The standard advice when an IBM audit shows an entitlement gap is to negotiate the price of closing it, on the theory that the auditor's gap analysis is broadly right. We disagree. In roughly 20 to 30 IBM audit defenses Fredrik Filipsson supported in 2024 to 2025, the gap analysis in multinational estates was wrong more often than right, because it matched global deployment against fragmented regional records. Consolidation alone closed 30 to 60 percent of asserted gaps before any negotiation. The buyer side move is to refuse the gap number until every group entity's entitlement record is consolidated and recognized; only the residual after that is worth pricing.

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. Inventory every Passport Advantage site number held by any group entity.
2. Build one global ledger mapping each entitlement to its covering deployment.
3. Verify ILMT coverage across all regions, not only the headquarters estate.
4. Document common ownership so cross entity recognition is ready before any audit.
5. Centralize future IBM purchasing or at least the recording of it.
6. If a notice arrives, refuse the gap analysis until the consolidated baseline is on the table.

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

What triggered the IBM audit at the Japanese automotive group?

An apparent entitlement gap triggered it. Global deployment was visible to the publisher while entitlements sat fragmented across regional Passport Advantage sites, making a compliant estate look exposed.

How much was the IBM audit claim reduced?

The claim closed 89 percent below the opening position. Entitlement consolidation covered most of the asserted gap and sub capacity evidence repriced the remainder.

Can entitlements bought by one subsidiary cover deployment at another?

Yes, with documentation of common ownership and internal use within the group. Cross entity recognition removed the largest block of this claim.

How long does entitlement consolidation take in a multinational group?

Typically two to four months across regions, and it is the highest value workstream in a fragmented estate because it shrinks the claim before any negotiation starts.

Did the group pay retroactive penalties to settle?

No. The small residual gap after consolidation settled as a forward purchase the group needed anyway, with no retroactive penalty component.