① Explainer · Audit Clauses
Every mainframe software contract carries an audit right. What that right actually allows, how much notice, how often, by whom, against what records, and how a shortfall is priced, is fixed in the drafting. Read the clause before the notice, because by then the terms are set.
An audit clause is the vendor's contractual right to verify that your deployment matches your entitlement. In plain terms it lets the publisher ask you to prove you are licensed for what you run. On the mainframe that proof is rarely a head count of installs; it is capacity data, SCRT reports, MSU figures, and product inventories tied to specific contracts and metrics.
The clause matters because the exposure is set by its limits, not by the vendor's good will. Two companies running the identical estate can face very different audits depending on whether their contracts cap frequency, require notice, restrict scope to the products in question, and define how any shortfall is priced. Vendor behavior here is best understood as a pattern: where the clause is loose, reviews tend to be broader and more frequent; where it is tight, the process stays inside the lines.
The same clause can be drafted to protect you or to expose you. The matrix below lays out the seven terms that carry the most weight, with the buyer friendly version against the vendor friendly version of each. Use it as a checklist when a contract crosses your desk.
| Term | Buyer friendly | Vendor friendly or silent |
|---|---|---|
| Notice | 30 days written notice, business hours | No notice stated, or very short |
| Frequency | Once per 12 months maximum | Unlimited or unstated |
| Scope | Named products and entities only | Entire estate, affiliates included |
| Who runs it | You self certify, or a named firm under NDA | Vendor or any appointee, open ended |
| Records required | Defined report set, your tooling | Vendor agents or scripts on your systems |
| True-up basis | Then current discounted rate | Undiscounted list, plus back maintenance |
| Cost shifting | Vendor pays unless shortfall above 5% | You pay audit cost regardless |
The two columns that move the most money are the true-up basis and cost shifting. A shortfall priced at undiscounted list with back maintenance and interest applied can multiply a modest compliance gap several times over. Negotiating those two lines at signing, when you still have leverage, is worth far more than arguing them under an open audit.
| Question | If yes | If no |
|---|---|---|
| Was contractual notice given? | Acknowledge, set the clock to the clause | Hold the start until proper notice runs |
| Is the request within drafted scope? | Prepare only the named products | Decline the excess, cite the clause |
| Are vendor tools demanded on your systems? | Check the clause permits it | Provide your own report set instead |
| Is a shortfall asserted at list price? | Test the true-up basis term | Reconcile the data before discussing money |
The through line is the same at every branch: the clause governs, not the cover letter. Most of the early pressure in an audit comes from requests that quietly exceed the drafted rights. Mapping each demand back to the clause is the single most effective discipline in the opening weeks.
The clause bites hardest when nobody read it until the notice arrived. By then the notice period, the scope, and the true-up basis are whatever was signed, often years earlier by someone who treated the audit section as boilerplate. The optimization is to treat audit terms as a negotiated item at every renewal, with the same care given to price.
Buyer side levers
The clause governs, not the cover letter.
Related explainers: software escrow and continuity rights, EWLC and entry workload license charges, and sysplex vs standalone pricing differences. Buyer guide: how to respond to a mainframe software audit notice. Commercial: mainframe audit defense and the contract review service. Hub: the IBM buyer side guide.
Audit notice or renewal under 18 months out? We mobilize within 48 hours.