SAP General Terms & Conditions: Hidden Risks Enterprise Buyers Miss

What SAP's GT&C Is and How It Functions

SAP publishes its General Terms & Conditions as a separate document from the Master Agreement. The hierarchy is:

1. Master Agreement (negotiated, customer-specific)
2. Order Form (specifies products, users, pricing)
3. General Terms & Conditions (governs how the above two operate)

The GT&C is the governing layer. Where Master Agreement language conflicts with GT&C language, the GT&C typically controls (unless the Master Agreement explicitly states otherwise). Where Order Form language conflicts with both the Master Agreement and GT&C, the Order Form is subordinate.

The core problem: Enterprise buyers negotiate the Master Agreement carefully, treating it as the governing contract. The GT&C is treated as boilerplate. In reality, the GT&C often contains more dangerous provisions than the Master Agreement because it governs the operation of the Master Agreement without being explicitly negotiated.

Implied Warranty Disclaimers: The "As-Is" Trap

SAP's GT&C contains this language: "Software is licensed 'as-is' without warranties of any kind. SAP disclaims all implied warranties, including warranties of merchantability, fitness for a particular purpose, non-infringement, and title."

This is a complete warranty disclaimer. It means:

• SAP makes no representation that the software will work for your intended use case
• If the software fails to perform as you expected, you have no warranty-based remedy
• Your sole recourse is specific performance (forcing SAP to fix a defect) or termination—but only if the defect prevents you from using the software entirely
• A feature gap, performance problem, or missing functionality is not a warranty breach

Compare this to typical enterprise software licensing, where vendors warrant that software will perform according to specifications. SAP's blanket "as-is" disclaimer is unusually aggressive.

Negotiation position: Carve out critical functionality. Example: "Warranty disclaimers do not apply to SAP's commitment that the software will operate in production environments with 99.5% uptime during contracted support windows. Critical modules (Finance, Supply Chain) are warranted to perform according to published data sheet specifications."

Acceptance rate: 60-70% if you limit warranty carve-outs to 3-4 mission-critical modules, not the entire system.

What This Means for Implementations

An SAP implementation runs 6 months and costs £8M. Two weeks before go-live, you discover the system cannot handle your transaction volume (300K transactions per day, but SAP's configuration supports only 180K). The project is at risk. You demand that SAP re-architect the system to meet your requirements.

SAP's response: "The software performed as configured. Your requirement for 300K transactions per day is a business requirement, not a system requirement. The system is not defective—your expectations were incorrect. We can re-architect for an additional £1.5M in professional services."

Without an explicit warranty that the system will handle your expected transaction volume, you have no contractual recourse. The "as-is" disclaimer permits this.

Negotiation approach: Before implementation kicks off, define critical performance parameters and add them to the GT&C warranty carve-out. Example: "System is warranted to support minimum 250K transactions per day during peak business hours, with response time <5 seconds for standard transaction types." This creates an explicit warranty that forces SAP to size the system correctly.

Software Update and Version Obligations

The Trap: Mandatory Updates on SAP's Timeline

SAP's GT&C states: "SAP may update or release new versions of the software at any time. Customer must implement updates and new versions within [180/365] days of availability. Failure to update within the required timeline voids support and maintenance."

This language appears in SAP's standard GT&C (variations exist based on product line). It means:

• SAP controls your update calendar, not your business cycle
• You must implement updates on SAP's timeline, even if your business is in the middle of fiscal year-end close
• Missing the update deadline voids maintenance—your system is unsupported until you update
• If you don't implement the update, you're in breach of the GT&C, which can trigger audit rights or license termination

Real-world scenario: SAP releases a major S/4HANA update in October. Your enterprise's fiscal year-end close is November/December. Your implementation team is fully dedicated to year-end close. You have no spare capacity to implement an SAP update. SAP's timeline requires implementation by March (180 days). You miss the deadline by 2 weeks. SAP voids your maintenance support. Three months later, an unrelated system issue arises that requires maintenance support to resolve. SAP refuses to help until you implement the update retroactively and pay a 6-month back maintenance fee.

How to Negotiate Update Obligations

Position: "Software updates are mandatory within 365 days of release. Customer determines implementation date within this window based on business readiness and project capacity. SAP will not void maintenance if customer misses the deadline, provided customer demonstrates good-faith implementation planning."

Backup position: "Critical security patches are mandatory within 90 days. Feature and functional updates are mandatory within 365 days. Non-critical updates are optional."

This separates security-critical updates (which are legitimate to mandate) from feature releases (which should be optional). Acceptance rate: 70% for the backup position when negotiated with SAP's Product Support team (not the legal team).

Unilateral Modification Rights: The Changing-Terms Trap

SAP's GT&C contains a modification clause: "SAP may modify these GT&C at any time. Modifications are effective 30 days after posting to SAP's website. Continued use of the software after the effective date constitutes acceptance of the modified terms."

This grants SAP unilateral right to change the contract terms without your explicit consent. You have three choices: (1) Accept the new terms, (2) Terminate the contract (triggering termination penalties), (3) Fail to comply with the new terms (triggering breach of contract claims).

Real scenario: Your Master Agreement with SAP expires on March 31, 2026. On March 1, 2026, SAP publishes an updated GT&C that changes the warranty disclaimer to be more restrictive and extends support response times from 4 hours to 8 hours. The modified GT&C is effective March 31 (30-day notice). Your renewal is scheduled for April 1. You're forced to accept the new terms or walk away from the renewal and lose your SAP investment.

Negotiation position: "SAP may not unilaterally modify the GT&C during the contract term. Modifications to the GT&C are effective only upon contract renewal or amendment. If SAP publishes material changes to the GT&C (>10% cost increase, >20% obligation increase, >30% scope reduction), customer may terminate without penalty within 60 days of notification."

Acceptance rate: 40% (SAP fights hard on this because unilateral modification rights are a key value extraction mechanism). Compromise: "SAP may make technical modifications to the GT&C that do not materially change customer obligations. Material modifications require customer written consent, or customer may terminate within 90 days of notification."

Anti-Assignment Clause: Outsourcing Restrictions

The GT&C typically states: "Customer may not assign, transfer, sublicense, or outsource the software to third parties without SAP's written consent. Prohibited assignment includes providing access to managed service providers, outsourcing vendors, or service bureau providers."

This clause is designed to lock you into using SAP-approved service providers (who generate higher professional services revenue for SAP). The problem: You may want to hire a cheaper managed service provider for SAP operations support. The GT&C forbids this without SAP consent (which is never granted).

What this means: You cannot outsource SAP operations to an MSP without licensing violations. Your only "approved" path is to pay SAP's premium support rates or hire SAP partners (who are more expensive than independent consultants).

Negotiation position: "Customer may engage third-party service providers for operational support (monitoring, patching, backups) provided they execute an NDA and agree to follow SAP's security and support protocols. SAP retains the right to audit third-party access for security purposes. Assignment to another enterprise (M&A scenario) does not require SAP consent if the acquirer is creditworthy and assumes the Master Agreement obligations."

Acceptance rate: 55% for third-party operational support carve-out. 75% for assignment in change-of-control scenarios.

Technology Use Rights: Virtualisation and Cloud Restrictions

The GT&C often contains restrictions on how you can deploy SAP software: "Software may not be virtualised, containerised, or deployed in public cloud environments without additional licensing. Virtualisation requires an Application Server Virtualisation license. Cloud deployment requires a RISE with SAP subscription."

These restrictions effectively segment your deployment options and force licensing upgrades when you move to new architectures.

Real-world impact: S/4HANA Migration to Cloud

You're migrating from on-premise SAP to RISE with SAP (SAP's cloud subscription). Your current Master Agreement covers on-premise deployment. The GT&C states that cloud deployment requires a separate RISE with SAP subscription (with different terms, pricing, and notice requirements). You cannot simply "move" your existing licenses to the cloud.

You're forced to: (1) Maintain your on-premise Master Agreement while it remains active (even though the system is decommissioned), (2) Purchase a new RISE with SAP subscription for cloud, (3) Pay for overlapping licenses during the migration window.

Negotiation position: "If customer migrates to RISE with SAP or other cloud deployment, existing on-premise licenses may be converted to cloud entitlements without additional licensing fees, at a conversion ratio of [1:1 or 1:0.75]. This permits orderly migration without duplicate licensing costs."

Acceptance rate: 50% when negotiated at contract signing. After contract signing, this is extremely difficult to negotiate (SAP will cite "cloud migration requires separate agreements").

Support and Maintenance Exclusions in the GT&C

The GT&C defines what SAP's maintenance obligation covers. Standard language: "SAP will provide support for the licensed software in unmodified, standard configuration. Support does not include: (a) custom modifications or customisations, (b) third-party integration issues, (c) performance problems resulting from customer configuration, (d) issues arising from customer changes to system parameters."

This language is reasonable but often interpreted very broadly by SAP support teams. A performance issue is attributed to "customer configuration" when in reality it's an SAP scalability limit. You have no maintenance support for resolution.

Negotiation position: "SAP will support the software in standard and custom-modified configurations. Support includes troubleshooting performance issues regardless of cause, provided they affect critical functionality. If SAP determines the issue results from customer configuration, SAP will provide remediation recommendations. SAP's obligation to support does not require resolving all issues, but requires good-faith troubleshooting and escalation."

This is subtly different but creates an obligation for SAP to investigate and recommend fixes, not just declare issues out-of-scope.

GT&C Interaction with RISE with SAP

RISE with SAP is a cloud subscription model that replaces traditional perpetual licenses. The RISE with SAP GT&C is different from (and often more restrictive than) the traditional SAP GT&C.

Key differences:

• Version control: RISE with SAP requires that you stay current on SAP's quarterly release cycle. You cannot defer updates to align with your business calendar.
• Customisation restrictions: RISE with SAP GT&C often limits custom development. SAP prefers configuration-only deployments to reduce support complexity.
• Data residency: RISE with SAP GT&C specifies where your data resides (typically SAP's data centres). You cannot specify a different cloud provider or region unless you negotiate a cloud addendum.
• Performance guarantees: RISE with SAP includes SLA language (e.g., 99.5% uptime) that is absent from traditional GT&C. This is one area where RISE terms are stronger.

If you're evaluating RISE with SAP, do not assume your existing Master Agreement protections carry over. RISE with SAP has a separate GT&C with different terms. Negotiate that separately.

How to Negotiate the GT&C

Step 1: Request the GT&C Early — Before the Master Agreement negotiation, request the current GT&C and give it to your legal counsel. Identify the provisions that conflict with your business requirements. Raise these in the Master Agreement negotiation as ancillary issues.

Step 2: Prioritise Key Provisions — Focus your GT&C negotiation on the three highest-impact areas for your use case: (1) warranty disclaimers (if you have critical functionality requirements), (2) unilateral modification rights (if contract term is long), (3) technology use rights (if you plan cloud migration or virtualisation).

Step 3: Request a GT&C Addendum — Do not attempt to modify the GT&C document itself (SAP uses a standard template globally and resists customisation). Instead, request a "GT&C Addendum" that carves out exceptions for your specific situation. This is typically accepted more readily than wholesale GT&C modifications.

Step 4: Link GT&C Improvements to Master Agreement Concessions — "We'll accept your liability cap language in the Master Agreement if you accept our warranty carve-outs and modification notice requirements in the GT&C Addendum." This creates a package that makes the negotiation reciprocal.

Step 5: Escalate to Product Counsel — SAP's sales legal team has authority over the Master Agreement. GT&C issues are often handled by SAP's Product Counsel (different team). Request a call with both teams to discuss GT&C modifications. This signals you're serious and elevates the discussion above routine contract review.

Conclusion: Don't Let the GT&C Undermine Your Master Agreement

Enterprise buyers spend weeks negotiating the Master Agreement and ignore the GT&C. This is backwards. The GT&C often contains more dangerous provisions than the Master Agreement because it governs the operation of the entire agreement.

Key actions:

1. Read the GT&C before signing the Master Agreement
2. Identify the three highest-risk GT&C provisions for your use case
3. Negotiate GT&C modifications as a package (not piecemeal)
4. Request an addendum rather than trying to modify the GT&C template
5. Ensure Master Agreement language does not conflict with GT&C language (or explicitly overrides it)

A well-negotiated GT&C Addendum often prevents £200-400K in unexpected costs and operational restrictions over a 5-year contract term.