Why recost the Oracle estate after an audit?
You recost the Oracle estate after an audit because a settlement usually adds licenses and resets the support baseline, so the post audit estate carries a new and often higher recurring cost that must be modelled rather than assumed. The settlement closes the compliance question, but it opens a financial one. Whatever you agreed to buy or true up now sits on the books at a support rate of roughly 22 percent of license value, and that support escalates annually. An estate that is not recosted simply absorbs the new run rate and discovers the full impact a year or two later.
This recosting is the bridge between the audit and ongoing cost control, and it sits within negotiation strategy more broadly, set out in the Oracle negotiation guide. The discipline is to treat the day the settlement is signed as the start of a cost programme, not the end of a problem.
A settlement resets your baseline. If you do not rebuild the cost model from the signed outcome, the new recurring cost becomes invisible until the escalation makes it impossible to ignore.
What changes in the cost model after an audit?
What changes after an audit is the license count, the support base, any cloud or OCI commitment taken as part of the settlement, and the annual escalation that now applies to a larger number. Each of these moves the recurring run rate. New licenses add directly to the support base. A settlement that includes an OCI commitment introduces a consumption obligation that has to be planned and used, not just paid. The escalation, applied to a higher base, compounds faster than before. The model that described your estate before the audit no longer describes it.
The OCI element deserves particular care, because settlements increasingly route value into cloud commitments rather than pure license fees, as examined in the OCI commitment in audit settlements. Whether that commitment is an asset or a liability depends entirely on whether you can consume it usefully, which is a recosting question.
How does the support baseline reset?
The support baseline resets because the new licenses are added at a support rate tied to their settlement price, and that becomes part of the support contract going forward with its own escalation. The licenses you acquired in the settlement are not a one off cost. They carry support at the standard rate, and that support joins the existing stream. If the settlement was structured without attention to the support tail, you can find that the recurring cost of the resolution exceeds the headline figure within a few years of escalation.
This is also where matching service level rules re enter, because the new licenses are now part of grouped agreements that constrain how you can later reduce. Any plan to trim the estate after the dust settles runs straight into repricing risk, covered in repricing risk when dropping licenses. Recosting therefore has to look forward, mapping not just today's run rate but how it escalates and what you can and cannot change later.
| Element | Before audit | After settlement |
|---|---|---|
| License count | Existing estate | Existing plus trued up |
| Support base | Prior baseline | Higher, reset to new total |
| Cloud commitment | None or prior | Possible new OCI obligation |
| Escalation | On smaller base | On larger base, compounds |
A worked example of recosting
Consider an estate that settles an audit by acquiring additional database licenses and accepting a modest OCI commitment. The headline settlement looks like a one time cost. The recosting tells the fuller story. The new licenses add to the support base at roughly 22 percent, and that support escalates each year. The OCI commitment must be consumed or it is wasted spend. Modelled over three years, the recurring cost of the settlement is materially larger than the headline, and the OCI commitment is only worth its price if a genuine workload migration is planned to absorb it.
The recosting turns this from a surprise into a plan. It identifies that the OCI commitment should be tied to a real migration, that the new support stream should be reviewed at the next renewal, and that any later reduction must account for repricing. The settlement becomes the input to a cost programme rather than a number that simply lands on the budget.
How support, escalation and any OCI commitment apply after a settlement is contract dependent and set by your signed outcome, support policies and Oracle Master Agreement. The figures here are indicative and meant to show the shape of the recosting, not predict your result.
How do you find savings after an audit settlement?
You find savings after an audit settlement by right sizing what you now own, modelling repricing risk before dropping anything, and structuring future renewals so the post audit baseline does not quietly escalate. Right sizing comes first, because the settlement may have left you with licenses you can consolidate or retire as workloads change. Modelling repricing protects the saving, because a careless termination can erase it. Renewal structuring is where the durable gains sit, since the support escalation is the long term cost, and a renewal is the moment to reset it.
The forward view connects to budgeting a changing estate, covered in budgeting Oracle in a shrinking estate, and to avoiding the habits that lock cost in, set out in the support mistakes that lock in cost. Recosting is the analysis. These are the moves it enables.
Your next step
Recosting is how an audit settlement becomes a managed cost rather than a hidden escalation, and it is best done as soon as the outcome is signed. An independent buyer side review rebuilds your cost model from the settlement, maps the support escalation and any OCI commitment, and finds the durable savings the recosting reveals. Book a strategy call to recost your estate after a settlement, model the three year run rate, and identify where the saving sits before the next renewal.
Book a strategy call to recost your estate and map the post audit run rate. Start at the contact page, or read the full Oracle negotiation guide.