SAP maintenance negotiation in 2026. Cut the base, then negotiate the terms.

SAP rarely cuts its support percentage. In the 35 to 45 negotiations we advised, savings came from removing shelfware from the base and from better terms, and SAP's July 2026 commitments make a third party exit far cheaper to reverse.

Which SAP support path are you actually negotiating?

You are on one of four paths, and the path decides what you can change. SAP sells Standard Support near 18 percent and Enterprise Support at 22 percent of net license value, bundles support inside RISE with SAP, and third party providers sell support outside SAP entirely.

The Standard Support rate depends on when you signed. SAP moved new Standard Support contracts from 18 percent to 19 percent in July 2013, so older agreements often still carry 18. Check the rate printed in your own support schedule before you quote either number to anyone.

Know your path before the first meeting

On a perpetual license you negotiate two numbers: the percentage and the license base it multiplies. Inside RISE there is no maintenance line at all. Support sits in the subscription alongside infrastructure and cloud operations, so the only thing to reopen is the subscription price.

A team that walks into a RISE renewal arguing about support percentages is spending time on a line item its contract does not have. Our RISE negotiation guide covers that path.

Why does the SAP support base move when the rate does not?

The percentage is company policy and the base is arithmetic about your own contract. SAP defends the rate hard because any concession would spread across its whole installed base. The licenses the rate multiplies are specific to you, and they are frequently wrong.

A percentage argument is a debate about SAP's business model. A base argument is a review of your own contract, and that is the one you can win.

Shelfware carries full support until it is removed

SAP charges support on the licensed base, whatever you have deployed. A module you bought for a rollout that never happened is billed at the same percentage as the modules running production, every year, until it leaves the base. Engine licenses sized for growth that never arrived behave the same way.

Removing it has historically been hard. When you terminated part of a license set, SAP could reprice the licenses you kept at a lower discount, which SAP's terms call rediscounting. That clawback is why shelfware removal has usually been a negotiated outcome rather than a notice you simply serve.

What the July 2026 SAP commitments let you terminate

After the European Commission accepted SAP's commitments on on premises maintenance, SAP published new terms effective July 10, 2026. They apply worldwide to on premises products for 10 years and exclude cloud offerings. Our analysis of the EU commitments goes through each clause.

Shelfware outside those four cases still has to be negotiated, but a cheaper return from third party support makes your alternatives more credible in that negotiation.

How do you check what your SAP support base actually pays for?

Start with paper, then measure. The support schedule in your contract lists the licenses and the net value that the percentage multiplies, and that number is often older and larger than anyone in IT remembers. Then compare it with what your systems report.

• Contract schedules and order forms. Reconcile every order since the original agreement to one list of licensed products, metrics and net values.
• SAP for Me. Shows your support contracts, installation numbers and the systems registered against each installation.
• USMM and the License Administration Workbench. The annual system measurement shows user types and engine metrics actually in use, system by system.
• Transaction ST03N. Workload statistics show which transactions and modules people run, which is the evidence that a licensed module sits idle.
• Your incident history. Export 24 months of SAP incidents by priority and count how many were raised as Very High.
• Your monitoring stack. List the tools you already pay for that overlap with what Enterprise Support provides.

The gap between the first item and the next three is your shelfware list. We cover the measurement tools in more detail in our guide to USMM, LAW and SLAW.

What have we seen in recent SAP maintenance negotiations?

Fredrik Filipsson advised on roughly 35 to 45 SAP support and maintenance negotiations in 2024 and 2025. The savings came from the base and from contract structure. The headline rate barely moved in any of them.

• Shelfware removal. Taking unused licenses out before renewal cut the support base by 10 to 25 percent. The work was done before the vendor conversation opened, which is the only reason it was available.
• Third party quotes. A credible quote from a third party provider moved SAP 10 to 20 percent, and the movement arrived as terms: scope, protections, tier flexibility and structure. The percentage stayed where it was.
• Reinstatement. Coming back to SAP after letting support lapse cost 150 to 200 percent of the lapsed support. SAP's account teams had that figure in mind whenever an exit was raised.

That third figure is the one that has changed. Under the July 2026 commitments the reinstatement fee is gone and back maintenance is capped, so an exit is far cheaper to reverse than it was when we ran those negotiations. Our SAP third party support comparison works through the providers and the full case for leaving.

Why we would not spend a third party quote on the rate

The usual advice is to get a third party quote and wave it at SAP until the percentage drops. We disagree. In our negotiations the quote did not buy a lower rate, because SAP will not set a precedent that spreads across its installed base.

It did buy terms: tier flexibility, caps on annual increases and rights to reduce the base. Ask for those, and keep the quote as a real, priced option. Where your own numbers show that leaving is cheaper over the migration horizon, the right course is to leave.

What does an SAP support renewal look like in numbers?

A hypothetical example shows why the base matters more than the rate. Say your company holds $20,000,000 of net license value on Enterprise Support at 22 percent, and a review finds 15 percent of that value is shelfware.

The rate cut SAP almost never grants would save $200,000 a year. Removing the shelfware saves $660,000, and moving the smaller base to Standard Support saves a further $510,000. If your contract still carries the older 18 percent Standard rate, the Standard line falls to $3,060,000.

What it costs to come back from third party support

Say the same company switches to third party support for two years and then returns to SAP. The support it let lapse is $3,740,000 a year, or $7,480,000 over the two years.

• Under the old terms. Reinstatement at 150 percent would cost $11,220,000, and at 200 percent $14,960,000. That equals six to eight years of third party savings, which is why most exits were one way.
• Under the July 2026 terms. There is no reinstatement fee. Back maintenance is the lower of 50 percent of $7,480,000 ($3,740,000) or six months of fees ($1,870,000), so the bill is $1,870,000.
• Against the savings. Two years at roughly half the SAP fee saves about $3,740,000, so the return costs about half of what the exit saved.

Your own contract terms and inflation adjustments will change these figures. Whatever the exact numbers, the cost of returning to SAP can now be calculated before you leave.

Should you stay on SAP Enterprise Support?

Not by default. Most customers sit on Enterprise Support at 22 percent and never use the mission critical response paths they pay for. The SAP ERP pages describe what each on premises offer includes, and the difference is mostly service levels and tooling.

SAP resists a downgrade to Standard Support because the higher rate protects revenue across its customer base, not because your systems need it. Treat the resistance as something to test with evidence.

• Count the mission critical tickets you actually raised. That count is the evidence the tier conversation turns on.
• Check whether you run your own monitoring. Stable systems with their own monitoring are paying for tooling twice.
• Ask for the downgrade in writing. Treat the first refusal as the start of the conversation.

How the 2027 deadline changes the conversation

SAP's maintenance strategy ends mainstream maintenance for SAP Business Suite 7 at the end of 2027. Extended maintenance runs from 2028 to the end of 2030 at a premium of two percentage points on the maintenance base.

A support negotiation held near that date is really a negotiation about the migration behind it. On the hypothetical $17,000,000 base, two extra points cost $340,000 a year. Settle the extended maintenance price, or the credit you get for converting, in the same paper as the renewal. Our 2027 ECC maintenance guide sets out the options.

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

Expect the same few lines in most renewals. Each has a reply that keeps the discussion on your base and your terms.

• "The support percentage is global policy." Agree, and move to the base: here is the list of licenses we want removed, and here is the usage evidence for each.
• "If you terminate those licenses we have to reprice the rest." Ask which clause allows it, then check whether any of the four July 2026 termination cases applies. Where none does, make the removal a condition of any new purchase.
• "Third party support will put your S/4HANA migration at risk." Answer with your own model: the migration date, the return cost under the capped back maintenance rule, and the savings in between.
• "You need Enterprise Support for the migration tooling." Ask SAP to name the tools, then propose Enterprise Support for the project period only, with a written step down to Standard afterward.
• "RISE removes all of this." It removes the maintenance line by folding it into a subscription. Ask for the full RISE price next to your current support cost before discussing it further.

Which contract terms should you ask SAP for?

Spend whatever pressure you have on paper that lasts beyond this renewal. These are the terms we ask for most often, and each protects a specific cost.

1. A cap on the annual support adjustment. SAP raised the cap on its annual inflation adjustment for on premises support to 5 percent in January 2024 and reviews that cap each year. A lower cap written into your contract protects every future year.
2. A tier step down right. The right to move from Enterprise to Standard Support at the next anniversary, on written notice, without repricing.
3. Termination rights beyond the four SAP cases. A named list of licenses you may drop at renewal without rediscounting the rest.
4. Named Commercial Installations. The split between installations written into the contract, so a later third party decision for one of them is already settled.
5. Extended maintenance pricing. The 2028 to 2030 premium, or a conversion credit, fixed now.
6. Initial term language. Confirmation that new purchases do not restart the minimum term, in line with SAP's July 2026 policy.

Our third party support report covers the wider market position, and our uplift cap benchmark shows what other SAP customers have signed.

When should you start preparing for an SAP support renewal?

Start about 12 months before the support anniversary. Most of the saving comes from reducing the base, and that work cannot be done in the final weeks of a renewal. Open the conversation with SAP once the base work has started, before it is finished.

What to do next

1. Confirm your support path. Perpetual on Standard, perpetual on Enterprise, RISE or third party, because each allows different changes.
2. Reconcile the base. Match the support schedule against USMM and workload data, and list every license with no active use.
3. Check the July 2026 termination cases. Failed implementations, end of life products and a workforce reduction of more than 10 percent all qualify.
4. Price the third party option properly. Include the capped back maintenance cost of returning, so the option is real.
5. Test Enterprise Support against your ticket history. Ask for the downgrade in writing if your systems are stable.
6. Spend your pressure on terms. Caps, step down rights and termination rights outlast any one year discount. Our SAP practice reconciles the base before the first meeting, which is where the savings in our engagements came from.

Frequently asked questions