Manufacturer defends post close IBM audit
How an acquired manufacturer turned a full capacity IBM demand into a sub capacity position that reflected actual usage, cutting a 5.2 million dollar opening claim to a defensible fraction.
This case study is an anonymised composite drawn from representative engagements. It names no real parties and uses approximate figures to illustrate typical outcomes.
This manufacturer defends post close IBM audit case study shows how a buyer met an inflated IBM claim with disciplined deployment evidence and brought it down to a number that reflected reality. The opening demand was 5.2 million dollars, built on a full capacity calculation that assumed every processor in every server was licensable. By rebuilding the deployment evidence and establishing eligible sub capacity reporting, the manufacturer reduced the genuine position to roughly 1.3 million dollars, most of it forward looking license value rather than penalty.
Inside the manufacturer defends post close IBM audit case study
Situation
A manufacturer had been acquired in a stock purchase and was being integrated into a larger group. It ran several IBM middleware products licensed on the processor value unit metric across a virtualised server estate. The target had intended to license on a sub capacity basis, which charges for the capacity a workload actually uses rather than the full server, but its reporting had lapsed and the data room held no current evidence of deployment. Standard diligence had reviewed the contracts but had not tested whether the sub capacity position could actually be supported.
Risk faced
IBM requires the IBM License Metric Tool to be deployed and reporting in order to claim sub capacity licensing. As of June 2026, where eligible sub capacity reporting is not in place, IBM may calculate the position at full capacity, meaning every physical processor in every eligible server is treated as licensable. That default is what produced the 5.2 million dollar opening demand. The genuine usage was far smaller, but without evidence the manufacturer could not rebut the full capacity calculation, and the change of ownership had put the estate squarely in IBM's audit sights.
Approach
We rebuilt the deployment evidence for each IBM product, establishing the actual processor capacity consumed by each workload across the virtualised hosts. We stood up eligible sub capacity reporting so the position could be measured on the correct basis going forward, and assembled dated evidence of the capacity caps and host configuration that limited each workload. With the buyer's counsel handling the contractual interpretation, we presented IBM with a measured sub capacity position rather than accepting the full capacity default, and disputed the elements of the claim that rested on the absence of reporting rather than on genuine usage.
Outcome
Once the deployment evidence and eligible reporting were in place, IBM could no longer default the calculation to full capacity. The genuine sub capacity position was roughly 1.3 million dollars, a reduction of about 75 percent from the 5.2 million dollar opening demand, and most of that remaining value was forward looking license the manufacturer needed regardless. The buyer closed the real gap and put ongoing reporting in place so the same exposure could not recur. The audit was defended not by argument alone but by evidence that held under scrutiny.
| Element | Opening position | After defense |
|---|---|---|
| Licensing basis | Full capacity default | Sub capacity, evidenced |
| Processor measurement | Every eligible processor | Capacity actually used |
| Reporting | Lapsed, no current data | Eligible reporting restored |
| Total claim | $5.2M | $1.3M settled |
Lessons for buyers
- IBM can charge at full capacity where eligible sub capacity reporting is not in place.
- The 5.2 million dollar opening demand rested on a missing report, not on genuine usage.
- Rebuilding deployment evidence reduced the position by about 75 percent.
- Restoring ongoing reporting closed the gap and prevented the exposure from recurring.
- Test sub capacity eligibility early. Confirm that reporting is in place before assuming a sub capacity position holds.
- Rebuild deployment evidence. Prove the capacity each workload actually uses rather than conceding full capacity.
- Restore reporting promptly. Put eligible reporting back in place promptly.
This outcome is the work of our M&A audit defense service, applied to the risks in the M&A software audit risk guide. For the questions buyers ask most, see the FAQ below.
Frequently asked questions
Why did an IBM audit follow the acquisition?
A change of ownership is a known prompt for publisher compliance teams, and IBM is among the most active after a deal. The combined manufacturer was larger and freshly capitalised, integration had re hosted workloads, and the change of control reset attention on the estate. The audit landed within the first year after close.
What is sub capacity licensing and why did it matter?
Sub capacity licensing lets a customer license IBM software for the processor capacity a workload actually uses rather than the full capacity of the server. To claim it, IBM requires the IBM License Metric Tool to be deployed and reporting. As of June 2026 IBM may charge at full capacity where eligible sub capacity reporting is not in place, which is what drove the inflated opening demand.
How was the inflated IBM claim reduced?
By rebuilding the deployment evidence, demonstrating the actual processor capacity each workload used, and establishing eligible sub capacity reporting so IBM could not default the calculation to full capacity. Once the measurement reflected real usage rather than the full server, the genuine position was a fraction of the opening demand.
Is this case study based on a real company?
No. It is an anonymised composite drawn from representative buyer side engagements. It names no real parties and uses approximate figures to illustrate a typical outcome rather than to describe a single identifiable transaction.
Facing an inherited IBM audit?
Request a confidential software M&A risk assessment. We rebuild the deployment evidence and defend the sub capacity position.