Reconciling inherited audit settlements and obligations is one of the most overlooked tasks after close, and one of the most expensive when it is missed. When a target settled a software audit before the deal, it rarely just paid a number and moved on. It signed a settlement agreement with binding forward terms: a capped deployment, a fixed product list, a true up schedule, restricted use rights, sometimes a waiver of future claims that lapses on a change of control. Those obligations transfer with the estate, and the moment you own the entity you own the duty to comply. This page sets out how we reconcile inherited settlements on the buyer's side as part of post close license reconciliation.
What reconciling inherited audit settlements and obligations involves
Reconciling inherited audit settlements and obligations means locating every audit a target previously resolved, reading the settlement terms in full, and folding the resulting commitments into the combined license position so the new owner stays inside them. A settlement is not a closed chapter. It is a live contract with conditions that continue for years, and those conditions frequently sit outside the standard licensing agreements that diligence reviews. They live in side letters, settlement deeds, and compliance certificates that the target's procurement team filed and forgot. If you do not go looking for them, you inherit obligations you cannot see and breach terms you never read.
Why inherited settlements carry forward obligations
Publishers do not settle audits for a one off payment alone. They use the settlement to lock in future revenue and constrain future use. Common forward terms include a deployment cap that the entity must not exceed, a defined set of licensed products with everything else explicitly out of scope, an agreed maintenance baseline, and an annual certification that the entity confirms compliance. Some settlements include a most favoured terms clause for the publisher or a right to re audit on a shorter cycle. Each of these is a tripwire. A combined entity that consolidates infrastructure, adds users, or migrates workloads can breach a cap or step outside the licensed product list without anyone realising a settlement ever set the boundary.
Where the settlement terms hide
The hardest part of reconciling inherited audit settlements and obligations is finding them. Standard diligence reviews the master agreements and the order forms, but settlement terms are usually recorded separately. Look for settlement deeds, audit closure letters, compliance certificates, amended order forms with unusual quantities, and email trails that reference a true up. The finance ledger can betray a settlement through a large one off licensing payment in a prior year. Procurement minutes sometimes record the decision to settle. We treat any of these as a flag to request the full settlement document, because the headline payment matters far less than the forward terms attached to it.
| Obligation | What it requires | How integration breaches it |
|---|---|---|
| Deployment cap | Usage must not exceed an agreed quantity | Adding combined entity users or cores |
| Fixed product scope | Only named products are licensed | Standardising onto a different edition or module |
| Maintenance baseline | Support must be maintained on a defined estate | Cancelling support to cut cost |
| Annual certification | Entity must certify compliance each year | New owner misses the filing date |
| Shortened re audit cycle | Publisher may re audit sooner | Combined estate audited before it is reconciled |
Key takeaways
- A target that settled an audit signed forward obligations that transfer to the buyer at close, not just a one off payment.
- Settlement terms hide in deeds, closure letters, and compliance certificates that standard diligence does not always pull.
- Deployment caps, fixed product scope, and certification deadlines are the obligations integration most often breaches.
- Reconciling these terms into the combined position before integration prevents a breach that reopens the audit.
- An inherited certification deadline missed by the new owner is a breach even if usage is fully compliant.
Fold the obligations into the combined position
Once located, each obligation has to be carried into the combined entity license position as a hard constraint, not a footnote. A deployment cap becomes a ceiling the consolidation plan must respect. A fixed product scope becomes a rule that blocks standardising the acquired entity onto a different edition without re licensing. An annual certification becomes a calendar item with an owner. The point of reconciliation is to make these invisible constraints visible to the people running integration, so that entity consolidation does not trigger a breach that no one knew was possible.
Why this matters more after a change of control
A change of control sharpens inherited settlement risk in two ways. First, it can lapse a waiver. Some settlements waive the publisher's right to pursue historic claims only while the entity stays under its current ownership, so the protection the target bought can evaporate the day you close. Second, a change of ownership is itself a trigger that draws publisher attention. Vendors monitor corporate filings, and an acquired entity with a recent settlement is a known quantity worth re auditing. This is the same dynamic covered in post close license true up risk, and it is why inherited settlements deserve priority in the first ninety days.
Quantify the inherited obligation as exposure
Treat an unreconciled settlement obligation as quantifiable exposure, not a compliance chore. The exposure is the cost of breaching the term: a re audit settlement priced at list, the loss of a negotiated discount, or the penalty written into the settlement itself. Public cases show how large inherited licensing exposure can become once a publisher prices it. As of mid 2025, SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million over disputed and inherited licensing, which underlines why a forward obligation left unmanaged is a real number, not a theoretical one.
Recommendations for buyers
- Request every settlement document, not the summary. The forward terms matter more than the headline payment.
- Build an obligations register at close. List each cap, scope limit, and certification with an owner and a deadline.
- Constrain integration to the inherited terms. Block consolidation moves that would exceed a cap or step outside licensed scope.
- Check whether the change of control lapses any waiver. Protection the target bought may not survive the deal.
- Quantify each obligation as exposure. Price the cost of breach so the deal team can weigh it against the integration plan.
Reconciling inherited audit settlements and obligations protects the combined estate
An inherited audit settlement is a contract the buyer never negotiated but is bound to honour. Reconciling inherited audit settlements and obligations means finding those buried terms, folding the caps, scopes, and deadlines into the combined license position, and treating each as quantified exposure rather than paperwork. Do that early and integration proceeds without reopening an audit the target thought it had closed. We trace and reconcile these obligations from the buyer's side only, paid solely by the acquirer, and we hand the deal team a register it can actually manage.