Oracle Fusion ERP Pricing: Named User vs Employee

Contents

Key takeaways How the two metrics differ What we have seen Who counts under each metric Where the crossover sits How the metric gets switched True ups and audits Which metric to choose What Oracle will say The ordering document Renewal timeline What to do next FAQ

Oracle Fusion ERP Cloud is priced per Hosted Named User or per Hosted Employee. One counts the people you authorize, the other counts your workforce, and the cheaper choice depends on your user ratio against the two rates you are quoted.

Key takeaways

Two different populations. Hosted Named User counts the individuals you authorize, while Hosted Employee counts employees plus contractors and consultants who access or are tracked by the programs, whether or not they open ERP.
One line of arithmetic. Named User stays cheaper while ERP users as a share of employees sit below the employee rate divided by the named user rate, so a ten to one ratio puts the crossover at 10 percent, or 500 users in a 5,000 employee company.
Use quoted rates only. Oracle discounts the metric it prefers more deeply, which shifts the crossover, so compare the two rates you are quoted rather than list prices.
The swing is large. In the deals we benchmarked, the metric choice alone moved the annual subscription by 20 to 35 percent on identical scope.
Ask for the self service price. Oracle lists an ERP for Self Service service at $20 per named user per month, which can beat Hosted Employee when most staff only file expenses and approve.
Only one metric can be governed. You can deprovision named users during the term, but only hiring and HR records move a Hosted Employee count.
Lock the metric in the order. Adding one employee facing module is the most common way the metric changes at renewal, so write in a consent clause and a line by line mapping obligation.

How do the Hosted Named User and Hosted Employee metrics differ?

Hosted Named User counts the people you authorize to use Oracle Fusion ERP Cloud. Hosted Employee counts your workforce, whether or not those people ever log in. The same deployment therefore produces two very different invoices, and the metric you sign is fixed in the ordering document and hard to change mid term.

Both definitions sit in Oracle's cloud service descriptions and in the definitions section of the applications price list. Read the version that governs your order date. A sales slide or a summary from the account team does not bind Oracle, and the wording changes between versions.

Hosted Named User: the authorization test

Oracle defines a Hosted Named User as an individual authorized by you to access the hosted service, whether or not that individual is actively using it at any given time. Authorization decides the count, and login activity plays no part.

Authorization is where the count grows unnoticed. 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, which is why deprovisioning belongs to the license owner as much as to the security team.

Hosted Employee: a population count

Hosted Employee covers the workforce. The current Fusion service descriptions count all of your full time, part time and temporary employees, plus your agents, contractors and consultants where they have access to, use of, or are tracked by the programs.

Whether any of those people open Fusion ERP Cloud has no bearing on the count. That is how the metric is designed, and it is why the per unit rate can sit so far below a named user rate.

How does Oracle measure each metric?

Oracle publishes a separate document, Metric Descriptions for Oracle Fusion Offerings, that explains how its tooling counts usage. It is worth reading next to the contract, because the measurement rules are more specific than the contract definitions.

Hosted Named User. Oracle counts active users assigned specific privileges for each service. For the ERP service these include privileges such as AP_MANAGE_PAYABLES_ACTIVITIES_PRIV and GL_MANAGE_PERIOD_CLOSE_ACTIVITIES_PRIV. A user holding several of them counts once.
Hosted Employee. Oracle counts every person tracked in your Fusion service during the month, whatever the person type, including employees, agents, contractors and consultants. Workers whose only person type is Retiree or Not Managed by HR are excluded.
What you can see. Your service administrator can download the SaaS Services Usage Metrics Report from the cloud portal. It shows what you bought, how much, and what you used over the last three months.

The practical point is that Oracle's view of your position comes from privilege assignments and person records. Your own view should come from the same two places, pulled before Oracle pulls them.

Why does Oracle offer two metrics at all?

One metric cannot price both shapes of customer. A shared services center with 400 finance users and 30,000 employees is a different deal from a manufacturer where everyone files expenses, and each metric suits one of them.

Offering both allows Oracle to meet each buyer. It also allows the account team to quote whichever produces the larger number, and there is no rule requiring them to show you the other one.

Watch the briefingResearch briefing · 4:43

How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal

Open the briefing with transcript and chapters Browse the full video library →

What have we seen in recent Oracle Fusion ERP metric negotiations?

The metric decision is usually worth more than the discount conversation. Across roughly 30 to 40 Fusion ERP Cloud negotiations I reviewed in 2024 and 2025, the choice of metric alone moved the annual subscription by 20 to 35 percent for the same user population. The widest swing we recorded was 33 percent.

Mid market. Hosted Employee priced lower than Hosted Named User in roughly seven of ten mid market deals. It priced higher in large enterprises whose employee base was wide relative to their ERP users.
First quotes. Oracle's opening quote came in on the metric that produced the larger number in about two of three cases we benchmarked.
Year two growth. Where named user counts were not actively governed, true ups during the term added 8 to 18 percent to year two spend. The median was 14 percent.
Renewals. In about one deal in four, the renewal quote arrived on a different metric from the expiring order, and the customer had never put the two metric columns side by side.

In each of these patterns, the buyer had not priced both metrics before Oracle's first quote arrived.

Free white paper

Oracle ERP Cloud Pricing

Per employee and per named user rates on Oracle ERP Cloud, module by module, in one free white paper.

Get the white paper →

Who actually lands in each population?

Work it out person type by person type, because this is where the number is set. The table below is the one we build in the first week of an ERP metric engagement, and it is the document we want the customer to own before Oracle quotes anything.

Treat the uncertain rows as questions to put in writing. Where the table says confirm, 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 row carries the economics of the whole choice
Part time and temporary employees	Only if authorized	Counts	The employee definition names part time and temporary staff
Contractors, agents and consultants	Only if authorized	Counts if they have access, use, or are tracked by the programs	Contractors held as person records in Fusion count. 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 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 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 expensive to argue
Autonomous agents acting on their own schedule	Unsettled, ask in writing	Does not count	See our Fusion AI agents pillar for the argument

The row that decides the deal

Look again at the second row. An employee who never opens ERP is free under Hosted Named User and fully chargeable under Hosted Employee, and every dollar of difference between the two quotes sits in that gap.

So the first number to establish is the proportion of your workforce that will touch ERP over the whole term, including users of modules you have not deployed yet. Supplier counting has its own rules, covered in our note on Fusion Procurement supplier user counting.

The outsourcing trap

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 fall either. The definition reaches agents, contractors and consultants who have access to the programs, and a provider's clerks working in your Payables screens fit that description. Ask the question before you sign the outsourcing contract.

Where exactly is the crossover between the two metrics?

The crossover sits where your ERP user ratio equals the ratio of the two rates. Few buyers run that calculation in the meeting, and it takes one line.

Hosted Named User costs users times the named user rate. Hosted Employee costs employees times the employee rate. Named User stays cheaper while users divided by employees is 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	Named User is cheaper below, in a 5,000 employee company
One fifth	20 percent	1,000 ERP users
One eighth	12.5 percent	625 ERP users
One tenth	10 percent	500 ERP users
One fifteenth	6.7 percent	333 ERP users
One twentieth	5 percent	250 ERP users

Take that table into the meeting. Once Oracle gives you two rates, you can state the crossover before the account team reaches the end of its slide, and the discussion turns from the headline to your own numbers.

The four variables that decide it

Get these on one page before Oracle quotes anything. Three of them are yours to establish, and only the rates come from Oracle.

User ratio. ERP users divided by total employees, measured against the crossover the two rates imply.
Quoted rates. The negotiated price per named user against the negotiated price per employee, taken at the same point in the negotiation.
Growth curve. How fast each population grows over the term. Headcount and ERP users rarely grow at the same speed.
Module mix. Employee facing modules such as expenses, time and self service procurement raise the user ratio.

A worked comparison over three years

Use illustrative rates of $2,400 per named user per year and $240 per employee per year. That is 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, which gives 5,513 in year three. The only thing that differs between scenarios is whether self service expenses is 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

With the company and the rates held constant, the answer flips on one deployment decision that finance usually treats as a user experience question. The right metric depends on the rollout plan, so put that plan in front of whoever signs the order.

Is there a third option for occasional users?

Often there is, and Oracle rarely raises it. Its Fusion Cloud Service Global Price List dated September 10, 2026 lists the ERP service at $625 per Hosted Named User per month (10 user minimum). Oracle Fusion Enterprise Resource Planning for Self Service lists at $20 per Hosted Named User per month (100 user minimum).

That second service is aimed at people who create expense reports, time cards and similar self service transactions without doing finance work. Map what your occasional users actually do against the current service description and the Enterprise Resource Planning Self Service User role before you model it.

The same company with a mixed named user order (self service at list, $240 a year)
Scenario	Full users at $2,400	Self service users at $240	Mixed named user cost	Hosted Employee cost
Year one, expenses opened to everyone	350	250	$900,000	$1,200,000
Year three, expenses rolled out	380	520	$1,036,800	$1,323,120

On these assumptions the mixed order beats Hosted Employee in both rollout scenarios. Your own result depends on the discount you win on each line and on how many people need more than self service. Ask Oracle to price it on the same quote, because it seldom appears unless you request it.

How far are the illustrative rates from list?

At $625 a month, the ERP service lists at $7,500 per named user per year. The illustrative $2,400 therefore assumes a 68 percent discount from list. Oracle's standard subscription term is three years, so every rate you accept is carried for at least that long.

The rate asymmetry Oracle does not point out

Oracle discounts the metric it wants you on. Quote one at 45 percent off list and the other at 15 percent, and the crossover shifts without anyone saying 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 state it in the room. Our Oracle Cloud ERP pricing guide covers how those discounts are usually structured.

How does the metric get switched on you inside a bundle?

It happens 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 anyone calling it a change. We see four versions of this, and none requires anything improper from the account team.

The suite quote that arrives on a different unit

You hold a named user order for financials. At renewal, Oracle quotes a suite or enterprise package, and the package is priced per employee because that is how the packaged SKU is built.

The headline reads as more modules for a similar number. The unit has changed underneath it, and your bill is tied to headcount for the rest of the term.

The one module that changes the basis

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 for pricing the whole population. A small module can change the basis of the entire subscription.

The mixed metric order

One order can carry both metrics at once, and double counting hides there. A base priced per employee alongside additional modules priced per named user can mean paying twice for the same people.

Ask for a line by line metric column on both the expiring order and the renewal quote, and put them side by side. If Oracle will not produce that mapping, treat the refusal as information about the quote.

The clauses that stop it

Write these in before signature. Afterwards you are asking for a favor.

No metric change without consent. The license metric for each program cannot change at renewal or on any new order without your written agreement.
Additions inherit the metric. Any module added mid term is priced on the metric already in force for that program family, at the rate already agreed.
Both quotes on request. Oracle will quote either metric on identical scope at any renewal, so the comparison is always available to you.
Mapping obligation. Every renewal quote arrives with a line by line comparison against the expiring order, including the metric column.

None of these terms is exotic. They are ordinary contract hygiene that few customers ask for, and the module and rate detail behind them is in our ERP Cloud modules and pricing guide.

What does an Oracle ERP Cloud true up or audit look like?

It usually looks like a renewal conversation rather than an audit letter. Oracle measures cloud usage continuously and compares it with what you contracted, so the correction tends to arrive as a repriced renewal or an order for additional users.

What triggers a review

Rapid user provisioning, an acquisition or a module expansion all flag the account. Oracle compares provisioned identities against entitlement, and the Software Investment Guide sets out the policy background for how it treats usage beyond what you bought.

The two metrics leave different evidence trails

Buyers tend to discover this late. Under Hosted Named User the evidence is your identity management and the role assignments in the Fusion Security Console, and authorization is the test.

Under Hosted Employee the evidence is your HR data, including every contractor record held in Fusion. An ERP contract obligation then sits with the HR team, so decide who owns the evidence before signature and tell them.

How to check your own position

Pull the same data Oracle uses, a month before any renewal discussion. Every item below is standard in Fusion.

Where the counts come from in Oracle Fusion
What to check	Where to find it	What it tells you
Contracted quantity against measured usage	SaaS Services Usage Metrics Report, downloaded by your service administrator from the cloud portal	What Oracle sees for the last three months, service by service
Who holds counted privileges	User and Role Access Audit Report, compared with the privileges listed for your service in Oracle's metric descriptions	Which users and service accounts count as named users
Dormant accounts	Inactive Users Report, after running the Import User Login History process	Authorized users who have not signed in and can be removed
Hosted Employee population	Person records by person type in Fusion HCM	Contractors and consultants tracked in the system, and records typed as Retiree or Not Managed by HR

How to defend the count

Deactivate dormant accounts before the measurement window and map each active identity to a contracted entitlement. A clean identity baseline is the best defense against a surprise true up, and it works only on one of the two metrics.

You cannot deactivate an employee to lower a Hosted Employee count. The closest equivalent is data hygiene: contractors who left months ago but still sit in Fusion as active person records inflate the number, and cleaning them up is legitimate.

Which Oracle ERP Cloud metric should you choose?

Choose the metric that prices your realistic three year user curve at the lowest total cost. Then lock the per unit rate and the count basis in writing, and do not let Oracle pick the metric for you.

Narrow deployments

If ERP touches finance and procurement only, Hosted Named User is almost always cheaper. Take the shared services example from earlier: 400 finance users at $2,400 cost $960,000 a year, while 30,000 employees at $240 cost $7,200,000. The saving holds only if someone owns the user list and removes leavers and unused roles every quarter.

Broad deployments

If every employee uses self service expenses or approvals, model Hosted Employee at the best rate you can get, and model the mixed named user order next to it. The simpler count can also cut administrative overhead, and in a large organization that overhead is real money.

First purchase, renewal or move from E-Business Suite

The metric question looks different depending on where you start. Each situation below needs its own check.

First purchase. Your user counts are forecasts. Build the rollout plan by module and by year, because Oracle will price the metric against its own forecast if you do not supply one.
Renewal. You have real usage data from the SaaS Services Usage Metrics Report. Use it, and compare the renewal quote line by line with the expiring order.
Move from E-Business Suite. EBS customers often assume their Application User counts carry across. Fusion proposals are built fresh, so check the metric on every line, and read our note on the licensing shift from EBS to Financials Cloud.

The control you give up with Hosted Employee

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 offers no equivalent. Nothing you do inside IT changes the number, because hiring sets it. You are buying predictability and paying for it with control, which can be the right trade if you make it deliberately and price the control before you hand it over.

We do not accept that Hosted Employee is the safer default

Resellers often pitch Hosted Employee as the simpler and safer metric because it removes user counting and audit risk. We disagree. In roughly six of ten Fusion ERP Cloud deals I modeled, Hosted Employee priced higher for narrow finance rollouts, because it charges for the entire workforce on a system a few hundred people use.

The better course is to model both metrics against the real three year user curve, make Oracle quote each one, and choose only then. Simplicity is worth paying for, but not at a 30 percent premium you never measured.

A spreadsheet cost model displayed on a computer screen — The comparison needs a three year model per metric, built by module and rollout wave. A single year snapshot hides the point where expenses or time entry reaches the wider workforce.

What will the Oracle account team say, and how should you answer?

Expect a handful of standard lines once the metric comes up. Each has a factual answer, and giving it early keeps the negotiation on your numbers.

"Hosted Employee means you never have a compliance problem." Reply that the employee count still rises with every contractor and consultant tracked in Fusion, so it has a compliance side of its own. Then ask for the named user price on the same scope.
"The suite gives you more modules for about the same spend." Ask what the suite costs on your current metric, and ask for the metric column on every line before you discuss the total.
"This discount is only available on the employee metric." Ask for the discount percentage on both metrics in writing, then compute the crossover at each. A discount that exists on one metric only is a pricing choice by Oracle.
"We can only quote one metric this quarter." Say you will not sign on one quote, and ask for both from the same approval level. Timing pressure at quarter end works for Oracle only while you have one number.
"Your usage report shows more named users than you own." Ask for the user list and the privileges behind the figure. Remove dormant accounts and service accounts from the discussion before any price is agreed.

Oracle's first quote usually carries the metric that bills more. Model both before signature, because afterwards the metric is locked and so is the bill it produces.

What do you write into the ordering document?

Six items cover it, and they fit on one page. Each is cheap to ask for before signature and close to impossible to win afterwards.

The metric, stated per line. Each line carries its own metric, so a mixed metric order is visible on its face.
The count basis. For named user, who counts as authorized. For employee, whether contingent workers, affiliates and transition populations are in or out.
The excluded populations. Suppliers, customers, external auditors and service accounts, each named explicitly.
The unit rate and the discount percentage, both held for the term and both carried into the renewal quote. Without the percentage, a renewal can keep the rate and lower the discount on added lines.
The metric change consent clause, plus the obligation to quote either metric on identical scope at renewal.
Divestiture and acquisition treatment, so a corporate event does not become a repricing event. State how a transition population is counted and for how long.

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. For renewal price caps, see our guide to Financials Cloud renewal uplift negotiation.

When should you start work before an Oracle ERP Cloud renewal?

Start 12 months out. The usage report covers three months, the rollout plan needs a business owner, and Oracle's quote cycle follows its own quarter ends, so a late start leaves you comparing one quote with nothing.

Metric decision timeline before an ERP Cloud renewal
When	What to do	Why then
12 months before	Pull the usage report, build the person type table, get the three year rollout plan by module	You need your own numbers before Oracle offers its version
6 months before	Request quotes on both metrics, and on a mixed named user order with self service lines	Leaves time for a second round from a higher approval level
3 months before	Compute the crossover from quoted rates, clean up dormant users and stale contractor records, table the contract clauses	The usage window Oracle reports on is now the one that matters
1 month before	Check the final order line by line against the expiring one, confirm metric, count basis and exclusions	Changes after signature need Oracle's agreement

The mistakes that cost the most

Comparing at list. List prices say nothing about the crossover, because the two metrics are discounted differently. Compare quoted rates only.
Modeling year one only. A rollout wave in year two can move you past the crossover. Model the full term.
Leaving HR out. On Hosted Employee, HR data is the license count. If HR does not know that, contractor records pile up unchecked.
Accepting the renewal total. A similar total can hide a new metric. Always compare line by line.

For the wider renewal sequence across Fusion, see our Fusion SaaS renewal guide. Our Oracle HCM Cloud licensing guide covers the sister suite and the third metric you will meet on an HCM order.

The Oracle Knowledge Hub holds the rest of our Oracle library. If you want us to run the comparison with you, our Oracle practice does this work for a fixed fee.

What to do next

Measure today. Count current ERP users and total workforce, and write the ratio down as a single percentage.
Map the people. Build the person type table for your organization, including outsourced teams, affiliates and transition populations.
Project three years. Pull a realistic three year curve for both populations and test it against the rollout plan, because one employee facing module can flip the answer.
Get two quotes. Ask Oracle to quote Hosted Named User and Hosted Employee on identical scope at the same time, plus a mixed order with self service lines.
Compute the crossover. Use the two quoted rates, then compare the result with your own ratio curve.
Clean the count. Deactivate dormant user records before any measurement window.
Lock the terms. Fix the per unit rate, the discount percentage, the count basis and a cap on annual increases, and add the metric change consent clause and the renewal mapping obligation.
Benchmark before signing. Run the numbers through an independent benchmark before you commit to a three year term.

When to bring in help

Want a second opinion on your Oracle position? Our Oracle licensing consultants are former Oracle insiders who now work only for buyers.

Frequently asked questions

What are the two Oracle ERP Cloud licensing metrics?

Hosted Named User and Hosted Employee. The first charges for each individual you authorize to access the service. The second charges for your whole workforce, including qualifying contractors and consultants, so people who never log in still count. Most ERP orders use one of them for the base service, and some mix both across lines.

Which metric is cheaper for Oracle ERP Cloud?

It depends on two numbers you can calculate before any meeting: your ERP user share of headcount and the ratio between the two quoted rates. If the user share is below the rate ratio, Named User wins. A ten to one ratio puts the break point at 10 percent of headcount.

What counts as a Hosted Named User?

Any person you have authorized to use the service, whether an employee, a contractor or a third party. A login that sat untouched for eight months still counts, because the test is authorization. Oracle's usage tooling identifies these users through the privileges assigned to them, so role design affects the count too.

Does Hosted Employee include contractors?

Yes, in most cases. Oracle's current definition covers agents, contractors and consultants who have access to, use of, or are tracked by the programs, alongside full time, part time and temporary employees. If you keep contractor records in Fusion HCM, expect them in the count unless your order excludes them by name.

Do suppliers and customers count under either metric?

They should not count toward the employee metric, and a supplier or customer who never appears as a person record in Fusion has no place in a Hosted Employee count. Get the treatment written into your own order anyway. Supplier and customer populations are usually an order of magnitude larger than your workforce.

Can we switch metrics mid term?

Rarely, without a new ordering document. The metric is part of the subscription contract, so a switch normally waits for a renewal or a renegotiation, and by then Oracle holds the timing advantage. Make the choice before the first signature, and write a right to requote on the other metric into the order.

How does the metric get changed without us noticing?

Usually through a renewal priced as a suite instead of as your current line items. Packaged SKUs often carry the employee metric by default, so the total looks familiar while the unit has changed. Ask for a comparison against the expiring order with a metric column on every line.

Does adding self service expenses change the answer?

It can reverse it. Opening expenses or time entry to all staff lifts your user ratio past the crossover, and it gives Oracle a reason to argue for the employee metric at renewal. Price the ERP for Self Service named user lines before you accept that the employee metric has become cheaper.

How do we avoid a surprise true up?

Run the Inactive Users Report and remove dormant accounts before each measurement window, then match every remaining identity to a line you have paid for. Keep the SaaS Services Usage Metrics Report on file each quarter so you see growth before Oracle raises it. This control exists only on the named user metric.

What is the first step on Oracle ERP Cloud metrics?

Write down your ERP user ratio as a single percentage, then ask Oracle for both metrics on identical scope at the same time. With the two rates in hand you can compute the crossover yourself, and the choice becomes an arithmetic question instead of a sales one.