Back maintenance and first year maintenance on a finding.

The headline number in an OpenText finding is rarely the whole bill. Underneath the license shortfall sit two further layers that often equal or exceed it: back maintenance owed on the licenses you are deemed to have needed all along, and first year maintenance on the new licenses you are now required to buy. Understanding how these layers stack is the difference between negotiating the real exposure and negotiating only its surface.

When an OpenText or Micro Focus audit concludes that you are noncompliant, the remedy is not a single line item. The contract treats the shortfall as a set of licenses you should have acquired at the time of use, and it prices the consequences of that fiction accordingly. The result is a composite number, and each component is calculated differently, which means each component can be reduced differently. A defense that only argues the license count leaves the maintenance layers untouched, and those layers are where a large share of the money lives.

The three layers of a finding

A typical OpenText finding is built from three stacked components. The first is the license shortfall: the additional licenses the vendor says you needed, priced at then current list price under the deemed acquisition mechanism. The second is back maintenance and support: the support fees the vendor argues you would have paid on those licenses across the period of unlicensed use. The third is first year maintenance on the newly required licenses, added because the new purchase carries support like any other. On top of these sits reimbursement of the vendor's audit costs.

The mechanism that turns unlicensed use into a list price purchase is the foundation everything else rests on, and it is worth reading in full in the deemed acquisition at list price clause explained. The audit cost component, which is genuinely separate from these maintenance layers, is covered in who pays for an OpenText audit and how cost recovery works.

What back maintenance actually claims

Back maintenance is the vendor's argument that, had you licensed correctly from the start, you would have been paying annual support on those licenses for the whole period. The claim therefore reaches backward across multiple years and applies a support rate to the deemed license value for each of them. Because support is charged as a recurring percentage of license value, a multi year lookback can add a sum comparable to the license shortfall itself, and sometimes larger.

Several elements of a back maintenance claim are contestable rather than fixed. The period matters: the vendor will often reach back as far as the evidence allows, but the actual duration of the overuse is a question of fact, not assertion, and a shorter substantiated period reduces the claim proportionally. The rate matters: the support percentage applied should reflect what was contractually applicable, not the highest available figure. And the base matters most of all, because back maintenance is calculated on the license shortfall, so any reduction in that shortfall flows straight through to the maintenance layer.

First year maintenance on the new licenses

First year maintenance is more straightforward in concept but no smaller in effect. When the finding requires you to acquire new licenses, the vendor adds the first annual support charge on those licenses to the settlement, just as it would on any new purchase. This is standard commercial practice, but in a finding it compounds the deemed acquisition: you are paying list price for licenses you are forced to buy, and then paying support on top of that forced purchase.

The defense against first year maintenance is therefore inseparable from the defense against the license count. Every seat, core, or unit removed from the shortfall removes both its list price and the support that would have ridden on it. This is one more reason the entire defense begins with an independent reconstruction of what you actually owe, built before the vendor's measurement defines the base, as set out in building an effective license position before the vendor script runs.

Why the layers multiply

The structural insight is that the three layers are not independent. The license shortfall is the base, and both maintenance layers are calculated from it. A finding that begins with an inflated seat count does not just overstate the license line; it overstates back maintenance and first year maintenance in the same proportion, because both are percentages of the same inflated base. This is why a finding can feel disproportionate to the underlying overuse. A modest exaggeration of the count is multiplied through every layer above it.

That multiplication is also the opportunity. Removing dormant accounts, service accounts, non production environments, and decommissioned systems from the count does not merely subtract a license line. It deflates the entire stack. In a recent insurance engagement involving a Documentum seat count, the finding fell from $7.2M to $1.6M settled, a 78 percent reduction, precisely because correcting the consumer count collapsed the layers built on top of it rather than negotiating each in isolation. The way that consumer count was contested is the work of the ECM and Documentum audit defense track.

Attack the base before the layers

The sequence matters. Negotiating maintenance percentages or lookback periods first, while accepting the license count, concedes the most valuable ground. The disciplined order is to fix the base, then address the periods and rates that sit on it. First, reconstruct the true effective license position and strip the count down to genuinely licensable use. Second, challenge the back maintenance period against the actual facts of when overuse began. Third, confirm that the support rates applied are the contractually correct ones rather than the vendor's preferred figures. Only then does the residual settlement reflect real exposure rather than stacked assumptions.

This is also where conversion forward becomes powerful. Rather than paying the full stacked remedy, a finding can often be resolved by converting into a clean enterprise agreement that prices the go forward estate on defined terms and absorbs the historical exposure into a negotiated settlement. How that conversion is structured on the buyer's terms is the subject of true up negotiation tactics under audit pressure and our OpenPass enterprise agreement negotiation track.

The number you negotiate is the number you build

Back maintenance and first year maintenance make a finding larger than the license shortfall suggests, but they also make it more responsive to a disciplined defense, because they amplify every correction you win at the base. The lesson is to treat the finding as a structure to be dismantled from the bottom up rather than a single figure to be haggled down. For the full method across every OpenText and Micro Focus product line, see the complete OpenText audit defense playbook. If a finding has landed and the maintenance layers are inflating the total, open a case and we will rebuild the base before we negotiate the bill.