Negotiating from a documented compliance position.
In an audit, the side with the better records sets the terms. A documented compliance position turns the conversation from arguing about the finding to defending a number you can prove. Evidence is what shifts the figure; opinion is not.
There are two ways to enter a settlement conversation. One is to react to the vendor's figure, contesting parts of it from instinct and hoping for a discount. The other is to arrive with your own number, built from records, and require the vendor to reconcile against it. The second approach consistently produces better outcomes, because audit findings rest on data, and data is answered by data. A documented compliance position is simply the act of having that data ready before the conversation starts.
Why documentation outranks argument
An auditor's finding is a set of claims with evidence behind each one: this many cores, this metric, this entitlement. To move a claim, you need counter-evidence, not a counter-opinion. A documented position gives every challenge a source: the ILMT report that proves sub-capacity coverage, the entitlement record that proves an offset, the hardware inventory that proves the core count. When a challenge is backed by a record, it is hard to dismiss; when it is backed by assertion, it is easy.
What the position contains
A position worth negotiating from is comprehensive and current, covering the same ground the audit will.
- An independent PVU and sub-capacity calculation per product
- ILMT coverage and the quarterly reports that support it
- A complete entitlement record, including bundled and prior-purchase rights
- A hardware and virtualization inventory mapped to deployments
- The metric that each entitlement actually specifies
How it changes the table
When you negotiate from documentation, the burden shifts. Instead of explaining why the vendor's number is too high, you present a number that is already substantiated and ask them to justify the difference. The conversation becomes a reconciliation of two evidenced positions rather than a haggle over one. That is a stronger place to stand, and it is where the largest reductions are found, because each disputed line is settled by a record rather than by who pushes harder.
Build it before you need it
The position is most powerful when it predates the audit. A company that keeps its compliance records current can produce the documented position in days, not weeks, and never has to assemble it under pressure. The buyer side discipline is to treat the documentation as a standing asset, so that when a finding arrives, the answer is already written and only needs to be applied.
Records beat arguments. A finding is a set of evidenced claims, and only counter-evidence moves them. Arrive with an independent calculation, ILMT reports, entitlement records, and a deployment map, then make the vendor reconcile against your number rather than defending theirs. Kept current, that position can be produced in days instead of assembled under pressure.
Want to negotiate from records, not instinct?
Our Audit Negotiation engagement assembles the documented compliance position, the calculations, reports, and entitlement records, so you defend a substantiated number rather than react to theirs.
See Audit Negotiation →The IBM Audit Brief
Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.
Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.