Hosted Named User. Hosted Employee. Pick correctly.

Oracle Fusion Cloud ERP sells on two licensing metrics. Hosted Named User charges per named application user. Hosted Employee charges per employee at the entity regardless of application access. The list price per unit differs. The total cost depends on the access ratio.

The break even point sits near 60 percent of employees touching the application. Below that ratio, Hosted Named User costs less. Above that ratio, Hosted Employee costs less. The right choice depends on the module mix because Core Financials touches Finance and HCM touches every employee.

The two metrics

Oracle Fusion Cloud applications carry two named licensing metrics. Hosted Named User and Hosted Employee. Each metric has a counting rule, a list price, and a typical use case. The choice cannot be changed mid term without an order document amendment.

Hosted Named User

Counts each application user with credentials. The user list runs through the identity store. Inactive accounts must be deprovisioned to drop from the count. The metric works for applications used by a defined subset of the workforce.

Hosted Employee

Counts every employee at the entity regardless of whether the employee touches the application. The payroll record drives the count. The metric works for applications used broadly across the workforce.

The contractual definition

Hosted Employee includes every full time, part time, and temporary employee. Contractors are usually included if they hold a corporate identity. Subsidiaries inside the corporate group typically count.

The list price gap

Hosted Named User typically lists 2 to 4 times the Hosted Employee per unit. The gap reflects the assumption that fewer named users translate to lower coverage.

• Pick Hosted Named User. When the application serves a defined functional group such as Finance, Procurement, or Supply Chain.
• Pick Hosted Employee. When the application serves the broad workforce such as HCM, Expense, or Performance Management.
• Audit the access projection. Map every potential user to the metric before the order document signs.
• Pin the metric in the order document. The metric cannot be changed mid term without amendment cost.

The break even math

The break even point depends on the per unit list price ratio. The typical ratio is 3 to 1 across most modules. The break even sits where the Hosted Named User count multiplied by 3 equals the total employee count.

The math formula

Hosted Named User cost equals user count times Hosted Named User rate. Hosted Employee cost equals total employees times Hosted Employee rate. The two costs equal when user count divided by employee count equals the rate ratio.

The typical break even

At 3 to 1 list rate ratio, the break even sits at 33 percent of employees as users. Below 33 percent of employees holding accounts, Hosted Named User wins. Above 33 percent, Hosted Employee wins.

The discount adjusted break even

Real list ratios after volume and strategic discount typically run 4 to 1 or 5 to 1. At 4 to 1, break even sits at 25 percent. At 5 to 1, break even sits at 20 percent. The lower the ratio, the lower the break even.

The growth risk

Hosted Named User scales with user adds. Hosted Employee scales with workforce growth. The customer projects three to five years to pick the metric correctly.

List price ratio	Break even user count	Hosted Named User cost	Hosted Employee cost
2 to 1	5,000 users (50%)	5,000 x rate	10,000 x rate / 2
3 to 1	3,333 users (33%)	3,333 x rate	10,000 x rate / 3
4 to 1	2,500 users (25%)	2,500 x rate	10,000 x rate / 4
5 to 1	2,000 users (20%)	2,000 x rate	10,000 x rate / 5
6 to 1	1,667 users (17%)	1,667 x rate	10,000 x rate / 6

Module by module

The right metric varies by module because the user population varies by module. The buyer side team picks the metric at the module level, not at the application level. The mixed metric pattern is permitted under the order document.

Core Financials

General Ledger, Accounts Payable, Accounts Receivable, Fixed Assets, Cash Management. Typical user count is 2 to 8 percent of employees. Hosted Named User wins clearly.

Procurement and Supply Chain

Sourcing, Purchasing, Inventory, Order Management. Typical user count is 4 to 12 percent of employees. Hosted Named User typically wins, with edge cases for broad self service procurement.

Project Management

Project Costing, Project Billing, Project Portfolio Management. Typical user count is 6 to 15 percent of employees. Hosted Named User wins for most deployments.

Human Capital Management

Core HR, Talent Management, Compensation, Benefits, Workforce Management. Self service touches every employee. Hosted Employee wins clearly.

Performance Management and Goals

Employee self service for performance, goals, and learning. Touches every employee. Hosted Employee wins.

Expense Management

Travel and Expense self service. Typical user count is 20 to 80 percent of employees depending on industry. The break even runs case by case.

• Map every module to a user projection. Three year user count projection per module.
• Run the math per module. Hosted Named User cost versus Hosted Employee cost.
• Pin the metric per module. Each module carries its own metric in the order document.
• Document the projection assumptions. User count growth, workforce growth, organisational change.

Three buyer picks

Across 50 Fusion ERP reviews, three picks recur as the optimal metric mix for typical enterprise deployments. Each pick balances the Hosted Named User economics against the Hosted Employee predictability.

Pick one. Finance and Procurement on Hosted Named User

Core Financials, Procurement, and Project Management on Hosted Named User. The user count is low and the math holds at 3 to 1 ratio. Typical saving is 30 to 50 percent against the Hosted Employee default.

Pick two. HCM on Hosted Employee

Core HR, Talent, Compensation, Performance, Goals, and Learning on Hosted Employee. The user count approaches 100 percent of employees and the math reverses. Typical saving is 20 to 35 percent against the Hosted Named User alternative.

Pick three. Expense on the case by case math

Expense Management depends on the travel intensity of the workforce. Sales heavy companies run Hosted Employee. Office heavy companies run Hosted Named User. The break even sits where roughly 25 to 33 percent of employees submit expense reports.

Common traps

Four traps recur in Hosted Named User and Hosted Employee deployments. Each trap has a documented mitigation pattern. The customer that misses the trap absorbs cost rather than capturing saving.

Trap one. Inactive Named User accounts

Hosted Named User counts every active credential. Accounts left active after termination still count. The mitigation is the quarterly deprovisioning cycle tied to the HR offboarding workflow.

Trap two. Contractor counting on Hosted Employee

Oracle counts contractors as employees on most contracts. The customer with a large contractor population on Hosted Employee pays for the contractor count. The mitigation is the order document language defining who counts.

Trap three. Subsidiary inclusion

Hosted Employee typically counts every entity in the corporate group. The acquisition that adds 5,000 employees triggers a Hosted Employee true up. The mitigation is the acquisition carve out clause.

Trap four. Metric switch mid term

Switching from Hosted Named User to Hosted Employee mid term requires order document amendment. The amendment carries a credit reset and typically loses prior discount. The mitigation is the upfront pick that holds for the term.

1. Audit the user inventory quarterly. Active accounts, dormant accounts, terminated accounts, contractor accounts.
2. Reconcile against HR offboarding. Every termination triggers an Oracle account deprovisioning.
3. Document the acquisition carve out. Order document language that pauses true up for 12 months on acquisition.
4. Lock the metric for the term. Mid term switches lose discount. Pick correctly at signing.

What to do next

The checklist takes the buyer from the renewal letter to the executed strategy. The window is the renewal anniversary. The earlier the work starts, the wider the option set.

1. Audit the planned module list. Every Fusion module in scope for the deployment.
2. Project the user count per module. Three to five year projection by module.
3. Run the break even math per module. Hosted Named User versus Hosted Employee at the projected user count.
4. Pick the metric per module. Mixed metric pattern is permitted under the order document.
5. Negotiate the rate ratio. Push for 4 to 1 or 5 to 1 ratio at signing to move the break even.
6. Document the carve out clauses. Acquisition, divestiture, organisational change.
7. Pin the metric in the order document. Each module with its own metric and rate.
8. Run the order through Vendor Shield. Independent buyer side review before signing.

Frequently asked questions

How Redress engages

Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the Oracle service line, and the Software Spend Assessment.

Read the related Fusion Cloud ERP pricing guide, the Oracle ERP calculator, the Oracle Cloud ERP pricing, the ERP Cloud negotiation playbook, and the Oracle Knowledge Hub.