SAP Licensing in Mergers & Acquisitions: What Happens to Your Licences When Companies Merge

Why M&A Is an SAP Audit Trigger

SAP licensing in mergers and acquisitions creates immediate compliance exposure that most legal and IT due diligence teams are not equipped to identify. SAP monitors corporate transaction announcements — public filings, press releases, regulatory notifications — and uses these as triggers for commercial engagement. In many cases, SAP's account teams contact a newly combined entity before the ink on the acquisition agreement is dry.

The reason is straightforward: corporate transactions routinely create out-of-scope use of SAP licences. When Company A acquires Company B, employees of Company B who begin accessing Company A's SAP systems are not covered by Company A's Named User licences unless their licences have been properly transferred or newly purchased. SAP's licence metrics are granted to specific legal entities, and changes in corporate structure create gaps that SAP's commercial teams are trained to identify and monetise.

This is not a theoretical risk. Our SAP licence compliance team has reviewed dozens of post-merger SAP positions where the acquiring entity was unaware of the licence exposure created by the transaction. In one case, a financial services firm that acquired a mid-sized processing company found itself facing a €14M SAP back-licence claim for users who had been accessing systems unlicensed for 18 months post-close.

SAP licensing in M&A is a specialist discipline. The combination of contractual complexity, Named User classification rules, and SAP indirect access risk creates a compliance landscape that requires forensic analysis to navigate safely.

How SAP Licence Rights Transfer — and When They Don't

SAP licences are granted to the specific legal entity named in the Master Agreement and Order Forms. This is not a technicality — it is the contractual foundation that SAP enforces during M&A events. When corporate structures change, the licence rights that exist within them must be explicitly addressed.

Asset Purchases vs Share Purchases

The structure of the transaction determines how SAP licences are treated. In a share purchase (where the buyer acquires the shares of the target company), the target's legal entity — and its SAP contracts — transfer to the acquirer as part of the acquisition. The SAP licences survive, though they remain attached to the original legal entity and may need to be restructured if the target is to be integrated into the acquirer's SAP landscape.

In an asset purchase, the target's SAP licences do not automatically transfer to the buyer. SAP licences are not typically classified as tangible assets that pass through an asset purchase without specific assignment. SAP's standard T&Cs require SAP's written consent for licence assignment, and SAP routinely uses this consent process as a commercial opportunity — requiring the buyer to purchase additional licences or upgrade existing ones as a condition of assignment.

This distinction is critical and is frequently overlooked in due diligence. If you are acquiring assets from an SAP customer, assume that the SAP licences will require renegotiation unless your advisors have confirmed otherwise.

Surviving Entity and Consolidated Landscapes

When two SAP customers merge and plan to consolidate onto a single SAP landscape, the licence position becomes significantly more complex. Users from both entities must be licensed under a single Master Agreement, user type classifications must be verified across the combined population, and any duplicate or conflicting licence grants must be resolved. SAP will typically require a formal Effective License Position (ELP) to be conducted before approving any consolidated licensing arrangement.

Before agreeing to SAP's proposed ELP process, engage independent advisors. SAP's ELP methodology is designed to identify compliance gaps — and the ELP results become the baseline for SAP's commercial proposal. An independent pre-ELP analysis gives you the ability to challenge SAP's numbers from a position of evidence rather than reacting to their findings after the fact.

The User Count Shock After a Merger

The most common post-merger SAP licensing problem is a rapid, unexpected increase in Named User counts. When the HR systems, Active Directory directories, and SAP user management functions of two organisations are consolidated, the combined user count almost always exceeds the sum of what each organisation had licenced independently. This happens for several structural reasons.

First, most organisations carry user licence overhead — professional users who have been reclassified from limited user types without properly adjusting their licence level, duplicate accounts, inactive accounts that were never deprovisioned, and test or training accounts that consume licence capacity without corresponding business value.

Second, the integration process itself creates new user provisioning. IT teams granting access to the new combined population often provision the highest available user type to avoid access issues — typically Professional or Limited Professional — without considering the cost implications.

Third, SAP's Named User type hierarchy means that users with even minimal transactional access require at minimum an Employee or Productivity licence. When Company B's employees are granted any access to Company A's SAP environment — even read-only access to a timesheet system — they may require full Named User licences under SAP's classification rules.

The financial exposure from user count growth post-merger can be material. Professional Named User licences are priced at €1,500–€4,000 each depending on the product and agreement. An organisation that finds itself 500 users over-deployed faces a back-licence claim of €750K to €2M before penalties or maintenance uplift is applied.

Indirect Access Risk in M&A

SAP indirect access — the use of SAP functionality through third-party systems that were not part of the original licence grant — is amplified significantly in M&A scenarios. The acquired company almost certainly has third-party systems that interface with SAP. If any of those interfaces create document-based transactions in the acquirer's SAP environment — Purchase Orders, Deliveries, Invoices, Goods Receipts — they may generate SAP Digital Access document charges that were not anticipated in the deal economics.

SAP Digital Access charges apply per document type at a rate that is set in your Order Form. A Delivery document costs approximately €0.30–€0.60 per document in a standard contract. A newly acquired logistics business processing 10 million deliveries annually through SAP could generate €3M to €6M in annual Digital Access charges that were invisible in the pre-acquisition due diligence.

The indirect access exposure from integration middleware is equally significant. If the acquired company uses MuleSoft, Dell Boomi, SAP Integration Suite, or any other iPaaS platform to integrate with SAP, the licence terms governing those integrations must be reviewed. Many integration licenses are company-entity-specific, and the change in corporate structure may void or limit existing permissions.

For a comprehensive analysis of how SAP indirect access works and how to defend against it, our full guide covers the mechanics in detail. Our SAP indirect access advisory service specifically addresses M&A scenarios.

SAP Licensing Due Diligence Checklist

SAP licensing due diligence must be performed before the transaction closes. Retroactive licence negotiations are always more expensive than pre-close discovery — once SAP knows the deal has closed, their commercial leverage increases significantly.

Negotiating Your SAP Position After a Deal Closes

If pre-close due diligence was not performed — or if the exposure identified post-close exceeds what was anticipated — the negotiation strategy must be adapted accordingly. SAP will be aware of the transaction and will have prepared a commercial proposal. The question is how to engage with SAP from a position of strength rather than reactive compliance.

The most effective leverage available to a post-merger SAP customer is the scale of the combined commercial relationship. A combined entity represents more annual revenue for SAP in maintenance, services, and future software. This commercial weight should be used explicitly in the negotiation: any resolution of the compliance gap should be bundled into a restructured enterprise agreement that delivers long-term predictability and meaningful discounts on the expanded licence estate.

Specifically, demand a comprehensive SAP contract negotiation that addresses: the compliance gap resolution terms (ideally with a limited look-back period and no penalties), a restructured Named User tier that reflects actual functional needs in the combined entity, and a maintenance fee structure that recognises the expanded commitment. SAP will resist all of these — but an informed buyer with a credible independent analysis has significantly more room to negotiate than SAP would prefer them to believe.

Our advisors recommend that all post-merger SAP negotiations include an independent Effective License Position analysis before any conversation with SAP begins. If you allow SAP to run their ELP first, their findings become the negotiating baseline. If you have your own evidence-based ELP, you can challenge their methodology, their classification decisions, and their commercial claims from a position of technical authority.

Handling Divestitures and Spin-offs

Divestitures present the inverse problem: the departing business unit must be carved out of the parent company's SAP licence estate and re-established with its own licences. SAP's approach to divestitures is predictably commercial — the divested entity must purchase its own licences at current list price, and the parent company typically cannot reduce its own licence commitments proportionally without triggering a formal renegotiation.

The most common divestiture scenario our team encounters is a situation where the parent company's SAP Enterprise Agreement was priced on the basis of total headcount or revenue that included the business being divested. Post-divestiture, the parent company is paying for more capacity than it needs — but SAP's contract terms typically lock in the commitment level for the remaining contract period.

Proactive planning before a divestiture is announced can create significantly better outcomes. If your organisation is planning a divestiture, engage advisors before the transaction is disclosed publicly. SAP's leverage is highest once they know a transaction is imminent — their ability to create conditions on licence separation diminishes when they believe it may not happen.

For a comprehensive view of how SAP licensing impacts strategic transactions, combine this analysis with our guides on SAP licence optimisation and SAP renewal negotiation strategy.

Frequently Asked Questions