Effective Licensing Position — the document that anchors the audit settlement.

What is actually deployed, where, at what version.

The deployment layer is the most operationally complex and the most often wrong. The inventory must cover every server, every virtual machine, every container, every endpoint, every user-licence-consuming session. It must record vendor product, version, edition, deployed options/packs/features, deployment environment (prod, non-prod, DR, test), virtualisation context (host-cluster topology for Oracle and IBM partitioning analysis), and last-active timestamp where the metric is user-based.

SAM tooling is necessary but never sufficient. Every SAM tool has blind spots, and the blind spots are vendor-specific: Oracle option detection requires direct database query (DBA_FEATURE_USAGE_STATISTICS); IBM PVU calculation requires ILMT history; Microsoft per-user reconciliation requires Azure AD sign-in correlation; SAP indirect access requires application-layer integration mapping. The deployment inventory is a stitched view, not a tool output.

What is actually entitled, under what metric, on what terms.

The entitlement layer is harder than buyers think. It requires every contract amendment, every order document, every ULA certification, every Software Assurance benefit, every previously-purchased option or pack. It requires correct metric interpretation: NUP minimums per processor on Oracle, qualified-user counting on Microsoft, Named User classification under SAP's licence schedule, PVU sub-capacity rules on IBM. It requires status verification: which licences are perpetual, which are subscription, which are on active support, which lapsed.

The most common entitlement error is failing to include licences acquired through M&A, channel resellers or historical OEM agreements. Across 340+ engagements, every third ELP discovers between $200K and $4M of forgotten entitlement that materially reduces the deployment gap.

Entitlement-side artefacts to assemble

• Master agreement and every amendment, by signed date.
• Every order document with metric and quantity stated.
• Software Assurance, Premier Support and renewal certificates.
• M&A integration evidence — which target-company contracts transferred.
• OEM and embedded-licence agreements often kept by line-of-business owners.

The reconciled net position is where the 68% reduction lives.

Reconciliation is not arithmetic. It is the application of contractual interpretation — the legitimate readings of the contract that favour the buyer where ambiguity exists. Oracle partitioning policy is interpretation, not contract. SAP indirect access methodology is interpretation. Microsoft per-user counting boundaries are interpretation. IBM sub-capacity rules require ILMT history. Each interpretation has a defensible reading and an over-aggressive reading. The buyer's ELP applies the defensible buyer-favouring reading consistently and documents the rationale.

The third layer is where the 68% average claim reduction we report originates. It is not built by inventory and entitlement alone — those layers identify the gap. The interpretation layer is what compresses the gap from "vendor opening claim" to "defensible settlement number." It requires former-vendor expertise on the team to apply credibly. A rigorous software license compliance assessment is what produces a defensible ELP in the first place — the reconciled, interpretation-tested net position the buyer brings to any settlement.

Continuous, not just under audit.

The mistake most buyers make is treating ELP as an audit-time deliverable. The cost of building an ELP under audit pressure is 3–5x the cost of maintaining one continuously, and the audit-time ELP is always less defensible because it is built fast. A continuously-maintained ELP, refreshed quarterly with deployment changes and annually for entitlement reconciliation, eliminates the audit-time crunch and produces materially better outcomes when audits do arrive.