Are license prices negotiable at an audit settlement?
Yes, license purchases at settlement are negotiable on both the discount and the support tail, and because Oracle wants the deal closed, a settlement can secure a better discount than a routine purchase if you only buy what you genuinely need. The settlement is a moment of unusual leverage. Oracle has a strong incentive to convert the finding into a clean sale, and that incentive can be turned into a better unit price, a higher discount, or more favourable support terms than the same licenses would attract in an ordinary deal. The buyer who treats the purchase as a negotiation rather than a remediation captures that value.
This is one of the most consequential parts of the overall negotiation, set out in the Oracle negotiation guide. The purchase is not a fixed consequence of the finding. It is a deal, and deals are shaped.
A settlement purchase is a negotiation with leverage, not a fine. The discount, the quantity and the support terms are all on the table, and the moment Oracle wants to close is the moment you have the most room.
How much should you buy at settlement?
You should buy only the licenses the verified, reduced finding actually requires, because buying ahead of need locks in a support tail of roughly 22 percent a year on quantities the business may never use. The quantity question is decided by the line by line review, not the preliminary finding, so the first discipline is to ensure the base has already been cut to what the evidence and contract support. From that reduced number, you buy to genuine need, resisting any push to round up or to acquire capacity for hypothetical growth that carries a permanent support cost.
The alternative of a forward commitment such as a ULA is sometimes offered instead of a discrete purchase, and the trade off between the two is examined in ULA versus buying licenses at settlement. Buying licenses keeps the position simple and bounded. A ULA can suit a genuinely growing estate but introduces certification risk later, so the choice depends on the roadmap, not the sales pitch.
What is the support tail on a settlement purchase?
The support tail is the recurring support fee, around 22 percent of license value with annual escalation, that attaches to every license you buy, so the long term cost of a settlement purchase far exceeds its headline price. This is why the quantity decision matters so much. A license bought once is paid for many times over through support, and the escalation compounds the base every year. A settlement that looks affordable on the headline can become a heavy recurring burden if the support tail was ignored when the quantity was set.
Because the tail is so large, it is itself a negotiation point. The discount on the license, the support rate, and the escalation terms all affect the lifetime cost, and a buyer who negotiates only the headline discount leaves the most expensive part of the deal untouched. The support tail is the long game, and it should be negotiated as deliberately as the purchase price.
| Element | One time | Recurring |
|---|---|---|
| License fee | Headline, discount negotiable | None |
| Support | None | About 22 percent yearly, escalating |
| Excess quantity | Paid once | Support on unused licenses forever |
The discount, support rate and escalation available at settlement are contract dependent and set by your negotiation, ordering documents and Oracle Master Agreement. The figures here are indicative and meant to show where the long term cost sits, not predict your terms.
A worked example of a settlement purchase
Consider a finding reduced by the line by line review to a genuine gap of 40 processor licenses. Oracle proposes a settlement purchase of 60, framed as headroom for growth at an attractive discount. The buyer who accepts the 60 banks a one time discount but commits to support on 20 licenses the business does not need, at roughly 22 percent a year escalating, for years. The buyer who holds to 40 pays for the genuine gap, negotiates the discount and the support rate on that quantity, and avoids a permanent tail on unused capacity. The headline saving on the larger deal is illusory once the support tail is counted.
How do you structure the purchase?
You structure the purchase by fixing the quantity to verified need, negotiating the discount and the support rate together, and pinning down the escalation and any future repricing exposure before you sign. The concessions Oracle is typically willing to trade, from discount depth to terms that protect you later, are mapped in the concessions Oracle will trade. Structuring also means looking ahead to how the new licenses sit within your grouped agreements, because that affects what you can later reduce without triggering repricing. A well structured purchase is bounded, fairly priced, and free of surprises in the support stream.
Your next step
A settlement purchase is a deal with real leverage, and the buyers who size it to need and negotiate the support tail pay far less over its life. An independent buyer side review fixes the genuine quantity, negotiates the discount and the support terms, and structures the purchase to avoid a costly tail. Download the settlement playbook for the full method on sizing and structuring a settlement purchase.
Read the Oracle Settlement Negotiation Playbook, or the full Oracle negotiation guide, for the complete method.