The July 26, 2026 cutover has passed, but any Services EA signed under an existing EA ID keeps True Forward for its full remaining term, which means the real decision is how to spend the 12 to 36 months of grandfathered runway you still hold.
Cisco moved Services EA hardware support to retroactive True Up billing for all new and renewed bookings from July 26, 2026, and attached a $200k ACV floor to hardware support inside the vehicle. Existing EA IDs are grandfathered for the duration of their remaining terms, including additional purchases and upgrades, so a customer with a 2028 anniversary is sitting on two more years of prospective-only billing worth roughly 15% of hardware support spend in avoided retroactive charges. The decision now is not whether to renew early, it is whether to extend, expand, or exit under the terms you already own before the grandfather clock runs out.
Prepared by Redress Compliance · September 3, 2026 · Cisco advisory practice. Services EA and EA 3.0 renewal engagements, 2024 to 2026.
Executive summary
The window to renew early and lock True Forward closed on July 25, 2026, and no amount of negotiation reopens it for a new booking.
Cisco's Enterprise Agreement Service Portfolio Guide states plainly that the True Up model applies to hardware support for all new and renewed Services EA bookings starting July 26, 2026.
So any renewal paper signed after that date carries retroactive growth billing regardless of what your account team implies.
Grandfathering is the asset you still own: existing customers under an existing EA ID retain True Forward for the duration of their remaining terms, including additional service purchases and upgrades.
That phrase "including additional service purchases and upgrades" is the operative one, because it means you can grow the estate inside the old model rather than under retroactive billing.
And on a $2M hardware support line the 15% headroom alone represents roughly $300k of consumption that never generates an invoice until the next anniversary.
The $200k ACV hardware floor ejects small and mid-size estates from the vehicle entirely, and Cisco lists "decrease discounts" as one of the four sanctioned ways to reach it.
Customers below the threshold at renewal must expand scope, buy more suites, upgrade support tier, add professional services, cut their discount, or move hardware support out of the Services EA altogether, which makes the floor a margin lever dressed as an eligibility rule.
The 90-day delisting cleanup window is the single most expensive operational trap in the new model, because delisted hardware remains True Up billable if it is not decommissioned inside that window.
Every organization we have taken through an install-base reconciliation has found stale assets in the 3 to 8% range of listed devices, and under True Up those assets now bill retroactively from the moment of overconsumption rather than prospectively from the next event.
What actually changed on July 26, 2026, and what did not
Cisco made a narrow change with wide financial consequences. Effective with bookings on and after July 26, 2026 (day one of Cisco FY2027), Hardware Support inside a Services EA moved from True Forward to True Up.
Software Support did not move: EA Software Support continues to align with software licenses and follows the True Forward process for growth.
Alongside the billing change, Cisco removed the Partial Commit option from hardware services while retaining it for software support, and attached a $200k minimum ACV threshold to HW CX plus a $100k TCV platform-level requirement covering SW CX and Professional Services.
Cisco's stated rationale is that the change "adheres to industry standards on growth capture and further aligns billing," which is vendor language for closing the gap between when you consume and when you pay.
Read the two models side by side before you accept any renewal paper, because the difference is not administrative, it is the timing of cash and the direction of the exposure. Our fuller breakdown of the mechanics sits in the True Up versus True Forward financial comparison.
| Mechanic | True Forward (grandfathered HW, all SW) | True Up (new and renewed HW bookings) |
|---|---|---|
| Billing direction | Prospective only, from the True Forward event forward through the remainder of the Suite Term | Retroactive, charged from the moment of overconsumption |
| Trigger point | Annual True Forward event, with off-cycle rights reserved for Exceptional Growth at the next semi-annual anniversary | Annual milestone date only |
| Growth headroom | Documented headroom before a billing event (Cisco materials cite 15%, some suite guides cite 20%: confirm per suite) | Consumption above entitlement is billable back to the date it occurred |
| Commit options | Full Commit and Partial Commit | Full Commit only for hardware; Partial Commit retained for software |
| Minimum threshold | No HW CX ACV floor under legacy terms | $200k ACV floor on HW CX; $100k TCV platform requirement for SW CX and Professional Services |
The table cannot show the trigger condition, and the trigger condition is where your leverage lives. Cisco enforces the $200k floor only when at least one HW CX suite appears in the proposal.
That is not a customer size test, it is a proposal composition test, which makes it a design lever rather than a fixed eligibility rule. Structure the deal without an HW CX suite and the floor does not attach, because HW CX remains purchasable outside the EA vehicle.
The four remedies Cisco lists for customers who fall short of the floor at renewal deserve attention: expand scope, buy more suites, upgrade to a higher support tier, add Professional Services, or decrease discounts. Cisco itself names discount reduction as a legitimate path to hitting $200k.
That is a margin lever presented as a compliance requirement, and you should treat it as such at the table.
Who is still grandfathered and how long the runway runs
Grandfathering attaches at the EA ID level, not at the individual suite or purchase order. Cisco's transition FAQ is explicit: existing customers under an existing EA ID retain the True Forward model for the duration of their remaining terms, including any additional service purchases and upgrades.
Read that clause twice. Additional purchases and upgrades made under a grandfathered EA ID inherit prospective-only billing. That converts your remaining term into a purchasing window, not merely a billing arrangement you happen to still hold.
Computing your runway is arithmetic, not interpretation. Start from the initial EA 3.0 order date, add the Suite Term, and account for automatic co-termination: suites added mid-term co-terminate to the original anniversary rather than extending it.
If you signed a five-year EA 3.0 in October 2024, your runway ends October 2029 regardless of what you bought in 2026. If you added a Services suite in 2025 under a 2023 EA ID, that addition dies with the parent term.
Pull the EA ID, the initial order date, the term length, and the anniversary date from your partner before you model anything, and reconcile against your annual milestone date, because that date governs when any True Up would fire once you convert.
Three cohorts, three different playbooks. 2027 anniversaries have roughly 12 months and should be moving now: front-load hardware support upgrades and refresh-driven additions into the grandfathered window, and model the $200k floor exposure before the renewal proposal lands. 2028 anniversaries hold two years of prospective-only billing, worth approximately 15% of hardware support spend in avoided retroactive charges on the growth you would have absorbed under headroom.
Use that time to reconcile install base and decide whether HW CX belongs inside the vehicle at all. 2029 anniversaries have the luxury of watching how Cisco enforces the 90-day delisting cleanup window on the first wave before committing to a structure.
One caution that applies to all three. Grandfathering protects the EA ID, so any restructure that Cisco or your partner books as a new agreement, including a mid-term consolidation of multiple EA IDs into one, forfeits the protection.
Get written confirmation that any amendment preserves the original EA ID before you sign it.
Right size your Cisco ELA and neutralize the true up
The buyer side brief for a Cisco Enterprise License Agreement: right size the suite, neutralize the true up, and lock the renewal before you sign.
Get the white paper →The grandfather clause is a purchasing budget, not a grace period
Every customer we have walked through the July 26 change reads the grandfather language the same way at first: relief.
Cisco's own FAQ says existing EA IDs retain True Forward "for the duration of their remaining terms, including any additional service purchases and upgrades," and the natural reaction is to file that under nothing changes yet and move on to the next fire.
That is the wrong reading, and it is expensive. The clause does not say your current install base stays on True Forward. It says additional purchases and upgrades under that EA ID stay on True Forward. Cisco did not grant you a stay of execution.
Cisco granted you a time-boxed right to buy growth at prospective-only pricing, and that right expires on your anniversary whether or not you used it.
Treat it as a budget line, because that is what it functionally is.
If your remaining term is 24 months and your annual hardware support ACV is $1.4M, the grandfathered runway is not an abstraction, it is roughly 15% of consumption growth per True Forward event that you can absorb without a retroactive charge.
Plus the certainty that anything you do trigger is billed forward from the event date rather than backward to the moment of overconsumption.
Model it as spend authority with an expiry date. The question stops being "should we defer the refresh to next fiscal" and becomes "what does deferring past the anniversary cost us in retroactive exposure we could have avoided."
The software carve-out tells you what this is really about. If Cisco were aligning to industry billing convention, as the customer FAQ claims, Software Support would have moved too. It did not. Software Support stays on True Forward and continues to align with the software licenses.
Only hardware moved. Hardware is where install-base drift lives: switches added in a branch buildout, an acquired site's estate absorbed into the contract, chassis upgraded mid-term, none of it visible in a Smart Licensing dashboard the way software consumption is.
Cisco is not standardizing billing mechanics. Cisco is closing a revenue leak specific to physical assets it cannot meter in real time, and it is closing it by shifting the reconciliation burden and the interest-free float onto you.
Test the 15% headroom against a real refresh cycle rather than a spreadsheet. Most enterprise access-layer refreshes we see run 20 to 35% of the estate in a single wave, which blows straight through the allowance in one event.
Under True Forward that overage is invoiced prospectively through the remainder of the suite term and your entitlement adjusts going forward.
Under True Up the same wave is billed from the day the assets went live, and if that was nine months before your milestone date, you are writing a check for nine months of coverage you already consumed.
The delta is not theoretical; it is the difference between paying for 15 months of a 24-month exposure and paying for all 24. Our own analysis of the two billing models on hardware support puts that gap at roughly 15% of hardware support spend across a typical term.
The counterargument deserves a straight answer: pre-buying coverage on hardware you have not deployed is dead capital. True. Nobody should book support on chassis sitting in a distribution center for eleven months. But that is not the move.
The move is to pull forward the deployments already funded and already scheduled for the quarter after your anniversary, so the assets land inside the grandfathered term instead of just outside it. You are not inventing capex.
You are re-sequencing capex you already approved so it lands on the favorable side of a billing rule. Where the deployment genuinely cannot move, buy the coverage in the last True Forward event before the anniversary, because entitlement bought under a grandfathered EA ID is itself grandfathered.
Reduce it to the asymmetry and the decision writes itself. Prospective billing errs in the buyer's favor: Cisco absorbs the gap between when you overconsumed and when it noticed.
Retroactive billing errs in Cisco's: you absorb it, with no discovery discount and no negotiation once the milestone report is generated. Every asset you onboard before your anniversary sits on one side of that line. Every asset you onboard after sits on the other.
There is no neutral position and no partial credit.
The $200k floor and the four forced remedies
The threshold only bites when at least one Hardware Support suite is in the proposal, and it bites hard: below $200k ACV, hardware is simply not eligible to sit inside the Services EA. Cisco's FAQ lists four sanctioned ways back over the line, and they are not equivalent.
Expanding scope and upgrading tier buy you something. Adding Professional Services buys you something if you had PS demand anyway. Decreasing discounts buys you nothing.
That fourth remedy is Cisco naming margin recovery as a compliance path, and it is the only one on the list where you pay more for the identical entitlement. Refuse it in writing and make your partner document the alternative.
The escape hatch is real: hardware support can be purchased outside the EA entirely, as standalone SmartNet or Full Coverage, and Full Coverage supports quarterly, semi-annual, and annual billing while the Services EA offers a single annual cycle.
For a customer near the floor, that cash-flow flexibility often outweighs the EA discount.
| Path to compliance | What it costs you | Verdict |
|---|---|---|
| Expand scope (add suites) | Real incremental ACV, but tied to entitlement you keep | Viable if demand is genuine |
| Upgrade support tier | Higher unit rate, higher SLA delivered | Viable if the SLA is needed |
| Add Professional Services | Counts toward floor via the separate $100k TCV platform requirement | Viable only against funded PS scope |
| Decrease discounts | Pure margin transfer, zero added entitlement | Refuse outright |
| Move hardware out to SmartNet or Full Coverage | Lose EA discount, gain quarterly or semi-annual billing | Often the strongest below $200k |
The four remedies are presented as a menu, but three of them require you to want something you did not previously want, and the fourth just raises the price. That structure exists because Cisco would rather you buy your way over the floor than exit the vehicle.
Model the exit first, not last: price standalone hardware support against the EA-discounted number and compare total three-year cash outlay, not headline discount percentage.
Remember that Partial Commit is gone from hardware inside the Services EA, so you cannot shrink your way to a workable number. Full Commit is the only option, which means the floor and the commitment structure now push in the same direction.
Read the $200k and $100k threshold mechanics before your partner builds the proposal, not after.
Coverage gaps that survive the transition and now cost more
Several rules did not change on July 26, but their cost of failure did.
The most dangerous is the delisting window: under Cisco's Services EA FAQ, delisted hardware assets remain eligible for True Up billing for 90 days from the delisting action, and any asset not actually decommissioned inside that window stays billable.
Under True Forward, a sloppy install base cost you a slightly inflated prospective run rate from the next milestone.
Under True Up, the same sloppiness is billed backward to the moment of overconsumption, so a 400-unit decommissioning project that slips one quarter converts an operational delay into a retroactive invoice line.
Treat the 90-day window as a hard project gate with a named owner, not an administrative courtesy, and build the reconciliation calendar against your Services EA True Up milestone date rather than your fiscal calendar.
Three more traps deserve budget lines.
First, EA 3.0 Program Terms give Cisco the right to initiate an off-cycle True Forward at the next semi-annual anniversary under Exceptional Growth, which means even grandfathered customers do not own a clean 12-month billing cycle if they absorb an acquisition mid-term.
Second, Cross Suite Value Shift, the mechanism most buyers assume will rescue a mis-sized suite, requires at least 60 days advance notice to the EA Authorized Partner and only works where the Full Commit suites were bought from the same partner, at the same time, for the same term.
On the initial EA order.
Miss any one of those four conditions and the flexibility does not exist. Third, and most misunderstood, licenses eligible for Cross Suite Value Shift may not be shifted into Services Suites, so software headroom cannot subsidize a hardware support shortfall.
Finally, install-base reconciliation help is tiered: below $25M in Global Price List hardware total you get a pooled Cisco Asset Management resource through the Portfolio Activation Specialist, not a dedicated one.
Assume that pooled resource is not accountable to your timeline and staff the reconciliation internally.
What the deal file shows: recurring patterns across 2024 to 2026 renewals
Cisco's Services EA FAQ states 15% growth headroom before charges, while third-party 2026 guidance cites a 20% allowance on many suites, so the only number that binds you is the one printed in your own Program Guide.
Cisco raised hardware roughly 3.4% in September 2025 and technical services by a comparable 3.4% in October 2025, each with 30-day quote protection, meaning quote timing is worth about a third of a point per month of delay.
The document set that governs your position is small and knowable: the EA Service Portfolio Guide, the EA 3.0 Program Terms and Program Guide, and the Services EA customer FAQ on the True Up and $200k ACV threshold transition.
In our experience across 2024 to 2026 renewals, buyers argue from the FAQ while Cisco enforces the Program Terms, and the two do not always align. Demand all three as attachments to the order form. The second recurring pattern is partner lock-in.
EA 3.0 permits each portfolio to be sourced through a different partner, but the Services portfolio must be bought through the same partner as the product portfolio, and every True Forward entitlement increase returns to that same partner.
That is a compounding annuity for the reseller and a shrinking option set for you: once the initial order is placed, competitive tension on services growth is gone for the term.
The third pattern is that price actions and cutovers cluster around Cisco's fiscal boundary, and 30-day quote protection is the only reliable hedge, which argues for locking quotes before September rather than negotiating through it.
Practically, that means your negotiation position rests on documents, not conversations.
Pull your Program Guide, confirm the per-suite headroom in writing, and score the partner concentration before you extend, using the Cisco renewal leverage scorecard to quantify how much of your remaining leverage is already committed.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
Your first five moves
- Get grandfather status confirmed in writing by Cisco, not your partner. Pull the EA ID, the suite term end date, and the anniversary date, and require a Cisco-sourced statement that the existing EA ID retains True Forward for the remaining term including additional service purchases and upgrades; assign this to the contract owner and close it within 10 business days, because partner-issued quotes are not contractual confirmation.
- Run install-base reconciliation before the next milestone, not after it. Reconcile serial-level hardware entitlement against deployed assets now, and if your Global Price List hardware total is under $25M, formally request the pooled Cisco Asset Management resource through the Portfolio Activation Specialist; in our deal experience, first-pass reconciliation on a mid-size estate surfaces 5 to 12% of assets that are decommissioned, duplicated, or wrongly tiered.
- Model the $200k hardware ACV floor against standalone renewal today. Price HW CX inside the vehicle versus outside it, and treat Cisco's own listed remedy of "decrease discounts" as what it is: a margin lever dressed as compliance, covered in our breakdown of the $200k and $100k Services EA thresholds.
- Pull planned hardware coverage forward into the grandfathered term. Any refresh, tier upgrade, or acquisition-driven addition landing inside the current EA ID is billed prospectively; the same purchase after term end is billed retroactively from the moment of overconsumption, a difference worth roughly 15% of hardware support spend.
- Set the 60-day and 90-day calendar triggers now. Cross Suite Value Shift requires 60 days advance notice to your EA Authorized Partner at the annual event, and delisted assets stay billable if not decommissioned within 90 days; put both on the finance calendar against your True Up milestone date.
Frequently asked questions
Can I still renew my Cisco Services EA early to lock in True Forward?
No. Cisco's Enterprise Agreement Service Portfolio Guide applies the True Up model to hardware support for all new and renewed Services EA bookings starting July 26, 2026, which was day one of Cisco fiscal 2027. A renewal signed today is a new booking and lands under True Up.
What you can still do is exploit the grandfather on your existing EA ID for its remaining term.
Does grandfathering cover new purchases I make during the remaining term?
Yes, and this is the most valuable line in Cisco's own customer FAQ. Existing EA customers under an existing EA ID retain the True Forward model for the duration of their remaining terms, including any additional service purchases and upgrades.
Get that confirmation in writing tied to your specific EA ID before you place growth orders, because partner-level restatements of the rule have been inconsistent.
What is the real financial difference between True Forward and True Up?
True Forward reviews consumption against entitlement at the True Forward event and invoices the increase prospectively through the remainder of the suite term. True Up charges from the moment of overconsumption, meaning retroactive billing back to when you exceeded entitlement.
On a mid-size hardware support estate that difference is typically several months of back-billed coverage per growth event, plus the loss of the 15% headroom that absorbed drift without any invoice at all.
What happens if my hardware support falls below the $200k ACV threshold?
You lose eligibility to include hardware support in the Services EA. Cisco's four remedies are to expand scope or add suites, upgrade to a higher support tier, add professional services, or decrease your discount, and the fourth is a straight margin grab you should refuse.
The fifth option Cisco also documents is buying hardware support outside the EA entirely, which is often cheaper and gives you quarterly or semi-annual billing instead of one annual cycle.
Is the growth allowance 15% or 20%?
Cisco's Services EA FAQ cites 15% for exceeding licensed amounts without immediate charges, while at least one 2026 partner guide cites 20% on many suites.
The allowance is set per suite in your Program Guide, so treat any single published number as unverified until you have pulled your own suite-level terms. Ask your account team to identify the allowance for each suite in writing before you model growth.
What is the 90-day delisting window and why does it matter now?
When you delist hardware assets, Cisco gives you and your partner 90 days to review and clean up the delisted install base. Assets not decommissioned inside that window remain eligible for True Up billing.
Under prospective billing this was an annoyance; under retroactive billing it converts stale asset records directly into back-billed charges, so it needs a calendared owner and a documented reconciliation.
Can I move my Services EA to a different reseller to create competition?
Not mid-term, and only partially at renewal.
EA 3.0 allows different partners per portfolio, but the services portfolio must be purchased through the same partner as the product portfolio, and any entitlement increase arising from a True Forward must be bought through the partner that sold you that suite.
Your competitive event is the renewal itself, which means partner selection has to be decided before the initial order, not after.
