The Java Audit Survival Guide.

If you are reading this with an Oracle email open in another tab, take a breath. The audit is the start of a negotiation, not a verdict. The buyer that prepares calmly almost always settles for a fraction of the first number Oracle puts on the table.

Why Oracle audits Java now

In January 2023 Oracle moved Java SE to the Universal Subscription, priced on a per employee metric. That single change turned Java from a quiet line item into one of the largest software exposures many enterprises carry. List pricing runs from 5.25 to 15.00 dollars per employee per month, stepping down through volume bands. The crucial detail is that the metric counts every full time and part time employee, every contractor, and every temporary worker, regardless of who actually touches Java.

Because the price is tied to headcount rather than to deployment, an estate running Java on a handful of servers can face a bill sized to the entire payroll. That gap between what you use and what you are billed for is the reason Oracle audits intensified in 2026, with the License Management Services team focusing on employee count, contractor inclusion, and deployment history going back three years.

The shape of an Oracle Java audit

Audits rarely arrive as a formal letter on day one. They usually open as a friendly note from an account team or a soft audit email asking you to confirm your Java usage or to run a script. That informal tone is deliberate. Anything you volunteer early becomes evidence later. The buyer side posture is simple: be cooperative, be slow, and be precise. You owe Oracle what your contract requires and nothing more.

A typical audit moves through four phases. First, contact and scoping, where Oracle defines what it wants to look at. Second, data collection, where measurement scripts and questionnaires arrive. Third, the findings, where Oracle presents a claim. Fourth, settlement, where the real number is negotiated. Most of the value you can protect is won in the first and last phases, not in the middle.

The first week: what to do and what to avoid

Route every audit communication through one named owner, ideally with procurement and counsel copied. Acknowledge receipt, ask Oracle to put the scope and the contractual basis for the review in writing, and do not run any script or share any data until that scope is agreed. Start an internal discovery in parallel so that you understand your real Java footprint before Oracle does. Knowing where Oracle Java actually runs, and where a free OpenJDK distribution already covers you, is the foundation of every later move.

Avoid three early mistakes. Do not confirm an employee number off the top of your head. Do not let well meaning engineers install Oracle tooling or send raw inventory exports. Do not treat a deadline in the email as fixed, because timelines are almost always negotiable.

How the claim is built, and where it inflates

The audit claim is roughly your employee count multiplied by the list price multiplied by whatever discount Oracle offers, often extended across the three year lookback. Each input is contestable. The employee count is frequently overstated because it sweeps in populations you can argue out or document differently. The list price assumes you sit in a band you may not belong in. The lookback assumes continuous commercial use that you may not have had.

Claim input	Oracle's assumption	Buyer side response
Employee count	Entire global headcount including contractors and temps	Build a documented, defensible population and challenge inclusions
Rate band	Top of the list ladder	Establish the correct volume band and any negotiated discount
Lookback	Three years of continuous commercial use	Show when public updates were free and when use actually began
Deployment	Java everywhere it is found	Isolate true Oracle Java need, migrate the rest

Every indicative figure Oracle presents is a starting position, not a fact. Treat it that way.

From findings to settlement

When the findings land, resist the urge to negotiate the headline number directly. Negotiate the inputs instead. Reduce the counted population through documentation. Move workloads that do not need Oracle Java to a free OpenJDK distribution so the residual envelope shrinks. Strip the contract traps that quietly inflate future cost: the minimum annual floor, the annual true up at each anniversary, and the renewal escalator. A smaller, cleaner residual is far easier to settle and far cheaper to carry.

Across the estates we defend, the average settlement lands at roughly 68 percent below Oracle's opening number. We have defended more than 120 million dollars in Java exposure across more than 300 audits, with more than 20 years of combined buyer side experience behind the work. Those outcomes come from method, not luck.

How we engage

We work two ways, both with no downside to you. A Fixed Fee from 18,000 dollars when the scope is known, agreed up front and backed by our guarantee. Or Gainshare, a share of verified savings or avoided exposure, with zero retainer and no risk to the customer. If we do not reduce your Oracle Java cost, we reimburse our service fee.

Start the cluster here

This guide is the hub for our audit defense library. From here you can dig into the moments that matter most.