Contents
Key takeawaysHow Fusion is licensedThe metric familiesReducing quantitiesBundled cloud creditsContract terms to checkWhat we see in renewalsAnswering OracleRenewal timelineWhat to do nextFAQFusion is a subscription that ends with its term, so the terms you can change are set at signature or renewal. The metric definition, the uplift cap and a written reduction right decide more of the cost than the discount.
- It is a term right. When the subscription ends the service stops, with no perpetual fallback, no third party support, and a short fixed window to retrieve your data.
- The metric drives the bill. Hosted Named User bills every enabled account holding the privileges, and contracted counts ran 15 to 25 percent above active users in our benchmarks.
- Hosted Employee counts almost everyone. Employees, agents, contractors and consultants all count, and only the Retiree and Not Managed by HR person types are excluded.
- Quantities ratchet upward. Additions process on any day, reductions only at renewal with a written right, and no customer we reviewed held one.
- Bundled credits expire unused. IaaS and PaaS credits do not carry beyond the term, and most subscriptions we reviewed let them lapse.
- Cap the uplift when you sign. The 35 to 55 percent band on a 36 month commitment holds only if the renewal uplift is capped in the original order.
How are Oracle Fusion Cloud Applications licensed?
Oracle Fusion Cloud Applications are sold as a subscription: a right to use the service for a fixed term, with no license you keep afterward. The suite covers five pillars, ERP, HCM, SCM, CX and EPM, and every service inside them has its own metric and its own counted population.
When the term ends, the service stops. There is no perpetual right to fall back on and no third party support option, so every commercial term you can influence gets set at signature or at renewal. The cost risk sits in the metric definitions and the renewal paper, far more than in the software.
| Dimension | Perpetual on premises | Fusion Cloud subscription |
|---|---|---|
| What you hold | A perpetual right, kept even without support | A term right that ends with the term |
| Annual cost | 22 percent support on the net license fee | The full subscription fee, repriced at each renewal |
| Reducing spend | Terminate support on proven shelfware | Only at renewal, and only with a written reduction right |
| Alternative supplier | Third party support keeps the software running | None, the service switches off |
| Your data at exit | In a database you control | Extractable in a defined window, then deleted |
| When you can negotiate | Support renewal, audit, or any time you choose | The renewal date, and nothing else |
What do former EBS and on premises customers get wrong first?
They bring perpetual instincts to a subscription. On a perpetual license you could drop support on shelfware, move to a third party provider, or hold an old release for years. In Fusion, Oracle ships quarterly updates on its own calendar, labeled 26A through 26D in 2026, and you must stay on supported releases.
If you are still deciding whether to stay on EBS with a support option or subscribe, the cost comparison is in our EBS licensing guide.
How to Negotiate the Oracle Java Employee Agreement: Honest Leverage in a Captive Deal
Which Fusion metrics do you pay for, and where do buyers lose money?
You pay on one of four metric families, and in every month of the term the metric shapes the bill more than the unit price does.
| Metric | Counted population | Count goes down when | Where buyers lose money |
|---|---|---|---|
| Hosted Named User | Every provisioned account holding the relevant privileges | Only at renewal, if the order permits it | Leavers and project accounts that were never deprovisioned |
| Active user | Accounts that transact in the measured period | Usage falls, within the contract rules | Rarely, which is why this is the metric to ask for |
| Hosted Employee | Everyone tracked in the service, contractors included | Only at renewal | Workforce growth with no change in usage at all |
| Consumption metrics | Order lines, records, planned item locations | At renewal, if volumes fell | Forecasting on averages instead of peaks |
What does "active" mean in a Hosted Named User contract?
A Hosted Named User contract bills every provisioned account that holds the relevant privileges, whether or not anyone uses it. Oracle's metric descriptions do call the count "active users", but active there means an account that is enabled and carries the role. A person who has not signed in for a year still counts.
Leavers never end dated, project and test accounts, and implementation consultants all stay in the count until someone removes them. A definition that counts only accounts transacting in the period removes that drift, so we ask for it, in the order itself, wherever the module supports it.
Who does the Hosted Employee metric count?
Hosted Employee counts every person tracked in your Fusion service during the month, once each, regardless of person type. That covers employees, agents, contractors and consultants. Oracle excludes only workers whose single person type is Retiree or Not Managed by HR, and the metric requires at least one Hosted Employee base service from Oracle Cloud HCM.
- Contractors are inside the count. Agency staff and consultants loaded into HCM for timekeeping or access raise the subscription.
- Acquisitions raise the bill. Loading an acquired workforce increases the count even when usage does not change.
- Person types are the only exclusions. Classification errors on those two types cost money every month.
We compare the two people metrics in Hosted Named User versus Hosted Employee, and cover HCM in the HCM Cloud licensing guide.
How do consumption metrics catch buyers out?
Consumption metrics count business volumes. Oracle Order Management, for example, counts sales order lines processed in the trailing twelve months, in units of 1,000. Planned item locations multiply the number of planned items by the number of planned locations, so one new warehouse raises the count across every item planned there.
Size on peak volumes, not averages, because additions during the term are bought on whatever terms the order sets while reductions wait for renewal. Our guides to order line pricing and SCM metrics cover the supply chain services in detail.
Oracle Fusion SaaS brief
Metric definitions, reduction rights, credit burn and renewal timing for Fusion Cloud buyers.
Get the white paper →Can you reduce Oracle Fusion quantities before renewal?
No. Oracle processes additions on any day of the term, but reductions only at renewal, and only where the ordering document grants a written right to reduce. Without that clause the standard paper works as a one way ratchet, and quantities only go up.
The timing is what makes it expensive. A company that finds a dormant population in the first month of a 12 month renewal period holds that finding for eleven months before it can act. On a 36 month commitment, the same finding can wait almost three years.
What does a dormant user population cost?
Say you contract 1,000 Hosted Named Users at a hypothetical net rate of $100 per user per month. A quarterly review shows 200 of those accounts, 20 percent, have not transacted. That gap sits inside the range we see in practice.
| Step | Calculation | Cost |
|---|---|---|
| Monthly cost of the dormant accounts | 200 × $100 | $20,000 |
| Annual cost | $20,000 × 12 | $240,000 |
| Paid before a 12 month renewal, found in month one | $20,000 × 11 | $220,000 |
| Paid before renewal of a 36 month term, found in month one | $20,000 × 35 | $700,000 |
Oracle refunds none of it. The only fix is a smaller quantity at renewal, which needs three things in place: the reduction right, the measurement to support it, and notice given on time. The module by module economics are in our Cloud ERP pricing guide and the base subscription versus add ons analysis.
What happens to the IaaS and PaaS credits bundled with Fusion?
They expire with the term. Where Oracle packages IaaS and PaaS credits into a Fusion subscription, the credit is part of what the fee buys, and unconsumed credit does not carry beyond the term. In six of ten of the subscriptions we reviewed, the bundled credit went unused.
The usual cause was that the credit had no owner. Finance saw a single subscription line, the applications team did not run infrastructure, and the infrastructure team often did not know the credit existed. We cover how Oracle structures credits in Oracle cloud contracts and credits for CIOs.
How should you manage the credit burn?
- Name an owner at signature. One person accountable for consumption, reporting to whoever owns the Fusion renewal.
- Plan workloads before accepting the credit. Integration, analytics, backup or test workloads on OCI that you would otherwise pay for elsewhere are the usual candidates.
- Review the burn monthly. Track consumption against a straight line to term end, in the same review as the user counts.
- Ask for carryover in writing. Unused credit that rolls into the renewal term, or converts to subscription value, is worth requesting even if Oracle declines.
Which contract terms decide your Fusion renewal before any price talk?
Four terms decide it, and the price is not one of them. If you cannot answer all four from your own paperwork in an afternoon, the renewal is not ready to negotiate.
- Term and renewal. Does the order auto renew, on what notice, and at what price basis?
- Quantity change rights. What you may add, what you may reduce, and the date each change takes effect.
- Data extraction. The window after termination, and the format Oracle will deliver.
- Metric document. Which service description, in which version, defines your metric.
What wording should you ask Oracle for?
These are the clauses we draft into Fusion orders. Oracle will resist some of them.
| Term | What to ask for | Why it matters |
|---|---|---|
| User definition | Count only users who transacted in the measurement period | Stops paying for dormant and leaver accounts every month |
| Reduction right | Reduce each service at renewal by a stated percentage, without repricing the remaining quantity | Turns the ratchet into a two way right |
| Renewal cap | An uplift cap of 0 to 3 percent that survives the term and binds the next renewal | Protects the discount you won at signature |
| Renewal price basis | Renew at current net unit prices, with no reference to list | Blocks a reset to list less a smaller discount |
| Metric version | The service description version in force at signature governs for the whole term | Oracle republishes its metric descriptions, and a later version can count differently |
| Term length | Offer a longer commitment only in exchange for the cap, the reduction right and the extraction terms | Term is what Oracle values most, so trade it for these protections before you trade it for extra discount |
| Data extraction | A window longer than the standard 60 days, plus export assistance | A migration rarely finishes inside two months |
What have we seen in recent Oracle Fusion renewals?
Across the roughly 25 to 35 Oracle Fusion Cloud renewals I benchmarked between 2024 and 2025, these findings kept coming up.
- Dormant users. Contracted user counts ran 15 to 25 percent above active users, and Oracle refunded none of the difference.
- Uncapped uplifts. Wherever no cap was written into the original order, renewal increases landed at 8 to 12 percent.
- Wasted credit. Bundled IaaS and PaaS credits expired unused in six of ten cases, almost always with no owner assigned.
- Missing reduction rights. Not one customer held a written right to reduce quantity at renewal, and several believed they did until we read the order with them.
- Discount band. On a 36 month commitment, 35 to 55 percent off list was the range achieved.
The reduction right finding matters most, because believing the flexibility existed delayed the measurement that would have proven the need for it.
A buyer who arrives at renewal with the active count measured, the metric argued, the cap demanded and the reduction right drafted negotiates a renewal. A buyer who arrives with only Oracle's quote negotiates a surrender.
Why is chasing the biggest discount the wrong place to start?
The usual advice is to push hardest on the discount percentage. We disagree, because the discount rarely decides the total. At the same list price, 45 percent off 1,200 users, 250 of them dormant, costs more than 38 percent off the 950 who are active.
Start with scope. In the Oracle SaaS renewals we prepare, 18 to 32 percent of the modules in a bundle are typically inactive. Strip those out with the dormant accounts, argue the metric, then write the cap and the reduction right. Price comes last, against a quantity you have proven.
How much of the discount does an uncapped uplift give back?
Up to about half of it within two cycles, depending on the discount and the uplift. Take a hypothetical subscription at $1,000,000 a year at list, signed at 45 percent off, and compare a 10 percent uplift at each renewal with a 3 percent cap.
| Point in time | Uncapped annual fee | Discount left | Capped annual fee | Discount left |
|---|---|---|---|---|
| Signature | $550,000 | 45 percent | $550,000 | 45 percent |
| After renewal one | $605,000 | 39.5 percent | $566,500 | 43.35 percent |
| After renewal two | $665,500 | 33.45 percent | $583,495 | 41.65 percent |
After two renewals the uncapped buyer pays $82,005 a year more. At the bottom of the band it is harsher: 35 percent off followed by two 12 percent uplifts leaves you paying 81.5 percent of list, with nearly half the discount gone.
What will Oracle's account team say, and how should you answer?
Expect these four positions at most Fusion renewals.
- "Reductions are not available under our standard terms." Treat it like any other negotiated clause. Make the reduction right a condition of renewing the rest of the order at the proposed quantity.
- "The increase reflects our annual price change." Ask where your order sets the renewal price basis. If it does not, the increase is a proposal, and your counter is a written cap that also binds the next renewal.
- "You will find a use for the cloud credits." Ask for the credit priced as its own line, and decline it if no named workload exists.
- "Hosted Employee is simpler because you stop counting users." It swaps a user count for a workforce count that includes contractors and grows with every acquisition. Model both on your own data first.
When should Oracle Fusion renewal preparation start?
Start at least 12 months out, because evidence for a reduction takes several quarters to build. Measure active users quarterly, reconcile the Hosted Employee population after every acquisition, and track the credit burn monthly.
| Months before renewal | What to do |
|---|---|
| 12 | Pull every order and the service description behind each metric. Answer the four checks. Start quarterly user measurement. |
| 6 | Second measurement. Model each service on each metric. List inactive modules and dormant accounts. |
| 3 | Send Oracle your written position on quantities, metric, cap, reduction right and extraction. Confirm the notice date. |
| 1 | Check the final quote line by line against your drafted clauses. Sign nothing that omits them. |
Which Fusion reports show what you actually use?
Standard Fusion security reports supply the evidence. Keep each quarterly output, since a trend persuades Oracle more than a snapshot.
- Inactive Users Report. Lists users who have not signed in for a period you set, 30 days by default, once the Import User Login History process runs daily. Users who never signed in do not appear, so check the full user list too.
- User Role Membership Report. Shows which users hold which roles, the basis for any privilege based count.
- User and Role Access Audit Report. Shows the privileges each user reaches through their roles, useful when a service is counted on a specific privilege.
- Person type counts in HCM. For Hosted Employee, count people by person type each month and confirm retirees and people not managed by HR carry exactly those types.
What to do next
- This week. Answer the four contract checks from your own paperwork: renewal mechanics, change rights, extraction window, and the governing metric document.
- This quarter. Measure active against contracted users, and repeat every quarter until renewal.
- Before the renewal proposal. Ask for a transacting user definition where the module supports it, and a written reduction right where it does not.
- Now, if you hold credits. Assign an owner to the IaaS and PaaS credit burn and review it monthly.
- In the order. Cap the renewal uplift in writing, with language that covers every renewal.
- If you want help. Our Oracle practice runs the Fusion renewal with you, from the first measurement to signature.
Frequently asked questions
How are Oracle Fusion Cloud Applications licensed?
By subscription for a fixed term, across the ERP, HCM, SCM, CX and EPM pillars, each service with its own metric. Nothing survives the term. The ordering document and the service description version it references are the whole of your entitlement, so keep both and read them before every renewal.
What is the difference between hosted and active user metrics?
Hosted Named User counts every enabled account holding the relevant privileges, used or not. An active user definition counts only accounts that transact in the measured period. The gap is widest in organizations with high turnover or many project accounts, so the transacting definition is worth negotiating wherever a module supports it.
What does the Oracle Hosted Employee metric count?
Every person tracked in the Fusion service during the month, counted once: employees, agents, contractors and consultants. Only people whose single person type is Retiree or Not Managed by HR drop out. Growth through hiring or acquisition raises the subscription even when no new person uses the finance or supply chain services.
Can you reduce Oracle Fusion quantities mid term?
No. Reductions take effect only at renewal, and only if the ordering document contains a written reduction right, which none of the customers we reviewed held. Negotiate it at signature or at the next renewal, per service, and check the notice date the order sets for requesting the change.
What discount is achievable on Oracle Fusion?
On a 36 month commitment, 35 to 55 percent off list. That discount lasts only if the uplift is capped: where no cap was written, renewal increases of 8 to 12 percent followed. Ask for a cap of 0 to 3 percent in the original order, worded to cover every renewal.
What happens to the bundled Oracle cloud credits?
They expire with the subscription term and do not roll forward on standard terms. Most waste traces back to a missing owner, so assign one and review consumption monthly. With no workload in mind, ask Oracle to price the subscription without the credit.
What happens to your data when an Oracle Fusion subscription ends?
Oracle's Cloud Hosting and Delivery Policies make your content available for 60 days after the services period ends, in a structured, machine readable format, and then delete it. Ask for a longer window and export help at signature, while you still have something to trade.