JD Edwards pricing, five metrics and a 2037 clock
JD Edwards does not price on job titles: it prices on application users, employees, connected devices, expense reports, and UPK developers, each with its own minimum, and the metric on your ordering document decides whether headcount growth costs money automatically. The professional, casual, and read only ladder buyers expect belongs to pre Oracle contracts and other vendors.
Prepared by Redress Compliance · August 7, 2026 · Oracle advisory. Based on 20 to 30 JD Edwards estates reviewed 2024 to 2025.
Executive summary
The employee metric is a ratchet with a wide net.
It counts everyone the programs track, not just people who log in, so a payroll or HR module tracks the whole workforce and the whole workforce counts, contractors, consultants, and agents included, with a minimum of all employees: an acquisition raises the bill with no new deployment.
And estates counting badge holders only are undercounted by design.
In our reviews, employee quantities sat frozen at the original order's headcount years after two acquisitions.
The leaver seats are the fastest money.
An application user is anyone authorized, not anyone active, so a dormant account never disabled is still a licensed user at audit: application user counts carried 20 to 35 percent of seats attached to people who had left or moved.
And modules stayed licensed at sites that had stopped running the process, carrying dead support.
Right sizing users and modules cut the maintenance base 15 to 30 percent before any renewal talk.
The minimums and the devices are the quiet lines.
Five application users per component, fifty connected devices, one thousand expense reports: the floors bind small deployments, and the connected device metric, warehouse scanners, weighbridges, and shop floor terminals pushing data into JD Edwards.
Is a licensable line that is rarely on anybody's inventory.
The database underneath licenses separately, often on an application specific full use grant that restricts what else may touch the instance.
The 2037 support commitment changes every exit argument.
Oracle has committed Premier Support for EnterpriseOne 9.2 through at least 2037, which removes the forced migration clock entirely: the Fusion conversation, the third party support comparison, and the renewal all price against a platform with a decade of committed support.
On your calendar rather than Oracle's.
Support runs at roughly 22 percent of net license fees across everything on the contract, running or not.
The five metrics, minimums, and list anchors
| Metric | What it counts | The minimum | The list anchor |
|---|---|---|---|
| Application user | Each individual authorized on the licensed programs | 5 per component | About $4,595 for Financials or Distribution Management |
| Employee | Everyone the programs track, contractors and agents included | All employees | About $185 for HR, $225 Payroll, $50 Health and Safety |
| Connected device | Devices exchanging data with no human interaction | 50 devices | Per device, module dependent |
| Expense report | Reports processed in a rolling twelve months | 1,000 reports | About $6 per report |
| UPK developer | People authorized to build simulations and documentation | 1 developer | About $17,500 |
The traps are wording problems, not counting problems.
Tracked by the programs means the workforce, not the login list; the same definition pulls in contractors and outsourced staff; authorized means the dormant account counts until disabled; and the connected devices on the shop floor are a licensable metric with a fifty device floor.
Each survives years of internal reviews precisely because the internal review counts what it can see, and the definitions count more.
Modules, the database, and the support line they feed
Module licensing is straightforward and the leak is not: you license the functional modules the business runs and pay support across everything on the contract whether the module runs or not, which is how sites that stopped a process a decade ago still fund 22 percent annually on its module.
The database beneath is its own line, separately licensed and often on an application specific full use grant whose boundary a reporting schema or shared workload silently crosses, and the technology foundation layer risks buying middleware the estate may already hold.
The counting detail per metric sits in the JD Edwards user types guide, and estates on pre Oracle paper check the concurrent licensing note before conceding any modern metric conversion.
The Oracle JD Edwards licensing brief
The five metrics worked end to end: the definitions, the minimums, the module and database boundaries, and the renewal sequence on the 2037 clock.
Get the white paper →The 2037 clock, and what it prices
The Premier Support commitment through at least 2037 for EnterpriseOne 9.2 is the strategic fact the whole estate prices against: there is no forced migration deadline, so the Fusion conversation happens on business merits rather than support panic.
The third party support comparison runs against a decade of committed Oracle patches rather than a closing window, and every urgency framed sales motion loses its clock.
The optimization sequence, users, modules, employees, and devices corrected before the renewal, is worked in the JD Edwards cost optimization guide, and the cloud path, where it genuinely fits, in the cloud migration licensing analysis.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across JD Edwards estates, 2024 to 2025
Across roughly 20 to 30 Oracle JD Edwards estates Fredrik Filipsson reviewed between 2024 and 2025, the licensed quantities were heavier than actual usage in most cases:
Application user counts never reduced after restructures, attached to people who had left or moved.
Held at the original order's headcount, years and two acquisitions after the definition said otherwise.
The two directions of the employee metric finding deserve equal weight: quantities frozen below the definition's reach are audit exposure accumulating silently.
And quantities above the real tracked population are support paid on phantoms, which is why the reconciliation runs both ways before any renewal.
The dead module cleanup completes the pass, terminating support on lines whose process stopped, and together the corrections cut maintenance bases 15 to 30 percent in our reviews, before a single renewal concession was requested.
Your first five moves
- Reconcile application users against active status and disable the dormant, because authorized counts and the 20 to 35 percent of leavers bill until removed.
- Re count the employee metric under its real definition, tracked populations with contractors, both directions, before an audit does it one way.
- Inventory the connected devices, scanners, weighbridges, and terminals, against the fifty device floor nobody budgeted.
- Audit the database grant boundary, because the ASFU instance under JDE converts to full licensing the day another workload touches it.
- Price everything against the 2037 clock, migration, third party support, and renewal alike, on your calendar. The Oracle practice runs the estate with you.
Frequently asked questions
How is Oracle JD Edwards licensed?
On five metrics, each with a minimum: application users at about $4,595 for core modules with a five per component floor, employees at $185 to $225 for workforce modules with an all employees minimum, connected devices with a fifty device floor.
Expense reports at about $6 with a thousand report minimum, and UPK developers at about $17,500.
Support adds roughly 22 percent of net fees annually.
Who counts under the JD Edwards employee metric?
Everyone the programs track, not just people who log in: a payroll or HR module tracks the whole workforce, so the whole workforce counts, and the definition pulls in contractors, consultants, and agents performing services.
Acquisitions raise the count automatically, and estates counting badge holders only are undercounted by the definition's own design.
What is the fastest JD Edwards licensing saving?
The leaver reconciliation: application users count by authorization, not activity, and 20 to 35 percent of seats in our reviews were attached to people who had left or moved, with dead modules carrying support at sites where the process had stopped.
Right sizing users and modules cut maintenance bases 15 to 30 percent before any renewal negotiation.
Do warehouse scanners need JD Edwards licenses?
Often yes: the connected device metric covers devices exchanging data with the programs without human interaction, scanners, weighbridges, and shop floor terminals included, with a fifty device minimum, and it is rarely on anyone's inventory.
The device census belongs in every JDE license review, because the audit script finds what the internal review never counted.
How long will Oracle support JD Edwards?
Premier Support for EnterpriseOne 9.2 is committed through at least 2037, which removes the forced migration clock: the Fusion decision prices on business merits, third party support compares against a decade of committed Oracle patches, and urgency framed proposals lose their deadline.
The timeline is yours, which is the strongest single fact in any JDE negotiation.
Is the database included with JD Edwards?
No: JD Edwards sits on a separately licensed database, frequently an application specific full use grant restricted to the JDE application, and a reporting schema or shared workload on the same instance converts the restricted grant into a full technology licensing requirement.
The grant boundary audit is part of every JDE estate review for exactly that reason.
