Oracle ERP Cloud Licensing Models: Hosted Named User vs Hosted Employee

Understanding Oracle ERP Cloud's Two Licensing Metrics

Oracle ERP Cloud operates on a subscription model, but the unit of measurement for that subscription varies depending on the module and how broadly it is deployed across your organisation. Oracle defines two primary metrics: Hosted Named User (HNU) and Hosted Employee (HE). Understanding the precise definition of each — and where Oracle applies them — is the foundation of any cost-controlled ERP Cloud deployment.

Unlike on-premises Oracle licensing, where you might licence by processor or by concurrent user, Oracle ERP Cloud assigns a named individual to each subscription unit. There are no concurrent user licences, no floating licences, and no shared login allowances. Every person who accesses the application must be counted and licensed.

Hosted Named User: Definition and Application

A Hosted Named User is an individual who is authorised to access a specific Oracle ERP Cloud service. The key word is authorised — not active, not logged in, but authorised. This means that anyone provisioned with a user account in the relevant Oracle Cloud module must be licensed, regardless of how frequently they use the system.

Key Characteristics of Hosted Named User

HNU subscriptions are the standard metric for Oracle ERP Cloud's core financial and operational modules. This includes Oracle Financials Cloud, Oracle Procurement Cloud, Oracle Project Portfolio Management Cloud, and Oracle Risk Management and Compliance Cloud. In each case, Oracle requires one HNU licence per provisioned user.

Oracle enforces a minimum of 20 HNU licences per subscription order, regardless of how many users your implementation actually requires. For smaller organisations, this minimum can represent a material cost floor. At list price, 20 HNU licences cost $150,000 per year. Negotiated enterprise pricing typically falls 30 to 45 percent below list, but the minimum applies regardless.

The standard list price for an Oracle ERP Cloud HNU is approximately $625 per user per month, equating to $7,500 per user per year. For a finance team of 100 users, the baseline subscription before any negotiation is $750,000 annually. Support fees on Oracle on-premises licences increase at 8 percent per year, but ERP Cloud subscriptions are subject to renewal price escalation that must be specifically negotiated at contract execution.

When HNU Is the Right Metric

Hosted Named User is appropriate when the group requiring access to a module is well-defined, professionally bounded, and significantly smaller than your total workforce. Finance teams, procurement specialists, project managers, and compliance officers are typical HNU user populations. These groups rarely exceed 10 to 20 percent of total headcount, which makes per-user licensing economical compared to workforce-wide metrics.

Hosted Employee: Definition and Application

The Hosted Employee metric is based on your organisation's total employee count rather than the count of named system users. Oracle defines an employee for this purpose as any full-time employee, part-time employee, temporary worker, or contractor whose employment data is processed or managed by the Oracle Cloud service in question.

The Hosted Employee metric is most commonly applied to Oracle HCM Cloud (Human Capital Management) and its constituent modules — Core HR, Payroll, Benefits, Talent Management, Learning, and Recruiting. It is also used for certain ERP self-service modules, including Oracle ERP Cloud Self-Service HR features and some Oracle SCM Cloud employee-facing components.

Key Characteristics of Hosted Employee

The defining characteristic of HE licensing is that it provides an enterprise-wide right to the relevant module functionality, scaled to your workforce size rather than to the number of named system users. For modules where access is expected across the entire organisation — such as employee self-service, expense management for all staff, or payroll processing that covers every worker — HE pricing can be significantly more economical than attempting to name every individual user.

Oracle's HE price points are lower per head than HNU, reflecting the broader user population and reduced per-user functionality expectations. The trade-off is that you pay for every employee, including those who will never actively use the system. A company with 5,000 employees pays for 5,000 HE licences even if only 4,000 submit expense reports and 1,000 are field workers without system access.

When HE Is the Right Metric

Hosted Employee pricing is typically the correct choice when adoption of a module is expected to be organisation-wide or when more than 50 percent of your workforce requires access. HR self-service, payroll processing, absence management, and benefits enrolment are natural candidates because every employee is effectively a user of these processes. Attempting to licence these capabilities by HNU almost always produces a higher total cost than HE pricing.

The Hybrid Approach: Combining Both Metrics

Oracle's ERP Cloud licensing model is not binary — the optimal solution for most medium-to-large enterprises is a hybrid structure that applies the correct metric to each module independently. Oracle explicitly permits this approach, and organisations that fail to negotiate a hybrid structure frequently overpay for one set of modules while under-licensing another.

A common hybrid structure for an integrated Oracle ERP and HCM deployment might look like this: Oracle Financials Cloud and Procurement Cloud licensed on a Hosted Named User basis for the 80 to 150 finance and procurement professionals who genuinely need full access. Oracle HCM Core HR, Payroll, and Employee Self-Service licensed on a Hosted Employee basis covering all 5,000 workers. Oracle Talent Management licensed as a separate HNU subscription for the 20 HR professionals administering the system, with a Hosted Employee add-on for the employee-facing functionality.

Five Factors That Drive the HNU vs HE Decision

1. User Population Breadth

The ratio of system users to total employees is the primary driver. If fewer than 20 percent of employees require access to a module, HNU is almost always cheaper. If more than 50 percent require access, HE pricing will typically be more economical. Between 20 and 50 percent, the decision depends on the specific module and negotiated per-unit pricing.

2. Module Functionality and Access Expectations

Some Oracle ERP Cloud modules inherently require access from a broad employee population. Oracle Expenses, for example, is designed for every employee who incurs business expenditure — restricting it to named users creates administrative overhead and potential under-licensing. Other modules, such as Oracle Risk Management Cloud or Oracle Financial Close and Consolidation, are genuinely limited to a small team of specialists and are correctly licensed on a HNU basis.

3. Headcount Growth Trajectory

Oracle subscriptions are typically structured for a fixed user count with annual true-up rights. For HNU subscriptions, adding users mid-term requires purchasing incremental licences at the pre-agreed rate. For HE subscriptions, the subscription already scales with headcount changes within a defined band. Organisations with significant anticipated headcount growth should model the compounding cost of HNU additions against a single HE metric that accommodates growth within agreed bands.

4. Contractor and Contingent Workforce Inclusion

Oracle's definition of a Hosted Employee typically includes temporary workers and contractors whose data is processed by the relevant module. Organisations with large contingent workforces must model whether these individuals should be included in the HE count. If contractors are licensed separately or excluded from scope, this can meaningfully alter the HE economics.

5. Negotiated Price Points

The economic boundary between HNU and HE is not fixed — it depends on the negotiated per-unit price for each metric. At list price, the HNU rate is approximately $625 per user per month. Oracle's HE rate varies by module but typically falls in the range of $3 to $12 per employee per month. At these list prices, the break-even point is roughly 50 to 200 named users per thousand employees, depending on the module. Negotiated pricing can shift this boundary significantly, and independent analysis of both metrics at achievable pricing is essential before committing to either structure.

Practical Optimisation Strategies

Conduct a Pre-Signature User Audit

Before signing any Oracle ERP Cloud subscription, map every individual who will need access to each module, segment by access level (full access versus read-only versus self-service), and produce an accurate count. Oracle's minimum user thresholds and bundling structures mean that an imprecise count at signature will persist for the entire subscription term — typically three to five years.

Negotiate Module-Level Flexibility

Request contract language that allows you to switch between HNU and HE metrics at renewal without penalty, and to add modules at the pre-agreed rate for any metric during the term. Oracle will resist this but will accept it in competitive procurement situations or where a significant multi-year commitment is on the table.

Model the 8 Percent Support Escalation Equivalent

Oracle Cloud subscription pricing is not subject to the same 8 percent annual support increase that applies to on-premises licences, but subscription prices do increase at renewal. Negotiate a cap on annual subscription price increases — typically 3 to 5 percent — as a contractual protection. Without this cap, Oracle's renewal pricing can represent a material unbudgeted cost at the end of a three-year term.

Review User Provisioning Quarterly

Oracle ERP Cloud's subscription cost is based on the number of provisioned users, not on active users. Employees who leave the organisation, change roles, or no longer require system access should be deprovisioned promptly. Quarterly user audits consistently identify 5 to 15 percent of licenced users who are no longer active — a reduction that directly reduces the HNU count at the next renewal point.

Common Mistakes and How to Avoid Them

The most frequently observed mistake in Oracle ERP Cloud subscription negotiations is applying a single metric — usually Hosted Named User — across all modules without evaluating whether a hybrid structure would reduce costs. This typically occurs because Oracle's sales process defaults to the metric that produces the highest revenue, and internal procurement teams lack the expertise to challenge it.

A second common mistake is accepting Oracle's minimum user counts without challenge. Oracle's standard quotation applies a 20-user minimum per module, which may exceed actual requirements for specialist modules with very limited user populations. In some cases, Oracle will accept a lower minimum for modules with small user groups when the overall deal value justifies it.

Third, organisations frequently fail to account for the cumulative cost of accessing multiple Oracle ERP Cloud modules. Each module is licensed separately, meaning that a user who requires access to both Oracle Financials and Oracle Procurement must be counted as an HNU for each module independently, unless the contract specifically bundles multi-module access into a single user metric.

Key Takeaways

Oracle ERP Cloud's two primary licensing metrics — Hosted Named User and Hosted Employee — serve different use cases and produce materially different costs depending on the breadth of system access required. The correct approach for most organisations is a hybrid structure that applies HNU to specialist modules with limited user populations and HE to broadly deployed modules where employee-wide access is expected.

The economics of each model depend on negotiated pricing, user population forecasts, and the specific modules in scope. Independent analysis before signature is the only reliable way to ensure that the licensing structure agreed at contract execution reflects actual usage patterns rather than Oracle's preferred commercial position.

For organisations approaching an Oracle ERP Cloud renewal or initial subscription negotiation, the combination of a pre-signature user audit, hybrid metric structure, and contractual price cap on annual escalation represents the minimum framework for cost-controlled deployment. Redress Compliance has structured hundreds of Oracle Cloud agreements across EMEA and North America, and independent advisory support consistently identifies 15 to 30 percent savings relative to Oracle's initial position.