SAP renewal timing and the windows that matter

Most SAP renewals close on the last working day before the agreement expires. The renewal package is presented as a single bundle, the discount is presented as a final offer, and the buyer signs because the alternative is to lose maintenance on a system the business depends on. The whole sequence appears to be driven by the calendar. It is not. The calendar is the negotiating instrument that produces that outcome, and procurement teams that treat the renewal date as fixed give up the largest single piece of leverage in the SAP relationship. This article sets out the windows that matter, the windows that do not, and how to engineer the close into the right week.

The two clocks running at cross-purposes

There are two clocks running in any renewal cycle. The buyer's clock is the maintenance expiry date in the contract. SAP's clock is the quarterly and annual bookings cycle. The renewal closes on the buyer's clock by default. The disciplined procurement function moves the close onto SAP's clock and uses the difference to extract a discount.

The mismatch is structural. SAP's bookings teams are measured on quarterly attainment. A booking that lands inside SAP's Q1 carries less weight than the same booking inside SAP's Q4. The buyer who can credibly hold the close into the last week of SAP's Q4 obtains a price reduction that, in our portfolio, sits consistently in the four to seven per cent band on a like-for-like basis. That is before any substantive negotiation on entitlements.

The twelve-month runway

The buyer-side renewal process should begin twelve months before the maintenance expiry date. Twelve months gives the buyer enough runway to run a license-position assessment, an entitlement reconciliation, a usage analytics exercise, and a competitive-alternatives review. Twelve months is also long enough to make a credible deferral threat: the buyer who can credibly run on perpetual licences with paid lapsed maintenance for one or two quarters is in a different conversation from the buyer who needs to close before expiry.

Procurement teams that begin the renewal conversation inside the last ninety days are negotiating from a defensive position. The runway is the precondition for everything else.

What happens in month nine

By month nine before expiry, the buyer should have completed an internal license position. The position document sets out current entitlements, current use, and the gap between them. It identifies shelfware (entitlements that exceed use) and exposure (use that exceeds entitlements). The position document is the basis for everything that happens in the renewal.

The position should be reconciled against USMM, LAW, the engine measurements, and the indirect-access topology map. The reconciliation is the document that determines what the buyer asks for in the renewal: contraction on shelfware, conversion of exposure, retention of unused capacity that has strategic value. See our pillar on license type inventory for how to build the position document.

What happens in month six

At month six, the buyer initiates the formal renewal conversation with SAP. The conversation is initiated by the buyer, not by SAP, and it is framed as a strategic review rather than a renewal. The buyer asks SAP for a renewal proposal that addresses the position document. The proposal lands inside thirty to sixty days and becomes the opening document of the negotiation.

Initiating the conversation from the buyer side is not a courtesy. It changes the cadence. SAP's account team prepares the proposal under the buyer's framing, which is the position document. SAP-initiated renewals, by contrast, are prepared under SAP's framing, which is forward growth.

The RISE conversation

Inside the renewal window, SAP will propose RISE as an alternative. The RISE proposal is presented as a discount on the renewal, conditional on a cloud commitment. The proposal is rarely as favourable as it appears on the front page. The buyer-side analysis we publish in RISE conversion negotiation tactics sets out the costs that sit behind the headline discount: the lift-and-shift assumption, the entitlements lost in conversion, the rate-card escalators, the exit provisions.

The RISE conversation, properly handled, becomes a source of leverage rather than a source of pressure. The buyer who can credibly walk away from the RISE proposal is in a stronger renewal position than the buyer who is presumed to be on the path.

What happens in month three

At month three, the buyer has the renewal proposal, the position document, the RISE alternative, and a competitive-alternatives review. The competitive review is not a procurement theatre exercise. It is a documented analysis of what the buyer's S/4HANA estate looks like under an alternative hyperscaler stack, an alternative ERP, or a contracted run-on model on lapsed maintenance. The competitive review does not have to lead to a switch. It has to be credible.

SAP's account team will calibrate the final discount against the credibility of the buyer's alternative. The credibility is a function of documentation, not of public posture. Buyers who say they are evaluating alternatives without documentation are routinely ignored. Buyers who present a costed alternative are routinely discounted.

The last week

The close should be engineered into the last week of SAP's fiscal quarter. SAP's account team will resist this; they would prefer to close earlier so that the bookings credit lands cleanly. The buyer's discipline is to refuse to close before the last week. The refusal is procedural rather than commercial: the buyer's legal review needs to land, the buyer's internal approval cycle needs to run, the buyer's audit committee needs to sign off.

The last-week close consistently produces a final discount tier that earlier closes do not. The mechanism is straightforward: SAP account teams have escalation authority to discount further in the last week that they do not have earlier. The discipline of holding to the last week converts that authority into price.

The three-year versus one-year question

Inside the renewal conversation, SAP will propose a three-year term against a one-year term, with a price differential. The three-year price is typically lower per year, but it removes leverage from the buyer for the next two cycles. The analytical question is whether the buyer's environment is stable enough that the lower price is worth the leverage loss.

For most buyers in active S/4HANA migrations, in active indirect-access disputes, or in active acquisitions, the one-year term is the better economic decision even at the higher annual price. The leverage retained is worth more than the discount foregone. For buyers in stable steady-state, the three-year term is acceptable.

The price uplift clause

Inside any renewal of more than one year, the price uplift clause is the most important commercial term in the contract. The uplift clause sets the rate at which maintenance fees increase each year. SAP's standard uplift in 2026 is in the six to seven per cent band, compounded. Buyers who negotiate the uplift down by two to three points across a five-year term save more than the upfront discount across the term. The uplift conversation is technical and should be led by procurement with counsel and the independent advisor in the room. Our paper on contract clauses to remove or rewrite sets out the uplift language we recommend.

What happens after close

The post-close work is the part most buyers underinvest in. The renewal contract sets the entitlements for the next term. The buyer who does not update the license inventory, the role mapping, and the topology map against the new contract begins the next cycle behind. The post-close discipline is to refresh the readiness documents inside thirty days of the renewal closing and to file the new contract alongside the readiness documents for the next audit cycle.

The bank case file describes a renewal cycle where the post-close discipline preserved the discount through a mid-term variation.

For a renewal cycle inside the next twelve months, the first conversation is about the runway and the position document. Our contract negotiation service describes how we structure that engagement, and the SAP RISE topic page sets out the RISE-specific negotiation work.