Singapore Telecom. IBM audit exposure cut 88 percent.

A Singapore telecom inherited IBM entitlements from a string of mergers, and the audit assumed none of them transferred. Reconstructing the entitlement chain entity by entity cut the claim 88 percent.

Why did IBM audit the Singapore telecom?

IBM audited the telecom because its deployment footprint did not reconcile with the surviving entity's purchase records. The estate ran MQ across network mediation, WebSphere behind customer portals, and Db2 under billing.

Two decades of mergers had scattered the purchasing history across defunct entity names and fragmented Passport Advantage site numbers. The auditor matched against one account and called the rest a gap.

• Audit trigger: deployment that did not reconcile with the surviving entity's account.
• Publisher position: unmatched deployment is unlicensed deployment.
• Customer reality: absorbed entities had bought the coverage under their own names.

How was the IBM audit claim defended?

The defense rebuilt the entitlement chain through every merger: original purchase records from absorbed entities, assignment language from the merger agreements, and a consolidated site number map that put the scattered coverage back under one view.

1. List every predecessor entity that ever bought IBM software.
2. Recover purchase records and Passport Advantage site numbers per entity.
3. Pull assignment and transfer clauses from each merger agreement.
4. Consolidate the chain into one entitlement baseline and re run the gap analysis.
5. Remediate ILMT and settle only the documented residual.

Did the entitlements legally transfer through the mergers?

Mostly yes, and that was the dispute that mattered. The merger agreements carried general assignment clauses, and IBM's transfer conditions were satisfied or curable in nearly every contested line. Once the legal position held, the commercial gap collapsed.

Why does M&A history inflate IBM audit claims?

M&A inflates claims because auditors reconcile deployment against the account in front of them, not the corporate family tree behind it. Every absorbed entity is a filing system the gap analysis never opened.

What role did ILMT play in the telecom's defense?

A supporting one. The entitlement chain was the main event, but remediated ILMT coverage restored sub capacity pricing on the virtualized estate, which kept the residual at a fraction of the full capacity number.

What was the commercial outcome for the telecom?

The audit closed 88 percent below the opening claim, settled at contract rates on the documented residual, with the entitlement chain consolidated under one Passport Advantage view for good.

• Claim reduction: 88 percent off the opening position at close.
• Settlement basis: the genuine residual only, at contract rates.
• Forward posture: one consolidated account, with entitlement transfer now a standing item in M&A due diligence.

What changed in the telecom's M&A playbook?

Software entitlement transfer became a closing checklist item. Every future acquisition now lands its IBM paper into the consolidated account within ninety days, so the next audit starts from one record instead of seven.

Where the common advice on post merger IBM estates is wrong

The standard advice after a merger is to negotiate a fresh enterprise agreement and fold the inherited mess into it, paying for certainty. We disagree. In roughly 25 to 35 IBM audit defenses Morten Andersen supported in 2024 to 2025, companies that bought certainty before tracing the chain repurchased coverage their predecessors already owned, sometimes twice. The inherited mess is usually an asset: decades of valid entitlements waiting to be consolidated. The buyer side move is to trace first and buy second. A fresh agreement signed before the chain is rebuilt prices the auditor's ignorance into your run rate.

What the engagement data shows

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

What to do next

Six moves turn this case into a smaller number on your own IBM exposure.

A sequence you can run this quarter

1. List every predecessor entity in your corporate history that bought IBM software.
2. Recover purchase records and site numbers for each, before the archives vanish.
3. Pull assignment clauses from merger agreements into one transfer file.
4. Consolidate Passport Advantage site numbers under one account view.
5. Add entitlement transfer to the closing checklist of every future acquisition.
6. If an audit letter 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 Singapore telecom?

Deployment that did not reconcile with the surviving entity's purchase records triggered it. Two decades of mergers had scattered entitlements across defunct names.

How much was the IBM audit claim reduced?

The claim closed 88 percent below the opening position, settled at contract rates on the residual left after the entitlement chain was reconstructed.

Do IBM entitlements transfer through a merger?

Usually, subject to assignment clauses and IBM's transfer conditions. In our defended cases the legal position held or was curable in nearly every contested line.

Why do auditors miss entitlements after M&A?

Because they reconcile against the account in front of them, not the corporate family tree. Predecessor purchases under old names and site numbers read as gaps.

How long did the entitlement chain reconstruction take?

About four months across seven predecessor entities, run in parallel with ILMT remediation so the settlement discussion started from a complete record.