Why the findings are negotiable.
Oracle's preliminary findings letter quantifies a license gap in unit terms and translates the gap into a dollar amount at Oracle's published list price. Neither input is fixed. The unit count rests on a chain of assumptions about deployment scope, virtualisation rules, options usage, and contract interpretation. The list price translation rests on the assumption that the customer will pay full undiscounted retail for net new licenses. The buyer side response challenges both inputs. The contractual challenge reduces the unit count. The commercial challenge reduces the price per unit. Both challenges run in parallel and both contribute to the settlement reduction.
The contractual levers.
The contractual levers reduce the license unit count by challenging the methodology Oracle used to count the deployment. The first lever is the scope challenge. Findings outside the audit scope are removed. The second lever is the script artefact challenge. Findings that are artefacts of the script methodology rather than actual licensable deployment are removed. The third lever is the contract definition challenge. Findings that conflict with the contract definition of licensable use are removed. The fourth lever is the virtualisation challenge. Findings based on Oracle's soft partitioning position where the contract supports a harder partitioning interpretation are reduced.
The commercial levers.
The commercial levers reduce the price per unit. The first lever is the discount challenge. Oracle does not charge list price on commercial deals. The settlement should reflect the customer's negotiated discount, not the published list. The second lever is the support stream challenge. Oracle's findings typically include retroactive support for the period of unlicensed deployment. The buyer side position is that support is purchased prospectively, not retroactively. The third lever is the format challenge. The settlement does not need to take the form Oracle proposes. A license purchase, a support stream extension, a cloud commitment, and a contract restructuring are all settlement formats. The format that best serves the customer's commercial interests is the format the buyer side selects.
Findings negotiation checklist
- Scope challenge to remove out of scope findings.
- Script artefact challenge with documented technical analysis.
- Contract definition challenge with buyer side legal review.
- Virtualisation challenge with deployment documentation.
- Discount challenge with reference to the customer's pricing history.
- Support stream challenge to remove retroactive support.
- Settlement format selection that serves the customer's roadmap.
The discipline in the response.
The buyer side response to the preliminary findings letter is a documented, structured, written response. The response is not a meeting. The response is a written document that addresses every finding in the order Oracle presented them. Each finding is challenged on contractual grounds and commercial grounds. Each challenge is supported by documentation. The documentation is included with the response. The response is treated as a formal commercial document and is reviewed by buyer side counsel before submission.
The timing of the negotiation.
The timing of the negotiation matters. Oracle's preliminary findings letter typically includes a response deadline. The deadline is a starting point for negotiation, not a fixed date. The buyer side response includes a timeline counter proposal that allows for documented review. Oracle may push back on the timeline. The buyer side discipline is to hold the timeline that supports a documented response. A rushed response that misses contractual challenges costs more in settlement than the time it saves in the audit.
The leverage in the closing.
The closing of the audit creates leverage that does not exist during the audit. Oracle's commercial team wants the audit closed and the revenue recognised. The closing date is typically aligned to an Oracle fiscal quarter or year end. The buyer side discipline is to use the Oracle fiscal calendar to time the settlement negotiation. A settlement that closes in Oracle's last week of the quarter is typically more favourable than a settlement that closes in the first week. The fiscal calendar is a buyer side lever and should be used.
The documentation after settlement.
The documentation after settlement is the final discipline. The settlement is documented in a closing letter and a contract amendment. The amendment defines the licenses purchased, the support stream, the discount, and the future deployment rights. The buyer side review of the amendment is the last opportunity to fix any drafting ambiguity. The amendment becomes the basis for the next audit cycle. A clear amendment prevents the next audit. An ambiguous amendment seeds the next audit.
The independent advisor.
The audit findings negotiation is the single most leveraged engagement in the Oracle customer cycle. The findings reduction is typically the largest single dollar saving in the customer's Oracle relationship. The buyer side advisor pays for itself in every audit we have defended. The advisor brings the methodology, the documentation discipline, the contract interpretation experience, and the commercial pacing that produce the 71 percent average reduction. Customers who defend audits without independent advice typically settle at 60 to 80 percent of the findings letter. Customers who defend with independent advice typically settle at 15 to 30 percent.
Related resources.
- Audit Defense pillar guide
- Audit Defense service
- Contract Review service
- ULA deal type page
- Oracle Database product page
- Oracle Audit Defense Handbook 52 page reference paper.
- Oracle LMS Audit Process Explained related sub article.