SAP contract terms, A–Z.
First the structure — what you actually sign, and what it drags in by reference. Then the vocabulary: what each term governs, why SAP moves on it or doesn't, and what shifts it. Written for the people who sign — not a legal commentary, a negotiator's view.
You don't sign one contract with SAP. You sign an order form — and the order form incorporates a stack of further documents by reference: six in SAP's own sample, twenty-five and more once each supplement brings in the services it bundles. A supplement per cloud service, a service description behind each supplement, a support schedule, a service level agreement, a data processing agreement, the AI terms, the general terms and conditions — or a master agreement carrying eight schedules of its own. Each is a separate file. Each lives at a URL SAP controls, carries its own version stamp, and changes edition without anyone re-signing. Most are never printed.
That structure is where the money hides. The metric that sets the price is defined in one document; the right to raise the price at renewal in another; the cap on what SAP owes you when it fails in a third; and the paragraph that decides which of them wins when they disagree sits in the order form itself, usually unread. Every term on this page belongs to one of those documents — the index below says which.
The cloud services, the usage metric, the quantity, the fee, the term, the renewal mechanics — and, in its Referenced Documents clause, the list below in order of precedence. The only document written for you and the one that wins when documents disagree.
Terms here: Order of Precedence · Referenced Documents · Subscription Term · Renewal Term · Fee Increase · Price Protection · Discount
Published at sap.com/agreements-cloud-supplement, one for every cloud service on the order form. Each supplement is where the usage metric, the bundled services and the product-specific SLA changes are defined — and each bundled service is itself "subject to the supplemental terms" of its own. The private-edition supplement bundles thirteen further services; the public edition bundles thirteen, one of which needs a separate Concur order form.
Terms here: Full Use Equivalent · Digital Access · Subscription Term
Pulled in by each supplement: metrics, ratios, sizing, system tiers, what "Document" or "Full Use Equivalent" means for that service. The private-edition guide runs to 133 pages. The number that determines the whole price is defined here and almost never read before signature.
Terms here: Full Use Equivalent · Digital Access · Named User
Support levels, response times, the definition of an incident. One document across the cloud portfolio.
The availability commitment and the credit formula — 99.7 % per month, 2 % of the monthly fee per 1 % below, capped. Private cloud edition and tailored option carry their own SLA alongside it; supplements may change the number for a specific service.
Terms here: Service Level Agreement
Roles, security measures, sub-processors, transfer mechanisms; the technical and organisational measures sit in a further schedule. Uniform across the install base; amended mainly where a regulator requires it.
Terms here: Data Processing Agreement
The AI Terms apply to every AI technology inside any cloud service; the AI Units Supplement and the AI Services List apply the moment AI units are on the order form — consumption metric, pooling, expiry, per-service conversion factors.
Liability, IP, confidentiality, termination, governing law. Under a Master Cloud Customer Agreement this slot is the MCCA, which itself packages the support schedule, the SLA, the DPA, the security measures, the product development schedule, the AI Terms, the professional-services schedule and the GTC as its eight schedules — signed once, then incorporated by every order form that follows.
Terms here: Limitation of Liability · Assignment · Termination for Convenience · Audit · Territory
Financial Services Annex and Cyber Security Annex for regulated customers; a partner's own agreement where the deal is partner-sold; termination or conversion addenda where on-premise licences are retired into the subscription.
Terms here: Conversion Credit · Maintenance Base
- SAP's sample cloud order form lists six documents in its Referenced Documents clause.
- Under a Master Cloud Customer Agreement, the order form lists three — but the MCCA it points to carries eight schedules.
- The private-edition supplement bundles thirteen further cloud services, each subject to its own supplemental terms and service description.
- Every additional product on the order form adds at least its supplement and its service description; several add an SLA of their own.
- The SAP Trust Center listed 301 supplement documents in English on 17 September 2026. A large enterprise buying across the portfolio can hold twenty of them under one signature.
SAP groups all of this into four building blocks — order form, cloud service description, data processing agreement, general terms. Those are categories. The documents multiply with what you buy. On-premise the shape is the same under different names: order form and Schedule 1, then Software Use Rights, Support Schedule, DPA, GTC.
ECC, S/4HANA on-premise, SAP Cloud ERP Private / RISE, GROW and BTP: which documents carry a signature, which are incorporated, where the money and the metric live, the order of precedence, version stamps, and the sources.
SAP's commercial paper — order forms, licence and cloud agreements, support schedules, supplements — runs on a vocabulary of its own. Most of it is never explained to the people who carry the decision. This is the vocabulary with the commercial view attached: for each term, what it governs, why SAP does or does not move on it, and the lever that shifts it.
- OpenRoutinely moved. Ask as a matter of course; not asking is leaving money on the table.
- MovableMoves with pressure, volume, timing or escalation. Expect a fight, expect to win something.
- HardMoves rarely and usually only at large deal size or board level. Trade for it, do not expect it free.
- FixedEffectively non-negotiable in standard paper. Spend your capital elsewhere; manage the consequence instead.
Before a negotiation, filter to open and movable and build the ask list from that. During red-lining, anything rated fixed that has nonetheless been granted is a genuine win — flag it in renewals rather than letting it lapse silently.
A
-
A support portfolio for customers under strict security or data-privacy regulation: support delivered under additional controls on who may access the systems and from where.
Why, and the lever → -
Affiliate Use
HardWhether group companies may use the licensed software, and on what basis.
Why, and the lever → -
Assignment
HardWhether the agreement can be transferred, typically on a merger, acquisition or divestment.
Why, and the lever → -
Audit
MovableSAP's right to verify licence compliance, the notice required, frequency, and who bears cost.
Why, and the lever →
C
-
Continuous Quality Check
FixedCQC: at least one remote quality-check service per year for each supported solution under Enterprise Support, delivered through SAP's lifecycle tooling, ending in an action plan or written recommendations.
Why, and the lever → -
Conversion Credit
MovableCredit granted for terminating existing licences, applied against a new purchase; the terminated licences' maintenance base is removed.
Why, and the lever → -
The customer's own SAP support organisation, which SAP recognises through a primary certification — remote, free under Enterprise Support on request — and which is a precondition for some of SAP's other support arrangements.
Why, and the lever →
D
-
Roles, security measures, sub-processors and transfer mechanisms for personal data.
Why, and the lever → -
Delivery of Software
FixedHow the software is made available, typically electronic download with an S-user ID and passcode stated in the order form.
Why, and the lever → -
Digital Access
MovableSAP's document-based licensing model for indirect scenarios, charging by documents created rather than by users.
Why, and the lever → -
Discount
OpenReduction from list price on licence or subscription fees, applied per line item.
Why, and the lever →
F
-
Fee Increase
MovableSAP's right to raise support or subscription fees at renewal, usually capped by reference to a published index.
Why, and the lever → -
Full Use Equivalent
FixedThe RISE / S/4HANA Cloud aggregation metric. Individuals are converted into a single pooled number at fixed ratios, and the pool may be reallocated between use types during the term.
Why, and the lever →
I
-
Indirect Use
HardAccess to SAP data or functions by people or systems that never log into SAP directly - through a portal, a middleware layer, a bot or a third-party application.
Why, and the lever → -
Initial Response Time
FixedWhat SAP's support service levels actually measure: the time until a qualified response, and — for the highest priorities — a corrective-action target for a resolution, a workaround or an action plan. Not a resolution time.
Why, and the lever → -
Initial Term
MovableThe first committed period, after which renewal mechanics take over. On-premise support terms commonly run to 31 December of the following full calendar year, which makes the real first term anywhere from 12 to 24 months.
Why, and the lever →
L
-
The cap on each party's damages and the categories excluded.
Why, and the lever → -
Local Business Hours
FixedThe clock the medium- and low-priority response targets run on: eight to six, Monday to Friday, in the customer's local time zone, excluding local holidays.
Why, and the lever →
M
-
Mainstream Maintenance
FixedThe first of SAP's maintenance phases for a release: full support under the customer's support agreement from release-to-customer through the unrestricted shipment phase. It is followed by extended maintenance where SAP offers it — at an additional fee and under a separate contract — and otherwise, automatically and at the unchanged support fee, by customer-specific maintenance with a restricted scope and no expiry date.
Why, and the lever → -
Maintenance Base
MovableThe notional licence value the support fee is calculated on. It is not the amount actually paid - it survives discounts, and it persists after the licence fee is long forgotten.
Why, and the lever →
N
-
Named User
HardThe classic on-premise metric: a licence per individual authorised to access the system, by user type, irrespective of actual use.
Why, and the lever →
O
-
Order of Precedence
MovableWhich document controls when the stack disagrees. Order forms list it explicitly.
Why, and the lever →
P
-
Price Protection
MovableA ceiling on future pricing for additional quantities or renewals.
Why, and the lever →
R
-
Referenced Documents
HardStandard terms incorporated by URL - use rights, support schedule, DPA, GTC, supplements.
Why, and the lever → -
Renewal Term
MovableAutomatic extension periods following the initial term, each typically one year.
Why, and the lever →
S
-
SAP ActiveAttention
MovableThe mid-tier premium engagement — successor of SAP ActiveEmbedded — with a defined set of proactive services and a smaller named SAP team than MaxAttention.
Why, and the lever → -
SAP Cloud ALM
FixedSAP's application lifecycle management tooling for cloud and hybrid landscapes, delivered as part of Enterprise Support, cloud editions under published usage rights — the successor role to SAP Solution Manager.
Why, and the lever → -
SAP EarlyWatch Alert
FixedThe automated monitoring report SAP generates on a supported system's health, performance and configuration, delivered as part of Enterprise Support and used by SAP to trigger further quality checks.
Why, and the lever → -
The default support level for on-premise software: mission-critical support with response-time commitments, the Support Advisory Center, Continuous Quality Checks, SAP EarlyWatch Alert, application lifecycle tooling, and the right to a service-level credit when SAP misses its own targets.
Why, and the lever → -
The support included in every cloud subscription fee: case handling with published response targets, 24×7 mission-critical support for the two highest priorities, the customer support website, and application lifecycle tooling.
Why, and the lever → -
A time-bound subscription that keeps ECC on SAP HANA in service from 2031 to 2033 for customers whose conversion will not be complete when extended maintenance ends in 2030, delivered through SAP's private cloud with transformation services attached.
Why, and the lever → -
SAP MaxAttention
MovableSAP's top premium engagement: a long-term, individually scoped partnership with named SAP experts, on-site and remote, around the customer's business goals as much as its technical landscape.
Why, and the lever → -
SAP Preferred Success
MovableThe paid add-on above Enterprise Support, cloud editions: faster response targets, a corrective-action target for high-priority cases, designated contacts, strategic guidance and success programmes for eligible cloud services.
Why, and the lever → -
PSLE: the support offering for large customers who run their own support organisation — the fundamental support services, tools and methods without the engagement layer of Enterprise Support, priced separately.
Why, and the lever → -
SAP Standard Support
HardThe lower on-premise support level: incident handling and updates without the mission-critical commitments, the Advisory Center and the quality checks that define Enterprise Support.
Why, and the lever → -
The global unit inside SAP support that handles very-high-priority incidents and top issues for Enterprise Support customers: an additional escalation level with round-the-clock root-cause analysis, quality-check planning and one Enterprise Support report a year on request.
Why, and the lever → -
SAP Value Assurance
MovableSAP's premium engagement for implementation projects led by the customer or a partner: safeguarding services scoped to a specific programme and its go-live.
Why, and the lever → -
Service Level Agreement
MovableAvailability commitment for cloud services and the credits payable when it is missed.
Why, and the lever → -
Subscription Term
MovableThe committed period for cloud services, and the basis on which volumes may change.
Why, and the lever → -
Support Case Priority
FixedThe four priorities a support case can carry — very high, high, medium, low — and the response targets each one triggers. The definitions are published and the customer sets the priority.
Why, and the lever → -
Support Percentage
HardThe multiplier applied to the Maintenance Base to produce the annual support fee. Standard enterprise support sits at 22%; SAP Product Support for Large Enterprises (PSLE) is priced separately.
Why, and the lever →
T
-
A right to exit without cause.
Why, and the lever → -
Territory
OpenWhere the software may be used, usually worldwide subject to export control.
Why, and the lever →
No terms carry this rating yet.
Before you rely on any of this. The ratings are judgement, not legal advice, and not a guarantee of what SAP will do in any given quarter. SAP's standard terms change: verify current wording in the standard documents published at the SAP Trust Center before using a definition in a live negotiation. Never state a current standard term from memory.