Key Takeaways

  • SAP contracts span multiple documents — the master agreement, order forms, product supplements, and schedules all require review; a gap in any one creates risk.
  • 40 critical items organised into 8 review categories cover every material risk area in enterprise SAP agreements.
  • Pricing protections, renewal mechanics, and indirect access definitions are the highest-priority items in virtually every enterprise agreement review.
  • RISE with SAP agreements require an additional layer of review covering subscription exit rights, BTP credit mechanics, and infrastructure bundling.
  • This checklist is a starting point. Independent expert review is required for agreements over €5M — the financial risk is too high for internal-only review.

The SAP contract review checklist is the most practical tool available for enterprise buyers preparing to sign or renew an SAP agreement. SAP contracts are complex — structured across multiple documents with cross-references, standard terms that can be modified by schedule language, and supplemental agreements that may override master contract provisions in ways that are not immediately apparent. A systematic checklist approach ensures that no material risk area is missed.

This checklist covers 40 critical review items across 8 categories, structured to guide a methodical pre-signature review of any enterprise SAP agreement. It is based on our experience conducting independent SAP contract reviews for enterprises globally, and specifically targets the categories of clauses that generate the highest financial exposure. For a deeper analysis of the specific red flags this checklist is designed to identify, see our complete SAP contract red flags guide.

The checklist is a diagnostic tool — it tells you what to look for. Our SAP contract negotiation advisors tell you what to do about it.

SAP Contract Red Flags Series

Step 1: Identify All Documents to Review

Before beginning the checklist review, you must identify and assemble every document that forms part of your SAP agreement. SAP's contract structure typically includes the following, each of which may contain independent risk provisions:

  • Master Software Agreement (on-premise) or Cloud Framework Agreement (RISE/cloud)
  • All Order Forms and supplemental order forms
  • SAP General Terms and Conditions (the specific version referenced in your master agreement)
  • Product Supplements for each product line
  • Schedule of Named Users and Authorised Programmes
  • Enterprise Support terms and supplements
  • Migration or conversion addenda
  • Data processing agreements and privacy schedules
  • Any side letters or commercial amendments

A red flag in any one of these documents can create material financial exposure. Do not limit your review to the master agreement and the headline order form.

Category 1: Pricing and Cost Escalation

Pricing Risk — 8 Items

List price escalation cap — Is there a contractual ceiling on annual list price increases? High Risk
Support fee calculation base — Is Enterprise Support (22%) calculated on net invoice price or list price? High Risk
Support rate escalation — Is there a cap preventing the 22% support rate from increasing over the contract term?
Cloud subscription escalation — For RISE/cloud agreements, is there a cap on annual subscription price increases? High Risk
Expansion pricing — What mechanism governs the price for additional licences or user expansion? Is it capped relative to current pricing?
Currency and invoicing — Are invoicing currency and FX treatment specified? Unspecified FX provisions can create unplanned cost variance.
Price freeze during negotiation — Is pricing frozen during active renewal negotiation periods?
Verbal commitments converted — Have all pricing commitments made verbally by SAP account teams been reflected in signed contract language? High Risk

Category 2: Renewal and Term Mechanics

Renewal Risk — 7 Items

Auto-renewal provisions — Does the contract auto-renew? What is the notice window and how is it calculated? High Risk
Anniversary date alignment — Is the anniversary date clearly specified and aligned with your commercial planning cycle?
Renewal term duration — For how long does the contract auto-renew? (1 year on-premise; 3 years for RISE is common.) High Risk
Cross-document renewal consistency — Do all order forms, supplements, and schedules have consistent renewal terms and notice windows?
SAP notification obligation — Is SAP contractually required to notify you in advance of each renewal window?
Post-expiry rights — What are your rights to continue using SAP software if a contract expires without renewal?
Evergreen clause detection — Are there any evergreen provisions that create indefinite renewal absent specific termination?

Category 3: Licence Scope and User Definitions

Licence Risk — 7 Items

User type definitions with functional constraints — Are Professional, Limited Professional, Developer, Employee, and other user types defined with specific functional activities included and excluded? High Risk
Indirect access definition scope — Is indirect access scoped to specific integration scenarios, or broadly defined? High Risk
API and integration coverage — Are your known API integrations with third-party systems covered by existing licences or explicitly excluded from indirect access claims?
Authorised programmes list — Is the Schedule of Authorised Programmes complete and aligned with your actual deployment?
RPA and automation coverage — Are robotic process automation and bot-driven SAP interactions addressed in the indirect access provisions?
Named user vs. concurrent access — Is the basis of your licence (named user vs. concurrent) clearly specified and aligned with your usage patterns?
Developer licence restrictions — Are Developer and Technical User licence restrictions clearly defined and matched to your development team structure?

Category 4: Audit Rights

Audit Risk — 5 Items

Audit scope restriction — Is the audit right limited to systems where SAP software is actually deployed? High Risk
Permitted measurement tools — Are the specific tools SAP may use (USMM, LAW) specified, with SAP's custom tools excluded?
Notice period for audits — Is the minimum audit notice period specified and sufficient (target: 30 business days minimum)?
Audit frequency limits — Is there a cap on how often SAP can conduct audits (target: once per 12-month period)?
Dispute resolution for audit findings — Is there a clear process for disputing SAP audit findings, including independent verification rights?

Category 5: Support and Maintenance

Support Risk — 4 Items

Support tier specification — Is the specific support tier (Enterprise Support vs Standard) clearly specified in the order form?
Third-party support rights — Does the contract permit you to switch to third-party maintenance (e.g., Rimini Street) without penalty?
Bundled support products — Are any products included in your support package explicitly listed, with their individual expiry dates specified?
ECC maintenance continuity — If running ECC, is your maintenance term defined in relation to SAP's 2027 mainstream end-of-maintenance date?

Category 6: RISE with SAP and Cloud

RISE/Cloud Risk — 5 Items

Exit and termination provisions — Are there contractual exit rights for change of control, material breach, or voluntary exit with defined financial penalties? High Risk
BTP credit mechanics — Are BTP credit allocations, expiry dates, and eligible services clearly specified?
Infrastructure pricing transparency — Is the infrastructure component of the RISE subscription priced separately and benchmarkable?
Conversion of perpetual rights — Does the RISE agreement modify or remove any existing perpetual on-premise licence rights? High Risk
Data portability and exit data rights — What are your rights to export SAP data on contract termination, and are these specified in terms that work operationally?

Legal Risk — 4 Items

Governing law and jurisdiction — Is governing law and dispute jurisdiction specified as your home jurisdiction (not Germany)? Medium Risk
Liability limitations — Are SAP's liability limitations balanced against the financial exposure you face under audit and indirect access provisions?
Termination for convenience — Under what conditions can either party terminate the agreement, and are the financial consequences of termination specified?
Entire agreement clause — Does the contract clearly specify which documents form the complete agreement, preventing SAP from asserting rights under documents not included?

📋 How to Use This Checklist

Work through each category with the relevant contract documents open. For each item marked as High Risk, confirm whether the contract contains adequate protection, a red flag requiring negotiation, or an ambiguity requiring clarification. The output should be a prioritised list of negotiation items, ranked by financial impact. Our SAP contract negotiation service uses this framework as the basis for all pre-signature advisory engagements.

When to Run This Checklist

The optimal time to run the SAP contract review checklist is 6–12 months before contract execution — providing sufficient time to identify risks, build a negotiating position, and allow for multiple rounds of commercial discussion with SAP. Running it 2–3 weeks before signing limits your ability to address findings effectively.

Beyond the initial execution review, run the checklist before every renewal — ideally 6 months before the anniversary date — and before signing any addendum, supplement, or migration agreement that modifies your existing terms. These supplemental documents frequently introduce new risk provisions that weren't in the original agreement.

After completing your internal review using this checklist, compare your findings with a professional assessment. Our independent SAP contract review consistently identifies material risks that internal teams miss — not because internal teams aren't capable, but because SAP contract risk requires specific forensic knowledge of how SAP's tools, audit teams, and commercial practices interact with contract language in practice.

Frequently Asked Questions

How long does an SAP contract review take?
An independent professional SAP contract review for an enterprise agreement typically takes 5–10 business days, depending on the number of documents, agreement complexity, and the scope of the review. Internal reviews using this checklist can be completed in 2–3 days if the relevant documents are assembled and the review is conducted systematically. Allow additional time for negotiation preparation after the review identifies issues.
What documents do I need for a complete SAP contract review?
At minimum: the master agreement or cloud framework agreement, all order forms, the applicable SAP General Terms and Conditions (the specific version referenced in your contract), the Schedule of Named Users and Authorised Programmes, and any migration or conversion addenda. For RISE agreements, also include the specific RISE with SAP supplemental terms, BTP addendum, and infrastructure services agreement.
Can internal legal teams conduct a complete SAP contract review?
Internal legal teams can review SAP contract language for structural completeness and identify obvious red flags. However, a complete review requires forensic knowledge of how SAP's audit teams, USMM measurement tools, and commercial practices interact with specific contract language — knowledge that typically requires SAP-specific advisory expertise. The highest-value items (indirect access scope, user type functional definitions, RISE exit mechanics) are consistently missed by internal teams without SAP specialist support.

📬 SAP Contract Intelligence

Get Expert SAP Contract Analysis — Free

Independent analysis on SAP contract risks, renewal traps, and negotiation tactics. No SAP affiliation. Corporate email required.