Post merger contract harmonisation for IBM software.

After a merger or acquisition, two IBM estates rarely line up. Different Passport Advantage sites, different entitlement records, and different reporting maturity have to be reconciled into one position. Done in a hurry, harmonisation can surface as the exact gap an audit is built to find.

Why two estates do not simply add up

Each party to a deal brings its own Passport Advantage relationship, its own site definitions, and its own set of entitlements. Combining them is not a matter of summing license counts. Entitlements are tied to the legal entity and the site that bought them, and whether they can move to the surviving entity depends on the terms under which they were acquired and on IBM accepting the transfer. Until that transfer is documented, the acquired entitlements may not legally back the deployments that now sit inside the combined organization.

That creates a window where the deployment footprint is larger than the cleanly transferable entitlement record. An audit landing in that window reads the combined estate against the entitlements it can verify, and the unverified entitlements from the other side of the deal do not count in your favor until the paperwork catches up.

Where harmonisation creates exposure

• Entitlements assumed to transfer that were never formally novated to the surviving entity.
• Deployments migrated onto the acquirer infrastructure before the entitlement record was reconciled.
• Overlapping products held on both sides, double counted or under counted in the merge.
• Divested units still running on entitlements that stayed with the seller.

The theme is ownership of the entitlement, not the size of the deployment. A combined estate can be genuinely covered in aggregate yet present as a shortfall because the proof of who owns what has not been assembled.

How we harmonise defensibly

Build one entitlement ledger

We assemble a single ledger from both sides, anchored on the Proof of Entitlement records rather than deployment snapshots, and flag every entitlement whose transfer is not yet documented. That ledger is the baseline the combined estate is measured against, and it is what a clean Proof of Entitlement trail exists to support.

Sequence the transfers

Where entitlements need to move between entities, we prioritise the ones tied to the largest deployments and the highest risk products, so the most material exposure is closed first. If an audit is already in motion, that sequencing feeds directly into settlement negotiation, turning an open transfer question into a managed term rather than a finding.