10 SAP Contract Red Flags That Cost Enterprises Millions

Broadly Worded Indirect Access Definition

The most financially dangerous clause in most SAP agreements is not the one about support fees or renewals — it's the indirect access definition. SAP's standard language defines "use" of SAP software to include access through any interface, including non-SAP systems that query SAP data. This single definition has been used by SAP's GLAC team to claim that every API call, RPA bot, middleware interaction, and third-party application integration requires a Named User licence.

The impact is proportional to your integration complexity. An enterprise with 50 SAP integrations and 5,000 back-office employees processed through connected systems can face a claim that every employee requires a Professional or Employee licence — even if none of them ever logs into SAP. SAP's indirect access claims have generated over $1B in additional licence revenue since 2017, funded largely by broad contract language that enterprises signed without understanding its scope.

What to demand: A specific, named list of integration scenarios that constitute indirect access, with all other integrations explicitly excluded. Your SAP indirect access advisory should be completed before the contract clause is finalised.

Uncapped Annual Price Increases on Licences

SAP's contracts permit annual list price increases. The standard language allows "reasonable market-aligned increases" — with SAP as the sole arbiter of what is reasonable. In practice, SAP has increased software list prices by an average of 4–9% annually across recent years. Compounded over a 5-year term on a €10M licence agreement, even a conservative 5% annual increase produces a cumulative cost 28% higher than the original baseline. That's €2.8M in additional spend on a contract that felt like it was set at signing.

The fix is a contractual price cap. It must be an absolute ceiling — not a guideline — tied to a specific published index (CPI is standard) with a hard maximum percentage. "We've never increased prices by more than X%" is not a contractual commitment. For detailed guidance, see our analysis of SAP price increase protections to demand in writing.

Auto-Renewal With Inadequate Notice Window

SAP agreements typically auto-renew unless cancelled within a notice window — standard wording gives 90 to 180 days. The problem is that "notice window" is calculated from the annual review date, not the contract end date. Internal teams rarely track this with the required precision. When the window is missed — and it frequently is — the contract renews automatically, eliminating the enterprise's ability to renegotiate terms, switch to third-party maintenance, reduce licence scope, or exit. The next opportunity may be 12 to 36 months away.

This is not a hypothetical scenario. In a 2024 review, a global retailer missed its 90-day SAP auto-renewal window by 11 days. The consequence was a 3-year forced renewal of an agreement that included uncapped support escalation and a list price increase provision that cost the business €1.9M in avoidable spend. Full analysis is available in our dedicated guide to SAP auto-renewal clauses and how to remove them.

Support Fees Calculated on List Price, Not Net Price

SAP Enterprise Support is set at 22% of licence fees. The question is: 22% of what? SAP's standard terms calculate support on the original list price — not the discounted net price you actually paid. If you negotiated a 40% discount on a €15M licence deal, your net price is €9M. Support at 22% of net is €1.98M annually. Support at 22% of list is €3.3M. That's a €1.32M annual overpayment — every year for the life of the contract.

SAP will argue this is standard practice. It is — and it's one of the most reliably negotiable points in any SAP enterprise agreement. Insist on support calculated on the net invoice price, with a specific contractual definition. Our SAP support cost reduction advisory has recovered this overpayment for dozens of enterprises.

Unlimited Audit Rights Without Scope Restriction

SAP's standard audit clause gives SAP the right to audit "your use of SAP Software" on reasonable notice — typically 30 days. The problem is the broad definition of "your use." SAP's GLAC team, in practice, interprets this as giving access to any system that interacts with SAP data: ERP, CRM, HR systems, middleware platforms, and production environments, regardless of whether SAP software is deployed there.

An unrestricted audit clause creates two independent risks. First, SAP gains access to data and system architecture information beyond what is needed for licence compliance verification — commercial intelligence your organisation has no incentive to provide. Second, the resulting claim is based on SAP's interpretation of its own measurement tools (USMM, LAW, STAR), without independent verification. Our SAP audit defence team has consistently demonstrated that SAP's USMM measurements overcount by 15–40% in standard enterprise environments. The contract should limit audit scope to deployed SAP systems and specify which tools may be used.

Vague User Type Definitions Without Functional Constraints

SAP's user type structure — Professional, Limited Professional, Developer, Employee, Functional, Productivity, ESS, and others — is the primary mechanism through which SAP's compliance team generates audit findings. The licence price differential between a Professional user (the most expensive) and a Limited Professional or Employee user is typically 3–5×. If your contract defines user types in terms that SAP can broadly interpret, every USMM measurement becomes a reclassification risk.

The standard red flag language is: "A Professional User is any individual who accesses the SAP System for any purpose." The better language specifies which transactions, modules, and functional activities are included and excluded for each user type. Getting functional constraints written into the user type schedule before signing is one of the highest-leverage SAP contract negotiation actions available.

RISE Contract Without Exit Provisions

RISE with SAP agreements are structured as minimum-term subscriptions — typically 3 to 5 years — with standard clauses that prevent termination for any reason other than SAP's material breach. Change of control, insolvency, strategic business transformation, or simply deciding to delay S/4HANA migration are not recognised exit triggers in most RISE agreements. Enterprises that sign RISE contracts during a period of strategic clarity find themselves legally bound when circumstances change — which they invariably do over a 5-year period.

Before signing any RISE agreement, our independent RISE advisory should identify specific exit scenarios, negotiate change-of-control provisions, and establish voluntary exit mechanics with defined financial penalties rather than open-ended obligations.

Support Fee Annual Escalation Tied to Uncapped Index

Separate from the base support fee calculation, many SAP agreements permit annual support fee escalation tied to an index — often a local CPI measure or SAP's discretionary "market rate" adjustment. In a period of elevated inflation (as experienced 2022–2024), a CPI-linked support escalator with no ceiling can generate support cost increases of 6–9% annually. Combined with a list-price escalator on the licence side, total SAP cost can increase by 15–20% in a single year without any change to the software deployed.

The fix is straightforward: the support fee escalator must have a hard annual ceiling (typically 3–5%), calculated on the net invoice price, with a specific cap mechanism that prevents compound stacking with any list price increase.

S/4HANA Migration Clauses That Remove Perpetual Rights

When SAP proposes an S/4HANA migration as part of a contract renewal or RISE agreement, the migration addendum sometimes contains language that modifies or removes existing perpetual on-premise licence rights. These clauses convert perpetual licences — assets your organisation owns — to subscription rights that expire or require ongoing payment. They may also remove the right to run legacy ECC systems in parallel during migration, creating operational risk that increases migration pressure and reduces your negotiating leverage.

Any SAP agreement that references migration, upgrade, or conversion of existing licences requires review by an S/4HANA migration licensing specialist before execution. The perpetual licence rights your organisation holds have real commercial value — typically 10–15% of the original licence value in third-party support contexts — and should not be surrendered without compensation or explicit strategic justification.

Governing Law Clauses That Favour SAP's Jurisdiction

SAP's standard contracts specify German law and German courts as the governing jurisdiction for dispute resolution. For enterprises headquartered in the UK, US, Australia, or other jurisdictions, this creates a practical barrier to commercial litigation against SAP — the cost, procedural complexity, and time required to pursue a dispute in German courts makes it commercially unattractive relative to settling on SAP's terms. This is not accidental. SAP's standard jurisdiction clause is a structural deterrent to contested disputes.

Negotiating governing law and jurisdiction to your home country — or to a neutral jurisdiction with established commercial arbitration precedent — is low cost at contract stage and high value if a dispute ever arises. Pair this with an agreed dispute resolution process that specifies independent technical measurement before any audit finding is accepted as binding.