>
PVU, RVU and VPC Metrics
Journal · May 2026 · 6 minute read

Why over buying PVU just in case is a mistake.

Buying a cushion of extra PVU feels like prudence. In practice it spends budget on protection that an audit ignores, because findings turn on deployment against entitlement product by product, not on a pile of surplus units sitting somewhere else. The cushion costs money up front, carries support charges forever, and rarely covers the gap it was meant to. Independent, not affiliated with IBM Corporation.

The instinct is understandable. PVU exposure is frightening, audits are unpredictable, and a buffer of unused entitlement looks like insurance against an unexpected finding. The trouble is that this particular insurance does not pay out the way buyers expect. An audit does not net your total purchased PVU against your total deployed PVU. It checks each product against its own entitlement, and a surplus in one place does almost nothing for a shortfall in another.

The buffer that protects nothing.

When IBM reconciles an estate, it builds the finding from specific products on specific hosts measured against the entitlement for those exact products. A general reserve of PVU does not slot into that calculation. If the finding is on WebSphere and the surplus was bought against a different product, the surplus is invisible to the finding. The buffer was sized against a fear, not against the way the audit actually counts, so it sits unused while the gap it was supposed to cover is charged anyway.

Why surplus does not offset a shortfall.

Entitlements are not fungible across products or, in many cases, across metrics. The reasons a buffer fails to transfer:

The legitimate offsets in an audit come from entitlements IBM overlooked for the very products in scope, not from unrelated surplus bought as a hedge.

The cost of carrying unused entitlements.

A buffer is not free to hold. Beyond the purchase, entitlements typically carry ongoing support and subscription charges that recur whether or not the capacity is ever used. So the cushion bought once keeps billing year after year, quietly, for protection it does not provide. Budget that could have funded accurate measurement or sub-capacity tooling instead funds shelfware that an auditor will never credit back to you.

The hedge that actually works.

The real protection against an unexpected finding is not surplus, it is knowing your position before IBM does. That means accurate, current measurement of what is deployed against what is entitled, product by product; a clean sub-capacity posture where PVU products are virtualized; and the discipline to reconcile on a schedule rather than discovering the gap in an audit letter. Money spent there reduces real exposure. Money spent on a just in case buffer mostly reduces the bank balance.

What this means under audit

An audit checks each product against its own entitlement, so a general PVU buffer does not offset a specific shortfall. Surplus is not fungible across products or metrics, it carries recurring support charges, and the auditor will not credit it against an unrelated finding. Spend on accurate measurement and a clean sub-capacity posture instead, because that is what reduces real exposure.

Common questions.

If I am over licensed overall, am I safe in an audit?
Not necessarily. Audits reconcile each product against its own entitlement. Being over licensed on one product does not cover a shortfall on another, so an overall surplus can sit beside a real finding that still gets charged.
Can I use surplus PVU to offset an RVU or user gap?
No. The metrics are not interchangeable. PVU surplus does not offset an RVU or user based shortfall, because each is counted on its own basis against its own entitlement.
What should I spend on instead of a buffer?
Accurate, current measurement product by product, a clean sub-capacity posture for PVU products, and regular reconciliation. That reduces real exposure, whereas a just in case buffer mostly adds recurring support cost for capacity an audit will not credit.
Tempted to buy a buffer before an audit?
We reconcile what you actually owe, product by product, against entitlements first, so you spend on the real gap rather than shelfware.
Explore PVU Reconciliation →

The IBM Audit Brief

Audit triggers, ILMT pitfalls, and settlement tactics for IBM software buyers.

IBM Audit

Independent, buyer side IBM software audit defense and negotiation. Not affiliated with IBM Corporation.

Services
Audit DefenseAudit NegotiationILMT RemediationSub-Capacity Defense
Products
WebSphereDb2CognosCloud Pak
Company
AboutContactJournalWhite Papers
Independent. Not affiliated with IBM Corporation.Buyer Side · Est. 2019