Broadcom Audit Claim Calculation Methods

Every Broadcom audit finding is the output of a specific calculation. The calculation is rarely shown to customers in full. Customers see the final number — the claim, denominated in dollars — and sometimes a one-page summary of how the calculation was performed. The intermediate variables, where most of the leverage actually sits, are usually obscured by the way auditors present their results.

This article walks through the calculation method that Broadcom auditors use in current practice, broken into its component variables. For each variable, it identifies the auditor's typical assumption, the customer's typical counter-position, and the size of the impact the variable has on the final claim. The objective is not to teach customers to perform the calculation themselves; it is to teach them which variables to challenge and what good a successful challenge actually does.

The basic structure of a claim

A Broadcom audit claim is the product of five variables. Deployment is the measured quantity of the product in use. Entitlement is the contractually licensed quantity. Gap is the difference between deployment and entitlement. Unit price is the price applied to each unit of gap. Multipliers are the uplifts, back-support, and penalties applied to convert the priced gap into the headline claim.

Most claims can be reconstructed as: Claim = (Deployment - Entitlement) × Unit Price × Multipliers. The auditor controls every variable except entitlement. The customer's leverage comes from challenging each of the four auditor-controlled variables, and the leverage compounds — a successful challenge on deployment combined with a successful challenge on unit price produces a much smaller final claim than either challenge alone.

Deployment measurement: how usage becomes a number

Deployment is the measured quantity of product in use. The auditor's measurement depends on three methodology choices: the measurement unit, the measurement window, and the inclusion rules.

Measurement unit

VMware audits measure deployment in CPUs, cores, or per-VM units depending on the licensing model. The shift from per-CPU to per-core licensing in the post-acquisition era has materially expanded the deployment number for many customers, because high-core-count hosts now count larger than they did under per-CPU terms. The applicable measurement unit is determined by the contract, not by Broadcom's current price list. Audits that apply per-core measurement to entitlements purchased under per-CPU terms are converting contractual terms into commercial terms, which is a defensible challenge.

Measurement window

Deployment can be measured as a point-in-time snapshot, an average over time, or a peak over time. Each produces a different number, and the gap between them can be large. Auditors typically prefer peak measurement, because it produces the largest number; customers typically prefer average measurement, because it more accurately reflects sustained usage. The contractually defensible measurement is usually the one that aligns with the licensing model — per-CPU licensing typically measures point-in-time host configurations, not transient VM utilisation peaks.

Inclusion rules

What counts as deployment? Production virtual machines and hosts almost always count. Powered-off VMs, disaster-recovery cold-standbys, lab workloads, and test environments often do not count under the applicable contract language. Auditors typically count everything that has been powered on within the measurement window; customers typically count only the deployment that meets the contractual definition of active use.

Entitlement: the contractually licensed quantity

Entitlement is the only variable the customer controls. It is established by the contractual records: purchase orders, license agreements, amendments, and Broadcom's internal entitlement system.

In practice, entitlement is rarely a single clean number. Customer records and Broadcom's internal records often disagree. Broadcom inherited records from VMware, Symantec, and CA Technologies through acquisition, and the migration of those records into Broadcom's systems was not clean. We have seen audits in which the customer's documented entitlement was twenty to forty per cent larger than Broadcom's internal entitlement record. In every case, the customer's documented entitlement governed once it was substantiated by purchase orders and signed agreements.

The first work of any audit defence is to reconstruct entitlement from the customer's own records, compare it to the auditor's stated entitlement, and surface any discrepancies in writing in the first weeks of fieldwork. Entitlement discrepancies that favour the customer almost always reduce the claim if surfaced; if not surfaced, they are silently absorbed into the auditor's working position and are never recovered.

Gap: the simple subtraction with complicated edges

Gap is deployment minus entitlement. The arithmetic is simple but the edges are not. Three edge cases produce most of the gap-related disputes.

Mixed entitlement types

Customers often have a mix of perpetual licenses, subscription licenses, and bundled-in entitlements (for example, VCF includes vSphere, vSAN, NSX, and Aria). The auditor's calculation should treat each entitlement type appropriately. Treating a perpetual entitlement as if it had expired, or treating a bundled entitlement as if the bundle did not exist, are common methodology errors that inflate the gap.

Entitlement applied at the wrong scope

An entitlement for one business unit being applied only to that business unit's deployment, when the contract permits enterprise-wide use, can produce an artificial gap. The contractual scope of each entitlement should be matched to the deployment scope before subtraction.

True-up entitlements purchased mid-period

If the customer purchased true-up entitlements during the audit period, those entitlements should be applied to the deployment that existed after the purchase, not subtracted from the deployment that existed before. Auditors sometimes apply true-up entitlements to the wrong portion of the deployment, producing an artificial gap.

Unit price: list, negotiated, or settlement

The unit price applied to the gap is one of the most contested variables in the calculation. There are at least three defensible price levels.

List price is the published Broadcom price for the relevant SKU at the time of the audit. Auditors typically apply current list price, which is usually higher than the price the customer would have paid in a normal procurement. Effective negotiated price is the price the customer historically paid for the same SKU under their master agreement — usually substantially lower than list. Settlement price is the price implicit in the eventual settlement structure, often lower again because Broadcom prefers to close audits with discounted settlements rather than litigate list-price claims.

The contractually defensible position varies by master agreement. Some agreements specify that audit remedies apply at the customer's "then-applicable" price, which is usually the negotiated price. Others are silent, which auditors interpret to mean list price. Customers should examine the language carefully and assert the most favourable defensible position.

Multipliers: support, penalties, and timing

The headline claim is rarely just gap times unit price. Auditors typically apply multipliers that uplift the priced gap into a larger headline number.

Back-support

If the deployment has been in place for several years, the auditor will often add back-support — the support payments that would have been due on the unlicensed deployment had it been licensed correctly. Back-support can multiply the unit-price-times-gap calculation by 1.5x to 3x, depending on the deployment age. The contractual basis for back-support is sometimes weaker than auditors imply; not all master agreements clearly authorise it, and where they do, the back-support period is often limited to the audit period itself rather than the full deployment age.

Penalty uplifts

Some auditors apply penalty uplifts — typically a percentage uplift framed as a "non-compliance premium" — on top of the priced gap. Penalty uplifts are rarely well-grounded in master-agreement language. Most agreements specify that the audit remedy is the unpaid license fee plus support, without a penalty component. Customers should challenge penalty uplifts on contractual grounds.

Subscription-equivalent uplift

In current Broadcom practice, the most consequential multiplier is the subscription-equivalent uplift. The auditor calculates the gap in perpetual-equivalent units, then "converts" the gap to subscription units at the conversion ratio Broadcom uses for VCF migrations. The conversion ratio is set by Broadcom and is heavily favourable to Broadcom. Customers should challenge the conversion as a commercial pricing choice that the audit clause does not authorise.

The sequence of compounding challenges

The order in which a customer raises challenges matters. Five compounding challenges, applied in sequence, typically reduce a claim by sixty to eighty per cent against the auditor's opening position.

First, deployment scope challenges — removing deployment that should not have been counted. Second, entitlement reconciliation — recovering documented entitlements that the auditor's records understate. Third, unit-price challenges — applying the contractually defensible price level rather than current list. Fourth, multiplier challenges — removing back-support and penalty uplifts that are not contractually grounded. Fifth, subscription-equivalent conversion challenges — refusing to accept the commercial conversion ratio as if it were a contractual remedy.

Each challenge on its own can reduce a claim by ten to thirty per cent. The five combined typically produce settlements in the thirty-to-forty per cent range of opening positions.

The methodology document that should always exist

Every audit should produce, by settlement, a written methodology document that records the auditor's measurement choices, the entitlement reconciliation, the price level applied, and the multipliers included. Customers should insist on receiving this document, in writing, before settlement closes. Without it, the calculation cannot be reconstructed if future disputes arise.

The methodology document also serves as a forward-looking compliance reference. If a future audit applies different methodology to the same environment, the prior methodology document is evidence of what was contractually accepted at the prior settlement. This is one of the small but durable benefits of doing the calculation work properly: it constrains the auditor's future methodology choices as well as the current one.

Related reading

For the procedural context inside which the calculation happens, see our companion guides on the audit process, scope limitation, and post-audit settlement. The calculation is what scope and data-request work shape, and what settlement negotiation closes.