Draft findings are a schedule of separate assertions, not one number. How to test the measurement, contest the interpretation, rebuild entitlement, and write the rebuttal that moves the schedule.
An Oracle audit claim is two things stacked together. A measurement of what ran, and an interpretation of what that use means under your contract. Both are contestable, and this is how to take the claim apart line by line.
Oracle is claiming that a specific quantity of a specific program was used in a specific period without matching entitlement, and pricing that gap at list. Every one of those elements is a separate assertion.
Buyers lose ground by treating the claim as a single number with a discount attached. Advisers who win treat it as a schedule of independent line items, each of which has to stand on its own.
Where the money in a claim line comes from, and who can move it
| Component | What it rests on | Who can change it | Where it is won |
|---|---|---|---|
| Quantity | Collected data plus a counting rule | The compliance team | Evidence, before any pricing talk |
| Unit price | The published price list | The account team | Commercial phase, not the review |
| Period | A first use date Oracle infers | The compliance team | Build records and change logs |
| Support charged back | The period times the support rate | The account team | Falls when the period falls |
A finding usually presents as a single figure that hides three multiplications. Quantity times list price, then a period of unpaid support applied to that same figure, then an implied forward support line that never appears on the page.
Separate them on your own spreadsheet on day one. The quantity is where evidence wins, the period is where records win, and the price is a commercial conversation that belongs in the audit negotiation guide, not in the review.
If the letter itself is still open on your desk and no findings exist yet, work the earlier stage first in the audit letter guide and the audit response playbook. This page starts the day the numbers arrive.
Ask for the derivation, not the total. For every line, Oracle should be able to name the host, the collection date, the script or output file, and the field within it that produced the count.
That request is reasonable, contractually consistent, and it is the single highest yield hour in the whole dispute. It also changes the tone, because it signals that the number will be checked rather than absorbed.
Oracle's summary spreadsheet is a derived artifact. The underlying collection output carries timestamps, host identifiers, version strings, and usage counters that the summary flattens away.
Reconcile three sources before you accept any quantity: the collection output, your own configuration management records, and the platform layer that shows where the workload actually ran. Where those three disagree, you have a dispute worth writing down.
The mechanics of the collection itself, including which views are read and how to run it without damaging your position, sit in the LMS script analysis guide. Oracle documents the compliance function and its remit on the License Management Services page.
Worked wording. "Line 14 counts 32 processors on host PRD09. Our asset record and the platform logs attached at tab C show PRD09 was decommissioned on 14 March 2024, before the collection date of 2 September 2024. We ask that line 14 be withdrawn."
Short, specific, evidenced, and it asks for one thing. Objections written like this get answered. Objections written as general disagreement get a meeting invitation.
You can contest any interpretation that depends on a document your agreement did not incorporate, or on a reading of a defined term that the definition does not support. Those are the two openings, and they are narrower than the internet suggests.
Oracle publishes operational documents that shape how it counts, including the partitioning policy. It is an educational document by its own wording, and it is not automatically contract text.
Whether it binds you depends on what your agreement incorporates and how. That question belongs in the agreement map, and the full boundary argument sits in our partitioning policy analysis.
Intent is not a defense. "Nobody meant to use it" and "the DBA did not know it was chargeable" are true statements that change nothing, because the grant is about use, not about intention.
Spending the dispute there costs credibility you will need later. Concede the lines that are genuinely real, early and visibly, and spend your capital on the lines that turn on evidence.
Rebuild it from your own records before you look at Oracle's version. The shortfall is a subtraction, and buyers routinely lose money because the number being subtracted is incomplete.
Three fields decide whether an entitlement counts against a finding. The exact program name, the licensing metric, and the legal entity that holds the grant.
A mismatch on any one of them lets the line stand. This is dull work and it is where a surprising share of the reduction comes from, which is why the entitlement rebuild should start the same week the notice arrives.
White Paper · Oracle
Oracle Audit Response Playbook
Meet an Oracle audit from a prepared position. Read it free.
It looks like a short cover letter, a line by line schedule, and an indexed evidence pack. Nothing else, and nothing rhetorical.
The reason it has to be a document is structural. The people who receive your argument in the review are not the people who will price the outcome, and only what is written down survives that handoff.
A disputed schedule, four rows from a composite engagement
| Claim line | Oracle's basis | Ground of objection | Effect on the line |
|---|---|---|---|
| 96 processors, database, four node cluster | Whole cluster counted | Interpretation and evidence: workload pinned to two hosts, movement logs attached | Reduced to the two hosts actually used |
| Management pack on 40 processors | Usage counter set | Measurement: counter set once by a default parameter, no subsequent activity | Line queried, remediated, and withdrawn |
| Support charged back to 2019 | Inferred first use | Period: build records show the hosts were provisioned in 2022 | Chargeback period cut by three years |
| 200 named users on a test system | Minimum applied per processor | Entitlement: unused grant held under an acquired entity | Netted to zero against existing holdings |
Accept them explicitly and in the same document. A rebuttal that disputes everything reads as noise, while one that concedes four lines and disputes eleven reads as a serious review.
Concession also buys sequencing. Once a line is accepted, you can insist that remediation is credited, that the period stops at the remediation date, and that the fix is reflected in the revised schedule.
The common advice is to open with a robust legal challenge to the audit right itself and refuse cooperation until Oracle narrows it. We disagree. In the disputes Fredrik Filipsson has worked, that opening produced two predictable outcomes: the review escalated to people whose job is escalation, and the buyer spent its credibility before a single line item had been tested. The audit right is usually real, the scope is negotiable, and the number is the soft target. Fight the schedule, not the clause, and use the clause only where a specific line depends on a document your agreement never incorporated.
Source: Redress Compliance advisory engagement file. Claim disputes reviewed during 2024 and 2025.
Then you change who is reading the argument, not the volume of it. A refusal at the review level is often a mandate limit rather than a considered rejection of your evidence.
Stop when the remaining disputed value is smaller than the value of the terms you could win instead. That crossover usually arrives once the schedule has stopped moving for two consecutive exchanges.
At that point the work moves to structure: the release, the support treatment, the amendment that fixes the definition that caused the gap. That is the ground covered in the audit negotiation guide, and it is where the remaining money is.
A finding is an assertion with a spreadsheet attached. Test the spreadsheet before you argue about the assertion, because most of the money is in the arithmetic.
Work the schedule in this order. Each step produces a document, and the documents are what move the number.
Yes, and most findings move. A draft finding is an opening position built from collected data and a counting interpretation, both of which can be wrong. Disputes succeed when they identify specific lines, state a ground of objection, and attach dated evidence rather than arguing about the total.
Dated records produced in the ordinary course of business. The strongest set is configuration and asset records, change and build logs, platform placement history, and procurement records proving entitlement by entity and metric. Screenshots and recollections carry little weight next to a timestamped export.
No, not in the sense of a punitive multiplier. Oracle's standard audit clause does not apply one. The figure feels punitive because quantities are priced at the published list rate rather than your negotiated rate, and because support is charged back to an inferred first use date.
Oracle usually proposes a short window, often two to four weeks, and it is a proposal rather than a contractual deadline in most agreements. A reasoned request for more time, tied to the volume of lines and the evidence needed, is normally accepted when it comes with a date you then meet.
Remediate anything genuinely non compliant immediately, and record the date. Remediation does not erase past use, but it stops the clock on that line and it demonstrates good faith, which materially changes the tone of the rest of the review.
It depends on your agreement. The policy is published as an educational document and is not automatically contract text, so the question is whether your master agreement or ordering document incorporates it and in what form. That is a clause reading exercise, not a technical one.
Before the first substantive response, not after the number is agreed. The reduction is won in the schedule and the sequencing, both of which are decided early. Once a figure has been accepted in principle, the remaining room is commercial structure rather than quantity.
We work the schedule, not the meeting. That means rebuilding entitlement, testing every measurement, drafting the objection package, and staying on the file until the revised schedule and the closing paper agree with each other.
Ongoing cover sits in Vendor Shield, renewal work in the Renewal Program, and price context in the Benchmark Program and our benchmarking practice. A wider spend review runs through the software spend assessment.
More on who we are: about us, the management team, our locations, and how to contact the practice.
The buyer side moves that keep your Oracle estate honest at renewal.
Independent. Buyer side. Built for Oracle customers running the next renewal cycle.
Open the white paper in your browser. Corporate email only.
Open the Paper →The LMS draft claim came in at twenty two million dollars. We disputed the metric, contested the virtualization policy, and closed the audit at four point two million as a forward OCI commitment. The cash exposure went to zero.
We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.
LMS audit patterns, script scope changes, virtualization policy updates, ULA negotiation movement, Java SE subscription benchmarks, and the wider Oracle commercial leverage signals across every engagement.
