① Journal · Broadcom (CA) · Audit
Since the portfolio moved to consumption licensing, Broadcom (CA) audits have shifted from counting seats to reconciling consumption against commitment. From the buyer side the activity clusters on four areas, and the financial exposure lives in the gap between the baseline you agreed to and the capacity you actually run.
A Broadcom audit is a consumption dispute. It is won on the baseline you modeled first.
Broadcom (CA) licenses the mainframe portfolio mainly through Mainframe Consumption Licensing (MCL), an annual subscription priced against a committed MSU (Million Service Units) baseline, with consumption below the baseline typically rolling forward to the next true up period during the term. That structure changes what an audit is. It is no longer a seat count, it is a reconciliation of consumed capacity against the number you committed to, product by product, across a portfolio that Broadcom has steadily consolidated. The common thread in the activity we observe is the gap: between contracted capacity and consumed capacity, between what the contract entitles and what is deployed, and between the baseline as signed and the baseline as it should have been modeled.
The pattern we commonly observe is not aggression for its own sake but a methodical test of consumption against commitment, with the fallback positions running in Broadcom's favor. Growth above the baseline triggers a True Forward charge that raises the floor for the remainder of the term rather than crediting unused capacity back. A baseline set high at signing, or a portfolio bundled without product level reconciliation, becomes the number every subsequent true up builds on. The buyers who come through a Broadcom audit without a surprise are the ones who validated their own consumption data before the notice arrived, inventoried every CA product actually running against entitlement, and modeled the MCL baseline before they ever signed it. Read this with the state of Broadcom CA renewals and the Broadcom (CA) publisher hub.
Where Broadcom (CA) mainframe audits cluster · what we commonly observe and the buyer defense
| Focus area | What Broadcom checks | Buyer defense |
|---|---|---|
| MCL consumption baseline | Consumed MSU against the committed baseline and rollover | Validate consumption independently, model the baseline before signing |
| Capacity reporting | Peak MSU and MIPS by product through SCRT report management | Validate SCRT, reconcile to contracted capacity per product |
| Portfolio entitlement | Deployed CA products across the portfolio against what is licensed | Inventory every product, document decommissions and scope |
| True Forward true up | Growth above baseline billed forward, not credited back | Track usage monthly, manage growth before the true up date |
These are patterns we commonly observe across Broadcom (CA) mainframe audits, not statements of Broadcom audit policy. Your specific entitlements, MCL terms, and measurement obligations govern; validate against your own consumption data and your contract before relying on any position.
The baseline is the number the entire term builds on, and it is far harder to reset once signed than to set correctly the first time. Pull twelve months of MSU consumption by product, separate stable workload from seasonal peaks, and model the baseline against your real profile rather than accepting Broadcom's framing. A baseline set to your validated consumption is a baseline you can defend at every true up. See our guide to negotiating the MCL consumption baseline.
Set the baseline once, set it right.
The audit is decided by the consumption data, and the buyer who validates that data first controls the discussion. Run your own SCRT and consumption validation before sharing anything, reconcile it against contracted capacity product by product, and resolve discrepancies internally rather than discovering them in Broadcom's report. Read our explainer on contractual MSU versus consumed MSU for the gap that drives most of the exposure.
Check your own numbers before the auditor does.
Broadcom has folded a wide CA catalog into a single portfolio, and entitlement against deployment is where the quiet exposure lives. Inventory every CA product actually running, match it to entitlement, document every decommission, and scope the audit to the products in question. Answer each request in writing. A clean portfolio inventory turns the audit into a reconciliation rather than an open ended portfolio true up. See our guide to preparing for a Broadcom CA renewal.
Know every product running before they ask.
④ Where the Broadcom audit is won
A Broadcom audit reconciles consumption against commitment. The defense is a baseline you modeled first. Model the baseline, validate consumption, inventory the portfolio.
Mobilization on an audit notice
Mainframe spend negotiated on the buyer side
Typical renewal reduction
Four areas: consumed MSU against the committed MCL baseline, capacity reporting by product through Broadcom SCRT report management, product entitlement across the consolidated CA portfolio against what is deployed, and the True Forward mechanism where growth above baseline is billed forward. The common thread is the gap between what you committed to and what you run.
Under Mainframe Consumption Licensing the fee is set against a committed baseline, with unused MSU typically rolling to the next true up during the term. Growth above baseline triggers a True Forward charge that raises the floor. A baseline set high, or a portfolio bundled without product level reconciliation, becomes the number every true up builds on. Modeling it before signing is the defense.
Treat it as a consumption and entitlement reconciliation. Validate your own data before sharing anything, inventory every CA product deployed against entitlement, document decommissions, and answer each request in writing scoped to the products in question. A consumption position you validated first turns the audit into a routine reconciliation. See what happens to pricing after a vendor is acquired.
We validate your consumption position independently, model the MCL baseline, inventory the portfolio, and manage the response from the buyer side so the reconciliation runs on your evidence. Our audit defense service mobilizes within 48 hours of a notice and our license negotiation service resets the baseline the audit and the next renewal both build on.
Related: Broadcom (CA) publisher hub · IBM audit activity · BMC audit activity · the MSU baseline · audit defense
Audit notice or renewal under 18 months out? We mobilize within 48 hours.
Get expert help →