Oracle's own License Definitions and Rules say external supplier use of the Supplier Portal is included in the application user licenses you already own. This guide shows you where that language lives, where the real cost sits (Self-Service Procurement and Hosted Employee metrics), and how to defend the position in an audit.
Oracle's own License Definitions and Rules say external supplier use of the Supplier Portal is included in the application user licenses you already own. This guide shows you where that language lives, where the real cost sits (Self-Service Procurement and Hosted Employee metrics), and how to defend the position in an audit.
External suppliers do not each require a paid seat. Oracle's own License Definitions and Rules (v031525, March 15, 2025) is explicit: for Sourcing, Oracle iSupplier Portal, Oracle Fusion Supplier Portal, Oracle Services Procurement and the related PeopleSoft and JD Edwards supplier programs, "use by Your external suppliers is included with Your application user licenses." That is the single most quotable line in any Fusion Procurement audit, and it disposes of the most common overcount Oracle's LMS team attempts.
Read literally, this means supplier portal users, sourcing bidders responding to RFQs and auctions, and self-service supplier contacts registering their companies are bundled into the buyer-side seats you already purchased. They are not counted as Hosted Named Users. In 25 years of negotiating Oracle procurement contracts, the supplier-count claim is the audit finding we most reliably knock out on paper alone, because Oracle's own document contradicts its auditors.
External supplier use of the Supplier Portal is bundled into the buyer-side licenses you already own. It is not a per-seat charge. Oracle's own rulebook says so.
The trap is not the suppliers. The trap is the metric attached to the modules your own internal buyers and employees touch. That is where the money moves, and that is what the rest of this page dissects. If you want the metric mechanics across the wider suite first, start with named user versus employee versus volume metrics and then return here for the procurement-specific reading.
Supplier accounts are created outside your internal named-user pool. Per the Oracle Fusion Procurement Implementation Guide, suppliers self-provision through the portal: supplier users with the Supplier Self-Service Administrator (SSA) role create additional supplier contact accounts themselves. Because these accounts appear in the same user tables an auditor queries, a lazy or aggressive count sweeps them in as if they were licensable Hosted Named Users.
The specific role at the center of the "do bidders count" argument is the Supplier Bidder role used for sourcing events. A supplier organization responding to an RFQ or reverse auction consumes a Supplier Bidder role. Oracle's contract language covers exactly this category. When an auditor lists your bidder population as a licensing gap, you cite v031525 and the finding evaporates. Document your supplier registration counts separately from your internal roster so the distinction is legible before Oracle asks.
One nuance worth stating plainly. The internal Supplier Portal administrator seats your buyers use to manage the portal are a different animal. In the Wright County, MN Oracle SOW (August 22, 2019), SKU B69718 (Oracle Fusion Supplier Portal Cloud Service, Hosted Named User) was licensed at $82.50 per user per month for only 10 users. Those 10 were internal administrators, not the external suppliers themselves. Confirm which population your Supplier Portal line item actually covers, because Oracle occasionally conflates the two to justify a larger buy.
Oracle Fusion Procurement is sold per user, per month, billed annually. Published benchmarks vary widely because they reflect different bundles and discount levels. Capterra (2026) lists a starting figure of $400 per month per user. SelectHub (2026) cites a high-end $625 per user per month reflecting premium bundling. ERP Research (June 2026) pegs the broader Fusion suite range at $175 per user per month for limited-scope users up to $625 for premium modules. These are list-style anchors, not what you should pay. The Wright County SOW shows real discounted units far below list, and we cover the discount curve below.
| SKU | Module | Metric | Real signed unit (Wright County SOW, 2019) |
|---|---|---|---|
| B69717 | Oracle Fusion Purchasing Cloud Service | Hosted Named User | ~$48.13 / user / month |
| B69718 | Oracle Fusion Supplier Portal Cloud Service | Hosted Named User | $82.50 / user / month (10 internal admin seats) |
| B69721 | Oracle Fusion Self-Service Procurement | Hosted Employee | $1.10 / user / month (100 users) |
| B78965 | Supplier Qualification Management | Hosted Named User | Not separately priced in this SOW |
The comparison in that table is the whole game. Purchasing power-user seats run at roughly $48 discounted. Self-Service Procurement ran at $1.10. The 44x gap is not a fluke discount. It reflects the fact that Self-Service Procurement is sold on a fundamentally different basis, and that basis is where the real trap lives.
Two definitions govern almost every Fusion Procurement dispute. Get these exactly right.
The current Oracle Fusion Cloud Global Price List (August 6, 2026) defines a Hosted Named User as "an individual authorized by you to access the hosted service, regardless of whether the individual is actively accessing the hosted service at any given time." Oracle's Metric Descriptions for Fusion Offerings (June 12, 2026) confirms the count is by privilege assignment, not login: it counts "the number of active users with at least one of the following privileges," and a user holding multiple qualifying privileges is counted once. This matters. You are billed on who is authorized, not who logged in last quarter, so dormant-but-provisioned accounts are billable exposure.
Self-Service Procurement is sold on a Hosted Employee basis. Under this metric, "the quantity of the licenses required is determined by the number of Employees and not the actual number of users." The definition then sweeps far past your payroll: it counts "all of your full-time, part-time, temporary employees, and all of your agents, contractors and consultants who have access to, use, or are tracked by the programs." Outsourcing widens the net again, pulling in the outsourcer's staff who provide the service and touch the programs.
The unit price on Self-Service Procurement looks trivial at a dollar a head. The metric behind it is your entire workforce plus contractors. Module mix moves the ratio, not the rate.
Redress Compliance's May 2026 analysis states the mechanism bluntly: "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," and "employee-facing modules move the ratio, not the rate." A $1.10 unit across 12,000 employees plus 3,000 contractors is $198,000 a year, and it grows with headcount automatically. Before you enable Self-Service Procurement, model the Hosted Employee count across your full tracked population, not the number of people you expect to raise requisitions.
The most expensive procurement audit finding usually has nothing to do with suppliers or headcount. It is seeded-role bundling. Oracle's predefined roles carry privileges that span modules. Assign one, and you may enable access to a service you never bought. As Redress Compliance (July 26, 2025) documents, "a generic finance role might include access to a procurement module that your company never purchased," and "Oracle would count those users as requiring the extra module subscription."
A concrete, documented example: the seeded Buyer role consumes an Oracle Fusion Enterprise Contracts Cloud Service license because it carries the OKC_AUTHOR_CONTRACT_TERMS_AND_CONDITIONS_TEMPLATE_PRIV privilege (Oracle Cloud Customer Connect, February 27, 2024). Your buyers doing ordinary purchasing work can silently trip a separate, licensable contracts product. Audit your role-to-privilege mapping and strip privileges that reach into unlicensed services. Custom-scoped roles are the defense; seeded roles are the liability. The same discipline is central to what Oracle examines in a Fusion audit.
A second, distinct trap is integration and technical accounts. Customers treat system-to-system integration accounts as non-licensed. Oracle disputes that (Redress Compliance, March 20, 2026). Name your technical accounts clearly, keep them off human-privilege roles, and hold the contractual position that automated integration users are not authorized human users. Prepare that argument before an audit, not during one.
Unlike on-prem Oracle, Fusion gives Oracle real-time visibility into user counts, role assignments, API consumption, and storage. That telemetry converts organic growth into a standing true-up exposure. Redress Compliance (March 20, 2026) models it: a customer that grows from 2,000 to 2,300 licensed users can face a retroactive true-up of $150,000 to $300,000 (300 users, 36 months, $15 to $30 per user per month at premium pricing). Growth you did not track is growth Oracle did track.
Oracle litigates aggressively when it believes it is owed. In the AFPA case (Computer Weekly, April 19, 2017), Oracle demanded 885 additional Purchase Order module licenses, issuing a claim of EUR 3,209,895 in license fees plus EUR 9,487,731 in support, and it pursued the damages at full list price despite AFPA having historically bought at an 86% discount. The lesson: a compliance gap can be repriced from your negotiated rate to list, so the cost of an unmanaged true-up is not your discount, it is Oracle's list. Keep your entitlement-to-consumption position defensible at all times.
For the broader context of how procurement sits within the Fusion supply chain estate and what drives total spend, use the Fusion SCM licensing buyer guide. If you are negotiating the underlying commercial terms, the Oracle ERP Cloud pricing playbook and the pattern of licensing external users in Experience Cloud both reinforce the same principle: never pay per-seat for populations the contract already covers.
Net position: suppliers are the false alarm, and the money is in the metric on your own people. Win the supplier argument on paper, then spend your negotiating energy on the Hosted Employee exposure, the seeded-role leakage, and the true-up band. That is where six-figure outcomes are decided.
No. Oracle's License Definitions and Rules (v031525, March 15, 2025) state that external supplier use of the Supplier Portal, Sourcing, and Services Procurement is included with the application user licenses you already own. Supplier portal contacts do not each consume a Hosted Named User seat.
No. Suppliers responding to negotiations use the Supplier Bidder role, which falls under the external-supplier bundling in Oracle's rules. If an auditor lists your bidder population as a gap, cite the v031525 language and require its removal from the count.
Because it is sold on the Hosted Employee metric, not per active user. The count includes all full-time, part-time, and temporary employees plus agents, contractors, consultants, and outsourcers who are tracked by the system. A low per-head rate applied to your entire workforce can still produce a large annual figure.
Seeded-role bundling. Predefined roles like Buyer carry privileges that reach into other licensable products. For example, the Buyer role consumes an Enterprise Contracts Cloud license through a contract-terms privilege. Audit role-to-privilege mappings and use custom-scoped roles to avoid enabling services you never bought.
Yes. In the AFPA case, Oracle pursued a Purchase Order shortfall at full list price despite the customer's historical 86 percent discount. An unmanaged true-up can be repriced from your negotiated rate to list, so track named-user growth against entitlement continuously.
Oracle counts by privilege assignment, not by login. A Hosted Named User is anyone authorized to access the service, whether or not they log in, and a user holding multiple qualifying privileges is counted once. Dormant but provisioned accounts remain billable, so deprovision users you no longer need.
Oracle EPM Cloud is metered per hosted named user at $250 Standard or $500 Enterprise. The module crossover, the minimums, the Hyperion five-year comparison, and the one-way door.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
