Mergers, acquisitions, divestitures and contract consolidation. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back. Session thirty eight, and today is what happens to your licensing when the company itself changes shape. Mergers, acquisitions, divestitures and the contract consolidation that follows. I want to warn you at the start that this is where I have seen the largest unplanned exposures in my career, and almost all of them were avoidable, because the questions that prevent them cost an afternoon and get asked too late. Today: why the licence does not follow the company, the four clauses that decide everything, what a divestiture really does to your costs, and how to use consolidation. Three knowledge checks. Let's begin.
Five objectives. First, know the licence does not transfer automatically, because a grant is to a named entity for a defined scope, so change either and the grant may no longer cover you. Second, read the four clauses that matter: assignment, change of control, affiliate definition and territory, since everything else follows from those. Third, handle a divestiture honestly, because users leave and the commitment usually does not, and the buyer will need service from you on day one. Fourth, treat consolidation as a negotiation, since two agreements meeting is one of the better opportunities you will get to fix terms. And fifth, get into due diligence, because four questions asked before the deal are worth a quarter of work afterwards.
Four things to frame it. Named entity, because the grant is to a legal person, and a new parent or a new subsidiary is not automatically that person. Defined scope, since use is permitted for your business as defined and an acquired business is often not inside that definition. Day one exposure, because integration starts immediately and paperwork does not, and the gap is where findings are created. And discovered late, usually twelve months later at a measurement, with no leverage and no easy remedy. Let me explain why this catches people, because the assumption behind it is entirely reasonable.
Guest analyst clip.
Cheap to ask before the deal and expensive to answer afterwards. That is the whole session in a sentence, and notice that it is a timing problem rather than a knowledge problem. The clauses are not hard to read. They are simply read at the wrong moment.
So, acquisition, four questions, ideally asked before signing rather than during integration. Can they use ours: does your agreement's affiliate definition cover a newly acquired entity, and from when, because some require notification. Can we use theirs: their SAP agreement may not survive the change of control, or may need consent to assign. What is the combined volume: users, engines and documents added together, which is a new number and it may cross a tier. And what is duplicated: two ERPs, two support contracts, overlapping modules, because genuine savings live there alongside real exposure. The pattern to avoid is integration proceeding at deal speed while licensing arrives at contract speed, and only one of those two is negotiable afterwards.
First knowledge check. You acquire a company and its three thousand staff start using your SAP system on day one. What is your position? A, covered, since they are now part of your organisation. B, it depends entirely on the affiliate definition in your agreement. C, covered for a grace period, which is standard. D, their own SAP licences transfer across to cover it. Pause here and pick an answer before you continue.
B. Affiliate definitions vary enormously: some cover majority owned entities automatically, some require the entity to have existed at signature, some require notification or consent, and some are silent, which is its own problem. A is the assumption that produces most acquisition findings, because organisational logic and contractual language are different things. C describes a grace period that exists in some agreements and is not a market standard you can rely on. And D assumes assignability, which is exactly what the change of control clause governs.
So, the four clauses, and the question to ask of each. The affiliate definition controls which group entities may use the software, and the question is whether it covers entities acquired after signature. Assignment controls whether the agreement can move to another entity, and the question is whether you can assign on a sale and whether that needs consent. Change of control governs what happens if you are acquired, and the question is whether the agreement survives, terminates or needs renegotiating. And territory and scope control where and for whose business use is permitted, where the question is whether an acquired business in a new country falls inside it. Four clauses, one afternoon of reading, and the answers are the same whether the transaction happens next quarter or never.
Now divestiture, five points. Users go and the commitment stays, because without a reduction right your volume is unchanged, so you pay for people you no longer employ. Maintenance stays too, since support is charged on licence value, so the annuity from session thirty six continues at the same rate. The buyer needs service, which usually means a transition services agreement where you provide SAP to a company you no longer own. Third party access is restricted, and that arrangement is exactly what most agreements limit, so check before you sign the TSA rather than after. And entitlement rarely transfers, so the buyer generally needs their own licences, which is their problem commercially and yours operationally. Let me put the finance version of this plainly.
Guest analyst clip.
Precisely when nobody has time to negotiate an amendment. That is the practical difficulty. The transition services period is short, busy and highly visible, and it is the worst possible moment to discover that an arrangement everybody assumed was routine needs the vendor's written consent.
Second knowledge check. You divest a division with thirty percent of your SAP users. What happens to the licence cost? A, it falls by roughly thirty percent. B, it stays, unless you negotiated a reduction right in advance. C, it falls at the next annual measurement automatically. D, it transfers proportionally to the buyer. Pause here before you continue.
B. Commitments move up easily and down rarely, which is session twenty seven's point arriving as a corporate event, and the reduction right that would help is one you have to have negotiated before you needed it. A is what the divestiture business case usually assumes, and the gap between that assumption and the contract is a real number somebody will have to explain. C confuses measurement with entitlement, because the measurement will show fewer users and you will still owe the committed volume. And D is not a mechanism that exists by default, since the buyer needs their own agreement.
Right, consolidation, five points, and this is the opportunity in the session. Take the better terms from each, cherry picking deliberately rather than defaulting to whichever paper is larger. Harmonise the metric definitions, because two definitions of a named user will otherwise appear in every future measurement. Net out the duplication, so overlapping modules and two support streams, where the savings are real if somebody looks for them. Align the renewal dates, which is session thirty's co-term argument, and an integration is the cheapest moment to do it. And do it while the budget exists, because consolidation looks less urgent after eighteen months and the terms available shrink with the urgency. Let me say why both sides want this.
Guest analyst clip.
The terms available shrink accordingly. Which makes this one of the few situations in licensing where moving quickly is genuinely in your interest as well as theirs.
So, due diligence, four questions and an afternoon. What does the target run: vendors, products, versions and volumes, and it is not a valuation exercise, just a list. Can our agreement cover them: the affiliate definition applied to this specific entity, with the date it takes effect. Can theirs survive the change: change of control and assignment in their paper, which decides whether you inherit anything usable. And what happens on day one: who needs access before any paperwork exists, and what that access costs if it is not covered. Then put a number on it, and a range is fine, because a number in the deal model beats a caveat in an appendix nobody reads.
Five traps. Licensing hears after close, which is the most expensive pattern in this session and the easiest to fix with one invitation. Assuming the affiliate clause covers it, because it might, and the variation between agreements is enormous, so read it. A TSA with no licence check, since providing access to a divested business is third party use and third party use is usually restricted. Modelling savings that cannot happen, meaning a divestiture case assuming proportional licence reduction with no reduction right in the contract. And missing the consolidation window, because the best terms are available while integration is funded and urgent, and that window closes.
Last knowledge check. When does licensing add the most value in a corporate transaction? A, during integration, when systems are being merged. B, during due diligence, before the deal is signed. C, at the next annual measurement. D, at the next renewal, once the picture is clear. Pause here, and think about when the answers can still change the deal.
B. Before signature the answers can still change the price, the structure or the transition arrangements, and the questions cost an afternoon. A is where licensing usually gets involved, and it is already too late to affect anything except the size of the remedy. C is where the problem is discovered rather than solved, on the vendor's timing. And D is a year later still, with the exposure accrued and your position weaker. Let me be specific about how to get invited, because that is the practical obstacle.
Guest analyst clip.
Negotiating from inside a fait accompli. So, five things to be ready before the event. Summarise the four clauses now, one page per major agreement, in plain language, kept with the entitlement register. Get on the M and A checklist, because a standing line in the diligence template is worth more than being known to the team. Keep a day one playbook: what access can be granted immediately, what needs consent, and who signs it off. Ask for reduction rights routinely, at every renewal, as a standard ask, because you need it before the divestiture rather than during. And track the entities, meaning which legal entities are licensed and what changed at the last restructure, because that drifts silently.
Three sentences. A licence is granted to a named entity for a defined scope, so it does not automatically follow the company through an acquisition, a divestiture or a restructure, and the affiliate, assignment, change of control and territory clauses decide what actually happens. Divestitures are asymmetric because the users leave while the commitment and its maintenance stay, unless a reduction right was negotiated in advance, and the buyer will usually need service from you under an arrangement most agreements restrict. And consolidation after an acquisition is one of the better negotiating opportunities available, since both sides want it, so take the better terms from each paper and do it while the integration budget still exists. Next session is the relationship itself: account teams, partners, roadmap pressure and the annual calendar.
Homework before session thirty nine, about ninety minutes, and the first item is worth doing whether or not a transaction is anywhere near you. One, read the four clauses: affiliate, assignment, change of control and territory, and summarise each in one sentence you could hand to a lawyer. Two, check your entity list, asking which legal entities are named or covered and whether that still matches your group structure. Three, look for a reduction right, because if any agreement lets you reduce committed volume then you now know whether a divestiture is affordable. Four, find the M and A process, asking who runs due diligence in your organisation and whether IT licensing is on the checklist, then ask to be added. And five, review your last event, because if you have acquired or divested recently then somebody should be able to say what happened to the licence position.
Five guides, all on redresscompliance dot com. M and A and licensing events covers acquisitions, divestitures and the clauses that decide the outcome, which is the reference version of today. Affiliate and assignment clauses goes into what the four clauses actually say and how much they vary. Transition services and third party use covers serving a divested business without breaching your own agreement. Contract consolidation is about merging two estates and the terms worth cherry picking. And SAP negotiation and the fiscal calendar is session thirty seven's reference, which is how to run the consolidation negotiation itself.
That is session thirty eight. The thing to take away is that the licence does not follow the company, the four clauses decide what does, and the questions are cheap before the deal and expensive after it. Next time, running the SAP relationship deliberately. See you then.