Cisco's July 26, 2026 Services EA change replaced True Forward with retroactive True Up billing on hardware support, added a $200k ACV minimum, and removed Partial Commit, shifting growth risk entirely onto the buyer

Every Services EA booked or renewed on or after July 26, 2026 now carries a retroactive annual hardware support bill, a hard $200k ACV eligibility gate, and mandatory full enterprise-wide commit. Software support kept True Forward and Partial Commit, which tells you exactly where Cisco's revenue pressure sits. If your Services EA renews in the next 18 months, the decision is no longer whether to renew but whether hardware support belongs inside the EA at all.

Prepared by Redress Compliance · September 2, 2026 · Cisco advisory. Services EA and ELA renewal engagements 2024 to 2026.

Cisco moved Hardware Support (HW CX) inside the Services EA from True Forward to True Up for all new and renewed Services EA bookings dated on or after July 26, 2026. That single word change reverses the billing direction.

Under True Forward, Cisco reviewed your consumption against entitlement, adjusted the entitlement going forward, and charged nothing for the period you had already over-consumed.

Cisco marketed this for years as "the industry's only enterprise billing program that lets you grow without a retroactive, surprise bill." Under True Up, Cisco measures your hardware install base at the annual milestone date and bills the overage for the year that just closed.

Then re-bases your run rate for the year ahead.

Software Support and software licenses keep True Forward, and Cisco's FAQ states there are "currently no plans" to extend True Up to software or software support. Read that word "currently" as what it is: a statement of present intent in a marketing FAQ, not a term of your agreement.

If it matters to you, and it should, it belongs in the Offer Description or an amendment, not in a web page Cisco can revise without telling you.

Two secondary mechanics changed alongside the billing model, and both compound it. Partial Commit was removed for hardware services, leaving Full Commit as the only structure, which means enterprise-wide coverage of the relevant install base rather than the subset you selected.

Partial Commit survives for software support. And a $200,000 ACV minimum now gates HW CX inside a Services EA, applied to new sales and renewals alike, against a $100,000 TCV platform requirement for Software Support and Professional Services.

The trigger cadence also narrowed: True Up fires only at the annual milestone, whereas Cisco's EA 3.0 program terms preserved the right to run an off-cycle True Forward at the next semi-annual anniversary under "Exceptional Growth." Fewer trigger points sounds like buyer relief.

It is not, because each trigger now carries a backward-looking invoice rather than a forward-only rate reset.

Practically, the change means your renewal question is no longer "what discount." It is whether hardware support belongs inside the EA at all. Cisco's own FAQ confirms HW CX can still be bought outside an EA, which makes standalone SmartNet a live comparison rather than a threat you cannot execute.

Model both before you engage, and price the EA path with our Cisco EA cost calculator so the retroactive exposure sits in the same spreadsheet as the discount.

Work the arithmetic once and the exposure stops being abstract. Take a Services EA carrying $1.2m of hardware support ACV. In month five of the contract year, an acquisition or a refresh pushes the covered install base up 18 percent, adding roughly $216,000 of annualized hardware support.

Under True Forward, that increment cost you nothing for the remainder of the year, and the entitlement stepped up at the next review.

Under True Up, the milestone date lands seven months later, and Cisco bills approximately seven twelfths of $216,000, near $126,000, as a retroactive charge for consumption already delivered, then bills the full $216,000 forward for year two.

Same growth, same gear, roughly $126,000 of new cash in the growth year that simply did not exist under the prior model. Growth arriving in month two costs closer to $198,000 retroactively. Growth arriving in month eleven costs about $18,000. Your invoice is now a function of the calendar.

Two consequences follow. First, True Up creates a double cost event in any growth year: the arrears invoice and the re-based forward rate hit the same budget cycle, which is precisely the year an integration program is already consuming contingency.

Second, acquisition-driven jumps are the worst case, because they are lumpy, mid-year, and unbudgeted, and Full Commit means you cannot scope the acquired estate out of coverage.

Before signing, model flat, 10 percent, and 25 percent growth against your actual refresh and M&A pipeline, then negotiate two protections: a cap on the retroactive lookback (we routinely ask for 90 days rather than the full year.

And in our market experience a three to six month cap is achievable on deals above $1m ACV), and a carve-out excluding install base acquired through M&A from the first milestone measurement.

If Cisco refuses both, the standalone hardware support comparison in your Cisco negotiation strategy becomes the stronger position, not the fallback.

Cisco published the $200k ACV minimum for Hardware Support (HW CX) inside a Services EA as an eligibility gate: fall below it at new sale or renewal and you are not eligible to include hardware support in the agreement. Read the FAQ one line further and the gate dissolves.

Cisco lists five ways a below-threshold account can qualify: expand the customer scope covered by the agreement, buy additional suites, upgrade to a higher support tier, add Professional Services, or decrease discounts. Four of those five change what you receive. The fifth changes only what you pay.

A minimum that can be satisfied by raising your net price on identical coverage is not an eligibility test, it is a floor price with an eligibility label attached.

In 25 years of negotiating Cisco service constructs, this is the clearest self-documenting admission I have seen that a published \"requirement\" is a revenue target.

Treat every reference to the threshold in your renewal deck as a discount negotiation in disguise, and price the alternative: Cisco confirms that customers below $200k ACV can still buy HW CX outside the EA, at whatever standalone discount you can hold.

The trap that catches most buyers is not the renewal, it is the mid-term addition. Cisco's FAQ is explicit that an active Software EA customer who has no Services EA and wants to add Hardware Support after implementation becomes subject to the $200k threshold at that point.

A modest hardware support attach, the kind that used to be a line-item addendum, now either clears $200k ACV or gets pushed outside the agreement entirely.

Note also the separate $100k TCV platform requirement covering SW CX and Professional Services, which is a different metric (total contract value, not annual) and is assessed at the platform level, so a single deal can trip both gates on different denominators.

Before you sign anything, model the standalone path with a Cisco EA cost calculator and hold the outside-EA quote as your walk-away number. If the only way into the EA is a smaller discount, the EA has stopped being a discount vehicle.

Partial Commit is gone from hardware services in a Services EA. Cisco removed it as part of the same True Forward to True Up transition, stating the goal plainly: to ensure a minimum ACV commitment and enterprise-wide coverage where applicable. Only Full Commit remains for hardware.

Software support keeps Partial Commit, which is the same tell that runs through the entire July 26, 2026 package.

Under Full Commit you must cover, for the entire EA term, all Cisco hardware purchased through the EA, and any new hardware bought during the term automatically adds the applicable entitlement to the suite.

Cisco assesses your installed base at the start of the suite term to establish initial coverage, so the baseline is set by what Cisco's records say you own on day one, not by what you nominate.

Services-only EAs were already Full-Commit-only, with no partial commitments permitted on any suite or add-on, so if you have been running a Services-only construct you already know the shape of this. Everyone else is inheriting it.

The exposure is in the gear buyers used to leave out.

Lab and staging switches, cold spares held for RMA-independent recovery, branch and edge devices at sites scheduled for closure, and end-of-life chassis running out their last two years before refresh: these were the classic Partial Commit exclusions.

And the exclusion was rational because none of them generate a TAC case worth paying an annual support premium for.

Under Full Commit every one of them carries support cost for the full term.

We do not have a published Cisco figure for what share of a typical installed base sat outside partial commitment, and I will not invent one, but in our negotiation practice the excluded tail has routinely run to a meaningful double-digit percentage of device count.

Weighted toward low-value gear where the support-to-asset-value ratio is worst.

Inventory that tail before you model the renewal, because it is the difference between a Services EA that prices competitively and one that quietly funds support on equipment you are decommissioning.

Read the July 26, 2026 change as a disclosure document rather than a program update. Cisco applied True Up, a $200k ACV eligibility gate, and Full Commit only to hardware support.

It left software support on True Forward, left Partial Commit intact for software, and stated that there are "currently no plans" to move software licenses and software support to True Up. Three coercive mechanics landed on one side of the portfolio and none on the other.

That is not a billing harmonization exercise.

If Cisco genuinely believed True Up was the superior industry-standard model, it would have applied it uniformly, because the administrative cost of running two consumption models inside one paper agreement is real and Cisco's own commercial operations teams carry it.

The asymmetry only makes sense if the two revenue streams face different competitive conditions.

Hardware support is a contestable market and always has been. Third-party maintenance providers price SmartNet-equivalent coverage at a fraction of list, resellers hold their own spares pools, and buyers can self-insure on non-critical, end-of-sale gear that Cisco would rather not carry anyway.

Every year a buyer keeps hardware support outside the EA is a year they can benchmark it, split it across suppliers, or shrink it by decommissioning. Cisco knows the elasticity of that line item because it watches attach rates fall on aging install base. Software support is a different animal.

There is no credible third party that will ship you an IOS-XE maintenance release, hold a TAC case open against Cisco's engineering, or entitle you to a Smart Licensing renewal. It is non-substitutable, so it needs no coercion. You do not build a fence around a market nobody can leave.

Each of the three mechanics reinforces that reading.

The $200k ACV floor removes the small and midsize hardware-support buyer from the EA entirely, which is precisely the population most likely to test a third-party maintenance quote, because their footprint is small enough to migrate in one project.

Full Commit forecloses the split-estate strategy, where a buyer keeps core data center and campus switching on Cisco support and moves branch, EOL, and lab gear elsewhere.

True Up itself converts growth from a forward-priced event into a retroactive settlement, which raises the cost of any in-term reduction because the netting math runs against a full-year baseline.

Read together, the three mechanics do one job: they make it structurally harder to move hardware support out of Cisco's perimeter mid-term.

Cisco's own FAQ makes the point unintentionally. When it lists how a customer below the $200k floor can qualify at renewal, one of the named remedies is to decrease discounts.

A vendor that instructs its field to raise a customer's unit price so the customer clears an eligibility threshold is not describing an eligibility rule. It is describing a price floor with an eligibility rule wrapped around it.

Our experience across Cisco EA negotiations is that where a vendor publishes the workaround, the workaround is the plan. Treat the $200k figure as a target ACV Cisco intends to defend, not as a technical qualification.

The buyer discipline that follows is straightforward. Treat every new hardware-support restriction as evidence that the underlying service is substitutable, and price the substitute before you concede anything.

Get a live third-party maintenance quote and a reseller-brokered SmartNet quote on the same install base, at the same coverage tier, before you enter renewal. If those numbers sit meaningfully below the EA-embedded price, you have quantified leverage.

If they do not, you have confirmed the EA is genuinely competitive and you can commit with confidence. Either outcome is worth more than the discount you would have argued for blind. Our Cisco EA sizing model exists to make that comparison in weeks, not quarters.

Finally, treat "currently no plans" as a forecast with an expiry date, not a promise. Cisco used near-identical language before prior program consolidations, and the word "currently" survives precisely because it costs nothing to withdraw. Do not accept it as reassurance.

Foreclose it contractually: require that True Forward, Partial Commit, and the absence of any minimum ACV apply to software support for the full committed term regardless of subsequent Offer Description or Program Terms revisions, with the version-locked document attached as an exhibit.

If your Cisco account team resists that specific clause, they have told you the second half of this change is already scheduled.

The single most expensive operational assumption buyers make under True Up is that unplugging a device removes it from the bill. It does not. Assets remain eligible for True Up billing until they are properly delisted, and the cleanup window is 90 days.

Miss it and the decommissioned chassis you pulled in month two is still sitting in the entitlement count at the annual milestone date, priced at full coverage. Under True Forward this was an irritation, because the adjustment ran forward and a late correction cost you part of a term.

Under True Up it is a cash event, because the settlement is retroactive across the whole measurement year. Decommissioning discipline has stopped being an asset-management hygiene item and become a direct financial control with a quantifiable annual value.

Value Shift is the mechanism Cisco offers as relief, and buyers routinely overread it.

It applies residual value from under-consumed entitlement against over-consumption within the same suite, and across eligible suites, so the True Up settlement reflects net install-base change rather than gross additions.

That is genuinely useful when you are simultaneously refreshing and expanding, because the retiring generation offsets the incoming one.

But the business rules for Value Shift are unchanged by the July 2026 transition, and the critical constraint remains: it nets against over-consumption, it does not generate a cash refund. If your install base shrinks in a given year, you do not get money back. You get nothing.

The mechanism is directional, and the direction favors Cisco.

That asymmetry sets the operating cadence. Reconcile the asset register against Cisco's entitlement view monthly, not annually, and structure the reconciliation to close at least 120 days before the milestone date so the 90-day delisting window still has room.

Name a single accountable owner for delisting evidence, typically inside asset management rather than procurement, with authority to compel serial-level disposal records from field teams.

Evidence quality matters: disposal certificates, RMA records, and dated site decommission reports are what survive a dispute.

Under True Forward, the billing event was diffuse: growth got reviewed, entitlement got adjusted, and Cisco retained the right to pull an off-cycle True Forward at the next semi-annual anniversary in cases of "Exceptional Growth." Under True Up.

Cisco's own FAQ is explicit that True Up will only be triggered at the annual milestone date.

That single sentence converts a diffuse process risk into a single, schedulable cash event, and it makes the milestone date the most important negotiated variable in the agreement after unit price.

In 25 years of negotiating Cisco paper, I have watched buyers spend six weeks arguing a two-point discount delta and then accept whatever milestone the booking system defaulted to, which is usually the anniversary of the booking date. That default is set by Cisco's fiscal convenience, not yours.

Three planning rules follow. First, align the milestone against your own fiscal year end, not Cisco's July close, so the retroactive hardware support charge lands in a period where you have budget authority and a variance line to absorb it.

A milestone that falls one month into your new fiscal year gives you eleven months of runway to accrue; one that falls in your final quarter gives you a hole. Second, sequence large hardware deployments immediately after a milestone rather than immediately before.

Under True Up, hardware added in month two of a measurement year still gets billed in full at the following milestone, but you hold the cash for eleven months instead of one, and you get a full internal budget cycle to build the accrual.

If your refresh calendar is known (a campus switching refresh, a data center pod build, a branch rollout), map it against candidate milestone dates before you sign, not after.

Third, write in a documented pre-milestone reconciliation review with the account team 60 to 90 days out, with Cisco obligated to deliver the install base file it intends to bill against. This is where Cisco Services disputes get won or lost.

Reconciling a serial-level asset list against your CMDB after the invoice arrives is a credit request; reconciling it before the milestone is a correction. Demand the review as a term, not a courtesy.

The break-even math changed on July 26, 2026, and most renewal models have not caught up. Before the change, the Services EA had to beat a la carte SmartNet on discount alone.

Now it has to beat a la carte SmartNet by enough to cover three additional costs: the $200k ACV hardware support floor, forced full enterprise-wide coverage of assets you would otherwise leave unsupported or move to third-party maintenance.

And the cash cost of retroactive growth billing at each milestone.

Stop comparing discount percentages. A 42% EA discount applied to 100% of your install base loses to a 34% standalone discount applied to the 68% of assets you actually want covered. The only defensible comparison is a line-level model built on your real serial-level install base.

The profile most likely to fail this test is consistent enough that we treat it as a screening rule: a flat or declining hardware estate, a heavy end-of-life population, and total hardware support spend under roughly $400k.

At $400k, the $200k floor consumes half your spend as a commitment before you have negotiated anything, and Full Commit strips out the one lever that made the EA tolerable on a shrinking estate, which was choosing what not to cover.

Buyers in that profile should model hardware support outside the EA and keep software support inside it, where True Forward and Partial Commit both survive.

Run the numbers through a Cisco EA cost model at line level, then hand your account team the output rather than asking them to size the deal for you. The party that builds the model sets the baseline.

The Offer Description and the EA 3.0 Program Terms for End Users (EDCS-23300076 Ver 1.5) govern; the marketing page does not.

Cisco's web copy still promises "you only pay for what you use in hardware support through one annual billing" with a price lock-in feature, and the EA landing page still calls True Forward "the industry's only enterprise billing program that lets you grow without a retroactive.

Surprise bill." Neither statement survives contact with a post-July 2026 hardware support suite.

Every protection you want has to appear in the signed Offer Description, an amendment, or a mutually executed side letter that explicitly overrides the standard terms by section number.

In 25 years of negotiating this vendor, the pattern is consistent: Cisco concedes billing mechanics and reconciliation rights at the deal desk level, and concedes scope and threshold protections only when the deal is large enough to reach the regional services leadership.

Price it accordingly and open the conversation at least 120 days before your milestone date, because none of these clauses gets drafted in the final two weeks.

Redress supports this work through Cisco licensing and negotiation services, and the sizing assumptions behind each ask are easier to defend when you have modeled them first in the Cisco EA calculator.

The threshold clause matters more than its low success rate suggests, because Cisco's own FAQ lists "decrease discounts" as an acceptable way for a customer to reach the $200k ACV minimum at renewal.

That is a vendor telling you in writing that a shortfall against the minimum converts directly into a price increase. If you divest a business unit or complete a refresh that shrinks the installed base, you inherit that outcome without a threshold-relief clause.

Ask for it, document the refusal, and price the risk into your renewal reserve.

The documentary record for this change is unusually clean, which helps buyers.

The primary source is Cisco's 2026 customer FAQ, "Services EA: Transition to True Up and $200K ACV Deal Threshold," which states the transition applies to Hardware Support for all new and renewed Services EA bookings from July 26, 2026, confirms Software Support remains under True Forward.

Confirms True Up triggers only at the annual milestone date, and confirms customers below the threshold are not eligible to include hardware support in a Services EA.

The EA Service Portfolio Guide carries the $200k ACV hardware figure alongside the $100k TCV platform requirement for Software Support and Professional Services.

The EA 3.0 Program Terms for End Users (EDCS-23300076 Ver 1.5, last modified January 9, 2026) preserve Cisco's right to initiate an off-cycle True Forward at the next semi-annual anniversary for exceptional growth, which is the cadence the hardware True Up replaces.

The EA 3.0 Buying Program Offer Description (December 2025) defines Full Commit coverage obligations.

The True Forward FAQ (c67-743368) and Cisco's September 29, 2022 blog, "Cisco Enterprise Agreement: New and Improved!," are the counter-evidence: both promoted Partial Commit and the absence of retroactive billing as headline flexibility features.

Three patterns recur across Cisco program revisions, and this one runs all three at once.

First, flexibility features are withdrawn once adoption is established: Partial Commit and no-retroactive-billing were the 2022 acquisition tools, and both are gone for hardware support in 2026 now that Services EA attach rates are mature.

Second, minimums arrive as pricing levers rather than eligibility rules, which Cisco makes explicit by listing discount reduction among the sanctioned methods of reaching the threshold.

Third, buyer-facing marketing outlives the terms that supported it, and the EA landing page still selling True Forward as a retroactive-bill shield is the current example. The practical consequence is that the term sheet and the campaign page now describe different products.

Treat the published FAQ and the Offer Description as the only load-bearing documents, quote them back by name and version in negotiation, and assume any feature described only in marketing copy is available for withdrawal at your next renewal.

Related reading: True Up vs True Forward on Cisco Services EA Hardware Support: The Financial Difference, Cisco Removed Partial Commit From Services EA Hardware: How to Respond, and Cisco Services EA Minimums Explained: The $200k Hardware and $100k Software Thresholds.

Does the July 26, 2026 True Up change affect my existing Cisco Services EA?

No, not until you book new business or renew. The True Up model applies to new and renewed Services EA bookings dated on or after July 26, 2026, so an in-term agreement booked before that date continues under True Forward for hardware support until it expires.

The exposure arrives at renewal, which is why the reconciliation and modeling work should start 9 to 12 months before your end date.

Is Cisco software support also moving to True Up?

Not today. Software support and software licenses remain under the True Forward model, and Cisco's customer FAQ states that there are currently no plans to implement True Up for them.

"Currently" is not a contractual commitment, so if the software line matters to you, negotiate an express bar on extending True Up to software support and licenses for the duration of your term.

What happens if my hardware support spend is below the $200k ACV threshold at renewal?

You cannot include Hardware Support in the Services EA. Cisco's published options are to raise contract value to meet the minimum (expand scope, add suites, upgrade support tier, add Professional Services, or accept lower discounts) or move hardware support coverage outside the EA.

Buying HW CX standalone remains fully permitted, and for a flat or declining estate it is frequently the cheaper outcome.

Can I still use Partial Commit for Cisco hardware support?

No. Partial Commit was removed from hardware services in the Services EA as part of the True Up transition, leaving Full Commit only, which requires covering all Cisco hardware purchased through the EA for the whole term.

Partial Commit remains available for software support, so the practical response is to keep the software side flexible and treat hardware coverage as an all-or-nothing scope decision.

What is the 90-day delisting window and why does it matter financially?

When hardware assets are delisted, you and your partner get a 90-day window to review and clean up the delisted install base.

Assets not fully cleaned up or decommissioned inside that window remain eligible for True Up billing, meaning you can pay retroactive support on equipment you no longer operate.

Assign a named owner and run monthly asset reconciliation rather than attempting a cleanup sprint after the milestone date.

How does Value Shift reduce a True Up bill?

Value Shift applies the residual value of unused or under-consumed entitlement against over-consumed entitlement at the billing event, within the same suite or across eligible suites, so the True Up reflects the net change in the hardware install base. The business rules are unchanged under True Up.

It reduces the amount billed, but it does not generate a cash refund, so do not model it as recoverable value.

Should I renew my Services EA before July 26, 2026 to keep True Forward?

That window has closed, since bookings from July 26, 2026 onward are already governed by True Up. The remaining decision is structural: whether hardware support belongs inside the EA at all given the $200k floor, mandatory Full Commit, and retroactive growth billing.

Model the standalone SmartNet alternative at line level on your actual install base before you accept any renewal quote.