- Disabling the SSO account blocks sign-in; it does not release the paid seat in the vendor’s console.
- Offboarding is the right reclamation moment: information is fresh and someone is already in the systems.
- Reassign before buying (a reassignment is free), transfer owned assets before releasing, and log every released seat against the contract.
- Detection should be automated; the release click, especially for bundles, should stay human.
License reclamation is the step where a departing employee’s software seats are actually released or reassigned, not just their account disabled. It’s the step most offboarding processes skip, because disabling the identity provider account feels like the finish line.
It isn’t. Every departure without reclamation leaves a small trail of paid seats attached to a person who no longer exists in your directory, and the trail compounds with turnover. This guide covers why offboarding is the right moment to reclaim, what a reclamation checklist looks like, and where the process genuinely gets complicated.
Why doesn’t disabling the account free the license?
Even where automated deprovisioning (SCIM) removes the user from the application, the paid seat frequently returns to an unassigned pool that nobody checks before the next purchase, which is how companies buy seat number 201 while owning twelve idle ones. Buyers describe the manual version constantly: license tracking in a spreadsheet, seats deactivated when somebody happens to notice, and a standing suspicion that the vendor invoice and reality diverged quarters ago. In License Logic’s interviews with 80 mid-market executives, 50% reported wasting 20% or more of license spend on unused seats, and departure-orphaned seats are one of the steadiest contributors.
Why is offboarding the right moment to reclaim?
Because it’s the one moment when the information is fresh and someone is already in the systems. At offboarding, IT knows exactly who is leaving, has admin consoles open anyway, and the manager still remembers what tools the person used. Eleven months later at renewal, none of that is true; reclamation becomes archaeology. Reclaiming at offboarding also changes what renewal negotiations look like: if seats are released continuously, the count you renew is close to the count you need. Half the executives in our interviews reported surprise renewals, and a renewal that arrives as a surprise is guaranteed to be renewed at the stale seat count.
What does a license reclamation checklist look like?
Add these steps to the offboarding checklist you already run, in this order:
Disable the identity provider account
You already do this. It secures access; it does not save money yet.
Pull the departing user’s app footprint
Which applications did this person appear in? Sign-in analytics answer this in one view; without them, the manager’s memory plus your top-ten-by-spend vendor list is a workable approximation.
For each app: reassign or release
If a replacement is starting, reassign the seat directly (a reassignment is free; a new seat is not). Otherwise release it in the vendor console, and note whether the vendor actually reduces billing mid-term or just pools it for the next true-up.
Transfer owned assets before releasing
Documents, dashboards, API keys, and scheduled reports owned by the account. Release the seat only after ownership moves, or you’ll be paying for a re-activation later.
Log the released seats against the contract
This is the step that converts operations into money: a running tally of released seats per vendor is the evidence you bring to the renewal to cut the committed count.
Where does reclamation get genuinely complicated?
- Bundled suites. A seat in a bundle may cover mail, storage, and a dozen services at once. Releasing it can affect data retention and shared resources, so bundles deserve a deliberate policy, not an automatic release. Treat single-SKU tools as the fast path and bundles as the careful path.
- Usage-based and floating licenses. Nothing to release per-user, but departures still matter: committed usage tiers deserve a look at renewal if headcount dropped.
- Contracts with seat minimums. Some agreements bill a committed floor regardless of assignment. Reclamation still helps, but the real fix happens at renewal, which is a contract-terms question, not a console question.
- Nobody owns step 5. The console work happens in IT; the renewal negotiation happens in finance. If the released-seat tally never crosses that boundary, the savings never materialize on an invoice.
What should tooling do, and what should stay human?
Tooling is best at detection and evidence; people should own the release decisions. A license management platform should show you inactive users across your identity providers (people who haven’t signed in for 90 days, including those who left), the applications each employee actually used, and the contract terms and per-seat costs those seats map to, so every departure has a priced checklist. That’s the visibility layer License Logic provides through SaaS license management: read-only sign-in analytics from Entra, Okta, and Google Workspace, inactive-user detection, and the contract repository holding the seat counts the reclamation tally feeds into.
For the purchasing-side twin of this problem, see our guide to the hidden cost of unassigned licenses.
License Logic surfaces inactive and departed users across Entra, Okta, and Google, maps each to the applications they used and the per-seat cost, and holds the contract the released-seat tally feeds into, so reclamation becomes a renewal-ready number instead of an afterthought.
Frequently asked questions
Doesn’t SCIM deprovisioning handle license reclamation automatically?
SCIM removes the user from the application, which is a security win, but the paid seat typically returns to an unassigned pool or stays counted in your committed total. Reclamation means the seat count you pay for changes, and that usually takes a deliberate step in the vendor console plus a note for the renewal negotiation.
Should we release a departing employee’s seat immediately?
Reassign immediately if a replacement is coming; a reassignment costs nothing while a fresh seat purchase does. Before releasing outright, transfer owned assets (documents, dashboards, API keys, scheduled reports), then release. For bundled suites, follow a written policy because releasing can affect data retention.
Do vendors refund unused seats mid-contract?
Rarely. Most SaaS agreements bill the committed count regardless of assignment, so mid-term releases usually stop future growth rather than shrink the current invoice. The invoice shrinks at renewal, which is why logging released seats per vendor matters: it’s the evidence for cutting the committed count.
How do we find licenses from employees who left months ago?
Compare your identity provider’s inactive and departed users against each vendor console’s assignment list. Inactive-user detection across Entra, Okta, or Google Workspace surfaces accounts with no recent sign-ins, including the departed; from there it’s a per-vendor cleanup pass, prioritized by seat cost.
Who should own the reclamation process?
IT owns the console work as part of the offboarding checklist; finance or procurement owns bringing the released-seat tally into renewal negotiations. Most reclamation programs fail in the handoff between those two, so make the tally a shared artifact both teams see.