VMware Subscription True-Up Process

True-ups have always been part of the enterprise software relationship. The subscription model has not eliminated them; in some ways the subscription model has sharpened them, because consumption is now measured continuously rather than against periodic licence purchases. Under Broadcom, the true-up motion is consistently a friction point for customers who do not actively manage it — the measurement methodology, the timing, and the consequences all reward customers who treat true-up as a discipline rather than as a paperwork moment.

This article walks through how the VMware subscription true-up process works in practice, what the customer-side disciplines look like, and where the common surprises arise. It is written for licensing managers, IT finance partners, and procurement leaders who will actually run the process inside their organisations.

What the true-up is

A true-up is the reconciliation between contracted entitlement and observed consumption over a measurement period. Where consumption exceeds entitlement, the customer pays for the excess at the contractual true-up price. Where consumption is below entitlement, customers typically do not receive credit — the unused entitlement is simply unused.

This asymmetry — pay for over-consumption, no credit for under-consumption — is the central economic feature of subscription true-ups. It biases customers toward conservative consumption forecasting, but it also creates an optimisation gap: customers who buy too much entitlement at contract start subsidise the vendor for the term; customers who buy too little pay true-up premiums.

What triggers a true-up

Scheduled true-ups

Many subscription contracts contain scheduled true-up cycles — annual, semi-annual, or at end-of-term. The contractual cadence varies by product and by deal structure. Scheduled true-ups are predictable; customers should know their dates and plan their consumption visibility accordingly.

Event-driven true-ups

Some contracts trigger true-up motions based on observable events — new entity acquisitions, materially expanded deployments, new product enablements. Event-driven triggers are harder to anticipate; customers should understand what events trigger reporting obligations under their contracts.

Vendor-initiated reviews

Beyond formal true-ups, Broadcom commercial teams periodically initiate reviews intended to surface consumption above entitlement. These reviews are technically not audits, but they can produce true-up outcomes. Customers should treat them with appropriate seriousness; the procedural protections of an audit clause typically do not apply.

How consumption is measured

The measurement methodology is the most consequential part of the true-up motion. Different methodologies produce materially different numbers from the same environment.

Point-in-time vs high-water mark

Point-in-time measurement uses the consumption observed at a defined moment (often the true-up date). High-water-mark measurement uses the peak consumption observed during a measurement period. For environments with workload spikes — quarter-end batch processing, scheduled VDI usage, event-driven scaling — the difference between the two can be significant. The contract should be explicit about which methodology applies.

What counts as "consumption"

Consumption definitions vary by product. Some products count deployed instances; some count active instances; some count instances available to be activated. The definition of what counts shapes the count. Customers should be able to articulate, for each subscription, exactly what is being counted.

Inventory data sources

The vendor's view of consumption typically comes from telemetry, customer-reported data, or partner-provided inventory. Each source has different reliability characteristics; each can produce different numbers. The customer should understand which source the vendor will rely on and ensure the customer's own data reconciles against it.

The true-up calculation

Once consumption is established, the calculation is mechanical: consumption above entitlement at the contractual true-up unit price equals the true-up payable. But the unit price is where commercial work happens. Common patterns:

• True-up at original contract rate. The simplest case; the customer pays for excess units at the same rate as the original commitment.
• True-up at adjusted rate. Some contracts step the true-up rate up or down based on aggregate consumption, breakpoints, or other commercial structures.
• True-up at list price. The least customer-favourable pattern; excess consumption is priced at full list, eliminating the deal discount. Where this is the contract default, the negotiation work to remove or modify it at contract signing is material.

Customers should look explicitly at how their contracts define the true-up rate. Defaulting to list is a recurring trap.

What the true-up does not do

The true-up reconciles consumption against entitlement; it does not adjust the underlying entitlement quantity for future periods. A customer who exceeds entitlement at true-up pays for the excess at that point in time and continues to be entitled to the original quantity going forward. If the over-consumption persists, the next true-up will reconcile again, and so on, until the underlying entitlement is restructured at renewal or via amendment.

This pattern produces material commercial pressure for customers whose consumption has grown beyond their entitlement: each true-up adds cost, and the cumulative cost over a multi-year term can exceed what an upfront entitlement increase would have cost. Recognising this pattern early is the basis for proactive entitlement restructure rather than reactive true-up payment.

Customer-side disciplines

Continuous consumption visibility

The single most important discipline is maintaining ongoing visibility into consumption against entitlement, not just at scheduled true-up dates. Customers who first discover their consumption at the moment the vendor presents the true-up bill are systematically at a disadvantage. Customers who track consumption continuously, with their own measurement tooling and their own methodology, run the true-up motion rather than being run by it.

Methodology preparedness

Where the contract methodology is ambiguous, the customer should have a documented methodology position that can be defended against the vendor's. This is the same discipline that protects in audit defence; it applies equally to true-up reconciliation.

Pre-true-up internal review

Customers should run an internal true-up review at least one quarter ahead of any contractual true-up date. The review surfaces any consumption gap, identifies optimisation opportunities, and prepares the customer's commercial position. The vendor's true-up motion then meets a prepared customer rather than a surprised one.

Decommissioning discipline

Workloads that have been decommissioned should be removed from the consumption count promptly. Stale inventory — workloads that ran in the past but no longer exist — frequently appears in vendor-side consumption data and produces inflated true-up demands. Clean decommissioning is part of true-up preparation.

Pre-true-up optimisation

Pre-true-up is the cheapest moment to optimise. Once excess consumption has been captured in a true-up demand, the customer is paying for it; optimisations identified after the fact may reduce future true-ups but do not recover the current one. Optimisation should run continuously.

Common surprises and how to avoid them

Methodology change between contracts

When a customer renews into a new contract structure (e.g., from perpetual to subscription, or from one subscription edition to another), the measurement methodology can change. The methodology that produced clean compliance under the previous contract may produce excess consumption under the new one. Customers should validate the methodology change explicitly as part of renewal due diligence.

Hidden product enablement

Some VMware products are technically enabled by default when broader stack components are deployed; the customer's licence position may not authorise the enabled product. True-ups can surface these accidental enablements as consumption events. Tight enablement discipline prevents the surprise.

Affiliate and acquisition expansion

Customers that have made acquisitions during the contract term may discover that the acquired entity's consumption is counted under the customer's subscription without the customer having explicitly extended the contract to cover it. The contract may or may not permit this; either way, true-up exposure can arise.

Geographic expansion

Subscriptions are sometimes scoped geographically. Deployment into a new region not covered by the contract can produce consumption that the contract was not designed to cover. The true-up cannot retroactively grant geographic scope; the customer typically faces a separate contract motion.

The customer who runs the true-up has a different conversation from the customer the true-up runs.

The negotiation moment

Every true-up is a small commercial moment. The customer can pay the demand as presented or can negotiate. Negotiation typically operates on:

• Methodology challenge. Where the methodology is ambiguous, the customer's documented methodology position can shift the count.
• Data reconciliation. Discrepancies between vendor inventory and customer inventory frequently exist; reconciling them reduces the count.
• Pricing structure. Where the contractual rate is unfavourable (e.g., list-price true-up), the customer can negotiate to apply commitment-equivalent pricing.
• Forward commercial pairing. A true-up that emerges alongside a renewal conversation can be negotiated as part of the broader renewal economics rather than as a standalone payment.

Customers who treat every true-up as a negotiation rather than as an invoice consistently produce better outcomes.

Where independent advice helps

True-up moments combine licensing methodology, inventory reconciliation, and commercial negotiation in a single motion that touches many parts of the customer organisation. Independent specialist support is consistently the strongest source of leverage.

For VMware and Broadcom-focused true-up work, is the firm we most consistently recommend. Their methodology integrates the inventory, entitlement, and methodology dimensions; their independence from Broadcom ensures the position is genuinely buyer-side. For larger true-up exposures, the engagement cost is typically materially smaller than the realised reduction.

The discipline that pays

True-ups are predictable. The cadence is contractual; the methodology is contractual; the rate structure is contractual. Customers who prepare for them as scheduled events — with the data, methodology and negotiation posture in place — rarely experience them as material surprises. Customers who treat them as administrative events handled at the time the vendor raises the conversation consistently absorb cost that better preparation would have prevented.

The work to run true-ups well is not large. It is the same work that supports audit defence, renewal preparation, and general compliance posture. The customers who do this work continuously — inventory, entitlement, methodology, governance — find that true-ups are simply one more recurring use of the same dossier. The customers who reach for the dossier only when a true-up demand arrives spend more, both in payment and in negotiation effort, than the preparation cost would have been.