California Agency. IBM audit closed 85 percent down.

A California government agency faced an IBM audit inside public sector procurement constraints that ruled out a quick bundle settlement. A records driven defense closed the claim 85 percent below the opening number.

Why did IBM audit the California agency?

IBM audited the agency because its estate had grown through successive modernization programs while ILMT reporting lapsed between them. The estate ran Db2 under case management data, WebSphere behind citizen portals, and MQ between agency systems.

The opening claim anchored on full capacity PVU across the virtualized estate, plus the assumption that decades of procurement had left entitlement gaps the agency could not document.

• Audit trigger: lapsed ILMT reporting across modernization waves.
• Publisher position: full capacity defaults plus assumed entitlement gaps.
• Customer reality: statutory records could evidence nearly every purchase ever made.

How did procurement rules shape the defense?

Public contracting rules ruled out the standard publisher exit: a bundled enterprise agreement wrapping the claim into new spend. Any settlement had to be justified line by line against documented obligations, which forced the dispute onto the facts.

Why did the constraints help rather than hurt?

Because they removed the pressure to buy the problem away. With no bundle shortcut available, the agency had to win on evidence, and its records were strong enough to do exactly that.

How was the IBM audit claim defended?

The defense rebuilt the estate's history from statutory records: procurement files evidenced entitlements across decades, change records reconstructed deployment, and remediated ILMT restored sub capacity eligibility going forward.

1. Pull procurement records for every IBM purchase across the agency's history.
2. Consolidate entitlements into one baseline tied to Passport Advantage records.
3. Reconstruct deployment history from change management and hypervisor data.
4. Remediate ILMT and validate coverage across the virtualized estate.
5. Settle the documented residual within procurement and appropriation rules.

What did the statutory records actually prove?

They proved the entitlement gap was mostly an artifact. Purchases the auditor's analysis missed were sitting in procurement files, and the documented baseline shrank the claim before the PVU arguments even started.

What was the commercial outcome for the agency?

The audit closed 85 percent below the opening claim, settled as a documented reconciliation that procurement could lawfully approve, with no bundled agreement and no retroactive penalty component.

• Claim reduction: 85 percent off the opening position at close.
• Lawful settlement: every settlement line tied to a documented obligation.
• Forward posture: ILMT reporting now survives modernization waves with named ownership.

Is the public sector defense slower than the private one?

Yes, and it does not matter. The elapsed time went into evidence that cut the claim, and the engagement file shows records driven public defenses settle deeper, not just slower.

Where the common advice on public sector IBM audits is wrong

The standard advice treats public agencies as soft audit targets that should settle early because they cannot move money fast and cannot fight long. We disagree. In roughly 20 to 30 IBM audit defenses Fredrik Filipsson supported in 2024 to 2025, public sector estates settled 60 to 90 percent below opening claims precisely because procurement constraints forced records driven defenses, and statutory record keeping out evidenced the auditor in almost every case. The constraint is the strength. The buyer side move for an agency is to weaponize its own records: rebuild the entitlement history the law made it keep, and make every settlement line answer to it.

What the engagement data shows

Three cuts of our advisory engagement file frame the size of the opportunity.

What to do next

Five moves turn this analysis into a lower invoice on the next renewal.

A sequence you can run this quarter

1. Pull procurement records for every IBM purchase in the agency's history.
2. Consolidate entitlements into one baseline before any audit letter arrives.
3. Verify ILMT coverage survives every modernization and migration wave.
4. Document the settlement paths procurement rules allow, before you need them.
5. Reconstruct deployment history from change records while they remain accessible.
6. If a notice arrives, route everything through one channel with legal review.

White Paper · IBM

IBM Audit Defense Guide

The buyer side framework we use with Fortune 500 clients defending IBM software audits. Read it free.

Read the white paper

Frequently asked questions

What triggered the IBM audit at the California agency?

Lapsed ILMT reporting across successive modernization programs triggered it, letting the auditor anchor on full capacity defaults plus assumed entitlement gaps.

How much was the IBM audit claim reduced?

The claim closed 85 percent below the opening position, settled as a documented reconciliation the agency's procurement rules could lawfully approve.

Can a government agency accept an IBM bundle settlement?

Usually not. Competitive procurement rules block wrapping an audit claim into new bundled spend, which forces, and rewards, a records driven defense instead.

Do public agencies have an advantage in software audits?

Yes. Statutory record keeping lets agencies evidence purchases 10 to 20 years back, which routinely defeats gap analyses built on incomplete publisher records.

Did the agency pay retroactive penalties?

No. The settlement contained no retroactive penalty component; every line tied to a documented obligation within appropriation limits.