Why are the finding and the deal two negotiations?
The finding and the deal are two negotiations because they answer different questions: the finding is a compliance question about what you already owe under your existing agreement, and the deal is a commercial question about what, if anything, you choose to buy in future. They have different facts, different leverage, and different right answers. Mixing them lets the weaker of the two ride on the stronger, and in an audit the finding is usually the weaker, because a preliminary finding arrives inflated at list price and an independent line by line review typically cuts it 60 to 80 percent.
When the two are merged, the buyer ends up paying for future product to settle a past claim. That is precisely the outcome Oracle's process is designed to produce, and it is precisely the outcome a disciplined buyer separates. The finding is settled for what the contract actually supports. The deal, if there is one, is judged on whether the product earns its keep on its own. This topic links up to the Oracle negotiation guide, and it sits beside negotiating the remediation, not the list price.
How does Oracle use the audit as a sales channel?
Oracle uses the audit as a sales channel by presenting a forward looking purchase as the way to make an inflated finding disappear, so a ULA, an OCI commitment, or a Java subscription is offered as the path to settlement rather than as a product decision on its merits. Analysts estimate that 20 to 30 percent of Oracle's on premises license revenue flows from audits, and findings feed directly into ULA renewals, OCI commitments, and the per employee Java Universal Subscription. The finding creates the pressure, and the deal is offered as the relief.
The mechanism is effective because it arrives at a moment of stress. A large preliminary number lands, the response window is 30 to 45 days, and a sales motion appears offering to resolve the whole thing if the buyer commits to a forward purchase. The purchase is framed as a discount on the finding, when in truth it is new spend layered on top of a claim that was never validated. Recognising the move is half of defeating it, because once the finding and the deal are seen as separate, the leverage shifts back to the buyer. For how this plays into a ULA, read the panic ULA, how audits sell agreements.
| Dimension | The finding | The deal |
|---|---|---|
| Question | What do you owe? | What might you buy? |
| Basis | Your existing contract | A future business case |
| Buyer move | Validate and reduce, 60 to 80 percent | Judge on its own merits |
| Risk if merged | Paid at list as the price of the deal | Bought under pressure, not on value |
How do you keep the finding and the deal apart?
You keep the finding and the deal apart by validating and reducing the finding to its defensible number first, settling the genuine compliance gap on the contract, and only then opening any conversation about a forward purchase as a separate decision with its own justification. The sequence is the discipline. The finding is taken line by line, every inflation tested against the agreement rather than the policy paper, and the corrected number established before any sales proposal is entertained. That corrected number is what you owe, and it is the basis for settling the compliance question.
Only once the finding is resolved does any deal get considered, and then strictly on whether the product serves the business. A ULA may make sense for an estate that is genuinely growing. An OCI commitment may make sense for a real cloud plan. A Java subscription may be the right answer for an estate that genuinely uses Oracle Java widely. But each is decided on its own merits, in its own time, with its own business case, not as the consideration for making an audit go away. Where the timing or the contract makes the separation genuinely hard, the position is contract dependent and is worked through before any signature.
The finding is what you owe under the contract you have. The deal is what you might buy in future. Settle the first on its merits before you ever discuss the second.
Our negotiation guide separates the finding from the deal, validates and reduces the compliance claim, and tests any forward purchase on its own business case. Fixed Fee or Gainshare, with no risk to you.
What is the buyer move?
The buyer move is to validate and reduce the finding to its defensible number first, settle the genuine compliance gap on the contract, and treat any forward purchase as a separate decision judged on its own business case, never as the price of closing the audit. Refuse to let a sales proposal be the route out of a finding. Take the finding line by line and establish what the contract actually supports. Settle that. Then, separately and without pressure, decide whether any product Oracle is offering earns its place in your estate. To carry this into the settlement itself, work across to negotiating support terms at settlement and up to the Oracle negotiation guide.
FAQ
Why split them? The finding is what you owe under your contract; the deal is what you might buy. Oracle uses audits as a sales channel, so keeping them apart stops a contested finding becoming a purchase.
How does Oracle merge them? By offering a ULA, OCI commitment, or Java subscription as the way to make an inflated finding go away.
What is the buyer move? Validate and reduce the finding first, settle the compliance gap, then judge any purchase on its own merits.