ALA versus transactional license models
Not every Micro Focus license is counted the same way, and the model a product is licensed under shapes the entire finding. A grant fixed by an Additional License Authorization counts an entitled quantity; a transactional model counts usage as it happens. ALA versus transactional license models is the distinction between licensing a defined capacity in advance and licensing consumption over time, and a finding that applies the wrong model, counting fixed entitlements as if they were metered usage, or metered usage as if it overran a fixed cap, can overstate the obligation in either direction.
This field note explains how the two models differ, where a finding crosses them, and how the defensible reading holds the count to the model the authorization actually established. It pairs with our ALA and entitlement review track.
What an ALA grant fixes
An Additional License Authorization typically fixes an entitlement: a defined quantity, under a defined metric, granted for a defined term or in perpetuity. The buyer holds that quantity regardless of how the usage fluctuates beneath it. Under this model the audit question is whether the deployment exceeds the fixed entitlement, and the entitlement is a known number the buyer purchased. The compliance question is binary at the boundary: is the deployment within the granted quantity or beyond it. Variation in day to day usage does not matter so long as it stays inside the fixed grant.
A fixed grant licenses a quantity you hold; a transactional model licenses usage you consume. A finding that counts one as the other is measuring against terms the authorization never set.
What a transactional model counts
A transactional or consumption model counts usage as it occurs, often by volume, by event, or by some unit of activity over a period. The entitlement is not a fixed quantity held in advance but a measured amount consumed, and the relevant records are usage logs over time rather than a single granted number. The audit question is what was actually consumed and whether it was paid for, and the answer depends on usage data, which is why the defensible reading of a transactional model rests on the same evidentiary discipline we apply to capacity in how to challenge an ALA capacity measurement.
Where a finding crosses the models
The error appears when a finding measures a deployment under the wrong model. A fixed ALA grant counted as if it were transactional can be charged for peaks of usage that the fixed entitlement already covered, treating ordinary variation as overrun. A transactional entitlement counted as if it were a fixed cap can be charged for exceeding a quantity that the consumption model never imposed. In both directions the finding applies a logic the authorization did not establish, and in both the correction is to read the governing document and count under the model it actually set. This is a structural cousin of the metric substitution examined in ALA named user versus capacity metrics, applied to the shape of the entitlement rather than its unit.
Mixed estates carry both models
Many estates hold both kinds of license, because different products, or different purchases, were sold under different models. A finding that applies one model across the whole estate will overstate wherever the assumption does not match the grant. Each product must be matched to the authorization that governed its purchase and counted under the model that authorization established, fixed or transactional. Sorting this out is part of reading the estate as a set of distinct grants rather than a single uniform arrangement, the same discipline we bring to layered authorizations in stacked and superseded ALAs in a license estate.
How we defend the correct model
Our defense establishes, for each product in the finding, which authorization governed the purchase and which licensing model that authorization set. Where the finding has counted a fixed ALA grant as transactional usage, we restore the fixed entitlement and show that the deployment stayed within it. Where a transactional entitlement has been counted against a cap it never had, we hold the count to the consumption the model actually measures. This is the Reconstruct and Rebut work of our method, and holding the count to the entitlement the buyer genuinely purchased is the same discipline that delivers the 68 percent average reduction we have achieved across more than 200 defended audits, recovering the difference between what was deployed and what the finding assumed.
The model decides what evidence even matters
Choosing the right model is not only about the size of the number; it determines what evidence is relevant in the first place. Under a fixed ALA grant, the decisive record is the entitlement: the granted quantity and the metric, set against a snapshot of the deployment at its boundary. Under a transactional model, the decisive record is usage over time: logs, volumes, and events across the measured period. A finding that applies the wrong model does not merely miscount; it demands the wrong evidence, asking a buyer with a fixed entitlement to account for usage peaks that are irrelevant to a fixed grant, or asking a buyer with a consumption license to prove it stayed under a cap that never existed. Settling the model first tells both sides which records actually decide the question, and it prevents an audit from burying a fixed entitlement under usage data that the grant was never measured by.
Closing the model question forward
Once the present finding has been corrected, the forward agreement should state the licensing model for each product plainly, so a future review cannot reopen the count by switching models. A clean forward arrangement records whether each entitlement is a fixed grant or a transactional one, defines how usage is measured under each, and removes the ambiguity that let the audit cross the two. Resolving the finding and fixing the model forward are two halves of the same work. If a finding has counted your fixed entitlement as metered usage, or your usage against a cap you never agreed to, open a case and we will hold the count to the model the authorization set.
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.
Counted under the wrong model?
We match every product to the authorization that governed its purchase and hold the count to the model the grant actually set, fixed or transactional, not whichever overstates the obligation. Open a case and recover the difference.
Open A Case →