>
Journal · Settlement and Negotiation

The IBM settlement letter, what must be named.

A reduced number means little if the paper around it is vague. The settlement letter is what actually closes the audit, and what protects you from the next one. The detail it names is the detail that holds. Independent and buyer side. Not affiliated with IBM.

Why specificity is protection.

An audit does not end when a price is agreed. It ends when a document records exactly what was resolved. A letter that settles a vague shortfall for a lump sum leaves the underlying question open, which means the same products can be reopened in the next review. The discipline at settlement is to name everything: the products, the period, the quantities, and the entitlements you walk away holding. Anything left unnamed is left unresolved.

The products and the scope.

The letter should name each product the settlement covers, by exact program name and the metric it is licensed under, and state the period it resolves. This converts the settlement into a closed boundary. If WebSphere and Db2 were in scope, the letter names them and the cores or users settled; products outside that list are explicitly outside the release. Vague language about a general compliance position invites a fresh audit of the same estate.

The number and what it buys.

The figure has to be tied to the entitlements it purchases, not floated as a penalty. A settlement that converts into licenses you keep is an asset; a bare penalty is a sunk cost. The letter should record what the payment delivers: the licenses granted, their metric, and whether they carry forward into your renewal. That distinction is the difference between buying capacity you needed anyway and simply paying to make an audit go away.

Sub-capacity reinstatement and forward terms.

Where sub-capacity was denied during the audit, the letter should record the reinstatement plan: the tooling fixed, the conditions restored, and the basis on which future reporting proceeds. This stops the same full-capacity argument from returning next cycle. The strongest settlements also fold forward renewal terms into the letter, locking pricing and protective language while you still hold leverage, rather than leaving them to a separate negotiation after the audit closes.

What this means under audit.

The settlement letter is the Settle step made permanent. A reduced number won on the facts can still be undone by loose paper, so the letter has to name the products, the quantities, the period, the release, the reinstatement, and the forward terms. Named precisely, the settlement closes the matter and shapes the next renewal. Left vague, it simply postpones the same fight.

Keep reading.

Close it on terms that hold.

Our audit negotiation team drafts and pressure tests the settlement letter, so the products, the number, and the reinstatement plan are all named. 48 hour mobilization on notice.

Get audit help now →

The IBM Audit Brief

Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.

IBM Audit

Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.

Services
Audit DefenseAudit NegotiationILMT RemediationSub-Capacity Defense
Products
WebSphereDb2CognosCloud Pak
Company
AboutContactJournalWhite Papers
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019