SAP Support and Maintenance Negotiation. A buyer side white paper.

SAP support negotiation is won on the base and the structure, not the headline rate, because the percentage looks fixed while the licenses it sits on and the tier you accept are both very much open.

This white paper is for SAP procurement leaders preparing a support negotiation. Read it with the support cost guide and the third party support comparison.

What support frameworks does SAP offer?

SAP sells four support paths: Standard Support near 18 percent, Enterprise Support at 22 percent of net license value, support bundled inside RISE with SAP, and third party providers outside SAP.

Each path attaches to a different contract. Standard and Enterprise Support sit on your perpetual license base. RISE support is folded into a subscription. Third party support replaces SAP entirely. The SAP ERP pages describe the on premise offers.

The path you sit in decides which levers exist. On a perpetual base you negotiate the percentage and the number it multiplies. Inside RISE the maintenance line disappears into a subscription fee you renegotiate whole.

Know your path before the first meeting. A perpetual customer and a RISE customer walk into different negotiations, and treating a bundled subscription like a maintenance line wastes leverage you do not actually hold.

How do standard and enterprise support compare?

Standard Support delivers core fixes, security notes, and legal updates at the lower rate. Enterprise Support adds service level commitments, Solution Manager tooling, and mission critical response times at 22 percent.

Most estates default to Enterprise Support and never use the mission critical response paths. SAP resists a downgrade to Standard Support, because the higher rate protects recurring revenue across the whole installed base.

Push for the downgrade anyway when the estate is stable. If you never open mission critical tickets and run your own monitoring, Standard Support can cover the same real need at a materially lower rate.

• Standard Support: lower rate, core fixes and updates.
• Enterprise Support: 22 percent, service levels and tooling.
• RISE bundled support: folded into the subscription.

What happens to support inside RISE?

Inside RISE with SAP, support stops being a separate 22 percent line. It is bundled into the subscription alongside infrastructure and cloud operations, so there is no maintenance percentage left to negotiate on its own.

The negotiation moves to the whole subscription. You cannot strip support out, so the levers become the term length, the committed volume, and the annual escalation cap written into the RISE order form.

How is the SAP maintenance base calculated and indexed?

Your support fee is a percentage of net license value, the discounted price you paid, not list. That base then rises every year through an indexation clause buried in the maintenance terms.

Two mechanics decide the number. The base is the sum of all licensed products at their contracted net price. The indexation clause lets SAP raise the fee annually, often tied to a consumer price index.

What does the indexation clause actually do?

SAP standard terms allow an annual support fee increase, historically capped near the local inflation index. Older contracts sometimes carry no cap at all, which lets the fee compound faster than your budget.

The buyer side move is to cap indexation in writing. Negotiate a fixed ceiling, for example the lower of CPI or 3 percent, held for the full agreement term. An uncapped clause is the most overlooked cost in the paper.

Audits feed the base too. An unresolved SAP audit that finds an indirect access or user classification gap can add licenses, and those licenses then carry support at 22 percent for every future year.

Support charged at 22 percent of net value compounds fast. Left uncapped, an indexed fee can overtake the original license spend within roughly seven to ten years, which is why the base and the clause matter more than the rate.

What levers move an SAP support negotiation?

Four levers hold under pressure: removing shelfware, challenging the Enterprise Support uplift, capping indexation, and holding a credible third party quote in reserve. SAP support direction is covered in SAP news.

The rate itself is the weakest lever. SAP protects the 22 percent because it anchors recurring revenue across every customer. Push there and you spend goodwill on the one number least likely to move.

Bundle your ask with something SAP wants. A support concession is easier to win when it rides alongside an S/4HANA commitment or a new cloud order, because SAP will trade maintenance terms to protect a larger deal.

How much does shelfware removal move the number?

Support is charged on licensed quantity, not deployed quantity, so unused licenses carry full maintenance. Removing shelfware before renewal cuts the base the rate multiplies, and the preserved figures below show the range.

The mechanism is a partial termination of the unused licenses, which drops them out of the maintenance base permanently. This is a paperwork move, not a discount, so SAP cannot claw it back through a later true up.

Find the shelfware with a deployment audit. Compare licensed quantities against active users and installed instances, and any gap that has sat unused for a year is a candidate to drop from the base.

How do you terminate shelfware before renewal?

You terminate shelfware through partial termination, dropping named licenses from the agreement so they leave the maintenance base. The catch is that SAP contracts often bundle products into an all or nothing support pool.

What is the all or nothing support rule?

Many SAP agreements say support applies to the entire installed base or none of it. That clause blocks you from cancelling maintenance on one unused product while keeping it on the rest.

The workaround is a negotiated partial termination right, or splitting the estate into separate line items during a larger deal. Do this when SAP wants something from you, such as an S/4HANA move or a cloud commitment.

Time the notice to the contract clock. Most SAP maintenance renews annually with a termination notice period, often three months before the anniversary. Miss the window and the shelfware rolls another full year.

Read the exact renewal and notice language in your agreement. The window, the notice format, and the products in scope vary by contract vintage, and one missed clause can cost a full year of avoidable support.

How does the ECC 2027 deadline change your leverage?

The 2027 deadline cuts both ways. SAP mainstream maintenance for Business Suite 7 and ECC 6.0 runs to the end of 2027, with optional extended maintenance to the end of 2030, per the SAP maintenance strategy.

Extended maintenance adds two percentage points to the maintenance basis for the 2028 to 2030 window. After 2030, ECC moves to customer specific maintenance, which delivers no new fixes or legal updates by default.

Who holds leverage before 2027?

SAP wants you on S/4HANA, committed to maintenance until 2040. That urgency is your lever. A customer weighing the move can trade timing for concessions on support, migration credits, and cloud pricing.

The counter move is to keep the ECC estate stable and price the third party path. A running ECC system on third party support removes SAP deadline pressure and resets the negotiation on your clock, not theirs.

Budget the extended maintenance premium either way. If you stay on ECC into 2028, the extra two percentage points apply to the full maintenance basis, so a 22 percent fee effectively becomes 24 percent for that window.

Is third party support worth the risk?

Third party support is worth it when your estate is stable and you are not chasing new SAP features, because it typically halves the fee. The risk is real, so weigh it against the saving before you switch.

Providers such as Rimini Street and Spinnaker Support cover break and fix, tax, legal, and regulatory updates. They do not deliver SAP code fixes, new versions, or access to the SAP support portal.

What are the real risks of leaving SAP support?

The core risks are loss of new versions, no vendor patches, and reinstatement cost if you return. For a frozen ECC estate heading to end of life, those risks shrink. For an active roadmap, they grow.

Never sign a third party deal without modeling the return path. Reinstatement and back maintenance can erase several years of saving if you need SAP support again for an S/4HANA move.

Do the due diligence before you switch. Confirm the provider covers your exact SAP versions, your tax jurisdictions, and your database, and get the reinstatement math in writing so no surprise cost appears if you return.

How should you structure the support deal?

Structure beats rate chasing. Fix the base, set the tier to what you consume, cap indexation, and write those terms into the paper. SAP agreement terms sit in the SAP agreements center.

A clean structure protects cost across the whole term, not just the first invoice. The renewal rate is a snapshot. The clauses on indexation, termination, and reinstatement decide what you pay for years.

How do reinstatement fees shape the deal?

Leaving and returning to SAP support triggers back maintenance plus a reinstatement fee, together reaching 150 to 200 percent of the lapsed amount. Price that into any third party move before you commit.

Reinstatement is SAP's exit tax, and it exists to make third party support a one way door. Model it against the years of saving, because a short third party stint followed by a forced return can net out negative.

Write the base into an exhibit, not a verbal understanding. List the licensed products, the agreed net values, and the support rate line by line, so a future SAP account team cannot quietly inflate the number again at renewal.

• Fix the base: remove shelfware first.
• Set the tier: match service level to real need.
• Cap the uplift: ceiling annual increases at CPI or a fixed percent.
• Secure the return path: settle reinstatement terms before any exit.

When should the support negotiation start?

Start twelve to eighteen months before the renewal, not when the invoice arrives. Shelfware removal, tier changes, and a third party quote each need months of lead time to become real leverage.

The renewal clock is the constraint. Most SAP maintenance auto renews unless you give notice inside the termination window, often ninety days before the anniversary. Map that date first and work backward.

Guard the internal calendar as tightly as the external one. Legal review, security sign off, and finance approval each add weeks, so a deal that looks done in principle can still slip past the notice window.

Where the common advice on SAP support negotiation is wrong

The standard advice is to push SAP for a lower support percentage and treat that as the whole negotiation. We disagree. Across the support negotiations Fredrik Filipsson advised on in 2024 to 2025, the rate almost never moved, while removing shelfware cut the base by 10 to 25 percent and a credible third party quote moved SAP 10 to 20 percent on terms. The buyer side move is to negotiate the base and the structure, not the rate. Clean the licensed quantity, set the tier to actual need, cap future uplift, and hold third party support in reserve. The percentage is the distraction, not the deal.

You will not negotiate the 22 percent down. You will negotiate the number it multiplies, and that is where the deal is won.

What savings should you benchmark against?

Benchmark against the two moves that hold: shelfware removal off the base and third party support off the rate. Public pricing math frames the range, and the preserved figures above sit inside it.

Shelfware removal cuts whatever share of your base is unused, dollar for dollar. Third party support roughly halves the maintenance fee on a stable estate. Indexation caps protect the compounding on top of both.

Treat any single percentage as a starting point, not a target. The right benchmark is your own cleaned base times the tier you actually consume, then held flat by a capped indexation clause.

Model the compounding, not just year one. A support fee held flat by a capped clause can save more over a five year term than a one time rate cut, because the cut erodes while the cap keeps working.

What to do next

1. Map the support line to actual license use and find shelfware.
2. Remove unused licenses before the renewal window opens.
3. Set the support tier to the service level you consume.
4. Stand up a credible third party support quote as leverage.
5. Model reinstatement and back maintenance fees on any exit.
6. Write a future uplift cap into the renewal paper.
7. Lock the agreed base, tier, and cap before signing.

White Paper · SAP

SAP support and maintenance. The buyer side negotiation

SAP support runs 22 percent of license value a year. Read it free.

Read the white paper

Frequently asked questions

Can you negotiate the SAP support rate down?

The headline support rate rarely moves. The negotiation is won on the base it multiplies and the tier you accept, both of which are open even when the percentage is not.

How does shelfware affect a support negotiation?

Support is charged on licensed quantity, not used quantity. Removing shelfware before renewal cuts the base the rate multiplies, often by 10 to 25 percent.

What is the role of third party support in negotiation?

A credible third party support quote is a leverage point. In our engagements it moved SAP 10 to 20 percent on terms even when the client stayed with SAP support.

How do standard and enterprise support differ?

Standard support delivers core fixes and updates at the base rate. Enterprise support adds service levels and tooling at a higher percentage that many estates do not fully use.

What are reinstatement fees?

Reinstatement fees apply when you leave SAP support and later return. They can reach 150 to 200 percent of the lapsed amount, so they shape the real cost of any third party move.

Is support negotiable inside RISE?

Inside RISE, support is folded into the subscription rather than charged as a separate percentage. The negotiation shifts to the subscription terms rather than a standalone maintenance line.

When should an SAP support negotiation start?

Start before the renewal window opens. Shelfware removal, tier decisions, and a third party quote all need weeks of lead time to become real leverage.

What should the final support deal lock in?

Lock the cleaned base, the tier matched to real need, and a cap on future uplift. Structuring those three protects the cost across the whole agreement term.

How much does third party support save on SAP maintenance?

Third party support typically runs about half the SAP fee, moving an estate from 22 percent of net value toward roughly 11 percent. The saving holds only on a stable estate that needs no new SAP versions or code fixes.

What happens to SAP support after 2027?

SAP mainstream maintenance for Business Suite 7 ends at the close of 2027. Extended maintenance runs to 2030 at two extra percentage points, after which ECC moves to customer specific maintenance with no new fixes.