ALA metric definitions versus the order form

A Micro Focus license lives in two documents that have to agree, and findings are built where they do not. ALA metric definitions versus the order form is the central reading problem in an entitlement dispute, because the order form names the product and the quantity while the Additional License Authorization defines what the metric actually means. When an auditor reads one without the other, the opening number can drift far from what the buyer agreed to pay for.

This field note explains how the two documents relate, where the gap between them inflates a finding, and how to reconcile them into a single defensible position. It pairs with our ALA and entitlement review track.

Two documents, one entitlement

The order form is the transactional record. It states the product purchased, the quantity, the unit named on the order, and the commercial terms that applied at the time. The Additional License Authorization is the definitional layer. It explains what the named unit counts, how it is measured, and what conditions attach to the grant. Neither document is complete on its own. The order says how many of something you bought; the ALA says what that something is. A reading that takes a quantity from the order and a definition from a different version of the ALA produces a number neither document supports.

Where the gap inflates a finding

The expensive gap appears when the metric named on the order is interpreted under a definition the order never referenced. A unit described loosely on a purchase order, such as a user or an instance, can be read narrowly or broadly depending on which definition is applied. An auditor inclined toward the larger figure will favour the reading that counts more of the estate. Where the order form names a unit and the controlling ALA defines it precisely, the definition that governed the purchase is the one that decides the count, not whichever definition produces the higher shortfall.

Version drift between order and authorization

Authorizations are revised over time, and a buyer's estate often spans several purchases made under different versions. A metric defined one way at the time of an order may be described differently in a later authorization. Treating the latest definition as if it governed an earlier purchase is version drift, and it is a frequent source of inflation. The defensible position pairs each order line with the authorization version in force when that line was bought, so the count rests on the terms that actually applied.

Quantity is not the same as scope

An order form quantity is a ceiling expressed in a unit, not a description of where the software may run or who may use it. The scope conditions, the territory, the use restrictions, and the deployment rules live in the authorization. A finding that treats a quantity as the whole of the entitlement, ignoring the conditions that define how that quantity may be deployed, misreads the grant. Reading quantity and scope together is what turns two partial documents into one complete entitlement, a discipline we describe further in ALA territory and use restrictions.

Reconstructing the entitlement from both records

The defense begins by assembling the complete paper trail: every order form, the authorization version each order referenced, and any amendments. We then build the effective license position from the documents that actually governed each purchase, before any vendor measurement script runs. This is the Reconstruct step in our method, and it is decisive here because the buyer who holds a reconciled record of order and authorization can answer the finding with the contract rather than with an estimate. The reconciliation discipline is the same one set out in reconciling ALA entitlements before an audit.

Challenging a mismatched finding line

When a finding line rests on a definition the order never referenced, the challenge is documentary. We identify the order that established the entitlement, produce the authorization version that governed it, and show the count the auditor used against the count the governing definition actually supports. Where the two diverge, the line is reduced to the figure the contract supports. In a recent engagement, pairing aging order forms with the authorization versions in force at the time of purchase removed a substantial portion of an entitlement based shortfall, the same pattern of correction reflected in our E-01 case file, where a seat count finding moved from $7.2M to $1.6M, a 78 percent reduction.

Order form ambiguity favours the reader who prepared

Order forms are often terse, naming a product and a quantity with little definitional detail, and that brevity is precisely why the authorization matters. An ambiguous order line is not an invitation for the vendor to choose the broadest reading; it is a reason to return to the authorization that gives the unit its meaning. A buyer who has already mapped each order line to its governing definition controls the interpretation, while a buyer who waits is left arguing against a definition chosen for its size rather than its accuracy.

Bundled orders need line by line treatment

Where an order form records a bundle or a suite rather than discrete products, the entitlement for each component still flows from the authorization, not from the bundle label. Treating a bundle as a single undifferentiated grant lets a finding count components under metrics that never applied to them. The defensible approach unpacks the bundle into its components and pairs each with its governing definition, a method we detail in how ALA bundles obscure true entitlement. Only then does the order quantity translate into a count that the contract actually supports.

Closing the gap in the forward agreement

Once a finding is reduced to its defensible figure, the remaining work is to stop the same ambiguity from recurring. A forward agreement that fixes the metric definition, records the unit precisely on the order, and removes the distance between the transactional and the definitional record makes the next review start from agreed terms. Resolving the present dispute and closing the gap that produced it are two halves of the same task, and doing both is how an order to authorization mismatch stops being a recurring liability.

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 a mismatch between your orders and your authorizations is driving a finding, open a case.