SAP is among the most complex enterprise vendors to manage — spanning ECC, S/4HANA, RISE, Digital Access, and a vast product portfolio. This guide gives CIOs and vendor management teams the practical playbook to control costs, optimise licensing, negotiate effectively, manage audits, and govern the SAP relationship on your terms.
Audit, plan, and negotiate. Know your position before SAP knows it.
Govern, monitor, and optimise. Don't wait for renewal to fix problems.
Right-size, renegotiate, and improve terms. Your leverage resets here.
SAP offers two fundamental licence models: named user licences assigned to individuals, and package/engine licences based on usage metrics like transactions, employees, or orders. Understanding these models — and the critical differences between ECC and S/4HANA — is the foundation of cost control. You can explore the complete framework in our SAP Knowledge Hub.
In legacy SAP ECC, customers buy perpetual licences for specific user types: Professional User (broad access, high cost), Limited Professional, Employee Self-Service (far cheaper, very limited functionality), and others. Each user requires the correct licence type for their role. Many companies accidentally over-licence users at higher levels than needed — a costly oversight that compounds every year through maintenance fees.
Package/engine licences cover specific SAP functions measured by metrics: employees, sales orders, CPU capacity. SAP audits engine usage. One spike can trigger a compliance bill.
S/4HANA can be licensed two ways: traditional perpetual (like ECC) or subscription-based via cloud offerings. On-premises S/4HANA uses named users and package metrics, but SAP simplified the core ERP bundle into a single package licence covering many modules.
In subscription models (S/4HANA Cloud, RISE with SAP), SAP uses Full User Equivalents (FUE) instead of individual named users — aggregating user types into a weighted unit under one contract. Don't assume a 1:1 swap when moving from ECC to S/4HANA. SAP's conversion programs may credit existing licences, but you rarely get full value. See how this plays out in our guide on SAP FUE licensing calculations.
The single biggest compliance risk for most SAP customers: indirect access — when non-SAP systems or external users use SAP data or functions without direct login. SAP's contracts require a licence for anything triggering SAP system processing. SAP won a £54.5M judgment against Diageo in 2017 and pursued Anheuser-Busch for $600M for unlicensed indirect use.
To address the ambiguity, SAP introduced Digital Access in 2018 — licensing nine document types (Sales Orders, Purchase Orders, etc.) created by external systems. Identify every third-party application, interface, and bot that reads or writes SAP data. Then decide: is named user licensing or the Digital Access document model cheaper for your environment? See SAP Digital Access: The Complete Guide for the full analysis.
Map every user to the correct licence type and every interface to the proper licensing mechanism.
Don't just run measurement tools annually for SAP's audit. Run quarterly for your own insight and early warning.
Organisations are typically over-licensed by 10–20%. Proactively reclaim licences from departures and role changes.
When new integrations are introduced, update licensing compliance immediately. Good governance avoids compliance surprises.
The choice between on-premises, hyperscaler-hosted, and RISE with SAP has profound implications for cost structure, contractual flexibility, and long-term vendor leverage. Each path carries trade-offs that are rarely presented honestly by SAP's sales organisation. Our CIO Playbook: RISE vs Traditional SAP walks through the decision in depth.
| Dimension | On-Premises | Hyperscaler (BYOL) | RISE with SAP |
|---|---|---|---|
| Licence Model | Perpetual + ~22% maintenance | Perpetual (BYOL) + maintenance | Subscription (FUE-based) |
| Cost Model | CapEx heavy, OpEx for support | OpEx cloud + OpEx maintenance | Pure OpEx subscription |
| Customisation | Maximum flexibility | Maximum flexibility | Private cloud: moderate; Public: limited |
| Infrastructure | You manage | Cloud provider manages | SAP manages (via hyperscaler) |
| Exit Flexibility | High — you own licences | High | Low — subscription, no ownership |
RISE bundles S/4HANA software, managed services, and infrastructure into one subscription. SAP becomes both your software vendor and cloud service provider. It includes BTP credits, Business Network starter access, and basis support. Scrutinise the contract: clarify allowed customisations, data residency, the RACI matrix, number of included sandbox/dev systems, and DR environments.
Standard RISE contracts often allow 3–5% yearly subscription increases and limit exit options. The hidden costs frequently catch enterprises off guard. For the full exposure analysis see RISE with SAP Negotiations: Hidden Costs & Securing Flexibility.
Many enterprises run SAP on cloud infrastructure using BYOL. You manage two relationships: SAP for software, cloud provider for infrastructure. SAP maintenance fees remain the same — you also incur hyperscaler costs. Manage these contracts in tandem, coordinating contract terms with SAP project cycles. Monitor total cost — cloud spend can spike if systems aren't right-sized.
One benefit: you negotiate cloud resource discounts directly. Caution: if you later move to RISE, SAP controls the cloud contract and you lose direct negotiation on infrastructure costs. Always compare 5-year TCO of self-managing on hyperscaler versus the RISE bundle before committing.
Before RISE, HEC was SAP's managed private cloud offering. SAP is actively migrating HEC customers to RISE. Apply the same diligence to any such migration — understand cost structure changes and ensure you don't lose favourable legacy terms in the transition. Verify what changes and what doesn't before agreeing to move.
A manufacturer comparing RISE vs self-managed on Azure chose RISE but negotiated an improved SLA of 99.7% with credits for downtime and a clause capping price increases at 2.5% per year. The negotiated protections made the economics predictable. The lesson: RISE is not a take-it-or-leave-it offer — every element is negotiable.
Managing SAP requires continuous oversight. Studies show up to 90% of SAP customers overpay due to over-licensing or unused licences. Strong contract governance and negotiation discipline are your primary levers. For detailed negotiation tactics see SAP Licence Negotiation: How to Maximise Your Outcome.
Complete an internal "Phase 0" assessment before contacting SAP: inventory all licences and usage, identify shelfware, map over-privileged users. Coming to SAP with a precise understanding of your utilisation prevents SAP from dictating the narrative and lets you counter any "gap" claims from a position of strength.
Align stakeholders — IT, procurement, finance, business units — and establish a communication plan. SAP's sales teams are adept at multi-threading and will approach executives directly to create pressure. Book a call with our team to structure your Phase 0 approach.
Be clear and firm about what you want to buy — and what you do not want. SAP's common tactic: bundle additional products or higher quantities than requested. Prevent this by stating required products and volumes in writing. SAP sales commonly uses FUD: competitor warnings, 2027 ECC deadline pressure, audit threats. Stay anchored in your business case and independent research.
If SAP claims "price will increase 10% next year" or "offer valid this quarter only" — verify it. Those claims are almost always negotiable.
Before buying more, scrutinise current usage. If you find shelfware, raise it in negotiation. Request to swap unused licences for something of equal value, or to terminate their maintenance. Example: if you bought 1,000 CRM licences but only use 300, negotiate exchanging the excess 700 for SAP Analytics Cloud rather than continuing to pay support on shelfware.
Negotiate price protections now: a clause allowing you to buy more users or modules at the same discount within two years prevents SAP from quoting exorbitant prices on expansion purchases later.
For certain components — procurement, analytics, CRM, HR — alternatives exist. Evaluating Salesforce, Workday, or others in parallel creates leverage. Use carefully — SAP will stress integration and indirect access costs to discourage. Your counter: understand the true indirect access cost of switching and remind SAP you're prepared to invest elsewhere.
When talks stall, escalate: CIO-to-SAP regional manager or CFO-to-SAP sales VP calls can unlock concessions the sales rep couldn't offer. Executive engagement can yield meaningful improvements even after a "best and final" quote.
Focus beyond the immediate purchase. For cloud/subscription deals, negotiate renewal terms now: cap price increases at renewal. For on-prem, lock in expansion pricing tied to the current discount off list. Negotiate contractual protections: swap rights, termination rights for cloud services if SLAs are consistently missed, language limiting audit frequency, and clauses excluding benign indirect uses from fees.
If it's not in the contract, it's not guaranteed. Free training, migration support, consulting hours — get everything in writing. Memories fade. Reps change roles.
Our SAP advisors benchmark your deal against hundreds of comparable enterprises, identify every clause risk, and sit alongside you during negotiations. Clients typically achieve 15–30% cost reductions versus going in alone.
Talk to a SAP Negotiation Specialist →Most large customers are on SAP Enterprise Support at approximately 22% of licence value annually. Understanding your entitlements, premium options, and escalation paths is critical to extracting value from this significant and often under-utilised spend.
Enterprise Support provides 24x7 support for high-priority issues, SAP Support Portal, Solution Manager, and enhancement package updates. For P1 (Very High) cases: call SAP support directly — don't passively wait for portal response. Use your SAP Customer Success Manager for liaison.
Also leverage proactive services included in the contract: Continuous Quality Checks, EarlyWatch alerts, Maintenance Planner, and Upgrade Checks. Most customers leave these on the table entirely.
MaxAttention is the top tier — SAP provides a dedicated expert team who deeply know your system and assist with architecture, performance tuning, and go-lives. ActiveAttention is scaled-down: a Technical Quality Manager off-site and specific expert services, not a full embedded team.
Both are expensive and multi-year. Insist on carrying over unused service days to next year, lock in resource rates for the duration, and benchmark against what comparable clients pay. Many assume premium engagement pricing is fixed — the included expert days, hourly rates, and scope are all negotiable.
For on-premise, SAP's SLAs cover response time, not fix time. For cloud contracts (RISE, SuccessFactors), there are uptime SLAs — typically 99.5% — and sometimes resolution timeframes. 99.5% allows ~1.8 days downtime per year. For 24x7 global operations, that may be insufficient. Push for 99.7% or 99.9% and meaningful remedies for breaches, not token credits.
Develop an internal SAP escalation procedure. If a P1 is not resolved within a defined window, escalate to Mission Control Centre. The phrase "we need a global escalation" causes SAP to bring product engineering into the conversation.
A manufacturing company on MaxAttention had chronic performance issues during quarter-end closing. After regular support channels failed for months, they invoked the MaxAttention escalation. SAP brought in a performance expert team for a week, identified a database indexing problem, and solved it. The key: persistent escalation and using paid entitlements the client had already purchased but hadn't fully activated.
SAP's account teams are expert negotiators who do this every day. Most IT and procurement teams face this once every three to five years. Level the playing field.
SAP has a highly organised sales structure: Account Executive, Customer Success partner, and product overlay reps for cloud products. Knowing their playbook — including the tactics commonly deployed against enterprise customers — is how you maintain control. The 15 Things CIOs Need to Know About SAP ECC End of Life covers these tactics in full.
SAP uses the 2027 ECC support deadline to create urgency — offering incentives to move to S/4HANA now while warning that waiting means losing out on deals. Counter this directly: use the deadline as leverage back at them. SAP needs your migration business too. "We know you want us to transition before 2027. We want a better price to make that happen." SAP is consistently more flexible before you've committed than after.
SAP reps may surface indirect access or compliance issues outside formal audit: "Let's do a licence review to make sure you're compliant." This conveniently finds a shortfall that creates a buying event at list price. Counter: do your own assessment first with tools like our SAP assessment tools. If a shortfall exists, negotiate it as part of a broader deal rather than a standalone purchase under implicit threat.
SAP will involve senior executives to engage your C-suite. Conversations are friendly and high-level but are ultimately looking for upsell opportunities and strategic commitments before the negotiation team has context. Prep your executives on SAP's likely goals so they respond with your company's needs, not SAP's agenda.
Watch for top-siding — going around the negotiation team to engage a C-level with promises or pressure. Nominate specific points of contact and brief your team not to make off-script commitments.
SAP proposes large bundles — "RISE + Ariba + Analytics all together for 30% off!" The overall discount sounds compelling, but often includes products you don't need. Always decompose a bundle: ask for individual component pricing. Often one component is heavily discounted while others are not. Take only the attractive pieces.
Also watch for "one-time" programs with fine print requiring long-term commitments. Evaluate against independent ROI analysis, not SAP's marketing materials.
Refer back to your IT strategy and budget. Keep a roadmap document to share showing when you plan major changes.
If SAP claims 30% savings, verify with external benchmarks or independent advisors. Build your own TCO models.
Buying a module you were considering anyway can relieve pressure elsewhere. Make trades explicit and deliberate.
Free training, migration support, consulting hours — if it's not in the contract, it doesn't exist. Reps move on.
SAP licence audits (often yearly LAW requests) are a normal part of the relationship. Treat audit readiness as an ongoing discipline, not an ad-hoc fire drill when the request arrives. Indirect access is the single biggest audit exposure for most enterprises. Our SAP Audit Preparation Toolkit provides the complete checklist.
Keep user lists clean — remove access promptly for leavers. Document every third-party system interaction with SAP. Run internal usage reports quarterly, not just when SAP asks. When SAP sends an official audit notice, respond cooperatively but carefully.
If you discover an inadvertent shortfall, you may choose to purchase needed licences before submitting audit data — at a negotiated rate rather than post-audit penalties. Always keep audit communications separate from active sales discussions. Never let the same SAP team manage both.
Map all data flows to and from SAP. Common culprits: middleware interfaces, customer and supplier portals, mobile apps, even Excel macros using ODBC connections. Classify each connection: read-only exports (currently no licence if done properly) versus creating transactions in SAP (requires licensing).
Close gaps on your own terms. Options include: purchasing SAP Platform User licences, opting into the Digital Access model, or re-architecting so external access doesn't hit SAP directly. For guidance on choosing between models see SAP Indirect vs Digital Access: How to Choose.
SAP focuses audits when they suspect a commercial opportunity: no recent licence purchases (suggesting grown usage without licences), mergers or acquisitions, large increase in user counts, approaching contract renewal, or if you've publicly announced a move to a competitor.
If you fall into any of these scenarios, double-check compliance proactively before SAP arrives. During an audit, if they request non-SAP system logs, involve your legal team to verify the request is within the contract's audit clause — not all such requests are contractually justified.
In new contracts, explicitly limit indirect risk: add clauses that cloud product use won't count as indirect use back to your ERP. Ensure new definitions only apply to the new product — preventing retroactive charges.
If audit findings occur, don't accept the first fee quote. Findings are negotiable. Convert audit shortfalls into a purchase with discounts or roll them into a broader contract deal. A managed audit outcome is always cheaper than a forced true-up. See guidance on SAP Indirect Access Mitigation Contract Clauses.
Use our SAP assessment tools to identify indirect access risks, user misclassification, and compliance gaps before SAP does.
Start Free Assessment →An SAP renewal is not just a procurement event — it's a strategic checkpoint and your most significant leverage window. Begin planning 6–12 months out. This is your chance to right-size, fix suboptimal terms, and set up the next cycle on better commercial ground.
Perform an internal licence audit and usage analysis well before the renewal date. Identify licences or subscriptions not fully used. It's far easier to non-renew or reallocate at the renewal point than mid-term. For cloud subscriptions: if you bought 1,000 users and only used 700, plan to renew for 700–800. Bring any needed expansion into a negotiated package for a better rate rather than signing a separate expansion later.
Renewal is your chance to repair contract terms that didn't serve you. Add price protection where it was missing. Harmonise inconsistent discounts. Negotiate swap rights — the ability to exchange unused licences for something of equal value. For cloud subscription renewals, push for renewal price caps and options to reduce quantities. For multi-year deals, ensure annual uplifts are capped at "CPI or 3%, whichever is lower."
Don't buy ad-hoc if you can avoid it. Unplanned purchases hand SAP the pricing power. Anticipate expansions and bundle them into planned negotiations. Negotiate a "commit-and-phase" deal or a pricing framework: "Any additional S/4HANA users added in the next two years will receive the same discount." Time expansion deals with SAP's fiscal calendar when possible — SAP is notably more flexible near Q4 and year-end.
Don't let SAP dictate when quotes arrive and when they must be signed. Manage dates yourself with intent.
IT, procurement, legal, and finance should know the goals and present a unified front. SAP will probe for splits.
State what you plan to renew and what not. Otherwise SAP assumes you'll keep everything plus more.
Remove shelfware. Improve terms. Fix pain points in the new contract. Renew at the right size, not the current one.
Managing SAP's complexity can be augmented with specialised tools and expert advisory. The right combination typically uncovers 15–20% cost savings through optimisation alone — before any negotiation begins.
SAP-focused SAM tools include Snow Optimizer for SAP, VOQUZ SamQ, ServiceNow SAM, and Aspera LicenseControl. These integrate with SAP to analyse user activity, licence assignments, and engine usage and automatically identify mismatches — users with expensive licences who only perform low-level tasks.
Ensure tools handle indirect usage tracking and stay updated with SAP's latest licence rules. SAP's own LAW tool shows raw consumption but does not suggest how to optimise or reduce costs. Use it for measurement; use third-party tools for intelligence. Our SAP assessment tools provide structured self-evaluation without requiring tool integration.
Providers like Rimini Street offer maintenance for SAP ECC at roughly 50% of SAP's fee. Switching cuts cost but you lose official SAP updates. Some organisations use this as leverage: the credible threat or actual move to third-party support pushes SAP to offer discounts or special support extensions. Others run hybrid: SAP support for critical systems, third-party for ancillary. The leverage value alone often exceeds the savings from switching.
Also automate licence management: integrate HR joiner/mover/leaver processes with SAP licence assignment so accounts are removed or adjusted automatically when employees change roles or depart.
Specialised advisory firms provide licence audits, contract negotiation support, and benchmarking against comparable enterprises. An SAP licensing advisor can tell you if a proposed discount is fair and where to push — backed by data from hundreds of comparable deals, not gut feel. They also identify contractual soft spots that typical IT teams miss.
Engaging advisors easily pays for itself in a major negotiation through cost avoidance. Also join SAP user groups — ASUG, DSAG — for community knowledge and peer intelligence that SAP cannot control or filter. Compare how this type of advisory approach differs from how Oracle clients and Microsoft clients use independent advisory to similar effect.
Managing SAP as a strategic vendor is a continuous journey of measurement, optimisation, and negotiation. Treat it as a year-round discipline — not a project when a contract is up — and you'll drive controlled costs, a transparent and fair contract, minimised compliance risk, and a vendor relationship that serves your business goals.
Proactive management at every stage: before signing (plan, audit, and negotiate), during the term (govern, monitor, and optimise), and at renewal (right-size, renegotiate, and improve terms). With SAP being so integral to operations, the effort invested pays back in both dollars saved and operational agility gained.
Share your current SAP landscape and timeline. We'll provide an independent licence assessment, pricing benchmark, and negotiation strategy — typically within 48 hours.
No obligation • Fixed-fee engagements • Results guaranteed
Independent advisory content across 11 vendor ecosystems. No vendor sponsorship. No conflicts.