Oracle opened with a four point seven million dollar Java audit claim. Redress Compliance closed the engagement at zero. The Universal Subscription was reset on a multi year buyer side price, and the side letter sealed the audit findings out of the next term.
Oracle opened against Avis Budget Group with a Java audit claim of four point seven million dollars. Ninety days later the claim closed at zero, the Universal Subscription was reset on a multi year price, and a side letter fenced the findings out of the next renewal.
This page reconstructs how the number moved, position by position. It is the negotiation record of the engagement: what was tabled, in what order, and why the order is the reason the claim died. Readers who want the counting methodology should start with the Oracle Java Audit Defense Playbook and the Java Knowledge Hub.
Oracle sent a courteous email from License Management Services, not a contractual audit notice. The note referenced an internal review of the Avis Java estate, named the Java SE Universal Subscription, quoted a deployed JVM count, and attached a closing price of four point seven million dollars.
That format is deliberate. A soft inquiry sits outside the audit clause, so Oracle carries no obligation to follow audit procedure, and the sales team keeps control of the conversation. The Oracle Java SE licensing FAQ describes the subscription model this pricing is built on.
The estate behind the number was typical of a North American vehicle rental operation at global scale: corporate IT running Java client and server applications, operations technology with Java embedded in rental and reservation platforms, and a long tail of third party products bundling Oracle runtimes. Oracle priced all three as one liability. The contract structure supported no such reading.
Two channels, two different tables
| Attribute | Soft inquiry | Formal audit |
|---|---|---|
| Sender | LMS or a sales overlay team | Oracle audit function under the contract clause |
| Contractual basis | None. Participation is voluntary | Audit clause, with notice periods and procedure |
| Oracle's goal | A subscription sale priced off fear | A compliance finding that forces a settlement |
| Buyer's leverage | High. Nothing is owed until proven | Procedural. Scope and evidence rules apply |
| Correct response | Engage on process, share no data | Counsel led response under the clause |
Avis procurement recognized the pattern from earlier Oracle database audits and made one decision that shaped everything after it: no substantive call with Oracle before an independent baseline existed. The channel stayed commercial, which meant the claim stayed negotiable.
Had the team confirmed even one deployment figure on that first call, the number would have hardened into an admission. Silence on data, combined with active engagement on process, kept Oracle selling rather than enforcing.
The claim priced the entire Avis footprint as one Universal Subscription liability, and two thirds of that construction did not survive contact with the record. The baseline, built before any data crossed the table, separated the claim into three components with three different owners.
Each finding became a negotiation position. None was revealed until its moment in the sequence, which is the discipline most internal teams find hardest to hold.
The claim moved because three positions were tabled in a deliberate order, each one closing a door before the next opened. The engagement ran roughly thirteen weeks from the first LMS email to a signed close, and the sequence, not the strength of any single argument, produced the zero.
The first filing was contractual, not technical. The team documented the clause defining an employee, mapped it line by line onto the Avis HR record, and delivered a written buyer side headcount that differed materially from the figure Oracle had used.
That single filing removed roughly forty percent of the inflated portion of the claim. Oracle did not contest it, because the operative words were Oracle's own drafting. Opening with the vendor's language does something subtle: it establishes that this buyer argues from the contract, which disciplines every exchange that follows.
Three weeks later, with the denominator already conceded, the team presented the ISV analysis. The majority of the measured JVM instances ran inside third party products, and the redistribution agreements confirmed the ISVs, not Avis, held the relevant Oracle relationship.
Oracle removed those instances without escalation. Pressing the point would have meant opening a rights dispute across its own ISV channel, a fight worth far more than one claim. A perimeter argument the vendor cannot afford to escalate is the cheapest concession in software audit defense.
Only after the claim had shrunk twice did the team table the OpenJDK migration plan: timelines, security patching coverage, budget, and an executive sponsor, all pointing at a complete Java exit inside an eighteen month window. This was presented as a decision already made unless the commercial terms changed.
Oracle's commercial team then ran the calculation that appears on every Java engagement we have closed. A customer who leaves is worth nothing. A customer on a multi year Universal Subscription at a defensible price is an annuity. The renewal conversation reopened, and the audit claim became the cost of admission Oracle chose to waive.
Reconstructed from the engagement record, the calendar breaks into four phases. The striking feature is how much of it was silence toward Oracle while the internal record was being built.
The engagement calendar, phase by phase
| Phase | Approximate window | What happened | What was deliberately withheld |
|---|---|---|---|
| Baseline | Weeks 1 to 3 | Contracts pulled, estate inventoried, HR record reconciled, ISV agreements collected | Everything. Oracle received scheduling replies only |
| Contractual filing | Weeks 4 to 6 | Written employee definition position delivered and acknowledged | The ISV analysis, already complete |
| Perimeter filing | Weeks 7 to 9 | ISV redistribution evidence tabled, instances withdrawn from the claim | The exit plan, already funded |
| Commercial close | Weeks 10 to 13 | Exit plan tabled, renewal reopened, package signed with side letter | Nothing. Every position was now on the table |
Note what the calendar implies about tempo. Oracle sets urgency in the first email precisely because a rushed buyer negotiates against itself. Avis answered every message inside two business days and still conceded nothing for a month, which is the balance to strike.
Sequencing fails when positions leak, so the roster mattered as much as the calendar. The Avis side ran four roles with strict boundaries.
The role Oracle wanted in the room, a technologist willing to discuss the estate conversationally, never appeared. That absence is a negotiation position in itself, and it costs nothing to hold.
The standard playbook says a Java claim is a compliance calculation: verify Oracle's count, correct the errors, and negotiate the residual down to a tolerable settlement. We disagree, because that framing accepts the claim as a bill when it is actually a quote. Oracle prices Java claims to make the Universal Subscription look cheap by comparison, and it will trade the entire claim away for the subscription outcome it wanted from the start. The buyer's job is therefore not to shrink the number but to restructure the conversation, in sequence, until the only thing left to negotiate is the forward subscription on the buyer's terms. Avis paid zero precisely because the claim was never treated as the subject of the negotiation.
The signed close contained four instruments, and the zero was the least valuable of them. The audit claim was withdrawn, the Universal Subscription was reset on a multi year buyer side price matched to the legitimate deployment, and two protective artifacts were added that most settlements omit.
The Avis settlement at a glance
| Item | Outcome |
|---|---|
| Audit claim opening position | $4.7M |
| Final settlement on the claim | $0 |
| Universal Subscription | Reset on a multi year buyer side price |
| Side letter | Audit findings ring fenced from the next renewal |
| Governance | Deployment protocol maintaining the baseline |
The side letter deserves the attention. Without it, audit findings resurface at the next renewal as anchor material, and the settlement you thought you closed becomes the floor of the next demand. The governance protocol keeps the deployment record continuously reconciled, so the next inquiry meets a prepared position on day one.
The protocol installed at close is four recurring disciplines, none of them expensive, all of them cheaper than a second engagement.
Avis subsequently enrolled in Vendor Shield, run by the same procurement team, on the stated logic that the Java motion would return on a different metric in a different cycle. The same client later applied the discipline to middleware, documented in the Avis WebLogic support strategy case.
Source: Redress Compliance advisory engagement file.
What this means for you depends on where the Oracle letter sits in your inbox, but the transferable mechanics are these six.
If an Oracle Java inquiry is live or likely, run this checklist in order.
White Paper · Oracle
The Oracle Java Audit Defence Playbook
What the Universal Subscription really costs and how buyers push back. Read it free.
The engagement library shows the same discipline against different estates: Kroger, Mercy Health, World Kinect, CSAA Insurance, Aegean Airlines, Meyer Sound, Kalahari Resorts, an Illinois manufacturer, and a global manufacturer.
Ninety days from the first License Management Services email to a signed close. Roughly the first three weeks built the independent baseline before any substantive call, and the remaining ten weeks carried the three negotiation positions and the commercial close.
Nothing against the audit claim itself. The forward looking Universal Subscription was reset on a multi year buyer side price scoped to the legitimate deployment, with a three year price lock, which is spend Avis controlled and would have faced in any scenario.
Because the claim was an anchor, not an expectation. Once the employee definition and the ISV perimeter had stripped its substance, the residual value of enforcement was lower than the value of a multi year subscription, and Oracle took the annuity.
Yes, and it usually carries more risk than a formal audit because teams treat it casually. Data volunteered on a friendly call becomes the evidential basis of the claim. The correct posture is polite, prompt, process driven engagement with zero data transfer.
The side letter. It explicitly prevented the audit findings from following Avis into the next term, and the deployment governance protocol keeps the record reconciled so any future inquiry starts against a prepared position rather than a blank page.
Before the first substantive conversation with Oracle, because the early calls are where claims are made or broken. Avis engaged advisors before responding, which preserved every position the sequence later spent. After data has been shared, options narrow considerably.
Renewal in twelve months. Audit notice in the inbox. RFP on the desk. We start where you are.
One letter a month. Negotiation moves, audit signals, and price book shifts.
