SAP renewal negotiation tactics. Indirect access, RISE and S/4HANA timing set the price.

SAP prices renewals around three issues: indirect access, the RISE decision and S/4HANA timing. Customers who raise all three early close 12 to 24 percent below SAP's first quotation, while arguing volume alone rarely gets far.

What decides the price in an SAP renewal negotiation?

Three issues decide it: your indirect access exposure, whether you convert to RISE with SAP, and when you commit to S/4HANA. SAP account teams carry internal targets on all three. Raise them yourself and you are negotiating on the measures that drive the account team's bonus, which is where the discount comes from.

Customers who put all three issues on the table early close 12 to 24 percent below SAP's first quotation. Each issue you add also improves the contract protections you can win, as the table shows.

How the three issues rank

1. Indirect access exposure. SAP counts indirect use at renewal. A clean, documented count that you produced turns an audit risk into something you can trade.
2. RISE conversion. SAP's sales team is paid on RISE bookings. A plan to stay on premises costs the account team a booking it was counting on, so it has a reason to improve the offer.
3. S/4HANA migration timing. The end of ECC maintenance frames every SAP conversation. A credible plan that does not depend on SAP earns discount.

Renewals that go badly tend to fail the same way. Customers argue the maintenance line, accept SAP's push toward RISE without modeling the alternative, and let the S/4HANA timeline drift into the quarter SAP prefers.

Our RISE negotiation guide, the SAP knowledge hub and our SAP services page cover each issue in more detail.

What have we seen in recent SAP renewal negotiations?

We ran or benchmarked roughly 40 to 55 SAP renewal engagements in 2024 and 2025. Customers who raised indirect access, RISE and S/4HANA timing together closed in a clearly better band than those who argued volume alone. Three patterns came up again and again.

• First quotations are high. SAP's first renewal quotation ran 14 to 26 percent above the figure the customer eventually signed, once all three issues were on the table.
• SAP's digital access counts run high. In roughly four out of five accounts, the count from SAP's own measurement was 30 to 50 percent higher than an independently scoped count. The typical gap was about 40 percent.
• December signatures go deeper. Renewals signed in SAP's December quarter carried a discount 4 to 8 percentage points deeper than the same deal modeled at mid year.

A wider view of our work points the same way. Across more than 90 SAP engagements in the last 24 months, customers who brought all three issues into the renewal closed at a median reduction of 19 percent against SAP's first quotation. Customers who argued only volume closed near SAP's contracted renewal terms.

How should you handle SAP indirect access at renewal?

Measure it yourself before the renewal opens, then decide on conversion with your own number in hand. Indirect access is SAP's term for people or systems that use SAP data through a non SAP interface, such as a web shop, a CRM system or a bot that creates orders.

In 2018 SAP moved indirect access from a per user concept to a document based model, which it calls digital access. The Digital Access Adoption Program (DAAP) is SAP's offer for converting to that model, and the choice between the two paths comes up at almost every renewal.

User based or document based pricing

• User based (legacy). Every indirect user needs a named license, usually Professional or Limited Professional. Audit risk is high and the counting argument is contentious.
• Document based (digital access and DAAP). You license the volume of documents that external systems create in SAP, measured each year. SAP uses nine document categories: sales, invoice, purchase, service and maintenance, manufacturing, quality management, time management, financial and material documents.

How to measure digital access before SAP does

SAP provides a digital access estimation tool that counts document creation across the nine categories in your production systems. Run it yourself, then go through the output with the owner of each interface.

• Creates or reads. Separate the interfaces that create documents from those that only read data.
• Direct or derived. Only documents an external system creates directly should count, so strip out documents SAP generated itself from a first document.

Check the named user side as well, because some Professional or Limited Professional users may exist only to cover indirect use, and those licenses matter when you negotiate a conversion. USMM and LAW give you the user counts. Our guides to digital access measurement tools and SAP digital access rules cover the document side.

What to settle before you convert to DAAP

1. Measure first. Complete your own count before the renewal opens. The documented count is your audit defense.
2. Convert on your terms. Conversion to document licensing is one way. Agree the document volume baseline, a cap on annual uplift and the audit clause before you sign.
3. Trade the exposure. Once it is measured and capped, the exposure SAP claims becomes something you can exchange for credit or price elsewhere in the deal.
4. Keep DAAP out of the signature pack until you have measured. Customers who sign a conversion inside the renewal without an independent count routinely lock in 30 to 50 percent more document volume than they need.

Check package and engine metrics while you count

Package and engine licenses, often priced on a business metric such as revenue, employees or orders, are where misclassified counts hide. The metric definitions in your contract can be negotiated at renewal, while the counts themselves have to be right. Our guide to SAP engine and package licenses lists the common errors.

Should you convert to RISE with SAP at renewal or stay on premises?

Make that decision separately from the renewal, on its own business case. RISE with SAP is SAP's S/4HANA cloud subscription, bundling infrastructure, the application and basic services into one contract priced on Full Usage Equivalents (FUE). Once signed, it can be reversed only at a heavy commercial penalty.

SAP also offers transformation incentives with RISE, including cloud credits meant to offset dual licensing costs during migration. Count those credits as part of the RISE price when you compare the options. Model the options with our RISE TCO calculator and our comparison of RISE and S/4HANA on premises.

How to keep RISE from taking over the renewal

• Separate the contracts. The renewal is a near term commercial event you control. The RISE conversion is a transformation decision with a different timeline and a different set of approvers.
• Validate the FUE count. FUE totals vary widely depending on how users are classified, so get a second opinion before you sign. Our FUE guide shows how the count is built.
• Negotiate the exit clause. Without a documented exit and data extraction process, RISE only works in one direction.
• Keep a stay option priced. A credible RISE light or stay on premises path, with its own cost, tells you what RISE should cost.

Why we advise against converting to RISE inside the renewal

SAP account teams present conversion at the renewal as the clean, lower risk path and call the maintenance line essentially fixed. We disagree with both claims. In roughly six out of ten SAP renewals we have advised, folding RISE into the renewal gave SAP control of price and timing at once.

The better course is to hold the renewal as the near term commercial event and treat RISE as a separate decision with its own business case, signed when it suits you. The account team will not propose that sequence. In our work it is the single change that most often improves the signed number.

How does the S/4HANA deadline change SAP renewal timing?

It puts a clock on both sides, and you can use yours. Mainstream maintenance for SAP Business Suite 7, which includes ECC, ends at the end of 2027. Extended maintenance runs to the end of 2030 at a premium of two percentage points on the maintenance basis.

SAP wants your S/4HANA migration commitment booked well before those dates. That urgency sits with the account team, and a customer with a documented plan can wait longer than SAP would like.

Timing rules for an SAP renewal

1. Know SAP's calendar. SAP's fiscal year ends December 31. Quarter end discounts typically land at 8 to 16 percent, and year end discounts can exceed 22 percent.
2. Bring the renewal forward by 90 days. Have the main negotiation done 60 to 90 days before the contract anniversary, so the final weeks are for signing and not for opening new issues.
3. Name the S/4HANA alternative. Best of breed migration plans are now a viable option for many customers, and SAP knows it. A documented plan changes the conversation even if you never carry it out.
4. Do not commit to a date early. A migration commitment made years ahead, such as signing up in 2025 for a 2027 migration, removes your timing argument for the next two renewals.

Automatic renewal is the other timing trap. SAP support typically rolls over each year unless you give notice, and across vendors our renewal timing research puts the cost of auto renewal traps at 7 to 15 percent. Our notes on SAP fiscal quarter timing and the 2027 end of ECC maintenance set out the calendar.

SAP wants the S/4HANA commitment booked. You want the right price on what you already run. The 2027 and 2030 dates serve whichever side frames them first.

How do you lower the SAP maintenance line at renewal?

Reduce the licenses it is charged on, then cap how fast it can grow. The maintenance line is the least negotiated number in most SAP renewals, yet every annual increase compounds over the term, which makes a cap on uplift worth more than most one time discounts.

Three routes to a lower maintenance bill

• Volume reductions on unused licenses. Identify shelfware with usage evidence and ask for it to come off the maintenance base.
• Migration credit. Convert unused licenses into credit toward S/4HANA instead of paying support on them.
• Third party support for non strategic systems. Stable systems that will not move to S/4HANA can often go to a third party support provider at a lower annual cost.

SAP's maintenance rules changed in 2026. Under commitments SAP gave the European Commission, which apply worldwide to on premises products from July 10, 2026 for 10 years, you can end or partly end maintenance in defined cases on three months' written notice before the end of the current term.

• Cases that allow termination. Products in customer specific maintenance, failed implementations, a workforce reduction of more than 10 percent over two years (counted back to January 1, 2025) and insolvency. Divested businesses can also take their licenses with them or end support on them.
• Split installations. You can divide commercial installations and choose a different support model, another provider or no support for each one.
• Cheaper return. SAP waives the reinstatement fee and caps back maintenance at the lower of 50 percent of the fees for the time off support or six months of fees.

In the cases they cover, these rules give a request to reduce maintenance a contractual basis it did not have before. Our analysis of the commitments covers the detail.

Worked example: a signing discount against an uplift cap

Say your annual SAP support bill is $4,000,000 and your contract allows increases of up to 5 percent a year. SAP offers a one time 8 percent reduction in year 1. The alternative ask is a cap of 2 percent a year on uplift for five years. These rates are illustrations, not SAP terms.

The 8 percent signing discount is worth $320,000. The cap is worth about $1,290,000 over the same five years, roughly four times as much, and nothing stops you from asking for both.

What will the SAP account team say, and how should you answer?

Expect the account team to steer toward RISE and a migration date, because that is what it is measured on. These are lines we hear often, with replies that keep the discussion on price and term.

• "Converting to RISE now gets you the best terms." Reply: we will evaluate RISE on its own business case and timeline, and today we are pricing the renewal of what we run.
• "Our measurement shows your digital access exposure is this number." Reply: we have our own count, scoped interface by interface, and we reconcile the two before any figure goes into a quote.
• "Maintenance is a standard percentage, so there is nothing to negotiate." Reply: the rate may be standard, but the license base and the uplift are not, so we want unused licenses reviewed and a five year uplift cap.
• "Approval for this price needs an S/4HANA commitment." Reply: we have a documented migration plan that includes a non SAP option, and the migration decision follows its own process.
• "This discount expires at quarter end." Reply: understood, and we are working to our own calendar, which points to a December signature if the terms are right.

Which contract terms should you ask for in an SAP renewal?

Ask first for caps on maintenance and cloud subscription uplift for the full term, then for limits on digital access volume and a way out of RISE. A discount is agreed once, while these terms keep working in every year of the contract.

Which SAP renewal tactics work, and which backfire?

The tactics that work put your facts on the table early and keep your agenda separate from SAP's. Most of them appear in the sections above: measure first, price the stay option, cap the uplift and sign in December. Two more are often missed, and a handful of habits undo the rest.

Two plays buyers underuse

1. Treat maintenance and cloud subscriptions as one budget. SAP price books handle them separately. Negotiate them together so a saving on one is not recovered on the other.
2. Point the alternative at real competitors. Our SAP competitive strategy guide shows how buyers use Oracle, Workday, Salesforce and Microsoft options to win a real discount from SAP.

Mistakes that cost customers money

• Letting SAP set the agenda. The account team's agenda is RISE conversion and an S/4HANA booking. Yours is price and term.
• Treating the renewal in isolation. The renewal, indirect access, RISE and S/4HANA strategy are four linked conversations, and handling them separately gives away your position in each.
• Making twelve asks at once. Pick three priority asks and three trade asks, and no more.
• Signing a DAAP conversion unmeasured. It locks excess document volume into every year of the term, as described in the indirect access section.

When should you start preparing an SAP renewal negotiation?

Give a strategic renewal that includes an S/4HANA decision 12 to 18 months of preparation. A maintenance only renewal still needs at least 6 months, and below 90 days you are negotiating with the contract clock running.

Our guide to S/4HANA migration strategy covers the migration plan that feeds the 12 to 6 month stage.

What to do next

This checklist takes you from where you are today to a documented position on each of the three issues.

1. Run the digital access measurement. Start 90 to 120 days before renewal and document the count.
2. Build the RISE versus stay model. Cover the FUE count, infrastructure cost and exit cost across three scenarios.
3. Name the S/4HANA alternative. Set out an SAP migration plan, a RISE plan and a credible best of breed scenario.
4. Audit package and engine licenses. Misclassified metric counts are common and expensive.
5. Put the negotiation on SAP's December calendar. Align your internal deadline with SAP's year end.
6. Get executive alignment in writing. The CFO, CIO and procurement should hold one position before the first SAP meeting.
7. Run a dry run. Hold an internal mock negotiation with all three issues priced and your concessions ranked.

We run SAP renewal work inside the Vendor Shield subscription, the Renewal Program, our SAP practice and the Software Spend Assessment, with benchmarking to test SAP's quote. Meet the management team, read about us, or contact us to discuss your renewal.

Frequently asked questions