The seller decisions on transfer, consent and TSA pricing become the buyer opening position. Here is how to read them.
Carve out software licensing for the seller covers what the parent must confirm, transfer, service and bill as a business unit separates, and it directly shapes the risk and the cost the buyer inherits. Even on the buyer side, understanding the seller obligations is essential, because the seller decisions on transferability, consent and TSA pricing become the new entity opening position.
The seller sits at the centre of the software separation. The parent holds the master agreements, the publisher relationships and the entitlement records, and it must decide what stays, what transfers and what is serviced through a transition services agreement. Three zones result. Group wide commitments and retained systems stay with the parent. Unit specific applications and dedicated licences transfer to the new entity where the contracts allow. Everything in between sits in the TSA shared zone, where the seller sublicenses parent software to the new entity for a fee until the new entity stands up its own contracts.
For a buyer, the most important point is that the seller obligations are not abstract. They set the terms of the deal. If the seller promises to transfer rights that actually require publisher consent, and never secures that consent, the buyer inherits a gap. If the seller services the TSA inaccurately, the buyer pays inflated pass through fees. The seller licensing position is the buyer starting position.
Five seller obligations carry the most weight, and each has a direct buyer side consequence. The seller must confirm what is genuinely transferable, because a promise that depends on consent the parent never obtains leaves the new entity exposed. The seller must service the TSA accurately, because over billing or under delivering sublicensed software during transition shows up as stranded cost on the buyer ledger. The seller must manage publisher consent carefully, because raising the transaction clumsily can trigger an audit on the parent estate that spills onto the new entity.
The seller must also true up its retained estate honestly, since minimums sized for usage that has left are often reflected in the TSA price the buyer pays. And the seller must hand over clean entitlement records, because incomplete data forces the new entity to re license blind and over buy. The table summarises these obligations and the buyer concern attached to each.
| Obligation | Risk if mishandled | Buyer side concern |
|---|---|---|
| Confirm what is transferable | Promising rights that need publisher consent the seller never secures | The buyer inherits a gap and an access risk |
| Service the TSA accurately | Over billing or under delivering sublicensed software during transition | Inflated pass through fees and stranded cost |
| Manage publisher consent | Triggering an audit on the parent estate by raising the transaction clumsily | Audit exposure can spill onto the new entity |
| True up the retained estate | Carrying minimums sized for usage that has left | Reflected in TSA pricing the buyer pays |
| Hand over clean records | Incomplete entitlement data slows the new entity stand up | Re licensing starts blind and over buys |
A buyer side advisor reads these obligations from the buyer perspective inside our carve out and TSA separation service, and the wider carve out and TSA software playbook sets out how the two sides interact through the whole separation.
The seller licensing position is not fixed. It bends with the structure of the transaction, and a buyer that understands the interaction can anticipate where the obligations will be hardest to meet. In a stock purchase, where the legal entity itself changes hands, many contracts can travel with the entity, but change of control clauses still apply and can require notice or consent. In an asset purchase or a true carve out, where only selected assets move to a new entity, anti assignment clauses bite directly, because each contract has to be assigned and most assignments need publisher consent. The seller obligations are heaviest in exactly the structures buyers most often use for carve outs.
This is why a buyer side review reads the seller commitments against the deal structure rather than in the abstract. A seller promise to transfer a SAP or Oracle agreement means one thing in a stock deal and something quite different in an asset deal, where the same promise depends on a consent the publisher is under no obligation to grant on the original terms. As of June 2026, publishers including Oracle and SAP are well known for treating assignment requests as an opportunity to reprice, which turns a routine transfer into a commercial negotiation the seller may not be motivated to win on the buyer behalf.
The practical consequence is that the buyer cannot rely on the seller to protect the buyer interest in these conversations. The seller goal is a clean exit. Where the structures make transfer difficult, the buyer needs its own visibility into which contracts are at risk, what consent each requires, and what the fallback is if consent is refused or repriced. That visibility is commercial diligence, and it belongs to the buyer, not the seller. For the legal interpretation of any specific clause, the buyer should engage its own counsel.
The seller and buyer interests align less than they appear. The seller wants a clean exit and a TSA that recovers its costs. The buyer wants accurate transfers, fair TSA pricing and no inherited audit exposure. The gap between those positions is settled in the transaction documents and the TSA schedules, which is exactly where a buyer side software review earns its fee. Reviewing the seller licensing assumptions before signing lets the buyer price the gaps, scope the warranties and time box the TSA charges before they become fixed.
This work pairs naturally with the buyer focused view in carve out software licensing for the buyer and with divestiture software licensing for the parent, which looks at the same separation from the seller side in more depth.
See also separating shared software licenses and carve out software audit risk for both sides.
We read the seller licensing position so you can price the gaps and time box the TSA before signing.
Request a carve out software assessment