The SAP Licensing Problem Most Enterprises Do Not Realise They Have
SAP licensing is deliberately complex. The named user classification system — Professional, Limited Professional, Employee, Developer, and the growing range of S/4HANA equivalents — is designed to maximise SAP’s revenue, not to reflect how your organisation actually operates. Most enterprises are significantly over-licensed because user types were assigned during implementation, never reviewed, and have silently accumulated cost for years while real-world usage patterns shifted.
Digital access and indirect usage add a second, largely invisible layer of exposure. Every time a third-party system writes a document to SAP — a warehouse management platform creating inventory records, an HR system triggering payroll postings, an ecommerce engine generating sales orders — SAP’s Digital Access model creates a potential licensing obligation. Most large enterprises have dozens of such integrations. Almost none have properly quantified the exposure before SAP does it for them.
HANA runtime, engine licensing, and S/4HANA migration planning add a third dimension. If you are running SAP ECC and have been told that S/4HANA migration is the only forward path, the contract structure SAP proposes for that migration will define your licensing cost for the next decade. The terms SAP starts with are never the terms an informed buyer accepts.
SAP’s own measurement tool — LAW — is designed to produce SAP’s compliance picture, not yours. It does not identify reclassification opportunities. It does not model indirect access defensibility. It does not benchmark your pricing against what comparable enterprises actually pay. Independent license management does all of these things, on your side of the table.
Why Going It Alone Creates Compounding Risk
Most organisations manage SAP licensing internally or delegate it to their SAP implementation partner. Both approaches carry structural limitations. Internal teams lack the external benchmarking data to know whether their classification ratios are market-standard. Implementation partners have ongoing commercial relationships with SAP that constrain how aggressively they will challenge SAP’s position — and limit what they tell you about the cost consequences of proposed contract structures.
The information asymmetry is significant. SAP’s account teams know exactly what comparable enterprises in your sector pay, which discount thresholds trigger approval at different levels, and how to frame a digital access finding in a way that creates commercial pressure toward settlement. Enterprise buyers do not have equivalent information unless they work with an advisor who has negotiated from both sides of that table.
What SAP License Management Delivers in Hard Numbers
Redress delivers four measurable, auditable outcomes from independent SAP license management. These are not vague advisory outputs — they are specific findings that directly reduce your SAP cost base.
Three Client Outcomes — Anonymised, Results Verified
The following outcomes are drawn from completed Redress Compliance engagements. Client names are confidential under NDA. Sector and scale details are accurate.
Global Manufacturing Group ($4.2M annual saving). A FTSE 100 manufacturer had not reviewed its SAP user classifications since a 2019 S/4HANA implementation. Redress identified 900 inactive users still consuming named user licences and a further 340 Professional users whose transaction profiles met Limited Professional criteria. Combined with engine right-sizing across four SAP landscapes, the documented annual saving reached $4.2M — achieved before contract renewal discussions had begun.
Healthcare System ($6.4M cumulative saving). A North American healthcare system engaged Redress across three consecutive SAP renewal cycles. The programme combined ongoing user reclassification, digital access monitoring across 14 third-party integrations, and renewal benchmarking. Cumulative documented savings over three years reached $6.4M, with the licence position improving at each renewal cycle.
Pan-European Retailer (audit avoided, $1.8M exposure eliminated). A retailer faced an SAP digital access finding linked to its ecommerce platform. Redress intervened before the measurement was formalised, reclassified document types correctly, and established a contractual position that eliminated the exposure. The potential claim SAP had signalled — valued at approximately $1.8M — did not materialise.
How the Engagement Works: Four Steps to a Defensible Position
Redress SAP license management engagements follow a proven four-stage methodology. Standard engagements complete in four to six weeks. Urgent pre-measurement assessments can complete in two to three weeks when SAP has already initiated a compliance review.
Why Redress — and Not Your SAP Partner
There are four structural reasons why Redress Compliance delivers outcomes that SAP implementation partners, SAM tool vendors, and generalist ITAM consultants cannot replicate.
What You Need to Get Started
Redress can begin a SAP license management engagement with the following information — most of which your IT procurement or SAP Basis team already holds. If you cannot locate all of it, that is not a barrier to starting.
- SAP order forms and current contract documentation (most recent version)
- Named user licence type lists — your user count broken down by classification type
- SAP LAW measurement data if a recent measurement has been run by SAP
- Engine allocation records for any HANA, BW/4HANA, or other engine licences
- A list of third-party systems that connect to, read from, or write to your SAP environment
Discovery is the first stage precisely because many enterprises cannot initially reconcile their own SAP documentation. We structure engagements to begin with partial information and assemble the complete picture as part of the process.
Who Gets the Most Value from Independent SAP License Management
Independent SAP license management delivers the highest returns for enterprises who meet any of the following criteria. If more than one applies, the financial case for independent management is overwhelming.
- Approaching an SAP renewal in the next 12 months — without independent benchmarking, you are negotiating from SAP’s commercial frame, not yours.
- Planning or evaluating S/4HANA or RISE with SAP migration — the contract SAP proposes for your migration defines your costs for the next decade. Get an independent view before committing.
- Have not reviewed user classifications since go-live — user type drift is nearly universal. The longer since last review, the greater the over-licensing.
- Running third-party integrations with SAP — every system that reads from or writes to SAP creates a potential digital access obligation SAP can and will measure.
- Have received or anticipate receiving a SAP measurement letter — the window before SAP formalises its findings is the highest-value intervention point.
- SAP spend exceeds $2M annually — at this scale, the advisory fee typically delivers 10–20x return in identified savings alone.
Download Our Independent SAP License Management Guide
Benchmarks, reclassification methodology, digital access framework, and the 12-point renewal checklist — for CIOs and procurement directors managing complex SAP estates.The S/4HANA Migration Trap — And How to Avoid It
SAP ECC mainstream maintenance for EHP 0–5 ended in December 2025. This is not a future deadline — it has already passed. Enterprises still running these versions face escalating maintenance cost, security risk, and increasing pressure from SAP account teams to commit to a migration path before the commercial terms deteriorate further.
The path SAP proposes is almost always RISE with SAP — SAP’s cloud subscription bundle. RISE pricing is complex, non-transparent, and structured to make direct comparison with your current cost extremely difficult without independent modelling. SAP bundles infrastructure, licences, support, and cloud services into a single commercial construct where individual components carry no standalone price.
Migration credits — the commercial incentives SAP offers to move existing ECC customers to S/4HANA — decrease 10% per year. A migration completed in 2025 secured meaningfully better credit terms than one completed in 2027. This is a real and compounding cost of delay. But the right response is not to accept SAP’s first RISE proposal out of urgency. It is to model your options independently and negotiate from your own analysis with full knowledge of what comparable buyers have actually achieved.
Our SAP RISE advisory service covers full migration evaluation, independent commercial modelling, and negotiation support — operating entirely outside of SAP’s migration incentive programme, which is designed to get you into RISE quickly, not to get you the best possible terms.
SAP Digital Access: The Exposure You Cannot See Until SAP Measures It
SAP’s Digital Access model replaced the old indirect access framework with document-based pricing. Instead of charging based on users of third-party systems connected to SAP, SAP now charges based on the number of SAP documents created via digital access — purchase orders, sales orders, production orders, goods receipts, financial postings, and other document types depending on your landscape.
The exposure this creates is substantial and almost entirely invisible until SAP runs a measurement. An enterprise with a Salesforce CRM creating SAP sales orders, a warehouse management system writing goods receipts, and an HR platform generating payroll postings may have tens of millions of digital access documents created annually — each potentially subject to SAP’s pricing metric under the terms of the Digital Access Adoption Programme (DAAP).
SAP’s DAAP rates are not market rates. Independent benchmarking against comparable transactions shows consistent over-pricing of 20–40% versus what enterprises actually negotiate when they approach DAAP with independent commercial intelligence. Our SAP Digital Access advisory service handles full exposure quantification and DAAP commercial negotiation based on market comparables — not SAP’s opening position.