The per employee metric Oracle introduced in January 2023 does not count Java users. It counts people. The definition reaches every full time and part time employee, every contractor, and every temporary worker, regardless of whether that person ever touches Java. For a company that uses a large contingent workforce, that single clause can double or triple the counted population, and with it the claim. Disputing who belongs in the count is therefore one of the highest value moves in any Java audit defense.
This article is part of the Java Audit Survival Guide, the buyer side pillar on defending an Oracle Java audit. Contractor inclusion is where many of the largest disputes are won.
What the metric actually says
The Universal Subscription is priced on a headcount figure, and Oracle's definition of that figure is deliberately broad. It is not the number of Java installs, not the number of Java users, and not the number of employees in IT. It is the total counted population: staff plus the contingent workforce. List pricing runs from 5.25 to 15.00 dollars per employee per month, so every name added to the count flows straight to the bill at the applicable band. Understanding that the charge is detached from actual use is the first step, because it tells you the fight is about the population, not the software.
Why contractor numbers are so often wrong
Oracle's opening count is an assertion, not a verified figure, and it is frequently inflated. Common errors that a defense surfaces:
- Contractors who left during the period being counted as though present throughout.
- Workers employed by a separate legal entity that is not the contracting party for the agreement.
- Seasonal or temporary staff double counted across overlapping engagements.
- Vendors and agency staff whose own employer, not your company, is the correct counted population for their use.
- Headcount pulled from a global figure when the agreement scope is narrower.
Each of these is a factual question with a documentary answer. Oracle's number stands only while it is unchallenged. The moment you produce dated headcount records tied to the correct contracting entity, the burden shifts back to Oracle to justify every name it added.
The entity question underneath the count
Contractor disputes often turn on which legal entity signed, or would sign, the agreement. The metric applies to the contracting entity's counted population, not to a sprawling global group. If contractors are engaged through a different subsidiary, a separate region, or an agency that carries its own obligations, they may sit outside the population that the agreement can reach. Mapping the contingent workforce to the right entity is detailed technical and contractual work, and it routinely removes large blocks of people from the count before any pricing conversation begins.
| Population Oracle asserts | Defended position |
|---|---|
| Every contractor, globally, full period | Only contractors of the contracting entity, for dated periods of engagement |
| Agency staff counted by your headcount | Counted by their own employer where the engagement supports it |
| Temporary workers counted year round | Counted only for the months actually engaged |
| Departed contractors still in the figure | Removed with dated offboarding records |
Indicative worked example. A retailer received a claim priced on a counted population that included thousands of seasonal and agency workers. Dated workforce records showed many were engaged for only part of the year, a large group were employed by staffing agencies, and a regional subsidiary outside the contracting entity held others. The defensible population fell sharply, and the claim fell with it. Figures are indicative.
Build the headcount evidence first
The defense depends on records, not arguments. Pull dated headcount by entity, separate permanent staff from the contingent workforce, and document start and end dates for contractors and temporary workers. With that in hand you can answer Oracle's count line by line rather than accept a single inflated total. The broader fight over the population figure, including permanent staff, is covered in disputing the employee number Oracle uses, and the disciplined opening response is set out in the first 48 hours of a Java audit.
The bottom line
The employee metric counts contractors and temporary workers by definition, but Oracle's specific count is an assertion you are entitled to test. Tie every name to the correct contracting entity and to a dated period of engagement, strip out departed and externally employed workers, and the counted population shrinks to what the agreement can truly reach. In a metric priced per head, every name you remove is money kept.
Next step. Get a Quote and we will pressure test Oracle's counted population and dispute every contractor that does not belong in it. Submit the form to Get a Quote. We work on a Fixed Fee from $18,000 or a Gainshare share of verified savings or avoided exposure, with zero retainer and no risk to you.