How to Build a Software Licence Inventory Before Your Next Renewal

A software licence inventory — sometimes called a licence position or effective licence position (ELP) — is a structured record of what software you are licensed to use, what you have actually deployed, and what the gap between the two means for your commercial and compliance position. It is the single most important document you can produce before entering any major renewal negotiation.

Without it, you are negotiating blind. The vendor knows exactly what you have. They have telemetry, renewal history, support case data, and in many cases, direct knowledge of your deployment footprint. Walking into an Oracle or SAP renewal without your own licence position is the equivalent of negotiating a house purchase without knowing the property's value.

This guide walks through the practical steps to build a reliable software licence inventory for your top-spend vendors in 4-8 weeks — fast enough to be useful before a renewal, thorough enough to support an effective negotiation.

What a Complete Licence Inventory Contains

A licence inventory is not a list of what software you've purchased. It is a structured reconciliation between three distinct datasets: your contractual entitlements, your deployment reality, and your actual usage. For each product in scope, you need to know:

• Entitlements: What you are licensed to use under current agreements — product names, editions, quantity, licence metric (named user, processor, per-device, per-seat), and any usage rights or restrictions.
• Deployments: What you have actually installed, activated, or configured across your environment — including virtual machines, cloud instances, containers, and third-party systems that call licensed software.
• Usage: How many people are actually using the software actively, with what frequency, and under which access methods.
• Gap analysis: The delta between entitlements and deployments — your over-licence position (waste) and your under-licence position (compliance risk).

The gap analysis is what drives both commercial and risk decisions. Over-licenced products represent money you can reclaim at renewal. Under-licenced products represent audit exposure that must be remediated before or during negotiation — you cannot negotiate a reduction if the vendor can immediately offset it with a compliance claim.

Step-by-Step: Building Your Licence Inventory

1. Identify your tier-1 vendor scope Start with the vendors that represent your top 80% of software spend. For most large enterprises, this is 4-8 vendors — typically Oracle, Microsoft, SAP, Salesforce, Workday, ServiceNow, and one or two cloud providers. A comprehensive licence inventory covering all software in your estate is a multi-year project. A focused inventory covering your renewal-critical vendors can be completed in weeks.
2. Retrieve all current contracts and order forms Gather every agreement, order form, amendment, and licence schedule for each vendor. This is harder than it sounds — many enterprises have agreements spread across legal, procurement, finance, and IT, with amendments that modified original terms in ways no one has tracked. Your entitlements come from contracts, not from vendor portals, which may not accurately reflect your purchased rights.
3. Run discovery tooling against your estate Use your SAM tool (Flexera One, Snow, ServiceNow SAM, or similar) to run a full discovery sweep. For Oracle, this means running the Oracle LMS Collection Scripts across all servers, VMs, and cloud instances. For Microsoft, pull data from Microsoft 365 Admin Centre, Intune, and Azure portal. For SAP, run USMM (User Measurement) and SLAW (System Landscape Analysis). The discovery output tells you what is installed and where.
4. Map deployments to licence metrics This is the most technically demanding step and the one most teams get wrong. Each vendor uses different licence metrics — Oracle counts processor cores with vendor-specific core factors; SAP counts named users across multiple user type categories; Microsoft counts assigned seats and active users; IBM counts PVU values. You need to map your discovered deployment data to the specific metric used in your contract.
5. Build the gap analysis spreadsheet For each product and licence metric: entitlements purchased vs deployments measured vs active users. Flag any products where deployments exceed entitlements (red: audit risk). Flag products where entitlements significantly exceed active usage (amber: reduction opportunity). This spreadsheet becomes your negotiation foundation.
6. Remediate compliance gaps before negotiating This is counterintuitive but critical. If you have under-licensed positions, do not walk into a negotiation with unresolved compliance gaps. Vendors use audit threats as negotiating leverage. Resolving your gaps — either by bringing licences into compliance or by restructuring your deployment — before negotiation removes that leverage from the vendor's hands.
7. Validate with your adviser before approaching the vendor Your licence position should be reviewed by a specialist negotiation adviser before any conversation with the vendor. An adviser can identify errors in your gap analysis (particularly around Oracle core factor calculations or SAP indirect access), quantify your reduction opportunity in commercial terms, and identify the negotiation levers your position supports.

Vendor-Specific Licence Inventory Complexities

Oracle

Oracle licence inventory is the most technically complex of any major vendor. Key challenges include: the core factor calculation for processor-based licences (different hardware has different factors ranging from 0.25 to 1.0), the treatment of virtual environments (Oracle's policy does not fully recognise VMware partitioning for licensing purposes, which catches many enterprises by surprise), and the scope of Java SE licensing under the Employee Metric introduced in 2023.

For Oracle, always run the LMS Collection Scripts on every server that could conceivably host Oracle software — not just servers you believe are running Oracle products. Oracle's definition of "installed" includes software loaded on a server even if not running.

Microsoft

Microsoft licence inventory complexity has increased significantly with the transition to NCE (New Commerce Experience) and the proliferation of Microsoft 365 add-ons. The key challenge is distinguishing between purchased licences, assigned licences, and actively used licences — these are three different numbers, and the gap between them represents your reduction opportunity at renewal.

Pull Microsoft 365 usage data from the Microsoft Admin Centre (Reports section) and Azure AD sign-in logs. Licences assigned but not activated for 60+ days are candidates for removal. Products included in bundle SKUs but never activated represent scope you can negotiate out of your next agreement.

SAP

SAP licence inventory requires running USMM (transaction to measure users) and SLAW (System Landscape Analysis Workbench) across your SAP landscape. The primary challenge is accurately categorising users — SAP has multiple user types (Professional, Limited Professional, Employee, etc.) with very different licence costs, and incorrect categorisation in either direction creates problems: over-paying for users who should be classified at a lower tier, or under-paying and creating a true-up liability.

Salesforce

Salesforce licence inventory is relatively straightforward — licence utilisation data is available directly in the Salesforce Admin UI under Setup > Company Information and the Licence Management App (LMA). The key metrics are assigned users vs active users in the last 30/60/90 days and feature licence utilisation vs assigned. Salesforce's standard contracts include True-Up provisions that allow the vendor to charge for actual usage above contracted amounts — but do not typically allow refunds for under-usage without renegotiation.

The Five Most Common Licence Inventory Mistakes

• Relying on vendor-provided data: Vendor portals show what the vendor says you purchased. They may not reflect amendments, may include products that were subsequently renegotiated, and cannot tell you what you actually deployed. Always build your inventory from your contracts and your own discovery data.
• Missing virtual and cloud deployments: Software installed on AWS, Azure, or Google Cloud instances is still subject to licence obligations. Many enterprises have complete discovery of their on-premises estate but no visibility of cloud-deployed licensed software.
• Ignoring third-party maintenance implications: If you are using third-party maintenance for Oracle or SAP support, your licence position may be different from what your contracts state — particularly around which products are still supported and which require remediation before return to vendor support.
• Not capturing all amendments: Enterprise software agreements are frequently amended. A renewal-stage inventory built from original contracts without capturing all subsequent amendments will be wrong — sometimes significantly.
• Waiting too long: A licence inventory built 3 months before renewal is too late to rationalise your deployment posture, remediate compliance gaps, or run a competitive evaluation. Start 9-12 months before your renewal date.

Using Your Licence Inventory in Negotiation

A completed licence inventory enables several specific negotiation moves that are impossible without it:

• Scope reduction: You can credibly request removal of over-licensed products or unused capabilities, with data showing exactly how much usage you have (or don't have). Vendors cannot easily contest data drawn from your own estate.
• True-up manipulation: Understanding your exact usage relative to your contracted quantities allows you to time true-up discussions to your advantage and avoid year-end surprises that vendors use as leverage.
• Compliance leverage removal: By remediating gaps before negotiation, you eliminate the vendor's ability to use audit threats as a pressure tactic during commercial discussions.
• Consolidation arguments: Knowing what you over-use in one product and under-use in another enables you to propose consolidation deals that serve both your interests and the vendor's revenue goals — creating win-win outcomes that are harder to achieve from pure cost-cutting positions.

Key Takeaways