① Guide · audit settlement
A mainframe audit ends in a settlement, and the number the vendor presents is the start of that negotiation, not the end. It moves on the count, the price, the back maintenance, and whether the shortfall becomes a penalty or a forward deal. Here are the levers, in the order that works.
Whoever brings the reconciliation sets the anchor.
By the time a settlement number lands, the audit has run through notice, data delivery, and reconciliation, and the vendor has built a case. That case typically bundles a claimed license shortfall with retroactive maintenance for the period and future support on the newly licensed capacity. Presented as a single figure, it looks like a bill. It is not. It is an opening position, and like any opening position it is set high enough to be negotiated down.
The buyers who pay the most are the ones who treat the finding as fixed and argue only about payment terms. The buyers who pay the least arrive with their own validated reconciliation, contest the components separately, and convert the conversation from a penalty into a forward deal. The difference is rarely the facts of the deployment; it is who framed the count and whether the buyer kept the levers below in play. This is the settlement stage of our audit defense work, and it begins in the first 48 hours.
| Lever | What it challenges | How it moves the number |
|---|---|---|
| Contest the count | The deployment claim itself. | Full capacity defaults, double counted or decommissioned systems fall out. |
| Contest the price | The rate applied to the shortfall. | List rate is negotiable, especially at volume. |
| Address back maintenance | Retroactive support charges. | Often the largest and softest component to reduce. |
| Fold into a forward deal | Whether it stays a penalty. | Vendor trades a smaller settlement for a larger commitment. |
| Cap the recurrence | The terms going forward. | Clean entitlement, caps, and consumption terms stop the gap reopening. |
Patterns commonly observed across publishers, not the terms of any one agreement or settlement. The components and their negotiability vary; your own contract, entitlement records, and validated consumption data govern the position.
A settlement looks backward. Leverage looks forward.
The single most useful move at settlement is to widen the frame from the past to the future. A pure compliance penalty has nothing in it for the buyer, but a vendor cares more about the ongoing relationship and the future run rate than about a one time charge. That asymmetry is the opening: a vendor will commonly reduce or absorb a settlement when it is wrapped into a larger forward agreement, because the renewal is worth more to them than the penalty. The buyer trades a backward looking charge for negotiated terms on the deal that actually matters.
Done well, the forward deal also closes the gap permanently. Folding the shortfall into a renewal is the moment to write in clean entitlement definitions, caps on uplift, and consumption protections, so the same finding cannot reopen at the next audit. The discipline is to keep the two threads visible, the settlement and the renewal, so the discount you are credited is real value and not the penalty quietly repriced as future cost. That is the heart of how we run license negotiation alongside audit defense, and it is far easier when the count was validated independently from the start.
④ What changes with us in the room
The vendor presents a bill. We present a reconciliation.
Typical renewal reduction we negotiate
Engagements delivered since 2019
Mainframe spend negotiated on the buyer side
No. It is the vendor's opening position, commonly bundling claimed shortfall with retroactive and future maintenance. It is the start of a negotiation. The number moves on the count, the price, the back maintenance, and whether the shortfall becomes a penalty or a forward deal. Accepting the first figure forfeits every lever at once.
Contest the count against your own validated SCRT and entitlement data, since findings often rest on full capacity defaults or decommissioned systems still recorded as live. Contest the price, address the back maintenance, and convert the shortfall into a forward deal. The most reliable move is arriving with your own reconciliation rather than reacting to theirs.
Often, because it converts a penalty into purchasing leverage. Vendors commonly reduce a settlement when it is wrapped into a larger forward agreement. Fold the shortfall in, write caps and clean entitlement into that deal, and keep the two threads visible so the renewal discount is real and not the settlement repriced as future cost.
Long before the number is presented. The strongest settlement rests on scope controlled at notice and data validated before delivery, so the reconciliation is yours, not theirs. The work starts in the first 48 hours of the audit, which is why we mobilize within 48 hours of a notice.
Related: audit defense service · the first 48 hours of an IBM audit · what auditors test · IBM licensing hub
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →