SAP Licensing Based on Usage Metrics

SAP Licensing Based on Usage Metrics

Usage metrics, including the number of users, transactions, data volume, and revenue processed, heavily drive SAP’s software licensing.

IT leaders must understand these metrics to align SAP licensing with actual usage, control costs, and prevent unexpected expenses.

This article explains how SAP licenses are based on usage metrics, the different models (user-based, package-based, and cloud), and how to optimize contracts based on real consumption patterns.

SAP License Usage Metrics

SAP licensing ties costs to the amount of software usage. Usage metrics are the measurable units that SAP uses to quantify consumption.

Common metrics include the count of named users, transaction or document volumes, and resource capacity (like CPU cores or GB of memory). SAP’s philosophy is to charge for the value you derive – more usage generally means a higher license requirement.

For example, an SAP ERP system might be licensed for a maximum number of sales orders per year or a set number of named users.

If your business processes 20% more orders this year, that higher usage could push you into a higher licensing band or require additional licenses.

In essence, usage metrics ensure that a company using SAP extensively pays more than one using it lightly, aligning costs with utilization.

Read SAP License by User Role.

Key SAP Licensing Metrics & Models

SAP offers several licensing models, each defined by different usage metrics.

Below are the primary license types and their metrics:

1. Named User Licenses: The most common model – you pay for each individual user authorized in the system. Users are classified by role, which determines the price.
   • Professional User: Full access to SAP modules; the most powerful (and expensive) user type. For example, a Professional user license might list around $3,000 per user (one-time, plus ~22% annual support).
   • Limited/Employee User: Restricted to specific functions or self-service tasks. These cost less (often 50% or lower than a Professional user). For instance, an Employee Self-Service user license may be only a few hundred dollars.
   • Example: If you have 100 employees in SAP, but only 20 perform advanced tasks (requiring Professional licenses), and 80 have basic usage, you should assign the costly Professional licenses only to those 20 power users and use cheaper licenses for the rest.
2. Engine/Package Licenses: These cover SAP functional modules or add-ons (engines) that are licensed based on a specific usage metric, rather than per user. The metric is tied to the module’s purpose:
   • Technical Capacity: e.g., database size in GB or number of CPU cores for SAP HANA.
   • Business Transactions: e.g., number of sales orders, invoices, or material line items processed annually.
   • Master Data: e.g., count of master records like employees in a payroll system or customers in CRM.
   • Financial Metrics: e.g,. Annual revenue or spend is managed in an SAP industry solution.
   • Example: SAP Payroll might be licensed for up to 1,000 active employee records. If you have 900 employees, you’re within the licensed metric; if you grow to 1,100 employees, you exceed it and need to buy more. Similarly, an engine for Sales Management might allow 500,000 order line items per year – if your sales volume increases beyond that, you must extend the license.
3. Digital Access (Indirect Use): SAP’s Digital Access licensing covers usage by third-party applications, devices, or bots that indirectly interact with SAP. Instead of counting users, it tracks specific business documents created or processed through non-SAP systems (e.g., an e-commerce platform generating a sales order in SAP).
   • Document Count: For indirect scenarios, SAP tracks documents such as sales orders, purchase orders, invoices, and others. You purchase document packs (often in blocks of 1,000 documents per year).
   • Example: A company integrates a web store with SAP, generating 50,000 sales orders annually in SAP. Under Digital Access, they might license, for example, 50,000 documents per year (if they exceed this, additional document blocks must be purchased). This model ensures even automated or IoT-driven processes are licensed via measurable units.

Together, these models mean SAP licensing can be a mix of user-based and usage-based fees.

A typical SAP ERP contract includes a bundle of named users of various types, as well as specific engine metrics (for modules such as SAP HCM, Warehouse, etc.). It may also include digital access if third-party integrations are significant.

Read SAP Cloud Platform License Types.

Why Usage Metrics Matter

Usage metrics directly influence cost and compliance, so IT leaders need visibility into them:

• Cost Transparency: Knowing your usage metrics (e.g., the number of documents, users, or transactions) enables accurate budgeting. It prevents over-buying licenses you don’t need and highlights areas where you might be incurring extra costs.
• Optimized Spending: By aligning licenses with actual usage, organizations can avoid paying for unused software. For instance, if only 60% of purchased user licenses are in active use, there’s an opportunity to reduce or reallocate licenses and save on maintenance fees.
• Avoiding Non-Compliance: Misunderstanding usage can lead to shortfalls. If your usage exceeds what you’re entitled to (e.g., more users or transactions than licensed), you risk non-compliance. SAP frequently audits its customers; if an audit finds that you are over the limits, the company will issue an unexpected bill (plus back maintenance) to “true up” the licenses. Understanding metrics helps avoid such nasty surprises.
• Scalability & Flexibility: Modern businesses grow and change rapidly. Usage-based licensing enables you to scale up as needed, but you must monitor metrics to determine when to make adjustments. Conversely, if usage drops or a project is retired, you may scale down licenses (where contractually possible) to avoid overspending.

SAP S/4HANA Cloud and Usage-Based Pricing

With the shift to the cloud (e.g., RISE with SAP S/4HANA), SAP has introduced new metric models, such as Full Usage Equivalents (FUE).

FUE is a weighted metric that aggregates different user types in cloud subscriptions:

• In S/4HANA Cloud, instead of buying a fixed number of each user type, customers purchase a pool of FUEs. Each user role consumes a certain fraction of an FUE based on its intensity. For example, a heavy “Core Use” business user might count as 1 FUE, a lighter “Developer” or occasional user might count as 0.5 FUE, and so on. SAP then totals your FUE consumption across all users.
• Minimum Commitments: SAP often requires a minimum FUE purchase for cloud deals (e.g., a baseline like 35 FUEs for a standard mid-sized deployment). This ensures a minimum revenue for SAP, even if your actual usage is lower initially.
• Subscription Metric: In cloud licensing, the cost is typically per user per month, but those users are underpinned by the FUE (Fully Utilized Entity) model. For example, a Professional cloud user might be roughly €90 (~$100) per user per month, whereas a limited-function user might be around €50 per month. These subscription fees cover software use, hosting, and support. For IT leaders, the key is that even in the cloud, monitoring usage is vital. If your user count or data consumption grows, it will increase subscription costs at renewal or trigger a move to a higher subscription tier.
• Comparison to On-Premises: On-premises SAP licenses are perpetual (a one-time fee, followed by annual support). In the cloud, it’s pay-as-you-go (annual subscription). However, both require tracking metrics: on-prem to stay compliant with contract limits and cloud to manage ongoing costs and avoid over-provisioning.

Monitoring Usage and License Optimization

SAP provides tools such as the USMM (User Measurement) and LAW (License Administration Workbench) to help customers measure usage across their systems. These tools consolidate user counts, classifications, and engine metrics to compare against your entitlements.

Actively monitoring your SAP usage is essential for both compliance and cost optimization.

Internal license audits or reviews should be conducted regularly (at least annually, if not quarterly) to catch mismatches early:

• User Classification Reviews: Ensure that each SAP user is correctly assigned to the proper license type in the system. If a user isn’t assigned a specific license type, SAP’s measurement will default them to the highest category (Professional) by default – unnecessarily inflating your compliance count. One global company discovered that dozens of casual users were listed as professionals in SAP’s records simply because nobody had updated their status; this oversight would have cost hundreds of thousands of dollars if not corrected. Regularly review user roles to downgrade those who don’t need full access (e.g., switch a former power user now doing a limited task to a cheaper license). This “right-sizing” can yield significant savings.
• Engine Usage Tracking: Keep an eye on metrics like employee counts, order volumes, or database size if you have engine licenses. It’s wise to track these in your SAP system or via reports. For example, suppose your sales department is onboarding a big new customer and expects a jump in order volume. In that case, you should forecast whether this could exceed your licensed transactions for the SAP Sales & Distribution module. Proactive tracking gives you time to purchase additional capacity or negotiate a new license band before you’re out of compliance.
• Leverage SAP’s Measurement Tools: On-premise SAP administrators should run USMM (in each system) and then aggregate the results with LAW. These tools will show you the current license consumption. For cloud services, SAP often provides admin dashboards to monitor usage (like user counts, data storage, API calls, etc.). IT teams should regularly review these usage dashboards to ensure they align with the terms of your contract.
• Optimize Indirect Usage: Indirect digital access can be a silent cost creep. To optimize and identify where third-party systems connect to SAP. Sometimes, simple tweaks like batching transactions can reduce the number of document creations. In one case, a company’s CRM was creating SAP sales orders in real-time for each small event. By switching to batch processing and consolidating some transactions, they significantly reduced the document count, stayed within their licensed indirect usage, and saved fees.

By diligently monitoring, companies can also prepare for SAP’s official audits with confidence. Rather than scrambling when SAP announces an audit, you’ll already know your usage profile and any areas of concern.

Companies that practice continuous license management often discover opportunities to negotiate better terms. For example, suppose you notice that a certain engine is consistently underutilized (perhaps you licensed 1000 employees for SAP Payroll but only have 800 active).

In that case, you might negotiate to reallocate that value to another needed area in your next contract true-up, rather than paying maintenance on the unused portion.

Risks of Exceeding License Entitlements

Ignoring usage metrics can lead to serious financial exposure. SAP will not automatically prevent you from using more than you purchased – your systems continue to run, and excess usage only becomes apparent later.

But when it does, SAP will demand compliance fees. Key risk scenarios include:

• True-Up Costs: If an official audit or annual measurement finds you exceeded your entitlements, SAP will require you to purchase the excess at the list price (often with backdated maintenance). These unbudgeted bills can be huge line items. It’s not uncommon for a CIO to discover that, due to growth or oversight, they are 20% over on a pricey engine license – translating to a six or seven-figure surprise cost.
• Compliance Penalties: While SAP typically resolves compliance issues by selling you additional licenses rather than taking legal action, being significantly out of compliance could strain your SAP relationship and leverage in negotiations. At extremes, it could even risk a breach of contract. Most importantly, you lose negotiation leverage when SAP knows you must buy additional licenses to continue operating legally.

To illustrate the financial impact of exceeding usage metrics, consider these examples:

In each case, a growing business metric (more data, more headcount, more transactions) led to an under-licensed situation. The remedy is expensive and often at unfavorable rates.

The takeaway: staying within contracted metrics is critical. If you know you’ll exceed them, address the issue with SAP in advance to potentially negotiate better pricing, rather than waiting for an audit.

Recommendations

• Proactively Track Usage: Implement regular internal license audits. Monitor user counts, transaction volumes, and other metrics via SAP’s tools or third-party solutions. Early detection of usage spikes gives you time to react.
• Align License Types with Roles: Match each user to the appropriate license type. Avoid “one size fits all” licensing – a casual user should not be required to consume a Professional license. Update user classifications whenever roles change; unclassified users will count as expensive licenses by default.
• Optimize and Reassign Licenses: Identify inactive or low-activity users and reassign or eliminate their licenses. Reclaim licenses from departed employees promptly. This governance can typically reduce unnecessary spending by 10-20%.
• Plan for Growth in Contracts: During contract negotiations, discuss your business growth plans. If you expect significant increases in employees or transactions, negotiate volume tier discounts or flexible terms (e.g., temporary bursts or a growth allowance) upfront. It’s easier to get favorable rates ahead of time than after you’ve exceeded limits.
• Negotiate Metric Definitions: Ensure the definitions of metrics in your SAP contract match your business reality. For instance, if “annual revenue” is a metric for a license, clarify if that means gross revenue, a specific division, etc. Ambiguity can lead to disputes or unexpected charges in the future. If a metric doesn’t suit your usage pattern, see if SAP offers alternative metrics (some engines allow choice of metric).
• Consider Digital Access vs. Named Users: For third-party integrations, analyze the cost of the Digital Access document model versus licensing all external users individually. Depending on your scenario, one may be cheaper. SAP’s Digital Access Adoption Program can sometimes provide discounts or credits – explore those with SAP if indirect usage is significant.
• Utilize License Management Tools: Leverage tools or services that can automatically analyze your SAP usage and provide recommendations for optimizations. Some SAM (Software Asset Management) tools can simulate SAP’s audit counting, helping you stay compliant and continuously optimize license assignments.
• Stay informed about changes: SAP licensing policies are constantly evolving (e.g., new cloud metrics, support fee increases). Keep up with SAP’s updates and industry analysis. For example, be aware of the shift toward cloud subscriptions and how this might impact your future licensing strategy or costs. An informed team can anticipate and adapt rather than react.
• Cross-Functional Governance: Treat SAP licensing as an ongoing governance topic involving IT, procurement, finance, and HR. Regular meetings to review usage and upcoming needs will help ensure there are no surprises. This collaborative approach means when you onboard new projects or acquisitions, everyone considers the SAP license impact upfront.
• Consult Experts When Needed: If your organization lacks internal expertise, consider engaging SAP licensing specialists or consulting firms. They can provide benchmarks, negotiation insights, and audit defense strategies that save money. The cost of advice is often far less than the cost of a licensing mistake.

FAQ

Q1: What does “license by usage metrics” mean for SAP?
A: It means SAP ties its software licenses to measurable usage factors – you pay based on how much you use the system. This could be the number of users, the number of transactions or documents, or other units, such as data volume. It ensures companies pay in proportion to their value and usage, rather than a flat fee, regardless of size.

Q2: What are the common SAP usage metrics that affect licensing?
A: Common metrics include the count of named users (categorized by type), transaction or document counts (e.g., the number of sales orders or invoices processed), master data counts (e.g., the number of employee or material records), and technical metrics such as database size or server cores. Some SAP products use industry-specific metrics (e.g., revenue or production output). These all define the limits of what you’ve paid for.

Q3: How does SAP measure and track our usage against our licenses?
A: SAP provides built-in measurement tools. For on-premise systems, administrators run the USMM tool to gather user and usage data in each system, then use LAW to consolidate that across the landscape. These tools report how many users of each type you have and how much you’ve consumed on each metric, which is then compared to your license entitlements. In cloud services, SAP automatically monitors usage (including user counts, memory usage, etc.) and may provide dashboards for you. Additionally, SAP audits customers periodically – during an audit, they will either request your USMM/LAW reports or run their own scripts to verify usage.

Q4: What happens if our usage exceeds the licensed amount?
A: If you use more than you paid for – say more users are active than you have licenses for, or transaction volume is above your entitlement – you are technically out of compliance. In practice, nothing will stop immediately, but an audit or annual check will reveal the overuse. At that point, SAP will require you to purchase the shortfall, usually at the list price. For example, if you only licensed 100 users but 120 are using the system, you’ll need to buy 20 more licenses retroactively. It’s often more expensive to true-up after the fact, so it’s best to monitor and purchase additional licenses proactively as needed.

Q5: Can we switch to a usage-based licensing model entirely?
A: Many SAP contracts already blend both named user licenses and usage-based (engine) licenses. With the move to the cloud (SAP S/4HANA Cloud or RISE), the model is more consumption-driven (based on user subscriptions and FUE metrics). If you are on traditional on-prem licensing, you can’t unilaterally change your metric model without re-negotiating with SAP – you’re bound by the metrics defined in your contract. However, you can optimize within that model (e.g., adjust the user license mix and drop unused components). When major changes, such as migration to S/4HANA or a contract renewal, occur, you have an opportunity to adopt more usage-based or flexible models. Always evaluate the cost impact of any model change with care (for some organizations, a pure usage model could increase costs; for others, it may decrease them).

Q6: What is SAP’s Digital Access, and do we need it?
A: Digital Access is SAP’s licensing model for indirect usage (when non-SAP systems or devices interact with SAP). Instead of requiring a named user license for, say, every web customer or sensor, SAP charges by the number of documents created. You “need” Digital Access if you have significant third-party integrations creating SAP business objects without traditional SAP user logins. Many older SAP customers have alternative arrangements for indirect use in their contracts; new SAP S/4HANA customers are generally expected to use Digital Access. It can simplify indirect licensing, but you should compare its cost vs. the old model. If your digital transaction volumes are high, it may become a significant cost element, which you can manage by controlling those integrations or purchasing sufficient document packs.

Q7: How do cloud subscriptions (SAP S/4HANA Cloud) handle usage metrics?
A: In SAP cloud subscriptions, you typically pay per user on a monthly or annual subscription basis. Those subscriptions are often tiered by user type (similar to Professional, Limited, etc.) and underpinned by the Full Usage Equivalent (FUE) model that weights different users. Additionally, cloud contracts might include other usage limits (for example, a certain amount of storage or API calls per month might be part of the package). If your usage increases (with more users or higher resource consumption), you typically adjust the subscription at the next renewal or purchase additional capacity. The good news is that cloud licenses are somewhat elastic – you can scale up by adding more subscriptions. The bad news is that if you vastly exceed contracted amounts (such as user counts), you may still face a true-up or have to immediately add licenses mid-term. Always monitor your cloud usage via SAP’s admin console to avoid any overage issues.

Q8: How can our organization reduce SAP licensing costs using usage metrics?
A: Start by analyzing your current usage deeply. Identify inactive users or those with access far beyond their needs – downgrading or removing these saves money. Optimize engine use: if an engine’s metric is significantly underutilized, see if you can remove it or negotiate a lower level in the next agreement. Ensure integrations aren’t unintentionally driving up metrics (e.g., unnecessary data syncs creating documents). Regularly review usage trends – if a particular metric is growing, address it promptly (perhaps by archiving data to limit database growth or by training users to use the system efficiently). Also consider alternatives: for instance, if your SAP system is used heavily only by part of the workforce seasonally, you could explore whether a more flexible licensing arrangement is possible (SAP typically doesn’t do short-term licenses easily, but in some cases, third-party managed services or cloud could be an answer). Finally, engage with SAP using data – if you can show them an accurate picture of your lower usage in certain areas, you might be able to negotiate the removal or replacement of licenses you don’t need, rather than blindly renewing everything.

Q9: How often should we review SAP usage and licenses?
A: It should be a regular process. Ideally, perform an internal license review quarterly or at least bi-annually. This doesn’t have to be as heavy as an official audit; it can be a simple report check of user counts and key metrics. You want to catch any drift in usage early. Certainly, before any SAP true-up or annual renewal cycle, conduct a thorough review to ensure you enter negotiations with clear data. Additionally, whenever there’s a major business change, such as an acquisition, divestiture, new SAP module deployment, or a significant increase in transactions, you should reassess licensing immediately. Some companies also schedule a yearly third-party SAP license assessment as a best practice to get an outside perspective and ensure nothing is missed.

Q10: Can we negotiate SAP license terms based on usage metrics?
A: Yes, you can and should. When you have good data on your usage, you have leverage to negotiate contract terms. For example, if you know you currently use 800 employees on an engine licensed for 1000, you might negotiate a lower band (if you don’t plan to grow much) to save cost. Alternatively, if you foresee growth, negotiate volume discounts for the additional usage upfront (like price breaks when you exceed certain user counts or transaction volumes). You can also negotiate definitions – ensuring, for instance, that “orders” exclude test or training transactions in the metric count. Another approach is to negotiate swap rights (exchanging one type of license for another) if your usage patterns change, thereby providing flexibility. SAP is often open to discussions, especially during big renewal or migration deals, to ensure the agreement fits your needs – but they won’t offer concessions if you don’t ask. Enter discussions with detailed usage reports and a clear case for any changes you request.

Read more about our SAP Licensing Services.

Schedule a meeting with us to discuss our SAP Advisory Services.

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit