Oracle Post Merger True Up

What is a post merger true up?

A post merger true up is the reconciliation and settlement of an Oracle licensing gap that surfaces after a transaction has closed, when the combined or acquired estate is found to deploy more than it is entitled to and Oracle requires the shortfall to be purchased. It is the bill for the diligence that did not happen, or did not go deep enough, and it lands on the acquirer because the liability attached to the entity it now owns. The true up is Oracle's preferred outcome from a transaction it was not consulted on, because the buyer is negotiating from the weakest possible position: it already owns the problem.

The true up is distinct from an ordinary audit settlement in that it is precipitated by the deal itself, often by Oracle noticing the transaction in the press or through a support contract change and opening a review in response. The acquirer, mid integration, is poorly placed to resist. This article sits under the license compliance pillar and is the recovery path for transactions that did not follow the due diligence playbook.

Why true ups happen after the deal

True ups surface after close for a predictable set of reasons. The transaction combined two estates whose deployments now exceed the sum of their entitlements, because consolidation enabled options or expanded user populations. The acquired entity carried compliance gaps that diligence missed or skipped. The deal triggered the assignment or change of control clause, and Oracle's price for consenting to the transfer is the true up. Or the integration itself, migrating workloads onto shared infrastructure, created new exposure that neither party had before.

The common thread is that the leverage moved to Oracle at close. Before the deal, the buyer could have allocated the cost to the seller or made consent a condition; after the deal, those options are gone and Oracle holds a clean compliance claim against an owner who cannot easily walk away. Recognising this dynamic is the first step in managing the true up, because it tells the acquirer that its position, while weaker than it should have been, is not hopeless if it can still produce its own evidence. The reconciliation that produces that evidence is in the effective licence position guide.

Managing the true up demand

Even from the back foot, a true up is a negotiation, not an invoice to be paid on receipt. The acquirer's defence rests on the same discipline that governs any audit: establish its own reconciled position before accepting Oracle's, test every element of Oracle's claim against the contract definitions, separate genuine gaps from disputed interpretations such as virtualisation or indirect use, and remediate what can be remediated technically before conceding it commercially. An option enabled but not needed can be disabled; a user population can be bounded; a virtualisation claim can be contested.

The goal is to convert Oracle's opening demand, which is invariably framed at list price across the broadest interpretation, into a settlement bounded by the buyer's evidence and remediation. This is the audit defence discipline applied to a transaction trigger, and it routinely reduces the demand substantially, because Oracle's opening number assumes the buyer will not push back. The full defensive method is in the audit defence pillar, and the engagement support is the audit defence practice.

Recovering from the seller

Where the true up arises from pre close non compliance, the acquirer may have recourse against the seller, but only if the deal documents provided for it. Representations and warranties about compliance, indemnities covering Oracle liabilities, and escrow arrangements are the instruments that allow an acquirer to push a true up cost back to the seller after the fact. Their existence and scope are determined entirely before close, which is why the diligence and deal drafting phase matters even for risks that only materialise later.

An acquirer facing a true up should therefore review the deal documents in parallel with managing the Oracle demand, to establish whether the liability is recoverable and to preserve any notice or claim deadlines. Where no such protection was negotiated, the acquirer bears the cost alone, which is the expensive lesson that makes the case for the due diligence workstream on the next deal. The standing capability that prevents the next surprise is software asset management across the combined estate.

The buyer side view

A post merger true up is a worse position than a properly diligenced deal, but it is not a lost one. The acquirer still controls its own evidence, and a true up negotiated from a reconciled position, with genuine gaps remediated and disputed interpretations contested, settles for a fraction of Oracle's opening demand. The mistake is to treat the demand as a fixed bill rather than an opening move, and to pay it before establishing what is actually owed under the contract.

The deeper lesson is preventive: the true up exists because the leverage was given away at close, and the cure is to run the Oracle workstream before the next transaction rather than after. Manage the current demand as an audit defence, recover from the seller where the documents allow, and resolve never to inherit an unmeasured Oracle estate again. To manage a post merger true up or build the diligence capability that prevents the next one, request a consultation.