The SAP Renewal Timeline: Preparation Starts 12 to 18 Months Before Contract Expiry

SAP contract renewals are not won in the final weeks before expiry. The decisive window opens 12 to 18 months earlier. What you prepare, structure, and decide during that period determines the quality of your next contract. Organizations that miss this window negotiate under time pressure, with an incomplete data foundation, and with an active auto-renewal risk in play.

This article walks through a phased model for structured renewal preparation, explains why SAP starts earlier than most customers expect, and identifies the most common timeline mistakes that forfeit the renewal governance moment.

Why SAP Starts Earlier Than You Do

One structural aspect of renewal preparation that is consistently underestimated in practice: SAP typically initiates the renewal dialogue with customers 12 to 18 months before contract expiry. SAP's renewal team operates with structured sales processes, a complete consumption history drawn from its own systems, and a clear objective for the next contract close.

For you, this means the following: if you have not yet started your own renewal preparation when the first SAP conversation arrives, you are facing a structurally prepared counterpart without an equivalent data foundation. This situation is not inevitable. It arises where consumption data is not consolidated on an ongoing basis and where renewal preparation is treated as an administrative task rather than a governance moment.

The renewal governance moment is the central commercial governance moment in the SAP contract cycle. Organizations that prepare it systematically enter the conversation on equal informational footing. Those that treat it as a formality hand the initiative to the other side.

The Phased Model (M-18 to M-0)

A structured renewal process divides into four phases. Each phase has clear tasks, typical owners, and a defined output. The model begins 18 months before contract expiry and ends with signing and the transition governance for the new term.

Phase 1 (M-18 to M-12): Inventory and Data Foundation

Phase 1 lays the groundwork for everything that follows. The goal is a complete, current picture of your contract position: what is agreed, what is actually used, and where the gaps are.

The first step in this phase is often the most labor-intensive: review all contract documents, including the Order Form, Schedules, Amendments, and any side agreements, for currency. Anything missing is requested from SAP. Schedule 5 as the price list reference is validated: unit prices, tier thresholds, minimum quantities. Credit balance development per contract year is reconstructed from monthly Balance Statements.

In parallel, consolidate consumption data. FUE utilization by user type for the past 12 to 18 months. BTP credit history by subaccount and project area. Cloud Managed Services usage against purchased volume. CAS package usage against paid volume. Prepare quality data as well: SLA compliance reports, ticket volumes, documented escalations.

Additionally, identify underutilization. Components where credits are being spent without reaching the agreed usage scope become visible in this phase. This is not a judgment on past operations; it is the factual basis for realistic volume planning in the next term. Raising underutilization for the first time during negotiations forfeits the earlier governance moment for targeted planning.

The output of Phase 1 is a complete overview of your contract position with a quantified delta between agreed and actually used volume. This overview is the foundation without which every subsequent phase rests on estimates.

Phase 2 (M-12 to M-9): Internal Alignment and Scenario Analysis

Phase 2 prepares the decision-making framework. The goal is an internally aligned picture of your requirements for the next term.

Here the stakeholder team is formally constituted: Contract Manager, Procurement, Controlling, and Executive. Each of these four roles brings a specific perspective without which later decisions will have blind spots. Assembling the team only in Phase 3 or 4 sacrifices lead time and creates information asymmetries within your own organization.

Based on the consumption data from Phase 1, three scenarios are defined. Scenario 1: status-quo renewal, extension on substantially unchanged terms. Scenario 2: volume or component adjustment based on the consumption analysis. Scenario 3: full renegotiation with changed contract parameters. Each scenario is assessed with its budget implications.

Finally, determine the projection requirements for the next term. What usage volumes are planned? New modules, a changed user population, planned BTP expansions, AI unit requirements. Where internal data or market knowledge is incomplete, Phase 2 is the right point to seek an independent assessment of your contract position.

The output of Phase 2 is an internally aligned decision framework: which scenario you are targeting, which parameters are negotiable, and which budget range has been cleared.

Phase 3 (M-9 to M-6): Clause Review and Negotiation Preparation

Phase 3 translates your data foundation and scenarios into a concrete negotiating position. The goal is a complete assessment of the critical clauses in your current contract and a documented starting point for the conversation with SAP.

Six clause areas determine how governable your next contract will be: the price adjustment clause (CPI mechanism), the auto-renewal clause, SLA structure and scope, exit clauses and data portability, the divestiture clause, and subscription flexibility. For each of these six areas, document what the current contract says and what should be different in the next term. This is the clause delta you bring into negotiations.

BTP consumption data is prepared in Phase 3 as structured negotiation input: a time series spanning 12 to 18 months, project allocation, cost center structure, and credit volume calibration for the new term. This is the most direct evidence of actual cloud usage below the FUE level.

Then initiate the first conversations with SAP proactively, before SAP takes the initiative on its side. Setting the timing of the conversation yourself means shaping the frame of the renewal dialogue.

The output of Phase 3 is a complete negotiating position: clause delta, structured data foundation, initial discussion status with SAP.

Phase 4 (M-6 to M-0): Negotiation, Close, Transition

Phase 4 is the execution phase. The groundwork was laid in the previous phases. Now you negotiate, decide, and close.

Conduct negotiations on the basis of the prepared data foundation: consumption analysis, clause delta, budget scenarios. The Executive releases the negotiation parameters in this phase. Having defined three scenarios in Phase 2 means entering negotiations with a clear margin to move.

Two operational points that are frequently noticed too late in Phase 4: lock-out periods and the auto-renewal decision. In the last six months before contract expiry, no new Managed Service or software subscriptions can be added; in the last twelve months, no new CAS units. Necessary component adjustments must be completed before these deadlines. The auto-renewal decision, whether to issue a termination notice or to let the contract roll, should be made no later than M-3, based on the state of negotiations and budget approval.

Phase 4 ends with signing the new contract and a documented transition governance: what runs until when under the old contract, and what starts under the new one.

The Most Common Timeline Mistakes

In practice, recurring patterns emerge that structurally undermine renewal preparation.

Data foundation as a bottleneck. The most common reason for a late start is not a lack of intent but a lack of data availability: FUE utilization, BTP credit time series, Balance Statement balances, SLA reports. This data cannot be reconstructed retroactively in four weeks. Organizations that do not maintain it on an ongoing basis discover in Phase 1 that the foundation for Phase 2 is missing.

Stakeholder involvement too late. Procurement learns three months before expiry that a renewal is coming. Controlling has no prepared consumption data. The Executive is only involved for the signing. This pattern leads to decisions being made without sufficient data or under time pressure.

Clause review as an afterthought. Clauses are often not reviewed until SAP has already submitted a proposal. At that point, the clause delta is a reactive document rather than a proactively defined negotiating framework.

Auto-renewal deadline as a structural risk. The contract rolls over without an active decision. The termination notice period, typically three months, is contract-specific and found in the Order Form. Organizations that have not anchored it in a deadline calendar risk an unwanted extension on terms SAP has communicated within the required notice window. This governance moment cannot be recovered after the deadline has passed.

Waiting reactively for SAP. Leaving the first contact to SAP means handing over the framing of the renewal dialogue. It does not have to be that way. Initiating contact proactively in Phase 3, on the basis of a complete data foundation, sends a different signal.

FAQ

When should I start preparing for a renewal?

No later than 18 months before contract expiry. The reason: the data foundation needed for a well-grounded negotiating position cannot be built on short notice. Consumption time series spanning 12 to 18 months, complete contract documentation, and stakeholder alignment all require lead time. Beyond that, SAP typically begins the renewal dialogue on its side within this same window.

What happens if I miss the auto-renewal deadline?

The contract renews automatically, typically for the original contract duration. SAP may increase the price for the new period, provided the increase was communicated at least 45 days before the renewal date. Renegotiation without a new opening is not possible. The right to terminate still applies if SAP announces a price increase, but the time available to act is then significantly shorter. The governance moment for a proactive negotiating position has already passed by that point.

Can I apply the phased model with a compressed timeline?

If the renewal date is less than 18 months away, the model needs to be adapted to the available time. Priority then is: build the data foundation (Phase 1), constitute the stakeholder team (Phase 2), complete the clause review (Phase 3). Phase 4 requires at least six months because the lock-out periods for new subscriptions apply before that. Organizations entering preparation with less than six months of lead time already have constrained options.

Next Steps

Start your renewal preparation with a clear structure. FinOptory's contract check delivers a complete inventory of your SAP contract position in four weeks: consumption data, clause assessment, and a data foundation for the renewal conversation. Fixed price: EUR 7,900. After four weeks, you know where you stand and which of the three renewal scenarios applies to your situation.

For the full picture: SAP Renewal Negotiation Framework covers all phases, data categories, and critical clauses. Building a Data Foundation for SAP Renewal goes deeper on the consumption, contract, market, and quality data that constitute a well-grounded negotiating position.

Created 2026-05-21. Version v1, status: draft, pending Bernhard review. Source basis: SAP_RISE/02_vertragsstruktur_enterprise_agreement.md, SAP_RISE/04_rise_betrieb_und_governance.md, SAP_RISE/07_service_description_guide.md (all partner-visible). SAP_RISE/08_rise_negotiation_playbook.md was not used.