Margrethe Vestager and Christian Klein signing settlement agreement at meeting

SAP’s EU Settlement Shifts ERP Customer Leverage

IT Management Comments Off on SAP’s EU Settlement Shifts ERP Customer Leverage

For CIOs and enterprise application leaders, the settlement is less a legal footnote than a governance reset. It weakens the assumption that ERP maintenance terms are fixed once the platform is embedded, which means contract oversight can no longer be treated as a procurement exercise handled at renewal time. Leaders should ask who owns support strategy across finance, operations, sourcing and transformation, and whether decision rights are clear enough to use the new flexibility without creating internal confusion.

The biggest management question is portfolio discipline. Greater freedom to split environments, terminate certain entitlements, or revisit support arrangements can release budget, but it can also fragment the operating model if applied piecemeal. The trade-off is straightforward: short-term savings and negotiating leverage versus the complexity of running mixed support structures, uneven service levels and more demanding compliance tracking. That makes benefits realisation and contract inventory management more important, not less.

This also changes how ERP modernization should be funded and sequenced. If maintenance spend can be reduced or redirected, the practical issue is whether the savings are captured centrally and reinvested into migration, data remediation and process redesign, or absorbed locally. CIOs should challenge business cases that assume support savings automatically translate into transformation capacity. The next questions are: which applications are truly strategic, which contracts are flexible, and what control points are needed to prevent tactical savings from undermining roadmap execution?

For vendor managers, the settlement is a reminder that leverage now depends on preparedness. Organizations that can quantify shelfware, support usage, migration status and business criticality will negotiate better than those relying on broad claims. The decision to stay, split, outsource support or accelerate modernization should be explicit, timed and measurable—not a default reaction to a contract event.

On July 9, 2026, SAP reached a Original Postresscorner/api/files/document/print/en/ip_26_1554/IP_26_1554_EN.pdf" shape="rect">settlement with the European Commission that closes an antitrust investigation into SAP’s maintenance and support practices for on-premises ERP software. Importantly, this was resolved through binding commitments rather than a finding of wrongdoing or a financial penalty. However, customers should not mistake the absence of a fine for the absence of impact. The commitments are legally binding for 10 years and apply globally, creating meaningful changes in how SAP customers can manage maintenance, support, and software entitlements going forward. What Happened? The European Commission’s investigation focused on whether certain SAP maintenance and support practices restricted competition in the aftermarket support ecosystem. Regulators were concerned that customers faced barriers when attempting to reduce support coverage, use third-party support providers, terminate unused licenses, or return to SAP support after leaving. Under the settlement, SAP agreed to several commitments, including:
  • Allowing customers greater flexibility to split SAP environments and use different support arrangements for different portions of their landscape.
  • Eliminating reinstatement fees and reducing back-maintenance charges for customers returning to SAP support.
  • Providing broader access to alternative licensing structures.
  • Clarifying contract provisions related to support obligations and license terms.
  • Allowing license termination in certain circumstances, including divestitures, insolvency situations, workforce reductions, reduced-support product phases, and some failed implementation scenarios attributable to SAP.
SAP has emphasized that the decision applies only to on-premises maintenance and support policies and does not affect its cloud offerings. The company characterized the outcome as providing greater clarity and flexibility while reinforcing customer choice. Why This Matters Now For nearly a decade, enterprise software buyers have complained that ERP vendors possess enormous leverage after implementation is complete. Once an ERP system becomes the operational backbone of the enterprise, switching costs become substantial, creating a dependency that often extends into maintenance, support, and future modernization decisions. The European Commission’s settlement directly targets some of these switching barriers. While the commitments are operational and contractual in nature, their strategic significance is much larger: they increase customer optionality precisely as thousands of SAP customers are navigating ECC-to-S/4HANA migration decisions. For SAP customers, the immediate implication is straightforward: negotiating leverage has improved. Organizations now have stronger grounds to question support costs, explore third-party support alternatives, rationalize shelfware, and negotiate more aggressively around long-term maintenance commitments. Vendors benefit when customer alternatives are limited. This settlement creates more alternatives. What It Means For SAP From SAP’s perspective, this outcome removes a regulatory overhang at an important time. SAP is currently focused on accelerating S/4HANA migrations, expanding Business Data Cloud adoption, and positioning Joule and Business AI as the foundation of its next-generation ERP strategy. A prolonged antitrust battle would have been a distraction at a moment when SAP wants customers focused on modernization. The settlement provides certainty and allows SAP to move forward without fines or ongoing litigation risk. That said, the decision reflects a broader trend regulators are increasingly scrutinizing: high switching barriers and vendor dependency in enterprise software markets. Historically, regulatory attention focused primarily on consumer technology platforms. This case signals that enterprise software vendors are no longer outside the scope of competition enforcement. It would not be surprising to see future scrutiny extend beyond maintenance practices into broader questions around migration incentives, cloud portability, data access, interoperability, and AI ecosystem dependencies. What It Means For SAP Customers The biggest beneficiaries are likely to be late-stage ECC customers. Many organizations still running ECC face difficult decisions around migration timing, third-party support, and cost containment. The settlement gives these customers greater flexibility to evaluate alternatives without some of the historical penalties associated with leaving and later rejoining SAP support programs. However, customers should avoid overinterpreting the decision.
  • This does not change SAP’s product roadmap.
  • It does not delay ECC support deadlines.
  • It does not reduce the strategic importance of S/4HANA.
  • And it does not fundamentally alter SAP’s cloud-first direction.
Organizations that view the settlement as a reason to postpone modernization risk missing the larger reality: innovation, AI capabilities, and future SAP investments remain concentrated in S/4HANA and cloud-based environments. The commercial flexibility created by this settlement should be used to negotiate better outcomes, not to avoid long-term modernization planning.  
SAP’s EU Settlement Shifts ERP Customer Leverage

Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.