Do Contractors and Consultants Count Toward Your Java Employee Number?

Oracle's Java employee number is a contract definition, not a head count, and the contractor clause is where most of the argument lives. This page sets out who counts, who does not, and the evidence that makes a narrower number survive an audit.

Who does Oracle count as an employee for Java?

Oracle counts two populations. The first is your own workforce, whether full time, part time or temporary. The second is the workforce of your agents, contractors, outsourcers and consultants, but only the part of it that supports your internal business operations.

Neither population is limited to people who touch Java. That is the whole design of the metric, and it is why the definition, not the deployment, is the commercial event. The mechanics of the metric itself are set out in the fully decoded employee metric.

The two clauses, separated

What the definition does not say

• It does not say every worker with a network account. Access is Oracle's proxy, not the contract's test.
• It does not say every worker at a supplier you contract with. It reaches the staff who support you, not the supplier's payroll.
• It does not say the peak number during the year. It attaches to the ordering document effective date and to your true up dates.
• It does not say the number in your annual report, your careers site, or a professional network profile. Oracle will still open there.

Read Oracle's published price documents for yourself before any call, because the wording is versioned and Oracle will quote the version that helps its number. Start with Oracle's published price lists and the Oracle pricing and licensing hub.

What does the contract text actually say about contractors?

It says the counted population includes the staff of your agents, contractors, outsourcers and consultants "that support Your internal business operations". That qualifying phrase is the whole battleground, and it is doing real work in the sentence.

Oracle reads the contractor clause as "anyone with a badge". The clause says "staff of our suppliers who support our internal operations". Those are different populations.

Three tests the phrase actually imposes

1. The relationship test. The person must be staff of an agent, contractor, outsourcer or consultant of yours. A supplier who sells you a finished product under a supply contract is not obviously acting as your agent.
2. The direction test. The support must run inward, toward your internal business operations. Staff who deliver an outcome to your customers under the supplier's own brand and control are pointed elsewhere.
3. The assignment test. The clause reaches staff, not companies. Only the individuals assigned to your account can support your internal operations, so only they can be counted.

Why the version of the price document matters

Oracle moved new Java sales to the employee based Universal Subscription in January 2023, and the surrounding definitions have been revised since. If your ordering document names an effective date, the wording in force on that date is the wording that governs your deal.

Ask Oracle in writing for the price document version referenced by your order, and keep a copy. In our files this single request has changed the counted population more than once, because the version Oracle quoted in the meeting was not the version attached to the paper.

Does it matter whether the contractor ever touches Java?

No, and buyers lose weeks discovering it. The quantity you must license is the number of qualifying people, not the number of people who run the software, and the licensed quantity must at minimum equal that number at the ordering document effective date.

This is why the "only fifty of our developers use Java" argument fails on its own. It is a real and important commercial argument about whether you should be on this product at all, and we make it in the piece on 50 developers and a 10,000 employee bill. It is not a defense to the count.

What to argue instead

• Relationship, not usage. "This supplier is not our agent or outsourcer, it is a product vendor under a supply agreement."
• Direction, not usage. "These people deliver a managed service to our customers, not support to our internal operations."
• Assignment, not usage. "The supplier employs 4,000 people. Twelve are named on our statement of work. Twelve is the number."
• Entity, not usage. "That subsidiary is not a party to this ordering document and holds its own agreement."

Which worker categories can you defensibly exclude?

Some categories are settled, some are genuinely arguable, and some buyers give away for free. The table below is the working classification we use to sort a population before any number goes to Oracle.

The category buyers give away without noticing

Transitional service agreements after a divestment are the quiet one. The people are on someone else's payroll, they support a business you have sold, and yet they usually sit inside your access systems for a year or more.

If Oracle counts them, you are paying employee subscription for a workforce you no longer own. Name them, date them, and get the cutover written down before the ordering document is signed.

How much is the definition fight actually worth?

It is worth the band annual rate multiplied by the number of heads you remove, and nothing else. That sounds obvious, and it is the calculation almost nobody performs before deciding how hard to argue.

Oracle's published rate falls as the counted population rises, so the value of one excluded head depends entirely on which band you sit in. The full ladder with worked examples sits in the tier pricing table.

A worked case, using Oracle's own example population

Take the population Oracle uses in its own published illustration. It totals 28,000 people, of whom 5,000 arrive from the supplier side rather than payroll. At the $6.75 rate that is $2,268,000 a year.

Now assume 1,200 of those 5,000 are staff of an outsourcer working on other clients, and 400 belong to product vendors under supply contracts. Removing 1,600 people leaves 26,400 and saves $129,600 a year at list, every year of the term.

Where the common advice on contractor head count is wrong

The common advice is to squeeze your counted population under the next tier boundary, because a smaller number must be a cheaper number. We disagree, and the arithmetic is not close. The published rate steps down at each boundary, so the annual bill is not monotonic across the ladder. A company counted at 900 people pays $162,000 a year at list, while a company counted at 1,000 pays $144,000, because it has crossed into the $12.00 band. Anywhere between 801 and 999 counted people you are paying more than a larger neighbor pays.

So before you spend a month excluding suppliers, check which side of a boundary the exclusions land you on. Sometimes the right move is to accept the wider population and take the lower rate that comes with it.

The boundary mechanics belong to the commercial levers page. The lesson lands here: exclusions are worth money inside a band and can cost money across one.

Where does Oracle overreach and where do buyers undercount?

Oracle overreaches on suppliers and buyers undercount on their own extended workforce. Both errors are expensive, and they are usually present in the same company at the same time.

The four overreaches to expect

• Whole supplier counting. The outsourcer's global head count is presented as if it were your extended workforce.
• Access as proof. Any identity in your directory is treated as a countable person, including service accounts and dormant records.
• Public numbers as anchor. Annual report head count or a professional network company page is used in place of your payroll.
• Group scope creep. Subsidiaries that hold their own agreements are folded into one number for convenience.

The four undercounts that create a true up

• Agency workers. Embedded staffing agency people are absent from payroll and present in every team.
• Fixed term and seasonal staff. They fall out of the extract because they are not permanent.
• Managed service teams on your systems. Service desk and infrastructure suppliers that plainly support internal operations.
• Recently acquired entities. Populations added by acquisition that nobody mapped to the contracting entity.

The pattern is a governance failure, not a licensing failure. Nobody owns reconciliation between the payroll system, the vendor management system and the accounts payable supplier master, so no single number exists until Oracle asks for one.

What the engagement file shows

Three cuts from our Java advisory work frame the size of the gap.

How do you evidence a narrower count so it survives an audit?

You build a numbered evidence pack that ties every excluded category to a document Oracle cannot wave away. Assertions lose. Dated records with named owners win, and they win again three years later when a different Oracle team reopens the file.

The six artifacts in a count that holds

1. An entity map. Which legal entities are party to the ordering document, and which hold separate agreements or none at all.
2. A dated payroll extract per entity. Taken on the ordering document effective date, not on the day the salesperson asked.
3. A vendor management system roster. Every agency and staffing worker, with start and end dates and the team they sit in.
4. Supplier assignment attestations. A short signed statement from each outsourcer naming the individuals assigned to your account.
5. A supply contract schedule. The suppliers you classify as product vendors, with the clause that shows goods or licenses rather than services.
6. An exclusions register. One row per excluded category, the test it fails, the evidence reference, and the person who owns it.

Run this before you talk numbers. A free Java employee count assessment will tell you where the reconciliation gaps sit, and the 2026 licensing benchmark tells you what a defended position looks like once the number is fixed.

What to hand Oracle, and what to keep

• Hand over: a single number, the categories behind it, and the tests you applied.
• Hand over: the entity map, because scope disputes are cheaper to settle early than in an audit.
• Keep: raw payroll extracts, directory exports and access logs. They answer questions nobody asked.
• Keep: internal drafts of the count. Superseded numbers become Oracle's anchor if they leave the building.

What should the ordering document say?

It should name your counted number, name the categories excluded from it, and name the date the number attaches to. Three sentences of drafting are worth more than three months of argument.

The three clauses to ask for

1. A stated quantity with a stated basis. The counted population as at a named date, with the exclusion categories listed by reference to a schedule.
2. An assignment based supplier definition. Supplier staff are counted only where they are assigned to your account under a statement of work.
3. A change of population mechanic. How the number moves on acquisition, divestment and true up, and confirmation that reductions are recognized at renewal.

Oracle will resist a bespoke definition and will often offer a schedule instead. A schedule is enough. What is not enough is a sales email confirming that "those contractors are out of scope", which is the artifact we most often find in a file that later lost the argument.

What changes if you hold legacy licenses or plan to leave?

If you still hold the older named user or processor based Java subscription, the employee definition does not bind you yet, and protecting that position is a separate discipline. The rules for keeping it are set out in the legacy metric renewal playbook.

If you are heading for an exit, the definition fight is still worth running, because it sets the price of the bridge. A credible migration plan also changes what Oracle will concede on supplier categories, which is the practical reason to build both at once.

The leverage that makes the definition argument land

• A mapped estate. You know which workloads genuinely require an Oracle build and which do not.
• A costed alternative. A funded plan to move the estate onto a community build, naming the distribution and the date.
• A live example. An Australian bank restructured from a workforce wide bill to a needs based estate, described in the Australian bank case.
• A modelled bill. The forecast you built yourself, covered in the bill increase forecast.

The wider negotiation strategy, including how the count interacts with term and tier, sits in the Oracle Java licensing pillar. Read it after you have fixed your number, not before.

What should a buyer do next?

1. Request in writing the price document version referenced by your ordering document, and read the definition in that version.
2. Name one owner for the count, sitting between human resources, procurement and IT, with authority to close the reconciliation.
3. Pull three extracts on the same date: payroll by entity, the vendor management system roster, and the supplier master from accounts payable.
4. Sort every supplier into agent, outsourcer, consultant or product vendor, and record which of the three tests each category fails.
5. Collect assignment attestations from your five largest service suppliers before you name a number to Oracle.
6. Price the exclusion set at the band annual rate, and check whether it moves you across a boundary before you argue it.
7. Put the number, the categories and the effective date into the ordering document or an attached schedule.
8. Diarize the true up dates and repeat the extract on each one, so the next renewal starts from evidence rather than memory.

Related advisory: the full topic guide.

Frequently asked questions

Do contractors always count toward the Java employee total?

No. They count only where they are staff of your agents, contractors, outsourcers or consultants and they support your internal business operations. Staff of a product vendor under a supply contract, or of an outsourcer working on other clients, sit outside that description and are defensibly excluded.

Does it matter whether a contractor actually uses Java?

No, and arguing it wastes leverage. The quantity is set by the number of qualifying people, not by who runs the software. Your arguments have to run on relationship, direction and assignment, which are contract tests, rather than on deployment evidence.

Do I count the whole outsourcing company or only its people on my account?

Only the individuals assigned to your account. The clause reaches staff who support your internal operations, and a supplier's people serving other clients cannot be doing that. Ask each major supplier for a short signed attestation naming the assigned individuals, and keep it with the count.

How do I handle seasonal peaks in the counted population?

Anchor the number to the contract dates rather than to the busiest week. The count attaches at the ordering document effective date and moves at your true up dates, so take dated payroll snapshots on exactly those days. Raise seasonality early, because it is much harder to unwind once a peak number is in a quote.

Can I get categories of contractor excluded in writing?

Yes, and nothing else is worth having. Ask for a schedule listing the excluded categories and the assignment based supplier definition, attached to the ordering document. A confirmation in an email from a sales contact is the artifact we most often find in files that later lost the argument.

What happens if we undercount and Oracle finds it later?

You face a true up on the difference, usually at a moment of Oracle's choosing rather than yours. The categories that create this are agency workers, fixed term staff, managed service teams on your systems, and populations added by acquisition. Reconciling those four before you sign is far cheaper than explaining them afterwards.

Should we send Oracle our payroll data to prove the number?

No. Provide the number, the category logic and the tests you applied, and keep the raw extracts. Raw data invites questions about populations that were never in dispute, and Oracle sets out its own audit and support practice in its published support policies.

Where do I find Oracle's own wording rather than a summary of it?

Oracle publishes its product and pricing material centrally, and the definition sits in the price documents rather than in marketing pages. Start at Oracle's Java product pages, then the price list index, and match the version to your ordering document date.