Stacked and superseded ALAs in a license estate

Few estates hold a single, clean authorization. Over years of purchases, renewals, and product changes, a buyer accumulates a layer of Additional License Authorizations, each governing what was bought when it was bought. Stacked and superseded ALAs are the result: multiple authorizations covering the same product family, some still in force, some replaced, and some that overlap in ways no one mapped at the time. A finding that reads this layer carelessly counts the same entitlement twice, applies an old metric to a new purchase, or ignores a grant that a later authorization carried forward.

This field note explains how layered authorizations form, where a finding goes wrong when it treats them as a flat stack, and how the defensible reading reconstructs the true position from the documents. It pairs with our ALA and entitlement review track.

How a license estate accumulates layers

Each purchase of a Micro Focus product is governed by the Additional License Authorizations in force at the time of that order. Buy a product in one year, expand it two years later, and renew the whole arrangement a year after that, and the estate now holds three documents that all speak to the same product. The terms are not always identical. Metric definitions evolve, bundles change shape, and capacity language is rewritten between versions. The estate is not one grant but a sequence of grants, and the entitlement that governs a given deployment is the one that applied to the purchase that put it there.

Most buyers never reconcile this sequence until an audit forces the question. The order forms sit in procurement, the authorizations sit in legal, and the deployed software sits in the data centre, and no single record ties the three together. That gap is exactly what a finding exploits.

Where a stacked reading inflates the finding

The first error is double counting. When two authorizations cover the same product, an auditor who adds the quantities together, or who counts a deployment against one authorization while the entitlement actually sits in another, manufactures a shortfall that does not exist. The estate has the entitlement; it is simply recorded across more than one document. Treating each authorization as a separate, additive obligation overstates demand while ignoring the supply already on the books.

The second error is applying the wrong metric. A later authorization may define a capacity term differently from the one it replaced. A finding that measures a deployment purchased under the earlier grant against the later metric, or the reverse, produces a count neither document supports. The deployment must be read against the terms that governed its purchase, not against whichever definition happens to inflate the number most.

Superseded does not always mean gone

The word superseded invites a careless conclusion: that the replaced authorization no longer matters. That is rarely true in full. A renewal or a new master arrangement frequently carries forward entitlements granted under the prior document, and the perpetual rights established earlier do not evaporate because a later contract was signed. Reading only the most recent authorization, and treating everything before it as void, can erase entitlements the buyer still holds. The defensible reading establishes what each authorization granted, what the later one replaced, and what it expressly preserved, so that nothing the buyer paid for is written out of the position. This is closely tied to the work of tracing version rights set out in version entitlement under Micro Focus ALAs.

Reconstructing the true entitlement position

Defending against a stacked finding is reconstruction work. We assemble every authorization that touches the product family, order them by the purchase each governs, and map which grant applies to which deployment. Where two documents cover the same product, we establish which entitlement is live, which was carried forward, and which was genuinely replaced, so the count is measured against the supply the estate actually holds rather than against an inflated sum. This is the Reconstruct phase of our method, and it depends on the same baseline discipline described in how to build an ALA entitlement baseline and the pre audit reconciliation in reconciling ALA entitlements before an audit.

An example of the layered correction

In a recent engagement, a finding counted a product family as if two authorizations were additive, doubling the apparent demand while ignoring that the later document had carried forward the entitlement granted under the earlier one. Once we sequenced the authorizations and showed which grant was live and which had simply been renewed rather than added to, the supposed shortfall closed against entitlements the estate already held. The discipline of reading the stack as a sequence, not a pile, is the same one that moved our E-01 case file from a $7.2M finding to a $1.6M settlement, a 78 percent reduction, by holding each count to the grant that genuinely supported it.

A layered estate hides supply, not only demand

It is worth restating what a careless stacked reading actually misses. A finding looks for demand, the deployed software that might exceed entitlement, and it is good at finding it. What a finding does not look for is supply that is recorded in a document other than the one it happened to open. When entitlements are spread across renewals and superseding arrangements, the supply side of the position is easy to undercount, and an undercounted supply produces an inflated shortfall just as surely as an overcounted demand does. Reading the full sequence of authorizations is therefore not only a defensive precaution against double counting; it is how the buyer surfaces entitlements it already holds but has not assembled in one place. The estate frequently contains more supply than the finding credits, and the layered documents are where that supply has been hiding.

Closing the layered estate forward

Once the present finding has been corrected, the layered estate should be consolidated forward so a future review does not repeat the double count. A clean forward agreement records the live entitlements in one place, states which prior authorizations it supersedes and which it preserves, and removes the ambiguity that let the audit add documents together. Resolving the finding and consolidating the estate are two halves of the same work, and completing both keeps the next review from starting where this one did. To put the documents in order before an auditor does, open a case with our team.

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.