SAP License Compliance in M and A

Where SAP shows up in M and A

SAP license compliance appears in M and A transactions at five points. Pre signing due diligence on the target SAP estate. Disclosure schedules in the transaction agreement. License transferability under the SAP master agreement that governs the target. Post close integration of the target SAP estate into the acquirer estate. Carve out license arrangements where part of an SAP estate is divested. Each point carries license consequence that affects deal value, deal timing, and post deal operating cost.

Deal teams that do not address SAP licensing in due diligence routinely discover at close that the target carries audit exposure, contractual restrictions on transfer, or a license posture that requires immediate remediation. The remediation cost typically falls on the acquirer because the seller has already exited. Pre signing due diligence is the most cost effective intervention available. Cross reference our due diligence guide and M and A compliance expertise page.

Due diligence on SAP in the target

SAP due diligence should run across five workstreams. Contract review to identify the SAP master agreement and any deviations from standard terms. Usage measurement to identify any current overconsumption against contracted entitlement. Indirect access review to identify any unaddressed exposure that becomes an audit finding post close. Audit history review to identify any open or recent audit findings that have not been settled. Renewal calendar review to identify the timing of the next renewal and the leverage it carries.

The five workstreams produce a license risk inventory that can be addressed in three ways. The risks can be priced into the deal through purchase price adjustment. The risks can be assigned to the seller through specific indemnities. The risks can be addressed pre close through remediation actions that the seller funds. Each option has trade offs that the deal counsel and the SAP advisor jointly assess.

License transferability under SAP master agreements

SAP licenses are not automatically transferable. The standard SAP master agreement restricts transfer to affiliates and conditions transfer outside the affiliate group on SAP consent. The consent is typically conditional on commercial terms that benefit SAP, including a transfer fee, a price refresh on the transferred licenses, or both. The consent timeline is also subject to SAP discretion and can extend the deal close timeline.

The most common deal value leakage in SAP M and A transactions is the discovery at close that licenses cannot be transferred without SAP consent and the consent comes with a material commercial condition that was not modeled in the deal economics.

The transferability question should be asked in the first weeks of due diligence, not the last weeks before close. Time is the variable that produces leverage in the transfer conversation. Detail in our license transfer in acquisitions guide.

Post close consolidation strategy

Post close consolidation of two SAP estates is one of the highest leverage license optimization opportunities available. The consolidation typically involves harmonizing user classifications across the two estates, eliminating duplicate licenses where the acquirer and target both license the same module, and renegotiating the combined contract with SAP at a scale that produces stronger commercial terms than either entity could secure alone.

The consolidation should begin within 90 days of close, while the combined operational baseline is still being established. Consolidation that begins later, after the operational pattern is set, is significantly harder to execute. Customers who consolidate proactively report savings of 25 to 40 percent against the combined pre deal SAP spend. The detail is in our post merger consolidation guide.

Carve out and divestiture license arrangements

Carve out transactions, where part of an SAP estate is divested, carry their own license complexity. The licenses that support the carved out business must be either transferred to the buyer, recreated by the buyer under a new SAP contract, or accessed temporarily under a transition services agreement while the buyer establishes their own SAP estate.

The three options carry different cost profiles and different operational risk. Transfer is typically the lowest cost option but requires SAP consent. New contract is typically the highest cost option but the cleanest legal arrangement. Transition services agreements carry interim cost and an open ended exposure to SAP audit during the transition period. The selection between the three options should be made by the deal team in coordination with the SAP advisor. The detail is in our carve out implications guide and the divestiture compliance analysis.

The deal protections that prevent leakage

Several specific protections in the transaction documentation reduce SAP related deal value leakage. Disclosure schedules that list the SAP master agreement, any deviations, and any open audit matters. Specific indemnities for known SAP risks, scoped tightly to the identified issues. Representations covering SAP license compliance to the seller knowledge standard. Closing conditions tied to SAP consent where consent is required for license transfer. Working capital adjustments that include the SAP maintenance and subscription line items in the closing calculations.

None of the protections eliminate SAP risk. Each protection allocates the risk between buyer and seller in a way that supports deal economics. The protections are negotiated at the same time as the broader transaction terms. Cross reference our license consulting service overview, our SAP M and A white paper, and our audit guide for the broader context.