IBM True Up Strategies: The Buyer Side Playbook.

What true up is.

An IBM true up is the annual reconciliation event in which a Passport Advantage customer measures the deployed software footprint, compares it against the entitled baseline, and purchases incremental licences for any gap. True ups are most common at the S and S anniversary date or at the end of an Enterprise Licence Agreement period, but they can occur at any point that IBM commercial wants to formalise the deployed inventory.

The true up is not an audit. It is a customer initiated reconciliation that gives the customer the chance to bring the entitlement record current ahead of any external review. Done well, the true up replaces the audit as the formal compliance event. Done poorly, the true up becomes a precursor to an audit because the reconciliation surfaces gaps that IBM commercial then chooses to examine more closely. The strategy guidance on this page is oriented at the well executed scenario.

Written from the buyer side by independent advisors. We are not an IBM Business Partner. The orientation here is on the buyer side levers, not on selling additional product. For our independence position, see why independence matters.

The arithmetic.

The true up arithmetic has three inputs. The deployed footprint, measured in the product specific metric (PVU, RVU, VPC, AppPoint, Authorized User, and so on). The entitled baseline, drawn from the Passport Advantage entitlement record. The reconciliation purchase, calculated as deployed minus entitled, times the relevant unit price, times the discount tier.

Three details matter. The deployed measurement is the source of most disputes. For PVU products under sub capacity, the four ILMT reports are the authoritative source. For products outside sub capacity, the measurement is a customer self assessment. See self assessment guide. For Cloud Pak and VPC products, the IBM License Service is the measurement source. See container licensing.

The unit price is drawn from the IBM published Net List Price at the time of the true up, and the discount tier is determined by the customer Passport Advantage relationship. The pricing surface is therefore current, not historical, and the buyer side discipline is to anchor the true up against the negotiated discount tier rather than the headline list price.

Lever one: pre true up harvest.

The first and largest lever is the pre true up harvest. Before the deployed footprint is measured, the customer side runs a complete harvest of all software that can be uninstalled, decommissioned, or moved off licensed servers. The harvest reduces the deployed footprint and therefore the true up bill.

The harvest discipline has three components. First, identify dormant software that is installed but not in active operational use. Second, decommission test, development, and disaster recovery environments that are not under active workload. Third, consolidate workloads onto fewer licensed hosts to reduce the PVU and VPC footprint. The combined harvest on a Fortune 500 estate typically reduces the deployed footprint by ten to twenty five percent. See shelfware recovery for the harvest mechanics.

The pre true up harvest is timing sensitive. The harvest must be completed before the deployed footprint snapshot is captured. For sub capacity products, the snapshot is the four ILMT reports covering the prior measurement period. For other products, the snapshot is the self assessment report. The harvest window is therefore the ninety day period preceding the measurement snapshot. See the 90 day evidence window.

Lever two: sub capacity tightening.

The second lever is sub capacity tightening. For PVU products under sub capacity, the deployed footprint is measured against the peak observed concurrent PVU consumption in the measurement window. Sub capacity tightening reduces the peak, which reduces the deployed measurement, which reduces the true up bill.

Sub capacity tightening has three operational moves. First, hypervisor pinning. Constrain the VMs running licensed software to a specific subset of physical hosts in the cluster. The pinning reduces the entitled host pool and therefore the measured PVU. Second, vCPU resizing. Right size the vCPU allocation on each licensed VM to match the actual workload requirement. The right sizing reduces the per VM PVU. Third, peak avoidance. Schedule heavy batch workloads outside the sub capacity peak measurement window to reduce the peak observed concurrent consumption. See sub capacity explained and VM virtualization rules.

Sub capacity tightening is the second largest lever after pre true up harvest on a typical Fortune 500 estate. The combined reduction is in the ten to twenty percent range relative to a baseline without active tightening discipline.

Lever three: metric optimisation.

The third lever is metric optimisation. Several IBM products carry alternative metrics, and the buyer side discipline is to deploy each workload against the metric that minimises the licence cost for that workload. Three metric optimisation patterns recur on Fortune 500 estates.

Authorized User vs PVU.

Many IBM products carry both Authorized User and PVU metrics. The optimisation is to identify workloads with low user counts but high PVU footprints, and route them onto Authorized User licences instead of PVU licences. The break even point varies by product but typically falls at fifty to one hundred Authorized Users per PVU equivalent. See PVU explained.

Authorized User vs Concurrent User.

For products that offer both Authorized User and Concurrent User metrics, the optimisation is to identify products with high named user counts but low simultaneous usage, and route them onto Concurrent User licences. Cognos and SPSS are typical candidates. See Cognos licensing and SPSS licensing.

VPC vs PVU on Cloud Pak.

The Cloud Pak portfolio uses VPC as the unified metric, but legacy PVU entitlement can sometimes be carried over. The optimisation is to compare the VPC cost against the carry over PVU equivalent and select the lower cost path. See Cloud Pak strategy.

Lever four: timing.

The fourth lever is timing. The true up can be executed at any point in the year, and the timing decision affects the commercial terms in three ways.

First, IBM quarter end. A true up executed at IBM March, June, September, or December quarter end is structurally easier to negotiate because the IBM commercial counterparty has quota pressure. The discount tier on the true up purchase is typically two to four percent better at quarter end than mid quarter.

Second, anniversary alignment. A true up executed at the S and S anniversary aligns the true up purchase to the existing S and S stream, simplifying the operational consolidation and the multi year overlay. See co term strategy.

Third, ELA window. A true up executed inside an active ELA period typically falls under the ELA commercial structure rather than the standard Passport Advantage tier. The ELA structure can be more favourable or less favourable depending on the ELA design. See ELA vs PA.

The annual cadence.

The four levers combine into a single annual cadence. The cadence has six phases that run on a twelve month cycle.

1. Inventory. Build the deployed inventory across the IBM estate. Update the SAM tool data, the ILMT reports, and the manual inventory for non sub capacity products.
2. Harvest. Identify and execute the pre true up harvest. Decommission dormant software, consolidate workloads, drop S and S on harvestable entitlement.
3. Tighten. Execute the sub capacity tightening discipline. Pin hypervisors, right size vCPUs, manage peak avoidance.
4. Optimise. Apply the metric optimisation discipline across products with alternative metrics.
5. Time. Select the true up execution window. Coordinate with the S and S anniversary, the ELA window, and the IBM quarter calendar.
6. Execute. Run the true up purchase against the negotiated discount tier, with the multi year overlay if applicable. See multi year strategy.

The annual cadence is the operational anchor for the buyer side IBM relationship. The cadence integrates the technical inventory work with the commercial negotiation work and the strategic optimisation work into a single rhythm that compounds across years. See cost optimization guide for the broader framework.

Where to go next.

For the operational guide to true up cycles, see IBM true up management. For the harvest discipline that funds the pre true up reduction, see shelfware recovery. For the sub capacity tightening view, see sub capacity explained. For metric optimisation, see PVU optimization. For the multi year overlay that anchors the true up purchase, see multi year strategy. For co term timing, see co term strategy. For the cost optimisation framework that contains the true up cadence, see cost optimization guide. For the audit defence view, see audit defence complete guide.

For a scoped advisory conversation about your annual true up cycle and the four lever discipline, the contact page is the entry point. A senior advisor responds within 24 hours.