Cisco ELA True Forward: How Billing Works and How to Negotiate It

True Forward vs Traditional True-Up: The Critical Distinction

To understand why Cisco's True Forward matters commercially, you first need to understand what it replaced. In traditional enterprise software agreements — Oracle, SAP, Microsoft Volume Licensing — when you deploy more licences than you have purchased, the vendor typically issues a "true-up" that bills you retroactively for the over-deployment from the date it occurred. If you over-deployed in January and the true-up occurs in December, you owe 11 months of retroactive overage charges — often at list price, with no discount applied.

Cisco's True Forward mechanism works differently. When your consumption during the ELA period exceeds your committed licence quantity, Cisco does not charge you retroactively. Instead, at the next scheduled True Forward event, your licensed quantity is adjusted upward to reflect your actual consumption level, and you pay the incremental cost prospectively — from the True Forward event date forward to the ELA expiry. You do not pay for the past period of overage that has already elapsed.

This is a materially more favourable structure for enterprise buyers. For a fast-growing organisation that adds 200 users to its Webex Collaboration deployment in Q1 of year two, a traditional true-up would charge for those 200 users for the entire remaining ELA term from Q1. Cisco's True Forward charges only from the True Forward event date — typically the annual anniversary — forward.

How the True Forward Calculation Works

Step 1: Overage Review

At each True Forward event (typically annually for Full Commit suites), Cisco reviews your actual consumption against your committed licence quantity using CSSM telemetry data. The consumption figure Cisco uses is determined by the peak usage recorded in CSSM during the review period. This is an important nuance: if your peak consumption during the year exceeded your committed quantity even temporarily — perhaps during a one-week period of elevated deployment — that peak could become the basis for the True Forward adjustment. Organisations running CSSM monitoring should track peak consumption throughout the year, not just at the True Forward date.

Step 2: Value Shift Application

Before any cash payment is calculated, ELA 3.0 applies the intra-suite value shift mechanism. If within the same suite you have both unused licence entitlement in one product and overage in another product, the residual value of the unused entitlement is applied against the overage cost. This calculation occurs automatically — Cisco's commercial team calculates the value shift in the True Forward settlement proposal, and the customer does not need to initiate it. However, verifying that the value shift has been correctly calculated requires understanding your consumption position for every product within each suite.

Step 3: Overage Pricing

Any net overage after value shift application is priced at the rate specified in the ELA. Under standard ELA 3.0 terms, overage quantities at True Forward events may be priced at Cisco's then-current list price, adjusted by a fixed discount applicable to overages. Critically, if you have not negotiated a "lock to contract rate" provision — requiring that True Forward overages are priced at your original ELA per-unit rate rather than then-current list — your True Forward cost for overages may reflect list price increases that occurred after your ELA was signed. For a three-year ELA with annual Cisco list price increases of 3 to 5 percent, the year-three True Forward pricing for overages could be meaningfully higher than your original ELA rate.

Step 4: Remaining Term Proration

True Forward overage costs are prorated for the remaining ELA term. If a True Forward event occurs at the end of year two in a three-year ELA, you pay for one year of incremental licences (from the True Forward date to the ELA end). If the True Forward event occurs at the end of year one, you pay for two years. The prospective billing mechanic means earlier True Forward events result in higher cash payments than later ones — an incentive to manage your consumption carefully in the first half of the ELA term.

The Five True Forward Negotiation Provisions That Matter

1. Lock Overage Pricing to Your Contract Rate

The most valuable True Forward negotiation provision is a contractual requirement that any overage quantities added through a True Forward event are priced at your original ELA per-unit rate — not at Cisco's then-current list price. This "contract rate lock" ensures that your consumption growth costs are predictable and consistent with the economics you evaluated when you signed the ELA. Without this provision, Cisco can price True Forward overages at its current list, which may be 5 to 15 percent higher than your ELA rate by year three. At high volume, this difference is financially material.

2. Negotiate True Forward Event Timing

True Forward events are scheduled in the ELA documentation and are negotiable. Aligning True Forward events to your internal budget cycle — typically your fiscal year end — allows you to plan for and approve True Forward costs within normal budget processes rather than as unplanned in-year charges. Misalignment between Cisco's scheduled True Forward dates and your budget approval cycle creates internal friction and may force acceptance of True Forward charges that weren't anticipated in your annual IT budget.

3. Define the Consumption Measurement Methodology

The standard ELA terms measure consumption using CSSM data, typically based on peak consumption during the review period. Negotiate the specific measurement methodology: is consumption measured as peak, average, or end-of-period quantity? A "peak during period" measurement is the most unfavourable for buyers because it captures temporary deployment spikes that may not reflect steady-state consumption. An "end-of-period" or "average during period" measurement is more representative of actual utilisation and typically results in lower True Forward exposure.

4. True Forward Cap Provision

Some large enterprise ELA negotiations achieve a True Forward cap provision — a maximum annual increase in the committed quantity that can be triggered by a True Forward event, expressed as a percentage of the original commitment (for example, 15 or 20 percent per year). This provision does not eliminate True Forward payments but limits the annual exposure to a predictable range. Combined with the growth allowance already built into the Collaboration and Security suites, a True Forward cap creates a robust ceiling on annual licence cost escalation from organic growth.

5. Advance True Forward Notice Period

Negotiate a minimum advance notice period before each True Forward billing event — typically 60 to 90 days. This notice period allows your team to review Cisco's consumption data, validate the calculation, apply any corrections to CSSM data that may be inaccurate, and prepare internal budget approvals for the True Forward charge. Without a defined notice period, Cisco may present a True Forward invoice with a 30-day payment requirement, leaving inadequate time for review and approval.

Managing True Forward Events In-Term

Effective True Forward management requires ongoing attention throughout the ELA term — not just at negotiation. The following practices reduce True Forward exposure and ensure that each True Forward event is managed from a position of preparation.

Quarterly CSSM Consumption Reviews

Pull CSSM consumption data at least quarterly and compare actual deployment against your committed licence quantities for each product within each suite. Identify products approaching their committed quantity and assess whether the trajectory suggests a True Forward overage at the next event. Early identification of overage risk allows you to take action — reducing unnecessary deployment, eliminating over-provisioning, or proactively discussing with Cisco's commercial team — rather than discovering overage only when the True Forward invoice arrives. Our Cisco Smart Licensing guide covers CSSM reporting and consumption monitoring in detail.

Pre-True Forward Audit

One quarter before each scheduled True Forward event, conduct an independent consumption audit: pull your own CSSM consumption report, calculate your net overage position after value shift, and estimate the True Forward charge using your ELA overage pricing. Compare this calculation against Cisco's subsequent True Forward proposal — discrepancies may indicate CSSM data errors (incorrectly registered devices, test environments counted as production, decommissioned systems still reporting) that should be corrected before the True Forward settlement is finalised. For comprehensive guidance on the annual reconciliation process, our Cisco ELA true-up guide provides the procedural framework.

Decommission Aggressively Before True Forward Dates

In the 60 to 90 days before a True Forward event, proactively decommission any Cisco deployments that are inactive or redundant — deregistering devices from CSSM, cleaning up test environment licences, and removing access for departed users in collaboration and security suite products. Consumption data that is removed from CSSM before the True Forward measurement date cannot be used to establish your overage baseline. This is not gaming the system — it is accurate licence management, and it is explicitly encouraged by the prospective billing model that True Forward creates.

True Forward and CSSM Telemetry: The Preparation Imperative

Cisco's CSSM telemetry gives Cisco's commercial team real-time visibility into your ELA consumption across all registered devices and software instances. Before any True Forward conversation starts, Cisco knows your deployment position. The preparation imperative for enterprise buyers is to match Cisco's information — to know what CSSM shows before Cisco presents the True Forward proposal.

Organisations that enter True Forward discussions having never reviewed their own CSSM data are at a fundamental informational disadvantage. Cisco may present overage numbers that include incorrectly registered devices, decommissioned systems that were never removed from CSSM, or test environments that should not count toward production entitlement. Without your own CSSM analysis, you have no basis to challenge these figures.

The broader context of Cisco's CSSM telemetry and what it means for enterprise commercial conversations is covered in the Cisco ELA negotiation playbook, specifically in the section on CSSM telemetry and the commercial information asymmetry it creates.

True Forward Checklist: Before Your Next True Forward Event

1. Pull CSSM consumption data for all products in all ELA suites 90 days before the scheduled True Forward event date.
2. Identify peak consumption during the review period — compare to committed quantities for each product.
3. Decommission inactive devices, test environments, and former-user access from CSSM before the measurement date.
4. Calculate your net overage position after intra-suite value shift for each suite.
5. Estimate the True Forward charge using your ELA overage pricing provisions.
6. Confirm the True Forward event date with Cisco's commercial team and request their consumption data for comparison.
7. Review Cisco's True Forward proposal against your independent calculation — raise discrepancies before accepting.
8. Process the agreed True Forward settlement within your budget approval process, using the advance notice period you negotiated.

For the full context on how True Forward fits within the broader Cisco ELA 3.0 commercial structure, see the ELA 3.0 guide covering what is new in the current programme, and for Meraki-specific True Forward considerations our Cisco Meraki licensing guide covers how Meraki dashboard licences interact with the ELA True Forward framework. For security suite-specific True Forward patterns, our Cisco security licensing guide provides product-level consumption benchmarks.

About the Author

Fredrik Filipsson is Co-Founder of Redress Compliance, with 20+ years of enterprise software licensing experience across 500+ client engagements. Fredrik has structured True Forward provisions across 100+ Cisco ELA negotiations and supported enterprises through dozens of in-term True Forward events. Recognised by Gartner as a leading independent adviser in enterprise software procurement. Connect on LinkedIn.