Every SAP contract is a template that arrives substantially intact from the SAP regional legal team. The buyer-side review and redline of that template is where the most consequential, lowest-visibility work in the negotiation happens. The headline discount is what gets the internal approvals; the clauses are what determine the cost and the risk profile over the life of the deal. Across our 500+ engagements, the same five clauses surface as the highest-impact rewrites — the ones where a sentence of redline is worth seven figures over the term and the SAP regional legal team will (eventually) accept the change because they have accepted it in other matters. The work is to know which clauses are negotiable, which are not, and what the acceptable language looks like.
The audit clause: scope and notice
Every SAP master agreement contains an audit-rights clause that gives SAP the right to verify the buyer’s use of the licensed software. The standard SAP drafting tends to be broad: open-ended notice, broad scope, broad data exchange, and unilateral SAP-side control of the timeline. The four rewrites that matter:
Notice period — the SAP default is 30 days; we push for 60 days as standard and have secured 90 days on larger contracts. The notice period is what allows the buyer to assemble the internal team, route the matter through counsel, and begin the independent measurement before the operational clock starts.
Frequency — the SAP default allows for once-yearly audits; we push for once every two years as the standard cadence, with extraordinary audits requiring additional written cause. The longer cadence reduces the operational burden and the negotiation surface area.
Scope — the SAP default tends to allow audit of “all use of the licensed software, including indirect use by any third party.” The rewrite narrows this to the named systems in scope, the agreed metrics, and the methodology in the schedule.
Data exchange — the SAP default allows for on-site presence and direct system access. The rewrite restricts to remote data exchange under a defined protocol, with the buyer’s commentary attached. The full protocol is the one we describe in responding to the audit notification letter.
The indirect-access definition: the most important sentence
The indirect-access definition determines the entire shape of any future indirect-access claim. The standard SAP drafting is broad and forward-leaning: “use of the licensed software, whether direct or indirect, by any person or system, including but not limited to….” The buyer-side rewrite has three priorities:
Define indirect use precisely, with reference to identifiable interaction events — not as a catch-all that covers any conceivable system connection.
Carve out backend system-to-system traffic that does not involve a named or identifiable human user. Master-data synchronisation, batch reconciliations, BI extractions, and middleware orchestration should be specifically excluded.
Lock the chosen pricing model. If the buyer is on a Digital Access document model, the contract should state that document-priced traffic is the exclusive measurement basis for indirect use and that any residual named-user reading is disclaimed. The detail by approach is in our RFC connections and indirect-access risk piece.
The uplift mechanism: the silent multiplier
The annual uplift on maintenance or subscription is the single largest source of unexpected cost growth across our renewal-engagement portfolio. The standard SAP drafting allows for an uplift “in line with SAP’s then-current pricing policies” (which is to say, whatever SAP chooses). The rewrites we apply:
Replace the open-ended language with a defined cap — CPI, CPI+1, or a fixed three to four per cent ceiling, whichever is lower. We have moved SAP from a default 6.5 per cent uplift to a CPI-capped uplift on contracts above ten million euros annual value.
Define the index that CPI refers to, with a specific source and a defined measurement window. “CPI” without further qualification is not enforceable.
Lock the cap for the contract term, not for a defined initial period only. SAP will sometimes accept a low cap for years one to three with a reversion to standard for years four and five; the rewrite is to extend the cap for the full term.
The economics of the uplift cap are detailed in price benchmarks and discount bands.
The termination for convenience right
The standard SAP drafting does not provide a termination-for-convenience right. The buyer is locked in for the contract term and has no exit other than a material-breach termination, which is hard to invoke. The rewrite we secure on larger contracts is a termination-for-convenience right at defined anniversaries (typically year three of a five-year deal), with a defined notice period (six to twelve months) and a defined exit-cost framework (typically a stepped-down obligation rather than a full remaining-term liability). The right is not used often, but its presence dramatically changes the negotiation dynamics at renewal — the buyer is no longer renegotiating against a captive renewal but against a credible exit.
The data portability commitment (RISE-specific)
For RISE contracts and other hosted arrangements, the data portability commitment is critical and is usually absent or weak in the standard drafting. The rewrite covers four elements:
Export format and frequency — the buyer’s right to export their data in usable, machine-readable formats, on demand, throughout the contract term.
Export assistance — SAP’s obligation to provide reasonable assistance with an export, with a defined SLA on responsiveness.
End-of-term export — the buyer’s right to retrieve all data and configuration in a defined window after termination, with no additional fee.
Source-code escrow or equivalent for any buyer-specific extensions developed under the contract.
The detail is in the SAP RISE topic page and the RISE Conversion Economics white paper.
The change-of-control provision
The standard SAP drafting tends to allow SAP to terminate or renegotiate on a buyer change of control (acquisition, merger, divestiture). The rewrite limits SAP’s right to terminate to changes of control where the acquirer is a direct SAP competitor, and explicitly permits the buyer to assign or split the contract on internal restructuring, divestiture, or acquisition. This clause becomes critical when the buyer organisation is in any kind of corporate-development pipeline.
The warranty and SLA credit structure
The credit structure on SaaS and hosted services tends to be templated and capped at a fraction of the relevant monthly fee. The redlines we apply are modest but useful: lower the threshold for credit-triggering events, raise the cap on credits per quarter, and add specific credit categories for data-loss events and security incidents. The credits are not generally where the financial value sits, but the credit structure is where the SLA discipline is enforced.
What not to spend chips on
The clauses where the SAP regional legal team has very limited authority and where buyer chip-spend is wasted:
The definitions of the named-user buckets — these are templated globally and will not move materially.
The fundamental product-warranty disclaimers — these are also templated globally.
The governing-law and jurisdiction provisions — SAP holds firm on these for operational reasons.
The full list of templated-and-immovable clauses is in our Buyer’s Guide to SAP Contract Clauses. The chip-stack is best concentrated on the five clauses above, where SAP regional legal has actual discretion and has accepted the redlines in comparable matters.
The sequencing of the redline conversation
The order in which the rewrites are introduced matters. The audit clause should go in early — it sets the procedural footing for the relationship. The uplift cap should come with the commercial discussion, packaged with the price negotiation. The indirect-access definition should be introduced after the buyer has done the integration-topology inventory — the position is much stronger when paired with the evidence. The termination-for-convenience right is the chip the buyer keeps in reserve for the final stages of the negotiation, often released only when the headline discount is approaching the buyer’s target band. The full sequence is described on the SAP contract negotiation service page and worked through in the global manufacturer case file.
The headline discount is what the internal committee approves. The clauses are what determines the cost. The two negotiations are different conversations, and the clauses are where the longer-term value sits.
If you have a renewal in flight, or a new master agreement landing for signature, the priority is the clause-by-clause review before the redline is exchanged. We work alongside in-house counsel and procurement under engagement letter; the first conversation is at no cost. The SAP contract negotiation service page describes how we structure the work, and the renewal leverage strategies piece is the companion read.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.