What an Oracle audit costs, all in. The settlement is one of seven layers.

An Oracle audit costs the settlement plus six other layers, each paid from a different budget at a different time. Most of the all in figure is fixed in the first 30 days, before anyone discusses a number.

How much does an Oracle audit cost, all in?

An Oracle audit costs the settlement plus six other layers: support charged back, the forward support tail, internal effort, external advice, remediation engineering, and any commitment attached to the close. Six of the seven are still moving after signature, so the final bill almost always exceeds the figure the board was given.

Only the settlement appears on Oracle's proposal. Build the table below on day one of the audit, before anyone has a number. Once every row carries an estimate, the settlement figure stops being the whole conversation.

Why are the seven layers never added up?

Each layer has a different owner and a different accounting period. The license sits in one budget, support in another, engineering in a third, and the hours in none at all. Since no single person is asked to total them, the total never gets built, and the board hears the settlement figure as though it were the cost.

Putting that total in one sheet, once, is the most valuable hour a finance lead spends on an audit. Give each layer a named owner and put an estimate in every cell, even a rough one, before Oracle's claim arrives.

Does Oracle pay any of the cost of running the audit?

No. Oracle's standard master agreement allows Oracle to audit on 45 days written notice and requires your cooperation and reasonable assistance. It also says Oracle "shall not be responsible for any of Your costs incurred in cooperating with the audit." Every internal hour and adviser invoice is yours, whatever the findings turn out to be.

Why does the support tail cost more than the settlement?

Support runs every year the licenses stay supported, at roughly 22 percent of net license fees, so five years of it costs more than the licenses you buy to settle. That fact should decide the shape of the settlement. In most post mortems we saw, it surfaced at the following renewal instead.

A worked example on $400,000 of settlement licenses

Say the audit closes with licenses bought at a net fee of $400,000. Support on those licenses then runs at $88,000 a year. The table follows the money for five years, before any renewal adjustment Oracle applies to the annual fee.

By the end of year five you have paid $440,000 in support on $400,000 of licenses. The five year cost of the settlement is $840,000, more than twice the headline, and that is before any support charged back for past use.

Why can the support tail only be shaped at purchase?

Two of Oracle's published technical support policies fix the tail once the order is signed.

• Matching service levels. Every license in a license set must sit at the same support level. You cannot leave the settlement licenses unsupported while the rest of that product stays on support.
• Repricing. If you later terminate some licenses on an order, support on the remaining licenses on that order is repriced at Oracle's current support list price less the standard discount.

So the things that shrink the tail have to be agreed before signature: the quantity, the license type, the discount that flows into the support line, and which ordering document the licenses land on. The recurring support arithmetic across a whole Oracle contract is covered in our guide to Oracle support costs in 2026.

Is backdated support negotiable?

It often is. Support charged back for the period of unlicensed use is frequently waived or shortened in settlement, so treat it in Oracle's first proposal as an opening position. Ask for it as a separate line, where you can see it and argue it.

Lapsed support follows a published rule. If the settlement adds licenses to a product where support on older licenses has lapsed, Oracle can require those back on support as well. The reinstatement fee is 150 percent of the last annual support fee paid, prorated back to the lapse date, plus the fee for the new support period.

How many internal hours does an Oracle audit consume?

A mid sized database audit consumes 200 to 600 hours, concentrated in a small group of senior people over four to nine months. None of it is invoiced, so it appears in no business case, yet it was often the largest cost after the licenses and their support. The spread by role is consistent enough to model.

Each band is the range we see for that role when it is heavily involved. Few audits hit the top of every band at once, and a narrowly scoped review may barely involve some roles, which is why the total stays inside 200 to 600.

How do you put a dollar figure on the hours?

Multiply the midpoint of each band by your loaded cost per hour, then put the total on the same page as the settlement. In most organizations the result surprises the finance lead more than the finding did. Say your loaded rate for senior technical and commercial staff is $120 an hour.

Use your own loaded rate, with benefits and overhead included, instead of the salary figure. Then add the cost of the work those people were supposed to be doing.

What does the displaced work cost?

The audit lands on the eight or so people you can least spare, the same people who run upgrades, hardware refreshes and other supplier renewals. The pattern we see most is a migration or consolidation slipping a quarter because the database team cannot do both. That delay is never booked as an audit cost.

Price the slip anyway. If a consolidation that retires Oracle processors slips past the support renewal date, you pay another full year of support on processors you meant to drop, plus whatever else the project was meant to save.

When is the all in cost of an Oracle audit decided?

Largely in the first 30 days, before any figure is discussed. The decisions that set the boundaries for every later number are made early, and at the time they do not feel like financial decisions.

• Scope. What the audit is permitted to look at: which products, legal entities and environments.
• Who answers. Which people are allowed to respond to Oracle, and what data leaves the building.
• Measurement. Whether you ran your own count before Oracle's collection.
• Coordination. Whether the response runs through one voice or is improvised across four teams.

The buyer who models the support tail on day thirty negotiates a different deal from the buyer who learns about it on day four hundred.

That difference has nothing to do with negotiating skill. It comes from knowing, while the shape of the deal is still open, what each shape will cost over five years. The settlement tactics are in our audit negotiation guide, and the line by line challenge of a finding is in fighting an audit claim.

Why saving your effort for the negotiation costs more

The usual account of an audit puts the money at the end. A claim arrives, a negotiation happens, a figure is agreed, so the common advice is to keep the early phase light and save your effort for the settlement talks.

We disagree. In the engagements we review, the all in cost was mostly fixed before the first claim, by scope and evidence choices made in the first month. Put the effort in early, while a scope limit or your own count can still change what Oracle is able to claim.

How do you check your own position before Oracle collects?

• Options and packs. Query DBA_FEATURE_USAGE_STATISTICS, or run the options_packs_usage_statistics.sql script from My Oracle Support, on every database, including standby and test copies.
• Virtualization. Export host, cluster and virtual machine placement from vCenter or your hypervisor console. Oracle's partitioning policy treats VMware as soft partitioning, so Oracle counts physical hosts and often argues for every host the virtual machine could move to.
• Entitlements. Collect every ordering document and support renewal, and reconcile them against the support contracts listed in My Oracle Support.
• Standby and recovery. List every Data Guard and standby configuration and how each one is licensed today.
• A dry run. Follow the internal review sequence in our guide to conducting an internal Oracle license audit, using the scripts described in our guide to Oracle compliance scripts.

What does remediation cost after an Oracle audit?

Remediation is engineering work that needs its own budget line. It is the layer most often discovered after signature, then funded late from a different budget once the next planning cycle has closed. Funded in the same business case as the settlement, it stops the exposure recurring in three years with better data.

Why should remediation come before the next collection?

Sequence the fix ahead of Oracle's next measurement, so the evidence that the problem is gone exists when someone asks for it. For option removal, that means feature usage records whose last usage date falls before the change, with no use since, filed with the change tickets that record the work.

What should you spend on external advice in an Oracle audit?

Spend advisory money on two things: an independent count before Oracle has one, and the structure of the closing paper. Without your own number you are negotiating against the only measurement in the room. The rest of the audit work can be done in house, provided one person owns it.

How should an adviser be paid?

A percentage of savings looks attractive to finance, but it prices the adviser's incentive against a baseline Oracle wrote. A high opening claim inflates both the saving and the fee. Read what any contingent fee is measured against before you sign the engagement.

Whatever the fee model, insist on independence. An adviser who also resells Oracle, or partners with Oracle on implementation, is not positioned to tell you the finding is wrong.

What will Oracle's account team say, and how should you reply?

Expect the conversation to shift from the finding to a purchase. A settlement that arrives with a forward commitment converts a one time exposure into a spend floor for the next three to five years, owned by whoever owns the roadmap. Prepare replies to these lines before the first settlement meeting.

What should the settlement paper say?

The closing paper decides several of the layers, so read it as a cost document. Ask for these terms before you sign.

• A release for the audited period. Written confirmation that the audit is closed for the products and entities in scope, so the same facts are not reopened.
• Backdated support waived or shortened. Shown as its own line, never folded into the license price.
• Support that follows the discount. Support is a percentage of the net fee for as long as the licenses are supported, so every point of license discount carries forward.
• The settlement licenses on their own order. Because repricing works order by order, a separate order means you can later terminate the settlement licenses whole without repricing an order you still depend on.
• No commitment inside the settlement. Any cloud or subscription purchase goes on separate paper and is judged on its own merits.
• A remediation window. Agreed time to remove option usage or change deployments found in the audit, with no further claim for that period.

What did Oracle audit cost reviews show in 2024 and 2025?

Across roughly 35 to 45 Oracle audit engagements we led or benchmarked in 2024 to 2025, the finance story was consistent enough to predict. Three findings recurred in almost every post mortem.

1. Only the settlement was budgeted. Finance had planned for the settlement and nothing else, so the support consequence surfaced at the following renewal.
2. The hours were never costed. Internal effort, often the largest cost after the licenses and their support, was missing from every business case.
3. The fix was funded late. The engineering needed to stop the exposure recurring came from a different budget, usually after the next planning cycle had closed.

Forward commitments were the other constant: 6 in 10 of the settlements we reviewed arrived with one attached. The exposures that most often required remediation were the virtualization boundary, uncatalogued option usage and standby counting. The virtualization boundary is worked through in our virtualization licensing guide.

What to do next

1. In week one. Build the seven layer sheet, with a named owner for each layer and an estimate in every cell, before a claim figure exists.
2. Before Oracle collects. Run your own count of options, virtualization and standby, so you are never negotiating against Oracle's number alone.
3. Cost the hours. Price internal effort at loaded rates and put the total on the same page as the settlement, so finance can see it.
4. Model the tail. Run five years of support for every settlement shape under discussion, because it can only be changed at the moment of purchase.
5. Scope the advice. Limit adviser spend to the independent count and the closing paper, and check what any contingent fee is measured against.
6. Fund the fix. Put remediation in the same business case as the settlement and finish it before the next collection. Our Oracle practice builds the model with you, and the Oracle knowledge hub holds the wider library.

Frequently asked questions