SAP Licensing FAQ — Straight Answers to the Questions SAP Doesn't Want You to Ask

SAP audits are rarely random. The most common triggers are: your contract renewal date approaching (SAP uses the audit to establish a higher baseline for the renewal negotiation), significant growth in your user count, SAP detecting third-party systems connecting to your SAP environment, a major system change such as an S/4HANA migration, and internal SAP commercial targets. The 52% of SAP customers who have been audited more than twice in 18 months are typically those with complex system landscapes or pending renewal events.

It's worth noting: SAP's measurement team is commercially incentivised. The audit process is directly connected to SAP's licence sales pipeline. Every finding becomes a conversation about buying more software. Understanding this is the first step in effective SAP audit defence.

USMM (User System Measurement and Management) is SAP's system measurement tool. It scans your SAP systems and generates a count of active users by licence type. SAP's audit team asks you to run USMM and submit the output — this becomes the basis for their Effective License Position (ELP) calculation.

The problem is that USMM frequently overcounts. It doesn't account for shared logins, test accounts, inactive users who haven't been locked, or users whose access profiles don't align with their purchased licence type. An unchallenged USMM submission can result in a back-licence claim of millions of pounds for users you don't actually need to licence at full Professional rates. Our SAP audit defence service begins with a forensic review of USMM output before any submission is made to SAP.

The ELP is SAP's calculation of your current licence position — the gap between what you're licensed for and what SAP claims you're using. It is the document SAP will present as the basis for any back-licence claim or additional purchase requirement. The critical point: SAP's initial ELP is almost always challengeable. The average SAP audit claim is 3–5 times what the customer actually owes, based on industry benchmarks.

Challenges typically focus on: user reclassification (downgrading Professional users to Limited Professional or Employee where access profiles support it), exclusion of inactive or locked users, challenge of indirect access inclusions, and methodology disputes around SAP's use of USMM versus LAW (License Audit Workbench) data. Read our complete SAP audit guide for a full walkthrough of the challenge process.

Technically, your audit obligations are defined by your Master Agreement and the SAP Customer Engagement Initiative (SAP CEI) terms. Most SAP contracts include a right-to-audit clause, but the scope and frequency are often negotiable. In practice, refusing an audit entirely tends to escalate the situation and gives SAP grounds to hold licence renewals or support. However, you do not have to accept SAP's measurement methodology without challenge, and you are not obligated to submit unreviewed USMM data. The strategic approach is to participate in the audit process while contesting the methodology and output at each stage — not to refuse, but to push back precisely and on evidence. This is exactly what our audit defence team does.

An unchallenged SAP audit from initial letter to final settlement takes 3–6 months. A contested audit — where you're challenging the ELP, reclassifying users, and negotiating the back-licence claim — typically takes 6–12 months. SAP's audit team will apply pressure at key milestones, particularly around your renewal date, to force a faster settlement. Engaging independent advisors early in the process is the best way to extend the timeline strategically while building a stronger evidence-based challenge.

Professional users have unrestricted access to all SAP functionality and are the most expensive licence type — typically priced at 3–5x the cost of Limited Professional users. Limited Professional users are restricted to specific tasks: they can approve purchase orders, process expense reports, run standard reports, or perform defined self-service activities, but cannot access the full breadth of SAP transactions.

The key licensing question is whether a user's actual business activities require Professional-level access, or whether their day-to-day work could be performed under Limited Professional permissions. Many organisations find that 20–40% of their Professional users perform activities entirely consistent with a Limited Professional licence — which SAP will never proactively flag. Reviewing and reclassifying users is one of the fastest ways to reduce SAP licensing costs.

Employee users are the lowest tier of SAP named user licence. They are restricted to self-service HR and payroll transactions — viewing payslips, submitting leave requests, updating personal data. ESS (Employee Self-Service) is a related concept, typically accessed via SAP's portal, allowing employees who aren't regular SAP users to perform these actions. FUE (Full Use Equivalent) is a metric SAP uses to aggregate different user types into a standardised measure for contract purposes.

Misclassification of Employee users as Professional users is extremely common — particularly in organisations that applied a standard Professional licence to all HR system users without reviewing actual access requirements. Each misclassified user is a direct cost-saving opportunity in a licence optimisation exercise.

Yes, and proactive reclassification before SAP initiates a measurement is significantly better than addressing it under audit conditions. The process involves reviewing each user's role assignments and transaction access profiles in SAP, mapping their actual activities to SAP's licence type definitions, removing access that exceeds their required licence level, and updating your internal tracking accordingly. A well-documented reclassification performed ahead of your next renewal or system measurement gives you a defensible position. Our SAP license compliance service handles this systematically for enterprise estates.

Developer licences are required for users who develop ABAP code, create or modify SAP objects, or perform system development activities. They're a common source of audit findings because organisations frequently grant developer access to users who need occasional system administration access — Basis administrators, for example — without recognising that this access profile maps to a Developer licence rather than a lower-cost type. Developer licences are also frequently left active after projects complete. A systematic review of user access profiles against Developer licence triggers is part of any thorough pre-audit preparation.

SAP indirect access — now more commonly referred to in the context of SAP's Digital Access model — occurs when users access SAP data or functionality through a third-party system rather than directly through the SAP GUI or SAP's own interfaces. Examples include: a Salesforce user who views inventory data pulled from SAP, a custom customer portal that creates sales orders in SAP, a warehouse management system that updates SAP material movement records, or an RPA (robotic process automation) bot that logs transactions in SAP.

SAP indirect access claims have generated over $1 billion in additional licence revenue since 2017. The most significant case was the $588 million award against Diageo in 2017, which established that indirect access via third-party systems is a material licence obligation. SAP subsequently introduced the Digital Access model in 2018, converting indirect access obligations from a named user basis to a per-document basis. Our indirect access advisory service maps your exact exposure before SAP does.

Under SAP's Digital Access model, indirect access is measured in documents rather than users. The four primary document types are: Orders (sales orders, purchase orders), Deliveries (outbound and inbound), Invoices (billing documents and invoice receipts), and Materials (goods movements, inventory postings). Each third-party-generated instance of these documents creates a Digital Access licence obligation at a per-document price.

The per-document cost sounds small, but at enterprise scale — thousands of orders per day flowing through an integrated system landscape — the total obligation can be substantial. Many RISE with SAP contracts now include Digital Access entitlements bundled into the deal, but the volume of documents included is often insufficient for the customer's actual integration footprint. Independent analysis before committing to a volume is critical.

A thorough indirect access assessment maps every system in your technology estate that has a connection to SAP — whether through an API, SAP's RFC (Remote Function Call) interface, BAPIs, web services, or file-based integration. For each connection, the analysis documents: the data flowing in and out of SAP, whether any SAP transactions are triggered, the volume of SAP document types created, and whether the access is within your current licence entitlement. This is technical and time-consuming work, but the alternative — having SAP's audit team map it for you — is significantly more expensive. Book a consultation to discuss your integration landscape.

RISE with SAP is SAP's bundled subscription offering combining S/4HANA Cloud Private Edition (the software), SAP Business Technology Platform (BTP) credits, SAP infrastructure hosting (typically on Hyperscalers — AWS, Azure, GCP), and SAP Enterprise Support. It is presented as a simplification — one contract, one vendor, one price. The reality is more complex: the bundled components are priced opaquely, the BTP credits included are typically insufficient for meaningful integration development, and the infrastructure element includes a margin that you could eliminate by negotiating a direct cloud hosting agreement.

Our RISE with SAP advisory service has reviewed over 50 RISE proposals. In nearly every case, the initial SAP proposal contains 25–35% excess cost that is negotiable — but only if you know where to look.

The most common hidden or underemphasised costs in RISE proposals include: escalation clauses in the Master Agreement that increase the annual fee by 3–5% regardless of your usage growth; BTP credit volumes that sound generous but don't cover basic integration scenarios (integrating a CRM to S/4HANA alone can consume a significant portion of the included BTP credits); infrastructure service levels that don't match enterprise requirements, requiring additional charges; the cost of migrating from ECC to S/4HANA, which is explicitly excluded from RISE; and the fact that RISE locks you into SAP infrastructure, eliminating your ability to optimise costs on the hyperscaler market independently. Read our full RISE with SAP guide for a complete breakdown.

Yes — significantly. SAP positions RISE as a standardised offering with limited flexibility, but this is a negotiating position, not a commercial reality. We have negotiated reductions in: the per-user pricing within the RISE bundle, the volume of BTP credits included (increasing them without additional cost), the length of price lock before escalators apply, the exit terms and IP ownership provisions, and the infrastructure specification relative to actual workload requirements. The key to successful RISE negotiation is entering the conversation with an independent analysis of what the components are worth separately, and what comparable enterprises have achieved in their RISE contracts.

S/4HANA Cloud Private Edition (PE) is SAP's term for a single-tenant cloud deployment — your own dedicated instance, hosted on SAP's managed infrastructure. It offers significantly more customisation capability than Public Edition and is the variant included in RISE with SAP. S/4HANA Cloud Public Edition is a multi-tenant SaaS deployment (formerly GROW with SAP) with a standardised code line, limited customisation, and a fundamentally different licencing model based on modules and user types specific to that offering. The distinction is important for licensing because they operate under different contract terms, different user type definitions, and different upgrade obligations. Our S/4HANA migration licensing service covers both paths in detail.

An SAP Enterprise Agreement (EA) is a volume licensing arrangement that allows you to deploy SAP software across your organisation under a single licence fee rather than purchasing individual products and user types separately. EAs typically include an Indirect Access entitlement, deployment flexibility across subsidiaries, and a fixed annual fee for a defined period. They can be advantageous if you have a complex, growing SAP footprint — but the total commitment over the contract term is substantial, and SAP's initial EA proposal almost always includes products you don't need and volumes you'll never consume. Independent benchmarking of the EA terms before signature is essential. Our SAP contract negotiation service has benchmarked hundreds of enterprise contracts.

The SAP Order Form is a legally binding document that incorporates your Master Agreement terms. Key areas to review: the exact Bill of Materials (BoM) — confirm you're only licenced for products you actually use and at the right user type quantities; the maintenance schedule — confirm the Enterprise Support percentage (22% of net licence value annually) applies to the net amount, not any inflated list price; contractual use rights — confirm you have the deployment rights you need for cloud, on-premise, or hybrid scenarios; and term and exit provisions — ensure you're not locked into a multi-year term without adequate exit mechanics. Never sign an SAP Order Form without independent review. A 30-minute call with our SAP licensing experts before signature can prevent years of overpayment.

Start 12–18 months before your renewal date. SAP's commercial team will have been building their case for why you need to expand your licence estate for months before they approach you. The organisation that prepares in advance — with a clean ELP, a reclassified user estate, a benchmark of competitive alternatives, and independent legal review of the renewal terms — consistently achieves better outcomes. The organisation that waits until SAP presents a renewal proposal and reacts to it is negotiating from weakness. Our contract negotiation advisory starts with a pre-renewal positioning assessment.

Almost always, yes. S/4HANA introduces a new user type framework — the Professional, Functional, Developer, and Employee structure — that doesn't map directly to the ECC user type classifications you're currently licenced under. Users who were licenced as Professional in ECC may require review to determine whether they still need Professional-level access in S/4HANA, or whether simplified role design in S/4HANA allows them to be licenced at a lower tier. Additionally, S/4HANA introduces new functionality (embedded analytics, Fiori-based applications) that can change how users interact with the system and what licence type they require. Migration is a forcing function for a thorough licence review — either you do it proactively, or SAP's measurement team does it reactively. Our S/4HANA migration licensing service addresses this ahead of go-live.

SAP ECC mainstream maintenance ends in 2027, affecting approximately 85% of SAP's installed base who still run ECC. Extended maintenance — at additional cost — is available until 2030, and SAP has indicated this may extend further, though no official commitment exists beyond 2030. The maintenance end date matters for licensing because SAP uses it as a significant commercial pressure point in renewal and migration conversations. Organisations that understand the actual risk (continued operation on ECC without SAP support is a real but manageable risk for many) are better positioned to negotiate than those who accept SAP's migration urgency framing at face value.

SAP offers three conversion paths: system conversion (technical migration of your existing ECC system in place), selective data transition (rebuilding your S/4HANA environment with chosen data sets), and new implementation (greenfield deployment). The licensing implications differ significantly. In a system conversion, your existing licence entitlements are typically carried forward, subject to a reconciliation process. In a greenfield deployment, you're effectively negotiating a new contract — which can be an opportunity to right-size your estate, but also carries the risk of SAP proposing an inflated starting position. Independent advice before committing to a conversion path prevents you from locking in a poor commercial position for the next decade of your SAP estate.

SAP Enterprise Support is SAP's mandatory support programme for enterprise customers, currently priced at 22% of net licence value annually. It replaced the previous Standard Support tier several years ago and includes SAP's support portal, SAP Solution Manager tooling, and SAP's direct support access. Enterprise Support is built into every SAP contract and cannot be eliminated — but the base on which it's calculated (net licence value) can be reduced through licence renegotiation, and in some circumstances the percentage itself has been negotiated as part of larger commercial discussions. Switching to third-party support (providers such as Rimini Street or Spinnaker Support) is a route some organisations take to reduce support costs significantly, though it carries implications for your SAP relationship and future upgrade eligibility.

Third-party SAP support providers such as Rimini Street and Spinnaker Support offer support for SAP ECC systems at significantly lower cost than SAP Enterprise Support — typically 50% or more in annual savings. They provide technical fixes, regulatory and tax updates, and security patching for your existing SAP version without requiring you to upgrade. The trade-offs: you lose access to SAP's innovation roadmap updates delivered through standard support, your SAP contract relationship will change, and if you return to SAP support in the future, requalification costs apply. The business case for third-party support is strongest for organisations running stable ECC environments with no near-term S/4HANA migration planned. Our SAP support cost reduction service analyses both paths.

SAP's licensing team is SAP's commercial team. Their role is to maximise the revenue SAP extracts from your engagement — whether through audit claims, renewal pricing, or upsell of new products. We are structurally on the opposite side of that table. We receive no revenue from SAP, no reseller commissions, no referral fees from any SAP partner. Our only commercial interest is the outcome we deliver for you. Former SAP insiders — including people who previously worked on SAP's audit and commercial teams — built this firm specifically to apply that insider knowledge in defence of enterprise buyers. Read about our team and approach →

A free 45-minute discovery call. No pitch, no proposal, no obligation — just a direct conversation about your SAP environment, the problem you're trying to solve, and our honest assessment of whether and how we can help. We'll tell you if the answer is "you don't need us for this" — because our reputation depends on giving you straight advice, not selling you an engagement. Book that call here →

Yes — and the sooner you contact us in an active audit, the better the outcome. We mobilise within 48 hours for active audit engagements. The most critical juncture is before any data is submitted to SAP's measurement team. Once SAP has your USMM output and has built their initial ELP, the challenge process is harder — though still very much achievable. If you're at any stage of an SAP audit, contact us immediately. See our SAP audit defence service and our full SAP audit guide for more detail.

Yes. All engagements are conducted under mutual NDA. Your SAP contract terms, system measurement data, commercial negotiation details, and all materials you share with us are treated as strictly confidential. We do not share client information with SAP SE or any SAP-affiliated entity, and we do not use anonymised client data in any public material without explicit permission. Confidentiality is foundational to the trust that independent advisory requires.