Oracle renewal quote decoded line by line.

An Oracle renewal quote arrives as a deceptively simple document. Two pages, a list of Customer Support Identifier numbers, a list of program names, a column of fees, and a total. Underneath the simplicity is a precise instrument designed to maximise the rate at which your support spend grows. This article walks line by line through a representative renewal quote and explains what each component is doing, where the negotiable money sits, and what to push back on.

The Customer Support Identifier number

Every line on a renewal quote begins with a CSI number. The CSI is the unique identifier Oracle assigns to a support agreement, and it is the key that links the renewal quote to the specific deployment rights and support service level you bought. CSI numbers are not a billing convenience. They are a contract index. Each CSI carries its own start date, its own anniversary, its own service level, and its own ratable footprint.

The first task on any renewal quote review is to confirm that every CSI on the quote belongs to your organisation and to a programme you still use. Oracle's support quoting system has a long tail of inherited CSIs from past acquisitions, divisions that have been divested, and legacy hardware that has been decommissioned. Removing dead CSIs from the renewal is the single highest yield activity we perform in the first 30 minutes of a renewal engagement.

The program name and version

The second column is the Oracle program name and the version against which support is being renewed. The program name links to the Oracle Technology Global Price List and to the Oracle Applications Global Price List, which define the underlying licence economics. The version matters because Oracle's Lifetime Support Policy divides programs into Premier Support, Extended Support, and Sustaining Support phases, each with a different fee multiplier and a different scope of coverage.

If your renewal quote shows a program on Extended Support, you are likely paying an Extended Support uplift of 10 percent on top of the base support fee. If your program is on Sustaining Support, you are likely paying base support for no new patches and no security updates. The first negotiation question on either case is whether the customer can migrate to a still supported version before the anniversary, and if not, whether the Extended Support uplift can be waived as part of a multi year renewal.

The quantity and metric

The third column is quantity, expressed in the metric defined on the original order document. Common metrics are Processor, Named User Plus, Application User, Custom Application User, Universal Credits, and Employee. Each metric has a different conversion to deployed capacity, and the metric on the renewal quote should match the metric on your original order.

If your renewal quote shows a quantity that has drifted from the quantity on your last quote, ask why. Drift sometimes reflects a legitimate true up. More often it reflects a quote system glitch, or worse, an Oracle attempt to fold deployment counts from an audit into the renewal stream. Every quantity should reconcile to the order document and to your internal Software Asset Management record.

The list price and the support fee

The fourth column is the list price. The fifth is the support fee. Oracle's standard support fee is 22 percent of net licence fee. Net licence fee is the price paid on the original transaction, not the list price. If your renewal quote shows a support fee at 22 percent of list rather than 22 percent of net, you are being overcharged. Push back. The correction can run six and seven figures on a large renewal.

The support fee carries an annual uplift, sometimes called the CPI uplift, that compounds year over year. Standard Oracle uplift sits between 4 and 8 percent. Some long tenured customers have a contractually capped uplift, often 3 percent. The renewal quote does not always disclose whether your uplift is contractually capped or whether Oracle has applied the standard uplift in error. The mark up is to confirm the contractual cap on every renewal.

The matching service level footnote

Most Oracle renewal quotes carry a footnote referring to Oracle's matching service level policy. The footnote is anodyne. The policy is not. Matching means that if you hold multiple licences of the same Oracle program, all of those licences must carry the same support level. You cannot drop support on half and keep support on the other half.

The implication is that partial support termination is economically prohibitive unless you can certify that the licences whose support you wish to drop are not in active use. The mark up is to negotiate a limited matching exemption that permits the partial drop. Oracle signs this language on large renewals. ULA Negotiation walks through the related ULA mechanics where matching has different implications.

The auto renewal clause and the termination window

The renewal quote sits inside the auto renewal mechanism in the OMA. The customer must affirmatively terminate the support agreement before the anniversary date, in writing, on Oracle's specified address, within Oracle's specified window. The window is typically 45 to 90 days before the anniversary, depending on the contract version.

If you miss the window, the renewal becomes binding even if you object after the date. If you signal termination but fail to follow Oracle's exact written notice procedure, Oracle will treat the signal as informal and the auto renewal will fire. We routinely audit our client base each spring for missed termination windows and find one or two every year. The remedy is to put the termination window in your contract management calendar with a 30 day pre alert and to send the termination notice via certified mail with delivery confirmation.

The negotiation steps

With the line by line review complete, the negotiation runs in three steps. Step one is correction of any errors in the quote, including dead CSIs, incorrect support level, support fee calculated against list rather than net, and uplift applied above the contractual cap. Step two is consolidation, in which we co term renewals, eliminate duplicate CSIs, and combine quotas where Oracle's matching rule permits. Step three is the multi year mark up, in which we trade extended commitment for fee hold, uplift cap, and contract term improvements.

Across the typical engagement, step one yields 5 to 12 percent savings, step two yields a further 4 to 9 percent, and step three yields the remainder of the 38 percent average we deliver. Every step is documented in writing so your procurement team can defend the final position to Oracle and to internal finance. For the broader framework see the pillar at Oracle Renewal Negotiation. For deeper reading on the timing question see Oracle quarter end renewal leverage. For the contract term context see Co-term Renewal and the Oracle Database product page. For the full negotiation framework download The Oracle Negotiation Playbook.