Oracle audit negotiation: why the settlement structure outweighs the discount.

An Oracle audit finding is a claim priced at list, and the discount you win against it is Oracle's easiest concession. The five year cost depends on which support set the licenses join, any forward commitment, and whether the deal rides on a renewal.

How does Oracle build a seven figure audit claim?

Oracle builds the claim by multiplying each unlicensed quantity by its published list price and adding three years of backdated support. Nothing in it reflects the discount you have received on every order you have ever placed with Oracle.

Take a mid sized finding: 60 processors of Database Enterprise Edition found unlicensed, with Partitioning, Diagnostics Pack and Tuning Pack detected on the same servers. The rates below are the per processor prices on Oracle's Technology Global Price List.

The $943,800 line is one year of support at list, and Oracle multiplies it by three for the backdated charge. The ratio is on the price list itself, where Software Update License & Support for Database Enterprise Edition is $10,450 per processor, 22 percent of the $47,500 license.

What does Oracle's audit clause actually allow?

The standard clause is short. Oracle may audit your use of the programs on 45 days written notice, you must cooperate and give reasonable assistance, and Oracle does not pay your costs of cooperating. If the audit finds non compliance, you must remedy it within 30 days of written notification.

The clause contains no punitive multiplier. What feels like a penalty is two ordinary charges stacked together, list pricing in place of your usual discount and three years of backdated support. Both are negotiable.

Which parts of an Oracle audit settlement can you negotiate?

Almost everything except the existence of a real shortfall and Oracle's right to audit. Each element responds to a different kind of pressure, and each has its own best moment in the audit.

• Quantity. Evidence reduces it. Counting errors, benign feature usage and decommissioned hosts are the three that recur. The mechanics are in fighting an Oracle audit claim, and the column by column reading is in interpreting LMS script output.
• Counting method. Where Oracle relies on a policy document that your contract does not incorporate, such as the partitioning policy for virtualized servers, your agreement text decides the count.
• Scope and entities. These are easiest to settle before data collection starts, because what the audit may examine is fixed in its first month.
• Backdated support. Oracle often waives it entirely in exchange for revenue it can recognize now. In our files this is the most reliable concession of all.
• The support set the licenses join. This matters more than the discount. Ask for a separate customer support identifier (CSI) before signature, because it is hard to arrange afterwards.
• A written release. Asking for one costs nothing. Name the entities, the programs and a date, and put it in the first settlement draft.
• The 22 percent ratio. This is fixed. You can only change the net fee it is calculated on, which is why the structure has to be agreed before the percentage.

How do you check your own numbers before answering the findings?

Rebuild the count yourself so that Oracle's figure is not the only one on the table. Oracle's audit team (License Management Services, now Global Licensing and Advisory Services) works from script output you supplied, and you are entitled to inspect every assumption behind it.

• Feature usage. Query DBA_FEATURE_USAGE_STATISTICS yourself and separate features detected once from features in current use. The difference is explained in detected versus currently used columns.
• Management packs. Check the CONTROL_MANAGEMENT_PACK_ACCESS parameter on every instance. It defaults to DIAGNOSTIC+TUNING on Enterprise Edition, so pack usage often reflects a default setting. See controlling Diagnostics and Tuning Pack access.
• Partitioning. Separate partitioned objects in Oracle maintained schemas, such as the unified audit trail in AUDSYS, from tables your applications created. The evidence standard is in partitioning feature usage defense.
• Processor counts. Recheck cores against the core factor table and confirm which physical hosts each virtual machine could actually run on.
• Entitlements. Collect every order form, the CSI list from My Oracle Support and any migration or merger paperwork. Missing paper is a frequent reason a license you own gets counted as a shortfall.

Why does the settlement structure matter more than the discount?

The discount is applied to a figure Oracle built from its own price list, while the structure decides what you pay every year after signature. Three choices set the five year cost: which support set the new licenses join, whether a forward commitment comes with the deal, and whether the settlement is folded into a renewal.

Why we do not chase the largest reduction off the claim

The usual advice on Oracle audit negotiation is to fight for the biggest possible cut to the finding. We disagree, because the percentage comes off a list price figure. A large reduction can still leave you paying more than your ordinary 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 staged for them to win. Spend the effort on quantity and structure first, then on price, and measure every offer against your standing discount instead of the opening claim.

Which support set should the new licenses join?

Ask for the settlement licenses on their own order and their own CSI. Support on them renews each year with an uplift and becomes hard to shrink once the new quantities are consolidated onto your main identifier.

Two rules in Oracle's Technical Support Policies explain why the order matters:

• Repricing. When you terminate some licenses on an order, or reduce their support level, support on the remaining licenses on that order is repriced at current list less the standard discount. With a separate order you can drop the settlement licenses later without reopening the price of everything else.
• Matching service levels. Every license of the same program, options included, must sit at the same support level. A separate CSI does not let you leave the new licenses unsupported while the rest stay on support; you would have to terminate them.

The support line compounds over the life of the licenses. A settlement that adds roughly $900,000 a year to it costs far more over five years than a smaller cash payment that adds no new support.

What will Oracle trade for a backdated support waiver?

Oracle trades backward looking money for forward looking money, and its preferences rank predictably. From most to least valued:

1. New license revenue recognized this quarter.
2. A cloud commitment with annual contract value.
3. Support continuation on a larger base.
4. Cash with no forward component, which Oracle resists most because it does the least for anyone's number.

That ranking tells you what to offer and what to ask for in return. The waiver costs Oracle little once you hand it something that lands in the quarter.

How should you read a cloud commitment offer?

Read it as two commitments: the cloud spend and the support base you have agreed to keep paying. Oracle Support Rewards accrue at $0.25 per $1.00 of OCI consumption, or $0.33 for ULA customers, and can only be applied to Oracle Technology Programs support invoices.

Those credits are worth nothing to an organization whose plan is to shrink that support bill, for example by moving to third party support. Price both commitments across the term, as we do in cloud contracts and credits. The redemption rules are in our Support Rewards guide.

Should the settlement be folded into your renewal?

No. Oracle will offer to combine them as a simplification, and it is simpler for Oracle. For you it turns a compliance matter into a precondition of commercial terms you would otherwise negotiate on their own merits, so keep the settlement on its own paper and its own signature.

The full cost picture is in what an Oracle audit really costs, the clause mechanics in Oracle contracts, and the wider library in the Oracle knowledge hub.

What does each settlement shape cost over five years?

The cheapest settlement is usually the one with the smallest support tail, even when its headline discount is lower. Continuing the hypothetical example, say validation shows the Partitioning usage came only from Oracle's own schemas, which removes that line, and corrects the processor count from 60 to 40.

The validated claim is then 40 processors of Database Enterprise Edition, Diagnostics Pack and Tuning Pack: $2,400,000 in licenses at list plus $1,584,000 of backdated support. That is $3,984,000, or 44 percent below the opening ask.

Five year cost is the license fee plus five years of support, before any uplift. Shape B carries the bigger headline, 50 percent off, and costs $1,296,000 more than Shape A over the five years.

Shape C only makes sense if you would have spent $1,200,000 on OCI anyway. Even then, the Support Rewards it earns, up to $300,000 at the standard rate if you consume all of it, reduce a support bill you may be trying to cut.

What did roughly 40 Oracle audit settlements in 2024 and 2025 show?

Across the 35 to 45 Oracle audit settlements we led or benchmarked in 2024 and 2025, the opening claim was almost never the right number. The headline discount was almost never what decided the final cost.

• The validation gap. Validated exposure landed 25 to 50 percent below the opening claim once scope, counting method and entitlement records were corrected.
• The forward close. Roughly 7 in 10 settlements resolved as a forward license purchase or a cloud commitment, and the rest as a payment.
• Backdated support. Oracle reduced or waived it in the large majority of closures where the buyer offered revenue landing inside Oracle's quarter.
• Five year comparisons. Buyers who compared the five year cost of each settlement form paid materially less than those who compared the discount on each.

Get the structure right and the percentage becomes a detail. Get it wrong and no percentage rescues it.

The arguments that worked in those settlements were about quantity and counting method. Appeals to fairness, or to the length of the customer relationship, changed nothing.

When in Oracle's fiscal year should you settle?

Be ready for approval four to six weeks before a quarter ends, with the shape of the deal agreed and only the number still open. Oracle's fiscal year ends May 31, 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 calendar time. A deep discount presented in the final ten days often cannot clear approval in time, which is why the usual advice to hold out until the last day fails.

What will the Oracle account team say, and how should you answer?

Expect the same handful of lines in most settlements. Each has a precise answer, and each answer works best in writing.

Five lines you will hear, with replies

• "This figure already reflects a substantial discount." Ask for the list price build up line by line, then compare it with the net price on your last order for the same program. That comparison is the only discount that counts.
• "We can only waive backdated support if you sign this quarter." Accept the timing on condition that the waiver, the release and a separate CSI all appear in the same draft.
• "Folding this into your renewal keeps it simple." Decline, and ask for the settlement as a standalone document priced on its own merits.
• "A cloud commitment makes the compliance issue go away." Ask what the commitment costs if you consume none of it, and whether licenses are still sold alongside it. Then price both over the term.
• "The script output is conclusive." The output shows what is installed and what ran, not what you owe. Ask which counting rule turned each row into a license, and where that rule appears in your contract.

What should the Oracle settlement agreement say?

Only the settlement letter and the order form bind you, so every concession has to be written into them. Ask for these terms in the first draft, because each one gets harder to add as the quarter closes.

• A release. Name the entities, the programs and a closing date, and state that Oracle releases claims for past use of those programs by those entities up to that date. Without it, the same usage can return in the next audit.
• A separate order and CSI. State that terminating the settlement licenses later will not trigger repricing of support on your other orders.
• Backdated support. Write the waiver or reduction into the order form itself, where it binds Oracle.
• Support pricing. Base support on the net license fee in the order and cap the annual uplift for the term. The wording is in price holds and uplift caps.
• Confidentiality. The current Oracle Master Agreement puts audit data and findings under its nondisclosure section. Older agreements may not, so have the settlement state it.

Which mistakes raise the settlement cost most?

• Pricing before counting. A discount agreed before the count is rebuilt locks in Oracle's quantity.
• Accepting lines by phone. A verbal yes to a finding is hard to reopen. Contest every line in writing against the findings paper.
• Running the scripts beyond the agreed scope. Every extra server or entity you collect data from is a candidate for a new finding. Run the collection only where the agreed scope says.

What to do next

1. Count first. Rebuild the deployment count and the entitlement position before you price anything.
2. Answer in writing. Contest each line of the findings paper with your evidence and the contract clause it rests on.
3. Model five years. Cost cash, forward purchase and cloud commitment side by side, including the support tail each one creates.
4. Draft the protections early. Put a separate CSI and a written release, naming entities, programs and a closing date, into the first settlement draft.
5. Separate and time the paper. Keep the settlement apart from the renewal and target a quarter close you can meet with terms agreed a month or more ahead. Our Oracle practice runs the settlement with you.

Frequently asked questions