Cutting an IBM Audit Settlement to the Defensible Number
In our engagement file, opening IBM claims ran 30 to 60 percent above the defensible number once sub capacity was proven. The settlement, not the finding, is where the money is decided.
Prepared by Redress Compliance · June 2026 · Representative IBM estate scenario (benchmark scenario, not a quote)
Executive Summary
An IBM audit finding is an opening position, not a bill. The number in the findings letter is built on full capacity counting and list price, the two assumptions most favorable to IBM. Both fall apart under evidence you already hold.
The single largest lever is sub capacity. Where the IBM License Metric Tool proves eligible virtualization, processor counts drop from full host capacity to deployed capacity. In the worked scenario below, that one move and three others take a 4.2 million dollar opening claim to a 2.8 million dollar defensible settlement.
The second lever sits in a line buyers forget: back maintenance. IBM bills back support for the unlicensed period at 100 percent, and routinely settles it at 50 percent or zero in exchange for going forward support. That line alone moved 450,000 dollars in the scenario.
This paper covers the resolution path, the four settlement levers, the bundle trap that quietly hands IBM the discount back, the legal posture decision, and what to harden the day the paper signs.
Benchmark ranges: Redress Compliance advisory engagement file, 2024 to 2025.
How an IBM audit finding actually gets resolved
Resolution runs in three stages: the findings letter, the rebuild of the defensible number, and the settlement. The money is decided in the rebuild, not the letter. Most buyers lose by treating the letter as a debt and negotiating only the discount on top of it.
The findings letter claims a quantity of unlicensed Processor Value Units or Virtual Processor Cores, then prices them at list and adds back support. Each input is contestable. The recount, not the discount, is where seven figures move.
The first contestable input is the count. Without ILMT installed and reporting, IBM counts every processor in the virtualization environment at full host capacity. With ILMT proving eligible sub capacity, the count drops to deployed capacity only. The recount in the scenario removes 500 of 1,120 counted cores on the WebSphere line.
| WebSphere ND line | Cores counted | Basis |
|---|---|---|
| Full capacity (no ILMT) | 1,120 | Every core in the cluster, IBM default with no metric tool data |
| Sub capacity (ILMT proven) | 620 | Deployed virtual capacity only, eligible virtualization documented |
| Overcount removed | 500 | Worth 520,000 dollars at this line's per core rate |
Full capacity versus sub capacity, WebSphere ND cores counted
Benchmark scenario, not a quote. Numbers match the table above.
The sub capacity right depends on a deadline most buyers miss. ILMT must be installed within 90 days of the first eligible sub capacity deployment, per the IBM sub capacity licensing terms. Quarterly snapshots must be retained for two years. Miss the install window and IBM is contractually entitled to full capacity for that period.
Acknowledge and freeze
- Confirm receipt, accept no number.
- Pull current ILMT reports across every cluster.
- Freeze new deployments of audited products.
Rebuild the number
- Reconcile owned entitlement against each claim line.
- Prove sub capacity to cut full capacity counts.
- Challenge list pricing where volume terms apply.
Sign clean, then harden
- Settle the gap on standalone paper.
- Put new licenses under support going forward.
- Lock ILMT discipline so it never recurs.
The four settlement levers: discount, scope, term, and credit
Four levers move an IBM settlement, and they are not equal. Scope and credit move more money than the headline discount, yet buyers spend their energy on the discount alone. Work them in order of leverage.
| Lever | What it changes | Where the leverage sits |
|---|---|---|
| Scope | Which products and processors are counted at all | Sub capacity proof and entitlement reconciliation remove counted units before any price applies |
| Credit | Back maintenance owed for the unlicensed period | Negotiable from 100 percent to 50 percent or zero in exchange for going forward support |
| Discount | Price per unit on the remaining shortfall | Challenge list where your volume band or prior pricing should apply |
| Term | Length and shape of the going forward commitment | Use the audit close as the moment to reset support terms, not to extend them blindly |
The credit lever surprises buyers most. Back maintenance is support IBM says you owe for running unlicensed product, billed at full rate for up to three prior years. IBM routinely waives 50 to 100 percent of it when you buy the licenses and put them under support, because it values the renewing stream more than the one time charge.
Back maintenance outcomes on the same shortfall
Benchmark scenario, not a quote. The 50 percent bar is the scenario outcome.
The bundle trap: why settlement plus renewal is the wrong paper
The standard advice, from resellers and from IBM account teams, is to fold the audit settlement into a new enterprise agreement or Passport Advantage renewal to "secure a better discount." We disagree, and the engagement data is consistent on this.
Bundling does three things, all in IBM's favor. It hides the settlement discount inside renewal pricing, so you can never prove what the compliance gap cost. It uses your weakest moment, an open finding, to price your strongest asset, the renewal. And it converts a one time charge into a multi year commitment sized on audit era assumptions.
IBM prefers the bundle because it protects the renewal margin and the support base. A separated settlement strips that protection and forces each number to stand on its evidence. That is precisely why the account team will push the bundle hardest when your exposure looks largest.
Legal posture: when to engage outside counsel, and when not
Most IBM audits resolve commercially and never need a lawyer at the table. Outside counsel is a tool for specific conditions, not a default escalation. Bringing legal in too early can harden a routine review into a dispute and raise IBM's posture in return.
| Engage outside counsel when | Handle commercially when |
|---|---|
| IBM alleges willful or bad faith non compliance | The dispute is a counting or entitlement disagreement |
| The claim threatens contract termination or audit clause breach | Back maintenance and discount are the open items |
| Privilege is needed over the internal exposure analysis | Your ILMT and entitlement records are clean and complete |
| Exposure exceeds your authority and reaches the board | The number is large but the path to settlement is clear |
When counsel does engage, scope them narrowly. Use legal to protect privilege over the exposure model and to hold IBM to the audit clause, not to run the commercial negotiation. The commercial recount and the levers stay with procurement and the advisor, where the value is built.
Post settlement hardening: what changes the day the paper signs
The settlement closes the past. Hardening prevents the next one, and it starts the day the paper signs, not the next budget cycle. The same gaps that produced this finding will produce the next unless three things change immediately.
- ILMT discipline. Install or repair ILMT on every cluster, confirm it reports, and lock quarterly snapshot retention for two years. Missing snapshots forfeit sub capacity for that period.
- Entitlement record of truth. Build one reconciled view of every Passport Advantage entitlement against deployment, owned by a named person, refreshed each quarter.
- Deployment guardrails. Gate new deployments of PVU and VPC products so nothing lands in a virtualization environment without ILMT coverage on day one, inside the 90 day window.
The going forward support terms you sign at settlement matter as much as the settlement figure. Reset support uplift caps and co termination at this moment, while IBM wants the close, rather than accepting the standard renewal shape later.
What a defensible settlement looks like, lever by lever
The waterfall below is a representative IBM estate, sized plausibly and varied for this paper. It is a benchmark scenario, not a quote. It shows the same four levers moving a 4.2 million dollar opening claim to 2.8 million dollars, every line reconciling to the next.
| Stage | Lever applied | Running total |
|---|---|---|
| Opening claim | Full capacity counting, list price, 100 percent back maintenance | $4,200,000 |
| Sub capacity proof | ILMT recount removes 500 full capacity cores | $3,680,000 |
| Entitlement reconciliation | Owned, unallocated entitlements offset the shortfall | $3,400,000 |
| Volume pricing challenge | List replaced with applicable volume band | $3,250,000 |
| Back maintenance waiver | Back support cut from 100 percent to 50 percent | $2,800,000 |
| Defensible settlement | One third of the opening number removed | $2,800,000 |
Settlement waterfall, opening claim to defensible number
Benchmark scenario, not a quote. Each bar matches the running total in the table.
Notice what the waterfall does not contain: a single concession that depends on IBM's goodwill. Every step is anchored in evidence the buyer controls, ILMT data, owned entitlements, contracted volume terms, and IBM's own preference for the support stream. That is what makes the 2.8 million dollar number defensible rather than negotiated down from fear.
Recommendation
Treat the findings letter as the opening bid and rebuild the number from evidence before you discuss settlement. The recount, not the discount, is where the money moves.
- Prove sub capacity and reconcile entitlement first. These remove counted units before any price applies, and they are the largest levers in every engagement we run.
- Refuse the bundle. Settle the compliance gap on standalone paper, then negotiate the renewal separately from a clean position, so each number stands on its own evidence.
We are glad to tie a meaningful part of the fee to delivered value.
Facing an IBM audit finding?
Talk to a buyer side advisor. Thirty minutes, your findings letter, and the recount that shrinks the number before you settle.
Buyer side intelligence, monthly
One letter a month. Negotiation moves, audit signals, and price book shifts.