Contents
Key takeawaysWhen to negotiateThe twelve tacticsBuilding an alternativeCutting scopeInside a RISE proposalIndirect accessContract termsAccount team linesWhat we have seenWhat to do nextFAQSAP customers have more room than they assume: SAP is mid transition, the S/4HANA date is commercially flexible, and each layer of a RISE proposal prices separately. These twelve tactics each rest on a document SAP's deal desk recognizes.
- Sign in SAP's Q4. The deepest discount tier opens in the last week of December, so pull the decision into Q4 even when your anniversary is in April.
- Start early. Preparation opened most of a year ahead is worth more than any single tactic, because it buys usage data, a developed alternative and executive alignment.
- Keep one alternative alive. Document it, give it an owner, and show SAP only part of it.
- Cut scope before discounting. Right size users and modules from authenticated usage, and challenge the FUE mapping.
- Split the RISE proposal. Each of the six layers prices separately against an outside comparison.
- Count indirect access yourself. Bring your own document counts, negotiate the tier and carry forward, and settle the history once.
- Protect the price in the contract. The per FUE price cap, module boundary, audit penalty cap and substitution rights outlast any headline discount.
SAP renewals are decided by timing, scope and contract terms more than by the headline discount. SAP needs its ECC customers to move to S/4HANA and RISE with SAP, and that pressure on its own sales targets is what gives you room.
I worked at SAP before we started Redress. The twelve tactics below come from more than 180 SAP engagements we have run in the last 30 months. Each one is backed by usage data, a priced option or a contract clause you can put in front of the account team.
When in SAP's fiscal year should you negotiate?
Negotiate in SAP's fourth quarter, October to December, and plan to sign in the final week of December. SAP's fiscal year ends on December 31, and the deepest discount tier opens only in those last days, when the deal desk is closing the year.
The table shows the bands we see by quarter and what each would be worth on a hypothetical proposal of $2,500,000 a year.
| SAP quarter | Calendar months | Discount band | On a $2,500,000 proposal | Best used for |
|---|---|---|---|---|
| Q4 | October to December | 10 to 22 percent | $250,000 to $550,000 | Large RISE deals, S/4HANA conversions, the main contract terms |
| Q1 | January to March | 6 to 14 percent | $150,000 to $350,000 | Renewal cleanups and indirect access settlements |
| Q2 | April to June | 4 to 10 percent | $100,000 to $250,000 | Module additions and line item negotiations |
| Q3 | July to September | 2 to 7 percent | $50,000 to $175,000 | Avoid for major deals, since SAP has time to walk away |
The gap between the top of the Q4 band and the bottom of the Q3 band is $500,000 a year on that proposal, before any other tactic runs, which is why we fix the signing quarter before anything else.
What if your SAP anniversary falls in April?
Bring the decision forward to the December before it. Sign in SAP's Q4 and ask for the new terms to start on your April anniversary, so you get year end pricing without paying twice for the same months. Waiting until April puts your signature in SAP's Q2.
Your counterweight to SAP's quarter end is a documented internal decision point, such as a board mandate or a budget close, that makes walking away real. Without one, the account team waits for your go live or support expiry to force the signature.
The full calendar, worked back from the renewal with one quarter held in reserve, is in our SAP contract negotiation playbook.
A timeline for a December signature
| Months before signing | What should be done |
|---|---|
| 12 | Usage extracts started, shelfware list opened, one alternative chosen for serious development |
| 9 | Two years of authenticated usage analyzed, integrations inventoried for digital access, executive sponsor named |
| 6 | Alternative priced and scoped in writing, RISE proposal requested with every layer as a separate line |
| 3 | Your contract terms drafted in your own wording, internal decision date fixed and shared with SAP |
| 1 | Final trades agreed, clauses checked in the order form, signature held for the last week of December |
Optimize the Estate First: The SAP Work That Pays for the Negotiation
What are the twelve SAP negotiation tactics?
The twelve fall into four conversations with SAP, three tactics in each: your alternatives, your scope, your term protections and the trades SAP wants. Run all four together. A discount won in one conversation is easily given back in another, for example through an uncapped renewal price or an inflated user count.
- Alternatives: the RISE alternative. An ECC stay on maintenance through 2027 and beyond, third party support, or a competitor ERP.
- Alternatives: best of breed. Workday for HCM scope, Salesforce for CX, Coupa for procurement.
- Alternatives: the hyperscaler path. The AWS, Azure and Google Cloud SAP partner paths, which SAP knows well.
- Scope: user counts. Shelfware documented, with any over count traded for credit.
- Scope: module mix. Dead modules swapped for needed ones.
- Scope: the FUE conversion. The user mapping and the conversion factor.
- Protection: the uplift cap. A ceiling on increases to the per FUE price.
- Protection: the scope boundary. Included modules defined in writing.
- Protection: the audit penalty cap. Written into the master contract.
- Trade: the S/4HANA commitment. Priced, with flexibility on the date.
- Trade: the reference right. A case study and reference.
- Trade: the multi year term. Given only for price and protections.
One negotiation that used all twelve
For a regional bank with SAP spend of 9.2 million euro, running all twelve tactics in a single Q4 cycle produced a 22 percent cut in the run rate. The uplift was capped at 3 percent for five years, indirect access was settled at Digital Access tiered pricing, and an audit cap went into the contract clauses.
The bank also secured a documented S/4HANA conversion path with two years of flexibility on the commitment date. None of the tactics was unusual. The result came from running all of them on the right calendar, with executives aligned in writing before the first SAP call.
SAP RISE Negotiation Guide
How to price and challenge each of the six layers in a RISE with SAP proposal.
Get the white paper →How do you build an alternative SAP will believe?
Pick one alternative, develop it with real scope and price, and keep it alive into SAP's Q4. A credible named alternative moved the deal desk by 10 to 18 percent on the run rate in our negotiations. You do not have to execute it. SAP has to believe it.
Credible means SAP can see that the work is funded and owned. Account teams often test this in informal conversations with your IT staff, so the people close to the project need to know it is live.
- A named option. An ECC stay on maintenance, a third party support contract, or a named competitor ERP. Mainstream maintenance for SAP Business Suite 7 runs to December 31, 2027, with optional extended maintenance to the end of 2030 at a premium of two percentage points, so an ECC stay has a real runway. Our comparison of extended maintenance and third party support prices both.
- A written scope. Which processes and users move, and when.
- A price. A quote or an internal cost model your finance team has signed off.
- An owner. An executive sponsor whose name SAP knows.
Best of breed and hyperscaler options
A best of breed carve out does not need to replace SAP to change the price. Moving HCM scope to Workday, CX to Salesforce or procurement to Coupa takes volume out of the SAP proposal, and the account team feels that in its own numbers.
The hyperscaler path matters in RISE, where SAP resells the infrastructure. A direct relationship with AWS, Azure or Google Cloud gives you a second price for that layer.
Why we don't put the rival quote on SAP's table
The usual advice is to hand SAP the competitor's proposal to prove the alternative is real. We disagree. Once SAP sees the full number, it prices just under it and sends specialists after the weak points in the rival scope.
Show SAP the vendor's name, the scope document and the sponsor, and keep the price and the gaps private. In our experience the deal desk goes further on an alternative it cannot fully see.
How do you cut the SAP scope before SAP prices it?
Count your own usage before SAP counts it for you. Every discount applies to a volume, so an inflated user count costs you money whatever percentage you win.
Use two years of authenticated usage data, document the shelfware, and trade any over count for credit against modules you do need. Swapping a dead module for a needed one is an easier approval for SAP than a reduction, because the contract value stays intact.
How to check your own position
- USMM and SLAW. SAP's own measurement program and the consolidation tool that combines results across systems. Run them yourself first. Our guide to USMM, LAW and SLAW covers what each reports.
- User last logon dates. Report RSUSR200 in the user information system lists users by logon date, which shows dormant accounts still holding a license.
- Workload statistics. Transaction ST03N shows which transactions users run, which is the evidence you need to move a user to a cheaper user type.
- Digital access estimation. SAP delivers an estimation report for ECC and S/4HANA through SAP Notes. SAP itself says it only estimates, so check its counts against your integration inventory. See our note on digital access measurement tools.
Why the FUE conversion is negotiable
RISE counts users in Full Use Equivalents: one FUE covers 1 advanced user, 5 core users or 30 self service users, and a developer consumes 2 FUE. SAP's default mapping from your named users to these categories is rarely the best one for you, and the conversion factor itself is open to negotiation.
Map users from what they actually do in ST03N, role by role, before you accept SAP's mapping. Our FUE calculation guide shows the method.
What is negotiable inside a RISE with SAP proposal?
Every layer is negotiable. The RISE proposal arrives as one annual number, but it is built from six parts that price separately, and each has its own comparison point outside SAP.
| Layer | What drives it | What to ask for |
|---|---|---|
| Base FUE pricing | Volume and the user mapping | Pricing on your own FUE count, with the conversion factor agreed |
| Infrastructure | SAP's hyperscaler line | Credit for an existing AWS or Azure commitment that can replace it |
| Migration services | Scope of the services package | A tight scope, priced against third party SI quotes |
| Premium support | Support tier | A separate line you can accept, reduce or remove |
| BTP credits | Credit volume and overage rate | A cap on the overage rate, agreed before the credits run out |
| Industry accelerators | Bundled content | Removal of anything you will not use; these are often inflated |
Ask for the layers as separate lines at the six month point, and put each one next to its outside comparison. Our RISE tactics analysis for 2026 works through each layer, and the BTP credits guide covers the overage rate in detail.
How should you handle SAP indirect access in a negotiation?
Treat it as a commercial item to be measured and capped. Under SAP's Digital Access model, indirect use is licensed by documents created in SAP by systems and people outside it, which means it can be counted, priced by tier and settled.
- Document every integration that writes into SAP.
- Classify each one as human triggered or machine triggered.
- Count the documents yourself, from your own data.
- Negotiate the Digital Access tier and the carry forward of unused volume.
- Settle any historic exposure once, with a documented boundary that closes it.
Settlements landed 25 to 50 percent below SAP's opening figure once the document counts came from the customer's own measurement. Say SAP opens at $2,000,000 for historic indirect use. On that range, a measured settlement would land between $1,000,000 and $1,500,000. The full method is in our Digital Access guide.
Close the audit risk before the renewal opens
An audit threat is SAP's strongest counter in a renewal. Prepare your audit defense file before talks start: USMM and SLAW results, the usage analysis and the digital access counts, reviewed and filed. When the account team raises compliance, you answer with data, and the conversation returns to price.
Which contract terms should you ask SAP for?
Ask for the clauses that outlast the price. A strong first term discount means little if SAP can reprice at renewal, widen an audit, or refuse to let you swap a module you no longer use.
- Per FUE price cap. A cap on the per FUE rate that holds for 3 to 5 years, so the unit price survives the first renewal. Compare what others get in our uplift cap benchmark.
- Included module boundary. A written list of what is in scope, so SAP cannot later argue a function needs a separate license.
- Audit penalty cap. A documented ceiling on audit penalties in the master contract.
- Module substitution rights. The right to swap unused modules for needed ones at equal value during the term.
- BTP overage rate. A fixed rate for credit overage, stated in the order form.
- Digital Access carry forward. Unused document volume carried into the next year.
- Conversion date flexibility. If you commit to S/4HANA, a window on the commitment date.
Say you pay $3,000,000 a year and the contract caps increases at 3 percent. Year two can rise to no more than $3,090,000, and after four capped increases the year five ceiling is about $3,376,500. Each extra point of permitted uplift adds roughly $30,000 a year, compounding.
The customer who wins the price but loses the clauses regrets the renewal within two years.
What SAP will want in return
SAP values your S/4HANA conversion commitment, a case study and reference right, and a multi year term. Price each one before you offer it, and never give one away to close a gap in the discount. Our term length benchmark shows how term and price trade.
What will the SAP account team say, and how should you answer?
Expect the same few lines in most SAP renewals, and prepare short replies in advance.
| What you will hear | What to say back |
|---|---|
| "This price is only available until quarter end." | "We can sign this quarter if our terms are in the order form. A price without the uplift cap and module boundary is not something we can take to our board." |
| "ECC support ends in 2027, so you need to decide now." | "Mainstream maintenance ends in 2027, extended maintenance runs to 2030, and we have priced third party support. We will decide on our date." |
| "RISE is a package. We can't price the parts." | "Then we cannot compare it. Please show infrastructure, migration services, premium support, BTP credits and accelerators as separate lines." |
| "The FUE mapping follows your current user types." | "Please show the mapping user type by user type. We are mapping from two years of actual usage and will share our version." |
| "Our estimate of your indirect use is attached." | "We will count the documents ourselves and share the counts. Any settlement covers history once, with a written boundary." |
What have we seen in recent SAP renewals?
Across roughly 60 to 80 SAP renewal negotiations we ran in 2024 and 2025, the price moved most for customers who started early and kept a credible alternative alive into SAP's Q4. Customers who opened preparation 9 to 12 months before the renewal captured 12 to 20 points more discount than those who started inside 90 days.
Time is what buys the inputs that change SAP's number: authenticated usage data, a developed alternative and written executive sign off on the walk away point.
What to do next
- Set the date. Map the renewal to SAP's Q4, whatever your anniversary, and fix the internal decision point that makes your deadline credible.
- Open the file a year ahead. Pull usage data, open the shelfware list, and choose one alternative for serious development.
- Develop the alternative and keep part of it private. Show SAP the vendor, scope and sponsor, and hold back the price.
- Run scope and terms as one package. Rightsized counts, the FUE conversion, the uplift cap and the audit penalty cap go to SAP together.
- File your audit defense before the renewal opens. USMM, SLAW and digital access counts, reviewed and ready.
- Get help if you need it. Our SAP negotiation practice runs all twelve tactics with you, for a fixed fee.
Frequently asked questions
When do SAP discounts peak?
In SAP's fourth quarter, October to December, where the band runs 10 to 22 percent and the deepest tier opens in the final week before the December 31 year end. Q1 suits cleanups and settlements at 6 to 14 percent, Q2 line items at 4 to 10, and Q3 is the quarter to avoid for major deals at 2 to 7.
How much is early preparation worth in an SAP negotiation?
Roughly 12 to 20 points of discount. That was the gap across our 60 to 80 renewals between customers who began 9 to 12 months out and those who began inside 90 days. A late start mostly costs you the alternative, because a credible option takes months to scope, price and get signed off.
Do alternatives really move SAP's price?
Yes. A named alternative kept alive into Q4 moved the deal desk 10 to 18 percent on the run rate. It works when SAP can see documented scope, a price and an executive owner. Whether you ever execute it matters far less than whether SAP believes you could.
What is negotiable inside a RISE proposal?
All six layers: base FUE pricing and the conversion factor, the infrastructure line, which an existing hyperscaler commitment can replace, migration services scoped against SI quotes, premium support, the BTP overage rate, and industry accelerators, which can often be removed entirely.
How should SAP indirect access be handled?
Treat it as a measured commercial line. Inventory integrations, separate human and machine triggered documents, and bring your own counts. Measured this way, settlements landed 25 to 50 percent below SAP's opening figure, with historic exposure closed once and a written boundary so it cannot reopen.
Which contract protections matter most with SAP?
The per FUE price cap of 3 to 5 years, the included module boundary in writing, the audit penalty cap and module substitution rights. Negotiate them alongside the price, because once the number is agreed SAP has little reason to concede terms.
Should you commit to S/4HANA to get a better SAP discount?
Only if the commitment is priced and flexible. SAP values a conversion commitment, so ask for a measurable price or credit in return, and a window on the commitment date. In one negotiation we ran, that window was two years.