The SAP negotiation, won on the calendar and held at the renewal
SAP's quarter ends create real pricing flexibility, and the first term discount means little without the clauses that survive it: deals closed under year end pressure without renewal protection saw their 20 to 40 percent discounts quietly clawed back at the next term. The playbook is timing, scope discipline, and the renewal cap, in that order.
Prepared by Redress Compliance · August 6, 2026 · SAP advisory. Based on 30 to 40 SAP negotiations advised 2024 to 2025.
Executive summary
Timing is the cheapest lever. SAP closes its books on March 31, June 30, September 30, and December 31, and the final month of a quarter, above all December, is when deal desks approve exceptions fastest.
The discipline is making SAP's quarter end, never your own go live or support expiry, the forcing date, with one full quarter held in reserve, because a deal that slips a quarter costs the account team real compensation and that pressure should work for you.
The discount is not the deal. First term discounts of 20 to 40 percent were quietly clawed back at renewal wherever no cap existed, and decomposed bundles revealed 15 to 25 percent of soft scope priced into package numbers nobody itemized.
A 55 percent discount off an inflated bill of materials costs more than 35 percent off a right sized scope, which is why the net price per FUE, per user, or per document, not the discount label, is the benchmark.
The fork decides the clause priorities. A perpetual negotiation is a capital purchase where support base protection and shelfware dominate; a RISE negotiation is a subscription where leverage collapses at renewal unless the cap and the growth price hold are contracted up front.
Run both forks in parallel late into the process: SAP compensates its field on cloud contract value, so a costed, executive backed option to stay perpetual is often the strongest price lever inside a RISE deal.
The 2026 landscape favors the prepared buyer.
Mainstream Business Suite 7 maintenance runs to end 2027 with extended maintenance to 2030 at a 2 point premium, RISE transition options keep ECC workloads viable to 2033, and SAP's July 2026 concessions, split landscapes on different support levels.
Termination of unused licenses in defined situations, and capped back maintenance on returning to support, each weaken the old all or nothing lock in.
Account teams will not volunteer them; put them on the table explicitly.
The discount ranges by deal type, and what moves each
| Deal type | Common range off list | What moves the number |
|---|---|---|
| Net new S/4HANA perpetual | 40 to 60 percent | Deal size, quarter end timing, live competition |
| RISE private edition, 3 year term | 30 to 50 percent | FUE volume, landscape scope, reference value |
| RISE, 5 year term with growth | 45 to 60 percent | Committed growth, executive sponsorship, year end |
| Cloud LoB: SuccessFactors, Ariba, Concur | 30 to 50 percent | Multi product bundling, term length |
| Flat renewal, no growth | 0 to 10 percent | A credible alternative, shelfware removal |
| ECC to RISE conversion | Credit driven | Treatment of existing license value and support spend |
A percentage off list is not a benchmark. List prices for FUE based subscriptions vary by edition and tier, so the discount label is the vendor's number about the vendor's number.
Compare the net price per FUE, per user, or per document against the market, and remember the range table's silent footnote: the renewal cap and the growth price hold matter more than any of these figures after year three.
The negotiation calendar, worked backward from the renewal
Baseline and alternative
Entitlements measured against actual use, the shelfware file opened, and the alternative path chosen for serious development.
Forecast and decompose
The demand forecast built, the requirements pack issued, component level pricing demanded behind every bundle, executives aligned.
Negotiate against their quarter
Terms negotiated against SAP's next quarter close with one full quarter in reserve, the January support anniversary priced into any larger deal.
The SAP negotiation fundamentals brief
The timing calendar, the leverage sources, the discount ranges by deal type, and the clause set that survives the first term.
Get the white paper →The two forks, perpetual and RISE, priced in parallel
The forks reward different clause priorities. Perpetual: named users and packages, perpetual rights held at term end, support uplift CPI based and capped, and the exits, third party support or staying on release, that the licensing guide maps.
RISE: FUE tiers plus infrastructure sizing, nothing held at term end, and a full reprice at list unless the renewal cap and growth price hold say otherwise.
The FUE metric itself negotiates before any discount does: one FUE covers one advanced user, five core users, or thirty self service users, and moving borderline users from advanced to core cuts the count materially, the mapping worked in the FUE optimization guide.
Scope discipline applies identically on both forks: buy what deploys in 12 to 18 months, strip anything without a named deployment date, and lock the future price with a written hold rather than buying early.
And while you scope, size the digital access document exposure yourself, before SAP sizes it for you.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across SAP negotiations, 2024 to 2025
Across roughly 30 to 40 SAP negotiations advised between 2024 and 2025, the deals that aged badly shared the same signature: closed under quarter end pressure with the first term number optimized and the renewal unprotected:
First term discounts recovered by SAP at renewal wherever no cap existed on the uplift.
Components revealed as negotiable or removable once package numbers were decomposed.
The third recurring finding was the quietest: audit and measurement clauses signed unread, then driving true up exposure for the rest of the term.
The measurement terms, USMM and LAW on the perpetual fork, contractual FUE overage on the RISE fork, shape every future conversation with SAP, and they are negotiable exactly once.
The renewal specific tactics, including the July 2026 concessions worked clause by clause, sit in the renewal tactics guide, and the RISE negotiation guide carries the subscription fork in full depth.
Your first five moves
- Build the calendar backward from the renewal, with SAP's quarter end as the forcing date and one full quarter in reserve.
- Right size before negotiating: a discount on shelfware is a false win, and the shelfware file opens twelve months out, not at the table.
- Decompose every bundle to component prices, and treat anything SAP will not break out as negotiable to zero.
- Contract the renewal before optimizing the first term: the uplift cap and the growth price hold outlast every headline discount.
- Run both forks until late, the costed perpetual option inside the RISE deal, and table the July 2026 concessions explicitly. The SAP negotiation practice sits on your side of it.
Frequently asked questions
When is the best time to negotiate with SAP?
The final month of an SAP fiscal quarter, and above all December: SAP runs a calendar fiscal year closing March 31, June 30, September 30, and December 31, and quarter end is when deal desks approve exceptions fastest.
Work backward from your renewal so SAP's close, never your own deadline, is the forcing date.
What discount should we expect from SAP?
It follows the deal type: net new S/4HANA perpetual commonly lands 40 to 60 percent off list, RISE private edition three year terms 30 to 50, five year growth deals 45 to 60, cloud line of business 30 to 50, and flat renewals 0 to 10.
Compare net price per FUE or per user rather than the discount label, because list varies by edition and tier.
Why do SAP discounts disappear at renewal?
Because the first term number and the renewal terms are separate negotiations, and only one usually happens: deals closed in SAP's final quarter without renewal protection saw uplift shocks of 20 to 40 percent at the next term.
The renewal cap and the growth price hold are worth more than any first term discount after year three.
How does a RISE negotiation differ from a perpetual one?
Perpetual is a capital purchase where support base protection, shelfware, and exit paths dominate; RISE is a subscription where you hold nothing at term end and leverage collapses at renewal unless the cap and price hold are contracted up front.
Run both forks in parallel: the costed perpetual option is often the strongest lever inside the RISE deal.
What is an FUE and why does the mapping matter?
The Full Use Equivalent is RISE's pricing metric: one FUE covers one advanced use user, five core use users, or thirty self service users, with a developer consuming two.
The role mapping that converts named users to FUE is itself a negotiation, and moving borderline users from advanced to core cuts the count materially before any discount applies.
What did SAP's July 2026 support concessions change?
Three things, following dialogue with the European Commission: landscapes may split into separate commercial installations on different support levels, unused licenses may be terminated in defined situations.
And returning to support carries back maintenance capped at the lower of six months of fees or 50 percent of the suspended amount.
Each weakens the all or nothing lock in, and account teams will not volunteer them.
