Summary
- The European Commission has accepted legally binding SAP commitments covering maintenance and support for customer-run ERP software.
- The measures address customer choice, switching, fee transparency, and third party support options.
- The case highlights the resilience and procurement risks tied to legacy enterprise platforms that remain operationally critical.
SAP has agreed to binding commitments in the European Union over maintenance and support practices for enterprise resource planning software run on customer infrastructure, closing a competition investigation with wider relevance for technology dependency, supplier control, and operational resilience.
The European Commission accepted commitments designed to address concerns that customers using SAP’s business management software faced unfair restrictions when seeking support from rival providers or ending support contracts. SAP said the decision gives greater clarity, choice, and safeguards for customers managing complex customer-run environments, while the Commission’s case focused on whether support and maintenance practices reduced competition and increased costs.
The agreement does not cover SAP’s cloud offerings, but the systems in scope remain central to many large organisations. Finance, procurement, human resources, manufacturing, supply chain, reporting, and regulatory evidence often still depend on ERP estates that have developed over many years. These platforms are not peripheral applications; they are often the operational record behind payments, inventory, supplier relationships, payroll, financial close, and management reporting.
Under the commitments described by the Commission and SAP, customers should gain more flexibility over maintenance choices, including clearer conditions for separating parts of an SAP landscape and greater predictability around support arrangements. Reuters reported that SAP’s plan includes an alternative method for calculating licence fees, removal of reinstatement fees, and reduced back-maintenance fees for returning customers, with the offer applying globally for 10 years.
The Commission’s decision gives technology, procurement, and risk teams a reason to revisit support arrangements for systems that may be difficult to replace quickly. Inflexible support contracts can slow architectural change, preserve unused licences, or make exit planning commercially unattractive. When the platform under discussion controls finance, manufacturing, procurement, or workforce processes, those commercial decisions become resilience decisions.
Cyber risk is also shaped by support access, patch cadence, vulnerability remediation, and recovery planning. Although the Commission case is an antitrust matter rather than a security enforcement action, support flexibility can affect how organisations isolate risk, upgrade exposed modules, decommission legacy components, or bring in specialist recovery and hardening expertise. ERP estates often contain privileged integrations, service accounts, custom code, and sensitive business data, which makes support strategy part of the control environment.
The settlement also sits inside a European market where regulators are paying closer attention to concentration risk and operational dependency. Financial services firms are subject to DORA requirements around third party ICT risk, exit planning, and resilience testing. NIS2 expands cyber duties across a broader set of essential and important entities. Cloud regulation and digital market rules are forcing more explicit discussion of portability, switching, and supplier power.
Organisations moving from long-standing ERP systems towards cloud services will still need to reconcile commercial flexibility with technical reality. Large migrations are expensive, lengthy, and risk-bearing. Many estates contain customisations, integrations, historical data, and business processes that are difficult to move without disruption. Support commitments can reduce one form of lock-in, but they do not remove the operational discipline needed to map dependencies, preserve recovery options, and govern change.
The settlement leaves SAP able to move forward without a finding of infringement, while giving customers a clearer framework for support decisions. Buyers now have an opportunity to reassess support segmentation, third party maintenance exposure, disaster recovery assumptions, and contract evidence around platforms that remain too central to be left to procurement inertia.
