SAP Change of Control Clauses Explained: Risks in M&A Deals

SAP Change of Control Clauses Explained: Risks in M&A Deals

Why Change of Control Clauses Matter in SAP Contracts

When companies merge or get acquired, SAP’s change of control clauses can become a hidden stumbling block.

These provisions give SAP a competitive advantage during corporate restructuring.

In plain terms, if your company goes through a merger or acquisition (M&A), SAP may treat it as a “license transfer” event. Without careful attention, you could face unexpected licensing demands or even contract termination at the worst possible time.

Read our guide for a full overview of all SAP Licensing & Mergers and Acquisitions risks.

Why should IT and procurement leaders care before a merger or acquisition? SAP often uses M&A events as an opportunity. They might insist on re-evaluating your licenses, pushing you to buy new licenses or upgrade to different products.

For example, SAP could claim that your old contract no longer applies after a merger, unless you re-sign under new terms.

If you haven’t planned for this, you might end up scrambling post-deal, facing compliance audits or being pressured into paying full list prices for licenses you thought you already owned.

In short, SAP’s change of control clause can turn an M&A into a licensing landmine. Proactive management of these clauses is crucial to avoid compliance violations and financial surprises.

It’s far better to neutralize the risk upfront than to let SAP dictate terms after the fact.

How SAP Defines Change of Control

Every SAP contract specifies what constitutes a “Change of Control.” Typically, it refers to any significant change in the ownership or corporate structure of the customer.

Common definitions include changes in majority ownership (for instance, if another entity acquires more than 50% of the company’s shares), mergers where the customer is absorbed or combined with another company, or even the sale of a substantial portion of assets.

In simple terms, if the company that signed the SAP contract is not the same entity afterward (because it has merged with or been acquired by someone else), SAP considers this a change of control.

SAP’s interpretation: SAP often interprets these events very broadly.

The moment such a change happens, SAP typically requires you to notify them and obtain consent to transfer or continue the license. If you don’t, they may claim you’re in breach of contract.

In many SAP agreements, there’s language that allows SAP to terminate the contract upon a change of control unless they explicitly agree to continue it.

This places the onus on the customer to obtain SAP’s approval in the event of an M&A transaction.

Why does SAP care?

From SAP’s perspective, a new owner or merged entity wasn’t part of the original deal, so they want the chance to re-price or re-negotiate. They might fear that a highly discounted contract could “fall into” the hands of a much larger company, or simply see a revenue opportunity.

As a result, SAP may demand that the new entity relicense the software (often at updated pricing or metrics) or, at the very least, submit to an audit to verify compliance under the new structure.

Example scenario:

Consider a company that spins off a division into a new standalone business.

SAP’s contract defined this spin-off as a change of control event. The new spin-off company continued to use the parent’s SAP system after separation. SAP objected, saying the licenses couldn’t be transferred so simply.

They treated the spin-off as a brand-new company with no rights under the original contract and triggered a €5 million license claim against the spin-off for continuing to use SAP without a new agreement.

This happened because the original contract’s change of control clause was broad, and no pre-arranged exception was in place for spin-offs. The parent company and new entity ended up in a costly negotiation with SAP after the fact.

For more SAP compliance risk awareness, read Indirect Access in SAP M&A: Hidden Licensing Traps.

Common Triggers During M&A

Various M&A scenarios can trigger SAP’s change of control clauses.

Here are the most common situations to watch out for:

• Acquisitions: When one company acquires another, a change of control is typically triggered for the acquired entity. If your company (Company A) acquires another company (Company B), either Company A or Company B’s SAP contracts could have change of control provisions. For example, if Company B is an SAP customer, its contract likely says it can’t be assigned or transferred without SAP’s consent. Even if Company A also uses SAP, you can’t simply merge Company B’s licenses or users into Company A’s contract without dealing with SAP. The acquisition effectively changes who “controls” the SAP licenses at Company B, so SAP gets a say.
• Mergers: In a merger of two companies (especially if both are SAP customers), at least one of the original entities changes control. Two SAP environments might need to be combined, or one phased out. SAP will view this consolidation as an event that requires review and attention. We’ve seen cases where, after a merger, SAP insisted one of the contracts be terminated and all licenses consolidated under a new contract – often on SAP’s newer pricing terms. Even in a merger where one name survives, that legal change can trigger the clause.
• Spin-offs/Divestitures: When a company carves out a subsidiary or business unit and makes it an independent company, that new entity has no automatic rights to the parent’s SAP licenses. The act of divesting or spinning off constitutes a change of control, as the spun-off business is no longer an affiliate of the original license holder. Unless provisions were made, the spin-off might suddenly find itself without a valid SAP license, even though it’s still running SAP. This is a classic situation where SAP will demand that the new entity purchase its licenses, or the parent must pay extra to cover the spin-off during transition.
• Internal Reorganizations: Sometimes, even internal changes can unintentionally trigger SAP’s radar. This could involve a restructuring where, for instance, a subsidiary holding the SAP contract merges into another internal entity, or the company changes its legal name or ownership structure (e.g., establishing a new holding company on top). If the SAP contract language is strict, these changes may technically constitute a transfer or assignment of rights. For instance, moving assets between subsidiaries or a private equity firm acquiring a controlling stake in the company could be considered a change of control. These “stealth” triggers often catch many teams off guard, as the business may view it as a trivial legal change, but SAP sees an opportunity to reassess the deal.

In all these cases, the key is that something about the legal identity or ownership of the SAP customer is changing. That’s the moment SAP’s change of control clause kicks in, and SAP will review whether they need to approve continuing the license, or whether they want to renegotiate terms.

The Risks for IT and Business Leaders

Failing to address change of control clauses ahead of time can create a minefield of risks for IT departments, procurement teams, and the business as a whole.

Here are the major risk areas and why they matter:

• Compliance Risk: If an M&A event increases your SAP usage or changes who is using it, you might unknowingly violate license terms. SAP can conduct a post-merger audit and discover, for example, that thousands of new users are accessing SAP without proper licenses. The result could be a hefty compliance penalty or forced purchase. Essentially, the usage of your merged or acquired entity might not be covered, and SAP audits are rigorous.
• Financial Risk: M&A can lead to surprise cost escalations. SAP may require you to purchase new licenses at the full list price (with little to no discount) to cover the change, or they may use the event as an opportunity to eliminate previous discounts. If your original contract is voided or needs renegotiation, you could lose favorable pricing. This can result in millions of euros in unplanned costs, erasing some of the synergies the deal was intended to create.
• Operational Risk: Uncertainty around licensing can delay integration projects. If it’s unclear whether you can legally combine systems or add new users, IT may have to put integration on hold. Imagine planning to integrate the acquired company’s operations into your SAP system, only to be told, “Wait until we sort out licensing with SAP.” This hinders the realization of business synergy and creates frustration at the executive level. In worst-case scenarios, parts of the business may operate in limbo or run duplicate systems, incurring additional overhead, until the SAP situation is resolved.
• Contractual Risk: Broad change of control language gives SAP the upper hand. If the clause is too loosely defined, SAP can interpret almost any corporate change as a trigger for action. This means the vendor controls the interpretation and timing – they decide if your scenario counts and when to enforce it. That leverage can be used to pressure you into accepting their terms. A minor ownership change or internal reorg that you thought was insignificant could become SAP’s chance to reopen your contract. Essentially, a poorly negotiated clause is a contractual “poison pill” that tilts the power balance in favor of SAP.

To summarize these risk categories and their impact, here’s a quick reference table:

As the table shows, a change of control clause is not just legal fine print – it can translate into real business impact. Compliance issues can become financial liabilities, and contractual loopholes can stall your integration plans.

The good news: with the right strategies, these risks can be anticipated and mitigated before they become problems.

Negotiation Strategies for Change of Control Protection

To avoid nasty surprises, it’s critical to address change of control clauses during contract negotiations or renewals – ideally, well before any M&A activity is on the horizon.

Here are key strategies to protect your organization:

• Narrow the Definition of “Control”: Don’t accept overly broad language. Ensure the contract defines change of control as only a significant, material change – for example, a transfer of majority ownership or a merger where your company is not the surviving entity. By narrowing the definition, internal minor reorganizations or small equity investments won’t trigger the clause. The goal is to prevent SAP from making trivial changes audible.
• Pre-Negotiate Affiliate and Subsidiary Coverage: A powerful approach is to expand the definition of the licensed entity to include future majority-owned affiliates or newly acquired subsidiaries. In negotiations, request language that explicitly allows any company you acquire (above a certain ownership threshold, such as 50%) to use the software under the existing contract. This way, if you buy a company, you don’t immediately have to buy them new licenses at full price. Similarly, if you spin off a company, negotiate a provision that allows for a grace period or an option for the spin-off to continue using SAP (perhaps via a transitional use license) without immediate violation. Essentially, bake M&A flexibility into the contract.
• Include Continuity Clauses (M&A Neutrality): Strive for an M&A neutrality clause, which is language stating that the current pricing, discounts, and terms remain valid through a merger or acquisition. For instance, a continuity clause might state that if the customer changes control, SAP will not terminate the agreement, and the existing license metrics and prices will continue for a specified period (or will be transferred to the new entity). This removes SAP’s ability to immediately jack up prices or void discounts post-deal. Even if SAP insists on a new contract eventually, a continuity clause can ensure you have a stable period during which the integration can happen without disruption or ransom.
• Negotiate Audit Restrictions During Transitions: Given SAP’s tendency to audit after significant changes, it’s wise to negotiate a grace period or limitations on audits surrounding M&A transactions. For example, you might negotiate that in the event of an acquisition, SAP will not audit the new combined company for, say, 12 months post-close (or that any audit will exclude the new entity for a period). At a minimum, secure an understanding that simply having more users due to a merger will not be treated punitively if you inform SAP and work in good faith to reconcile licenses. The aim is to avoid an aggressive compliance audit the moment you merge, when you’re most vulnerable.
• Leverage the Deal’s Strategic Value: Remember that a merger can also make you a bigger customer for SAP, which gives you leverage. Use that during negotiations: if SAP wants to sell you their cloud offerings or an S/4HANA upgrade, tie it to them granting leniency on change of control. For instance, you might say, “We’ll consider moving to S/4HANA as part of this acquisition’s integration, but we need assurance that our current licenses transfer without extra cost.” Use SAP’s sales interest to extract contractual protections.

Example – A Procurement Victory:

One procurement lead at a global firm anticipated an upcoming acquisition and smartly negotiated both affiliate coverage and a continuity clause into their SAP contract renewal. Sure enough, a year later, the company acquired a smaller competitor.

SAP immediately invoked the change of control clause, demanding the new subsidiary’s users be relicensed, quoting an exorbitant €10M for a new license deal.

However, thanks to the negotiated protections, the company’s team pushed back: the contract already allowed newly acquired affiliates to be added without additional license fees, and guaranteed that existing discounts would carry over.

Faced with this, SAP backed off its demands. The result: the customer avoided that €10M relicensing cost entirely. This example highlights how proactive negotiation can counter SAP’s typical approach.

Example Scenario — IT Leadership Neutralizes Change of Control Risk

To illustrate how these strategies play out, let’s walk through a simulated case step by step:

• Scenario: A global enterprise (Company X) acquires a regional company (Company Y) that has its own SAP system and licenses. Company X is aware of SAP’s change of control clause from the start.
• SAP’s Demand: Right after the acquisition announcement, SAP notifies Company X that Company Y’s use of SAP cannot continue under the old contract due to the change of control. They insist that Company X must sign a new license agreement to cover Company Y’s SAP users and systems. SAP’s proposal comes with a hefty price tag — e.g., a fresh license purchase at list price, plus a requirement to move to the latest SAP products.
• IT Leadership’s Response: Fortunately, Company X’s IT and procurement leadership anticipated this. In Company X’s master SAP agreement (signed the previous year), they had pre-negotiated an affiliate inclusion clause and ensured continuity of pricing. This clause explicitly states that if Company X acquires a company, the acquired entity’s SAP use is covered under Company X’s existing contract terms for a minimum of 12 months, with all original discounts intact. Armed with this clause, the IT leadership informs SAP that the change of control is contractually covered and that SAP’s demand for a new agreement violates the negotiated terms.
• Outcome: Confronted with the contractual language, SAP backs down. They acknowledge that as long as Company Y’s usage stays within the agreed scope, no immediate relicensing is required. The integration of Company Y into Company X’s SAP landscape proceeds smoothly and without additional costs. The result is a seamless transition: zero incremental license spend and no disruption. The IT team’s foresight in securing change of control protections turned what could have been a multimillion-euro surprise into a non-event.

This scenario highlights a critical lesson: with the right clauses in place, IT leadership can effectively mitigate SAP’s leverage during M&A and maintain the tech integration on track.

IT Leadership Checklist for Managing Change of Control Clauses

Every IT and procurement leader involved in SAP and M&A should proactively address change of control clauses.

Use this checklist to ensure you’re covered:

• ☐ Review current SAP contracts for Change of Control language. Know exactly what your contract says. Is there a clause that triggers on an acquisition or merger? Does it allow any transfer at all? This is the starting point for risk assessment.
• ☐ Narrow definitions of “control” to major changes only. If your contract is up for negotiation or amendment, refine the change of control clause. Exclude minor stake changes or internal restructurings. Make it clear it applies only to significant events (like a sale of the company or merger with a third party).
• ☐ Negotiate continuity clauses for M&A neutrality. Aim to insert a clause that guarantees the contract (and pricing) remains in effect post-merger or acquisition. This can be framed as “M&A shall not itself cause price increases or termination of this agreement for a defined period.”
• ☐ Ensure affiliate and subsidiary coverage is explicit. Your contract should allow your affiliates (companies you own) to use the SAP systems. Push for wording that automatically includes future affiliates acquired above a certain ownership threshold. This way new acquisitions inherit the rights to use your SAP environment without breaching the agreement.
• ☐ Add audit restrictions during transition periods. If possible, get terms that prevent SAP from conducting surprise audits immediately following an M&A event, or limit the scope (e.g., they can audit the original environment but not penalize added users for a grace period). This gives you breathing room to true-up licenses if needed, rather than dealing with an audit when you’re busiest integrating.
• ☐ Benchmark to resist SAP relicensing uplift. Always know the market pricing. If SAP does push for new licenses, having benchmark data for similar deals helps you negotiate. Also, when negotiating M&A protections, use benchmarks to argue why continuity is fair (e.g., “Our discount is standard for our size; a merger shouldn’t erase that”). Arm yourself with data so SAP can’t take advantage of an information imbalance.

By following this checklist before any merger or acquisition, you’ll greatly reduce the risk that SAP’s change of control clause catches you off guard.

Preparation is key – once the deal is underway, your leverage to negotiate better terms with SAP is much weaker.

5 Recommendations for IT & Procurement Leaders

To wrap up, here are five high-level recommendations for IT and procurement professionals to manage SAP licensing risks in M&A scenarios:

1. Audit existing SAP contracts for change of control exposure. Proactively identify any problematic clauses now. If you encounter “poison pill” language, develop a plan (such as renegotiation or at least awareness of the risk) before entering an M&A deal. Surprises only help SAP, not you.
2. Treat M&A neutrality as a must-have goal in negotiations. When renewing or signing new SAP agreements, make neutrality in M&A a priority. Don’t treat it as a minor legal footnote – it’s as important as pricing or discounts because it protects those very terms in a merger.
3. Secure affiliate coverage in advance of acquisitions. If you anticipate growth by acquisition (or even if you don’t, since plans can change), ensure your SAP license scope is flexible. It should allow the addition of new business units or legal entities without incurring immediate penalties. This foresight can save you huge costs down the road.
4. Use continuity clauses to preserve existing price levels. Lock in your discounts and caps. For example, negotiate that any additional licenses required due to a merger will be priced at the same discount percentage as your current agreement. This prevents SAP from using the event to reset you to the list prices.
5. Make change of control protections part of the M&A due diligence process. When your company is contemplating a merger or acquisition, involve the IT procurement team early. Evaluate the target’s SAP status: What contracts do they have? Are there any licensing landmines? Plan how you’ll integrate or whether you need SAP’s consent. This should be a checklist item in any due diligence process, right alongside financial and legal due diligence. Don’t wait until after the deal closes to address it.

By following these recommendations, IT and procurement leaders can act as strategic advisors during mergers and acquisitions (M&A), ensuring that SAP licensing doesn’t derail the business objectives of the deal. Remember, the best time to defuse a bomb is before it’s ticking – and that’s exactly what a well-handled change of control clause is doing for your M&A plans.

FAQ

How does SAP define “Change of Control” in contracts?

SAP typically defines a change of control as any significant change in the ownership or control of the customer. This typically includes events such as a merger, the acquisition of the customer by another company, or the sale of a controlling stake in the company. In practical terms, if another entity acquires your company or you merge with another company, SAP considers this a change of control. The specific wording can vary, but it often covers direct or indirect changes in ownership of more than 50% of voting rights or a change in the entity that ultimately controls the customer. The key is that SAP sees the customer as “not the same” after the event, which triggers special provisions in the contract.

Can SAP force relicensing after an acquisition?

Yes, if your contracts aren’t prepared to handle it, SAP can effectively force relicensing after an acquisition (or any change of control). They do this by either terminating the old contract or refusing to recognize the transfer of licenses to the new entity. For example, if you acquire a company that has its own SAP license, SAP may require you to sign a new agreement to cover the acquired installation. Or, if your company is acquired by someone else, SAP’s consent may be required to continue using the software, and they may condition that consent on signing new licenses. In many cases, “forcing relicensing” means SAP asks the new combined entity to purchase licenses as if it were a new customer, potentially at less favorable terms. However, with the right contract clauses (like continuity and affiliate use provisions negotiated in advance), you can prevent or limit SAP’s ability to compel a full relicense.

What protections can IT leaders negotiate in advance?

IT leaders and procurement can negotiate several protections into SAP agreements before any M&A takes place:

• Affiliate Use Clauses: Language that allows any company you acquire (that meets certain criteria, e.g., you own more than 50% of it) to use your SAP licenses. This avoids immediate license violations when you add new subsidiaries.
• Continuity or Neutrality Clauses: Provisions that maintain the same contract terms and pricing despite a change of control, at least for a transitional period. Essentially, it neutralizes the M&A event so SAP can’t use it to change the deal on you instantly.
• Consent for Transfer: Pre-approval language where SAP agrees not to unreasonably withhold consent for transferring the contract to a new entity or reorganizing internally. Even better, get SAP to agree to automatic novation to an acquirer, provided certain conditions are met.
• Transition Assistance Agreements: In some cases, companies negotiate a clause that in the event of a divestiture, SAP will allow a temporary use of the software by the spun-off entity for X months, giving time for that entity to negotiate its deal or migrate off.
• Audit Grace Period: As mentioned earlier, a clause to prevent or limit audits immediately after an M&A can be negotiated.
  By securing these protections in your contracts ahead of time, you give your organization a safety net. You’re effectively taking away SAP’s element of surprise and leverage when a merger or acquisition happens.

How do change of control clauses impact affiliates and subsidiaries?

Change of control clauses and related contract language determine whether your affiliates and subsidiaries can use the SAP software under your master agreement.

In many standard SAP contracts, usage rights are limited to the named licensee and its majority-owned affiliates (which may be explicitly listed or defined). If a subsidiary is wholly or majority-owned, it can often use the software under the parent’s license, provided the contract defines “Customer” to include affiliates.

Problems arise when:

• You acquire a new subsidiary that wasn’t originally named – if your contract doesn’t automatically cover new acquisitions, that subsidiary’s use of SAP might not be allowed until you add them (which could mean buying more licenses).
• If you divest or a subsidiary leaves your corporate structure, that former affiliate immediately loses any rights under your contract, because it’s no longer “your” affiliate. Without a plan, that means they must stop using SAP or quickly secure their deal.
  In short, change of control clauses can limit or permit the extension of licenses to affiliates. It’s critical to clarify the definition of affiliate usage in your contract. Ideally, ensure any entity in which you hold more than 50% ownership is covered. This way, when your corporate family changes (through acquisitions or spin-offs), you know exactly who is allowed to use the licenses. Getting this wrong can either leave a new affiliate unable to use SAP (hurting business continuity) or inadvertently allow use where it shouldn’t (creating compliance risk).

What steps should leadership take before any merger or acquisition regarding SAP?

Before any merger or acquisition, IT and procurement leadership should take the following steps related to SAP licensing:

1. Due Diligence on Contracts: Immediately review the SAP contracts of your company and, if possible, the target company. Identify any change of control, assignment, or transfer clauses that will be triggered. Understand the licensing position of both entities (What licenses exist? What is the usage? Any compliance gaps?).
2. Engage with SAP Early (Carefully): In some cases, it makes sense to approach SAP early and discreetly for guidance or to negotiate terms for the upcoming change. This can be delicate – you don’t want to signal weakness or urgency. But if you have a good relationship or a large deal, discussing how to make the transition smooth (on the condition of preserving terms) can set the stage. Alternatively, some companies choose to keep SAP at arm’s length until they have a solid plan internally.
3. Plan License Integration or Separation: Depending on the scenario (merger vs. divestiture), plan how you will integrate or separate SAP environments. If merging two SAP-using companies, decide which contract will survive or if a new consolidated contract is beneficial. If separating, plan for the departing unit’s SAP access (e.g., a temporary license extension or a clean cut-off).
4. Negotiate Before Closing: If you identify that SAP will require a new contract or additional licenses, negotiate that before the deal closes whenever possible. Pre-closing is when you often have more leverage (the deal isn’t final, and both sides want to avoid post-close chaos). For instance, you might negotiate with SAP for a merged contract that only modestly increases cost, rather than waiting and paying more later.
5. Include in M&A Agreements: Make SAP licensing a point in the merger or purchase agreement between companies. For example, if you’re acquiring a company, ensure the seller addresses any open SAP compliance issues (perhaps by obtaining extra licenses or providing a warranty that they comply). Also, define who is responsible for any fees SAP might charge due to the change of control. This way, if SAP comes knocking for a big bill, there’s clarity on whether the buyer or seller handles it (or if the cost was factored into the purchase price).
6. Internal Alignment: Brief your leadership (CIO, CFO, etc.) about the implications of SAP’s clauses. They must understand early on that “we might need to allocate budget or negotiation effort to handle SAP.” Setting this expectation ensures you get support for whatever strategy you need to execute (whether it’s tough negotiating with SAP or investing in license rationalization).

By taking these steps before a merger or acquisition is finalized, you significantly reduce the chance of being blindsided by SAP-related issues during the hectic post-merger integration.

Essentially, you’re bringing SAP licensing into the overall M&A planning process, rather than treating it as an afterthought – and that can make all the difference in avoiding compliance or cost surprises.

Would you like to learn more about how we can support your organization with SAP during mergers and acquisitions?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit