- The Fundamental Distinction
- SAP Named User Licence Types & Pricing
- SAP Engine Licence Types & Cost Drivers
- When Named User Licensing Creates Over-Licensing Risk
- When Engine Licensing Delivers Significant Savings
- Named User vs Engine: Head-to-Head Comparison
- How to Model TCO for Your Scenario
- Common Mistakes Enterprise Buyers Make
The Fundamental Distinction
SAP offers two fundamentally different approaches to licensing: Named User licensing (also called User pricing) and Engine licensing (usage-based metrics). Understanding this distinction is essential because choosing the wrong model can cost your organisation hundreds of thousands of pounds annually.
Named User licensing assigns a licence to a specific person. That user pays a fixed annual fee (typically £2,000–£6,000+ per user per year, depending on user type) regardless of how much or how little they interact with the system. Once assigned, the licence is tied to that individual. Over-licensing occurs when users are assigned licences they rarely use—a common scenario in large enterprises where user rosters are poorly managed and audited.
Engine licensing, by contrast, charges based on measurable usage metrics. Instead of "per user," you pay per transaction, per employee processed, per order line, per document posted, or similar countable events. A high-volume transactional process might be far cheaper on Engine licensing than on Named User. Conversely, a small number of highly interactive users might be cheaper under Named User licences.
"The difference between Named User and Engine licensing isn't academic—it's a multi-million-pound decision. Enterprise buyers who align the wrong model with their usage patterns have often overpaid for years before an audit forces a recount and reckoning."
SAP Named User Licence Types & Pricing
SAP offers several Named User licence tiers, each with different functionality and cost. Approximate list prices (as of 2026, subject to volume discount and negotiation) are:
Professional User
Full unrestricted access to SAP modules (Finance, HR, Supply Chain, etc.). Typically the most expensive Named User tier. Approximate list price: £4,500–£6,500 per year. Used for finance managers, procurement specialists, and others who need comprehensive system access.
Limited Professional User
Restricted access to specific modules or functionality; useful for power users in one domain (e.g., accounts payable specialist). Approximate list price: £2,800–£4,200 per year. Slightly cheaper than Professional but still a significant annual commitment per person.
Employee User
Read-only or minimal transaction capability. Commonly assigned to operational staff who need to view data or submit simple requests (time sheet entry, leave approval). Approximate list price: £1,200–£2,200 per year. Often the most mis-allocated licence type in large enterprises, assigned to casual users who might better fit a lower-cost model.
ESS/MSS (Employee/Manager Self-Service) User
Very restricted, purpose-built for employee self-service portals and manager approvals in HR. Approximate list price: £500–£1,200 per year. One of the cheapest Named User options, yet often not fully utilised because the portal experience is limited.
Developer User
Full access for developers and technical architects working in development or test environments. Typically not counted in production licensing but critical for development teams. Approximate list price: £3,000–£5,000 per year.
The core issue with Named User licensing is that you pay the full annual fee whether the user logs in once a year or 100 times a day. In large organisations with 2,000+ Named Users, even a 10% over-allocation (200 unused or under-utilised users) represents a £400,000–£1,000,000+ annual overspend.
SAP Engine Licence Types & Cost Drivers
Engine licences charge based on volume of measurable activity. Key types include:
HR Payroll Engine
Charged per employee processed in each payroll cycle. If your organisation processes payroll for 5,000 employees monthly, you might pay per employee per run. A typical mid-market rate: £8–£15 per employee per payroll cycle. For 5,000 employees monthly, that's £40,000–£75,000 annually—far cheaper than licensing 5,000 Named Users. But if your payroll is processed centrally by two HR staff, Named User licensing (2 × £2,500 = £5,000) would be vastly cheaper.
Order-to-Cash Engine
Charged per order line. High-volume transaction processing (e-commerce, bulk order entry) can run into thousands of order lines monthly. Typical pricing: £0.50–£2.00 per order line per month. A company processing 50,000 order lines monthly might pay £25,000–£100,000 annually—substantially less than licensing dozens of order-entry users at £3,000–£5,000 each. A company processing 500 order lines monthly might be better served by Named User licensing.
Financial Accounting Engine
Charged per document (GL posting, invoice, etc.). Common in large finance teams. Typical rate: £1–£5 per document per month. A finance team posting 10,000 documents monthly might pay £10,000–£50,000 annually; licensing five professional finance users at £5,000 each would cost £25,000, but often exceeds document processing needs for true high-volume scenarios.
Other Engines
Material Management, Fixed Assets, Procurement, and other modules have engine variants. All follow the same principle: you pay per unit of activity, not per user.
When Named User Licensing Creates Over-Licensing Risk
Named User licensing is most vulnerable to over-licensing in these scenarios:
- Organisational change without licence review. After a merger, restructuring, or departmental reorganisation, user lists quickly become stale. Employees leave; roles are rewritten. Yet licence assignments persist. We see enterprises with hundreds of "orphan" Named Users assigned to former employees or obsolete positions.
- Broad departmental access provisioning. IT departments often assign broad user groups (e.g., all operations staff) a Named User licence as a convenience, rather than conducting granular access control. Result: many users have licences they never use.
- Lack of usage monitoring. Without system audit logs or user activity reports, organisations cannot distinguish between heavy users and logged-in-once users. The licence fee is identical either way.
- Indirect access not managed. Employees who interact with SAP through other systems (e.g., a third-party procurement portal that writes to SAP) may trigger indirect access licensing rules, requiring additional Named User or Engine licences.
- Peak-load provisioning. During peak seasons, IT may temporarily license additional staff to handle volume surges. Once peak passes, those temporary licences are often not deactivated.
A typical SAP compliance audit uncovers 8–15% over-allocation of Named User licences in enterprise environments. For a 2,000-user estate, that's 160–300 excess licences, worth £320,000–£1,500,000+ in back-billing liability.
When Engine Licensing Delivers Significant Savings
Engine licensing excels in high-volume, low-interaction scenarios:
High-Volume Order Processing
An e-commerce business processing 100,000+ order lines monthly. Named User: licensing 30 order-entry staff at £3,000 per user = £90,000/year. Engine (Order-to-Cash): 100,000 lines × £1.00/line/month = £1,200,000/year. Engine would be more expensive. But at 20,000 lines/month with only 3 order-entry staff: Named User £9,000, Engine £240,000. Named User wins here.
Batch Payroll Processing
A payroll team of 4 people processing 8,000 employees quarterly. Named User: 4 users × £2,500 = £10,000/year. Engine (HR Payroll): 8,000 employees × £10/run × 4 runs/year = £320,000. Named User is vastly cheaper. Flip the scenario: 8 payroll staff processing 100,000 employees monthly. Named User: 8 × £2,500 = £20,000. Engine: 100,000 × £10 × 12 = £12,000,000. Engine is catastrophically more expensive. Volume and complexity drive the decision.
Centralised Document Entry
A finance shared service centre posting 500,000 GL entries monthly from a team of 20 staff. Named User: 20 × £4,500 = £90,000. Engine (Financial Accounting): 500,000 × £2/month = £1,000,000/year. Named User is far cheaper. But a smaller organisation posting 5,000 documents monthly with a team of 2 finance staff: Named User £9,000, Engine £120,000/year. Named User wins decisively.
The critical insight: Engine licensing saves money when the volume metric is very high relative to the number of people driving that volume. Conversely, Named User licensing saves money when transaction volume is moderate and staffing is lean.
Named User vs Engine: Head-to-Head Comparison
| Aspect | Named User Licensing | Engine Licensing |
|---|---|---|
| Cost basis | Per assigned individual (annual flat fee) | Per measurable transaction/unit (volume-based) |
| Audit risk | High—easily accumulate unused assignments | Moderate—requires accurate transaction counting |
| Flexibility | Easy to add/remove users (but high cost per user) | No per-user limit; scales automatically with volume |
| Indirect access exposure | High—may trigger additional licensing if not managed | Low—transaction counts are explicit |
| Best for low-interaction users | Poor fit (you pay full price for light usage) | Excellent (pay only for actual usage) |
| Best for high-volume transactions | Excellent (fixed cost regardless of volume) | Poor fit (costs can scale with transaction spike) |
| Typical audit discovery | 8–15% over-allocation of users | Under-counting of transactions (2–10%) |
| Mid-market typical cost / 1000 transactions/month | £9,000–£15,000 (assuming 4 users at £2,250 avg) | £1,000–£5,000 (depending on module) |
| Mid-market typical cost / high-volume batch (100k+/month) | £9,000–£15,000 (same regardless) | £100,000–£500,000 (scales linearly) |
How to Model TCO for Your Scenario
To determine which licensing model saves your organisation money, follow this five-step approach:
- Audit current user base. Export your current Named User assignments from SAP. Cross-reference against your HR system and active directory. Remove terminated employees, inactive accounts, and duplicates. Identify how many users are actually active (logged in at least once per quarter). This gives your true baseline.
- Classify users by type and interaction intensity. Segment your users: how many Professional, Limited Professional, Employee, ESS/MSS? For each segment, estimate usage intensity (daily/weekly/monthly/quarterly). Calculate the cost-per-interaction for each user. A user interacting 50 times/year costs £50–£130 per interaction (dividing annual licence by interaction count); a user interacting 500 times costs £5–£13 per interaction.
- Count transaction volumes for your key business processes. How many orders do you process monthly? GL documents? Payroll cycles and employee counts? For each process, determine the volume metric SAP uses (Order-to-Cash: order lines; HR Payroll: employees per cycle; Financial Accounting: documents). Work with your SAP administrator to pull transaction logs for the past 12 months.
- Price both scenarios. Calculate Named User: total active users × user-type average cost. Calculate Engine: transaction volumes × SAP's rate card for each metric. (You can request indicative pricing from SAP or your reseller; rates vary by module, geography, and contract terms.)
- Compare and build negotiation strategy. Which model is cheaper? By how much? If the gap is >20%, that's your leverage point with SAP. If you're currently overpaying under one model, SAP is often willing to switch you to the cheaper alternative, because it locks you into higher usage-based commitments. Use this comparison to negotiate discounts and contract terms that align with your actual usage.
Common Mistakes Enterprise Buyers Make
Based on our experience advising 500+ SAP customers over the past 11 years, we see these mistakes repeatedly:
1. Assigning Named User Licences Broadly Without Review
IT teams provision Named User licences as the default for any employee who "might need" SAP access. Over time, this creates thousands of unused or under-utilised assignments. The fix: implement quarterly licence reconciliation. Identify users who have logged in fewer than four times in the past year and either deactivate or convert to a lower-cost tier (ESS/MSS) if appropriate.
2. Not Distinguishing Indirect Access
Employees using portals, mobile apps, or middleware that read/write to SAP may trigger indirect access licensing obligations. A support portal used by 5,000 customers to check order status might inadvertently create an indirect access exposure. Conduct an indirect access audit and factor any exposure into your TCO calculation.
3. Failing to Use Cheaper User Tiers
Many employees assigned Professional User licences (£4,500–£6,500/year) only use ESS/MSS functionality (view timesheets, submit leave requests, check pay stubs). Downgrading them to ESS/MSS users (£500–£1,200) can save £3,000–£5,300 per person. A 2,000-user estate with 400 incorrectly-tiered users could save £1,200,000–£2,100,000 by correcting tier assignments.
4. Ignoring Seasonal and Peak-Load Opportunities
If your Named User costs spike during peak season (holiday hiring, year-end close), you may be better served by a hybrid model: Named Users for your core team, Engine licensing for peak-load surges. Negotiate seasonal flexibility into your contract rather than paying for licenses you'll use only eight weeks per year.
5. Not Negotiating for Cheaper Engine Rates
SAP's list rates for Engine metrics are not fixed. We have negotiated rates 20–40% below list, particularly for high-volume customers or multi-year commitments. If you're switching from Named User to Engine, use that shift as a negotiation opportunity. SAP prefers Engine licensing because higher volume locks you in; they'll often discount aggressively to win that deal.
6. Forgetting to Include Support and Maintenance Costs
Many organisations compare licence costs only. But SAP maintenance (typically 17–22% of licence cost annually) and support contracts scale with your licence count. Reducing Named Users from 2,000 to 1,800 saves not just £300,000–£900,000 in licence costs, but also £50,000–£200,000+ in annual maintenance. Factor the full TCO, not just licence fees.
Conclusion: Align Your Licensing Model to Your Usage Reality
Choosing between Named User and Engine licensing is not a technical decision—it's a financial one. The wrong choice can easily cost your organisation seven figures annually. Named User licensing suits organisations with stable, lean user bases and low transaction volumes. Engine licensing excels in high-volume, automated scenarios with few human handlers.
The majority of enterprises we advise could save 25–40% on SAP licensing costs simply by conducting a rigorous audit, correct user tier assignment, and honest comparison of both models. Start with a clear picture of your current state—who is licensed, how they use the system, and what your transaction volumes truly are. From there, negotiation becomes straightforward.
Need help auditing your SAP licensing position or modelling a switch between Named User and Engine? Contact us for a confidential assessment. Our team of former senior SAP executives has negotiated over $2.4 billion in software licensing savings and can help you identify where you're overpaying.