Contents
Key takeawaysHow EBS is licensed and pricedThe license metricsWhat the database costsHow the metric shapes costSelf service rolloutsHow to check your positionWhat we see in reviewsWhat Oracle will saySupport and FusionWhat to do nextFAQOracle E-Business Suite is licensed module by module on metrics such as Application User and Employee, and the database underneath is licensed separately, usually for more. The metric you accept at purchase sets your cost for a decade, because metrics rarely move back down.
- Every module is its own line. EBS has no suite license; each module carries its own quantity and metric, and the database is licensed separately.
- The database usually costs more. A two node, 32 core production database is $760,000 of Enterprise Edition list before options, and over $1.3 million with a typical option stack.
- Authorization is what counts. An Application User is anyone authorized on a module, so one person on four modules is four licenses.
- Reconciliation pays first. Buyers who deprovisioned dormant users before renewal cut Application User counts by 20 to 35 percent.
- The restricted use grant is narrow. It covers unmodified EBS only, so reporting schemas and warehouse feeds on the instance need full licenses.
- Changing the metric is expensive. Oracle adds quantity on your current metric within days, while a new metric needs a new order priced against current list.
How is Oracle E-Business Suite licensed, and what does the price list show?
Oracle E-Business Suite is licensed module by module. Each module sits on its own line of your ordering document with a quantity and a metric, such as Application User, Employee or a transaction volume. There is no suite license, and the Oracle Database underneath is licensed separately, usually for more money than the application lines.
The line structure matters because Oracle audits and prices findings line by line. A module missing from your order is unlicensed, however closely it belongs with modules you did buy. The full catalog of modules and families is in our EBS module list.
What does the current EBS price list show?
Oracle publishes the E-Business Suite Applications Global Price List on its website. The September 10, 2026 edition prices the most common modules as shown below. Annual Software Update License and Support is 22 percent of the license price.
| Module | List price | Metric | Minimum | Annual support at list |
|---|---|---|---|---|
| Financials, Purchasing, Order Management, Inventory Management (each) | $4,595 | Application User | 5 | $1,010.90 |
| iProcurement | $115 | Application User | 100 | $25.30 |
| Human Resources | $185 | Employee | 100 | $40.70 |
| Payroll | $225 | Employee | 500 | $49.50 |
| Self Service Human Resources | $40 | Employee | 100 | $8.80 |
| Internet Expenses | $6 | Expense Report | 1,000 | $1.32 |
The transactional modules cost $4,595 per Application User, while the HR modules cost $40 to $225 per Employee and count everyone. Oracle discounts license fees from list, and support is charged every year on the net fee you pay.
The Negotiation, and the Baseline That Ends It
Which license metrics does Oracle use for EBS modules?
EBS uses five metric families: Application User, Employee, transaction volume, company financials such as revenue, and the restricted use technology bundled with the applications. Each grows for a different reason, and each has its own typical failure.
| Metric | What it counts | How it grows on you | The common trap |
|---|---|---|---|
| Application User | Named individuals authorized per module | Only when people are added, so it is the most controllable | Leavers and dormant accounts never deprovisioned |
| Employee | The population the module serves | Automatically, with headcount and acquisitions | Contractors and part timers counted as employees |
| Volume: expense reports, order lines | Annual transaction volume in bands | Whenever volume crosses a band boundary | No one owns the counter, so bands are breached unnoticed |
| Revenue or cost of goods sold | Reported financial figures | With business performance, outside IT control | Acquisitions reprice the line with no usage change |
| Restricted use technology | The embedded database and tools, for EBS only | The moment a non EBS workload joins | A reporting schema converts it to a full license need |
Oracle defines an Application User as an individual authorized to use the programs, whether or not they are actively using them. One person authorized on four modules therefore needs four licenses.
Who counts toward the Employee metric?
Oracle's definition covers full time, part time and temporary employees, plus agents, contractors and consultants who access, use or are tracked by the programs. Many buyers assume contractors sit outside the count. Under the standard definition they sit inside it, unless your order says otherwise.
Why do volume metrics get breached without warning?
Volume metrics such as Expense Report and Order Line count transactions processed during a 12 month period, and your order licenses a fixed quantity or band. Any rolling 12 months above that quantity is a shortfall. Finance owns the process and IT owns the license, so the counter often has no owner.
Say you license 30,000 expense reports a year, $180,000 at the $6 list price. An acquisition lifts volume to 36,000. The 6,000 extra reports cost $36,000 of license at list plus $7,920 a year in support, and the shortfall dates from the month the limit was crossed.
Oracle EBS Licensing Brief
Map your modules and metrics, test the restricted use boundary and price the support decision.
Get the white paper →What does the database under EBS cost?
The database is usually the larger number. EBS application lines are counted in users, while a full use Oracle Database license is counted in processors at technology list prices. A two node production database on 32 Intel cores, at the 0.5 core factor, needs 16 processor licenses and $760,000 of Enterprise Edition list before any option.
Production EBS databases rarely run bare Enterprise Edition. Two nodes usually means Real Application Clusters, and most DBA teams also run the Diagnostics and Tuning Packs. Prices are from Oracle's September 15, 2026 technology price list.
| Component | List per processor | 16 processors at list |
|---|---|---|
| Database Enterprise Edition | $47,500 | $760,000 |
| Real Application Clusters | $23,000 | $368,000 |
| Diagnostics Pack | $7,500 | $120,000 |
| Tuning Pack | $5,000 | $80,000 |
| Total license | $83,000 | $1,328,000 |
| Annual support at 22 percent | $18,260 | $292,160 |
That stack passes $1.3 million at list before a single application user is counted. Line by line prices are in our technology price list guide, the counting rules in the database licensing guide, and the processor arithmetic in the core factor guide.
What does the restricted use database license cover?
Oracle's Applications Licensing Table grants a restricted use license for Database Enterprise Edition and Internet Application Server Enterprise Edition with EBS. It may be used only to run the licensed E-Business Suite applications, deployed without modification. The same table lists what needs full use licenses instead:
- Schema changes. Adding or changing tables, columns, stored procedures or triggers in the EBS application schema needs full Database and Internet Application Server Enterprise Edition licenses.
- Custom middle tier work. Custom or modified reports, forms, workbooks and Java pages need full Internet Application Server Enterprise Edition licenses for the users or processors they are deployed to.
- Other workloads. Any use of the database or application server outside the licensed EBS programs.
The breaches come from ordinary work: a BI reporting schema, a custom application on the same instance, a data warehouse feed. Each turns the bundled right into a full license requirement at technology prices. Our EBS compliance guide covers how auditors test that boundary.
Application User counts authorization on an EBS module. Named User Plus, from the technology price list at $950 per user, counts individuals and devices authorized on the database, measured at the front end of any multiplexing layer.
You can be fully compliant on Application Users and badly exposed on the database beneath them. That split is the most common shape of EBS audit finding we see.
How does the metric change your EBS cost as the company changes?
Over ten years, the metric on a line changes your cost more than anything else in the order. Application User grows only when you add people, while Employee, volume and revenue metrics grow with headcount, transactions and financial results.
Metrics also move mostly upward. Oracle will add quantity on your existing metric within days, while changing the metric itself needs a new ordering document and a repricing against current list.
| Scenario | Application User | Employee | Revenue based |
|---|---|---|---|
| Day one: 4,000 staff, 250 real users | 250 licenses | 4,000 licenses | Priced on current revenue |
| You acquire a 2,000 person business | Add only users who log in | Add 2,000 automatically | Reprices on combined revenue |
| You outsource payroll processing | Remove those users at renewal | No relief, the population is unchanged | No relief |
| Revenue doubles, usage flat | No change | No change | Cost doubles |
| Where it hurts most | Dormant accounts you forgot | Growth and acquisitions | Success itself |
Put prices on the acquisition row. Human Resources lists at $185 per Employee, so 4,000 staff is $740,000 at list. Acquiring a 2,000 person business adds $370,000 of license at list and $81,400 a year of support, whether or not any of the new people use the module.
When does the Employee metric make sense?
The Employee metric has two sound uses. The first is modules almost everyone uses, where per head pricing beats counting users and removes the administration. The second is a stable or shrinking workforce in a mature business, where it buys predictability. Anywhere else it pays off only if your headcount falls.
The discount is applied once. The metric is applied every year you run the module.
Why the discount percentage should not be your first fight
The usual advice for an EBS purchase is to push hardest on the discount off list. We see it differently. The discount lowers one license fee and the support base, but the metric decides how many units you pay for after every acquisition and reorganization.
Settle the metric definition, the counted population and the reduction rights first, then negotiate the discount. Go back to the Human Resources example. Ten extra points of discount on $740,000 saves $74,000, once. The 2,000 person acquisition adds $148,000 of license even at 60 percent off, plus support on it every year after. Our EBS negotiation guide covers the sequence.
Which five questions should be answered before a module line signs?
Get each answer in writing before signature. Afterward they are terms you live with.
- Headcount. What happens to the line if headcount doubles and usage does not?
- Acquisitions. Do acquired populations land inside the metric automatically, and at what unit price?
- Divestitures. Is there a written right to reduce quantities and support when you sell a business?
- Outsourcing. Does the metric follow work you outsource, and whose staff are counted then?
- Definition. What does the contract say, word for word, and does it match the definition the sales team described?
Which contract terms should you ask for?
- The metric definition in the order. Copy the definition and counted population into the ordering document, so a later policy revision cannot widen it.
- A divestiture reduction right. Without one, Oracle's support policies reprice the remaining licenses on an order when you terminate part of it.
- A price hold on added quantities. The same unit price and discount for extra users until the next renewal, as set out in our note on price holds and uplift caps.
Why does a self service rollout create an EBS license gap?
Rolling iProcurement or Self Service HR out to the whole workforce authorizes the whole workforce, unless the contracted metric says otherwise. A convenience project becomes an enterprise wide license event, usually with no one from licensing involved.
Say you employ 6,000 people and 400 of them raise requisitions. At $115 per Application User, iProcurement for those 400 costs $46,000 at list. Give every employee access and the requirement becomes 6,000 users, or $690,000 at list, with $151,800 a year of support on top.
Self Service HR is priced per Employee on the current list, so it already counts the whole population. If your order licenses it on another metric or for a named group, read that wording before HR switches it on for everyone.
How do you check your own EBS license position?
Start from the data Oracle's auditors would use: the user, responsibility and login records in the EBS FND tables, and the database's own feature usage history. Pull everything on the same day so the counts reconcile.
| Question | Where to look | What it tells you |
|---|---|---|
| Who is authorized on which module | FND_USER joined to FND_USER_RESP_GROUPS_DIRECT and FND_RESPONSIBILITY | Application Users per module, the number Oracle counts |
| Who is dormant | LAST_LOGON_DATE and END_DATE in FND_USER | Accounts with no login for 12 months, and leavers never end dated |
| Which responsibilities are used | FND_LOGIN_RESPONSIBILITIES, when the Sign-On:Audit Level profile is set to Responsibility or Form | Access granted but never exercised |
| Volume counts | AP_EXPENSE_REPORT_HEADERS_ALL and OE_ORDER_LINES_ALL over 12 months | Headroom before the next band |
| Restricted use boundary | DBA_USERS, DBA_OBJECTS and DBA_DB_LINKS on each EBS instance | Custom schemas, added objects and outbound feeds |
| Database options in use | DBA_FEATURE_USAGE_STATISTICS | Options and packs that need processor licenses |
Run the database checks before Oracle's audit scripts do. Our guide to the feature usage report explains how to read the output.
What have we seen in recent EBS license reviews?
Across the roughly 25 to 35 Oracle E-Business Suite engagements I reviewed in 2024 and 2025, two problems came up again and again. The user list was inflated, and the database boundary was leaking.
- Dormant users. Where no recent review had been done, Application Users with no login for a year averaged 30 to 40 percent of the licensed total, all renewing at full rate.
- Reconciliation results. Buyers who reconciled and deprovisioned before renewal cut their Application User counts by 20 to 35 percent.
- Boundary breaches. Roughly half the environments we reviewed had crossed the restricted use grant, through reporting schemas, custom applications or warehouse feeds.
The dormant share has a price. Say you hold 800 Financials Application Users bought at 60 percent off list, so each cost $1,838 net and carries about $404 a year in support. If 280 of them are dormant, you pay about $113,000 a year to support licenses no one uses.
Cutting that support takes planning, because Oracle reprices the remaining licenses on an order when you terminate part of it. The surer gain comes from reassigning dormant licenses to new starters instead of buying more.
What will Oracle's account team say, and how should you answer?
These are the lines we hear most often in EBS renewals and audits, with a reply to each.
- "Your reporting schema breaks the restricted use license, so you need full Enterprise Edition everywhere." Ask which instance and which objects, and limit the discussion to those servers. Moving the reporting workload off the EBS instance is often cheaper than licensing it.
- "If you leave support, coming back will be expensive." That is accurate, so put it in your comparison. Price the 150 percent reinstatement fee against the years of savings and your upgrade plans.
- "Commit to Fusion now and we will credit your EBS support." Ask for the credit amount, its duration and the subscription ramp in the ordering document, quoted separately from the EBS renewal.
- "Moving HR to the Employee metric will make compliance simpler." It will, and it will also count every contractor and every acquired employee. Ask for a five year cost at your planned headcount on both metrics before you agree.
Should you keep Oracle support on EBS or move to third party support?
It is a real decision with real costs either way. EBS is mature, and Oracle has moved the Premier Support date more than once, most recently extending Premier Support for EBS 12.2 through at least 2037 in March 2026. Third party support runs at roughly half the Oracle fee.
The losses are also real: no new patches from Oracle, no upgrade path, and no route back without cost. To come back, Oracle charges 150 percent of the last annual support fee for the whole lapsed period, plus the fee for the next 12 months. Weigh both sides in our third party support analysis and the support cost reduction strategies.
How does a future Fusion move affect the license review?
The eventual Fusion migration is its own negotiation on its own calendar. It starts from the same module inventory the license review needs, and Oracle will size its proposal from whatever footprint you share. Reconcile first, then compare against the Fusion modules list.
What to do next
- Reconcile users now. Match Application Users against login activity and deprovision dormant accounts before the renewal prices them again.
- Audit the restricted use boundary. List every schema, feed, database link and custom application on each EBS instance, then move or license whatever falls outside the grant.
- Read every metric definition. Compare the wording in your orders with Oracle's current definitions, and answer the five growth questions in writing before any new module line signs.
- Give each volume counter an owner. Someone in finance or order management should report expense report and order line volumes against the licensed band every quarter.
- Price the support decision. Compare Oracle support with third party support at about half the fee, using your real patch needs and upgrade plans. Our Oracle practice can run the review with you.
Want a second opinion on your Oracle position? Our Oracle licensing consultants are former Oracle insiders who now work only for buyers.
Frequently asked questions
How is Oracle E-Business Suite licensed?
Module by module. Each module is a separate line with its own quantity and metric: Application User for named authorized people, Employee for the population a module serves, volume metrics for transactions and revenue metrics for financial figures. The database is licensed separately on technology metrics and usually costs more.
How much does Oracle E-Business Suite cost per user?
On Oracle's September 2026 price list, Financials, Purchasing and Order Management list at $4,595 per Application User, and HR modules at $40 to $225 per Employee. Support adds 22 percent of the net license fee each year, and the database is priced on top.
What is the difference between Application User and Named User Plus?
Application User counts authorization on an EBS module; Named User Plus counts individuals and devices authorized on the database, from a different price list. Clean Application User counts say nothing about the database, and that gap is where EBS audit findings usually land.
What does the EBS restricted use database cover?
Only the licensed EBS applications, running without modification. A reporting schema, custom application or warehouse feed on the same instance means full technology licensing at list. Roughly half the environments we reviewed had crossed that line, usually through routine work never checked against the grant.
What is the fastest EBS licensing saving?
Reconciling dormant users. Application Users who had not logged in for a year averaged 30 to 40 percent of licensed totals in our reviews. Oracle counts authorization, so removing access is what lowers the count, and ending leavers promptly is the cheapest control you have.
Should EBS use the Employee metric?
Only for modules nearly everyone uses, where per head pricing beats counting, or for stable and shrinking workforces that value predictability. Elsewhere the count rises with every hire and acquisition, with no relief when you outsource work or usage falls.
Is third party support viable for EBS?
Yes, for many EBS customers, but it is a trade. You pay roughly half the Oracle fee and give up new patches and the upgrade path, and returning to Oracle carries a reinstatement fee. Decide on your patch needs and Fusion timeline, priced with real numbers rather than assumed.