Paying for the same software twice is one of the easiest leaks to miss in a separation. Here is how buyers design it out.
Carve out and the risk of double licensing describes the very common outcome where a separating business ends up paying for the same software twice, once through the parent during the transition and again under its own new contracts. It is pure duplicated spend, it is entirely avoidable, and it is one of the easiest leaks to miss because the two charges sit on different ledgers managed by different teams.
During a carve out the new entity usually relies on the parent for software through a transition services agreement, paying pass through fees for sublicensed access. At the same time it is racing to stand up its own contracts before the TSA ends. The danger sits in the overlap. If the new agreements switch on before the parent billing switches off, the business pays for both at once. If the buyer already licenses the same publisher elsewhere, the new entity contract duplicates entitlement the group already owns. If a shared platform is split without reconciliation, both sides count the same users against separate licences. Each of these is double licensing, and each lands quietly.
The reason it goes unnoticed is structural. The TSA charges flow through the separation programme, while the new contracts flow through procurement, and no single owner is watching both. By the time finance reconciles the full picture, months of duplicated spend may already be sunk.
Double licensing tends to appear in five recurring scenarios. TSA overlap with new contracts is the most common, where the parent keeps billing sublicensed software after the new entity has signed its own. Early re licensing creates a parallel running window when new agreements are switched on before parent access is switched off. Buyer estate overlap happens when the acquirer already holds an agreement with the same publisher the new entity is signing. Shared platform double counting arises when both sides count the same users. Forgotten auto renewals keep parent subscriptions alive long after the unit has gone. The table sets out how to remove each one.
| Scenario | What gets paid twice | How to remove it |
|---|---|---|
| TSA overlap with new contracts | Parent bills sublicensed software while the new entity already signed its own | Align contract start dates with TSA exit, not before |
| Early re licensing | New agreements switched on before parent access is switched off | Stagger cutover so old and new do not run in parallel longer than needed |
| Buyer estate overlap | The buyer already licenses the same publisher the new entity is signing | Consolidate onto the buyer agreement where terms allow |
| Shared platform double count | Both parent and new entity count the same users against separate entitlements | Reconcile deployment to entitlement on both sides |
| Forgotten auto renewals | Parent subscriptions renew automatically after the unit has left | Inventory and cancel on a tracked schedule |
Catching these overlaps is part of our carve out and TSA separation service, and it connects to the wider carve out and TSA software playbook. It also draws directly on the work in stranded software costs in a carve out.
A buyer carving out a 600 person business signed its own Microsoft and collaboration agreements early, keen to show the new entity standing on its own feet. The contracts went live three months before the TSA ended. During those three months the parent continued to bill the same software through the TSA schedule, because the sublicensed access had not been switched off in step with the new contracts going on. The business paid for both. On a separate front, the buyer group already held an agreement with the same security publisher the new entity had just contracted independently, so the group was now paying for two overlapping entitlements for one population of users.
Neither overlap was the result of negligence. The separation team owned the TSA schedule and was focused on exit readiness. Procurement owned the new contracts and was focused on getting the entity operational. Each did its job, but no one held a view across both ledgers, so the overlap was nobody specific responsibility. It surfaced only when finance reconciled the combined picture two quarters later, by which point the duplicated spend was already sunk.
The composite captures why double licensing is a coordination problem rather than a competence problem. The defence is structural: one owner, one reconciliation that puts the parent billing, the TSA schedule and the new contracts in a single view, and a cutover calendar that aligns the switch off of old access with the switch on of new contracts. With that view in place, every overlap is visible before it is paid, and the cutover window is deliberately short rather than accidentally long.
The fix is coordination, not heroics. A single reconciliation that maps the parent billing, the TSA schedule and the new entity contracts side by side exposes every overlap before it is paid. The most powerful control is aligning contract start dates with the TSA exit rather than signing early, so the business never runs both at once for longer than a planned cutover window. Where the buyer already licenses a publisher, consolidating the new entity onto the existing agreement removes the duplication entirely and often improves the volume position. Where shared platforms are split, a deployment to entitlement reconciliation on both sides stops the same users being counted twice.
Governance is what keeps the fix in place after the cutover. The single owner who reconciles both ledgers should hold that view until the TSA is fully exited and the parent billing has stopped in full, not just until the new contracts go live. Auto renewals deserve particular attention, because a parent subscription that quietly renews after the unit has left can reintroduce duplication months after everyone believed the separation was complete. A short standing review of the combined contract and billing position, run through the first year of independence, catches the overlaps that a single point in time reconciliation would miss.
This is the same measurement discipline that drives negotiating software terms for the new entity and re licensing the carved out business from scratch. One reconciliation, mapped across both ledgers, removes the duplication that no single team can see alone.
Related reading includes separating shared software licenses and exiting the TSA cleanly on software.
We map both ledgers in one reconciliation so every overlap is caught before it is paid.
Request a carve out software assessment