Modification rights in a RISE contract.

A RISE with SAP contract runs for five to seven years. The service inside it does not stay still. SAP releases new versions, deprecates features, restructures pricing, adds modules, retires modules, changes sub processors, and updates the technical specification. The modification rights inside the contract determine what SAP can change unilaterally, what requires buyer consent, and what triggers a remedy for the buyer. The standard contract gives SAP broad latitude to modify the service. The buyer who signs without negotiating modification rights signs a contract whose subject matter can change without their consent. This article walks through the modification rights that matter, the asymmetries inside the standard contract, and the provisions that restore balance.

Unilateral modification of the service

The standard RISE contract typically reserves to SAP the right to modify the service from time to time. The language is broad. It covers product changes, feature additions, feature removals, and technical reconfigurations. SAP commits to maintaining the overall service quality and to providing notice of material changes. The notice period is often short, and the buyer's remedy is limited to termination if a material adverse change occurs.

The buyer should narrow the modification right. The right should be limited to changes that do not materially reduce the functionality available to the buyer at signature. Where SAP intends to remove a feature, the buyer should have continued access for a defined period, typically twelve to twenty four months, to allow migration to an alternative. The notice period should be ninety days for material changes, with the right to escalate disputes about materiality to a defined process rather than to immediate termination only.

Deprecation of features and replacement obligations

SAP routinely deprecates older functionality as it pushes the product roadmap forward. The deprecation is part of the service lifecycle, and a contract that prevents deprecation entirely is unrealistic. The contract should specify how deprecation works, what replacement SAP is committed to providing, and what migration support the buyer receives.

The buyer should negotiate a deprecation clause that specifies the minimum notice period, the obligation to provide a functional replacement or to support continued use during transition, and the financial accommodation if the deprecation requires the buyer to invest in a parallel system. The clause aligns SAP behaviour with the buyer's planning cycle and protects the buyer against deprecation announcements that are too short for the business to absorb.

Pricing modifications during the term

The standard contract usually fixes the subscription fee for the term, subject to inflation indexation or other escalators. The buyer should confirm what is fixed and what can move. Fixed FUE pricing for the term is standard. Pricing for additions, expansions, and new modules is sometimes fixed and sometimes left open. The buyer should negotiate fixed pricing for any anticipated additions, with a forward pricing schedule that locks the discount on incremental capacity.

The buyer should also negotiate protection against indirect pricing modification. SAP cannot raise the price for existing capacity but may raise the price for adjacent services that the buyer depends on. The buyer should require that adjacent service pricing be fixed for the term or governed by the same escalator that applies to the main contract.

Service definition modifications

The service definition document inside a RISE contract specifies the operational commitments. Availability targets, response times, change windows, escalation paths. The document is sometimes treated as static and sometimes treated as modifiable by SAP. The buyer should clarify which.

The buyer should negotiate that the service definition document is part of the contract and cannot be modified by SAP without buyer consent. SAP may improve the service unilaterally, but degradation of the service definition requires buyer agreement and may trigger a credit or termination right. The provision prevents the situation where SAP shifts the operational commitments through unilateral document updates without renegotiating the price.

Technical specification modifications

The technical specification governs the SAP version, the database configuration, the network topology, and the integration capabilities the buyer can consume. The standard contract typically allows SAP to update the technical specification as part of the service lifecycle. The buyer should confirm what the update right covers and what it does not.

The buyer should negotiate that material technical specification changes, those that affect integrations, performance characteristics, or supported capabilities, require notice and a transition period. The buyer should also negotiate continued access to the previous version for a defined period after an upgrade, to allow the buyer to validate the new version against custom code and integrations before the cutover is irreversible.

Sub processor and infrastructure modifications

SAP runs the RISE service on hyperscaler infrastructure that SAP can change. The buyer signed for a service hosted on a specific hyperscaler in a specific region. The buyer should not be forced to accept relocation to a different hyperscaler or a different region without consent. The standard contract sometimes reserves SAP the right to move infrastructure to optimise SAP economics. The buyer should challenge the right.

The buyer should require that material infrastructure moves require buyer consent. The buyer should retain the right to be notified of any infrastructure change that affects data residency, network topology, or service performance, with the right to object if the change creates regulatory or operational issues for the buyer. The provision protects the buyer against unilateral infrastructure rationalisation that affects the buyer's compliance posture.

Conclusion

The modification rights inside the RISE contract are the mechanism through which the service can change during the term. The standard contract gives SAP broad rights to modify the service, the technical specification, the operational definition, and the sub processor configuration. The buyer who signs without restricting those rights signs a contract whose terms can shift away from the deal that was agreed. The negotiation should narrow the unilateral modification right, structure the deprecation mechanics, fix the pricing exposures, protect the service definition, govern the technical specification, and require consent for material infrastructure moves. None of the provisions is unreasonable to request. None is offered in the standard contract. The buyer's job is to identify the asymmetry and to close it before signature, when the leverage exists. After signature, every modification becomes a negotiation conducted under the original contract's terms, and the original contract's terms favour SAP.