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 Oracle's own definitions, who lands in each population, the crossover arithmetic, and how the metric gets switched underneath you.
One counts permissions and the other counts people. That is the whole difference, and it is the reason the same deployment produces two very different invoices. The metric is fixed in the ordering document and is hard to change mid term.
Both definitions live in Oracle's cloud service descriptions and in the definitions section of the applications price list. Read the definitions that govern your order date, not a summary, and not a slide.
A Hosted Named User is an individual authorized by you to use the service, whether or not that individual is actively using it at any given time. Authorization is the test, not activity.
That single word does most of the damage. A user provisioned in March and never used again is still authorized in December. The count includes employees, contractors and third parties who hold access.
A Hosted Employee count covers the workforce, not the users. Oracle's standard wording reaches full time, part time and temporary employees, and in the same breath the agents, contractors and consultants supporting your internal business operations.
Whether any of them ever open Fusion ERP Cloud is irrelevant to the count. That is not a loophole or an aggressive reading. It is the design of the metric, and it is why the metric can be cheaper.
Because one metric cannot price both shapes of customer. A shared services center with 400 finance users and 30,000 employees and a manufacturer where everyone files expenses are not the same deal.
Offering both lets Oracle meet each one. It also lets Oracle quote whichever produces the larger number, and there is no rule requiring the account team to show you the other.
Work it out person type by person type, because this is where the number is really set. The table below is the one we build in the first week of an ERP metric engagement.
Treat the uncertain rows as questions to put in writing rather than as answers. Where we say confirm, it is because the treatment varies by ordering document and by price list version.
Who counts, under which Oracle ERP Cloud metric
| Person or account | Hosted Named User | Hosted Employee | What to do about it |
|---|---|---|---|
| Employee who uses ERP daily | Counts | Counts | The only row both sides agree on |
| Employee who never opens ERP | Does not count | Counts | This single row is the entire economics of the choice |
| Part time and temporary employees | Only if authorized | Counts | Oracle's employee wording reaches part time and temporary staff |
| Contingent workers supporting internal operations | Only if authorized | Usually counts | The wording reaches agents, contractors and consultants. Name the exclusions |
| Outsourced accounts payable team at a provider | Counts, they are authorized | Expect Oracle to say it counts | Outsourcing the work does not obviously remove the people. Settle it before signature |
| Employees of a majority owned affiliate | Counts if authorized | Depends on the affiliate definition | Read how your master agreement defines affiliate, then read it again |
| Divested entity on a transition services agreement | Counts | Unclear without a clause | The most common gap we find. Write the transition population into the order |
| External auditors with read access | Counts | Does not count | Small numbers, but they are named and they are often forgotten |
| Suppliers using a supplier portal | Confirm in writing | Does not count | Supplier populations dwarf employee ones. Never assume this one |
| Customers using self service | Confirm in writing | Does not count | Same exposure, same answer. Get it stated on the order |
| Integration and service accounts | Ask in writing | Does not count | Rarely addressed until an audit, and then it is expensive to argue |
| AI agents acting on their own schedule | Unsettled, ask in writing | Does not count | See our Fusion AI agents pillar for the argument |
Look again at the second row. An employee who never opens ERP is free under Hosted Named User and fully chargeable under Hosted Employee. Every dollar of the comparison sits in that gap.
So the first number to establish is not a price. It is the share of your workforce that will genuinely touch ERP over the term, including the modules you have not deployed yet.
Companies outsource accounts payable expecting the license count to fall with the headcount. Under Hosted Named User it does not, because the provider's staff still need authorized access to process your invoices.
Under Hosted Employee it may not either, because the standard wording reaches contractors and agents supporting internal business operations. Ask the question before you sign the outsourcing contract, not after.
At the point where your ERP user ratio equals the ratio of the two rates. That is the whole calculation, and almost nobody runs it in the room.
Write it out. Hosted Named User costs users times the named user rate. Hosted Employee costs employees times the employee rate. Named User is cheaper while users divided by employees stays below the employee rate divided by the named user rate.
The crossover ratio implied by the two rates you are quoted
| Employee rate as a share of the named user rate | Crossover user ratio | In a 5,000 employee company | Below that many ERP users |
|---|---|---|---|
| One fifth | 20 percent | 1,000 ERP users | Named User is cheaper |
| One eighth | 12.5 percent | 625 ERP users | Named User is cheaper |
| One tenth | 10 percent | 500 ERP users | Named User is cheaper |
| One fifteenth | 6.7 percent | 335 ERP users | Named User is cheaper |
| One twentieth | 5 percent | 250 ERP users | Named User is cheaper |
Take that table into the meeting. When Oracle gives you two rates, you can state the crossover out loud before the account team has finished the slide, and the conversation changes shape immediately.
Get these on one page before Oracle quotes anything. Three of them are yours and only one belongs to Oracle.
Use illustrative rates of $2,400 per named user per year and $240 per employee per year, a ten to one ratio, so the crossover sits at 10 percent. Replace both with the rates you are actually quoted.
The company has 5,000 employees growing 5 percent a year. The only thing that differs between the two scenarios is whether self service expenses gets rolled out to the wider workforce.
Illustrative three year comparison, 5,000 employees, crossover at 10 percent
| Scenario | ERP users | Employees | User ratio | Named User cost | Employee cost | Cheaper metric |
|---|---|---|---|---|---|---|
| Year one, finance and procurement only | 350 | 5,000 | 7.0 percent | $840,000 | $1,200,000 | Named User by $360,000 |
| Year one, expenses opened to everyone | 600 | 5,000 | 12.0 percent | $1,440,000 | $1,200,000 | Employee by $240,000 |
| Year three, finance only | 380 | 5,513 | 6.9 percent | $912,000 | $1,323,120 | Named User by $411,120 |
| Year three, expenses rolled out | 900 | 5,513 | 16.3 percent | $2,160,000 | $1,323,120 | Employee by $836,880 |
Same company, same rates, same year. The answer flips entirely on one deployment decision that the finance team usually treats as a user experience question.
That is the real finding. You are not choosing a metric. You are choosing a metric conditional on a rollout plan, so put the rollout plan in front of whoever signs.
Oracle discounts the metric it wants you on. Quote one at 45 percent off list and the other at 15 percent, and the crossover moves without a word being said about it.
So insist on both quotes at the same time, from the same approval level, with the discount percentage stated on each. Then compute the crossover from those two numbers and say it in the room.
Quietly, at renewal, inside a quote that looks like a discount. The metric is an attribute of the ordering document, and a new ordering document can carry a different one without anybody calling it a change.
We see four versions of the same move. None of them require anything improper from the account team, which is exactly why they work.
You hold a named user order for financials. Oracle quotes a suite or enterprise package at renewal, and the package is priced per employee because that is how the packaged SKU is built.
The headline is more modules for a similar number. The unit changed underneath the number, and your bill is now tied to headcount for the rest of the term.
Adding a single employee facing module is the most common trigger we see. Self service expenses, time entry or self service procurement all imply that the whole workforce touches the system.
Once that is true, Oracle has a clean argument that the population, not the user list, is the right basis. The module is small. The consequence is the entire subscription.
One order can carry both metrics at once, and that is where double counting hides. A base priced per employee alongside additional modules priced per named user means you may be paying twice for the same people.
Ask for a line by line metric column on both the expiring order and the renewal quote. Put them side by side. If Oracle will not produce that mapping, you have learned something.
Write it in before signature, because after signature you are asking for a favor. Two sentences do most of the work.
None of these are exotic. They are ordinary contract hygiene that almost nobody asks for, and the module and rate detail behind them sits in our ERP Cloud modules and pricing guide.
It looks like a renewal conversation, not an audit letter. Oracle measures cloud usage continuously and compares what it sees against what you contracted, so the correction usually arrives as a repriced renewal.
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.
This is the operational consequence buyers discover late. Under Hosted Named User the evidence is your identity management system, and the test is authorization rather than activity.
Under Hosted Employee the evidence is your HR reporting, which means an ERP contract obligation now sits with the HR team. Decide who owns the evidence before signature, and tell them.
Deactivate dormant accounts before the measurement window and map each active identity to a contracted entitlement. A clean identity baseline is the single best defense against a surprise true up.
Note what that sentence implies. Only one of the two metrics can be defended this way, because you cannot deactivate an employee to lower a Hosted Employee count.
White Paper · Oracle Fusion
The per employee truth on Oracle ERP Cloud. 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, because the metric that can be governed also has to be.
If every employee uses self service expenses or approvals, model Hosted Employee at the best rate. The simplicity can also cut administrative overhead, and that overhead is real money in a large estate.
Hosted Named User is the only one of the two you can manage during the term. Deprovision leavers, tighten role assignment, retire a dormant department, and the count comes down.
Hosted Employee has no such lever. Nothing you do inside IT changes the number, because the number is set by hiring. You are buying predictability and paying for it with control.
That trade can be the right one. Just make it deliberately, and price the control you are handing over rather than discovering its value in year two.
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.
Six things, and they take one page. Every one of them is cheap to ask for before signature and close to impossible to win afterwards.
Oracle's own applications pricing pages and the definitions section of the Fusion Cloud Service global price list are the reference points for items one to three. Quote them back.
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 individuals you authorize to use the service. Hosted Employee counts the workforce, whether or not any given person opens ERP.
Whichever one wins the crossover calculation on your numbers. Named User is cheaper while your ERP users as a share of the workforce sit below the ratio of the employee rate to the named user rate. At a ten to one rate ratio that crossover is 10 percent of headcount.
Any individual authorized to use the service, including employees, contractors and third parties with access. Authorization is the test, not activity, so a provisioned account that nobody has opened in eight months still counts. That is why deprovisioning is a licensing task rather than a housekeeping one.
Usually yes. Oracle's standard employee definitions reach full time, part time and temporary employees plus the agents, contractors and consultants supporting internal business operations. Name the exclusions you want in the ordering document rather than relying on how the sentence reads to you.
They should not, but confirm it in writing on your own order. Supplier and customer self service populations are usually an order of magnitude larger than the employee population, so this is the one exclusion you never leave to assumption.
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, which is exactly when your leverage is lowest.
Through a renewal quote priced as a suite rather than as your existing line items. A packaged SKU often carries the employee metric by default, so the number looks comparable while the unit underneath it has changed. Ask for a line by line comparison with the metric column shown.
It can flip it entirely. Opening expenses or time entry to the whole workforce moves your user ratio above the crossover, which is the point at which Hosted Employee starts to price lower. It also hands Oracle the argument for the employee metric at renewal.
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, and it only works on the named user metric.
Write down your ERP user ratio, then make Oracle quote both metrics on identical scope so you can compute the crossover. The metric choice alone moved the annual subscription by 20 to 35 percent on identical scope in the deals we benchmarked.
Hosted named user versus hosted employee metrics, module pricing, and the negotiation levers on Oracle ERP Cloud.
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.
