What records support an ALA entitlement position

A finding is only as strong as the entitlement record it is measured against, and the entitlement record the vendor uses is one the vendor itself maintains. To defend the count, the buyer needs its own record of what it holds, built from the documents that prove entitlement contractually rather than the vendor's internal summary. What records support an ALA entitlement position is the practical question of which documents establish, line by line, the licenses a buyer purchased under its Additional License Authorizations, and assembling them deliberately is what turns a defensive posture into an evidenced one.

This field note sets out the records that carry entitlement, how they fit together, and how a complete record holds a finding to what was actually bought. It pairs with our ALA and entitlement review track.

The order form and its authorization

The foundational record is the order form together with the Additional License Authorization it incorporates. The order form states what was bought and in what quantity; the authorization defines the metric, the rights, and the conditions attached to that purchase. Read together, they establish both the number and the terms under which it is counted, which is why they sit at the centre of any entitlement position. The decisive role these documents play, and how they outweigh a vendor summary, is the subject of reducing an ALA finding with order form evidence.

Renewal and maintenance records

Maintenance and support contracts are entitlement records in their own right, because they presume and reference the underlying licenses they cover. A support renewal that names a product and quantity is evidence that the entitlement existed at the time of renewal, even where the original order form is missing, and the continuity of support payments establishes that the license was held and maintained across the period. These records frequently bridge gaps in the purchase history and confirm the persistence of an entitlement the vendor summary may have dropped. The forward obligations they carry are examined in ALA support and maintenance obligations.

Amendments, migrations, and true ups

Entitlement is rarely static. It is amended, migrated between products, expanded at true up, and carried forward through acquisitions, and each of those events generates a record that changes the entitlement picture. A migration document that converted one product entitlement into another, a true up that added quantity, an amendment that changed a metric, all of these must be in the record, because a finding that ignores them measures against a frozen and incomplete version of the entitlement. Gathering these change records is central to the reconstruction described in reconciling ALA entitlements before an audit.

Deployment and usage records

Entitlement records prove what the buyer is allowed to run; deployment records prove what it actually runs, and the finding is the gap the vendor asserts between them. A buyer's own deployment data, inventory exports, configuration records, and usage logs, is essential evidence, because it lets the buyer test the vendor's scan against an independent account of the estate. Where the vendor count includes instances that are dormant, decommissioned, or non production, the buyer's deployment records are what demonstrate it. Pairing entitlement with deployment evidence is the structure of defending an ALA based finding line by line.

How a complete record reduces the number

In a recent engagement, a finding rested on a vendor entitlement summary that recorded only the most recent renewal quantity, while the buyer's records held an earlier order form and a migration document that together established a larger entitlement carried forward. Assembling those records into a single chain restored the full entitlement and removed the asserted shortfall on the affected lines. This is the ordinary effect of a complete record: each document that proves entitlement the vendor summary understated, or deployment the vendor scan overstated, subtracts from the finding. Built carefully across an estate, this evidentiary discipline is a large part of how we deliver the 68 percent average reduction we have achieved across more than 200 defended audits.

Organizing the records into a position

Records become a position only when they are organized to answer the finding directly. The defensible structure maps each line of the finding to the specific documents that establish the true entitlement and the actual deployment for that line, so the rebuttal is not a stack of paperwork but a line by line demonstration. Building that mapping, and presenting it so the burden shifts onto the finding to justify any number that exceeds the record, is the discipline set out in documenting ALA entitlements for a rebuttal. The records do not argue on their own; the position built from them does.

Keeping the record current

The record that defends this finding should not be allowed to lapse before the next review. Maintaining a current entitlement record, updated as orders, renewals, and migrations occur, means the next audit meets a prepared position rather than a scramble, and it removes the ambiguity that lets a finding overreach. The work of assembling the record for a present finding becomes the baseline that protects future ones. If an audit is measuring your deployment against an entitlement record you cannot see or verify, open a case and we will build the documented position that holds the count to what you bought.

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.