Line by line review of every RISE order form, schedule, and exhibit before signature.

Why even sophisticated procurement teams sign RISE contracts they would not have written.

RISE with SAP arrives as a multi document package. There is a master agreement that may date back ten years, a RISE specific order form, two or three schedules covering services and pricing, a hyperscaler appendix, and a data processing exhibit. The order form references the master, the master references SAP standard general terms, and the standard general terms reference policies hosted on a SAP URL that can change without notice. Few procurement teams have the bandwidth or the SAP specific fluency to follow the trail through.

The consequence is predictable. Buyers sign RISE deals containing automatic price escalators that compound annually, indirect access clauses that expose mobile and partner traffic to retroactive true ups, exit terms that require ninety days of parallel run at full RISE price, and discount structures that look generous in year one and collapse in year four. None of these clauses are hidden. They are simply not noticed in the rush to close before quarter end.

The work of contract review is not adversarial. It is structural. Every clause has a purpose, and most have a counter clause that protects the buyer with equivalent precision. The redline document we deliver typically rewrites twelve to twenty clauses across the package. Each rewrite is paired with the SAP commercial argument that justifies it and the precedent from other RISE deals that supports it.

The seven document layers of a RISE with SAP package.

RISE proposals look like a single contract. They are not. They are layered documents, and each layer has its own risk profile.

We read every layer in sequence. We build a single risk register that cross references clauses across layers, since a permissive clause in layer two is often constrained by a stricter clause in layer six, and vice versa. SAP account teams know these interactions. Most buyers do not.

Seventeen clauses that almost always need rewriting.

Across 500 plus engagements, certain clauses appear with such regularity that they have become standard targets in the redline. We do not propose to rewrite a clause unless we have precedent from a comparable RISE deal showing that SAP has accepted the rewrite before.

1. Automatic price uplift. Most RISE order forms include a year over year inflator. Three to five percent is typical. We negotiate it to fixed numbers, capped at a published index, or removed entirely for the first three years.
2. Indirect access carve out. Standard RISE language treats every external user as a potential FUE. We rewrite this to define indirect access narrowly and exclude documented mobile and partner traffic categories.
3. Document and digital access volume caps. The Digital Access Adoption Programme model is volume based. We negotiate ceilings on the per document price, true up windows, and grace periods for spikes.
4. Renewal price protection. Default renewal language refers to SAP list price at the time of renewal. We rewrite it to the lower of list price or original price plus capped inflation.
5. Termination for convenience. Almost never included by default. We negotiate a partial termination right that allows scope reduction at renewal milestones.
6. Step down rights. Buyers should be able to reduce FUE volumes during the term if business conditions change. We negotiate a fifteen percent step down right with no penalty.
7. Hyperscaler change rights. RISE pins workloads to a specific hyperscaler. We negotiate the right to change hyperscaler at renewal at no cost.
8. SLA credit caps. Standard SLAs cap credits at trivial percentages. We negotiate uncapped credits for repeated breaches.
9. Audit cooperation cost. SAP audit clauses often require the buyer to fund SAP audit teams. We negotiate a cap on this cost and a notice requirement.
10. Custom code support. RISE excludes custom code by default. We negotiate a defined custom code support window.
11. Exit data extraction format. Default exit language allows SAP to deliver data in proprietary formats. We negotiate open standard delivery.
12. Parallel run obligation. Exit clauses often require the buyer to keep RISE live during migration. We negotiate the parallel run window down to thirty days.
13. Source code escrow. Not standard in RISE. We negotiate escrow for custom developments and configurations.
14. Sub processor approval. Default GDPR exhibits allow SAP to add sub processors freely. We negotiate a notice and objection process.
15. Liability cap floor. Standard caps tie to twelve months of fees. We negotiate a floor for data loss and privacy breaches.
16. Force majeure scope. Standard force majeure clauses excuse SAP from broad categories of failure. We narrow the scope materially.
17. Most favoured customer. Difficult to obtain but worth pressing. Partial MFC for specific terms is sometimes achievable.

Four phases from intake to signed redline.

What the buyer ends up with.

At the end of a contract review engagement, the buyer holds three artefacts. The first is a redlined version of every document in the package, with every change tracked and annotated. The second is a risk register that classifies every remaining clause as accepted, accepted with comment, or to be revisited at renewal. The third is a negotiation playbook that summarises the SAP commercial logic behind each accepted concession, so the buyer is positioned to defend the contract internally and at renewal.

Average outcomes across 500 plus engagements include $2.1M in exposed savings across the seven year term, seventeen clauses rewritten on average, and a documented audit trail that supports both compliance reporting and renewal negotiation.