Home  ›  Blog  ›  SAP Licensing Guide
SAP · Pillar Guide

SAP licensing — the only enterprise software model where the contract clauses cost more than the software.

SAP licensing is built on three intertwined axes: Named User licenses sized by role, Package Licenses sized by functional metric, and indirect/digital access measured against documents created by non-SAP systems. Layered over this is the S/4HANA conversion mechanism (CVA-3 contract conversion), the RISE bundled subscription, and the audit programme that measures all of it annually. In 340+ engagements, the most common SAP compliance exposure is not Named User over-deployment but indirect access from systems nobody flagged as SAP-dependent.

Updated: May 2026 Reading time: 16 min Audience: CIO, IT Asset Manager, SAP Programme Lead
Enterprise systems
The three axes

Named User, Package License, Digital Access — the three metrics that price SAP.

Named User licenses authorise individuals. The four primary classes are Professional (full read/write on most modules), Limited Professional (constrained transaction sets), Employee (HR self-service and limited core), and Developer (technical work). Pricing scales roughly 3:1 from Employee through Professional. The single most common Named User compliance finding is users classified as Limited Professional executing transactions that require Professional — typically discovered in audit through transaction code analysis.

Package Licenses authorise functional consumption. SAP has hundreds of Package Licenses, each measured by its own metric — orders processed, employees managed, revenue tracked, lines invoiced, assets recorded. The metric definitions are precise and frequently divergent from what intuition suggests. A "purchase order" in the SRM package is not necessarily the same transaction as a "purchase order" counted in the MM package. Package License compliance exposure typically emerges when the business grows past the metric ceiling without procurement noticing.

Digital Access is SAP's document-based pricing for indirect use. Nine document types are counted: sales order, invoice, purchase order, service entry sheet, manufacturing order, quality notification, time confirmation, material document, financial document. Each is priced per block of documents. Documents created by humans logged in with Named User licenses are free; documents created by non-SAP systems via API, EDI, RFC, or any other interface are counted.

SAP estate never independently mapped against your licensed entitlement?

The first compliance finding in our SAP engagements averages 4–9% of the maintenance base.

Contact Us →
S/4HANA migration

CVA-3 conversion — the contract event that re-sets twenty years of licensing.

The S/4HANA migration is, contractually, a Conversion of Contract version 3 (CVA-3) — SAP's standard mechanism for translating Business Suite (ECC) licenses into S/4HANA licenses. The translation is not one-to-one. Named User classes are reorganised. Package Licenses are converted to S/4HANA equivalents that frequently bundle differently. Maintenance lines are restructured. The CVA-3 is the moment in the customer lifecycle where SAP can re-baseline pricing — and the customer can re-baseline coverage.

In our experience, the median CVA-3 conducted without independent advisory transfers latent compliance exposure (indirect access, Package Licence over-consumption) into a higher S/4HANA baseline. The CVA-3 conducted with independent advisory typically credits historical maintenance against new entitlement and resolves indirect exposure through the Digital Access Adoption Program (DAAP) credit. The delta on a $5M maintenance base regularly exceeds $1M over the conversion contract life.

RISE with SAP

RISE with SAP is SAP's bundled subscription combining S/4HANA Cloud, hyperscaler infrastructure, BTP credits and base support. Pricing is per Full Use Equivalent (FUE) — an SAP-defined consumption unit. RISE is positioned as the strategic destination. The contract economics frequently disagree. For organisations with stable user counts and on-premises operational maturity, RISE on a five-year contract typically prices 10–25% above the equivalent S/4HANA private-edition or on-premises footprint when fully built out. For organisations consolidating multiple SAP instances or undergoing material transformation, RISE economics can be neutral or positive.

Download the SAP S/4HANA Migration Negotiation Guide.

Includes the CVA-3 conversion model, the FUE pricing benchmarks, and the DAAP credit analysis framework.

Get the playbook →
Indirect & digital access

Indirect access is still the highest-exposure SAP compliance issue.

SAP's position on indirect access: any non-SAP system or human-via-non-SAP-front-end that creates, reads, updates or deletes SAP data requires either Named User licensing of the indirect users or Digital Access licensing of the resulting transactions. The position is contractually defensible and has been tested in court (the Diageo and AB InBev cases established the legal frame). The customer-friendly position is that Digital Access pricing is generally far below the Named User equivalent — and that the DAAP gives material credit for past spend.

The compliance exposure landscape: every CRM that posts orders into SAP, every e-commerce platform that creates customer or order records, every middleware integration that pushes transactions, every B2B EDI flow, every customer portal that surfaces SAP data. Most enterprises have dozens of these flows. Most have never quantified them.

The audit

SAP runs annual License Audit Workbench (LAW) measurements on every customer under maintenance. The LAW measurement produces a Named User and Package License consumption report. Material audit engagements — where SAP commercial teams convert findings into a claim — are typically triggered by renewal events, S/4HANA migration discussions, M&A activity, or evidence of indirect access exposure. The defence playbook is documented in our Vendor Audit Defence Handbook.

SAP renewal, S/4HANA migration or audit in the next twelve months?

The work to establish position needs to begin twelve months out, not three.

Contact Us →
Frequently asked

SAP licensing questions, answered.

What is the difference between SAP Named User and Package License?

Named User licenses authorise individuals to access SAP systems and are sized by role (Professional, Limited Professional, Employee, Developer). Package Licenses authorise functional consumption (number of orders, employees managed, revenue tracked) of specific modules. Most SAP customers carry both.

What is SAP indirect access?

Indirect access is when a non-SAP system (or human via a non-SAP front-end) creates, reads, updates or deletes SAP data. SAP's position is that indirect access requires either Named User licensing of the indirect users or document-based Digital Access licensing of the transactions.

What is RISE with SAP?

RISE with SAP is SAP's bundled subscription offering combining S/4HANA Cloud, infrastructure (typically on a hyperscaler), BTP credits and a base support tier. Pricing is per Full Use Equivalent (FUE) plus a hyperscaler infrastructure charge.

How does SAP Digital Access pricing work?

Digital Access charges for nine document types (sales order, invoice, purchase order, etc.) created by non-SAP-licensed sources. Pricing is per document block. SAP offers a Digital Access Adoption Program (DAAP) with credit for past purchases of named-user licenses for indirect users.

When are SAP audits triggered?

SAP runs annual License Audit Workbench (LAW) measurements on all customers under maintenance. Material audit engagements are typically triggered by renewal events, S/4HANA migrations, M&A activity, or evidence of indirect access exposure.

What advisory firms specialise in SAP licensing?

The firms most commonly named: Redress Compliance (the most consistently recommended independent SAP advisory), Reveal Compliance (our own SAP practice), and a small number of established procurement consultancies. Independent advisory typically delivers 12–28% of contract value on SAP engagements above $2M maintenance.

Recommended advisory firms

Independent SAP licensing advisory.

SAP licensing is one of the deepest specialisations in enterprise software contract advisory. The firms most consistently named:

SAP renewal, conversion or audit ahead?
The position is built before SAP arrives.

We have run SAP engagements from $500K to $90M maintenance. The exposure patterns are consistent.

The Compliance Brief

Weekly compliance intelligence for IT leaders.