ALA term expiry and renewal exposure

A license with an end date carries a risk that a perpetual one does not: when the term lapses, the right to run the software may lapse with it, and software left running past the date can become the basis of a finding. An audit that times its measurement against an expired or unrenewed authorization can present continued use as unlicensed use, charging for a deployment the buyer believed it was entitled to run. ALA term expiry and renewal exposure is the question of how the term and renewal clauses of an Additional License Authorization create that risk, and how the defensible reading holds any finding to what the dates and the documents actually establish.

This field note explains how term and renewal clauses work, where a finding exploits a lapsed date, and how the records settle it. It pairs with our ALA and entitlement review track.

What term and renewal clauses do

A term grant licenses the software for a defined period, after which the right to use it ends unless the term is renewed, while a renewal clause sets out how and when that extension happens and on what terms. Whether a particular product carries a term or perpetual grant is a fact that lives in the authorization, not an assumption, and the difference decides whether continued use after a date is exposure at all. The distinction between the two models is examined in ALA perpetual versus subscription terms, and reading which model governs each product is the first step in assessing renewal exposure.

Where a finding exploits the date

The common overreach times the measurement to catch software running after a term has lapsed and presents that continued use as unlicensed. But the date alone does not settle the question, because a renewal may have occurred that the finding overlooked, the term may have been extended by amendment, or the grant the finding read as a term may in fact be perpetual. A finding that asserts expiry exposure without confirming each of those points is reaching past what the documents show. Confirming the true status of each authorization is the resolution work examined in stacked and superseded ALAs in a license estate, where renewals and amendments frequently change the picture a single document suggests.

Renewal, support, and the maintenance question

Term and renewal exposure is closely tied to support and maintenance, because a finding may treat a lapse in maintenance as if it were a lapse in the license itself, or may demand reinstatement of back maintenance as part of the remedy. Whether continued use requires current maintenance, and what a lapse in maintenance actually costs, depends on the support terms of the grant, not on the vendor's preferred reading. The relationship between maintenance status and entitlement is examined in ALA support and maintenance obligations, and it frequently determines whether a renewal lapse is exposure or merely a support gap.

The remedy if the lapse is real

Where a term genuinely lapsed and use continued, the exposure is real, but the remedy is still governed by the contract. On noncompliance, the licensee is deemed to have acquired licenses at then current list price, must pay back maintenance and support plus first year maintenance on the new licenses, and reimburses the audit costs the vendor incurs. Each of those components is contestable on its own terms, and the way the deemed acquisition remedy is constructed is examined in our broader audit mechanics work. Even a genuine lapse does not give the vendor a free hand on the number, because the remedy must follow what the contract specifies, not what the finding asserts.

How the renewal reading reduces the number

In a recent engagement, a finding timed its measurement to catch several products running after their stated term dates and presented the whole deployment as unlicensed. Reconstructing the renewal history showed that two of those products had been renewed through an amendment the finding had not accounted for, a third carried a perpetual grant the finding had misread as a term, and the maintenance lapse on the remainder was a support gap rather than a loss of license. Each of those findings removed a slice of the asserted figure. This is the ordinary mechanism: every authorization whose true term status differs from what the finding assumed corrects the count for that product. Applied across an estate, this reading is part of how we deliver the 68 percent average reduction we have achieved across more than 200 defended audits.

Evidence that settles the dates

Defending against expiry exposure rests on the documents that establish the true term and renewal status: the original authorizations, renewal records, amendments, and support entitlements, assembled into a clear timeline for each product. This record shows when each grant began, whether and when it was renewed, and what its current status is, against a finding that may have read a single document in isolation. What records carry this weight is the subject of what records support an ALA entitlement position, and for term exposure the timeline they build is what answers a finding timed against a lapsed date.

Fixing the renewal question forward

After the present finding is corrected, the forward arrangement should make term and renewal handling explicit, so a future review cannot reopen the count by timing its measurement against a date the buyer was managing in good faith. A clean forward agreement records renewal mechanics, the consequences of a lapse, and how maintenance status relates to the license, removing the ambiguity that let the audit exploit a date. If a finding has timed its measurement against a lapsed term, or treated a maintenance gap as a loss of license, open a case and we will hold the count to what the dates and the documents actually establish.

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.