A CIO and ITAM guide to understanding Oracle's Hosted Named User, Hosted Employee, and consumption-based licensing metrics. How each model works, why Oracle assigns them, and how to optimise cost and compliance across your Fusion Cloud portfolio.
This article is part of our comprehensive Oracle Fusion Applications SaaS Licensing and Negotiation Guide. For related topics, see Cloud Apps Licence Compliance: Right Quantity and Roles and Negotiating Oracle SaaS Contracts.
Oracle's Fusion Cloud applications, spanning ERP, HCM, CRM, and SCM, operate on a subscription licensing basis rather than perpetual licences. Each cloud service is sold under a defined metric set by Oracle. Customers cannot arbitrarily choose a licensing model for a given service. Understanding these models is critical for CIOs to anticipate costs, manage compliance, and negotiate contracts effectively.
Oracle's subscription models generally fall into two broad categories: user-based licensing and consumption-based licensing. In all cases, subscriptions are time-bound (often 1 to 3 year terms) and include support as part of the subscription fee.
| Model Category | How It Works | Common Applications | Key Risk |
|---|---|---|---|
| User-Based: Hosted Named User (HNU) | Each individual with login credentials must be licensed. Licences are not shared or pooled | ERP Financials, Procurement, SCM, CRM Sales | Excess active accounts vs licensed quantity |
| User-Based: Hosted Employee (HE) | Every employee in scope is counted, regardless of whether they use the system directly | HCM Core HR, Payroll, Employee Self-Service | Under-reporting employee headcount at true-up |
| Consumption-Based: Records | Charged per block of data records (e.g., 1,000 customer records) | Customer Data Management, Marketing Cloud | Data growth exceeding purchased blocks |
| Consumption-Based: Transactions | Measured by orders processed, invoices generated, or revenue value | Commerce Cloud, Billing, Tax Filing | Volume spikes driving unexpected cost increases |
| Consumption-Based: Storage/API | Specialised metrics for integration, analytics, or environment-based pricing | Integration Cloud (message packs), Analytics | Overconsumption of committed blocks |
Oracle predetermines the licensing metric for each cloud service based on how the product delivers value. The metric is set in Oracle's price list and your ordering document. You cannot switch a per-employee service to per-user or vice versa. Your strategy should focus on choosing the right combination of services that fit your organisation's usage profile. If a metric does not suit your needs, consider alternative Oracle products or even third-party solutions. Always model out the 3 to 5 year cost under the given metric, factoring in growth.
User-based models tie subscription cost to the number of people in your organisation who use, or benefit from, the software. Oracle uses two specific terms in contracts for these arrangements, and confusing them is a common source of budget surprises.
A Hosted Named User licence is assigned to a specific individual authorised to access an Oracle Cloud service. Each distinct user requires a subscription. This is an authorisation-based model: every person with access credentials is considered a licensed user, regardless of whether they actively use the system daily. Licences are not shared or pooled. Two employees cannot share one login to save costs.
If 50 sales reps need Oracle Sales Cloud, you must subscribe to 50 HNU licences. When a user leaves and is replaced, you can reassign their licence to the new hire, but you cannot have more than 50 active users at once on 50 licences.
This model is common for modules where usage is limited to specific roles: Oracle Fusion ERP Financials (accountants and analysts), SCM systems (supply chain planners), or CRM modules (sales representatives). It offers fine-grained control, as you pay only for employees who need access. However, it requires diligent user management. Inactive accounts should be removed promptly to avoid paying for unused licences.
The Hosted Employee metric is essentially an enterprise-wide subscription based on the total number of employees. Oracle defines "employee" broadly, typically including full-time, part-time, temporary workers, and often contractors or external agents whose data is processed by the system. You pay for every employee in scope, not just the daily users.
This metric is commonly applied to Oracle's HCM cloud modules and other services that provide value proportional to workforce size. Core HR and payroll services are priced per employee because every employee's data is stored and managed, even if only HR staff log in. If you have 3,000 employees and Oracle HCM Core HR is priced at $X per employee per month, you pay for all 3,000.
The advantage is simplicity: you do not need to track named users or worry about adding individual licences as you expand. The challenge is cost predictability for large organisations. As your workforce grows, subscription costs grow linearly.
| Dimension | Hosted Named User (HNU) | Hosted Employee (HE) |
|---|---|---|
| Who is counted | Each individual with login credentials | Every employee in scope (FT, PT, temp, contractors) |
| Typical modules | ERP Financials, Procurement, SCM, CRM Sales | HCM Core HR, Payroll, Employee Self-Service |
| Cost driver | Number of system users | Total workforce headcount |
| Scaling behaviour | Granular: pay per user added | Linear: grows with every new hire |
| Compliance risk | Excess active accounts vs licensed quantity | Under-reporting employee headcount at true-up |
| Key negotiation lever | Start lean, add users over time | Lock in volume discount for large headcount |
Oracle Fusion Cloud ERP often uses Hosted Named User licences for modules such as Financials or Procurement. A finance team of 25 using Fusion Financials Cloud under HNU at $600 per user per month costs 25 x $600 x 12 = $180,000 annually. If the team grows or other departments start using the system, additional user subscriptions are required. In contrast, Oracle Fusion Cloud HCM for Core HR might require the Hosted Employee metric. A firm with 5,000 employees paying $5 per employee per month for Core HR costs 5,000 x $5 x 12 = $300,000 annually. Although perhaps only 50 HR staff use the system actively, the pricing reflects the value of managing all 5,000 employees' data.
Beyond per-user models, Oracle offers certain SaaS subscriptions on a consumption basis. Pricing is based on the volume of measurable usage rather than the number of users. These metrics align with services where value is directly correlated with data processed or transactions handled.
| Consumption Type | How It Works | Example Application | Cost Behaviour |
|---|---|---|---|
| Records-Based | Charged per block of data records (e.g., 1,000 customer records stored in the system) | Customer Data Management, Marketing Cloud | 50,000 records at $100 per 1,000 records/month = $5,000/month. Scales with database growth |
| Transaction Volume | Measured by orders processed, invoices generated, or monetary value processed | Commerce Cloud (revenue metrics), Tax Filing (per return), Billing Cloud (per invoice) | Higher activity incurs higher subscription fees. Seasonal spikes can drive unexpected costs |
| Storage / API Calls | Specialised metrics for integration, analytics, or environment-based pricing | Integration Cloud (message packs), Analytics Cloud (data volume) | Consumption in predefined blocks. Commit to base level, purchase additional blocks if exceeded |
Consider a field service management cloud charging $0.50 per work order completed. At 100,000 service tickets per year, the annual cost is $50,000. If volume spikes to 150,000, costs rise 50%. Some contracts still require committing to a base block. Consumption metrics are fair when usage fluctuates, but budgeting becomes challenging if usage can surge unexpectedly. Build buffer into your contract (e.g., license for 120,000 if you expect 100,000) and negotiate unit pricing for additional consumption in advance.
Oracle determines the licensing metric for each cloud service based on who or what drives the value received from that service. Customers cannot choose a different metric for a given product. Understanding the rationale helps CIOs anticipate Oracle's pricing logic and negotiate more effectively.
| Rationale | How It Works | Implication for Buyers |
|---|---|---|
| Value Alignment | Applications providing enterprise-wide value (e.g., HR systems benefiting every employee) use employee metrics. Specialist tools used by select teams use per-user metrics to align pricing with the expected breadth of usage | If a module's metric does not match your usage pattern (e.g., per-employee for a tool only 50 people use), the economics may not work. Evaluate alternatives |
| Simplicity and Fairness | Standardising the metric ensures customers pay a consistent rate proportional to a clear factor. Prevents attempts to license a widely-used system with just a handful of users | Oracle maintains pricing integrity across its customer base. Expect limited flexibility to change a service's metric |
| Product Structure | Each Oracle SaaS product has licensing rules baked in. Modules for self-service by all employees are sold per-employee; back-office functions are per-user | A few products offer tiered models, but these are exceptions. Map your needs to the available metrics before committing |
Since you cannot change a service's metric, the strategy for CIOs is to choose the right combination of services that fit your organisation's usage profile. If a metric does not suit your needs, consider alternative Oracle products or even third-party solutions. Always model out the 3 to 5 year cost under the given metric, factoring in growth. If Oracle's per-employee pricing for a module seems expensive for your scenario, compare with other solutions on the market. Oracle can sometimes offer different packages or adjust pricing when it knows you have alternatives.
Each licensing model presents distinct challenges for budgeting and compliance. Understanding these differences allows IT procurement teams to build appropriate governance processes and avoid expensive surprises at audit or renewal.
| Model | Cost Control | Compliance Risk | Key Governance Action |
|---|---|---|---|
| Hosted Named User (HNU) | Scales with actual users, which is efficient if usage is limited. If many employees eventually require occasional access, per-user costs can quickly escalate. Forecast how many users might need the system over time | Enabled user accounts must never exceed the licensed quantity. Oracle's contract holds you responsible for excess usage, potentially requiring back-billing or a true-up purchase | Audit active accounts quarterly. Verify the number of enabled user accounts does not exceed your licensed quantity. Strong Identity and Access Management processes are essential |
| Hosted Employee (HE) | Very predictable if workforce size is stable, but essentially a site licence for the enterprise. Large organisations pay for everyone, including those who rarely interact with the software | Contracts may require annual certification of employee numbers or include clauses to adjust fees if the count exceeds a threshold. A 10% leeway is standard before triggering a contract adjustment | Clarify "employee" definitions. Confirm whether contractors, temps, and subsidiary staff count. Ensure HR and IT collaborate to report accurate figures |
| Consumption-Based | This can be the trickiest: usage may vary month to month or year to year. Implement monitoring to avoid exceeding contracted amounts. Build buffer into your contract | Oracle provides admin consoles to view usage reports. Unexpected spikes should prompt early discussions with Oracle about expanding at a negotiated rate | Set up internal dashboards or alerts to track usage statistics. Treat it like a cloud usage bill. No one wants a surprise overage |
Audit active accounts quarterly: verify the number of enabled user accounts does not exceed your licensed quantity. Sync with HR processes: ensure joiners, leavers, and movers are reflected in Oracle access within 30 days. Clarify "employee" definitions: confirm whether contractors, temps, and subsidiary staff count under your agreement. Negotiate headcount buffers: request at least 10% growth tolerance before triggering a true-up. Review at renewal: reductions in employee count usually cannot reduce fees until the next renewal cycle.
Enterprises moving to Oracle Fusion SaaS often struggle with the complexity of mixed licensing models. It is common to have a mix of user-based and consumption-based services within a single Oracle portfolio: Oracle ERP (user-based), Oracle HCM (employee-based), and Oracle Integration or Analytics Cloud (consumption-based) running simultaneously.
| Challenge | What Goes Wrong | How to Address It |
|---|---|---|
| Budget alignment across models | Aligning different metrics in budgets and monitoring compliance across departments is inherently complex. A sales manager may not realise adding 10 new reps has licensing cost implications. An HR exec may not consider that hiring 200 staff increases the HCM bill at renewal | Cross-functional communication is the single most important governance measure. Every department head who can trigger a usage increase must understand that cloud services are metered |
| Pricing transparency gaps | Oracle's pricing transparency can be limited: official price lists exist but are complex, and discounts are heavily negotiated. The list price per user or per 1,000 records is rarely what enterprises pay | Understanding the models helps you push for volume discounts on a data-driven basis. Benchmark against Oracle's peer deals to establish fair pricing |
| True-up and contract inflexibility | Once you commit to a certain quantity for a 3-year term, you generally cannot reduce that commitment until the end of the term. Cloud subscriptions are "use it or lose it" on an annual basis | Negotiate downward flexibility clauses. Request at least the right to revisit metrics at renewal. Some agreements allow a degree of reduction at renewal without penalty |
| Departmental cost attribution | Each new hire, each new data record, and each new transaction carries a cost implication. Without clear internal cost attribution, departments over-consume without accountability | Implement chargeback or showback models that allocate Oracle SaaS costs to consuming departments. Make the cost of each new user or transaction visible to budget owners |
The shift from perpetual licences to cloud subscriptions fundamentally changes cost dynamics. In the perpetual world, adding users to an existing licence was often "free" until the next audit. In the cloud world, every new hire, every new data record, and every new transaction carries a direct cost implication. Cross-functional communication is the single most important governance measure. Every department head who can trigger a usage increase must understand the metered nature of cloud services and the financial impact of their decisions.
| # | Recommendation | Detail |
|---|---|---|
| 1 | Inventory your needs per service | Before signing any Oracle SaaS contract, map out which roles or data will use each service. Determine if a service's metric aligns with your usage. If a module is per employee, ensure you truly need it enterprise-wide. This prevents unnecessary over-commitment to an expensive metric |
| 2 | Leverage Oracle's price metric definitions | Obtain Oracle's official definitions for metrics like "Hosted Named User" or "1,000 Records" from the proposal or ordering document. Understanding the fine print (what counts as a record or an employee) will help avoid compliance surprises. Clarify any ambiguities with Oracle in writing |
| 3 | Right-size the initial subscription | For user-based services, start with the number of users you realistically need on day one. You can usually add users later. For consumption metrics, purchase a baseline covering current usage with some growth room. Avoid wildly overestimating unless a bulk purchase yields big discounts you are sure to utilise |
| 4 | Implement strong access governance | Collaborate with HR and IT security to ensure prompt removal or adjustment of Oracle SaaS access when employees leave or change roles. Regularly review user lists versus active staff. This governance ensures you are not paying for licences for former employees or unnecessary accounts |
| 5 | Monitor consumption actively | For services with consumption metrics, set up internal dashboards or alerts to track usage statistics. Treat it like a cloud usage bill. If you see trends of increasing usage, initiate conversations with Oracle early about expanding at a negotiated rate |
| 6 | Anticipate growth and changes | Plan for company growth, acquisitions, or divestitures that may occur during the subscription term. If you expect a major increase in users or data, negotiate terms that accommodate that now. If a business unit might be divested, be cautious about long, inflexible commitments |
| 7 | Educate stakeholders on cloud metering | Ensure department heads understand that cloud services are metered. A sales VP should know that each new hire incurs an additional cost for a Sales Cloud subscription. Building this awareness helps the business align operational decisions with IT cost implications |
| 8 | Benchmark alternatives | If an Oracle SaaS metric appears costly for your scenario, compare with other solutions on the market. Oracle can sometimes offer different packages or adjust pricing when it knows you have alternatives. Use comparisons to drive better negotiations |
| 9 | Review contracts for flexibility | Look for clauses allowing adjustments to quantities. Some agreements allow a degree of reduction at renewal without penalty or include provisions to convert metrics if Oracle's packaging changes. Negotiate at least the right to revisit metrics at renewal |
| 10 | Engage licensing expertise | Oracle licensing is complex, and cloud models are no exception. Independent licensing specialists can identify gotchas: prerequisite modules that must be licensed for each user, ways to optimise counts, and ensure your understanding of user vs consumption models is accurate before committing to a multi-year deal |
The single highest-return activity for any Oracle SaaS customer is conducting a thorough internal audit before renewal. Clean data and accurate counts give you the strongest negotiating position. Verify active user accounts against HNU licences. Confirm employee definitions exclude out-of-scope categories. Measure actual consumption against purchased blocks. This work typically takes days, not months, and the savings are measured in hundreds of thousands of dollars.
A global manufacturer with 8,000 employees was licensing Oracle Fusion ERP (HNU for Financials, 120 users), Oracle HCM (Hosted Employee, 8,000), and Oracle Integration Cloud (message packs, consumption-based). At renewal, Oracle proposed a 15% across-the-board price increase.
Working with independent advisors, the IT team discovered: 28 ERP user accounts were assigned to employees who had left the company, the HCM contract counted 800 contractors who should not have been in scope, and the Integration Cloud was consuming only 60% of purchased message packs.
| Service | Issue Found | Action Taken | Annual Savings |
|---|---|---|---|
| Fusion ERP (HNU) | 28 user accounts assigned to departed employees | Reduced from 120 to 92 HNU licences | $201,600 |
| Fusion HCM (HE) | 800 contractors counted who should not have been in scope | Renegotiated employee definition to exclude contractors | $48,000 |
| Integration Cloud | Consuming only 60% of purchased message packs | Right-sized message packs down 35% | $42,000 |
| Total annual savings | $291,600 | ||
This $291,600 in annual savings was achieved before negotiating any discounts on unit pricing. The savings came entirely from right-sizing: removing departed employees from HNU licences, renegotiating the employee definition to exclude contractors, and reducing unused Integration Cloud message packs. Understanding Oracle's subscription metrics and conducting a thorough internal audit before renewal is the single highest-ROI activity for any Oracle SaaS customer. Clean data and accurate counts give you the strongest negotiating position.
Hosted Named User (HNU) licences are assigned to specific individuals who access the system: you pay only for people with login credentials. Hosted Employee licences charge for every employee in your organisation (or in scope), regardless of whether they use the system directly. HNU is common for specialist tools like ERP Financials. Hosted Employee is common for enterprise-wide services like HCM Core HR.
No. Oracle predetermines the licensing metric for each cloud service based on how the product delivers value. The metric is set in Oracle's price list and your ordering document. You cannot switch a per-employee service to per-user or vice versa. Your strategy should focus on choosing the right combination of services that fit your usage profile.
Oracle typically defines "employee" broadly to include full-time, part-time, and temporary workers, and often contractors or external agents whose data is processed by the system. The exact definition varies by contract, so it is critical to review and clarify this in your ordering document. Negotiate exclusions for categories that should not be in scope, such as third-party contractors managed by separate systems.
For user-based models, you can typically add more users at any time by purchasing additional subscriptions. However, reductions are usually not allowed until renewal. For employee-based models, a true-up typically happens at renewal: if your headcount has increased, Oracle will require a subscription adjustment. A standard 10% growth tolerance is common before triggering mid-term adjustments. Negotiate how increases are handled upfront.
Consumption-based subscriptions charge based on measurable usage rather than user count: data records stored, transactions processed, API calls made, or message packs consumed. Oracle sells consumption in predefined blocks. You commit to a base level and purchase additional blocks if exceeded. Monitoring actual usage against contracted amounts is critical to avoid overage charges at true-up.
Start with a thorough internal audit: verify active user accounts against HNU licences, confirm employee definitions exclude out-of-scope categories, and measure actual consumption against purchased blocks. Right-sizing before renewal is the single highest-ROI activity. Engage independent advisors to benchmark pricing and negotiate better terms across all metrics simultaneously.
Generally no. Once you commit to a certain quantity for a 3-year term, you cannot reduce that commitment until the end of the term. Cloud subscriptions are "use it or lose it" on an annual basis. This is a major shift from the perpetual licence world. Negotiate downward flexibility clauses during initial contracting. Some agreements allow a degree of reduction at renewal without penalty, or include provisions to convert metrics if Oracle's packaging changes.
Oracle often sets minimum user counts for enterprise subscriptions. Many services require at least 10 or 20 users, ensuring a baseline spend regardless of your actual team size. For consumption-based services, Oracle sells in predefined blocks (e.g., blocks of 1,000 records or message packs). You commit to a minimum base level. Always verify minimums in your ordering document before signing.
Not sure whether your Oracle Cloud subscriptions are right-sized? Our independent advisors help CIOs verify user counts, validate employee definitions, benchmark pricing, and negotiate better terms at renewal.
Oracle Contract NegotiationIndependent subscription optimisation. Metric analysis. Compliance governance. Contract negotiation. 100% vendor-independent. Fixed-fee engagements.