Oracle Fusion ERP Cloud is sold on two subscription metrics that produce very different bills for the same deployment. The choice is a commercial decision, not a technical one. Read the comparison before the renewal quote lands.
Oracle Fusion ERP Cloud is priced on either a Hosted Named User metric or a Hosted Employee metric. The two count completely different populations and rarely cost the same. This guide covers the mechanics, the audit posture, and the buyer side moves.
Oracle Fusion ERP Cloud is a subscription service. The bill scales by one of two count metrics, not by modules alone. The metric is fixed in the ordering document and is hard to change mid term.
A Hosted Named User is any individual authorized to use the service, whether or not they log in during a given month. The count includes employees, contractors, and third parties with access. Oracle defines the service in its cloud service descriptions and hosting policies.
A Hosted Employee count covers all employees and contingent workers in the organization, regardless of whether they touch ERP. It is the same family of broad metric Oracle applies across Fusion ERP Cloud and adjacent Fusion suites.
The right metric depends on the ratio of ERP users to total employees. A narrow user base favors Named User. A wide one can favor Hosted Employee at a low per employee rate, as set out in Oracle's applications pricing.
Four inputs drive the comparison. Get them on one page before Oracle quotes.
Illustrative metric comparison for a 5,000 employee organization
| Scenario | ERP users | Total employees | Lower cost metric |
|---|---|---|---|
| Finance only rollout | 350 | 5,000 | Hosted Named User |
| Procurement plus finance | 1,200 | 5,000 | Depends on rate |
| Self service expenses for all | 5,000 | 5,000 | Hosted Employee |
| Shared services center | 600 | 5,000 | Hosted Named User |
Oracle reviews active user records against the contracted Named User count. Cloud services are measured continuously, so a true up can arrive at renewal rather than through a formal audit letter.
Rapid user provisioning, an acquisition, or a module expansion all flag the account. Oracle compares provisioned identities against entitlement. The Oracle Software Investment Guide sets the policy framing.
Deactivate dormant accounts before the measurement window. Map each active identity to a contracted entitlement. A clean identity baseline is the single best defense against a surprise true up.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Choose the metric that prices the realistic three year user curve at the lowest total cost, then lock the per unit rate and the count basis in writing. Do not let Oracle pick the metric for you.
If ERP touches finance and procurement only, Hosted Named User is almost always cheaper. Govern the list actively to stop creep.
If every employee uses self service expenses or approvals, model Hosted Employee at the best rate. The simplicity can also cut administrative overhead.
The standard reseller pitch is that Hosted Employee is the simpler and safer metric because it removes user counting and audit risk. We disagree. In roughly six of ten Fusion ERP Cloud deals Fredrik Filipsson modeled, Hosted Employee priced higher for narrow finance rollouts because it taxes the entire workforce for a system a few hundred people use. The buyer side move is to model both metrics against the real three year user curve, force Oracle to quote each one, and only then choose. Simplicity is worth paying for, but not at a 30 percent premium you never measured.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
Oracle picks the metric that bills the most. The buyer side job is to model both before signature, because after signature the metric is locked and the leverage is gone.
Oracle Fusion ERP Cloud is sold on either a Hosted Named User metric or a Hosted Employee metric. Hosted Named User counts authorized individuals. Hosted Employee counts the whole workforce regardless of ERP use.
It depends on the ratio of ERP users to total employees. Narrow finance and procurement rollouts usually favor Hosted Named User. Deployments where every employee uses self service can favor Hosted Employee at a low rate.
Rarely without a new ordering document. The metric is fixed in the subscription contract, so it should be chosen before signature. Switching usually requires a renewal or a renegotiation.
Any individual authorized to use the service, including employees, contractors, and third parties. The count is independent of whether the person logs in during a given month.
Oracle measures cloud usage continuously and compares active identities against the contracted count. A true up can arrive at renewal rather than through a formal audit letter.
Deactivate dormant accounts before each measurement window and map every active identity to an entitlement. A clean identity baseline is the strongest defense against an unexpected charge.
Yes. Employee facing modules such as self service expenses and approvals push the comparison toward the Hosted Employee metric because they widen the real user base.
Model both metrics against the real three year user curve before Oracle quotes. The metric choice alone can move the annual subscription by 20 to 35 percent on identical scope.
Oracle ULA exit moves, audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, applications, and cloud estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
The cheapest Oracle ERP Cloud metric is the one you modeled before Oracle did. Most buyers model it after the quote, when the metric is already locked.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Oracle pricing shifts, audit patterns, and negotiation levers from live engagements. No vendor spin.
