An Effective Licence Position is the reconciliation of what you have deployed against what you are entitled to use. It is easy to describe and genuinely hard to build. Here is what goes into one, and why an annual snapshot is no longer good enough.
If you are new to Software Asset Management you have probably heard of an Effective Licence Position without being told what one actually is. This is the short version.
An Effective Licence Position — usually just “ELP” — is one of the foundations of SAM. As the name implies, it is the current effective status of your licence consumption against your entitlement for a given publisher: Microsoft, Adobe, IBM, Oracle, SAP, and every other vendor you buy from. It shows you two kinds of exposure at once. Compliance failure, where you are consuming more software than you hold licences for. And overspend, where your usage is well below what you have already paid for.
To be genuinely effective — as opposed to an Ineffective Licence Position — it has to be built on a careful reconciliation between two data sets: what is deployed, and what you are entitled to use.
That sounds simple. It is not. Both data sets are larger and messier than people expect, and both have to be collected, processed and presented in a form you can actually work with.
To understand your consumption of a particular publisher’s software, you need three things.
Only when you have all three, from across the whole network, can you reconcile against the second data set.
Entitlement data will come from several places, and assembling it is an administrative job in its own right. Typical sources:
Expect that no single source gives you everything. Consolidation and triangulation across all three is normal, not a sign that something has gone wrong. CerteroX SAM holds licences, transactions, agreements, maintenance, suppliers and publishers in one place, including Microsoft Licence Statement import, so the reconciliation happens against a single entitlement record rather than a folder of spreadsheets.
Now you have two data sets and can reconcile them. Simple in theory, considerably more involved in practice.
A SAM tool does the heavy lifting: recognising applications, versions and editions, and using information such as SKUs to apply the right licensing rules. Some publishers’ rules automate cleanly. Some are hard — and it is worth being precise about what “hard” means, because it is not the same as impossible. Oracle options and packs with evidence and override, processor types and core factors, cover-down logic for Enterprise Edition, IBM PVU and Virtual Processor Core sub-capacity, SAP named-user de-duplication across systems, Microsoft server core licensing with cluster and virtualisation awareness — those are all modelled by dedicated engines rather than left to a generic rule set. Six publishers get that treatment.
What the reconciliation produces is not a single number. It is purchased, used, available, required, variance and exposure, per licence — plus the overspend and additional-licence-required calculation, downgrade rights, second-use entitlement and the Exclude From Licensing workflow that keeps MSDN, development, training and second-use devices out of a count you would otherwise have to defend.
Where a consultant still earns their keep is on the contracts. Someone with in-depth knowledge of a publisher’s specific agreement — the amendments, the negotiated terms, the clause that changes how a metric is counted for you and nobody else — works alongside the tool to finesse the calculation so the position reflects your commercial reality rather than the publisher’s standard terms.
And that is an Effective Licence Position. Easy to explain, much harder to build.
It is important to understand that the ELP is a means to an end, not the destination. Armed with the position, and enriched with metering data about actual usage, you can make real decisions: what to buy next, where the financial and compliance risk sits, whether anyone is using the technology you have already adopted. File-based usage metering with first-used and last-used tracking, and a % Used utilisation figure over a rolling 90-day window, is what turns “we own 400 of these” into “we own 400 and 130 have not been opened since March”.
The other thing to understand is shelf life. A position finalised in a project has begun going out of date by the time it is presented. An annual Effective Licence Position belongs to the era it came from. This is the part of the original argument that has been overtaken by the product: CerteroX SAM maintains a continuous compliance position rather than a point-in-time reconciliation, so the question stops being “when was the last ELP?” and becomes “what does it say this morning?”
Finally, the value of the Effective Licence Position is changing. It used to exist because someone needed to establish a compliance position — often because a letter had arrived. That is still true to a degree. But as organisations move to cloud applications and subscription licensing, the position becomes more useful for optimising consumption and spend than for defending a number. The compliance case for building one has not gone away. The commercial case has overtaken it.
If you need to build a position for Microsoft, Oracle, IBM, SAP or another major publisher, talk to us.
Other posts covering the same ground.
An Oracle Unlimited Licence Agreement is only unlimited within its clauses. What certification actually asks of you, where toxic consumption creeps in, and why the measurement work has to start at the beginning of the term rather than the last six months.
Microsoft's August 2025 Product Terms changes: Extended Term standardised across programmes, Exchange and Skype for Business Server Subscription Editions, the Exchange and Windows 10 ESU programmes, and the Dynamics 365 F&O enforcement dates.
Renew, rescope or exit — an Oracle ULA gives you three routes and a narrow window to choose between them. The questions to settle first, and a six-point health check to see how ready you actually are.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.