SAP Named User Licensing Guide: User Types, FUE Metrics, Indirect Access and Right-Sizing Strategy

SAP's Named User licensing model remains the dominant commercial framework for ECC and S/4HANA on-premises deployments. For most enterprises, it is also one of the least audited and most over-purchased licensing arrangements in their software portfolio.

The core complexity stems from three factors: SAP offers more than 20 distinct user types with overlapping feature sets and pricing that ranges from approximately 100 per year (Employee Self-Service) to over 3,000 per user annually (Professional User). Second, SAP has 3,000+ products and over 100 usage metrics, creating enormous ambiguity in licensing interpretation. Third, indirect access — where third-party systems read from or write to SAP without a named user licence — remains a critical audit risk in 2026 for any organisation linking cloud, middleware, or partner solutions to SAP.

This paper unpacks the Named User licensing model, maps the full user type taxonomy and pricing landscape, explains the audit mechanism (including the Licence Audit Workbench), and provides a structured right-sizing methodology. We also cover the Digital Access alternative — particularly relevant for integration-heavy environments — and the Digital Access Adoption Programme (DAAP), which offers up to 90% discount on conversion to Digital Access pricing for a limited time.

SAP's Named User model assigns a licence type to an individual person. That licence grants the person access to a defined set of SAP functionality. The person is "named" in the system (typically via user IDs tracked in the Licence Admin Workbench), and SAP charges an annual fee for that named assignment.

Core Principles of Named User Licensing

Unlike consumption-based or cloud FUE (Full User Equivalents) models, Named User licensing is a fixed, capacity-based arrangement. Once you assign a Professional User licence to an employee, you pay the annual fee regardless of whether that employee uses the system daily, weekly, or not at all. This creates three immediate implications for enterprises:

• Capacity planning: You must forecast user counts and types accurately months or years in advance.
• Headcount volatility: Mergers, reorganisations, and attrition directly impact licence costs. A company with 5,000 users may suddenly need 5,200 or contract to 4,800, requiring licence portfolio rebalancing.
• Feature creep: As organisations assign more users to higher-value user types to unlock new capabilities, licence spend compounds without proportional business benefit.

Why Named User Licensing Persists

From SAP's commercial perspective, Named User licensing offers predictability. Enterprise buyers commit to a user count, and SAP's revenue is fixed across the contract term. From the enterprise perspective, it can provide cost certainty — if your user count is stable, your licence costs are stable.

However, this model breaks down in scenarios involving high-volume integrations, temporary workforce scaling, or complex enterprise architectures where indirect access becomes difficult to control.

SAP's user types are hierarchical. A higher-tier user type can generally perform all functions of lower-tier types, but at a higher price. Understanding the taxonomy is critical to right-sizing.

The Professional User Trap

Professional User is SAP's highest-cost Named User type at approximately 3,000–3,500 per year. Many enterprises assign this type broadly — to anyone who might need to access more than one functional area, or anyone with a senior title — without analysing actual system usage.

In reality, most organisations can meet their business requirements with a much smaller number of Professional Users. The typical distribution we observe in right-sizing engagements is:

• 10–15% Professional Users (true power users, process owners)
• 30–40% Limited Professional or Functional Users (focused transactional staff)
• 40–55% Employee Self-Service or read-only users (reporting, self-service HR/expense)

Limited Professional vs Functional User

These types are often conflated. The distinction:

• Functional User: Focused access to specific modules (Finance, Procurement, Warehouse) with full transactional authority within those modules. No access to SAP core systems or cross-functional data.
• Limited Professional User: Access to a subset of features and modules, but with some cross-module visibility. Priced identically but appropriate for staff needing multi-module awareness without full Professional User capability.

Developer and Test Users

Developer and Test user types are valid only for non-production SAP instances. Assigning a Developer licence to a Production user violates your licence agreement and creates audit exposure. This is a common misclassification. Before confirming any user type assignment, confirm the target system (Dev/QA/Prod) and the actual user role.

For RISE with SAP, SAP Hana Cloud, and cloud-native S/4HANA deployments, SAP has moved away from Named User licensing toward Full User Equivalents (FUE). This section is critical for organisations migrating to the cloud or negotiating new cloud contracts.

What Is an FUE?

An FUE is a unit of measurement that abstracts the specific user type. SAP calculates FUEs based on user type and engagement model:

• Professional User = 1.0 FUE (full system access)
• Functional / Limited Professional = 0.5 FUE (module-specific access)
• Employee Self-Service = minimal FUE (typically 0.1–0.2, sometimes free)
• Contingent Worker / Partner Portal = 0.2–0.5 FUE (depends on access scope)

Named User vs FUE: Cost Implications

Converting from Named User to FUE can yield significant savings, particularly if your current deployment is top-heavy with Professional Users. For a typical enterprise with 5,000 users distributed as 1,000 Professional (3,000 each), 2,000 Functional (1,500 each), and 2,000 ESS (100 each):

• Named User cost: (1,000 × 3,000) + (2,000 × 1,500) + (2,000 × 100) = 8 million annually
• Equivalent FUE capacity: (1,000 × 1.0) + (2,000 × 0.5) + (2,000 × 0.2) = 2,400 FUEs
• FUE cost at ~2,000 per FUE per year: 2,400 × 2,000 = 4.8 million annually
• Potential saving: 40%

Note: FUE pricing varies by region and engagement type. The above is illustrative. Always obtain SAP pricing for your specific scenario before making investment decisions.

Indirect access is the single largest licensing compliance risk in modern SAP deployments. It occurs when a third-party system — cloud integration platform, RPA tool, partner portal, analytics system — reads from or writes to SAP data without a direct named user interaction.

How Indirect Access Arises

Typical scenarios include:

• API Integrations: A cloud-based procurement platform pulls PO data from SAP via REST API, creates records, and posts receipts back.
• RPA: Robotic process automation scripts log into SAP, fill forms, and submit documents without human interaction.
• BI/Analytics: Tableau, Power BI, or Qlik connects to SAP, extracts transactional data in real-time or batched.
• EDI / Master Data Sync: Third-party suppliers sync invoices, shipments, or vendor data directly into SAP.
• Middleware (MuleSoft, Boomi, SAP PI): Integration platform reads from SAP and distributes data to multiple downstream systems.

In each case, SAP licence compliance requires either: (a) a named user licence for the system doing the access, or (b) a Digital Access licence covering that specific access pattern.

Digital Access Licensing

Digital Access is SAP's alternative licensing model for scenarios where traditional Named User licensing is impractical. Instead of licensing a "user," you licence the documents or transactions that flow through SAP from a third-party system.

Digital Access Pricing Model

Digital Access is priced per document type consumed. Example document types include:

• Purchase Orders (PO)
• Goods Receipts (GR)
• Invoices (IV)
• Sales Orders (SO)
• Delivery Notes (DN)
• Master Data Records (MD)

Pricing varies by document type and region. A typical pricing example: Purchase Orders might cost 0.05–0.10 per document, while more complex document types (Invoices with allocation) might cost 0.15–0.25.

Digital Access vs Named User: Which Model Fits?

Digital Access makes economic sense when:

• Integration volume is very high (>50,000 documents per month).
• User count is variable (temporary workforce, seasonal spikes).
• User is a system, not a human (RPA, API, EDI).

Named User licensing remains more economical when:

• Integration volume is low (<5,000 documents per month).
• Human users perform the actions (even if some are automated).
• User count is stable and forecastable.

Understanding SAP's audit methodology is essential for audit defence and for proactive compliance. SAP audits using a combination of manual review and automated tooling.

The Licence Audit Workbench (LAW)

The Licence Audit Workbench is SAP's primary tool for Named User compliance verification. It is installed in your SAP system and generates a comprehensive report of all active and inactive user accounts, user type assignments, and system usage data.

LAW Data Points

The LAW report typically includes:

• User ID and assignment: User name, assigned user type, date of assignment, last login.
• System usage: Module access, transaction codes executed, report generation, data changes.
• Inactive users: Users not logged in for 90, 180, or 365 days.
• Concurrent user analysis: Peak concurrent users per system (relevant for CAL licensing).
• Cross-system usage: Users accessing multiple SAP instances (ECC, BW, etc.).

Audit Frequency and Rights

Most SAP maintenance and service agreements grant SAP the right to conduct a full licensing audit every two years. Some agreements are more restrictive (every 3–5 years). At contract renewal, audit rights are often reconfirmed or expanded. Redress recommends reviewing your SAP contract's audit clause annually.

Common Audit Findings

Based on 180+ audit defence engagements, these are the most frequent findings SAP raises:

• Over-assigned user types: Users assigned Professional when their actual usage (via LAW) shows Functional-level access patterns. Finding: under-licensed, true-up required.
• Inactive users still licensed: Accounts inactive for 12+ months still assigned licences. SAP argues you owe for the entire period. Often negotiable during true-up.
• Undisclosed indirect access: Third-party systems (APIs, RPA, BI tools) accessing SAP without named user or Digital Access licences. Major exposure.
• Cross-system unlicensed access: User assigned Professional on ECC but also accessing BW, Portal, or other SAP products without additional multi-product licences.
• Concurrent user overages: CAL (Concurrent Access Licence) deployments where peak concurrency exceeded licenced capacity.

Audit Outcome Scenarios

Audit conclusions generally fall into three categories:

• Compliant: Actual usage aligns with licensed user types. No true-up required. (Rare.)
• Minor adjustment: Discrepancy found but limited exposure. True-up typically 50,000–150,000.
• Major true-up: Significant over-assignment or indirect access gap. True-ups of 200,000–1,000,000+ are not uncommon in complex deployments.

Right-sizing is the systematic process of aligning your licensed user types with actual system usage. It is your primary tool for reducing Named User licence spend while ensuring audit compliance.

Right-Sizing Framework

We recommend a six-step approach:

Typical Right-Sizing Outcomes

Based on 180+ engagements, the average right-sizing exercise yields a 15–40% reduction in Named User licence spend. The range depends on how long the organisation has gone without formal audit or optimisation:

• Recently audited (0–2 years): 5–15% savings. Compliance is already relatively tight.
• Audited 2–5 years ago: 15–25% savings. Moderate over-licensing due to headcount changes, role evolution.
• Never formally audited or >5 years: 25–40% savings. Significant over-licensing; many inactive users; widespread Professional User assignments that do not reflect actual usage.

Common Right-Sizing Pitfalls

• Data quality: Licence Audit Workbench data is only as good as your user maintenance practices. If inactive accounts are never deleted, LAW will show false activity. Clean your user base first.
• Business exception cases: Some users may have legitimate reasons for a higher licence type despite lower usage (executive dashboards, backup authority, compliance requirements). Document these exceptions clearly.
• Growth planning: Do not reclassify based on today's usage alone. If you are planning to onboard 500 new finance users in 6 months, account for that in your Functional User capacity.
• SAP product complexity: Some features (BW analytics, Portal, Workflow) may require Professional User even if core ECC usage is Functional-level. Work with SAP or a licensing advisor to clarify scope.

SAP's Digital Access Adoption Programme (DAAP) is a time-limited offer to incentivise migration from Named User to Digital Access licensing. For organisations with high-volume integrations, DAAP can reduce licence spend by 50–70% compared to Named User baseline.

DAAP Structure and Incentive

Under DAAP, SAP offers:

• Up to 90% discount on Digital Access pricing for a defined conversion period (typically 12–24 months from agreement signature).
• Flexible phased migration: You do not need to convert all integrations at once. Gradual migration to Digital Access is allowed.
• Named User + Digital Access hybrid: Run both licensing models simultaneously during transition.

DAAP Calculation Example

Consider a large enterprise with 10,000 monthly purchase orders flowing from a cloud procurement system into SAP:

• Named User approach: Licence the system as a Professional User: 3,000–3,500 per year. (Plus you may need multiple licences for redundancy, backup, or different integrations.)
• Digital Access approach: 10,000 POs/month × 12 months = 120,000 annual transactions. At 0.08 per PO with 90% DAAP discount: 120,000 × 0.08 × 0.10 = 960 per year.
• Saving: ~3,000 per year via DAAP.

DAAP Eligibility and Timeline

As of April 2026, DAAP eligibility criteria are:

• Active SAP maintenance contract (SLA).
• S/4HANA or ECC on EHP 6 or later (for older systems, upgrade may be required).
• Documented integration scenario and document volume forecasts.

DAAP has no announced end date as of early 2026, but SAP has stated it is a time-limited programme. Redress recommends treating any DAAP discussion as time-sensitive; do not delay if Digital Access aligns with your architecture.

DAAP Negotiation Strategy

When approaching SAP about DAAP:

• Present a detailed integration inventory: which systems feed SAP, document types, monthly volume, expected growth.
• Request DAAP pricing for your specific document mix and volume profile.
• Negotiate flex: ±10–15% volume variance should be allowed without penalty.
• Lock in discount duration: Request multi-year discount continuity, not just 12 months.
• Include audit rights and measurement methodology in the amendment.

Effective SAP licensing negotiation is built on three pillars: data, alternatives, and timing. The following framework has been tested across 180+ negotiations and consistently yields 10–25% savings beyond standard list pricing and rightward shifts in commercial risk.

Pre-Negotiation Preparation

Step 1: Conduct a Right-Sizing Analysis

Before any contract negotiation, complete a Licence Audit Workbench analysis. This provides defensible data on your actual user type distribution and usage patterns. Armed with LAW analysis, you can:

• Show SAP your current over-licensing (e.g., 200 users currently assigned Professional but actually using Functional scope).
• Propose reclassification as a genuine cost reduction (vs. generic "we need a discount").
• Demonstrate your compliance and governance rigour, which improves negotiation position.

Step 2: Benchmark Against Digital Access

Obtain detailed Digital Access pricing for your integration scenarios. Even if you don't plan to convert, this establishes a competitive alternative. SAP will negotiate harder on Named User pricing if Digital Access is a credible option.

Step 3: Timing Around Renewal

Initiate negotiations 9–12 months before contract expiry, not 30 days before. This gives both parties time to model options and avoids last-minute pressure. If SAP threatens audit at renewal, reframe as opportunity: "Let's run LAW together, agree on a clean baseline, and lock in a fair price based on actual usage."

Negotiation Talking Points

Opening Offer

Present SAP with a reclassified user portfolio based on LAW analysis. For example: "Our LAW review shows 200 users currently assigned Professional but using Functional scope. If we reclassify these, our portfolio shrinks from 5,000 users (20% Professional, 40% Functional, 40% ESS) to a right-sized distribution (10% Professional, 50% Functional, 40% ESS). This saves 1.2 million annually. We'd like to lock in these savings in the new contract at list pricing."

Multi-Year Commitment Discount

Offer a 3- or 5-year commitment in exchange for a tiered discount: 5% Year 1, 7% Year 2–3, 10% Year 4–5. SAP values revenue predictability; multi-year lock provides that.

Efficiency Metrics

Propose efficiency targets: "We commit to maintaining a Professional-to-total-user ratio of no more than X% over the contract term. Any ratio improvement yields a rebate." This ties discount to your performance, which SAP finds attractive.

Digital Access Hybrid

Propose moving high-volume integrations (APIs, RPA, EDI) to Digital Access, retaining Named User for core staff. This typically costs less than pure Named User and positions you for future cloud migration.

Deal Structure Best Practices

• Audit protection: "SAP agrees not to conduct audit during Years 1–2 of contract, or only on 30-day written notice and with joint remediation plan if findings arise." This gives you runway to implement reclassifications without surprise audit exposure.
• Measurement methodology: "User type assignments are determined by Licence Audit Workbench output. Disputes resolved via joint review with independent arbiter if needed." (Avoids SAP unilaterally reinterpreting user type scope.)
• Volume flex: "User count can fluctuate ±10% annually without true-up. True-ups only apply if annual variance exceeds ±10%."
• Inactive user grace period: "Users inactive for 6 months are automatically delicensed with 3-month notice. No retroactive charges for the deactivation period."
• Multi-product clarity: "Named User licence grants access to ECC and standard analytics modules only. Additional SAP products (BW, SuccessFactors, Ariba, Fieldglass) require separate licences and are not covered by this Named User assignment."

Negotiation Anti-Patterns

Avoid these common mistakes:

• Asking for a percentage discount without justification: "We need 15% off." SAP will decline unless you offer something in return (multi-year commitment, efficiency targets, workflow streamlining).
• Threatening to migrate to oracle or another ERP: SAP knows migration cost is 20–50 million+. This threat lacks credibility for most enterprises.
• Using competitive pricing from a different vendor: SAP pricing is not directly comparable to Oracle, Workday, or Infor. Feature sets differ. Stick to SAP-to-SAP comparisons (Named User vs Digital Access).
• Negotiating in-contract: Once you sign, you have limited leverage. Negotiate renewals early.

Beyond price, the terms and conditions of your SAP licensing agreement determine your audit exposure and operational flexibility. This section outlines critical clauses to negotiate.

Audit Rights Clause

Default SAP language: "SAP may audit Licensee's use of the software at any time, up to once per calendar year, with 14 days notice."

Redress recommended language: "SAP may audit Licensee's Named User compliance once every two years, with 60 days written notice. Audit is conducted during normal business hours, on-site or remotely as agreed. SAP shall bear all travel and resource costs. Findings are shared within 30 days; Licensee has 90 days to respond with remediation plan. Any true-up is capped at 20% of annual licence fees, unless undisclosed indirect access is discovered."

Measurement Methodology Clause

This clause defines how SAP determines compliance. Without specificity, SAP has wide latitude to interpret user type scope.

Recommended clause: "User type determination is based on primary business function and system access pattern as measured by Licence Audit Workbench output for the preceding 12 months. Professional User is assigned only to staff requiring access to 8+ SAP modules and executing 50+ distinct transaction codes. Functional User is assigned to staff with access to 1–3 modules and defined transaction codes. ESS is assigned to self-service and read-only access. In event of dispute, determination is made jointly by Licensee and SAP, with escalation to [independent arbiter] if consensus is not reached within 60 days."

Dispute Resolution Process

SAP will propose: "Any disputes are resolved through SAP's standard audit appeal process." This is non-binding mediation that SAP controls.

Redress recommended language: "Disputes regarding user type classification or licence compliance are resolved as follows: (1) Joint technical review by Licensee and SAP team within 30 days. (2) If unresolved, escalation to [both parties' CFO/VP level] within 14 days. (3) If still unresolved, binding arbitration under [JAMS / AAA] rules, with costs split 50/50. Arbitration decision is final and binding."

DAAP Pricing Lock

If you negotiate DAAP pricing, lock it in contractually. SAP's default language allows DAAP to expire after 12 months without extension.

Recommended language: "Digital Access Adoption Programme discount of [90%] is locked in for the full contract term (through [Year/Date]). Discount is not subject to sunset, withdrawal, or renegotiation during the contract term. If SAP discontinues DAAP for the broader market, Licensee retains the negotiated discount pricing."

Indirect Access Licensing Clause

Be explicit about what counts as indirect access and how it is licensed.

Recommended language: "Third-party systems accessing SAP via API, middleware, EDI, or other automated means are licensed as follows: (a) Systems licensed as Professional Named Users; (b) Document-heavy integrations (>5,000 documents/month) are licensed under Digital Access; (c) Read-only analytics access via Licensee's existing Business Warehouse entitlement does not require separate licence. Licensee shall maintain an integration inventory and provide it to SAP annually. Any unlicensed access discovered by Licensee is reported to SAP within 30 days; retroactive true-up is limited to 12 months of undisclosed access."

Volume Flex and True-Up Mechanics

Standard SAP language often allows unlimited user count variance and retroactive true-ups for any overages. This creates budget uncertainty.

Recommended language: "User count may vary by ±10% annually without true-up. True-ups are assessed only if variance exceeds ±10%. True-up is calculated as ([Actual Users] - [Licensed Users]) × [Average cost per licence] for the overage period, not to exceed 12 months. True-ups are invoiced within 30 days of audit completion and are due within Net 45."

Multi-Product Clarity

SAP often interprets Named User licences as covering multiple SAP products (ECC, BW, SuccessFactors, Ariba, etc.). Clarify scope.

Recommended language: "Named User licence covers access to SAP ECC and integrated SAP Analytics Cloud reporting only. Access to BW, SuccessFactors, Ariba, Fieldglass, Concur, or other SAP product requires separate product-specific licence. Licensee is not obligated to purchase multi-product packages if only single-product access is required."

This case study illustrates the practical application of right-sizing, renegotiation, and audit defence across a large SAP deployment.

Scenario

Organisation: Large multi-national financial services firm, 50,000 employees globally.

SAP footprint: ECC (core finance, procurement, HR), BW (analytics), Portal (user dashboards). Deployed in EMEA, APAC, Americas across 15 subsidiaries.

User base: 5,000 named SAP users distributed as follows:

• 1,200 Professional Users (at ~3,200/year) = 3,840,000
• 2,100 Functional Users (at ~1,600/year) = 3,360,000
• 1,700 Employee Self-Service (at ~120/year) = 204,000
• Total annual licence spend: 7,404,000

Audit trigger: SAP conducted a surprise audit (permitted under then-current contract) in Q2. Findings indicated 18% over-licensing and undisclosed indirect access via an RPA tool.

Right-Sizing Analysis

Redress pulled Licence Audit Workbench data and cross-referenced with HR data and transaction logs. Key findings:

• Over-assigned Professionals (250 users): Assigned as Professional but actual usage was single-module (Procurement or Finance) with transaction code count in Functional range (30–50 vs 100+ for true Professionals). LAW analysis showed these users rarely accessed multi-module integration points.
• Inactive users (180 users): No system access recorded for 18+ months, yet still assigned and paid for.
• Indirect RPA access (undisclosed): An automation platform accessed SAP 120,000 times per month for procurement processes but had no named user licence. True-up exposure: 1–2 million for 18 months of back charges.
• Over-licensed Functional (150 users): These users only used self-service expense reports and self-serve training—should be ESS, not Functional.

Reclassification and Re-Negotiation

With LAW data in hand, Redress proposed a reclassified portfolio:

• 950 Professional Users (vs 1,200): Remove 250 over-assigned. Keep 950 who genuinely require multi-module access.
• 2,250 Functional Users (vs 2,100): Add 150 from mis-assigned Functional, subtract 0 from Professional reclassification net. This provides relief to those needing Functional scope.
• 1,820 Employee Self-Service (vs 1,700): Remove 180 inactive, add 150 from Functional mis-assignments. Net +140 for new HR self-service rollout planned for Year 2.

Revised annual licence spend: 950 × 3,200 + 2,250 × 1,600 + 1,820 × 120 = 3,040,000 + 3,600,000 + 218,400 = 6,858,400

Saving from reclassification: 545,600 annually (7.4% reduction).

For the RPA indirect access, Redress negotiated Digital Access conversion at 0.06 per document, covering 120,000 documents/month = 1.44 million/month or ~17.3 million annually under baseline Digital Access. However, with DAAP 90% discount: ~1.73 million annually. This was still exposure for past-due fees, so Redress negotiated a one-time true-up of 250,000 (covering ~3 months of back liability) in exchange for future compliance.

Negotiation Outcome

Armed with defensible LAW analysis, the firm re-negotiated the SAP contract renewal as follows:

• Reclassified user portfolio locked in: 950 Professional, 2,250 Functional, 1,820 ESS.
• Annual licence cost: 6.86 million (down from 7.40 million; 7.4% reduction).
• RPA access converted to Digital Access under DAAP: 1.73 million/year for 120,000 documents/month. Net savings vs Named User for the RPA system: ~1.47 million annually.
• 3-year contract with multi-year discount: 5% Year 1, 7% Years 2–3, on Named User spend (net: 6.51 million Year 1, 6.38 million Years 2–3). Additional 1.2 million/year saving in Years 2–3 due to RPA efficiency gains.
• Audit protections: No audit in Years 1–2 unless major compliance breach. Year 3 audit with 60 days notice and 20% annual fee cap on true-ups.
• True-up for RPA back liability: One-time 250,000 charge (settled via discount offset).

Financial Impact

3-year contract value:

• Year 1: 6.51 million (Named User) + 1.73 million (Digital Access) = 8.24 million
• Year 2: 6.38 million + 1.73 million = 8.11 million
• Year 3: 6.38 million + 1.73 million = 8.11 million
• 3-year total: 24.46 million

vs Prior trajectory (no renegotiation):

• Year 1 (post-audit): 7.40 million + 250,000 true-up + 1.47 million RPA baseline = 9.12 million
• Year 2: 9.12 million × 1.05 (assumed annual growth) = 9.58 million
• Year 3: 9.58 million × 1.05 = 10.06 million
• 3-year total: 28.76 million

3-year saving: 4.3 million (15% reduction).

ROI on engagement (150,000 fee): Payback within 1.5 weeks.

Key Takeaways from Case Study

• LAW analysis is foundational: Without it, the firm would have passively accepted SAP's audit findings and paid 2 million+ in unjustified true-ups.
• Right-sizing is a conversation starter: The reclassification gave the firm negotiating credibility. SAP acknowledged the logic and was willing to discount because the firm had done the work.
• Indirect access is everywhere: RPA, API, and automation tools are standard in modern enterprises. Licensing them is not optional; it must be part of your portfolio strategy.
• Multi-year commitments drive discounts: A 3-year deal with audit protection and efficiency targets is more valuable to SAP than annual renegotiations. Use that leverage.

Redress Compliance is a Gartner-recognised, 100% buyer-side enterprise software licensing advisory firm. We have no commercial relationships with any software vendor — our only client is the enterprise buyer.

Our SAP licensing advisory practice has completed 180+ SAP Named User and licensing engagements across EMEA, North America, and APAC. We specialise in Named User right-sizing, audit defence, contract negotiation, and Digital Access adoption strategies. We typically engage 9–12 months before contract renewal to allow sufficient time for Licence Audit Workbench analysis, competitive benchmarking, and negotiation positioning.

SAP Licensing Services · SAP Knowledge Hub · All White Papers