SAP's standard terms and conditions contain 10 clauses that our team flags on every contract review. Every one of them is routinely negotiable. Most enterprises sign without ever challenging them. Here is what to look for and how to push back.
SAP's standard terms and conditions are not presented as negotiable because SAP does not want you to negotiate them. The standard agreement is designed to look complete, professional, and inevitable — a formality before you get to the commercially interesting conversation about price and implementation timeline. This is exactly how SAP wants it.
The reality is that every clause in SAP's T&Cs is the result of deliberate commercial engineering. Each provision maximises SAP's revenue, limits your recourse, and creates structural dependency that compounds over time. The 10 clauses below are the ones our SAP contract negotiation team flags on every review. None of them should be accepted without a fight. Read the full strategic overview in our SAP T&Cs complete guide.
SAP's standard audit rights clause grants SAP the right to audit your use of all licensed software at any time, with as little as 10 days' notice. It specifies that audits may be conducted using SAP's own measurement tools — USMM, LAW, STAR — which SAP controls and interprets without independent verification. The clause typically places all audit costs on the customer unless the audit reveals no compliance gap.
More dangerously, the standard clause does not limit the frequency of audits, does not specify what happens to the data collected by SAP's tools, and does not provide a binding dispute resolution mechanism for contested audit findings. SAP's measurement tools routinely overcount licence consumption, and without contractual dispute rights, you have limited ability to challenge the findings.
SAP's standard liability cap limits your total recovery to 12 months of the fees paid under the relevant Order Form. For a large enterprise paying £20 million annually in SAP licensing and support, this cap is set at the same level as your annual cost. But a catastrophic SAP failure — a major data breach, a botched upgrade that takes core systems offline for weeks — could cost multiples of that figure in operational losses, regulatory penalties, and recovery costs.
The cap is made more severe by the standard exclusion of consequential damages: lost revenue, business interruption, and reputational harm are all typically excluded from any recovery. Combined, these provisions mean that SAP's liability to you in the event of a catastrophic failure could be a tiny fraction of your actual loss. See our dedicated guide on SAP liability cap negotiation for the full picture.
Modern SAP agreements — particularly for cloud products including RISE with SAP and SAP BTP — include provisions that permit SAP to collect and process "anonymised and aggregated" data from your environment for product improvement purposes. The definition of "anonymised" is typically set by SAP, not you, and the data collected can include usage patterns, configuration data, and performance metrics that reveal commercially sensitive information about your operations.
This data flows to SAP's product development and commercial teams. SAP uses it to identify potential compliance gaps, prioritise new product development, and inform commercial strategy for customer renewals. You are, in effect, funding SAP's competitive intelligence operation. For detailed analysis, see our guide on SAP IP and data clauses.
SAP's Support Maintenance Schedule includes automatic annual escalation provisions that typically allow SAP to increase support fees by a defined percentage — often CPI plus a fixed amount — without further negotiation. Over a five-to-ten year agreement, this escalator can add tens of millions to your total cost of ownership. More significantly, the schedule is structured to auto-renew unless terminated within a narrow window, and terminating support — even to move to a third-party support provider — triggers complex licence restrictions.
Our SAP support cost reduction service has helped enterprises reduce ongoing support obligations by 30–50% through targeted renegotiation of these provisions.
SAP's standard definition of "use" of licensed software is deliberately broad. It captures direct user activity and typically extends to any process or system that creates, reads, modifies, or deletes data in an SAP system — regardless of whether a licensed user was directly involved. This is the contractual foundation of SAP's indirect access programme, through which SAP has extracted over $1 billion in additional licence revenue since 2017.
Without explicit contractual definition of what constitutes indirect access, SAP retains maximum flexibility to assert liability for third-party system integrations, custom applications, and automated processes that interact with your SAP landscape. Our indirect access advisory service specialises in restricting this exposure.
Are these red flags in your current SAP agreement?
Our SAP contract negotiation experts will review your Master Agreement and identify every problematic clause, with a prioritised negotiation brief. Book a free consultation to start.
SAP's standard agreements — particularly multi-year cloud commitments for RISE with SAP — do not include a customer right to terminate for convenience. Once signed, you are locked in for the full contract term with no unilateral exit mechanism. This means that changes in your business strategy, technology direction, financial position, or M&A activity cannot release you from your SAP commitments without significant financial penalty.
RISE with SAP agreements are typically five-year commitments. An enterprise that signs a RISE agreement and then decides two years later to change strategy, divest a division, or move to an alternative cloud platform faces the full remaining contract liability — potentially tens of millions of dollars. See our article on SAP termination rights for negotiating exit provisions.
SAP's cloud agreements typically include provisions that allow SAP to modify, update, or discontinue product functionality with limited notice. While SAP presents this as necessary for cloud service delivery, the practical effect is that SAP can change what you are paying for mid-contract. Features you selected, integrations you built, and workflow configurations you depend on can be altered or removed at SAP's discretion.
For enterprises that have made significant investments in SAP configuration and custom development, unilateral product change rights represent a real operational risk. The standard clause provides minimal compensation for the disruption caused by material product changes.
SAP's change of control provisions are typically drafted to protect SAP's interests in customer restructuring events — they require SAP's consent for licence transfers arising from acquisition, merger, or divestiture. But they rarely provide corresponding protection for the customer when SAP itself is the subject of a change of control. If SAP is acquired by a private equity firm or another technology company, your agreement terms may change materially with limited recourse.
SAP's standard agreements typically specify German law or the law of the relevant SAP entity's home jurisdiction as governing law. For UK, US, Australian, and other non-German enterprises, this creates practical challenges in contract interpretation, dispute resolution, and legal enforcement. German commercial law has specific characteristics — particularly around implied warranties and liability — that differ materially from common law jurisdictions in ways that can disadvantage enterprise buyers.
For cloud agreements, SAP's service level agreements are presented as robust commitments to uptime and performance. The reality is that SLA remedies — the service credits available when SAP misses its commitments — are typically set at a fraction of the financial harm caused by a service outage. A 99.9% monthly uptime SLA sounds impressive until you calculate that it permits nearly 9 hours of downtime per year, and that the associated service credits are typically capped at 10–30% of monthly fees regardless of the actual business impact.
Identifying red flags is only half the work. Converting them into successful negotiating positions requires commercial leverage, precise legal language, and the expertise to know which battles SAP will genuinely fight and which it will concede. Our SAP contract negotiation team has the experience to navigate this process efficiently. We know SAP's negotiating patterns, we know the positions SAP's legal team will defend, and we know where the commercial concessions are available.
The most important principle is timing: every one of these red flags is easier to negotiate before you sign than after. The moment you have committed to SAP commercially, your leverage diminishes substantially. Build your T&Cs negotiation into your procurement process from the start, not as an afterthought once the business decision has been made. For the complete framework, see our SAP T&Cs enterprise guide. And consult the SAP licensing basics guide for foundational context on how SAP's commercial model works.
Prioritise in order of financial impact: (1) liability cap and consequential damages exclusion — these define your worst-case recovery; (2) audit rights — these govern your compliance exposure; (3) indirect access definition — this caps your uncapped liability exposure; (4) support fee escalation — this defines your long-term cost trajectory. If you can move these four, you have materially improved your position.
No. SAP negotiates T&Cs regularly with enterprise customers. The standard agreement is a starting position, not a final offer. SAP's willingness to move on specific provisions depends on your commercial value to SAP, the timing relative to SAP's fiscal year, and the quality of your counter-positions. Independent advisory support significantly improves negotiation outcomes by ensuring your positions are well-prepared and commercially credible.
Yes — and cloud agreements introduce additional complexities. RISE with SAP agreements bundle multiple products under layered T&Cs, each with its own provisions. The telemetry data clauses, unilateral product change rights, and SLA remedy limitations are particularly significant in cloud agreements. RISE with SAP five-year commitments make the termination for convenience provision especially important to negotiate before signature.
A thorough T&Cs negotiation typically takes six to twelve weeks from initial contract receipt to execution-ready agreement. Attempting to compress this timeline is the most common mistake enterprise buyers make — and it consistently produces worse outcomes. Build the negotiation period into your procurement schedule from the outset.
📬 SAP Licensing Intelligence
Expert analysis on contract negotiation, audit defence, and cost reduction. Buyer-side only. Corporate email required.
Independent SAP licensing advisory — not affiliated with SAP SE. SAP, S/4HANA, RISE with SAP, and all SAP product names are trademarks of SAP SE.