What a Cisco True-Up Actually Is — and Why It Surprises So Many Enterprises

What Is a Cisco ELA True-Up

The Cisco ELA true-up is the annual reconciliation between the user or device population committed in your ELA at signing and the actual deployment at the point of measurement. In theory it is a straightforward accounting exercise. In practice, it is one of the most commercially consequential conversations enterprises have with Cisco each year — because the rules governing what counts as "deployed," how the measurement is conducted, and what rate applies to any over-deployment are often misunderstood by the procurement teams responsible for managing the ELA.

Step 1: How Cisco Measures Deployment for True-Up

Cisco's primary measurement source for ELA true-up is the Cisco Smart Software Manager (CSSM) portal. For ELA customers with Smart Licensing-enabled products deployed in cloud-connected mode, CSSM holds a continuous record of product usage by Virtual Account — including quantity of licences in use, feature tier activated, and out of compliance status where deployment exceeds the entitlement pool. At the true-up date (typically the ELA anniversary), Cisco's account team pulls this CSSM data as the basis for the reconciliation discussion.

For products not yet migrated to Smart Licensing — legacy PAK-based Cisco software, some older Catalyst switching estates, and certain collaboration on-premise deployments — the true-up measurement relies on a combination of self-declaration by the customer and Cisco's own knowledge of the deployment from installation records, support contract data, and any on-site presence. The absence of Smart Licensing data does not reduce Cisco's ability to assert a true-up claim — it increases the ambiguity that makes settlements harder to challenge.

The true-up measurement window matters. Most Cisco ELAs measure deployment as of a specific date — the ELA anniversary — rather than as an average or peak across the year. This creates both risk and opportunity: an enterprise that reduces deployment ahead of the measurement date (by decommissioning unused products or returning licences to the pool) can legitimately reduce its true-up obligation. Conversely, a deployment spike at the measurement date that exceeds the baseline creates a true-up demand even if the spike is temporary.

Step 2: True-Up Financial Mechanics

When CSSM or self-declaration data shows deployment in excess of the ELA committed baseline, Cisco calculates a true-up charge. The rate applied to the over-deployment depends critically on which true-up model was negotiated into the original ELA:

True forward pricing: Over-deployment is priced at the same contracted rate as the original ELA commitment. This is the most favourable true-up model for the enterprise — additional units are priced consistently with the committed volume, preserving the discount level achieved at ELA signing. True forward is the standard Redress Compliance negotiating position for all Cisco ELA true-up clauses.

List price over-deployment: In ELAs that were not carefully negotiated, over-deployment units are priced at list price — significantly higher than the contracted ELA rate. An enterprise with a 40 percent ELA discount that triggers list price over-deployment provisions effectively loses the discount on every unit deployed beyond the committed baseline.

Retroactive true-up: The most aggressive true-up model, where over-deployment is calculated retroactively for the entire period since the over-deployment began. Under a retroactive model, deploying 100 extra users for 24 months generates a true-up charge for 24 months of list price fees on those 100 users. This model is rare in well-negotiated ELAs but appears in standard Cisco ELA template language if not explicitly removed.

Step 3: Running Your Own Internal Check Before Cisco Does

The enterprises that handle true-ups most successfully are those that run their own internal measurement before Cisco's account team initiates the formal process. The internal check has four components.

First, pull your CSSM Virtual Account data for every account associated with the ELA — the CSSM portal provides a licence consumption report by product and Virtual Account that mirrors what Cisco's account team will see. Second, map the CSSM consumption data against your ELA baseline document — the schedule or exhibit that defined the committed user or device population at signing. Any gap between these two documents is your estimated true-up exposure. Third, identify decommissioned or returned products that may still appear as active in CSSM because they were not formally returned to the licence pool — these can legitimately be removed from the consumption count before the true-up measurement date. Fourth, check whether any products deployed have had higher feature tiers activated than the ELA licences — Catalyst Advantage features on Essentials-licensed devices, or SecureX integrations not included in the ELA security scope, both create tier-based true-up exposure in addition to quantity over-deployment.

Negotiating True-Up Settlements

Pre-true-up reviews consistently identify over-deployment that can be remediated before the measurement date — and true-up settlement negotiations consistently produce better outcomes than simply accepting Cisco's opening demand. Our team does both.

When Cisco's account team presents a true-up demand, the negotiation has four components: first, validating the deployment measurement (CSSM data has known limitations — version tracking, duplicate device records, and Virtual Account misassignments are common sources of inflated consumption counts); second, identifying legitimate reductions (decommissioned products, returned licences, and products in non-production environments that may be contractually excludable); third, challenging the applicable rate (if the ELA true-up clause is ambiguous on whether true forward or list price rates apply to over-deployment, that ambiguity is a negotiating position); and fourth, structuring the settlement as a new commitment rather than a one-time payment (adding over-deployed users to the ELA baseline at contracted rates, with a new multi-year term, often produces a lower immediate cost than paying the true-up demand directly).

True-up window approaching? Our team pulls your CSSM data, calculates the exposure, and prepares the negotiation position before Cisco's account team arrives.

Your True-Up Number Is Already in CSSM. Run Your Own Check Before Cisco's Account Team Does.

The CSSM portal gives both sides the same data. Cisco's account team will review it before the true-up conversation. Enterprises that review it first — and prepare a remediated position, a challenge to inflated consumption records, and a structured counter-proposal — consistently achieve better settlement outcomes than those that wait for Cisco to drive the process. Our Cisco advisory team conducts pre-true-up health checks — pulling CSSM data, mapping deployment against your ELA baseline, calculating financial exposure by true-up model, and preparing the negotiation position for the settlement discussion.