SAP licensing negotiation in 2026. Win it on the calendar, keep it at renewal.

SAP's quarter ends create real pricing flexibility, but a first term discount lasts only as long as the renewal terms behind it. Plan the timing, size the scope, then contract the renewal cap before you optimize the headline number.

An SAP negotiation is decided by the calendar, the scope and the renewal terms. Many buyers put all their effort into the first term discount and sign renewal language they have barely read, and that language decides what they pay from year four onward.

I worked at SAP, Oracle and IBM before we started Redress. This page covers when SAP's deal desk has room to move, what each deal type earns, how perpetual and RISE deals differ, and the terms that keep a good price after the first term.

When does SAP give its best price?

In the final month of an SAP fiscal quarter, and December above all. SAP closes its books on March 31, June 30, September 30 and December 31, and its deal desk approves exceptions fastest in the closing weeks, most of all before the December 31 fiscal year end.

The window only helps if you reach it with a finished requirement and a credible alternative. We work from a 12 month runway, counted back from your renewal or support expiry.

Why should SAP's quarter end set the deadline, and not your go live?

If your go live or support expiry forces the signature, the account team knows you have to sign and waits you out. Make SAP's quarter end the forcing date and hold one full quarter in reserve. A deal that slips a quarter costs the account team real compensation, as our guide to SAP fiscal quarter timing explains.

Why does the January support adjustment matter?

SAP adjusts fees on existing Standard Support and Enterprise Support agreements each January 1, and for 2026 the increase follows local CPI, capped at 5.0 percent. A larger deal signed in the fourth quarter should state how the support base is treated, or the January invoice takes back part of the December discount.

What discount should you expect by SAP deal type?

It follows the deal type. Net new perpetual deals discount the most and flat renewals the least, and what shifts the number differs by type.

After year three, the cap on renewal uplift and the hold on growth pricing matter more than any figure in this table.

Why is a percentage off list a poor benchmark?

List prices for FUE based subscriptions vary by edition and tier, so a discount is SAP's number measured against another SAP number. Compare the net price per FUE, per user or per document, using benchmarks such as our FUE price bands.

A 55 percent discount off an inflated bill of materials can cost more than 35 percent off a scope sized to what you will deploy. Say SAP proposes a perpetual bundle at $6,000,000 list, and your sizing shows only $4,000,000 of it deploys within 18 months.

• SAP's proposal. 55 percent off $6,000,000 is $2,700,000 net.
• Your sized scope. 35 percent off $4,000,000 is $2,600,000 net, $100,000 less.
• Every year after. Support is charged on net license value, so the bigger deal also pays more support on items still unused.

Pair the smaller deal with a written hold on the price of the deferred items.

How do perpetual and RISE negotiations differ?

A perpetual deal is a capital purchase, so the support base, shelfware and exit paths matter most. RISE is a subscription: you hold nothing at term end, and your position at renewal is weak unless the renewal cap and growth price hold were signed at the start.

Our SAP licensing guide maps the perpetual exits and what each does to your rights.

Why price both options until late?

SAP pays its field teams on cloud contract value, as our note on what SAP sales is paid on shows. A costed, executive backed option to stay perpetual is often the strongest price pressure inside a RISE deal, so keep it funded until close to signature.

How does the FUE count change the price before any discount?

One FUE covers one advanced use user, five core use users or thirty self service users, and a developer consumes two. The role mapping is agreed with SAP, and it sets the volume every discount applies to.

Say 1,000 users map as 200 advanced, 500 core and 300 self service: 200 plus 100 plus 10 is 310 FUE. Move 60 borderline users to core and it becomes 140 plus 112 plus 10, or 262 FUE. That is 48 fewer before any discount. Our FUE optimization guide covers the role by role method.

What scope should you buy on either path?

Buy what deploys in 12 to 18 months, strip anything without a named deployment date, and lock the future price with a written hold instead of buying early. Size your own digital access document exposure too, before SAP sizes it for you.

Which contract terms protect your SAP price at renewal?

The renewal uplift cap and the growth price hold protect you most. Get each of these in the order form or agreement, since a sales email carries no weight at renewal.

• Renewal uplift cap. A ceiling on the increase at first renewal, stated against the final year of the current term.
• Growth price hold. The net unit price held for added volume through the term, so you buy when you deploy.
• Component price schedule. Every bundled item priced separately, which exposes soft scope and allows removal later.
• Support base terms. How the perpetual support base is calculated, a capped CPI uplift, and what happens when licenses are terminated.
• Measurement terms. Scope and notice for USMM and LAW runs, or how RISE overage is measured and priced.
• Conversion credit. For ECC to RISE, the written treatment of existing license value and support spend.

Why the biggest year end discount is the wrong target

The usual advice is to hold out for SAP's year end and push for the largest first term discount. We disagree. December is when the deal desk has the most authority, and a headline percentage is the cheapest thing it can give, because SAP can recover it at the first renewal if no cap is signed.

Spend the year end pressure on the renewal cap, the growth price hold and the component price schedule first. Accept a slightly lower headline if that is the trade, since the deal desk approves exceptions most readily in the closing weeks of a quarter.

What changed in SAP maintenance and support for 2026?

Business Suite 7 mainstream maintenance runs to the end of 2027, extended maintenance to 2030 at a premium of two percentage points, and RISE transition options keep ECC workloads viable to 2033. In July 2026, following dialogue with the European Commission, SAP added three concessions.

• Separate installations. On premises systems may be split into separate commercial installations on different support levels, or none.
• Termination of unused licenses. Allowed in defined situations, which SAP lists as including severe workforce reductions, divestiture, bankruptcy and implementation failure.
• Capped back maintenance. Returning to support costs at most the lower of six months of fees or 50 percent of the fees for the time off.

Each weakens the old all or nothing lock in. Account teams will not volunteer them, so table them and ask SAP to confirm in writing how each applies to you. Our analysis of the EU commitments has the detail.

What have we seen in recent SAP negotiations?

Across roughly 30 to 40 SAP negotiations we advised in 2024 and 2025, the deals that aged badly closed under quarter end pressure with the first term number optimized and the renewal unprotected. Three findings recurred.

1. The clawback. First term discounts of 20 to 40 percent were recovered at renewal wherever no cap on the uplift existed.
2. Soft scope. Broken down to component prices, bundles held 15 to 25 percent of scope that was negotiable or removable and had never been itemized.
3. Measurement clauses signed unread. These went on to drive true up exposure for the rest of the term.

The measurement terms shape every later conversation with SAP, and you negotiate them exactly once.

Our renewal tactics guide works the July 2026 concessions clause by clause, and the RISE negotiation guide covers the subscription side in depth.

How do you check your own position first?

Run SAP's own measurements early. Transaction USMM measures users and engines per system, and the License Administration Workbench (LAW, now SLAW) consolidates them. Report RSUSR200 lists users by last logon date, which is where the shelfware file starts. See our USMM and SLAW guide.

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

Most lines aim to fix the signature date or keep the bundle intact. These come up most often.

What to do next

1. Build the calendar. Work back from renewal, with SAP's quarter end as the forcing date and a quarter in reserve.
2. Size before you negotiate. Open the shelfware file twelve months out; a discount on shelfware is a false saving.
3. Break down every bundle. Treat anything SAP will not price separately as negotiable to zero.
4. Contract the renewal first. Secure the uplift cap and growth price hold before the first term number.
5. Keep both options alive. Carry the costed perpetual option into the RISE talks and raise the July 2026 concessions.
6. Bring in help. Our SAP negotiation practice works for you at a fixed fee, with no ties to SAP.

Frequently asked questions