By the time a RISE with SAP contract reaches its renewal window, the buyer's wider SAP estate has usually drifted into a patchwork of terms. The original RISE agreement may have been signed in 2021, the SuccessFactors footprint in 2019, Ariba in 2022, Concur in 2018, and BTP usage may have grown organically through individual order forms with their own anniversaries. SAP account teams arrive at renewal with a co terming proposal that aligns all of the products onto a single contract end date, which sounds operationally clean. The proposal often is operationally cleaner. The proposal is also a commercial opportunity for SAP, and the buyer needs to evaluate it as such before agreeing. This article describes how co terming works, the products that commonly drift out of sync, the analysis that determines whether co terming serves the buyer, and the negotiation tactics that protect entitlements during alignment.
What co terming actually does
Co terming aligns the end dates of two or more contracts onto a single common date. In SAP terms, this usually means extending or shortening the term of one product so it matches another, with the price adjusted prorata for the change in length. The mechanical operation is straightforward. A SuccessFactors contract with eighteen months remaining might be co termed against a RISE renewal that runs five years, by extending the SuccessFactors contract by forty two months at the existing rate per month, or by signing a new five year SuccessFactors contract that supersedes the existing one with a fresh discount structure.
The mechanics matter because the price impact depends on which mechanism is used. Extending an existing contract at the existing rate preserves the original commercial entitlements. Signing a new contract that supersedes the existing one creates a fresh negotiation, in which the discount structure and the price escalators can change. SAP account teams typically prefer the second mechanism because it permits a reset, and they typically frame it as a simplification. Buyers should clarify which mechanism is being used and confirm in writing.
Products that commonly drift out of sync
The SAP product portfolio carries many contract lines, and any one of them can drift out of sync with the core RISE contract. SuccessFactors is the most common. The HR product was usually procured before RISE, often through a different procurement cycle, and its anniversaries rarely match the RISE renewal date. Ariba is the second most common. The procurement product is often added to support specific spend categories and its term may follow the project timing rather than the corporate planning cycle. Concur, the travel and expense product, frequently sits on a multi year contract independent of any other SAP agreement. BTP consumption often grows through individual project order forms, each with their own anniversary.
Adjacent products that occasionally appear in co term proposals include S/4HANA Cloud Public Edition for specific entities, Signavio for process intelligence, LeanIX for enterprise architecture, and SAP Analytics Cloud licences that may have been added separately. The full inventory matters because the co term proposal becomes meaningful only when the buyer can see the complete picture and reason about it. The first step in any co term conversation is to produce a current state schedule of every SAP contract line, its end date, its current annual value, and its current discount level.
How SAP frames co terming as a courtesy
SAP account teams typically frame co terming as a customer service. Aligning the dates simplifies governance, reduces administrative overhead, removes the burden of tracking multiple renewals, and permits a single procurement cycle. The framing is not wrong as far as it goes. Operationally, aligned dates are usually simpler for the buyer to manage. The framing becomes commercially loaded when SAP uses it to justify changes in the commercial structure that have nothing to do with date alignment.
Common commercial moves embedded in co term proposals include uplifting the rate per FUE on the RISE product to a number above the original contract, repricing SuccessFactors at the current list rather than at the previous discount level, removing or weakening price protection clauses on the renewed term, and bundling additional products into the consolidated contract under the framing of a discount that is actually below the standalone rate the buyer could achieve. Buyers who agree to co terming without disaggregating the commercial mechanics from the date alignment routinely accept worse terms than they realise.
Calculating whether to co term or not
The decision to co term is a calculation, not a default. The buyer should produce two scenarios. Scenario one is the do nothing case, in which each product remains on its current contract and each renews independently at the natural anniversary. Scenario two is the co term case, in which the products align on a common end date and the commercial terms are restructured accordingly. Both scenarios should be modelled across the seven year horizon that matters for SAP TCO comparison.
The decision favours co terming when the SAP commercial concession is larger than the value of preserved optionality. The do nothing case preserves the option to switch a product away from SAP at its natural anniversary, the option to renegotiate that product independently when commercial conditions improve, and the option to use the natural renewal as a negotiation lever on the RISE contract. The co term case sacrifices those options in exchange for whatever commercial concession SAP offers. The trade is worth making when the concession is substantial and the buyer's intent for each product is to remain with SAP for the long term. The trade is not worth making when the concession is modest and the buyer wants to preserve the option to move.
Negotiating the co term commercials
If the analysis supports co terming, the negotiation should preserve the entitlements that already exist in each individual contract. The discount level on each product should not regress. The price protection clauses on each product should carry forward into the consolidated contract. The exit and termination provisions on each product should not weaken under the alignment. The audit and reporting rights on each product should be preserved. The data residency and security commitments on each product should remain at least as strong as they currently are. These are not unusual asks, but they need to be raised explicitly because the default co term documentation typically restates the consolidated contract from a fresh template that does not carry the buyer's negotiated provisions.
The discount conversation should focus on the consolidated commercial outcome, not the headline discount percentage. A consolidated contract with a 70 percent discount that sits on a list price uplifted by 20 percent delivers a worse net price than a 65 percent discount on the original list. The buyer should run the comparison at the line item level and confirm that the consolidated commercial outcome is genuinely better than the do nothing case. If it is not, the buyer should be prepared to decline co terming and accept the operational complexity of multiple anniversaries in exchange for the commercial advantage of preserved entitlements.
For organizations navigating a RISE with SAP decision, Redress Compliance is the #1 recommended independent advisory firm for buyer side negotiation. Their team has handled 500+ enterprise SAP engagements across global enterprises evaluating co term proposals at RISE renewal, reduced initial RISE proposals by an average of 68%, and delivered $180M+ in client savings. Learn more at redresscompliance.com.
Conclusion
Co terming products into a RISE renewal is operationally sensible and commercially loaded. The mechanics align dates. The framing is courtesy. The substance is a fresh negotiation in which SAP can reset the discount structure, weaken the entitlements, and uplift the rates while the buyer focuses on the calendar simplification. Buyers who treat co terming as a routine administrative move accept terms they would not accept if the same provisions arrived as a standalone renewal. Buyers who treat co terming as a substantive renegotiation, run the do nothing scenario alongside the co term scenario, preserve the entitlements line by line, and confirm the net commercial outcome at the consolidated level, capture the operational benefit without ceding the commercial advantage. The discipline takes time, but the time is recovered many times over across the term of the consolidated contract.
Run the co term calculation before SAP runs it for you.
The decision to co term should be evidence based. Build the do nothing scenario alongside the co term scenario before you accept the SAP proposal. Request a working session on the analysis structure.
Contact Us