ALA support and maintenance obligations

The license fee is rarely the largest part of a compliance finding. The larger part is what attaches to it. ALA support and maintenance obligations are the recurring fees a buyer agrees to pay alongside an Additional License Authorization, and they are also the mechanism by which a finding multiplies. When a shortfall is alleged, the vendor does not only price the missing licenses; it prices the support that would have been paid on them, reaching backward, and adds the first year of support going forward. Understanding how these obligations stack is essential to taking apart the number they produce.

This field note explains what the support and maintenance obligations cover, how they convert a license shortfall into a much larger demand, and how the defensible reading holds each layer to what the contract and the facts support. It pairs with our ALA and entitlement review track.

What the obligation actually covers

Support and maintenance is the recurring service a buyer pays for in exchange for updates, fixes, and vendor assistance. It is priced as a percentage of the license value and renewed on a defined cycle. The obligation is real and contractual, but it is bounded: it applies to the licenses actually held, at the value those licenses were priced at, for the periods the contract covers. A finding that treats the support obligation as open ended, or that attaches it to a license shortfall that does not survive scrutiny, has built the largest part of its number on a base that may not hold.

How the remedy stacks the number

On a finding of noncompliance, the remedy is not a single charge. The licensee is deemed to have acquired the missing licenses at the then current list price. On top of that sits back maintenance and support, as though the licenses had been carried and supported all along. On top of that sits the first year of maintenance on the newly deemed licenses. And the buyer also reimburses the costs the vendor incurred performing the audit. One alleged shortfall becomes four charges, and three of them are derived from the first. This stacking is the engine of the inflated finding, and we examine the full mechanic in how much can an ALA misinterpretation cost in an audit.

Why the base matters more than the multiplier

Because back support and forward maintenance are calculated from the license shortfall, the most effective place to reduce the total is the shortfall itself, not the percentages applied to it. A finding that overstates the license position by counting deployments the entitlement actually covers does not only overcharge for licenses; it inflates every derived charge by the same proportion. Correcting the underlying count, by holding it to the metric and the grant, brings down the back maintenance and the forward maintenance automatically, because there is less license value for them to attach to. This is why our defense always begins with the entitlement position rather than with the support arithmetic.

Back maintenance is not unbounded

A finding will often reach back as far as it can on the support charge, but the reach is not unlimited. The periods covered, the rate applied, and the value the rate is applied to are all matters the contract defines and the buyer can test. A support charge calculated on a license shortfall that has been corrected must be recalculated on the corrected base. A rate applied beyond the periods the contract supports can be challenged on the contract's own terms. Establishing the boundaries of the back maintenance claim is part of reading the obligation precisely rather than accepting the figure the finding presents, and it draws on the documentary discipline set out in documenting ALA entitlements for a rebuttal.

How we defend the support and maintenance figure

Our defense treats the support and maintenance charge as derived, not primary. We first reconstruct the license position and correct the underlying count, because every reduction there flows through to the back maintenance and the forward maintenance. We then test the support charge directly: the rate, the periods, and the base it is applied to, against what the authorization and the contract actually provide. Where the finding has priced support on a shortfall that does not hold, we strip the derived charges that the corrected base no longer supports. This is the Rebut and Resolve work of our method, and the same discipline of attacking the base before the multiplier is what moved our E-01 case file from a $7.2M finding to a $1.6M settlement, a 78 percent reduction, once the underlying count and everything priced on it were corrected together.

Audit cost recovery rides on the same base

There is a fourth charge that often travels with the support figure and deserves the same scrutiny. On a finding of noncompliance, the buyer also reimburses the costs the vendor incurred performing the audit. Like back maintenance and forward maintenance, this charge is presented as a fixed consequence, but it sits on the same contested base: it is justified by the existence of a shortfall, and where the shortfall is corrected, the premise for charging the buyer the full cost of the exercise weakens with it. We treat the cost recovery line the way we treat every derived charge, by testing whether it follows from a finding that holds rather than accepting it as an automatic add on. When the underlying position is corrected, the derived charges, support, maintenance, and cost recovery alike, are recalculated against what survives, not against the opening number.

Closing the support question forward

Once the present finding has been corrected, the forward agreement should state the support and maintenance terms plainly: the rate, the base, the renewal cycle, and what happens on a future true up. A clean forward arrangement removes the ambiguity that lets a future review stack derived charges on a contested base, and it converts the support obligation into a known, bounded cost rather than a lever the next audit can pull. Resolving the present finding and fixing the support terms forward are two halves of the same work. If a finding has priced years of back support on a license shortfall you do not accept, open a case and we will hold each layer to what the contract supports.

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.