Oracle EBS licensing is perpetual and module-based: each E-Business Suite module is priced per Application User — roughly $4,600–$5,800 at 2026 list for core modules — and every individual authorized to use a module needs a license, whether or not they log in. The database and middleware underneath are licensed separately. The two exposures that decide audit outcomes are uncounted self-service users and a database tier running beyond its restricted-use grant — both are controllable with an annual self-audit.
EBS estates are decades old, and their license positions drift: modules get switched on, self-service portals get rolled out to whole workforces, and databases quietly outgrow their restricted-use grants. Oracle's audit machinery is built to find exactly that drift. This guide sets out the metrics, the money, and the defense — and every pricing and policy figure below carries a source and a date.
Key takeaways
- EBS modules are licensed per Application User at roughly $4,600–$5,800 list for core modules — Financials at about $5,765 and Inventory at about $4,595 per named user — plus 22% of net license value in annual support (Oracle Applications Global Price List, 2026).
- Authorization, not activity, is what Oracle counts — every user with an active EBS responsibility needs a license even if they never log in, which is why end-dating dormant accounts is the cheapest compliance control in the estate.
- Self-service undercounts are the single largest EBS compliance gap — rolling iExpenses or Employee Self-Service out to a full workforce can create a multi-thousand-user shortfall against a few hundred licensed seats.
- The Oracle Database under EBS is licensed separately, and a restricted-use grant is void the moment that database serves custom schemas or third-party tools — the database tier drives the largest EBS back-licence claims.
- Across 600+ Oracle engagements, uncounted self-service and dormant users account for the majority of the removable exposure in a typical EBS audit claim (Oracle Licensing Experts engagement data, 2026).
- EBS 12.2 Premier Support runs through at least 2037 (Oracle, April 2026), so no support deadline forces a re-platform — a fact that strengthens every renewal, migration, and audit negotiation.
Recommendations by role
An EBS license position is owned by nobody by default: IT assigns responsibilities, HR rolls out self-service, DBAs enable options, and finance pays the support bill. Oracle audits the whole estate at once. Here is what each owner does first.
CIO / Head of Applications Strategy
- Commission an annual EBS self-audit — users, modules, database tier — so Oracle never knows your position better than you do.
- Put module activation under change control: one unlicensed module switched on in a test-turned-production instance is a standard audit finding.
- Use the 2037 Premier Support runway as negotiating strength — you are not under a deadline, and every Oracle proposal should be priced knowing that.
SAM / ITAM Manager Control
- Reconcile FND_USER and responsibility assignments against entitlements quarterly; end-date every dormant account — authorization is what gets counted.
- Inventory self-service module access against licensed counts before Oracle does; this is where the biggest gap almost always sits.
- Verify read-only users are technically locked to inquiry-only responsibilities — the 50–80% discount evaporates if a user can post a single transaction.
DBA / Infrastructure Stack
- Map every EBS database against its grant: restricted-use entitlements die the moment the instance serves non-EBS schemas or tools.
- Run an options usage check — Partitioning, Diagnostics Pack, Advanced Compression enabled by default are separately licensable and routinely claimed in audits.
- Document the architecture: DR servers, test clones, and reporting replicas all carry licensing consequences auditors will price.
CFO / Procurement Cost
- Benchmark before any EBS purchase or true-up — discounts of 40–60% off list are routine in negotiated transactions, and Oracle's first quote assumes you do not know that.
- Challenge the support base: right-sizing shelved licenses before renewal cuts the 22% annuity permanently.
- Never settle an audit claim at face value — audit claims are opening positions, and the counted "gap" usually shrinks under forensic review.
The Oracle EBS licensing framework: seven questions that decide your position
How does Oracle EBS licensing actually work?
Oracle E-Business Suite is licensed perpetually, module by module. Each module — Financials, Purchasing, Inventory, Order Management, HR — is a separate line item with its own metric and price, and the standard metric is the Application User: a named individual authorized to use that module. The definition is unforgiving — authorization is the trigger, not usage. A user with an active responsibility who has not logged in for two years still requires a license. You buy the license once, then pay Oracle 22% of net license value every year as support, which is where the lifetime cost actually accumulates.
End-dating dormant responsibilities is free and immediately reduces your countable population. Run the reconciliation quarterly — an account cleanup performed the week an audit letter arrives looks like evidence tampering; one performed every quarter looks like governance.
What does EBS licensing cost in 2026?
On Oracle's 2026 Applications Global Price List, core EBS modules list at roughly $4,600–$5,800 per Application User — Financials near the top at about $5,765, Inventory around $4,595, with Procurement and Order Management modules sitting lower (Oracle Applications Global Price List, 2026). Modules carry user minimums — commonly 5 or 10 users, with some self-service and hub products requiring far more. The arithmetic compounds fast: 500 Financials users represent about $2.9M in list license value and roughly $630K per year in support. List price is the start of the conversation, not the end — negotiated EBS transactions routinely close at 40–60% off list.
Oracle discounts against alternatives it can see. An EBS true-up priced alongside a credible third-party-support or migration evaluation closes materially deeper than one priced as a captive renewal. Build the alternative before you ask for the number.
Application User vs Named User Plus vs Processor — which metric applies where?
An EBS estate almost always carries two metric families at once. Application User covers the application modules — it counts named individuals per module, full stop. Named User Plus (NUP) is Oracle's technology metric for the database and middleware layer: it counts humans and devices with access, and carries per-Processor minimums — 25 NUP per Processor for Database Enterprise Edition. Processor licensing replaces user counting entirely and prices the hardware cores via the Core Factor Table; it becomes the practical choice when user populations are large or uncountable. The audit trap is assuming the application license covers the stack: it does not, and the two counts are tested separately.
| Metric | What it counts | Where it applies | Watch for |
|---|---|---|---|
| Application User | Named individuals authorized per module, regardless of usage | EBS application modules (Financials, SCM, HR…) | Dormant accounts and self-service rollouts inflating the count |
| Named User Plus | Humans + devices accessing the technology layer | Database and middleware under EBS (when full-use) | Per-Processor minimums (25 NUP/Processor for DB EE); devices count |
| Processor | Hardware cores × Core Factor Table | Large or uncountable populations; external-facing systems | Virtualization and DR architecture can multiply the core count |
| Custom Suite User | Named individuals across a negotiated module bundle | Custom Application Suite (CAS) agreements | Minimum-purchase thresholds; scope drift outside the defined bundle |
Why do self-service and read-only users create the biggest compliance gaps?
Because they scale by workforce, not by department. When an organization deploys iExpenses, iProcurement, or Employee Self-Service, every employee who can reach the portal needs a license for that module — even the one who files a single expense report a year. An estate licensed for 500 core users that opens iExpenses to an 8,000-person workforce has created a 7,500-user gap overnight, and Oracle's audit scripts will find it in the responsibility tables. Read-only users are the mirror-image opportunity: priced 50–80% below full-use licenses, but valid only when the user is technically confined to inquiry-only responsibilities. Oracle assesses what a user can do, not what they did — one transactional privilege and the discount is gone.
An HR or finance project rolling any self-service module out "to everyone" without a licensing review is the most expensive routine decision in an EBS estate. The go-live email costs nothing; the audit three years later prices every mailbox on it.
Oracle does not audit what your users did. It audits what your responsibility tables say they were allowed to do — and it prices the difference.
How is the database stack under EBS licensed?
Separately — always. Every EBS instance runs on an Oracle Database and middleware layer that carries its own entitlements. Many estates rely on restricted-use licenses bundled with EBS, which are valid only while the component exclusively serves the EBS application. The moment that database hosts a custom schema, feeds a third-party reporting tool, or gains an extra instance, the restricted-use grant is exceeded and full-use Database EE or SE2 licensing applies retroactively. Add the separately licensable options — Partitioning, Diagnostics Pack, Advanced Compression — that DBAs enable by default, and the database tier becomes the source of the largest EBS back-licence claims. Our Oracle Database licensing guide covers the full mechanics.
"Which exact database and middleware entitlements are included with our EBS licenses, under which restricted-use definitions, and in which ordering documents?" If Oracle cannot point to the document, assume the grant is narrower than your architecture — and verify before an auditor does.
When does a Custom Application Suite make sense?
A Custom Application Suite (CAS) is a negotiated bundle: Oracle groups your chosen EBS modules into one suite licensed under a single Custom Suite User count, so each licensed user can access every module in the bundle. There is no public price list — CAS deals are priced case-by-case and carry minimum-purchase thresholds. CAS suits estates where the same population genuinely uses many modules; it is poor value where usage is siloed, because you pay the blended rate for users who touch one module. The two contract points to defend are the module list (scope drift outside the defined bundle is unlicensed use) and the unit price at growth (fix the rate for future users at signature, or additions reprice at Oracle's discretion).
"Additional Custom Suite User licenses purchased during the term shall be priced at the per-user rate set forth in this Order Form, with the module scope of the Custom Application Suite fixed as listed in Schedule A and amendable only by written agreement."
How do you defend an Oracle EBS audit?
By holding your own count before Oracle builds one for you. An Oracle LMS audit of EBS concentrates on three areas: user counting (the FND_USER table and responsibility assignments, per module), module sprawl (functionality in use that was never licensed), and architecture change (the database tier, DR, and cloned environments). The forensic, evidence-based defense mirrors that: reconcile users quarterly and end-date dormant accounts; put module activation under change control; and audit the database grants annually. When the claim arrives, treat it as an opening position — audit claims are negotiable, the counted gap routinely shrinks under scrutiny, and the strongest settlements convert exposure into a restructured deal rather than a cheque. Our buyer-side audit defense practice exists for exactly this sequence, and the wider playbook is in our Oracle audit defense guide.
Across 600+ Oracle engagements, the average audit claim opens at 3–5× what the customer actually owes once dormant users, self-service scope, and database grants are forensically reviewed — and in EBS audits specifically, uncounted self-service and dormant users are the majority of the removable exposure (Oracle Licensing Experts engagement data, 2026).
Which EBS licensing posture fits your estate?
Application User per module, actively governed
The default and usually the cheapest posture: license each module for its real, reconciled user population, end-date dormant accounts quarterly, and hold the audit-ready count yourself.
Custom Application Suite
Worth pricing when one population genuinely works across many modules. Fix the future unit rate and the module scope at signature — both drift in Oracle's favor otherwise.
Right-sized mix with read-only tiers
License the full population for self-service modules, then cut cost with 50–80% cheaper read-only tiers for inquiry-only users — provided the technical restriction is airtight.
Processor licensing on the affected tier
When counting users is impractical — external-facing or high-churn populations — Processor licensing caps the metric argument, but verify core counts, virtualization, and the Core Factor Table math first.
There is no single correct posture — only the one that matches how your workforce actually touches EBS. The common error is licensing the original 2008 deployment and letting fifteen years of rollouts drift away from it.
What an ungoverned EBS estate costs at audit
Strengths and cautions of each EBS licensing approach
| Approach | Strength | Caution |
|---|---|---|
| Application User per module | Pay only for real users per module; transparent list pricing; easiest to right-size | Authorization-based counting punishes dormant accounts and unmanaged self-service rollouts |
| Custom Application Suite | One user count across a module bundle; simpler administration for multi-module populations | No public pricing; minimum thresholds; blended rate overpays for siloed users; scope drift risk |
| Read-only user tiers | 50–80% cheaper for inquiry-only populations; legitimate right-sizing for reporting users | Void if the user can transact; Oracle tests capability, not history — configuration must be airtight |
| Processor on the tech stack | Removes user-counting disputes; predictable for large populations | Core Factor Table math, virtualization, and DR can multiply cores; usually costlier for small counts |
Acronyms and key terms
- E-Business Suite (EBS)
- Oracle's on-premise enterprise application suite — Financials, Procurement, HR, Supply Chain, Manufacturing — licensed perpetually by module and user.
- Application User
- The EBS named-user metric — every individual authorized to use a licensed module requires a license, regardless of actual usage.
- Named User Plus (NUP)
- Oracle's technology metric counting humans and devices accessing the database or middleware, with per-Processor minimums (25 NUP per Processor for DB EE).
- Processor
- Oracle's hardware metric — licensable cores calculated via the Core Factor Table; replaces user counting where populations are large or uncountable.
- Custom Application Suite (CAS)
- A negotiated bundle of EBS modules licensed under a single Custom Suite User count, priced case-by-case with minimum-purchase thresholds.
- Restricted-Use License
- A database or middleware entitlement bundled with EBS, valid only while the component exclusively serves the EBS application.
- Self-Service User
- An employee accessing self-service modules such as iExpenses or Employee Self-Service — each requires a license for that module.
- Read-Only User
- A user technically restricted to inquiry-only responsibilities, licensable at a 50–80% discount — void if the user can perform any transaction.
- FND_USER
- The EBS foundation table of user accounts and responsibility assignments — the primary data source in an Oracle EBS audit.
- Module Sprawl
- The gradual activation of unlicensed EBS modules over years of operation — a standard Oracle LMS audit finding.
- Core Factor Table
- Oracle's published table of per-core multipliers used to convert physical cores into Processor license counts.
- Premier Support
- Oracle's full support tier — patches, security and regulatory updates — extended for EBS 12.2 through at least 2037.
Oracle EBS licensing FAQ
How is Oracle E-Business Suite licensed?
Oracle E-Business Suite is licensed perpetually, module by module, with each module priced on its own metric — most commonly Application User, the named-individual metric under which everyone authorized to use a module needs a license whether or not they log in. Core module list prices run roughly $4,600 to $5,800 per Application User on Oracle's 2026 Applications Global Price List, plus 22% of net license value in annual support. The Oracle Database and middleware under EBS are licensed separately; the application license never covers them.
What is the difference between Application User and Named User Plus in EBS?
Application User is the module-specific named-user metric for EBS applications: it counts individuals authorized to use that module only. Named User Plus is Oracle's technology metric, counting humans and devices accessing the underlying database and middleware, with per-Processor minimums. An EBS estate typically carries both — Application User licenses for the modules, and NUP or Processor licenses for the separately licensed database stack. Auditors test both counts, and the database side is the one buyers most often forget.
How much does Oracle EBS licensing cost in 2026?
On Oracle's 2026 Applications Global Price List, core E-Business Suite modules list at roughly $4,600 to $5,800 per Application User — Financials sits near the top at about $5,765 and modules such as Inventory near $4,595 — with per-module user minimums and 22% of net license value in annual support. A 500-user Financials deployment therefore represents roughly $2.9M in list license value plus about $630K per year in support before any discount. Discounts of 40 to 60% off list are routine in negotiated EBS transactions.
Do self-service users need Oracle EBS licenses?
Yes. Every employee who can access an EBS self-service module — iExpenses, iProcurement, Employee or Manager Self-Service — requires a license for that module, even if they log in once a year. This is the single largest EBS compliance gap: an estate licensed for 500 core users that rolls iExpenses out to an 8,000-person workforce has silently created a 7,500-user shortfall. Oracle audits count authorization, not activity, so end-dating unused responsibilities is the control that closes the gap.
Are read-only Oracle EBS users cheaper to license?
Read-only EBS licenses are typically priced 50 to 80% below full-use Application User licenses, but Oracle enforces the boundary strictly: a read-only user must be technically restricted to inquiry-only responsibilities, and a single transactional action re-classifies that user as full-use. Oracle audits assess what a user can do, not what they actually did, so the discount only survives an audit if the inquiry-only configuration is airtight and documented. Configured correctly, read-only tiers are a legitimate way to right-size a large reporting population.
Is the Oracle Database under EBS licensed separately?
Yes. E-Business Suite always runs on an Oracle Database and middleware stack that carries its own licenses — either restricted-use entitlements limited strictly to the EBS application, or full-use Database Enterprise Edition or SE2 licenses. The classic audit finding is a technically full-use database serving custom schemas, third-party tools, or extra instances that the restricted-use grant does not cover, plus separately licensable options such as Partitioning or Diagnostics Pack enabled by default. The database stack, not the application modules, produces the largest EBS back-licence claims.
What does an Oracle LMS audit of EBS focus on?
Oracle LMS audits of E-Business Suite focus on three areas: user counting, module sprawl, and architecture change. Auditors pull the FND_USER table and responsibility assignments to count every authorized user per module, look for modules in use that were never licensed, and examine the database tier for full-use deployment beyond a restricted-use grant. The buyer-side defense is an annual self-audit of the same data: end-date dormant users, disable unlicensed modules, and reconcile the database stack before Oracle counts it for you.
How long will Oracle support E-Business Suite?
Oracle has extended Premier Support for E-Business Suite 12.2 through at least 2037 under its Continuous Innovation model — the ninth consecutive annual extension, announced in April 2026. EBS customers on 12.2 keep receiving patches, security fixes, and regulatory updates with no extended-support surcharge. That runway means there is no support deadline forcing a move to Fusion Cloud, and it strengthens every EBS customer's negotiating position on renewals, migrations, and audit settlements.
Methodology & sources
The metric definitions, list prices, and support-lifecycle dates in this guide are drawn from Oracle's published 2026 price-list and lifetime-support documentation and from Oracle Licensing Experts engagement data across 600+ Oracle negotiations and audits. Proprietary figures are labelled "Oracle Licensing Experts benchmark, 2026" or "OLE model, 2026" and reflect outcomes from buyer-side advisory work; they are directional ranges, not guarantees. Oracle revises its price list and support policy periodically — always confirm the current figure against the live Oracle document for your region before building a business case. For deeper detail, see our Oracle EBS licensing guide, our EBS user licensing models breakdown, and our buyer-side Oracle compliance review and license optimization services.
- Oracle Corporation, Oracle E-Business Suite Applications Global Price List, 2026 — module list pricing, metrics, and licensing minimums.
- Oracle Corporation, EBS 12.2 Premier Support Extended Through At Least 2037, April 2026 — the ninth annual Continuous Innovation extension.
- Oracle Corporation, Oracle Lifetime Support Policy: Oracle Applications, 2026 — Premier, Extended, and Sustaining Support definitions.
- Oracle Licensing Experts engagement data, 2026 — EBS audit claim composition, self-service exposure patterns, and negotiated discount ranges across 600+ engagements.
Download this guide as a PDF
Take the full Oracle EBS Licensing Guide into your next planning session — the metric map, the 2026 module pricing, the self-service and database-stack traps, and the audit-defense sequence in one printable brief. We also review your specific EBS position on request.
Request the PDF & an EBS license review →Keep reading
Free weekly Oracle briefing
EBS lifecycle alerts, audit-defense intelligence, and application licensing tactics — from former Oracle insiders.
Know your EBS position before Oracle prices it for you
Get an independent, buyer-side review of your Oracle EBS estate — the user counts Oracle will test, the self-service exposure hiding in your responsibility tables, and the database grants that decide the largest claims. In one anonymized engagement, forensic review cut a manufacturer's opening EBS audit claim from $6.5M to under $2M. We have advised on $1.8B of Oracle spend and cut costs an average of 38%.