{"id":52491,"date":"2026-07-10T21:51:07","date_gmt":"2026-07-10T21:51:07","guid":{"rendered":"https:\/\/www.europesays.com\/germany\/52491\/"},"modified":"2026-07-10T21:51:07","modified_gmt":"2026-07-10T21:51:07","slug":"eu-binds-sap-to-decade-of-erp-aftermarket-reforms-in-landmark-antitrust-deal","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/germany\/52491\/","title":{"rendered":"EU Binds SAP to Decade of ERP Aftermarket Reforms in Landmark Antitrust Deal"},"content":{"rendered":"

Enterprise software customers running SAP’s on-premises ERP systems woke up Thursday with a new set of legally enforceable rights they did not have 24 hours earlier. The European Commission formally closed<\/a> its antitrust investigation into SAP’s maintenance and support practices on July 9, 2026, accepting a binding package of remedies that will govern the Walldorf, Germany-based company’s global operations for the next decade. For the roughly 20,000 to 25,000 organizations still running SAP’s legacy ECC platform without a licensed path to its successor, the decision arrives at a moment when their leverage over SAP’s account teams \u2014 and the cost of their eventual exit \u2014 has materially changed.<\/p>\n

The case, filed under EC case number AT.40823<\/a> and opened in September 2025, centered on four practices regulators found may have breached Article 102 of the Treaty on the Functioning of the EU, which prohibits the abuse of a dominant market position. SAP allegedly prevented customers from canceling support contracts on software licenses they were no longer using \u2014 the industry term for this is “shelfware” \u2014 and charged reinstatement fees that regulators characterized as punitive to organizations that had tried cheaper third-party support and then wanted to return. It also extended initial contract lock-in periods with each new license purchase and required customers to source maintenance from a single provider at uniform pricing, blocking module-by-module competition. The Commission accepted binding commitments from SAP under Article 9(1) of Regulation 1\/2003, a procedure that closes a case without a formal infringement finding, in exchange for SAP’s agreement to implement specific reforms.<\/p>\n

SAP disputed that its practices violated EU law. As the company said in a statement<\/a> on July 9: “As the only Fortune 50 technology company headquartered in Europe, SAP’s maintenance practices are aligned with industry standards and offer customers a broad range of deployment, licensing and maintenance options across on-premise and cloud environments.”<\/p>\n

What SAP Must Now Do \u2014 and Immediately Cannot Charge<\/p>\n

The commitments that became legally binding on July 9 include several measures with direct, near-term consequences for organizations in active SAP contract negotiations.<\/p>\n

SAP eliminated reinstatement fees outright. Companies that left SAP’s official maintenance network<\/a> to use a third-party provider \u2014 among them Rimini Street and Spinnaker, which both offer comparable support at roughly half SAP’s standard 22 percent annual license fee \u2014 can now return to SAP support without paying penalty charges. SAP also capped back-maintenance charges at 50 percent of the standard rate, for a maximum of six months.<\/p>\n

SAP must permit customers to split their ERP landscape \u2014 contracting different support providers, at different service levels, for different modules. This breaks the single-provider requirement that regulators identified<\/a> as a structural barrier to competition in the aftermarket.<\/p>\n

Customers now have explicit termination rights in situations that were previously off-limits: where SAP bears responsibility for a failed implementation; in insolvency or bankruptcy; where a company reduces its workforce by 10 percent or more over two years, triggering a proportional right to reduce license volume; and where a business unit is divested. SAP must also stop resetting the initial lock-in period each time a customer purchases an additional license \u2014 a practice critics described as perpetually moving the exit clock forward.<\/p>\n

An independent monitoring trustee will report to the Commission throughout the 10-year period. Non-compliance can trigger fines of up to 10 percent of SAP’s worldwide annual turnover without requiring any separate finding of infringement \u2014 and periodic penalties of 5 percent of daily global revenue per day of continued non-compliance. Based on SAP’s reported 2024 revenues<\/a> of approximately $37 billion, a single infringement finding would carry exposure exceeding $3.7 billion.<\/p>\n

Why This Arrives at the Worst Possible Moment for SAP’s Legacy Base<\/p>\n

The timing of the decision carries its own significance independent of its legal content. SAP’s mainstream maintenance deadline for ECC \u2014 the platform most of its large-enterprise install base built its operations on over the past two decades \u2014 falls on December 31, 2027. According to SAPinsider’s ERP Migration and Transformation 2026 Benchmark Report<\/a>, between 20,000 and 25,000 legacy SAP ERP customers have not yet licensed S\/4HANA, SAP’s cloud-native successor. Only 34 percent of organizations that have deployed S\/4HANA have fully completed their transition, meaning the practical number still running on or migrating from ECC is substantially larger.<\/p>\n

The resource market for S\/4HANA migration work is already tightening. Consulting fees for S\/4HANA specialists have risen significantly since 2023, according to market data, and organizations starting migrations in 2026 face delivery slots, architect availability, and integration expertise that early movers have already claimed. A full ECC-to-S\/4HANA migration for a large enterprise typically requires 18 to 36 months \u2014 a window that, for any organization that has not yet begun, now runs past the 2027 deadline into SAP’s extended maintenance period, which carries a surcharge of approximately 2 percentage points above the standard rate and runs through 2030.<\/p>\n

For the organizations caught in this position, the newly binding commitments change the calculus in a specific way. Companies that had exited SAP maintenance to use Rimini Street or Spinnaker to buy time \u2014 and reduce costs \u2014 during a prolonged migration period can now return to SAP support when their project is complete without facing back-maintenance penalties equivalent to everything they saved. The landscape-splitting right also allows organizations to maintain third-party support on stable modules while paying SAP for the specific components where SAP’s active development matters for the migration.<\/p>\n

Why Article 9 Matters \u2014 and What It Cannot Do<\/p>\n

The SAP case closed under Article 9(1) of Regulation 1\/2003, not under Article 7, which is the mechanism the Commission uses to issue a formal infringement decision and impose fines. The distinction is consequential beyond SAP’s immediate situation.<\/p>\n

Under Article 9, the Commission accepts binding commitments from a company under investigation, terminates the case without finding that EU law was violated, and without creating a binding legal precedent applicable to other companies. SAP’s competitors in the enterprise software aftermarket \u2014 Oracle, Salesforce, IBM \u2014 are not legally bound by this decision. Each of those companies can argue that its own maintenance and support practices are distinguishable from SAP’s, and that the commitments are voluntary remedies accepted by SAP without admission of wrongdoing, not a ruling that aftermarket lock-in as a practice violates Article 102.<\/p>\n

The practical deterrent effect therefore depends on the credibility of the Commission’s stated intention to pursue similar investigations elsewhere \u2014 and on how explicitly the Commission signals that it views aftermarket lock-in as a categorically prohibited abuse of dominance, rather than a fact-specific finding about SAP’s specific contract terms. EU Executive Vice-President Teresa Ribera addressed this directly on July 9, saying in the Commission’s official announcement<\/a> that the decision gives customers “more freedom to choose maintenance and support services without unfair restrictions that raised their costs and stifled competition.” She described the commitments as setting “a benchmark for the industry more broadly.”<\/p>\n

Brussels’ Warning Shot at Cloud Infrastructure<\/p>\n

The most consequential sentence in Ribera’s statement on July 9 was not about SAP’s on-premises business. It was about what comes next. The decision, she said, “should serve as a warning against similar practices in the cloud markets, where customers are increasingly moving.”<\/p>\n

That warning was not issued in a vacuum. Fifteen days earlier, on June 25, the European Commission published preliminary findings<\/a> from a seven-month investigation concluding that Amazon Web Services and Microsoft Azure appear to meet the criteria for designation as gatekeepers under the Digital Markets Act \u2014 the first time the EU’s landmark digital competition law has been applied to cloud infrastructure rather than consumer-facing platforms. Neither AWS nor Azure meets the DMA’s standard quantitative revenue thresholds for designation; the Commission’s preliminary finding rested on a qualitative assessment of their entrenched position and the role of AI-driven demand in cementing cloud lock-in. AWS and Azure together held approximately 65 to 70 percent of EU cloud revenue in the first quarter of 2026, according to Synergy Research Group data.<\/p>\n

A final DMA gatekeeper designation for AWS and Azure \u2014 expected before the end of 2026 \u2014 would impose interoperability requirements, data portability rights, and restrictions on self-preferencing on the world’s two largest cloud providers. Both companies have indicated they will contest the preliminary findings, with a September 2026 deadline to respond before a final decision. The EU General Court’s July 8, 2026 ruling in the Apple DMA case<\/a> established that designated gatekeepers cannot challenge DMA obligations in the abstract before a specific enforcement decision is issued \u2014 a sequencing rule that now applies to every pending DMA proceeding.<\/p>\n

The SAP on-premises settlement and the AWS\/Azure DMA preliminary findings, taken together, trace the outline of a coherent EU enforcement doctrine. Competition lawyers call the underlying concept “aftermarket lock-in” \u2014 the extraction of value through support, switching-cost, or data-egress mechanisms tied to a customer’s dependence on a vendor’s core product. That doctrine, as articulated by the Commission across both proceedings, now applies from the ERP layer through the cloud infrastructure layer.<\/p>\n

What to Watch Before Year-End<\/p>\n

SAP’s second-quarter results are scheduled for July 23. Analysts will have their first look at whether the settlement affected customer sentiment, how renewal negotiations shifted during the investigation period, and whether the cloud business \u2014 which the commitments do not touch \u2014 shows any effect from the changed on-premises environment.<\/p>\n

The DMA gatekeeper determination for AWS and Azure is expected before December 31, 2026. Both companies have stated they will contest the preliminary findings; the General Court’s July 8 Apple sequencing rule means any legal challenge must come after, not before, a final designation order.<\/p>\n

For enterprise technology buyers, the decision’s most actionable consequence does not require waiting. The commitments took effect July 9. Organizations carrying unused SAP licenses, managing contracts with back-maintenance obligations, or planning to return to SAP support after a period with a third-party provider have new rights they can exercise in the next renewal conversation.<\/p>\n

Frequently Asked QuestionsDoes the EU ruling mean SAP has been found to have broken the law?<\/p>\n

No. The European Commission accepted SAP’s commitments under Article 9(1) of Regulation 1\/2003, which closes an antitrust investigation without a formal finding of infringement. SAP did not admit wrongdoing. The commitments are legally binding on SAP \u2014 violation can trigger fines \u2014 but no other enterprise software company is legally required to comply with them, because the case produced a settlement, not an infringement ruling. Other vendors’ maintenance and support practices remain subject to separate investigations if the Commission decides to pursue them.<\/p>\n

What is aftermarket lock-in, and why does the EU consider it an antitrust problem?<\/p>\n

Aftermarket lock-in occurs when a dominant vendor uses customers’ dependence on its core product to extract above-market prices or restrict competition in the downstream market for support, maintenance, or services. In SAP’s case, regulators found that customers who adopted SAP ERP as their core system of record were effectively captive to SAP’s support pricing because switching away from SAP’s maintenance network and returning later triggered fees that, in regulators’ assessment, negated the savings. The EU views this as a potential abuse of dominance under Article 102 of the Treaty on the Functioning of the EU \u2014 the same legal theory now being extended toward cloud infrastructure through the DMA gatekeeper framework for AWS and Azure.<\/p>\n

How do the new termination rights affect organizations planning to stay on ECC past 2027?<\/p>\n

Organizations that remain on ECC after SAP’s mainstream maintenance deadline are now in a materially different negotiating position for extended support arrangements. The new landscape-splitting right allows them to contract third-party providers \u2014 Rimini Street and Spinnaker are the two largest, both offering support through 2040 where contracts permit, at roughly half SAP’s standard rate \u2014 for the modules where SAP’s active development matters least, while maintaining SAP support selectively. The abolished reinstatement fees remove the penalty for returning to SAP later, which previously made “trying third-party support” a one-way door for many customers. SAP’s extended maintenance offering runs through 2030 at a surcharge of approximately 2 percentage points above the standard annual rate.<\/p>\n

What does the DMA cloud gatekeeper designation mean for organizations running workloads on AWS or Azure?<\/p>\n

If the preliminary findings against AWS and Azure are confirmed in a final decision expected before end of 2026, both companies would face binding obligations on interoperability, data portability, and self-preferencing. The practical effect for enterprise buyers would include easier migration of workloads between cloud providers and restrictions on AWS and Azure using their own infrastructure advantage to preference their own AI tools over third-party alternatives. AWS and Azure have indicated they will contest the preliminary findings. The General Court’s July 8 sequencing rule means that challenge must come after any final designation order issues, not before \u2014 reducing the viability of pre-emptive litigation as a delay tactic.<\/p>\n","protected":false},"excerpt":{"rendered":"Enterprise software customers running SAP’s on-premises ERP systems woke up Thursday with a new set of legally enforceable…\n","protected":false},"author":2,"featured_media":52492,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21036],"tags":[23752,42347,23167,721,42345,9695,42346,42344],"class_list":["post-52491","post","type-post","status-publish","format-standard","has-post-thumbnail","category-sap","tag-antitrust","tag-digital-markets-act","tag-enterprise-software","tag-eu","tag-european-commission-at-40823","tag-sap","tag-sap-ecc-maintenance-support","tag-sap-erp-antitrust-settlement"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/posts\/52491","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/comments?post=52491"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/posts\/52491\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/media\/52492"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/media?parent=52491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/categories?post=52491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/germany\/wp-json\/wp\/v2\/tags?post=52491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}