Your Oracle Java cost is driven by one number: the counted population. A defensible employee count, sourced from systems of record and reconciled across them, is the foundation of every dollar you save.
Why the count is the whole game
Under the Universal Subscription that Oracle introduced in January 2023, your Java cost is driven by one number: the size of your counted population. The metric counts every full time and part time employee, every contractor, and every temporary worker, regardless of who actually touches Java. Multiply that figure by a list rate that runs from 5.25 to 15.00 dollars per employee per month and you have the opening exposure. Because the rate is fixed by band, the only variable a buyer truly controls is the population. A defensible employee count is therefore not paperwork. It is the foundation of every dollar you save. For the mechanics behind the metric, start with the employee metric explained.
What defensible actually means
A defensible count is one you can stand behind in front of Oracle, in writing, with dated records that agree with each other. It is not the lowest number you can imagine. It is the accurate number you can prove. The difference matters because Oracle will test any figure you present. A count that falls apart under one question hands the initiative back to the vendor. A count that holds up shifts the burden onto Oracle to challenge your evidence rather than onto you to justify a guess.
Three qualities make a count defensible. It is sourced from systems of record rather than memory. It is dated to a defined measurement point rather than floating in time. And it is internally consistent, so that the figure in your human resources system matches the figure in your contractor register and your organizational charts.
The five sources you assemble first
Before you state a number, gather the records that support it. These are the sources a disciplined buyer pulls together:
- Human resources extracts for full time and part time staff, dated to the measurement point.
- A contractor register showing start and end dates and the engaging entity for each person.
- Temporary and seasonal worker records, including agency staff and short engagements.
- Organizational charts that show legal entity boundaries, not just reporting lines.
- Payroll or finance data that can corroborate the headcount from an independent system.
When two independent systems produce the same figure, that number becomes very hard to dispute. When they disagree, you want to find and resolve the gap before Oracle does.
A worked build
The example below is indicative, but it shows how a raw figure becomes a defensible one. A services firm began with a rounded total workforce number that Oracle had assumed, then corrected it against systems of record.
| Stage | Counted | Annual list at $9.00 |
|---|---|---|
| Oracle assumed total workforce | 9,500 | $1.03M |
| Corrected to actual HR headcount | 8,600 | $929K |
| Duplicate and lapsed records removed | 8,150 | $880K |
| Documented and reconciled | 8,150 | $880K |
The figures are indicative. The lesson is not. A clean, reconciled count removed roughly fifteen percent of the assumed population before any argument about rate band, discount, or migration was raised.
Measure at a defined point, not a peak
Headcount moves through the year. If Oracle measures at a seasonal peak, or averages across a period that flatters its own estimate, your population looks larger than your steady state. Choose a defensible measurement date, document why it represents your true workforce, and apply it consistently across every source. Never let the count be measured at the moment your business is at its fullest unless that genuinely reflects the year.
Reconcile before you reveal
The most common self inflicted wound is presenting a number that your own records later contradict. Reconcile your sources internally first. If the human resources extract says one figure and the contractor register implies another, resolve that quietly before any conversation with Oracle. A coherent count is worth more than a clever argument, because the moment your figures disagree with each other, the vendor stops engaging with your case and starts probing your credibility.
Keep contractors and temporary staff precise
Contractors and temporary workers are where counts most often go wrong, in both directions. Oracle's definition is broad and pulls them in, so you cannot simply exclude them. But stale registers routinely carry people who left months ago, and lapsed engagements that should have closed. A precise, dated register that closes finished engagements is both more accurate and lower than a register left to drift. For the detail on these groups, see do contractors count under the Java employee metric and do temporary workers count under the Java metric.
Document the entity boundaries
Large organizations are rarely a single legal entity. A defensible count records which people belong to which entity, because an entity with its own licensing position should not be swept into a parent figure by default. Organizational charts that show legal boundaries, not just management lines, let you separate populations that Oracle would otherwise merge. This is detail work, and it is some of the most valuable detail in the whole exercise.
Build the count before you need it
The best time to build a defensible count is before an audit letter arrives. LMS audits intensified in 2026 with a three year lookback, which means Oracle may ask about historical populations, not just today's. A count you assembled calmly, with reconciled sources and a defined measurement date, is far stronger than one thrown together under a deadline. Treat the count as a living record you maintain, not a fire drill you run when the letter lands.
Where a clean count takes you
A defensible count is the entry point to every other move. Once the population is documented and reconciled, you can dispute Oracle's larger figure with evidence, isolate the workloads that truly need Oracle Java, migrate the rest to a free OpenJDK distribution, and negotiate the residual against a smaller envelope. Across the estates we defend, settlements average about 68 percent below Oracle's opening number, and a clean count is almost always the first brick in that result. When you are ready to act on the count, see disputing the employee number Oracle uses.
Download the Employee Metric Defense Kit
A buyer side workbook for CIOs, procurement, and general counsel. Trade a work email, get the kit and The Java Audit Brief.
Download guide