Journal · Audit

Audit defense outcomes: what 30 to 92 percent reduction looks like.

Audit settlements land all over the map, and the spread is not luck. It is the distance between an inflated opening claim and a defensible position. Here is what separates a modest reduction from a large one, and how to land at the high end.

The reduction is not a discount. It is the measure of how inflated the opening claim was.

When an audit settles far below the number on the first findings letter, it is tempting to read that as a negotiated favor. It is not. The opening claim is an estimate built on incomplete data and worst case assumptions, and the reduction against it simply measures how far those assumptions were stretched. A settlement landing near the bottom of the range usually means the claim was close to defensible from the start, the records were thin, and the room to move was small. A settlement landing at the top usually means the opening number rested on measurement errors, double counting, or entitlements the customer could prove all along but had not organized.

So the percentage describes the gap, not a generosity. Two factors set how wide that gap can be: how inflated the vendor's opening position is, and how defensible the customer's actual position turns out to be once it is properly assembled. The buyer cannot control the first, but controls the second entirely, and that is where the outcome is decided. Read this with our note on license records that win audits and our audit defense service.

What moves the outcome across the range

Pattern level · what the reduction looks like and what drives it

Where it landsWhat that usually meansWhat got it there
Lower reduction Opening claim was close to a defensible figure Genuine gap, thin records, vendor measurement accepted
Mid range reduction Some findings rebutted, some conceded Partial records, mixed entitlement clarity, contested peaks
Higher reduction Opening claim rested on errors or provable entitlements Clean baseline, independent measurement, strong contract terms
Claim withdrawn or near zero Finding could not survive contact with the records Documented entitlements, validated SCRT, audit clause limits

Pattern level outcomes we commonly observe, measured against the vendor's opening claim, not a quoted or guaranteed result. The room to move depends on how inflated the opening position is and how defensible your records and contract are. Every case differs; treat the range as calibration, not a promise.

Three things that land you at the high end

№ 01

A baseline that rebuts line by line

The single biggest determinant of the outcome is whether you can answer each finding with documented entitlement. A maintained baseline lets you contest the claim item by item rather than negotiating a lump sum, and every item you rebut comes straight off the top. Reconstruction under the audit clock rarely matches a baseline kept current.

Rebut findings, do not negotiate totals.

№ 02

Measurement you control

On the mainframe, inflated findings most often trace to the measured peak. Validating SCRT and sub-capacity data independently removes the largest source of overstatement and forces the claim back onto numbers you can stand behind. When the measurement is yours, the vendor's worst case assumption has nothing to rest on.

Own the number the claim is built on.

№ 03

The contract read for limits

Audit clause scope, entitlement definitions, prior settlements, and use rights frequently cap what is actually owed regardless of the technical finding. Reading the contract for those limits before responding often shrinks the claim more than any technical argument, because it changes what the vendor is entitled to ask for at all.

The contract often caps the claim before the data does.

Where the outcome is decided

The opening claim is inflated by design. Your records, your measurement, your contract set the floor. The reduction is the gap you can prove, not the favor you are granted.

48 hr

Mobilization on an audit notice

$180M+

Mainframe spend negotiated on the buyer side

500+

Engagements delivered since 2019

Frequently asked questions

Q1

Why do audit outcomes vary so widely?

Because the opening claim is an estimate built on incomplete data and worst case assumptions, not a settled figure. The reduction against it measures how far the claim was inflated, how clean your records are, and how strong your contractual defenses are. The percentage describes the gap, not a discount. See the audit clause you signed and forgot.

Q2

What separates a small reduction from a large one?

The quality of your license records, the independence of your measurement, and your contractual position. Where all three are strong, the defensible number sits far below the opening claim. Where records are thin and the measurement is the vendor's, the room to move is smaller. See license records that win audits.

Q3

Are these figures guaranteed?

No. Outcomes depend on the specifics of the claim, the records, and the contract. Any range describes a spread of patterns, not a promise. A reduction is measured against the vendor's opening position, which itself varies in aggressiveness. We frame outcomes as patterns to calibrate expectations, not a quoted result.

Q4

What should I do the day a finding arrives?

Do not respond on the substance yet. Acknowledge receipt, then assemble the baseline, validate the measurement, and read the contract for limits before engaging the findings. Our audit defense service mobilizes within 48 hours and our Broadcom (CA) audit defense page covers the publisher specific patterns.

Related: mainframe audit defense · license records hygiene · why audits are rising again · the renewal that became an audit · Broadcom (CA) audit defense

Audit notice or renewal under 18 months out? We mobilize within 48 hours.

Get expert help

Findings letter in hand? We measure the gap and defend it line by line.

Get expert help