SAP Discount and Pricing Benchmarks Guide 2026

Why SAP Pricing Benchmarks Matter More Than You Think

SAP is the world's largest enterprise application software vendor by installed base, and its pricing architecture is deliberately opaque. There is no published price list that corresponds to what enterprises actually pay. The Price List exists only as an internal reference document from which discounts are then negotiated — and the spread between list price and transaction price across the enterprise customer base is enormous, routinely ranging from 20 percent off for uninformed buyers to 70 or 80 percent off for informed, competitive, and well-prepared negotiations.

The consequence is that two enterprises of similar size, running similar SAP deployments, with similar strategic profiles, can be paying radically different amounts for equivalent software. The difference is not the software — it is the quality of the commercial preparation and negotiation. Pricing benchmarks are the instrument of that preparation. They tell you what other enterprises are actually paying, which gives you the confidence to walk away from — or aggressively challenge — SAP proposals that sit at the expensive end of the market range.

On-Premise Licence Pricing Benchmarks

SAP's perpetual on-premise licence model is no longer SAP's preferred commercial direction, but it remains the licensing vehicle for hundreds of thousands of enterprise deployments globally. Understanding what constitutes a good deal in this model is foundational because on-premise licence values also determine the maintenance baseline — which compounds indefinitely at 22 percent per year.

Discount Ranges by Deal Archetype

The achievable discount on a new SAP on-premise licence purchase depends on several variables: deal size, competitive alternatives in play, timing relative to SAP's fiscal year, the customer's strategic value to SAP, and whether the purchase is for a core ERP module or a peripheral application. With those variables understood, the market benchmarks are:

• Mid-market deals (under $1M licence value): 20 to 40 percent off list price. These deals receive less senior attention from SAP account teams and less discretionary pricing authority. Competitive alternatives and fiscal year timing are the primary levers.
• Standard enterprise deals ($1M to $5M licence value): 40 to 55 percent off list price. This range represents the centre of the enterprise market. Well-prepared buyers with independent benchmarks and competitive alternatives should target the upper end of this range.
• Large enterprise deals ($5M to $20M licence value): 50 to 65 percent off list price. At this scale, SAP account teams have meaningful discretionary pricing authority and are motivated to avoid deal loss. Competitive preparation and fiscal year timing can push outcomes to 65 percent or beyond in favourable conditions.
• Strategic and mega-deals (over $20M licence value): 60 to 80 percent off list price. At mega-deal scale, pricing moves into direct negotiation with SAP leadership. Independent benchmarking and experienced advisory support are effectively mandatory to achieve outcomes at the top of this range.

These ranges apply to net new licence purchases. Incremental add-on purchases within an existing enterprise agreement typically receive less favourable pricing — the sense of urgency and competitive threat that drives maximum discounting is absent when the customer is already committed to the SAP platform.

RISE with SAP Pricing Benchmarks

RISE with SAP is SAP's cloud transformation subscription offering, packaging S/4HANA Cloud Private Edition software, cloud infrastructure, technical managed services, and a defined set of SAP Business Technology Platform credits into a per-user, per-month subscription. It is SAP's preferred commercial vehicle for S/4HANA migrations, and it is the product most likely to feature in SAP's commercial proposals to ECC customers approaching the 2027 maintenance deadline.

List Price vs. Market Price

SAP's published S/4HANA Cloud Professional user list price is approximately $120 per user per month ($1,440 per year). This is the number SAP sales materials reference and the starting point for most initial proposals. It is not the number that informed enterprises pay.

Market benchmarks for RISE with SAP, based on negotiated deals across a range of enterprise sizes and commitment levels:

• Small deployments (under 500 users, 3-year commitment): $90 to $110 per user per month. Initial discounts of 10 to 25 percent off list are achievable without significant competitive preparation.
• Mid-size deployments (500 to 2,000 users, 3-year commitment): $75 to $95 per user per month. At this scale, well-prepared buyers should target 25 to 38 percent off list price.
• Large deployments (2,000 to 5,000 users, 3 to 5-year commitment): $60 to $80 per user per month. The 5,000-user, 5-year commitment is where 40 to 50 percent discounts become achievable for prepared buyers.
• Enterprise deployments (over 5,000 users, 5-year commitment): $55 to $75 per user per month. The largest RISE deals, negotiated with competitive alternatives and migration leverage, have achieved discounts approaching 55 percent off list price in favourable conditions.

These benchmarks reflect direct subscription pricing. The total cost of RISE includes infrastructure surcharges for specific cloud regions, BTP credit consumption beyond the included bundle, and premium add-on modules that may not be included in the base subscription. Modelling the total RISE commitment over the contract term — not just the headline per-user rate — is essential to evaluating any RISE proposal.

What RISE Does and Does Not Include

SAP's RISE marketing materials describe an all-inclusive bundle. The commercial reality is more nuanced. RISE includes SAP S/4HANA Cloud Private Edition software licences, cloud infrastructure (typically hosted on a hyperscaler partner), technical managed services covering system administration and patching, and a defined quantity of BTP credits. What RISE does not include: Digital Access licences for third-party integrations, premium Fiori applications sold separately, SuccessFactors modules, Ariba, Concur, or any other cloud application outside the S/4HANA core, additional BTP credits beyond the bundle, and certain AI and analytics capabilities that SAP has progressively moved to separate licensing since 2024.

S/4HANA Cloud Public Edition Benchmarks

S/4HANA Cloud Public Edition (formerly SAP S/4HANA Cloud) is SAP's multi-tenant SaaS ERP offering, running on shared SAP-managed infrastructure with quarterly release cycles and limited customisation capabilities. It is SAP's preferred deployment model for net new S/4HANA customers without complex existing SAP estates.

List pricing for S/4HANA Cloud Public Edition is approximately $100 per user per month for Professional access (full transaction access) and $50 per user per month for Starter access (limited access). Negotiated pricing typically falls 15 to 30 percent below list for most enterprise deals, reflecting SAP's higher margin on public cloud compared to on-premise. The more limited customisation and the absence of a competitive migration path from existing ECC deployments reduces customer leverage in public cloud negotiations.

SAP Support and Maintenance Benchmarks

SAP Enterprise Support is priced at 22 percent of the net licence value per year. This is one of the most expensive support contracts in the enterprise software industry, and it is one of the least frequently negotiated. Most SAP customers accept the 22 percent rate as fixed when it is in fact a negotiable commercial variable — particularly at renewal and during broader licence negotiations.

The True Cost of SAP Support Over Time

The compounding nature of SAP support spend is not widely understood. An enterprise that purchased $10 million of SAP licences at 40 percent off list ($6 million net) will pay $1.32 million per year in Enterprise Support at 22 percent of the $6 million net licence value. Over five years, that is $6.6 million in support alone — more than the original licence investment. The total 5-year cost of ownership reaches $12.6 million before any additional purchases, cloud costs, or services.

SAP applies annual inflationary increases to support fees of between 3 and 5 percent per year in standard contracts. Over a five-year term, a 4 percent annual increase compounds to a 22 percent increase in the annual support bill — without any additional software being licensed.

Support Rate Negotiation

The 22 percent Enterprise Support rate is negotiable under specific conditions: during a major licence expansion, as part of a RISE with SAP migration commitment, during a competitive review where third-party maintenance is explicitly being evaluated, or when the customer has identified significant shelfware and is threatening to reduce the maintenance base. Third-party maintenance providers (Rimini Street, Spinnaker Support) typically price at 50 percent of SAP's support rate for equivalent coverage, and their existence as credible alternatives has produced meaningful SAP support rate reductions in competitive negotiations — typically in the range of 10 to 25 percent off the standard 22 percent rate.

SAP BTP Credit Pricing Benchmarks

SAP Business Technology Platform is the integration and extension layer that sits across RISE with SAP, on-premise S/4HANA, and SAP's cloud applications. BTP licensing is credit-based — enterprises purchase a pool of credits consumed by BTP services at defined rates. The credit pricing model makes BTP costs highly variable and frequently unpredictable.

BTP Credit Benchmarks

SAP's list price for BTP credits is approximately $1.00 per credit. Standard enterprise discounts from independent negotiation fall in the range of 15 to 30 percent off list, producing effective prices of $0.70 to $0.85 per credit for mid-size BTP commitments. Large BTP commitments bundled with RISE or S/4HANA migrations have achieved effective credit prices in the $0.60 to $0.75 range.

The more important variable than the per-credit price is the total committed credit pool. SAP's BTP sizing estimates consistently underestimate production consumption volumes — because SAP models BTP consumption based on standard use cases, while enterprise implementations invariably involve custom extensions, integrations, and services that consume credits faster than SAP's standard models predict. Independent BTP consumption modelling, built bottom-up from actual planned service usage, is the prerequisite for any rational BTP pricing negotiation.

CPEA vs. BTPEA: Which Agreement Structure?

SAP offers two enterprise agreement structures for BTP: the Cloud Platform Enterprise Agreement (CPEA) and the newer BTP Enterprise Agreement (BTPEA). The BTPEA was designed for customers with significant BTP commitments and offers flexibility in credit allocation across BTP services. For organisations with annual BTP spend above $500,000, the BTPEA structure typically produces 5 to 15 percent better effective pricing than CPEA. For smaller BTP commitments, the difference is minimal. The agreement structure should be evaluated as part of the broader BTP commercial discussion rather than accepted as a default.

SuccessFactors PEPM Pricing Benchmarks

SAP SuccessFactors is SAP's cloud HCM suite, priced on a per-employee-per-month (PEPM) basis. The PEPM model means cost scales directly with headcount — a simple structure that is frequently misunderstood in its detail because the headline PEPM rate reflects a suite of modules whose actual scope varies significantly by contract.

PEPM Rate Benchmarks by Module

SAP does not publish official SuccessFactors PEPM rates, but market data from enterprise negotiations produces the following benchmarks:

• Employee Central (Core HR): $6 to $8 per employee per month at list price; $4 to $6 negotiated for standard enterprise deals. Full Suite contracts that include Employee Central as the base module produce blended PEPM rates of $12 to $22 per employee per month for the core HR and talent stack.
• Employee Central Payroll: $8 to $12 per employee per month additional for payroll processing capability. Payroll modules are among the least discounted components of the SuccessFactors suite due to their regulatory complexity and switching costs.
• Performance and Goals, Succession, Learning, Recruiting: Each module adds $2 to $6 per employee per month at list. Suite discounting typically reduces module-by-module adds to $1 to $4 each when purchased as part of a multi-module commitment.
• Full Suite contracts (all major modules): Enterprise-negotiated full-suite PEPM rates in the range of $18 to $28 per employee per month are achievable for large deployments. Smaller organisations (under 5,000 employees) typically see $22 to $35 per employee per month for comparable scope.

SuccessFactors Discount Drivers

SuccessFactors cloud pricing discounts are lower than SAP on-premise discounts, reflecting the subscription economics and SAP's higher margins on cloud revenue. The most effective discount levers for SuccessFactors are: committing to multi-year terms (3 years versus 1 year adds 5 to 15 percent to achievable discounts), bundling SuccessFactors with RISE with SAP in a single commercial discussion, timing the negotiation to align with SAP's fiscal year end (December), and introducing Workday as a competitive alternative — SuccessFactors deals with credible Workday proposals in play consistently achieve 10 to 20 percent better outcomes than comparable deals without competitive presence.

SAP Fiscal Year Timing: The December Lever

SAP's fiscal year ends on December 31 — the same as the calendar year. This alignment means that SAP's entire global sales organisation is managing quarter-end and year-end pressure simultaneously in November and December each year. The commercial implications are significant and consistent.

SAP's Q4, and particularly December, is the period in which sales representatives have the greatest authority and incentive to close deals at rates they would not offer earlier in the year. Revenue recognition pressure, year-end commission structures, and the desire to book deals before the annual reset all combine to make December the most commercially generous window of SAP's year for new deals, expansions, and renewals.

Practically, this means enterprises should plan SAP negotiations to have their commercial proposals and counter-proposals ready to exchange in November, targeting signature in December. Deals that drag into January lose the Q4 commercial urgency entirely — SAP's sales teams reset their quotas and their willingness to offer exceptional terms resets with them.

The Q4 leverage applies most powerfully to: new licence purchases, RISE with SAP commitments, SuccessFactors expansions, BTP credit pool purchases, and Enterprise Support rate negotiations linked to a licence expansion. It applies less powerfully to: audit settlements (which are driven by audit timeline, not calendar), Digital Access negotiations (which are driven by risk management logic), and purely contractual amendments with no revenue element.

SAP Deal Construction: Where the Margin Is

Understanding how SAP constructs deals helps buyers identify where the real negotiating room exists. SAP's account teams are experienced professionals with sophisticated pricing tools and clear commission structures. Their incentives are to maximise revenue per deal while closing at rates that keep the customer committed to SAP's platform roadmap.

SAP's deal structuring typically protects margin through three mechanisms. First, the initial proposal is set at a level that builds in room for concessions — the first SAP proposal is never the best achievable outcome. Second, bundling creates apparent value while obscuring the individual component economics. A RISE bundle that includes BTP credits, specific modules, and managed services presents a complex TCO picture that is difficult to decompose without detailed product knowledge. Third, multi-year commitments lock in per-unit pricing that may look attractive today but prevents customers from capturing market price reductions in future years.

Counter-strategies are consistent across deal types: disaggregate every bundle to understand component economics, model the full multi-year cost before committing to any term length, and benchmark each major line item independently before accepting a bundled price.

Building Your SAP Negotiation Benchmarking Package

A complete SAP benchmarking package for a major negotiation covers five elements:

1. Product-level price benchmarks for every major line item in the SAP proposal, expressed as a range from market floor to market ceiling with your target in the upper third of achievable outcomes.
2. Discount structure analysis identifying the gap between SAP's initial proposal and market comparables, expressed as the dollar value of the negotiation opportunity.
3. Deal timing assessment mapping the negotiation timeline to SAP's fiscal year calendar and identifying the optimal windows for commercial pressure.
4. Competitive alternatives map identifying which components of the SAP proposal have credible alternatives (Workday vs. SuccessFactors, third-party maintenance vs. SAP support, on-premise alternatives to RISE), along with the commercial leverage each alternative creates.
5. Walk-away positions defining the specific terms at which the current SAP proposal is commercially unacceptable and an alternative path is more favourable — the boundaries that discipline the negotiation team's decision-making under commercial pressure.

Enterprises that enter SAP negotiations with all five elements prepared consistently outperform those that approach the negotiation reactively or rely primarily on their internal relationships with SAP account management. The investment in preparation typically returns ten to thirty times its cost in better commercial outcomes.