Support Reinstatement Fees

Reinstating lapsed software support typically costs the back-maintenance you skipped plus a reinstatement penalty of 20 to 50 percent of that amount, so a one-year lapse on a $1,000,000 support contract commonly costs $1,200,000 to $1,500,000 to restore. The fee exists to make dropping support and re-entering it more expensive than simply paying every year, and most major vendors enforce it in near-identical language. This guide explains how reinstatement fees are calculated, which vendors charge them, when a deliberate lapse still makes financial sense, and how to negotiate the penalty down before you sign anything.

Reinstatement fees sit at the center of every support-reduction decision, which is why they belong in our software contract negotiation guide and in any serious evaluation of third-party support. Understand the math before you let a renewal lapse, not after.

What a reinstatement fee is

A reinstatement fee is the charge a vendor levies to restore software maintenance after the customer has allowed it to expire. It is not the same as a renewal. A renewal continues an unbroken support stream at the contracted rate. A reinstatement restarts a support stream that the vendor considers terminated, and it carries two components: the maintenance fees for the period the contract was lapsed, billed retroactively, and a penalty on top of those fees. The combined charge is the price of re-entry.

The economic purpose is straightforward. Vendors price perpetual-license support at 18 to 25 percent of license value per year because that recurring stream is more profitable than the original license sale. If customers could drop support during quiet years and rejoin only when they needed a patch or an upgrade, the recurring model would collapse. The reinstatement penalty removes that option by making intermittent support more expensive than continuous support.

How vendors calculate the fee

Most reinstatement formulas have the same two parts. First, the vendor charges the support fees for every year the contract was lapsed, as if you had never stopped paying, frequently uplifted by the annual increases you would have absorbed. Second, the vendor adds a reinstatement penalty, usually expressed as a percentage of those back-fees. The penalty most often falls between 20 and 50 percent, though some contracts push higher.

The hidden third cost is forward repricing. When you reinstate, the vendor often resets your support base to current list pricing and strips the legacy discount your original deal carried, so the post-reinstatement annual fee can exceed what you paid before the lapse. Model the new run rate, not just the one-time re-entry charge, the same way you would model any list price versus net price gap.

Reinstatement policy by vendor

The major enterprise vendors publish or enforce reinstatement terms that differ in detail but agree on intent. The figures below are advisory estimates drawn from negotiated outcomes and should be confirmed against your specific contract language.

Oracle is the canonical example of the punitive end. Its policies pair a 50 percent reinstatement fee with a matching-service-levels rule that prevents selectively dropping support on part of a license set to shrink the bill, a structure covered in detail in our Oracle third-party support analysis. Broadcom sits at the other structural extreme: because VMware is now subscription-only, there is no maintenance to reinstate, only a fresh purchase at current per-core pricing with the minimum-core rules reapplied.

When a deliberate lapse still pays

A planned lapse can be rational, but only when the reinstatement math is part of the decision from day one. The case is strongest for stable, end-of-life products you do not intend to patch or upgrade and may retire entirely. If you will never reinstate, there is no penalty to weigh, only the savings from stopping payment. The case is weakest for actively developed products where you will need the next release, because reinstatement is then a near-certainty and its penalty erases the interim savings.

The break-even is simple to express. If annual support is S, the reinstatement penalty is P percent, and you lapse for N years, you save N times S during the lapse but pay back roughly N times S plus P percent on re-entry. You come out ahead only if you never reinstate, or if the interim savings can be invested into a migration that removes the product before any reinstatement is needed. This is why a lapse decision and a third-party support evaluation usually travel together.

Third-party support as the alternative

Third-party support providers such as Rimini Street, Spinnaker Support, and Support Revolution offer maintenance for stable enterprise products at roughly half the vendor fee, with no reinstatement penalty of their own. The trade is that you forfeit vendor patches, version upgrades, and the right to buy new licenses on the same product line in many cases. For a frozen estate that will not change for several years, third-party support captures most of the savings of a lapse without the re-entry risk, because the provider keeps you supported the whole time.

The decision is rarely permanent. Many buyers use third-party support as a bridge while they migrate off the product, then drop support entirely once the migration completes. The reinstatement question only returns if you plan to come back to the vendor, which is why the exit plan and the support plan should be designed as one. Pair this analysis with a disciplined renewal calendar so no decision is made under deadline pressure.

How to avoid an accidental lapse

Most reinstatement fees are paid by accident, not by strategy. A renewal notice goes to a mailbox no one monitors, a purchase order stalls in approval, or a contract auto-terminates because the renewal was not countersigned in time. The fix is operational: every support contract belongs on a tracked renewal calendar with an owner, a notice date, and an escalation path that fires well before expiry.

The same calendar discipline that prevents accidental lapses also strengthens deliberate negotiation. A renewal worked months ahead, with the reinstatement clause read and the alternatives priced, negotiates from strength. A renewal handled in the final week, with support about to lapse, negotiates from weakness, and that is precisely when vendors hold firm on price. Treat reinstatement terms as something you read at signing, not something you discover at renewal, the same discipline that defeats a routine price increase.

Read the reinstatement clause at signing

The cheapest reinstatement negotiation happens years before any lapse, in the original contract. Most buyers never read the reinstatement language until they need it, by which point the terms are fixed and the bargaining power is gone. Insist on reading and amending the clause at signing, when the vendor wants the deal and will concede terms that cost it nothing today. The three terms worth fighting for are a cap on the reinstatement penalty, a defined grace period before a lapse is treated as termination, and protection of the original discount on reinstatement.

A penalty cap converts an open-ended risk into a known number. Vendors often resist a hard cap but will accept a ceiling expressed as a percentage of one year's support, which is far better than an uncapped formula that compounds with every year of lapse. A grace period, typically 30 to 90 days, prevents an administrative delay from triggering the full penalty, and it is the single most valuable protection against accidental lapses. Discount protection ensures that if you do reinstate, your forward rate returns to the contracted discount rather than resetting to current list, which is where the largest hidden cost usually sits.

Tie these terms to the audit clause as well. A vendor that can both penalize a lapse and trigger an audit holds two forms of pressure at once, so the contract should keep the two separate and bound. Our audit defense team reviews reinstatement and audit language together, because the same clause that governs re-entry often interacts with the compliance terms. Pair the review with the protections in our price protection clauses guide so the forward rate is defended along with the penalty.

If you are already past signing and facing a lapse, the negotiation shifts to the vendor's retention incentive. Document why reinstatement is in the vendor's interest, the continued relationship, the forward commitment, and the avoided churn, then present the waiver as a mutual outcome rather than a concession. Vendors waive or reduce reinstatement penalties far more often than their published policy suggests, especially when the request arrives near a quarter close with a forward order attached.

Common questions

Can a reinstatement fee be negotiated away?

Often, yes, especially when the lapse was administrative rather than a deliberate exit. Vendors will waive or reduce the penalty to retain the account, particularly near quarter-end and when you commit to a forward renewal. Escalate above the renewals desk and document the cause of the lapse.

Does third-party support trigger a reinstatement fee?

Not from the third-party provider. The reinstatement fee only arises if you later return to the original vendor for support. If you migrate off the product before reinstating, the fee never applies.

Is back-maintenance always charged in full?

Most vendor formulas charge the full lapsed-period fees plus a penalty, and many also reprice the forward support base to current list. Always model the new annual run rate, not just the one-time re-entry charge, because the lost legacy discount can outlast the penalty.

How long can support lapse before reinstatement is refused?

It varies by vendor and product. Some allow reinstatement at any time for a fee; others refuse once a product reaches end of support or once entitlements are purged. Confirm the specific limit in your contract before you let anything lapse.