Practical guide

Software License Inventory: What to Record for Every License, Field by Field

A software license list is only useful if someone can act on a row without asking around. This guide goes field by field through what to record for every software license, why each field earns its place, and what to leave out.

September 30, 2026 · 8 minute read

Why the fields matter more than the tool

A software license list is only useful if someone can act on a row without asking around. Most license trackers fail the same way: they record the product name and a date, and nothing that tells you who decides, what was bought, or where the terms live. When the renewal shows up, the team starts the research from scratch.

This guide goes field by field through what to record for every software license, why each field earns its place, and what to leave out. It is written for IT and ops teams at mid-size companies who need a working inventory, not a full asset-management program. The same fields work in a spreadsheet or a dedicated tool.

The short version: a minimum record

If you only have time for a first pass, capture these for every license:

Product and vendor
License or plan type
Quantity purchased and quantity in use
Renewal or expiration date, with the date meaning labeled
Cancel-by date if it auto-renews
Business owner and technical/admin owner
Reminder recipients
Annual cost and billing method
Link to the source document
Status and last verified date

The sections below explain each one and add optional fields for when you need more detail.

Identity fields: what is this?

Product name: The name people actually use, plus the formal product or plan name if it differs. Pick one naming convention and stick to it so duplicates are easy to spot
Vendor: The company you pay, which is not always the product brand (resellers and marketplaces count). This is who you contact at renewal
Edition or plan: The tier you are on. Renewals often hinge on whether you still need the higher tier
Category: A small, consistent set (for example: productivity, security, engineering, finance, design). Useful for spotting overlap during reviews
Internal record ID (optional): A stable reference that survives product renames and vendor acquisitions

Entitlement fields: what did we buy?

License or plan type: Per user, per device, concurrent, usage-based, site, subscription, or perpetual. This determines what "in use" means
Quantity purchased: Seats, devices, or units in the current term
Quantity in use: Assigned or active users from the admin console. Record when you last checked, because this number goes stale fast
Term length: Monthly, annual, or multi-year
Maintenance or support coverage (for perpetual licenses): Perpetual software often has a separate support or maintenance renewal with its own date
Restrictions worth knowing (optional): Legal entity, region, or environment limits if they affect who can use it

Date fields: when does something have to happen?

This is where most license lists break. One "date" column is not enough, and an unlabeled date is a guess.

Renewal or expiration date: When the current term ends, access stops, or the next charge lands. Label which one it is
Cancel-by date: For auto-renewing licenses, the last day notice counts. Write it down as its own field rather than working it out each time
Start date (optional): Helpful for multi-year terms and for confirming the vendor's dates match yours
End-of-support date (optional): For installed or perpetual software, the date the vendor stops shipping updates. It is a separate risk from renewal
Last verified date: When someone last confirmed the dates against the source. Stale dates look just as confident as fresh ones

For the full cancel-by checklist, see how to avoid surprise SaaS auto-renewals.

Ownership fields: who acts?

Business owner: The person who can say whether the tool is still worth paying for. A person, not a department
Technical or admin owner: The person who can add and remove users, change settings, and handle cancellation steps
Backup owner: Someone who can act if either owner is out or leaves
Reminder recipients: Who must hear about the upcoming date. Use real, monitored addresses; a reminder to a departed employee is the same as no reminder

If the business owner and admin owner are the same person, that is fine. Just make sure the name is there. For more on why ownership comes first, see how to track expiration and renewal dates without missing one.

Commercial fields: what does it cost and how is it paid?

Annual cost: Normalize monthly charges to a yearly figure so you can sort by spend
Billing method: Invoice, corporate card, or marketplace. Card-billed tools are the ones most often missing from inventories
Billing and renewal contact: The email the vendor sends renewal notices to. Check that someone actually reads it
Auto-renews (yes/no): Plus the notice period, if there is one
Notice method (optional): How cancellation must be sent, if the agreement specifies it
Cost center or budget owner (optional): Helpful when finance needs to approve or accrue

Evidence and status fields: how do we know, and where does it stand?

Source document link: Order form, agreement, or confirmation email. This is what you check when dates disagree
Status: Active, under review, renewing, cancelling, or cancelled. Keep cancelled rows as an archive rather than deleting them
Last decision: What was decided at the last renewal and why, in one line. It saves repeating the same debate next year
Notes: Only the context the next reviewer needs

What not to store in the inventory

Full license keys, passwords, or recovery codes: Keep those in a password manager or secrets vault and store only a reference to where they live
Every historical invoice: Link to where finance keeps them
Full contract text: Link to the document; the inventory is for dates, owners, and decisions
Fields nobody maintains: A column that is blank in most rows makes the whole list look unreliable. Drop it or make it someone's job

Checklist: build or clean up your license inventory

Export recent software spend from AP and card statements
Export app and admin lists from your identity provider or password manager
Merge into one list with one row per license agreement
Fill the minimum record for every row before adding optional fields
Label every date with its meaning (renewal, expiration, cancel-by, end of support)
Name a business owner and admin owner for every row
Replace any reminder recipient who has left or whose address bounces
Link the source document for anything above your review threshold
Set a last verified date and a plan to refresh it
Put unowned or undated rows at the top of the next review

Keeping it current

An inventory is a snapshot the day you finish it. Keep it useful with a light rhythm:

When you buy: Add the row the same day, with owner and dates
When someone leaves: Reassign their rows before their account is closed
Weekly: Scan what is due in the next 30 days and confirm each owner knows
Quarterly: Refresh quantities in use, spot-check dates against source documents, and run the software renewal review checklist for anything coming up

FAQ

Should we track SaaS subscriptions and installed software in the same inventory?

Yes, if the same team handles renewals for both. The fields are nearly identical. Installed or perpetual software just adds maintenance coverage and end-of-support dates.

How detailed should seat counts be?

Detailed enough to support a renewal decision. Purchased versus in use, with a last checked date, is usually enough for mid-size teams. Per-user assignment history belongs in the admin console.

Is a spreadsheet good enough for a license inventory?

For a small, stable list with clear owners, often yes. When rows drift, dates disagree with vendor portals, or reminders depend on one person, see how to move renewal tracking out of spreadsheets.

Who should maintain the inventory?

IT or ops usually keeps the list itself. Each row still needs a business owner who decides whether to renew, and finance should be able to see it.

Can the same fields work for non-software renewals?

Mostly. Insurance, certificates, permits, and domains all need a labeled date, an owner, recipients, and a source link. The entitlement fields are what make software different.