Home  ›  Articles  ›  ALA & Entitlement

Documenting ALA entitlements for a rebuttal

ALA & EntitlementField noteUpdated May 2026

A rebuttal is only as strong as the records behind it. A finding presents the vendor's count; the answer to it is the buyer's evidence of what was actually granted. Documenting ALA entitlements for a rebuttal means assembling the authorizations, order forms, and deployment records that establish the licensed position, organised so each line of the finding can be met with the document that governs it. Without that assembly, even a correct objection collapses into assertion. With it, the objection becomes a record the vendor must answer.

This field note explains which documents carry the entitlement, how to organise them so a rebuttal lands, and why the buyer who holds the evidence sets the terms of the conversation. It pairs with our ALA and entitlement review track.

The burden the contract puts on the buyer

The EULA states that compliance is the sole responsibility of the licensee. That allocation is not only a liability rule; it is an evidentiary one. It means the buyer is expected to be able to show what it is entitled to, and a finding is built on the assumption that the buyer cannot. The most effective rebuttal turns that assumption around by producing the records the vendor presumed were missing. The documents do not merely support the objection; they shift who has to do the explaining.

The principle

A finding is a claim about what the buyer cannot prove. A documented entitlement turns the claim back: here is the grant, here is the order, here is the deployment within it. Now the vendor must answer the record.

Which records carry the entitlement

The entitlement lives across a small set of document types, and a rebuttal needs all of them aligned. The Additional License Authorization states the grant, the metric, and the conditions. The order form names the quantity purchased and ties it to a date and a price. The deployment record shows what is actually running and how it maps to the metric. Together these answer the three questions a finding raises: what was granted, how much was bought, and whether the deployment falls within it. We set out the full inventory of supporting records in what records support an ALA entitlement position, and the present note focuses on assembling them into an answer.

Aligning the documents to the finding

A pile of contracts is not a rebuttal. The records must be aligned to the finding line by line, so that each count the vendor asserts is met with the authorization that governs it and the deployment evidence that places the use inside the grant. Where the finding counts a deployment as unlicensed, the rebuttal points to the order form that bought it and the authorization that permits it. Where the finding applies the wrong metric, the rebuttal points to the metric the authorization actually specifies. This line by line alignment is the same discipline we describe in defending an ALA based finding line by line, and the documentation is what makes that defense more than argument.

Reconstructing what cannot be found at once

Few estates hold every document neatly filed. Authorizations sit in legal, order forms in procurement, deployment data in operations, and some records have to be reconstructed from renewals, invoices, and correspondence. The work of building the position from incomplete records is reconstruction, and it is most effective done before the vendor's measurement runs, not in response to it. Assembling the entitlement baseline ahead of time, as set out in how to build an ALA entitlement baseline, means the rebuttal is ready when the finding arrives rather than being chased after it.

Documentary disputes resolve faster

Entitlement disputes that turn on documents close more quickly than those that turn on argument, because there is little to debate once the grant and the deployment are both on the table. A buyer who can produce the authorization that permits a counted deployment removes that line from the finding without a prolonged exchange. The cleaner and more complete the record, the less room the finding has to persist, and the faster the number comes down. This is why we treat documentation not as a formality but as the core of the rebuttal.

How we build the documented rebuttal

Our defense assembles every authorization, order form, and deployment record that touches the products in the finding, aligns them to the vendor's count line by line, and reconstructs whatever the estate cannot produce directly. We then present the entitlement position as a record rather than an objection, so each count is met with the document that governs it. This is the Reconstruct and Rebut work of our method, and the discipline of answering a finding with evidence rather than assertion is what moved our E-01 case file from a $7.2M finding to a $1.6M settlement, a 78 percent reduction, once the entitlement behind each disputed seat was documented and aligned to the count.

A controlled channel protects the record

How the documentation reaches the vendor matters as much as what it contains. A rebuttal built on careful records can be undermined if material is handed over piecemeal, out of context, or through several uncoordinated contacts, because a document read in isolation can be made to support a reading its surrounding terms would not. The discipline that protects the record is a single controlled channel: one route through which entitlement evidence is assembled, reviewed, and presented as a coherent position rather than leaked as fragments. The buyer who controls the channel controls the framing, and the framing is part of the rebuttal. Records presented as an organised answer, with each document accompanied by the authorization and order that give it meaning, are far harder to turn against the buyer than the same records produced one at a time on request.

Closing the documentation question forward

Once the present finding has been answered, the records that defeated it should be kept current, so the next review starts from a maintained position rather than a scramble. A forward agreement that records the entitlements clearly, and a practice of keeping the authorizations, order forms, and deployment data aligned, turns the rebuttal that worked once into a standing defense. Resolving the finding and maintaining the record forward are two halves of the same work. If a finding has reached your estate and you need the entitlement documented before you respond, open a case and we will assemble the answer.

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.

Need the entitlement documented before you answer?

We assemble the authorizations, order forms, and deployment records that prove the grant, and align them to the finding line by line so each count is met with the document that governs it. Open a case and answer with a record, not an argument.

Open A Case →
When an OpenText or Micro Focus audit notice arrives, the first seven days carry more weight than any week that follows. OpenText Audit Defense is an independent, buyer side firm founded in 2020 by former vendor compliance leadership. We have defended more than 200 audits, reduced the average finding by 68 percent, and mitigated more than $90M in claims. We do not resell OpenText software, and we are not affiliated with OpenText Corporation. To open a case, use the contact form on this site.