Oracle EPM Cloud pricing in 2026. The metric on the order form sets the bill.

Oracle EPM Cloud is priced per user per month by module. The bill is set by which metric your order form uses, Hosted Named User or Hosted Employee, and by how many environments you buy.

How is Oracle EPM Cloud priced?

Oracle EPM Cloud is billed per user per month, invoiced annually, with no single platform fee. Legacy per module contracts charge for each module enabled and its assigned users, with minimums commonly around ten users per module. The current tiers charge per user for the tier, which bundles the business processes.

Two things the rate card never shows decide most of the bill. The first is which metric your order form uses, since Oracle lists EPM Enterprise Cloud Service under both Hosted Named User and Hosted Employee. The second is how many environments you end up paying for.

EPM Standard and EPM Enterprise

New subscriptions come in two tiers, EPM Standard and EPM Enterprise. Older contracts still carry the per service subscriptions that Oracle's documentation now calls legacy, where each module is its own order line with its own user count. The tier decides which business processes, and which features inside them, you can create.

That table is the first test for any Enterprise quote. If none of the Enterprise only business processes or features are in use or planned in the contract year, Standard covers the scope. Check Transaction Matching and custom Planning cubes first, because they sit inside business processes Standard also offers and are easy to miss in a tier comparison.

What is the difference between Hosted Named User and Hosted Employee for EPM?

Hosted Named User counts the people you provision in EPM. Hosted Employee counts every person tracked in your Fusion service, including agents, contractors and consultants. It requires at least one Hosted Employee base service from Oracle HCM underneath it.

How the metric changes inside a Fusion deal

The switch to Hosted Employee rarely arrives as a proposal of its own. It happens when EPM is folded into a wider HCM or ERP negotiation. The order form is then normalized onto one metric for simplicity, usually Hosted Employee when HCM already sits on it.

From then on the EPM line grows with total headcount instead of with the planner population. The deal team that agreed to it has usually moved on by the time finance sees the second or third renewal.

A worked example of the two counts

Say you provision 300 EPM users and your HCM service tracks 11,000 people: 9,000 employees, 1,500 contractors and 500 agents and consultants. In year two you acquire a company with 2,000 staff and add 20 finance users. In year three a project brings in 800 contractors who never touch EPM.

The two metrics carry different unit rates, so year one totals can favor either. The difference lies in how each count grows. The named user count moved with the finance team, while the employee count moved with corporate events the EPM budget owner does not control.

The same Hosted Named User and Hosted Employee decision applies across Oracle's ERP applications, and our guide to the ERP licensing models covers it in detail. The HCM side of the prerequisite is in the Oracle HCM Cloud licensing guide.

Which EPM modules end up on the order form?

On legacy contracts, five module lines appear on most EPM order forms, each a separate SKU that bills whether anyone uses it or not. On Standard or Enterprise the same business processes come inside the tier, so the question becomes whether you need the tier at all.

• Planning and Budgeting. The entry point and the most widely deployed module, covering financial, workforce, capital and project planning.
• Financial Consolidation and Close. The highest per user rate in most quotes we see. Account Reconciliation frequently sits alongside it, either bundled or billed separately, so confirm which on your order form.
• Tax Reporting, and Profitability and Cost Management. Each is its own SKU with its own user count and its own user minimum, billed whether you reach it or not.
• Enterprise Data Management. Metered on records rather than users, which catches buyers who priced it like the other modules.
• Data Management. The integration layer that feeds everything else. It is easy to miss on an order form because finance teams rarely ask for it by name.

How to check who uses each module

Oracle gives administrators the reports needed for this. Run them well before the renewal proposal arrives.

• User audit report. The EPM Automate command userAuditReport lists who signed in over a date range. It only reaches back 120 days, so schedule it monthly and keep the files through a full budget cycle.
• Role assignment report. roleAssignmentReport shows which role each user holds per environment. Compare administrator and power user roles with the people who actually build or change models.
• The order forms themselves. List every line with its SKU, metric, quantity and unit price, then match each line to an environment and a business process.

How do EPM Cloud environments get billed?

An environment is a purchased order line, not a setting. Each subscription provisions a defined set of business processes, and every additional one is ordered as an Additional Application SKU on the Hosted Environment metric.

Oracle's documentation is direct about the commercial nature of this. Requests for additional business processes go to your account representative, and Oracle asks customers not to raise a service request because Support cannot help with it.

Why the environment count grows

On EPM Enterprise, each environment holds one application and therefore one business process. Switching an environment to a different business process means resetting it through Recreate Service, which wipes what was there.

So a team that wants Planning and Tax Reporting running side by side needs two environments, each normally paired with a test environment. Add a sandbox for a consolidation redesign and a second planning application for a subsidiary, and the count climbs without any change in users.

Build an environment inventory

Build one for the renewal file, showing which business process sits in each environment, on which SKU, at which rate. It belongs next to the user classifications, because Oracle counts both and only the user count was ever visible to the budget owner.

What have we seen in EPM Cloud reviews in 2024 and 2025?

Across roughly 20 to 30 EPM Cloud subscriptions we reviewed in 2024 and 2025, the rate card was never the reason the bill was too high. The excess came from how users were classified, what was bought and never opened, and what was counted without anyone in finance tracking it.

Professional users who never build a model

Professional user counts ran 15 to 30 percent above the people who actually built models. On the order forms we reviewed, a planner line was priced at several times a viewer line, so every misclassified viewer carries that multiple.

The error only runs one way. We have never seen an account team downgrade a user on its own initiative, so the correction comes from you at renewal or not at all.

Modules and environments no one tracked

Between 40 and 60 percent of the subscriptions we reviewed carried at least one module that had never been opened. Each carried its own user minimum, billing regardless. None of the finance teams could say how many environments they were paying for.

Enterprise where Standard would have done

Buyers on Enterprise whose real scope fit inside Standard paid a 30 to 50 percent premium for capability they did not use. The check is the tier table above, run against the business processes you have actually created. Plans shown during the original sale are not evidence of use.

Why we advise against folding EPM into the main Fusion order by default

The usual advice is to consolidate every Oracle SaaS line into one negotiation for a bigger discount. We disagree with doing that by default. Bundling moved effective EPM per user rates 10 to 25 percent at renewal, in whichever direction the preparation decided, and it is where the metric switch happens.

Negotiate in the same cycle and align the end dates if that helps. Keep EPM as separate lines with their own metric and quantities, and ask for the standalone quote beside the bundled one. The broader Fusion context is in our Fusion applications guide and the Fusion modules list.

Oracle counts the users and the environments. Only one of those numbers usually reaches the budget owner.

How should you prepare for an EPM Cloud renewal?

Run the review in a fixed order and start it early. In our Oracle SaaS work, an unprepared customer typically receives the renewal proposal around 90 days before expiry, carrying a 9 to 12 percent uplift. A usage audit across Oracle SaaS subscriptions typically finds 30 to 50 percent shelfware.

1. User classification audit. Planners against viewers, per module.
2. Module activation inventory. Drop the modules no one has opened.
3. Environment census. Every environment, business process, SKU and rate.
4. Tier test. Standard against Enterprise on the capability actually opened.

Hold the metric question through all four steps: the metric on each line in writing, with the other metric quoted on the same page. The true up and ratchet rules that apply to Fusion SaaS quantities are covered in our Cloud ERP pricing guide.

What the account team will say, and how to answer

• "Hosted Employee keeps EPM consistent with your HCM order." Ask for both metrics quoted for the same scope on one page, with the EPM line recalculated after your planned acquisitions.
• "Environments are part of the platform." Ask for every environment and business process listed on the order form with its SKU and rate.
• "Enterprise gives you room to grow." Ask which Enterprise only business process you have created. If the answer is none, ask for the Standard quote.
• "Reducing quantities will reprice the remaining users." Ask for the renewal unit price capped in writing, independent of quantity.
• "Consolidating EPM into the Fusion deal gets you a better discount." Ask for the standalone EPM quote next to the bundled one and compare effective per user rates.

Contract terms to ask for before you sign

If the renewal is close, the Oracle practice runs this review with you. For earlier planning, the Fusion SaaS renewal guide covers the wider Oracle SaaS timetable. Customers still on Hyperion should read the Hyperion to EPM Cloud migration cost analysis before they convert.

What to do next

1. This week. Pull every EPM order form and write down the metric, quantity and unit price on each line.
2. This month. Schedule a monthly userAuditReport export so you have login data beyond the 120 day window.
3. Next 60 days. Audit professional classifications, planners against viewers, per module.
4. Next 90 days. Inventory module activation and list every environment with its business process and SKU.
5. Six months out. Test Standard against Enterprise on what you actually opened, and request quotes on both metrics.
6. At signature. Confirm the metric, counted population, acquisition terms and fixed quantity in the order form.

Frequently asked questions