Fusion is a term right, and the renewal is the only leverage moment
Oracle Fusion Cloud Applications are licensed by subscription, not perpetual license, and that single fact changes every commercial move available: when the term ends the service stops, there is no dropping support and carrying on, and all the leverage that made on premise negotiations work concentrates into one date a year. The complexity sits in the metric definitions and the renewal terms, not in the software.
Prepared by Redress Compliance · August 8, 2026 · Oracle advisory. Based on 25 to 35 Oracle Fusion Cloud renewals benchmarked 2024 to 2025.
Executive summary
The metric outranks the count, every month of the term. Hosted users bill every provisioned account whether used or not, active users bill only accounts that transact, and Hosted Employee bills the whole tracked workforce, contractors and agents included, with retirees the notable exclusion.
Across our renewals, contracted user counts ran 15 to 25 percent above active users.
And Oracle does not refund the difference: a contract written on hosted users charges for every leaver and project account nobody deprovisions, which is why the active user metric is the one to ask for wherever the module supports it.
Quantities ratchet: add any Tuesday, reduce only at renewal, and only with the right in writing. Not one estate we reviewed held a written right to reduce quantity at renewal, and several believed they did until we read the order with them.
The four contract checks that decide the position, none of them the price: the term and auto renewal mechanics, the quantity change rights in both directions, the data extraction window after termination, and which version of which service definition document governs your metric.
The bundled cloud credit is priced in and thrown away. IaaS and PaaS credits bundled into the subscription went unused in six of ten estates, and they do not carry beyond the term: the credit is part of what the subscription fee buys, so unconsumed credit is money paid for nothing.
And the burn plan belongs in the same review cadence as the user counts.
The discount that frames it all: 35 to 55 percent off list is the band on a 36 month commit, and uncapped renewal uplifts of 8 to 12 percent, which landed wherever no cap was written, erase that discount within two cycles.
The perpetual instincts are the expensive ones.
A perpetual estate could terminate support on proven shelfware, run third party support, and choose its own upgrade timing.
The subscription has none of those, the service switches off at term end, Oracle updates on its own quarterly cadence, and your data is extractable within a defined window and then gone.
The consequence is a different negotiation: everything, the metric, the cap, the reduction right, and the extraction window, is negotiated at signature or at renewal, and at no other moment, because the walk away option that disciplined the on premise relationship does not exist here.
The term right against the perpetual license
| Dimension | Perpetual on premise | 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 net license | The full fee, repriced each renewal |
| Reducing spend | Terminate support on proven shelfware | Only at renewal, only with a reduction right |
| Alternative supplier | Third party support keeps it running | None; the service switches off |
| Your data at exit | In a database you control | Extractable in a defined window, then gone |
| Leverage moment | Support renewal, audit, any time you choose | The renewal date, and nothing else |
Four contract checks before any price conversation.
The term and renewal mechanics, does it auto renew, on what notice, at what price basis; the quantity change rights, what you may add, what you may reduce, and on what date; the data extraction window and format; and which service definition document, in which version, defines your metric.
If those four cannot be answered from your own paperwork in an afternoon, the renewal is not ready to negotiate.
The metric families, and where buyers lose money
| Metric | Counted population | Reduces when | Where buyers lose money |
|---|---|---|---|
| Hosted Named User | Every provisioned account | Only at renewal, if permitted | Leavers and project accounts nobody deprovisions |
| Active user | Accounts transacting in the period | Usage falls, within contract rules | Rarely; this is the metric to ask for |
| Hosted Employee | Everyone tracked, contractors included | Only at renewal | Growth with no usage change at all |
| Consumption metrics | Order lines, records, planned item locations | At renewal, if volumes fell | Forecasting on averages instead of peaks |
The Oracle Fusion SaaS brief
The metric definitions, the ratchet mechanics, the credit burn plan, and the renewal calendar worked on a representative estate.
Get the white paper →The ratchet, the credit, and the renewal calendar
The ratchet is the structure everything else hangs on: additions process any day of the term, reductions process only at renewal and only where the order grants the right.
So the estate that discovers its 15 to 25 percent dormant population mid term holds that discovery eleven months before it can act on it.
The renewal preparation therefore starts early, the active user measurement running quarterly, the Hosted Employee population reconciled after every acquisition since the metric counts contractors you never considered employees.
And the IaaS and PaaS credit burn tracked monthly because the six in ten estates that wasted it simply never assigned an owner.
The module by module economics sit in the Cloud ERP pricing guide and the base subscription versus add ons analysis, and the escape arithmetic every legacy estate weighs, staying on EBS with support options against subscribing, in the EBS licensing guide.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Fusion renewals, 2024 to 2025
Across roughly 25 to 35 Oracle Fusion Cloud renewals Fredrik Filipsson benchmarked between 2024 and 2025, the gap between contracted and active users averaged 15 to 25 percent:
Renewal increases landing wherever no cap was written into the original order.
Estates whose bundled IaaS and PaaS credits expired unused, with no owner assigned.
The reduction right finding deserves the emphasis: not one estate held one in writing, and the belief that they did, until the order was read together, is exactly how the ratchet works, because the assumption of flexibility postpones the measurement that would have proven the need for it.
The subscription model concentrates a decade of commercial relationship into one annual date, and the buyer who arrives at that date with the active count measured, the metric argued, the cap demanded, and the reduction right drafted negotiates a renewal.
The buyer who arrives with a quote negotiates a surrender.
Your first five moves
- Answer the four contract checks from your own paperwork: renewal mechanics, change rights, extraction window, and the governing metric document.
- Measure active against contracted users quarterly, the 15 to 25 percent gap Oracle never refunds.
- Negotiate the active user metric where the module supports it, and the written reduction right where it does not.
- Assign an owner to the IaaS and PaaS credit burn, the value six of ten estates paid for and threw away.
- Cap the renewal uplift in writing, because 8 to 12 percent uncapped erases the discount in two cycles. The Oracle practice runs the renewal with you.
Frequently asked questions
How are Oracle Fusion Cloud Applications licensed?
By subscription: a right to use the service for a fixed term across the ERP, HCM, SCM, CX, and EPM pillars, each with its own metric and counted population.
When the term ends the service stops, there is no perpetual fallback or third party support option, which concentrates all commercial leverage into the renewal date.
What is the difference between hosted and active user metrics?
Hosted users bill every provisioned account whether anyone uses it or not; active users bill only accounts that transact in the measured period.
Contracts written on hosted users charge for dormant accounts every month, and contracted counts ran 15 to 25 percent above active users across our renewals, so the active metric is the one to negotiate wherever the module supports it.
What does the Oracle Hosted Employee metric count?
Every person tracked in the service during the month, counted once: employees, agents, contractors, and consultants, with only retirees and workers not managed by HR excluded.
Two consequences follow: contractors you never considered employees are inside the count, and an acquisition raises the subscription even when usage does not change at all.
Can you reduce Oracle Fusion quantities mid term?
No: additions process any day, reductions process only at renewal and only where a written reduction right exists in the ordering document, and not one estate we reviewed held one, though several believed they did.
The right gets negotiated at signature or renewal, drafted explicitly, because the default paper is a one way ratchet.
What discount is achievable on Oracle Fusion?
35 to 55 percent off list is the band on a 36 month commitment, but the discount only survives if the renewal uplift is capped: uncapped increases of 8 to 12 percent landed wherever no cap was written, erasing the original discount within two cycles.
The cap belongs in the original order, not the renewal conversation.
What happens to the bundled Oracle cloud credits?
The IaaS and PaaS credits packaged into Fusion subscriptions expire with the term, and they went unused in six of ten estates we reviewed, mostly because nobody owned the burn.
The credit is part of what the fee buys, so the fix is an owner and a monthly burn review, or a smaller subscription that stops paying for capacity nobody consumes.
