ALA perpetual versus subscription terms

Whether a license persists after a payment lapses, or evaporates with it, is one of the sharpest distinctions in any Micro Focus estate, and a finding that gets it wrong can charge a buyer for software it already owns outright. ALA perpetual versus subscription terms is the difference between a grant that gives the buyer a lasting right to use a version it has paid for and a grant that licenses use only for the duration of an active term, and a finding that treats a perpetual entitlement as a lapsed subscription, or counts a subscription beyond the right it conveyed, can misstate the obligation in ways that the governing authorization plainly resolves.

This field note explains how the two term models differ, where a finding confuses them, and how the defensible reading holds the count to the right the authorization actually granted. It pairs with our ALA and entitlement review track.

What a perpetual grant conveys

A perpetual license conveys a lasting right to use the licensed version, typically of the software as it existed at the time of purchase, and that right does not end when maintenance lapses. Maintenance and support are separate from the license itself: dropping support may end the right to new versions and vendor assistance, but it does not retract the perpetual right to continue running the version already licensed. A finding that treats a lapse of support as a lapse of the license itself misreads the grant, and separating the perpetual right from the support obligation is the foundation of the defense. The support side of this relationship is examined in ALA support and maintenance obligations.

What a subscription term licenses

A subscription, or term license, grants use only for a defined period, and the right ends when the term ends unless it is renewed. Under this model the entitlement is bounded in time as well as quantity, and the relevant compliance questions include whether the deployment stayed within the term and whether use continued after expiry. The exposure that arises when a term lapses or comes up for renewal is its own subject, examined in ALA term expiry and renewal exposure, and a finding that counts subscription use must be read against the term the authorization set, not against an open ended assumption.

Where a finding confuses the models

The error appears when a finding applies the wrong term model to an entitlement. A perpetual license counted as a lapsed subscription can be charged as though the buyer must re acquire software it already owns, treating an expired support contract as an expired license. A subscription counted as if it were perpetual can understate or misstate the renewal obligation. In both directions the finding asserts a term the authorization did not establish, and the correction is to read the governing document and apply the term model it actually set. This is the same structural discipline applied to entitlement shape in ALA versus transactional license models, here turned on the duration of the right rather than how it is counted.

Mixed estates carry both term models

Most Micro Focus estates of any age hold both perpetual and subscription licenses, because purchasing models shifted over time and because different products were sold on different terms. A finding that assumes a single term model across the estate will misstate wherever the assumption does not match the grant, and the correction is to match each product, and often each purchase, to the authorization that governed it. This per grant reading is the same discipline required to untangle layered entitlements, set out in what is an Additional License Authorization, applied here to the term each grant carries.

How the distinction reduces the number

In a recent engagement, a finding charged a buyer for re acquiring a product on the basis that its support had lapsed, treating the lapse as the end of the license. The governing authorization granted a perpetual right to the licensed version, separate from support, so the perpetual entitlement remained intact and the deployment was within it. Restoring the distinction between the owned license and the lapsed support removed the re acquisition charge entirely. This is the ordinary mechanism: each perpetual right correctly distinguished from a support lapse, and each subscription held to its actual term, subtracts from the finding. Applied across an estate, this contributes to the 68 percent average reduction we have achieved across more than 200 defended audits.

Version rights follow the term model

The term model also shapes which versions a buyer is entitled to run. A perpetual license typically conveys the right to the version owned at purchase, while access to newer versions depends on active support, and a subscription may convey rights to versions released during the term. A finding that charges for a version the buyer is not entitled to, or denies one it is, is often making a term error in disguise, which is why the term model and the version entitlement are read together, as set out in version entitlement under Micro Focus ALAs.

Fixing the term question forward

Once the present finding is corrected, the forward agreement should state the term model for each product plainly, so a future review cannot reopen the count by confusing perpetual ownership with subscription expiry. A clean forward arrangement records which entitlements are perpetual and which are term based, separates the license right from the support obligation, and removes the ambiguity that let the audit charge for owned software. Resolving the finding and fixing the term model forward are two halves of the same work. If a finding has charged you to re acquire software you already own perpetually, or counted a subscription beyond its term, open a case and we will hold the count to the right the authorization granted.

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.