Why counter claims work.
An Oracle audit is presented as a one way examination of the customer's deployment. The framing is incomplete. The customer has its own claims against Oracle that arise from the same commercial relationship. Over delivered licenses, mis applied support charges, double counted entitlements, and unfulfilled contractual commitments are all examples of buyer side claims. The audit creates an opportunity to bring these claims into a single negotiation. The combined negotiation reaches a more favourable settlement than a one sided audit defence. The counter claim strategy is documented, conservative, and supported by evidence. It is not a litigation tactic. It is a commercial leverage tactic.
The over delivered license claim.
The over delivered license claim is the most common counter claim. The customer has purchased Oracle licenses that exceed actual deployment. The over delivery may have arisen from forecasted deployment that did not materialise, from a project that was cancelled, or from a deployment plan that changed. The over delivered licenses continue to attract support charges. The buyer side claim is for the value of the over delivered licenses and the associated support stream. The claim is documented by reference to the purchase history and the current deployment inventory. The settlement may take the form of a credit against the audit findings, a reduction in the support stream, or a license swap.
The mis applied support claim.
The mis applied support claim arises when Oracle has charged support on entitlements that have been terminated, swapped, or migrated. Oracle's billing systems do not always reflect contract amendments. The buyer side review of the support history may reveal charges that should not have been billed. The claim is for refund of the mis applied charges. The settlement may take the form of a credit, a refund, or a reduction in the future support stream. The discipline is to document the support history against the contract history before raising the claim.
The double counted entitlement claim.
The double counted entitlement claim arises when the same deployment has been licensed under two separate Oracle agreements. The double counting may have arisen from an acquisition, from a contract consolidation, or from an internal procurement error. The buyer side claim is for credit of one of the two licensing positions. The settlement may take the form of a license consolidation, a credit against the audit findings, or a contract amendment that removes the duplicate entitlement. The discipline is to document the contract chain and the deployment chain.
Counter claim categories
- Over delivered licenses with continued support charges.
- Mis applied support charges on terminated entitlements.
- Double counted entitlements from contract overlap.
- Unfulfilled contractual commitments from prior agreements.
- Discount erosion below the most favoured customer position.
- Audit scope expansion beyond the contractual audit clause.
The unfulfilled commitment claim.
The unfulfilled commitment claim arises when Oracle has made contractual commitments that have not been delivered. The commitments may include training credits, professional services hours, cloud credits, or specific support response times. The buyer side claim is for the value of the undelivered commitments. The settlement may take the form of a credit, a delivery of the commitments, or an extension of the commitment period. The discipline is to document the original commitment and the actual delivery before raising the claim.
The documentation standard.
The counter claim documentation standard is high. Each claim is supported by contract text, by financial records, and by deployment data. The documentation is prepared before the claim is raised. The claim is presented in a structured document that mirrors the Oracle findings letter. The structure includes the contract basis, the financial calculation, the supporting documentation, and the proposed settlement. The structure produces a counter claim that Oracle can evaluate quickly and that the buyer side can defend.
The timing of the counter claim.
The timing of the counter claim affects its impact. A counter claim filed at the start of the audit signals buyer side resolve and shapes the audit pace. A counter claim filed at the closing meeting reshapes the settlement. The buyer side discipline is to file the counter claim at the closing meeting where the audit settlement is negotiated. The closing meeting is the venue where the audit findings and the counter claims are reconciled into a single commercial position.
The commercial framing.
The counter claim is framed as a commercial reconciliation, not as a dispute. The buyer side position is that the commercial relationship has produced obligations in both directions and that the settlement should reflect the net position. The framing keeps the conversation in the commercial channel and avoids escalation to legal. The framing is reinforced by the buyer side single point of contact who manages the relationship through the settlement.
Related resources.
- Audit Defense pillar guide
- Audit Defense service
- Contract Review service
- Perpetual Licenses deal type page
- Oracle Database product page
- Oracle Audit Defense Handbook 52 page reference paper.
- Oracle Audit Findings Negotiation related sub article.