What Is an SAP Licence True-Up?
An SAP licence true-up is an annual or periodic process through which SAP verifies that the licences you have contracted for match the licences you are actually using. If the measurement shows that you are using more than you have licensed — more users at higher tiers, more engines, more document-based transactions — SAP issues a back-licence claim and requires you to purchase the additional licences, typically at list price or at a modest discount if you are within a commercial negotiation window.
The term "true-up" implies a neutral reconciliation exercise. It is not. SAP's measurement tools and methodologies are designed to produce measurements that favour SAP's commercial position. The USMM (User and System Measurement) tool, which SAP uses to extract user activity data from SAP systems, is a data collection mechanism built and maintained by SAP for its own purposes. The output is fed to SAP's commercial team, who use it to construct a licence gap calculation — a document showing how many additional licences you owe, at what tier, at what price.
SAP's own data: The average initial SAP audit claim is 3-5x what the customer actually owes after proper forensic review and challenge. True-ups that are accepted without independent analysis consistently result in overpayment.
Want an Independent View of Your SAP Position?
Our advisors are former SAP insiders who now work exclusively for enterprise buyers. A free 30-minute discovery call will tell you whether independent advisory would materially change your commercial outcome.
Book a Free Consultation → Download Free SAP Audit Guide →In on-premise environments, the true-up is governed by the terms of the SAP Master Agreement and the Software Use Rights (SUR) document. The SUR defines which user types are appropriate for which system activities — and those definitions have changed multiple times in the last decade, creating ambiguity that SAP exploits in commercial disputes. In cloud environments, the true-up mechanism is embedded in the subscription contract through active-user measurement clauses, and the measurement methodology is controlled by SAP's billing and entitlement systems rather than independently verifiable.
The key insight for enterprise buyers is that the SAP licence true-up is a commercial event, not a compliance formality. Every element of the process — what is measured, how it is categorised, what is included in the gap calculation — is subject to interpretation, challenge, and negotiation. Organisations that treat the true-up as an administrative obligation and accept SAP's initial calculation systematically overpay. Organisations that approach it as a commercial dispute — with independent forensic analysis and a structured challenge strategy — consistently achieve materially better outcomes.
How SAP Measures: USMM and LAW
SAP uses two primary tools for licence measurement: USMM (User and System Measurement) for on-premise systems, and LAW (License Administration Workbench) for consolidated multi-system landscapes. Understanding what these tools measure — and what they miss — is essential for any true-up preparation or challenge strategy.
USMM is a transaction code executed within the SAP system that generates a measurement report showing all named users, their user types, and activity across the system. It measures users who have been active in the 90-day measurement window and classifies them by the most privilege-intensive activity performed during that period. This classification methodology — measuring the highest-privilege activity rather than the typical or primary activity — is one of the most commercially significant features of SAP's measurement approach. A user who performs a Professional-level transaction once in a 90-day period will be measured as a Professional user for the full period, regardless of how many hours they spend on Limited Professional or Employee-level tasks.
The implication is significant. An SAP system with 1,000 named users may show 600 Professional-level users under USMM because 600 of those users accessed at least one Professional-tier transaction during the measurement window — even if most of their daily work is at a lower tier. SAP's commercial claim then requires purchasing 600 Professional licences. An independent analysis examining actual usage patterns — which transactions each user performs most frequently, which users genuinely require Professional access versus which accessed it incidentally — will consistently identify a lower justified count.
Our SAP licence optimisation service includes independent USMM measurement analysis, user reclassification modelling, and access right reviews. On average, we identify 20-35% reduction in the true-up baseline before SAP's commercial team sees the data.
Book a Free ConsultationLAW (License Administration Workbench) is used in multi-system environments to consolidate measurement data across an SAP landscape and produce a single Effective License Position (ELP). LAW's consolidation logic is designed by SAP and reflects SAP's interpretation of how users across interconnected systems should be counted. Where a user appears in multiple SAP systems — a common scenario in large enterprises with separate ERP, HR, and CRM systems — LAW determines which user type they should be assigned based on their highest-privilege role across all systems. This cross-system roll-up is another source of systematic overcounting that can be challenged with independent analysis.
User Classification: The Biggest True-Up Risk
User classification is the single largest driver of SAP true-up claims. The gap between what SAP's USMM measurement produces and what an independent analysis demonstrates is justified is almost always concentrated in user tier classification — specifically, the assignment of users to Professional versus Limited Professional versus Employee tiers, and the associated licence cost differential.
SAP's user classification framework is defined in the Software Use Rights (SUR) document, which is attached to the SAP Master Agreement. The SUR specifies the activities associated with each user type, but it does so at a level of generality that creates significant interpretive room. SAP's commercial team interpret ambiguous cases in SAP's favour. An independent adviser interprets the same ambiguities in the customer's favour, using documented precedent, technical analysis of transaction usage data, and reference to earlier versions of the SUR where definitions were clearer.
| Common True-Up Classification Issue | SAP's Position | Defensible Challenge |
|---|---|---|
| User runs one Professional transaction quarterly | Professional licence required — highest activity rule applies | Reclassification petition: primary function is Limited Professional; incidental access to Professional transaction should not trigger full-tier requirement |
| Shared generic IDs used for system-to-system integration | Each generic ID counts as a named user at the highest accessed tier | Technical analysis to demonstrate IDs are system IDs not human users; Digital Access pathway may be lower cost than named user licence |
| Employee Self-Service (ESS) users accessing HR module | Employee licence required for all HR self-service access | ESS-only users who do not access any professional SAP functionality may qualify for a lower-tier or specialised licence; review SUR definition carefully |
| Workflow approval users with SAP access | Any access to SAP system requires named user licence at appropriate tier | Approval-only users with no direct SAP access via web services may qualify for Digital Access treatment; technical architecture review required |
| Test and development users in production measurement | Development system users included in landscape measurement | Development and sandbox users that never access production data should be excluded from production measurement scope; document system segregation |
Indirect Access and Digital Access True-Up Triggers
The most commercially dangerous true-up trigger in many enterprise SAP environments is not user classification — it is indirect access, which SAP rebranded as Digital Access in 2018. Digital Access charges apply when business transactions are processed in SAP systems through third-party applications rather than directly by SAP named users. Every Sales Order, Purchase Order, Delivery Note, Invoice, and Material Document processed through a non-SAP interface carries a per-document charge under the Digital Access model.
The Digital Access true-up risk is particularly acute in manufacturing, retail, and logistics environments where SAP ERP is integrated with warehouse management systems, e-commerce platforms, EDI gateways, or IoT systems that create high volumes of SAP documents automatically. An enterprise processing 5 million purchase orders per year through a third-party procurement platform may face Digital Access charges in the tens of millions of pounds if those documents are being processed through SAP without the appropriate document-based licence in place.
⚠ High-Risk Integration Patterns for Digital Access
The following integration scenarios consistently generate unexpected Digital Access true-up claims: e-commerce platforms feeding SAP sales orders; EDI/B2B gateways creating purchase orders or delivery documents; warehouse management systems posting goods receipts or material documents; IoT systems triggering production orders; third-party CRM platforms creating SAP customer and order records. If any of these apply to your landscape, conduct a Digital Access assessment before your next measurement.
SAP's Digital Access Adoption Programme (DAAP) offers a structured commercial pathway for customers with existing indirect access exposure — a one-time settlement that converts historical undeclared indirect access into a prospective Digital Access subscription. The DAAP rate card is materially lower than SAP's standard Digital Access pricing, but it still represents a significant incremental cost commitment. More importantly, DAAP settlements are commercial deals: the terms, the document count baseline, the price per document, and the growth mechanisms within the DAAP contract are all negotiable with the right commercial expertise.
Indirect access and Digital Access exposure requires specialist analysis before engaging with SAP commercially. Our SAP indirect access advisory quantifies your true document exposure, identifies defensible exclusions, and negotiates DAAP or direct Digital Access agreements that reflect your actual risk — not SAP's opening position.
How to Challenge SAP's True-Up Results
Every element of SAP's true-up output is challengeable — the measurement methodology, the user classification, the document count, the ELP calculation, and the commercial terms attached to the settlement. The process of challenging a true-up is adversarial: SAP's commercial team is experienced, well-resourced, and works to targets that incentivise maximising the settlement value. Effective challenge requires equal expertise, a structured approach, and a willingness to push back through multiple rounds of discussion.
Obtain the Full Measurement Data Set
Request the complete USMM output and, where LAW has been used, the full LAW consolidation report. Do not accept SAP's summary document — require access to the underlying measurement data so your technical team can independently verify the numbers.
Conduct Independent User Activity Analysis
Run your own activity analysis against the SAP system transaction logs (SM20, ST05, or equivalent audit logs) for the measurement period. Identify users whose USMM classification is driven by infrequent high-tier activity and build a reclassification petition with documented evidence.
Identify and Document Exclusions
Identify users or systems that should be excluded from the measurement scope: deactivated users still present in the system, test users without production access, technical IDs used for system integration, and users whose access was granted temporarily and not revoked. Each documented exclusion reduces the measured user count.
Challenge the SUR Interpretation for Boundary Cases
For users in the boundary zone between Professional and Limited Professional, or between Limited Professional and Employee, compile the specific transaction codes used by each user and cross-reference against the SUR definition. Where SAP's classification relies on a broad interpretation of a vague SUR term, document the alternative interpretation and present it as your justified position.
Present Your Counter-ELP Formally
Produce a counter-Effective License Position document that presents your independently derived licence position, with supporting evidence for every variance from SAP's measurement. Present this to SAP's commercial team formally, in writing, and establish it as the starting point for commercial negotiation rather than SAP's measurement.
Pre-True-Up Preparation: A 90-Day Programme
The most effective way to manage SAP true-up risk is to conduct proactive preparation before SAP's measurement window opens. A 90-day pre-true-up programme — running your own measurement, cleaning your user data, and reclassifying boundary users before SAP can measure them — consistently produces better outcomes than reactive challenge after SAP has submitted its claim.
The programme begins with a self-assessment run of USMM at least 90 days before the expected SAP measurement date. This internal measurement identifies your current risk position: how many users are classified at each tier, where the boundary cases are, and where your largest exposure sits. With this data, your IT and procurement teams can take targeted action — deactivating users who no longer need system access, adjusting role assignments to reduce tier-triggering transaction access, and initiating the formal reclassification process for users whose classifications can be justified at a lower tier.
User access rationalisation before the measurement window is not "gaming" the true-up — it is sound licence management practice. SAP measures what you have at the point of measurement, and you are entitled to ensure that your system reflects your legitimate business requirements at that point. If a user genuinely does not need access to Professional-tier transactions, removing that access is appropriate. If a user was given access speculatively and does not use it, removing it reduces your exposure without affecting your business.
Key action: Run USMM at 90 days, 60 days, and 30 days before your expected SAP measurement date. The 90-day run establishes your baseline risk. The 60-day run measures the impact of your rationalisation actions. The 30-day run provides your final expected position. Going into SAP's measurement with a pre-prepared counter-position is the single most powerful true-up risk mitigation available.
Negotiating the True-Up Settlement
When SAP presents its true-up claim, the negotiation begins. SAP's initial commercial proposal is not its final position. The gap between what SAP initially demands and what a well-prepared customer ultimately pays is regularly 40-60% — reflecting the combination of measurement challenges, classification disputes, and commercial negotiation on the settlement price per unit.
SAP's commercial team operates within authority levels that determine how much discount they can offer without escalation. For large true-up settlements — above certain thresholds that vary by region and account team — SAP requires internal approval for discounts beyond the standard commercial terms. Knowing this escalation structure, and deliberately triggering it by creating a challenging negotiation position rather than accepting standard terms, often results in more favourable commercial outcomes because senior approval processes at SAP tend to take a longer-term account relationship view rather than a pure transaction view.
The timing of the true-up settlement matters commercially. SAP's financial calendar creates pressure points — end of quarter, end of half-year, and particularly end of financial year — where SAP's commercial teams are under pressure to close deals. A customer who is prepared to delay settlement into a pressure period, backed by a credible alternative position and documented challenge evidence, will consistently achieve better commercial terms than one who agrees quickly to SAP's initial timeline.
Where the true-up includes a significant Digital Access or indirect access component, the settlement negotiation should be integrated with the broader question of your SAP commercial roadmap. If you are planning to move to S/4HANA or considering RISE, the true-up settlement can be structured as part of a broader commercial agreement that includes transition credits, migration incentives, or preferential pricing on the forward contract in exchange for settlement of the historical exposure. SAP is frequently more flexible on historical claims when the customer is committing to a forward commercial relationship.
Our SAP audit defence service covers the full true-up process — from pre-measurement preparation and USMM analysis through challenge strategy and settlement negotiation. We've resolved over $200M in SAP licence exposure across dozens of enterprise clients. See our SAP licensing case studies for specific examples.
Start Your True-Up DefenceKey Takeaways
- SAP's true-up is a commercial process, not a compliance formality — every element from measurement to settlement is subject to challenge and negotiation.
- USMM's "highest activity" classification methodology systematically overstates user counts; independent analysis consistently identifies 20-35% reduction in the defensible baseline.
- Digital Access (indirect access) is the highest-risk true-up trigger for integrated enterprise landscapes — quantify document exposure before SAP does.
- Pre-true-up preparation — running your own USMM 90 days ahead, rationalising access, reclassifying boundary users — is the most effective risk mitigation available.
- SAP's initial true-up claim is typically 3-5x what the customer actually owes after forensic challenge; accepting without independent review is a systematic overpayment.
- Settlement timing matters — SAP's financial calendar creates commercial pressure windows that benefit well-prepared customers willing to delay agreement.
- True-up settlements can be integrated with forward commercial negotiations (RISE, S/4HANA migration) to achieve better overall terms than either transaction delivers independently.
Your Next SAP True-Up Is a Commercial Event. Treat It as One.
Don't accept SAP's measurement as final. Our independent forensic analysis, user reclassification expertise, and true-up negotiation track record consistently deliver materially better outcomes than unassisted customer negotiation.
Independent SAP Licensing Advisory
We are former SAP insiders working exclusively for enterprise buyers. Our advisory services cover audit defence, contract negotiation, licence optimisation, RISE advisory, and S/4HANA migration — all buyer-side, no SAP affiliation.
Book a Free Consultation →