The deemed acquisition at list price clause explained.

The reason an OpenText finding lands so high is rarely the size of the shortfall. It is the remedy that sits on top of it. Under the standard clause, a licensee found noncompliant is deemed to have acquired the missing licenses at the then current list price, must pay back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost of the audit. One gap becomes several charges.

Understanding this clause is the difference between negotiating a number and negotiating a structure. Buyers who treat the finding as a single figure argue about the total and lose. Buyers who understand that the figure is assembled from distinct layers can challenge each layer on its own terms, and that is where the reduction comes from.

Layer one: the shortfall priced at list

The first layer is the alleged gap between what you are entitled to and what the vendor says you are using, priced not at the discount you originally negotiated but at the current published list price. This single mechanic can multiply a finding several times over, because enterprise software is rarely bought at list. A product acquired years ago at a steep discount is repriced at full rate for the purpose of the remedy.

The shortfall itself is the most contestable layer, because it depends entirely on the metric and the population the vendor has counted. A named seat count that sweeps in service accounts and dormant users, an events per second figure that conflates burst with sustained throughput, or a core count that includes non production environments will all overstate the gap before list pricing is even applied. Reconstructing that population is the heart of the defense, and it is described across our track pages and in the complete OpenText audit defense playbook.

Layer two: back maintenance and support

On top of the repriced shortfall, the clause typically requires payment of back maintenance and support, as though the licenses had been properly held and maintained over the period in question. This treats the alleged underlicensing as a historical fact and charges for the support that would have accompanied it. Because back maintenance is calculated from the shortfall, every license stripped out of the shortfall removes its share of back maintenance too. The layers are linked, and reducing the base reduces everything stacked on it. We examine the mechanics in detail in back maintenance and first year maintenance on a finding.

Layer three: first year maintenance on the new licenses

The licensee is also commonly required to pay first year maintenance on the licenses deemed acquired, as if they were a fresh purchase. So the same shortfall drives a list price charge, a backward looking support charge, and a forward looking maintenance charge. Three figures, one underlying population. This is why the population question matters more than any other in the exercise.

Layer four: the cost of the audit

Finally, the clause usually requires the licensee to reimburse all costs the vendor incurs in performing the audit. This layer is often presented as non negotiable, but it is contingent on a finding of noncompliance in the first place, and its scope can be questioned like any other line. The fuller treatment of who carries audit cost, and when, is in who pays for an OpenText audit and how cost recovery works.

A worked example of how the layers compound

Consider how the layers interact in practice. Suppose a vendor alleges a shortfall of a thousand units and prices them at a list rate several times the discount you originally paid. That repriced shortfall is layer one. Back maintenance is then calculated as though those thousand units had been licensed and supported across the period under review, adding a second figure tied directly to the first. First year maintenance on the deemed acquisition adds a third. Audit cost recovery sits on top as a fourth. Each layer is a function of the same thousand units, so the total is not the shortfall plus a fixed penalty. It is the shortfall multiplied through several mechanisms at once.

Now suppose reconstruction shows that four hundred of those units were service accounts, dormant users, duplicates across systems, or non production environments that never belonged in the count. Removing them does not reduce the finding by forty percent of one layer. It reduces the base that all four layers are calculated from, so the list priced charge, the back maintenance, the first year maintenance, and the cost recovery all fall together. This compounding is precisely why the population question dominates everything else, and why a discount on the headline total is a far weaker outcome than a correction at the base.

Why the clause is written this way

The structure is deliberate. List pricing removes the benefit of any discount you negotiated. Back maintenance and first year maintenance convert a one time gap into a recurring obligation. Audit cost recovery shifts the expense of the exercise onto the party being audited. Taken together, the clause is designed to make noncompliance expensive enough that settlement looks like relief. The defense does not dispute that the clause exists. It disputes the inputs the clause is applied to.

What list pricing does to an old discount

The list price mechanic deserves particular attention because it quietly undoes years of careful procurement. Enterprise software is almost never bought at the published rate. A buyer negotiates volume discounts, competitive concessions, and bundle pricing, and the effective rate paid can be a fraction of list. The remedy clause sets all of that aside. For the purpose of a shortfall, the deemed acquisition is priced at the then current list price, as though no discount had ever been agreed. A product that cost a quarter of list when it was bought is repriced at full list when it is found short, so the same unit can be several times more expensive inside a finding than it was inside the original order.

This is why the size of an alleged gap is so much more consequential than it first appears, and why the population question is never merely administrative. Each unit wrongly swept into the shortfall is charged at the highest possible rate and then carries its share of back maintenance and first year maintenance on top. Removing it removes the most expensive version of that unit from the finding. The discipline of pricing the defensible position against the actual entitlement, rather than accepting list pricing on an inflated count, is a recurring theme across our defense tracks.

How the layers come down

Because compliance is treated as the sole responsibility of the licensee, the vendor will present the finding as settled fact and invite you to true up. It is not settled fact until the population, the metric, and the entitlement have been independently reconstructed. The four Rs method exists to do exactly that: take over the channel, rebuild the effective license position, challenge each line of the finding, and resolve on the buyer's terms, often by converting the exposure into a clean OpenPass enterprise agreement with defined metrics. The negotiation that follows is covered in true up negotiation tactics under audit pressure, and the contractual basis for the vendor's position in why compliance is the sole responsibility of the licensee. If you are staring at a finding built this way, you can open a case.