Defending an ALA based finding line by line

An audit finding arrives as a single intimidating total, but it is built from many separate lines, and each line stands on assumptions that can be tested. Defending an ALA based finding line by line is the discipline of refusing to negotiate the total until every line beneath it has been examined against the Additional License Authorization that governs it. The total is the vendor's story about the estate. The lines are where that story can be shown to be wrong.

This field note sets out the order of attack on an entitlement based finding, what to challenge in each line, and how the reductions accumulate. It pairs with our ALA and entitlement review track.

Never negotiate the total first

The most common and most costly mistake is to treat the headline figure as the thing to bargain down. A total presented for negotiation invites a discount, and a discount leaves the flawed structure intact. The defensible approach treats the total as merely the sum of contestable lines and works upward, correcting each line on the contract before any conversation about settlement begins. When the lines are corrected, the total falls on its own, and it falls further than any discount would have moved it.

Line one: the mapping and the metric definition

The first line to test is whether each product was mapped to the correct authorization and metric, because everything downstream inherits that choice. We confirm which grant governed each purchase and what the metric actually counts under that grant, the discipline described in how OpenText maps products to ALAs in an audit. Where a product was mapped to a broader metric than its purchase invoked, correcting the mapping reduces the count before any individual user or core is even examined.

Line two: scope and conditions

Once the metric is correct, the next line tests the conditions on the grant: territory, permitted use, deployment topology, and any environment restrictions. A finding that counts deployments outside the licensed scope, or that ignores conditions limiting how a quantity may be used, overstates the obligation. Reading the scope conditions against the deployment removes counts the grant never authorised, a layer we examine in ALA territory and use restrictions.

Line three: the count itself

With metric and scope settled, the count becomes testable. We examine whether the figure includes service accounts, dormant users, decommissioned systems, non production environments, or passive standby nodes that the metric does not capture as licensable consumers. Each inclusion that the definition does not support is removed. Counts assembled from raw discovery data routinely sweep in items that the contractual metric excludes, and separating the licensable from the merely present is where a large share of the reduction is found.

Line four: the remedy stack

A noncompliance finding is not a single charge. The licensee is deemed to have acquired the shortfall at then current list price, must pay back maintenance and support, must pay first year maintenance on the new licenses, and reimburses the costs OpenText incurs performing the audit. One shortfall becomes several charges stacked together. Each layer of the stack depends on the shortfall figure beneath it, so every reduction in the count cascades through the stack and reduces the total by more than the count reduction alone.

How the reductions accumulate

Because the lines are layered, corrections compound rather than merely add. A mapping correction reduces a count; the reduced count carries a smaller list price charge; the smaller charge carries less back maintenance and less first year maintenance. A single early correction therefore moves the total at every level above it. This compounding is why line by line defense produces reductions that surprise buyers who expected only a modest discount. In a recent engagement, working an entitlement finding from the mapping upward removed the majority of the opening figure, the same pattern reflected in our E-01 case file, where a seat count finding moved from $7.2M to $1.6M, a 78 percent reduction.

Documenting each correction

Every line correction must be evidenced, because an audit conversation is won on documents, not assertions. For each line we hold the order form, the governing authorization version, the deployment evidence, and the measurement record, so each reduction rests on a fact the vendor can verify rather than a position the vendor can simply reject. The evidentiary discipline is the same one set out in reconciling ALA entitlements before an audit, and it is what turns a plausible argument into an unanswerable one.

Why line by line beats a global settlement

A buyer offered a global settlement is being asked to accept the structure of the finding in exchange for a number. Line by line defense refuses that trade. It insists that each component be correct before any total is agreed, which means the eventual settlement rests on a corrected finding rather than a discounted wrong one. The difference is not merely tactical. A settlement built on corrected lines also produces a cleaner forward position, because the same corrections that reduced the finding define the entitlement going forward. A global settlement leaves the underlying ambiguity in place to resurface at the next review.

Converting the corrected finding forward

When the lines are corrected and the total has fallen to its defensible figure, the final step is to convert forward on the buyer's terms. A forward agreement that carries the corrected metric definitions, the agreed scope, and the count methodology turns the work of the defense into durable protection, so the next review begins from settled terms rather than contested ones. Resolving the present finding and writing its corrections into the forward agreement are two halves of the same task, and completing both is how line by line defense stops the same finding from returning.

For the full method, read the complete OpenText audit defense playbook, and for entitlement defense across the Micro Focus estate see our ALA and entitlement review track. If you are holding an entitlement finding you want taken apart line by line, open a case.