SAP charges for package or engine licences in addition to user licences — covering specific modules and components measured by business metrics rather than per user. This guide explains how engine licensing works, the common metrics (employees, revenue, cores, memory), pricing structures, tracking and optimisation strategies, audit pitfalls including indirect access, and actionable recommendations for CIOs and licence managers.
SAP package licences (also called engine licences) cover specific SAP functional modules or technical components that are not covered by standard named user licences. Unlike user licences tied to people, engine licences measure usage based on a specific unit of measure — typically a business metric like employee count, revenue throughput, or technical capacity.
For example, if you use SAP's Payroll module, you pay for that module based on the number of employees processed — not how many HR staff log in. The SAP licensing model separates these two dimensions: user licences (who accesses SAP) and engine licences (what SAP functionality is consumed at what scale).
| Dimension | User Licences | Engine / Package Licences |
|---|---|---|
| What's Measured | Individual people who log in | Business volume or technical capacity consumed |
| Metric Examples | Named User, Professional, Limited Professional | Employees, revenue, GB of HANA memory, cores |
| Pricing Model | Per user per year (or perpetual + maintenance) | Per metric unit — tiered or flat (perpetual + maintenance, or cloud subscription) |
| Scope | Covers access to SAP system | Covers specific module/component functionality |
| Audit Focus | User type classification, over-provisioning | Metric overuse, unlicensed modules, indirect access |
One-time licence fee plus ~22% annual maintenance. The engine metric is fixed at purchase — if your business grows beyond the licensed metric, you must purchase additional entitlements.
Engine metrics may be factored into the overall subscription fee. Usage tiers are defined in the order form. Exceeding the tier triggers a true-up or upgrade discussion.
Smaller engines might cost tens of thousands of dollars; large enterprise engines (SAP HCM Payroll, HANA database) can cost hundreds of thousands or even millions.
SAP uses a variety of metrics to licence its packages. Understanding the specific metric for each engine in your contract is essential — it defines how usage is counted and when additional purchases are triggered.
| Metric Type | What It Measures | Typical Modules | Pricing Notes |
|---|---|---|---|
| Total Employees | Number of employee records in the system | HCM, Payroll, Benefits, Time Management | Tiered pricing — cost per employee decreases at higher bands |
| Annual Revenue / Spend | Monetary throughput processed by the module | Sales & Distribution, Procurement, Ariba | Often banded by revenue ranges (e.g., $0–$500M, $500M–$1B) |
| Processor / Cores | Server CPU cores running the component | SAP HANA, NetWeaver, integration engines | Per-core pricing; virtualisation rules apply |
| Memory (GB) | Amount of memory allocated to the database | SAP HANA (Runtime, Platform Edition) | Per-GB pricing; tiers based on total memory allocation |
| Documents / Transactions | Number of business documents processed | Digital Access, EDI, e-commerce integrations | Per-document pricing; volumes measured annually |
| Records / Objects | Number of managed records or objects | Master Data Governance, Product Lifecycle Mgmt | Flat or tiered per record count |
Most engine metrics use tiered pricing where the per-unit cost decreases as volume increases. Understanding your current tier — and the thresholds that trigger the next tier — is critical for cost planning.
Definitions of "employee," "revenue," or "document" may differ from your internal understanding. Always refer to SAP's contractual definitions, not assumptions. For example, SAP may count contingent workers as "employees" for HCM licensing.
On-premise engine licences carry ~22% annual maintenance. A $500K engine licence costs $110K/year in maintenance alone — a significant ongoing commitment that should factor into total cost of ownership analysis.
Engine licences span SAP's entire portfolio — from core ERP modules to infrastructure components and industry solutions. Below are the most common engines enterprises encounter:
| Engine / Package | Metric | Description | Cost Indicator |
|---|---|---|---|
| SAP HCM / Payroll | Employees | Covers HR, payroll processing, benefits, time management for entire workforce | $$$ — scales with headcount |
| SAP HANA Database | Memory (GB) or Cores | In-memory database engine; Runtime (bundled with apps) or Platform (standalone) editions | $$$$ — memory-based pricing can be very expensive |
| SAP Digital Access | Documents | Covers indirect/digital access — transactions created by non-SAP systems (APIs, bots, web portals) | $$ — per-document; volumes can grow rapidly |
| SAP S/4HANA (select engines) | Various | Certain S/4HANA modules have engine components alongside user licences | $$–$$$$ — depends on module |
| SAP Ariba | Managed Spend | Procurement platform licensed by the value of spend managed through it | $$$ — banded by spend volume |
| SAP SuccessFactors (select) | Employees | Cloud HR modules may include engine components for workforce size | $$ — per employee per year |
| SAP Integration Suite | Messages / API Calls | Integration platform licensed by message volume or API call counts | $$ — tiered by volume |
| SAP Master Data Governance | Records | Licensed by number of master data records managed | $$ — per record tier |
Effective engine management requires routine tracking of usage metrics and proactive adjustment — not just reactive responses during audits.
Use SAP's built-in LAW (Licence Administration Workbench) and measurement programmes periodically — not just when SAP requests them. Schedule quarterly measurement runs to understand your current consumption against each engine entitlement.
Create and maintain a master list of all engine licences, their metrics, contracted quantities, current consumption, and renewal dates. This single view prevents surprises and enables proactive planning.
Establish internal alerts when engine consumption reaches 80% of licensed capacity. This gives you time to negotiate additional entitlements or optimise usage before exceeding limits.
If an engine is consistently under-utilised compared to your licensed amount, negotiate a reduction at renewal. Paying maintenance on unused capacity is a direct waste — reclaim it or swap it for entitlements you actually need.
If usage is nearing or exceeding the licensed limit, engage SAP proactively through a licence extension or contract adjustment. Negotiating before an audit gives you far more leverage than responding to an audit finding.
Mergers, acquisitions, headcount changes, revenue growth, and new integration projects all directly affect engine metrics. Build licence impact assessment into your M&A and project planning processes.
SAP licence audits pay special attention to engine licences. These are the most common pitfalls that generate compliance findings and unexpected costs:
Using more of a product than licensed — or using a product with no licence at all — is the most common finding. SAP will require you to purchase the shortfall, often with retroactive fees. A company that grew from 5,000 to 8,000 employees without updating their HCM engine faces a compliance gap of 3,000 employees.
If external systems (web portals, e-commerce platforms, RPA bots, third-party apps) create, read, or modify SAP records without licensed users, SAP considers this "indirect access." Without proper Digital Access licensing, an audit will charge for those documents — often at significant cost.
Disagreements about what counts as an "employee" or how "revenue" is calculated are common. SAP's definition in the contract may differ from your internal HR or finance definitions. Always use SAP's contractual definitions when measuring compliance.
Modules that were activated for testing, proof-of-concept, or accidentally enabled can trigger compliance findings even if actual business use is minimal. SAP's position is that activation equals usage.
For HANA-based engines, allocating more memory to the database than licensed — even if not fully utilised — can create a compliance gap. SAP measures allocated memory, not just consumed memory.
After mergers or acquisitions, the combined entity's employee count, revenue, or transaction volumes often exceed the original licence entitlements. If not addressed promptly, the acquirer inherits a compliance liability.
If you expect business growth, secure a higher metric band upfront or a predictable growth tier. A pre-negotiated escalation path is significantly cheaper than an unexpected true-up at audit time.
When negotiating broader SAP deals (S/4HANA migration, RISE with SAP, etc.), include engine entitlements in the overall package. SAP is more likely to offer favourable engine pricing as part of a larger commitment.
SAP's fiscal year ends in December. Quarter-end (March, June, September) and especially year-end negotiations give you more leverage as SAP teams work to close deals.
If you have engine entitlements you no longer use, negotiate to swap them for engines you do need. SAP may agree to reallocate the licence value — particularly if it avoids a maintenance reduction.
During negotiations, ensure the contract explicitly defines how each metric is measured. Ambiguous definitions create audit risk. Get written confirmation of what counts as an "employee," how "revenue" is calculated, and how HANA memory is measured.
Include contract terms that specify how over-consumption will be handled — grace periods, notification requirements, and pricing for true-ups. This prevents SAP from applying list pricing to audit findings.
Maintain an inventory of all engine licences and their metrics. Regularly compare actual usage to entitlements. Set internal alerts as usage approaches limits so you can respond proactively — not reactively during an audit.
Perform self-audits focusing on engines. Run measurement reports and check if any engine usage exceeds entitlements. Address gaps before SAP's official measurement request arrives.
If you expect business growth, include buffer or flexible terms for engine metrics during contract negotiations. Securing a higher metric band or predictable growth tier upfront is cheaper than an unexpected true-up.
Turn off or remove SAP modules you aren't using or aren't licensed for. This prevents accidental activation and audit findings. If a licensed engine is no longer needed, consider retiring it to save on maintenance.
Map out all integrations with SAP. If non-SAP systems create SAP transactions (sales orders via e-commerce, automated entries via RPA), quantify this indirect usage and ensure you have appropriate Digital Access licensing.
Major business changes — M&A, restructuring, new projects, headcount changes — directly affect engine metrics. Build licence impact assessments into your change management and project planning processes.
Ensure every engine metric is clearly defined in your contract. Ambiguous definitions create audit risk. Get written clarity on what counts as an "employee," how "revenue" is calculated, and how technical metrics are measured.
Use each contract renewal as an opportunity to right-size engine entitlements. Remove engines you no longer use, adjust metric bands to reflect actual consumption, and negotiate better terms based on your usage data.
Engine licences and their maintenance are often a hidden cost centre. Ensure your total cost of ownership analysis explicitly breaks out engine costs so leadership understands the full SAP investment.
SAP engine licensing is complex and high-stakes. An independent SAP licensing advisor can identify over-licensing, negotiate better terms, and prepare your audit defence — without the conflicts of interest that come with SAP-affiliated consultants.
User licences cover who can access SAP — they're tied to named individuals. Engine (package) licences cover what SAP functionality is consumed and at what scale — they're measured by business metrics like employee count, revenue, memory, or document volumes. Most SAP deployments require both user licences and engine licences.
SAP uses the Licence Administration Workbench (LAW) and annual measurement programmes. SAP typically requests measurement results once per year. The measurement output shows your actual consumption against each metric, which SAP compares to your contracted entitlements to identify any shortfall.
Yes, but SAP is typically reluctant to reduce entitlements (and the associated maintenance revenue). Your strongest position is to demonstrate with data that the engine is genuinely under-utilised, negotiate the reduction as part of a broader deal, and engage well before the renewal deadline. Independent advisory support helps in these negotiations.
SAP Digital Access is a licensing model that covers "indirect access" — transactions created in SAP by non-SAP systems (APIs, web portals, bots, third-party integrations) rather than named users. It's measured by document type and volume, making it effectively an engine/package licence. Many organisations are caught out by Digital Access in audits because they didn't realise their integrations required separate licensing.
SAP HANA is licensed based on memory (GB) allocated to the database. There are two editions: Runtime (bundled with SAP applications, restricted to running SAP workloads only) and Platform (standalone, for non-SAP workloads too — significantly more expensive). SAP measures allocated memory, not consumed memory, so over-provisioning your HANA instance can create a compliance gap even if the data doesn't fill the allocated space.
Not entirely. Cloud subscriptions (including RISE with SAP) typically bundle some engine metrics into the subscription fee, but the metrics still exist and are measured. Your order form will specify usage limits for employee counts, document volumes, storage, etc. Exceeding those limits triggers additional charges. The metric mechanics are similar — they're just wrapped into the subscription model.
SAP will require you to purchase additional entitlements to cover the shortfall. The pricing applied is typically current list price (not the discounted rate you originally negotiated), and SAP may seek retroactive maintenance fees. This is why proactive monitoring and early negotiation are far more cost-effective than audit-triggered remediation.
Mergers and acquisitions often increase employee counts, revenue throughput, and transaction volumes — all of which can push engine consumption beyond licensed limits. SAP contracts are typically non-transferable, so the acquiring entity may need to negotiate new entitlements or true-ups for the combined organisation. Build licence assessment into your M&A due diligence.
In some cases, yes. SAP may agree to reallocate licence value from unused engines to engines you need — particularly if the alternative is a maintenance reduction. This is a negotiation, not an automatic right, and works best when done as part of a broader contract discussion. Independent advisory can help structure these swap proposals.
At minimum, conduct a full engine review annually aligned with SAP's measurement cycle. Perform quarterly spot-checks for high-risk engines (HANA memory, employee-based HCM, Digital Access volumes). Major business events — M&A, restructuring, new integrations — should trigger an immediate engine impact assessment.
Share your SAP estate details. We'll assess your engine licence positions, identify compliance gaps and over-licensing, and build an optimisation and negotiation strategy — typically within 48 hours.