Subscription and Support Reinstatement Fees
Dropping IBM Subscription and Support to save money, then needing it back, is one of the most expensive round trips in the catalog. Reinstatement is rarely a simple resume; it carries back charges and reopens the question of what you were running while uncovered. Lapsing support is easy; getting it back is not.
What Subscription and Support actually covers
Subscription and Support, often shortened to S and S, is the annual entitlement to new versions, fixes, and IBM support for a licensed product. It is renewed yearly against the licenses you hold. Letting it lapse stops your right to upgrades and support, but the underlying license to use the version you have generally remains. The trap is that buyers who lapse S and S often keep deploying, patching, or expanding the software, and some of that activity quietly depends on rights that only active support carries.
What reinstatement costs and why audits follow
When you come back, IBM does not simply restart the clock. Reinstatement typically requires paying for the lapsed period as well as resuming forward, so the saving from the gap is recovered and then some. More importantly, asking to reinstate or to support a product you let lapse is itself a recognized audit trigger. It signals to IBM that the estate changed while it was not watching, and the natural next step is to verify what was deployed during the uncovered window. A reinstatement request can therefore open a broader review rather than close a small gap.
- Back charges apply: reinstatement usually recovers the lapsed period, not just the forward renewal
- The license may persist: lapsing S and S stops upgrades and support, but typically leaves the existing version licensed
- Reinstatement is a trigger: asking to support a lapsed product invites IBM to check what ran while uncovered
- Timing matters: the longer the gap and the more the estate changed, the larger the exposure on return
What is negotiable, and how buyers approach it
Reinstatement terms are not fixed. The back charge, the reinstatement uplift, and whether the return is bundled into a broader renewal are all open to negotiation, especially when the buyer is committing to a larger forward relationship. We reconstruct exactly what was deployed during the lapse so the conversation is grounded in evidence rather than IBM's assumption, then position the reinstatement inside a forward deal where the commitment to renew offsets the back charge. Walking in with a clean record of the uncovered period is what keeps a reinstatement from turning into a full audit settlement.
A reinstatement request tells IBM the estate moved while support was off, and that invites scrutiny of the lapsed window. Before you ask to come back, reconstruct what was actually deployed during the gap so you can answer the question the request will provoke. Treat the back charge and reinstatement uplift as negotiable inside a forward agreement, and never reinstate piecemeal while the rest of the estate is undocumented.