Key Takeaways
- Seven distinct risk categories apply to SAP licensing in post-M&A environments — each requires a specific mitigation approach, not a generic "licensing review."
- The change-of-control notification risk is highest priority: a poorly timed or worded notification can hand SAP the commercial initiative at the worst possible moment.
- Indirect access exposure from the target's integration landscape is consistently the most underestimated M&A licence risk — and the most expensive when it surfaces.
- USMM timing risk is acute: SAP measuring the combined landscape before your independent analysis is complete is a commercially exploitable event that must be prevented.
- Proactive mitigation is always less expensive than reactive defence — the window to act is the 90 days immediately post-close.
SAP right-sizing after M&A involves a specific and well-documented set of risks. SAP's commercial and audit teams are experienced at M&A events — they've been through hundreds of them. They know which risks enterprises typically miss, and they're positioned to exploit each one. This article maps the seven most critical risks and the specific mitigation strategy for each.
For the full strategic context on M&A right-sizing, read our complete guide to SAP right-sizing after M&A. If you're looking for the practical methodology, see our practical enterprise guide. Our SAP licence optimisation advisory provides specific M&A risk assessment and mitigation support.
Risk 1: Change-of-Control Notification Timing
Premature or Poorly Framed Notification
SAP's ELAs require notification of a change of control, typically within 30–90 days. Most enterprises either notify too early (before their internal analysis is complete) or too late (breaching the notification deadline, creating a contractual default).
Notifying too early — before your ELP and reclassification analysis is complete — hands SAP's commercial team the M&A event as a sales trigger. SAP will immediately schedule a "strategic review" meeting, framed as helpful planning, which is in practice an intelligence-gathering exercise for SAP's upsell agenda. Your team enters that meeting without a prepared position.
Complete your internal licence analysis before notifying SAP. If the notification deadline is approaching before analysis is complete, send a minimal factual notification that satisfies the contractual obligation without disclosing your commercial position: confirm the transaction, identify the new contracting entity, and state that a detailed licence review is underway. Explicitly do not invite SAP to conduct its own measurement.
Risk 2: Indirect Access Exposure from Target's Integrations
Inherited Indirect Access Liability
When you acquire a company, you inherit its SAP integration landscape — including any indirect access exposure that the target had not identified or resolved. Third-party systems connecting to SAP via APIs, RFC connections, or batch interfaces may be creating Digital Access document obligations (Orders, Deliveries, Invoices, Material Documents) that require explicit licence coverage. If the target's contract predates SAP's Digital Access model, the inherited exposure may be completely undocumented.
SAP's audit team actively investigates M&A events for this exact scenario. They look at the combined system landscape and compare it against the combined contracted Digital Access entitlement. Any gap is an audit finding — and indirect access claims are notoriously difficult to challenge after the fact.
Include an indirect access landscape review as a mandatory component of SAP M&A due diligence. Map every third-party system that touches SAP in the target's landscape, identify the document types being created, and calculate the Digital Access licence requirement. This analysis must be completed before close or immediately post-close. Our SAP indirect access advisory provides this analysis as a standalone service.
Inherited Indirect Access Risk Can Cost Millions
SAP indirect access claims arising from M&A integrations are one of the most common post-merger licence disputes. Our indirect access advisory identifies and resolves inherited exposure before SAP's audit team finds it first.
Get an Indirect Access AssessmentRisk 3: USMM Timing and Combined Landscape Measurement
SAP Measures Before You Do
SAP's annual system measurement cycle can collide with an M&A event in the worst possible way: SAP runs USMM on the combined post-acquisition landscape before the enterprise has completed its own analysis and reclassification. The resulting measurement captures the maximally inflated user count — all users from both entities, with no reclassification — and SAP uses that as the compliance baseline.
Actively delay SAP's access to the combined landscape for measurement purposes until your independent analysis and, ideally, your contract amendment are complete. If your annual measurement window is approaching, formally request a deferral citing the M&A integration process — SAP will typically grant this. Never allow SAP to run LAW or USMM across a combined landscape without an agreed commercial framework in place first.
Risk 4: Dual-Payment During Transition Periods
Paying for Both Entities Simultaneously
In both acquisitions and divestitures, enterprises commonly end up paying the full contracted licence cost for both entities during the transition period. In a divestiture, the selling entity continues paying its full contracted cost while the divested entity starts paying for a new SAP agreement. In an acquisition, the acquiring entity pays its own licence cost while the target's licence obligations continue under their separate contract until it expires or is terminated.
SAP will not flag this situation or offer relief voluntarily. Understanding how SAP calculates licence fees and the contractual mechanisms that govern transition periods is essential for limiting this exposure.
Negotiate a transition period provision as part of any M&A-related contract amendment. The provision should specify the date on which the acquired entity's licences transition to the combined contract, eliminate double-payment for any transition period, and provide a credit or offset for any licence overpayment during the integration. This is achievable but must be explicitly negotiated — SAP does not offer it as a default.
Risk 5: Engine and Package Licence Threshold Crossings
Combined Landscape Exceeds Metric Thresholds
SAP engine licences (ALE, APO, ICH, Solution Manager) and package licences are often metric-based — the licence cost is tied to revenue, asset value, or transaction volume thresholds defined in the Order Form. When two entities are combined, the combined metrics may exceed the contracted thresholds, creating an immediate compliance gap that SAP can quantify with precision. This is particularly common in acquisitions where both entities use the same engine and the combined volumes cross a pricing tier boundary.
Map every engine and package metric across both entities before close. Calculate the combined metric value and compare against the contracted thresholds in each entity's current agreement. Where the combination crosses a threshold, this becomes a negotiating point — not an automatic cost increase. Use the M&A event to renegotiate engine and package pricing at the combined volume level, which should produce a lower per-unit cost even if total volumes increase.
Risk 6: S/4HANA Migration Licence Double-Billing
M&A and S/4HANA Migration Running Concurrently
Many enterprises combine post-acquisition integration with an S/4HANA migration — rationalising the combined landscape onto a single S/4HANA system. If not managed carefully, this creates a scenario where the enterprise is paying for ECC licences (while legacy systems remain operational), S/4HANA licences (for the target migration), and potentially RISE subscription costs — simultaneously, for the same functional users.
Our S/4HANA migration licensing advisory specialises in navigating this intersection. The key is to model the full licence cost timeline before committing to either the integration roadmap or the S/4HANA contract.
Develop a licence cost timeline model that maps every licence obligation across every system in every scenario — existing ECC, acquired ECC, target S/4HANA, and RISE if applicable. Identify the specific dates on which legacy licence obligations can be contractually terminated. Use these dates as hard constraints on the technical integration roadmap, not as optional targets.
Risk 7: Support Cost Lock-In During Right-Sizing
22% Support Obligation on Inflated Licence Base
Every SAP Named User licence carries a 22% annual Enterprise Support obligation. During the right-sizing process — which typically takes 3–6 months from close to contract amendment — the enterprise is paying 22% of the full inflated licence base. For a €50M combined licence value, that's €11M per year, or approximately €2.75M per quarter. Every week of delay in completing the right-sizing costs real money.
Treat the right-sizing timeline as a cost recovery exercise: calculate the daily cost of the inflated support obligation and use that figure to prioritise and resource the analysis process. For large M&A transactions, deploying independent advisory resource to accelerate the analysis by 4–8 weeks typically delivers a 10–20x ROI on the advisory cost. See our SAP support cost reduction advisory for specific approaches to minimising the support cost exposure during transition.
More in This Series
Independent SAP licensing advisory — not affiliated with SAP SE. SAP, S/4HANA, RISE with SAP, and all SAP product names are trademarks of SAP SE.