Seven in ten Oracle audits settled as a forward purchase, not a payment
A finding is a claim about your use, priced at list, and the discount you win against it is the concession Oracle gives most willingly. What sets the five year cost is the shape of the settlement: which support set the new licenses join, whether a forward commitment rides along, and whether the paper is folded into a renewal.
Prepared by Redress Compliance · August 16, 2026 · Oracle advisory. 35 to 45 audit settlements led, 2024 to 2025.
Executive summary
A finding is a claim, not an invoice. It is built from the published price list, so nothing in it reflects the discount you have received on every purchase you have ever made from Oracle.
Validated exposure landed 25 to 50 percent below the opening claim once scope, counting method, and entitlement records were corrected. The argument happens on quantity and method, never on fairness.
Roughly seven in ten settlements closed as a forward purchase or a cloud commitment, because Oracle trades backward looking money for forward looking money. That asymmetry is the whole game.
Support at 22 percent of the net license fee makes a discount an annual liability, not a one time saving. Structure the paper first and the percentage second.
Where a seven figure audit number comes from
Every line in an opening claim is a published rate multiplied by a quantity. Take a mid sized finding: 60 processors of Database Enterprise Edition found unlicensed, with Partitioning, Diagnostics Pack, and Tuning Pack detected on the same estate.
| Line | List rate per processor | Quantity | At list |
|---|---|---|---|
| Database Enterprise Edition | 47,500 | 60 | 2,850,000 |
| Partitioning | 11,500 | 60 | 690,000 |
| Diagnostics Pack | 7,500 | 60 | 450,000 |
| Tuning Pack | 5,000 | 60 | 300,000 |
| License subtotal at list | 4,290,000 | ||
| Support at 22 percent, one year | 1 year | 943,800 | |
| Backdated support, three years | 3 years | 2,831,400 | |
| Opening ask | 7,121,400 |
The trap inside every headline reduction: if your standing discount on Database is 60 percent, those same 60 processors on a normal order form price near 1.7 million rather than 4.3 million. A 50 percent discount off the audit anchor is therefore worse than your everyday commercial terms. Oracle's standard audit clause contains no punitive multiplier; what buyers experience as a penalty is two ordinary things stacked, list pricing instead of your discount and backdated support instead of support starting today, and the second is frequently waived outright.
What moves, and what actually moves it
- The quantity found moves on evidence. Counting errors, benign feature usage, and decommissioned hosts are the three that recur, and the mechanics are set out in fighting an Oracle audit claim and the column by column reading in interpreting LMS script output.
- The counting method moves where policy is not contract, which is decided by your agreement text against Oracle's published policy documents rather than by argument.
- Scope and entities move best before collection, because what the audit was allowed to look at is settled in the first month, not the last.
- Backdated support is often waived entirely in exchange for revenue Oracle can recognize now instead of in arrears. It is the single most reliable concession in the file.
- The support set the licenses join matters more than the discount, and the time to ask for a separate support identifier is before signature, not after.
- A written release is free to ask for. Name the entities, name the programs, state a date, and put it in the first settlement draft rather than the last.
- The 22 percent ratio itself never moves. You move the net fee it is calculated on, which is why the structure conversation has to come before the percentage conversation.
The Oracle audit response playbook
The notice to settlement sequence: scope negotiation, evidence standards, finding challenges, and settlement mechanics.
Get the playbook →The discount is the concession Oracle gives most willingly
The common advice on Oracle audit negotiation is to fight for the biggest possible reduction off the finding. We disagree, and the arithmetic is the reason. The discount percentage is applied to an anchor Oracle built from its own price list, which means a large reduction can still leave you paying more than your ordinary commercial terms would have produced on a routine order form. A buyer celebrating 60 percent off a number that was never real has won an argument that was staged for them to win.
What determines five year cost is structure, and structure has three components. The first is which support set the new licenses join, because support runs at roughly 22 percent of the net license fee under Oracle's published technical support policies, renews with an uplift, and is hard to shrink later once quantities are consolidated onto a single identifier. A settlement that adds nine hundred thousand a year to the support line costs far more over five years than a smaller cash payment against no new support identifier, and the two are routinely presented as if the larger discount made the first one better.
The second component is whether a forward commitment rides along. Oracle trades backward looking money for forward looking money, and its currencies rank predictably: new license revenue recognized this quarter, then a cloud commitment with annual contract value, then support continuation on a larger base, then cash with no forward component, which is the form it resists most because it does the least for anyone's number. Understanding that ranking tells you exactly what to offer and exactly what to ask for in return. The cloud sweetener deserves particular care, because support rewards credits are only usable against an Oracle technology support bill and are therefore worth nothing to an organization whose whole strategy is to shrink that bill. Read a rewards backed settlement as two commitments, not one, and price both across the term as we do in cloud contracts and credits.
The third is whether the paper is bundled. Oracle will offer to fold the settlement into an upcoming renewal, presented as simplification, and it genuinely is simpler for Oracle. For you it converts a compliance matter into a precondition of commercial terms you would otherwise negotiate on their own merits. Two papers, two signatures, two negotiations. Get the structure right and the percentage becomes a detail; get it wrong and no percentage rescues it. The full cost picture is in what an Oracle audit really costs, the underlying clause mechanics in Oracle contracts, and the wider library in the Oracle practice.
- Your agreements decoded into plain English before the auditor interprets them for you
- Every settlement clause flagged with the exact quote, the page, and the replacement language
- Five year cost modeled across cash, forward purchase, and cloud commitment shapes
What the settlements showed, 2024 to 2025
Across the 35 to 45 Oracle audit settlements the practice led or benchmarked, the opening claim was almost never the right number and the headline discount was almost never the thing that mattered:
How far exposure fell below the opening claim once scope, counting method, and entitlement records were corrected.
Settlements that resolved as a forward license purchase or a cloud commitment rather than as a payment.
The patterns: backdated support reduced or waived in the large majority of closures where the buyer offered revenue landing inside Oracle's quarter, and buyers who compared the five year cost of the settlement forms, rather than the discount on them, paying materially less than those who did not.
Oracle's fiscal year ends 31 May, so its quarters close at the end of August, November, February, and May. Discounts are approved in bands and each escalation takes one to three weeks of real calendar time, which is why the standard advice to hold out until the last day fails. The better play is to be approvable four to six weeks before a quarter ends, with the shape of the deal already agreed and only the number still moving.
Your first five moves
- Rebuild the count and the entitlement position before you price anything, so there are two measurements in the room instead of one.
- Contest lines in writing against the findings paper, which is an assertion, not an obligation. Only the settlement letter and order form bind you.
- Model the five year cost of each settlement shape, cash against forward purchase against cloud commitment, including the support tail each one creates.
- Ask for a separate support identifier and a written release in the first settlement draft, naming entities, programs, and a closing date.
- Keep the settlement paper and the renewal paper apart, and be approvable four to six weeks before Oracle's quarter ends. The Oracle practice runs the settlement with you.
Frequently asked questions
Is an Oracle audit finding a bill you have to pay?
No. A finding is a claim about your use of Oracle programs, priced at list, and claims can be wrong on the data, wrong on the counting method, and wrong on the contract reading. It is produced by a team applying Oracle's counting method to data you supplied, on assumptions you are entitled to inspect.
Does Oracle charge a penalty on top of the licenses?
Not in the standard paper. Oracle's audit clause contains no punitive multiplier. What buyers experience as a penalty is two ordinary things stacked: list pricing instead of the discount you normally receive, and backdated support instead of support starting today. Both are negotiable and the second is frequently waived outright.
What is actually negotiable in an Oracle audit settlement?
Almost everything except the existence of a genuine shortfall and Oracle's right to audit. Quantity moves on evidence, counting method moves where policy is not contract, scope moves best before collection, backdated support moves on forward revenue, and the release costs nothing to ask for. The 22 percent support ratio does not move.
Why does the 22 percent support line matter more than the discount?
Because Oracle does not discount the support percentage, it discounts the net license fee and then calculates support as roughly 22 percent of that fee. A license discount is therefore not a one time saving, it sets an annual liability that renews with an uplift for as long as you hold the licenses.
What will Oracle trade a backdated support waiver for?
Forward revenue it can recognize inside the current quarter. Oracle values new license revenue first, a cloud commitment second, support continuation on a larger base third, and cash with no forward component last. The things you want most are cheap for Oracle to concede once you hand it something that lands in the quarter.
Should the settlement be bundled into the renewal?
No. Oracle will offer to fold them together as a simplification, and it is simpler for Oracle. For you it makes the compliance matter a precondition of commercial terms you would otherwise negotiate on their own merits. Two documents, two signatures, two negotiations.
Is a cloud commitment settlement cheaper than paying cash?
Often not. Support rewards credits are real but only usable against an Oracle technology support bill, so they are worth nothing to an organization trying to shrink that bill. Read a rewards backed settlement as two commitments, committed cloud spend and a support base you have agreed to keep paying, and price both across the term before comparing.
When in Oracle's year should the settlement close?
Oracle's fiscal year ends 31 May, so quarters close at the end of August, November, February, and May. Deep discounts are approved in bands and each escalation takes one to three weeks, so a deep discount presented in the final ten days often cannot be approved in time. Be approvable four to six weeks before the quarter ends.
How to Prepare for Your Oracle SaaS Negotiation
The 90-day renewal proposal with a 9 to 12 percent uplift is the bill for not preparing. The ARR compensation game, the utilization audit that finds 30 to 50 percent shelfware, benchmarks targeting 0 to 3 percent, one costed alternative, and sequencing toward May 31.
