Software License Management (2026): Find Unused Licenses, Reclaim Seats and Stop Paying for Leavers

TL;DR

• Software license management is the practice of tracking which software licenses a company owns, who holds each one, whether it is used, and when it renews, so you pay only for seats people need and stay within the contract terms.
• The common leaks are seats still assigned to people who have left, seats nobody logs into, and whole tools that auto-renew after a team quietly moved to something else.
• You find it by joining three records that rarely meet: the HRIS leaver list, software invoices and card spend, and app access or last-login data. Then you reclaim seats before each renewal's notice deadline.
• Sentra joins the HRIS and finance records with what people said in email, chat and meetings, such as "we moved off that tool in August", and raises the seat or renewal to its owner with the evidence before the notice date. A named person approves before anything goes out.

What software license management is

Software license management (SLM) is the process of tracking, controlling and documenting the software licenses a company pays for, so that usage matches what the contracts allow and the company stops paying for licenses it does not use. It covers the inventory of licenses, who each seat is assigned to, how often it is used, the contract terms and the renewal date.

SLM sits inside software asset management, which in turn sits inside IT asset management. ManageEngine and Freshworks both describe it this way. The international standard for the wider discipline is ISO/IEC 19770-1, which sets out requirements for an IT asset management system.

Software license management vs SaaS management

The two terms overlap, and buyers search for both. The difference is mostly about where the software runs and who buys it.

Most finance and IT leaders need both, because much new software arrives as SaaS that a team signed up for without IT. Our guide to shadow AI covers the same pattern for AI tools.

Where software license spend leaks

Unused software licenses are common, not an edge case. Zylo, a SaaS management vendor, reports in its 2026 SaaS Management Index that the average organization uses 54% of its SaaS licenses and wastes $19.8M a year on unused ones, ranging from $3.8M at companies with 1 to 500 employees to $80.6M at companies with more than 10,000. Those are Zylo's own figures from its customer data, so treat them as a direction, then measure your own.

The leaks fall into a small number of patterns.

• Leavers' seats. Someone leaves, IT disables single sign-on, and the paid seat stays assigned in the vendor's admin console. Disabling the login does not cancel the subscription.
• Inactive seats. A person still works at the company but has not opened the tool in months. Often they changed roles or the team changed process.
• Shelfware renewals. A whole tool is no longer used because the team moved to another product. Nobody tells procurement, and the contract auto-renews at full seat count.
• Duplicate tools. Two teams pay for two products that do the same job, often one through IT and one on a company card.
• Tier overbuy. Everyone is on the premium tier when most people use only the features in the basic one.
• True-up surprises. The opposite problem. More people use a tool than the contract allows, and the vendor bills the difference at audit or renewal.

The first three are the easiest to fix, because each one has a person who knows the answer. HR knows who left. The team lead knows the tool was dropped.

License types and what to count

What counts as "unused" depends on how the license is sold. ManageEngine lists the common models. The table shows what to count for each.

How to find unused software licenses

You can run this by hand in a spreadsheet for your 20 largest contracts.

1. List what you pay for. Pull 12 months of software invoices from accounts payable and software charges from card and expense data. Group them by vendor. The card data is where tools bought without IT appear.

2. Record the contract terms. For each vendor, note seat count, price per seat, billing cycle, renewal date, auto-renewal clause and notice period. The notice period matters more than the renewal date, because after it passes you usually cannot reduce seats until the next term.

3. Pull the assignment list. Export assigned users from each vendor's admin console, or from single sign-on where the app is connected to it.

4. Match against the HRIS. Compare assigned users with the HRIS list of current employees and with termination dates. Any seat held by someone with a termination date is a leaver's seat.

5. Check activity. Use last-login or last-activity dates. Flag seats with no activity in 90 days, and set the threshold per tool, since a quarterly reporting tool may be opened only once a quarter.

6. Ask the owner. For each tool, name a business owner and ask whether the team still uses it and plans to keep it. This step finds the shelfware renewals that data alone misses.

7. Decide per seat. Reclaim, reassign, downgrade or keep. Record the decision and who made it.

The license reclamation process

License reclamation is the step where you take back a paid seat from someone who does not need it and either reassign it or remove it at renewal. It needs a light process, because removing a seat can delete data or break a workflow.

1. Notify. Tell the seat holder and their manager that the seat will be removed on a set date unless they reply. Skip this step for leavers.

2. Preserve data. Before removing a leaver's seat, transfer ownership of files, dashboards and integrations they created. Many tools delete a user's content when the seat is removed.

3. Reclaim into a pool. Move the seat to an unassigned pool rather than cancelling it straight away. New hires take seats from the pool before anyone buys more.

4. Reduce at renewal. Before the notice deadline, set the renewal seat count to active users plus a small buffer for expected hires.

5. Record the evidence. Keep the list of seats removed, the reason and the approver. This answers the next audit question and the next "why can't I log in" ticket.

Leavers' seats should come back as part of offboarding, not as a quarterly cleanup. NIST SP 800-53 control PS-4 on personnel termination already asks organizations to revoke access within a defined period. Reclaiming the paid seat in the same step closes the cost leak as well. Our employee offboarding checklist puts seat reclamation under IT and finance on the after-exit list.

Renewal calendar template

Keep one row per contract. Review the sheet monthly, and act on any row whose notice deadline falls in the next 90 days.

Worked example: two renewals and a quiet migration

The figures are illustrative. A 400-person company has two contracts renewing on 1 December, each with a 60-day notice period, so the deadline to change either is 2 October.

The project tool has 120 named seats at $40 per user per month. HR's records show 14 seat holders left the company during the year. Their single sign-on accounts were disabled on their last day, but nobody removed the seats in the vendor's console. Another 31 seat holders still work at the company but have not logged in for 90 days. Reclaiming the 45 seats and renewing at 80, with a small buffer for hires, saves 40 seats, or 40 x $40 x 12 = $19,200 a year.

The design tool has 25 seats at $15 per user per month. In August, the brand lead wrote in a team chat that the team had moved its work to a different design product and would not need the old one. Nobody forwarded that message to procurement. Every seat in the old tool shows no activity since August, but the contract has an auto-renewal clause. Cancelling before 2 October saves 25 x $15 x 12 = $4,500 a year.

The usage data alone flags both tools. What makes the second decision safe is the chat message, because it shows the owner meant to stop, not that the team was on holiday. Without it, someone chases the brand lead for a reply in the last week before the deadline.

Common mistakes in software license management

• Tracking renewal dates instead of notice deadlines. By the renewal date it is usually too late to reduce seats.
• Treating a disabled login as a cancelled seat. Single sign-on stops access. It does not stop billing.
• Ignoring card spend. Tools bought on company cards never enter the contract register, so they never get reviewed.
• One inactivity threshold for every tool. A 30-day rule removes seats from people who use a tool every quarter.
• Removing seats before saving data. Some vendors delete a user's content with the seat.
• No business owner per tool. If nobody owns the tool, nobody can confirm it is no longer needed, and the renewal goes through.
• Annual cleanups. Waste builds every month between reviews. Tie leaver seat reclamation to offboarding and review renewals monthly against the notice calendar.

The last point is the same class of problem as maverick spending: purchases that happen outside the process cannot be checked against it.

How Sentra catches this automatically

Software license waste persists because the facts sit in different places. The HRIS knows who left. The ERP and accounts payable know what you pay and when it renews. The fact that a team stopped using a tool usually sits in a chat thread or a meeting, and the person who signs the renewal never sees it.

Sentra joins what the systems of record say with what people said. It reads the HRIS, ERP and finance data alongside email, chat, meetings and documents, and works out what is true now. When a brand lead writes that the team has moved off a tool, Sentra records when that became true. When the renewal for that tool approaches, Sentra checks the contract against that fact and against the HRIS leaver list, and raises the gap to the tool's owner with the evidence: the invoice, the renewal and notice dates, the leavers still holding seats and the message showing the team moved on.

A named person approves each finding before it reaches anyone else, so a cancellation request never goes to a vendor on Sentra's say alone. Every claim cites its source, and permissions follow the source, so HR records stay visible only to people who could already read them. Sentra replaces none of your systems. Your HRIS, ERP and procurement tools stay the record, and Sentra connects to them through 200+ integrations. It holds SOC 2 Type II and ISO 27001 certifications and runs in the cloud, in an isolated VPC or air-gapped on premises.

To see it find the leavers' seats and quiet migrations in your own renewals, book a demo.

How to start

• If you have no contract register, start with 12 months of invoices and card spend for the top 20 vendors and build the renewal calendar above. That alone shows the next 90 days of decisions.
• If you have a register but no usage data, add last-login exports for the five largest contracts and match them against the HRIS leaver list. Leavers' seats are the fastest saving, because nobody needs to be asked.
• If you already run a SaaS management tool, check whether it knows when a team decided to stop using a product. Usage data shows that a tool went quiet. It does not show why, or whether the owner agreed.

FAQ