Documenting Your Counter Position for IBM
An IBM audit finding arrives as a spreadsheet that looks final. It is not. It is a claim, and a claim can be answered. The buyers who reduce their exposure most are the ones who put a documented counter position on the table, item by item, with evidence IBM cannot wave away. Reduce the number on the record, not in conversation.
Why a verbal pushback fails
Telling an auditor that a finding feels too high changes nothing. The audit team works from a deployment report and an entitlement comparison, and it will hold its position until you replace a line in that report with better evidence. A counter position is the document that does the replacing. It restates each disputed finding, names the correction, and attaches the proof. Without it, the conversation drifts and the original number stands.
What a counter position contains
The strongest counters are built before the first meeting, not improvised during it. Each disputed line should carry its own evidence so the auditor can verify the correction without trusting your word.
- The finding as stated: the product, the quantity, and the metric IBM applied, quoted exactly
- The correction: the recalculated quantity and the rule or record that supports it
- The evidence: ILMT reports, Passport Advantage entitlement records, deployment inventory, or the relevant licensing rule
- The offset: entitlements IBM omitted, including unused or transferred licenses that reduce the net claim
Anchor every line to a source
An incorrect PVU value is challenged with the published value unit per core for that processor, not an assertion. A denied sub-capacity claim is restored with continuous ILMT reports retained for the lookback period, showing the virtual cores actually allocated to the IBM software rather than the full physical host. A bundling finding is answered by the entitlement scope of the bundle. The pattern is the same in each case: tie the line to a record IBM itself recognizes.
Sequence the document for settlement
Order the counter so the largest defensible reductions appear first, then the offsets, then any items you concede. Conceding a small, genuinely accurate line early builds credibility for the larger challenges that follow. The goal is a single artifact that names the products, the corrected numbers, and the evidence, so the settlement conversation starts from your figure rather than IBM's.
The finding is the opening position, not the result. Build a written counter that restates each disputed line, attaches ILMT and entitlement evidence, and credits the offsets IBM left out. Challenges land 30 to 50 percent of findings on average, but only when the correction is documented and sourced. Put the number on the record and make IBM disprove your evidence, not the other way around.