---
title: "Licences at offboarding: seats of people who left"
description: "How to find paid seats still held by people who have left by joining each seat list with the directory, and how to close the gap in the offboarding process."
url: https://www.cureman.de/en/articles/offboarding-licences
language: en
updated: 2026-11-16
alternate_de: https://www.cureman.de/de/artikel/lizenzen-beim-offboarding.md
---

# Licences at offboarding: seats of people who left

> A seat held by someone who has left is found by joining each application's seat list with the directory on the email address. Every billable seat whose holder the directory marks as having left is unused, whatever the activity data says, and it still gives access. Before removing it, hand over what the account owns. The seat then goes to a joiner, or the paid count is reduced at the next invoice or renewal. A monthly join catches what the offboarding checklist missed.

A seat of someone who has left is the one licence finding that needs no threshold and no question. The directory says the person is gone, the application's seat list says they still hold a seat, and the join between the two lists is the finding. This article is about running that join and about why the seat was still there.

## Why seats outlive the people who held them

Offboarding usually ends with the account in the directory being disabled. That stops the sign-in. It does not free the licence.

| What happened at offboarding | What it leaves behind |
| --- | --- |
| Account disabled in the directory, application connected by single sign-on | The person cannot sign in. The seat stays assigned and billed |
| Application not connected to single sign-on | The person can still sign in with the application's own password |
| Seat assigned through a group nobody cleaned up | The seat is reassigned on the next sync |
| Account kept so that its data is not lost | A paid seat used as an archive |
| Contractor or temporary worker never in the HR system | Nobody triggers the offboarding at all |

Only a removal in the application itself, or automated provisioning that reaches it, ends the seat.

## The join

You need two lists and one key.

| List | Columns needed |
| --- | --- |
| Directory or HR system | Email address, employment status, leaving date, manager |
| Seat list of each application | Email address, licence type, whether the seat is billable, last activity |

Join on the email address in lower case. Each seat lands in one of four groups.

| Result of the join | Meaning | Action |
| --- | --- | --- |
| Holder found, employed | Normal | None here |
| Holder found, marked as having left | A leaver's seat | Remove after handover |
| Holder found, marked inactive or on long leave | Depends on policy | Decide per case |
| Holder not found in the directory | External, service account, alias or an old domain | Sort by hand |

The fourth group takes the most time on the first run and little afterwards, once service accounts and externals are labelled as such.

## Step by step

1. **Pull the directory** with status and leaving date. Include people who left in the last twelve months, not only current staff.
2. **Pull the seat list** of each paid application, with the flag that says whether a seat is billable. Deactivated users are free in some applications and billed in others.
3. **Join and count** per application: seats held by leavers, times price per seat.
4. **Sort the unmatched seats** into externals, service accounts and errors. Give each service account an owner.
5. **Hand over before removing.** Transfer files, dashboards, automations and API tokens that belong to the account. Ask the leaver's former manager who takes them.
6. **Remove or deprovision the user** in the application and record who did it and when.
7. **Use the freed seat**: give it to a joiner, or reduce the paid count.

## What it saves, and when

Yearly cost of leavers' seats = seats × price per seat per month × 12.

A worked example with invented figures: 4 seats of people who left, at 25.00 a month. 4 × 25.00 × 12 = 1,200.00 a year.

When the money stops depends on the contract. With monthly billing the reduction applies from the next invoice. On a committed term it usually applies at renewal, unless the vendor agrees to an earlier change, so the list belongs in the renewal preparation described in [preparing a SaaS renewal](https://www.cureman.de/en/articles/prepare-saas-renewal). Until then a freed seat still has a use: the next joiner gets it and no new seat is bought.

## The access matters more than the money

A leaver's seat is first of all an open door. Where the application is not behind single sign-on, the former employee can still sign in. Where it is, tokens, sessions on mobile devices and shared links may outlive the directory account. Treat these seats as a security finding with a short deadline, not as a cost item for the next quarter.

## Closing the gap in the process

- **One offboarding checklist per person**, generated from the seat lists, not from memory: every application in which this person holds a seat.
- **An owner per application** who removes the user and confirms it.
- **Automated provisioning** where the application and the plan support it, so that removal in the directory removes the seat.
- **Group-based assignment** reviewed with the groups: removing someone from the group has to remove the licence.
- **Contractors in the directory** with an end date, so that their leaving is an event at all.
- **A monthly join** as described above. It finds what the checklist missed, and it is the measure of whether the process works: the number should be near zero.

The same join belongs in the regular rhythm described in [SaaS licence management basics](https://www.cureman.de/en/articles/saas-licence-management-basics).

## What goes wrong

- **Disabled is taken for removed.** The directory shows the account as disabled, and the application bills the seat regardless.
- **The account is deleted with its data.** Dashboards and automations disappear, and the team notices a week later.
- **The seat is kept as an archive.** If the data is needed, export it or transfer it. A full licence is an expensive way to store a mailbox.
- **Leavers' seats are mixed with inactive seats.** A leaver's seat needs no question to the holder. An inactive seat does, as described in [how to find unused software licences](https://www.cureman.de/en/articles/find-unused-software-licences).
- **Service accounts are removed in the clean-up.** An integration stops the same afternoon.

## How Cureman does it

Cureman reads the directory through the connector to the identity provider, with each person's status and manager, and the seat lists through the connectors to the applications. All connectors only read. Every billable seat whose holder the directory marks as having left or as inactive is listed per application with the affected accounts and the calculation: seats, times price per seat, times twelve, with a note on whether the reduction applies from the next invoice or at renewal. The finding is filed as a security finding with high confidence, and these seats are kept out of the inactive-seat and tier findings, so that no seat is counted twice. Removing the seat is a step of the finding's action plan: done by hand in the vendor's console, or through the vendor's API where the organisation has allowed that and a person has approved the step in full. See the page about [licence optimisation](https://www.cureman.de/en/modules/licence-optimisation).

## Questions and answers

### Why do former employees still hold software licences?

Because disabling the account in the directory blocks the sign-in and leaves the seat assigned in the application. The licence is freed only when the user is removed or deprovisioned in the application itself, by hand or through automated provisioning. Applications that are not connected to single sign-on are missed altogether.

### How do you find seats of people who have left?

Export the directory with each person's employment status, export the seat list of each application, and join the two on the email address. Every billable seat whose holder is marked as having left is a finding. Seats that match nobody in the directory are a second list to sort by hand into externals, service accounts and aliases.

### Does removing a leaver's seat save money straight away?

It does with monthly billing, from the next invoice. On a committed term the paid seat count usually falls only at renewal, but the freed seat can be given to the next joiner instead of buying a new one. The access is closed at once in both cases, which is reason enough to remove the seat.

### What has to happen before a leaver's account is deleted?

Hand over what the account owns, such as files, dashboards, automations, shared links and API tokens, to a named person. Many applications delete or orphan this content with the user. Check as well whether the account is a shared or service account that happens to carry a person's name.

### How are people on long leave treated?

As a decision of their own, set by policy. A person on parental leave or a sabbatical is still employed, and their seat is not a leaver's seat. Some organisations suspend such seats and restore them on return, where the application keeps the data of a suspended user.

## The module that does this

[Licence optimisation: seats, plans and renewals](https://www.cureman.de/en/modules/licence-optimisation): The licence optimisation module reads seats, plans and activity from vendor APIs, finds unused seats and oversized plans, and asks seat holders after approval.

## Read next

- [How to find unused software licences](https://www.cureman.de/en/articles/find-unused-software-licences): A step-by-step method to find unused software licences from the vendor's own data, ask the seat holders, and remove seats before the renewal date.
- [SaaS licence management: what to track and when](https://www.cureman.de/en/articles/saas-licence-management-basics): What SaaS licence management is, which records to keep for every application (seats, plans, renewals, owners) and the yearly rhythm that keeps them true.
- [Preparing a SaaS renewal](https://www.cureman.de/en/articles/prepare-saas-renewal): How to prepare a SaaS renewal. Work out the notice date, the seats you need and the plan mix, and decide what to ask the vendor for before the deadline.
