In an audit Oracle does not accept your conclusions, it tests your evidence, and where the record is thin it fills the gap with assumptions that favor Oracle. This is a buyer side guide to the exact evidence an LMS review will look for, so you can build the record before the audit asks and keep the burden of proof where it belongs.
An Oracle audit is an evidence contest, and where your record is silent the auditor's assumptions take over, always in Oracle's favor. Build the deployment history, distribution proof, and population evidence that an LMS review demands before it begins, so every claim you make is backed and every gap that would otherwise cost you is closed.
It is tempting to think of an Oracle Java audit as a measurement exercise, where the truth is discovered and a number falls out. It is closer to a contest over evidence. The Oracle License Management Services team, which intensified its Java reviews in 2026, does not simply accept what you tell it. It asks you to prove it, and where you cannot, it is free to substitute an assumption, and those assumptions are not neutral. They lean toward the largest defensible number. The practical consequence is that the strength of your position is determined less by what is true and more by what you can demonstrate. The organizations that fare worst are not those with the most Oracle Java. They are those that cannot evidence their own estate and so concede the framing to Oracle.
This is sharpened by the metric Oracle moved to in January 2023. The Universal Subscription counts every full time and part time employee, every contractor, and every temporary worker, regardless of who uses Java, so the populations and histories under examination are large and the cost of an unproven gap is high. A single unevidenced area can be the difference between a contained outcome and a workforce wide claim.
An LMS review tends to probe the same categories every time, and knowing them lets you prepare the proof in advance. It asks for deployment history, because the 2026 audits reach back three years and Oracle wants to know not just what runs today but what ran across that window. It asks for the distribution of each install, because the entire question of whether you owe anything turns on commercial Oracle Java versus a free build. It asks about the employee population, because that is the basis of the price under the per employee model. And it asks about removals and changes, because an install that came and went still sits inside the lookback period and Oracle will want it accounted for.
| Category | What Oracle wants to see | Why it matters |
|---|---|---|
| Deployment history | What ran across the three year window | Lookback period |
| Distribution proof | Vendor of each runtime | Decides if you owe |
| Population data | How the employee count is derived | Sets the price |
| Removal records | When installs were retired and why | Closes past gaps |
Build the record Oracle will ask for before the audit begins, and decide deliberately what you will and will not share. Evidence prepared in advance is precise and on your terms. Evidence assembled under an audit deadline is rushed, incomplete, and hands Oracle the gaps.
The most expensive part of an audit is rarely the Oracle Java you can prove. It is the area where your record says nothing. When you cannot show what ran two years ago, Oracle is free to assume the worst case ran the whole time. When you cannot prove an install was a free distribution, it can be treated as commercial. When you cannot explain how a runtime arrived or when it left, the benefit of the doubt does not go to you. Each silence is an opening, and an experienced auditor is skilled at converting silences into a larger number. Building the record in advance is how you close those openings on your own terms rather than leaving them for Oracle to fill.
There is a decisive advantage to preparing evidence before an audit rather than during one. Evidence gathered ahead of time is calm, complete, and accurate. You can reconcile your discovery against your procurement records, confirm distributions, document removals, and derive your population from a defensible source, all without a clock running. Evidence assembled after an audit letter lands is the opposite: hurried, partial, and shaped by pressure, which is exactly the condition in which mistakes are made and gaps are left. The same record that looks like diligence when prepared early looks like a scramble when prepared late, and auditors read the difference.
Having the evidence is one thing. Deciding what to provide is another, and it is a decision that should be made deliberately rather than reflexively. An audit is a commercial negotiation, not an open book examination, and you are entitled to manage what you disclose, when, and in what form. Over sharing can hand Oracle material it did not have and would not otherwise have obtained, while under sharing can look evasive. The right posture is prepared and precise: know your record cold, share what serves your position and what you are genuinely obliged to share, and never improvise under pressure. This is the point where buyer side advice earns its keep, because the choice of what to put on the table shapes the outcome as much as the evidence itself.
An Oracle audit tests your evidence, not your good faith, and every gap in your record is filled with an assumption that favors Oracle. Build the deployment history, distribution proof, population basis, and removal records the LMS will ask for before the audit starts, and decide deliberately what to share. To create the underlying record, read building a Java inventory that holds up, and to test your position the way Oracle will, see how to audit yourself before Oracle does. When an audit is live, the safest first move is to read our Oracle Java licensing guide for 2026 and bring in buyer side help before you respond.
Book a Strategy Call and we will map the evidence an Oracle audit will demand, find the gaps in your record, and help you close them before an LMS review tests them.
Book a Strategy CallFixed Fee from $18,000 or Gainshare, a share of verified savings or avoided exposure with zero retainer and no risk to you. We sit between you and Oracle and we never take vendor money.
Get a QuoteWeekly intelligence on Oracle Java licensing moves and the buyer side defenses that work.