1. EBS Suites and Licensing Principles
Oracle EBS organises modules into functional suites — collections of related applications. It's critical to understand that buying a suite isn't an "all-you-can-use" buffet of every module in that suite. Licences still apply per module or per specific metrics. Some suites offer shared licensing, while others require a separate licence for each piece.
| Suite | Key Modules | Shared Licence? | Primary Metric |
|---|---|---|---|
| Financials | GL, AP, AR, Fixed Assets, Cash Management | No — modules licensed separately | Application User (named) |
| HRMS | Core HR, Payroll, Time & Labour, Self-Service HR | Some employee-based overlap; Payroll separate | Employee count |
| Supply Chain | Inventory, Order Management, WMS, ASCP | Rarely — nearly all separate | Mix of named user and transaction-based |
| Procurement | iProcurement, Sourcing, iSupplier, Contracts | Partially — self-service may overlap | Mix of employee and professional user |
| Projects | Project Costing, Billing, Management, Contracts | No — each component is distinct | Named user (role-based) |
Read our ultimate updated guide, Oracle E-Business Suite Licensing Guide — 2026 Edition. For a quicker overview, see Oracle EBS Licensing Basics.
2. Licensing Oracle Financials Modules
Oracle Financials is one of the most widely deployed EBS suites, featuring modules such as General Ledger, Accounts Payable, Accounts Receivable, and more. Each Financials module carries its own licence requirements, usually tied to named users. In practice, if a user has a responsibility for a particular Financials module, that user needs to be counted against a licence for that module.
| Module | Metric Type | How Licensing Works |
|---|---|---|
| General Ledger | Application User | Counts each user with GL responsibilities. Typical named-user licensing. |
| Accounts Payable | Professional User | Full AP users (managers, clerks with entry/update roles) require licences. Inquiry-only users may qualify for read-only. |
| Accounts Receivable | Professional User | If a user can create or manage invoices in AR, they count as a licensed AR user. |
| Fixed Assets | Named User | Same named-user approach as other Financials modules. |
| Cash Management | Application User | Users with bank reconciliation or cash management responsibilities need licences. |
| Collections | Functional User | Typically counts collectors or users accessing Collections functionality. |
For read-only licensing options, see Oracle EBS Read-Only User Licence.
3. Licensing HRMS and Payroll Modules
Unlike Financials, Oracle's HRMS modules use employee-based metrics rather than per-named-user metrics. Licensing is based on the number of employees or workforce size managed in the system, not just how many people log in. This surprises many teams during audits — even employees who never directly use EBS might count toward your licence if their records reside in the HR module.
| Module | Metric | Key Points |
|---|---|---|
| Core HR (HRMS) | Employee count | Licensed per employee in the HR database. Every person whose data is in HR counts, regardless of system login. |
| Payroll | Payroll employees | Counts each employee or worker paid via Payroll. Includes contractors if paid through Oracle Payroll. Always a separate licence from Core HR. |
| Time & Labour (OTL) | Named users | Licensed per user of the timekeeping system. Counts anyone who can enter or approve time cards. |
| Self-Service HR | Employee User | Cheaper licence for employees using self-service features (personal info, benefits). Still counted per employee accessing the portal. |
Are You Over-Licensed on EBS Modules?
Many enterprises pay for EBS modules they no longer use, or licence full-use users who only need read-only access. Our independent Oracle advisers can review your EBS module licensing, identify optimisation opportunities, and reduce costs by 20–40%. Fixed-fee engagements. No ties to Oracle.
4. Licensing Supply Chain & Manufacturing Modules
Licensing for Oracle's Supply Chain Management (SCM) and manufacturing modules is a mix of user-based and transaction-based metrics. Many core SCM modules (Inventory, Purchasing) use named-user licences, but advanced or high-volume modules (Order Management, warehouse systems) use business metrics such as orders processed or machines deployed.
| Module | Metric Type | Licensing Notes |
|---|---|---|
| Inventory | Named User | Counts each user with inventory responsibilities — managers, material planners, anyone using the Inventory module. |
| Order Management | Order Lines (transactional) | Licensed by number of order lines processed annually. Must predict volume; exceeding licensed count requires true-up. |
| Purchasing (Core) | Professional Users | Counts procurement professionals (buyers, managers) as named users based on responsibility mapping. |
| Warehouse Management (WMS) | Named Users | Counts warehouse operators and managers. May include RF/barcode device usage considerations. |
| Advanced Supply Chain Planning (ASCP) | Processor or Named User | High-value module licensed by either CPUs/processors it runs on or by named planning users. |
5. Licensing Procurement Modules
Oracle's procurement suite extends beyond core Purchasing to include self-service and supplier-facing modules. The key is to differentiate who in your organisation uses which procurement tool and how that translates to Oracle's licensing definitions — internal employees, external suppliers, and different metric types all apply.
| Module | Primary Metric | Notes |
|---|---|---|
| iProcurement (Self-Service) | Employee Users | Licensed by number of employees with requisitioning access. Broad user base — many employees create purchase requests. Priced lower per head than professional users. |
| Sourcing | Power Users (Named) | Licensed per sourcing professional. Only procurement specialists organising auctions/RFQs need licences — usually a small, controlled pool. |
| iSupplier Portal | Supplier Users / Partners | Often included with Purchasing or licensed by external supplier users. External user access must be managed closely. |
| Procurement Contracts | Document Count or Users | May use a document-based metric (count of contracts managed) or be tied to contract manager roles. Specialised approach. |
Notice the balance between internal and external considerations. iProcurement covers a broad employee base with a cheaper self-service licence, while Sourcing focuses on your internal procurement team with higher-cost professional licences. iSupplier involves users outside your company entirely. Always delineate between these user groups to stay compliant.
6. Licensing Projects Suite Modules
Oracle's Projects Suite helps manage project finances and contracts, and it's composed of multiple integrated modules with varying licensing metrics. Projects licensing is very role-driven: a project cost accountant needs a different (often cheaper) licence than a project manager who uses advanced functionality.
| Module | Metric / Licence Type | Notes |
|---|---|---|
| Project Costing | Named Users | Counts each user performing costing activities (project accountants entering costs). |
| Project Billing | Named Users | Counts users generating project invoices or billing events. |
| Project Management | Professional Users | Licensed per project manager or planner. Higher-tier (more expensive) licence for advanced PM functionality. |
| Project Contracts | Document-based or Roles | Tied to number of project contracts managed or the users who author/manage contracts. |
7. Shared vs Separate Licensing: Suite Scenarios
One of the most common misconceptions in EBS licensing is that belonging to a suite unifies the licensing for all modules. In reality, some modules share certain entitlements while others always require their own licence.
| Suite | Do Modules Share a Licence? | Key Exceptions |
|---|---|---|
| Financials | Partially (limited). Core modules sometimes sold together, but usage tracked per module. | Users accessing multiple Financials modules typically need per-module licences. |
| HRMS | Mostly shared via employee-based count. Core HR and Self-Service HR often fall under one employee metric. | Payroll is always separate — licensed per paid employee, distinct from Core HR. |
| Procurement | Partially. iProcurement may cover multiple self-service features via an employee licence. | Sourcing and Procurement Contracts are separate add-ons requiring their own licences. |
| Supply Chain | Rarely shared. Nearly all SCM modules licensed separately. | A "Supply Chain suite" deal may bundle pricing, but compliance is tracked per module. Manufacturing modules are always separate. |
| Projects | No. Each component is distinct. | Costing, Billing, Management, and Contracts each require separate entitlements. |
A manufacturing company purchased an "Oracle Financials Suite" bundle, assuming it covered all Financials modules for all users. During an Oracle audit, it was revealed that while the bundle pricing covered General Ledger and Accounts Payable, the company had also enabled Cash Management and Advanced Collections without separate entitlements. The audit found 85 users accessing unlicensed modules. Result: A six-figure true-up for the unlicensed modules, plus retroactive support fees. The lesson: always verify which modules are explicitly included in any suite deal, and lock down access to modules you haven't licensed.
Need clarity on which EBS modules you're actually entitled to use?
Oracle Licence Management →8. Optimising EBS Licence Usage Across Suites
Many organisations over-licence or under-utilise what they've bought, usually because EBS responsibilities don't perfectly match purchased entitlements. With cleanup and governance, you can optimise licensing and potentially save hundreds of thousands of dollars — or at least close compliance gaps before Oracle finds them.
| Optimisation Action | Savings Potential | Why It Helps |
|---|---|---|
| Remove unused responsibilities | 💰 High | Immediately reduces full-access (professional) user counts. Many organisations drop dozens of expensive licences after cleanup. |
| Responsibility mapping review | 💰 High | Ensures you're not over-licensing. If someone only needs inquiry access, don't give them an update role that forces a higher licence. |
| Reclassify to read-only | 💰 High | Users who only view data can be moved to read-only licences at 40–60% of the cost. See EBS Read-Only User Licence. |
| Employee metric review (HR/Payroll) | 🔄 Medium | Verifies that employee counts are accurate. Removing duplicate or inactive records lowers the count. |
| Integration account review | 🔄 Medium | Technical/integration accounts set up as full users consume licences unnecessarily. Reconfigure to eliminate "ghost" users. |
| Centralise module access approvals | 🔄 Medium | Prevents managers from handing out responsibilities casually. A process that triggers a licence check before granting access avoids over-allocation. |
| Monitor transaction-based metrics quarterly | 🔄 Medium | Tracks order lines, employee counts, etc., to catch limit breaches before an audit forces a true-up. |
- Audit user responsibilities quarterly. Pull a report of all EBS users and their assigned responsibilities. Remove any responsibility that isn't needed. Fewer responsibilities = fewer licences required.
- Reclassify users to lower-cost tiers. Move users from Professional/full-use to Self-Service, Employee, or read-only categories wherever their actual activity permits. Reserve expensive licences for genuine transactional users.
- Align HR data with licensing. Remove terminated employees from EBS HR. Ensure your headcount reflects only the active workforce. Each extra employee record can increase your HRMS licence obligation.
- Audit custom integrations. Customisations or integrations may use modules in the background (e.g., a custom app writing into Inventory tables). Ensure indirect usage is accounted for in your licensing — or adjust the integration.
- Monitor business metrics. Track order lines, payroll counts, revenue bands, and employee totals quarterly. Set internal alerts at 90% of licensed capacity. Early warning gives you time to optimise or budget for expansion.
Facing an Oracle EBS Audit?
Oracle's audit teams verify module-by-module compliance, not suite-by-suite. If you've received an audit notice — or want to prepare before one arrives — our independent advisers can validate your module entitlements, challenge incorrect findings, and negotiate on your behalf.
💡 5 Expert Takeaways
1. Every EBS module has its own licensing metric. Buying a suite doesn't give blanket access — track usage module-by-module.
2. Financials and Supply Chain modules are heavily user-based. If someone has the responsibility in EBS, assume they need a licence for that module.
3. HRMS and Payroll licensing are tied to workforce size, not system usage. Even non-users can drive up costs if they're in the system.
4. Projects and Procurement modules use a mix of metrics — named users, employee counts, and document counts. Manage different measurement types within these areas.
5. Optimising starts with aligning EBS setup to actual needs. Regularly review responsibilities, user counts, and business metrics. The easiest savings come from removing needless access and keeping data clean.