Cisco's switch to True Up on Services EA hardware support converts a $0 first-year growth bill into up to 12 months of retroactive support charges on every net-new device, calculated from ship date at install-base list price

Under True Forward, hardware added mid-term cost nothing until the next anniversary, then billed forward only. Under True Up, effective July 26, 2026 for all new and renewed Services EA bookings, the same device accrues charges from the day it shipped and lands as a single lumpy invoice at the annual milestone. Because hardware services were never eligible for the 15% growth allowance, the meter starts at device one, and your only offset is a disciplined decommission and delisting process inside a 90-day window.

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

The two models share a vocabulary and almost nothing else. Under True Forward, Cisco measures your consumption against entitlement at the anniversary, and if you are over, you pay the difference going forward for the balance of the term.

The device you shipped in month two of the milestone year rode free for ten months. Under True Up, the same measurement happens at the same annual milestone date, but Cisco bills the growth retroactively from the moment consumption began.

Cisco's own FAQ language is unambiguous on this: True Forward customers "grow without retroactive billing and pay for growth going forward," while under True Up "customers pay retroactively for growth at the annual milestone date." The trigger event did not move. The billable start date did.

For hardware, consumption is defined at ship date for a new asset and at contract-add date for an existing asset, so the clock starts before the box is racked, before it is configured, and before it carries a single production packet. Two operational facts amplify the swing.

First, Services EA supports only one annual billing cycle, whereas Services Full Coverage supports quarterly, semi-annual, and annual, so there is no smoothing mechanism inside the EA construct.

Second, Pure Consumption is calculated on install base list price, not on the net price you negotiated for the commit, which means the retroactive tranche is priced on a basis you never signed off on.

Both event types are administered in Enterprise Agreement Workspace (EAWS) with real-time consumption reporting at software.cisco.com at product and suite level by enrollment, so the data to model this exists before the invoice does. Most buyers never pull it.

Our Services EA True Up guide walks the enrollment-level view in more detail.

The bundled commercial changes compound the mechanical one. Partial Commit has been removed from hardware services entirely, so you can no longer underwrite a fraction of the install base and let Pure Consumption absorb the rest at a rate you tolerate.

Full Commit is the only path, and Full Commit carries not-to-exceed price protection, which is now your primary defensive asset rather than a nice-to-have.

Confirm in writing that the legacy ceiling language, where the maximum price is the original price set at the time of the original order, survives verbatim into the True Up paperwork.

Model this in a spreadsheet before signature, not after the first milestone. The arithmetic is four steps. Take your planned net-new hardware for the milestone year by tranche.

Price each tranche at install base list for the matching HW CX suite, not at your net, because Pure Consumption is calculated on list. Weight each tranche by months elapsed from ship date to the milestone date, divided by twelve.

Subtract only decommissions you have validated and delisted inside the 90-day window. What falls out is your retroactive charge, and under True Forward the same inputs produced zero. The timing weight is the whole game. A device shipped one month after the milestone carries an 11/12 weight.

The same device shipped one month before the milestone carries 1/12. Same box, same suite, same list price, roughly eleven times the first-year charge. Size the suite basis with our Cisco EA cost calculator before you plug in the timing weights.

Two disciplines make the model defensible. First, hold the list-price basis even when your account team quotes net, because the gap between the two is your discount and Pure Consumption does not honor it.

Second, treat decommissions as unproven until delisted and confirmed in EAWS, since delisted assets remain eligible for True Up billing after the 90-day window closes. Build the model with zero assumed decommission credit, then add credit back only for assets with a delisting confirmation.

That is the number you negotiate against.

Read Cisco's own True Forward FAQ language and you will find the promise in plain text: grow without a retroactive, surprise bill. That was not an accounting footnote buried in an offer description.

It was the headline differentiator the account team used to move you off standalone SmartNet renewals and into a Services EA in the first place, and in twenty-five years of sitting across from this vendor I have never seen a Cisco EA pitch deck that did not lead with it.

Cisco has now reversed the single feature that justified the program's existence for hardware support, and the stated rationale, "adherence to industry standards on growth capture," is a rationale about Cisco's revenue recognition, not about your operating model.

Name that plainly in your first renewal meeting, in writing, and make the account team explain what the customer receives in exchange.

The reversal does not arrive alone, and that is what turns an irritation into a structural problem. True Up on hardware support lands at the same moment Partial Commit is removed from hardware services, leaving Full Commit as the only path, while software support keeps Partial Commit.

Stack those two facts against the requirement to cover the estate and the picture is unambiguous: a program sold as flexibility, pay for what you consume, adjust as you grow, has been converted into a commitment program where the whole install base is committed.

Growth is billed backward from ship date, and the mechanism that let you commit only part of the estate is gone.

You are being asked to accept more obligation and less optionality on the same contract paper.

The most useful admission in Cisco's own FAQ is the one buried near the bottom: Cisco acknowledges existing operational pain points and says it will prioritize a capabilities roadmap. Translate that.

A vendor that intends to bill you retroactively, per device, from ship date, at install-base list price, is telling you in advance that the tooling and data supporting that calculation are not yet ready.

Ship-date-driven retroactive billing is only as accurate as the install-base record, and Cisco has conceded the record needs work. That is your audit-defense lever and it is a strong one.

Every True Up invoice should be treated as a vendor assertion requiring device-level proof: serial number, ship date, contract add date, and current entitlement.

Insist the agreement carries a dispute and re-billing clause tied to install-base accuracy, and put the burden of substantiation on Cisco, not on your asset team.

The $200,000 net ACV threshold on hardware support is not an administrative floor, it is segmentation.

Cisco has decided that mid-market hardware support does not belong in an EA and should sit back in standalone HW CX or SmartNet, where discounting is transactional and the vendor keeps pricing power at each renewal.

The cruelest detail is that the threshold is calculated on net ACV after discounts, so a well-negotiated deal can disqualify itself.

Buyers sitting between roughly $150,000 and $250,000 face a genuinely perverse choice: expand scope, buy suites you do not need, upgrade a support tier, add professional services, or accept a shallower discount to stay inside the program that just took your True Forward protection away.

My read for most organizations in that band is to model the standalone path seriously before conceding anything, because the arithmetic frequently favors leaving. Use a Cisco EA suite sizing model to price both paths, then decide with numbers rather than with the account team's framing.

Then there is the grandfathering rule, which is the most valuable single fact in the entire change: existing customers under an existing EA ID keep True Forward for the remainder of their terms, including additional service purchases and upgrades.

That converts your current EA ID into an asset with a measurable shelf life. Every month of remaining term is a month of $0 first-year growth billing on net-new hardware.

Any co-term, consolidation, restructure, or "let's just refresh the paper early" conversation is a request to surrender that asset, and it should carry a price.

Before you sign anything that touches the EA ID, read the mechanics in our Services EA True Up hardware support guide and quantify what the grandfathered term is worth in retroactive charges avoided.

Finally, the roadmap. Cisco states there are currently no plans to implement True Up for software licenses and software support. That is language, not a commitment, and it is precisely the kind of language that preceded this hardware change.

"No current plans" is a statement about intent on a given day, revocable by the next offer description update.

If software support and licenses matter to your cost base, and for most enterprises they matter more than hardware, then paper it: True Forward for software, named, for the full term, with any model change requiring your written consent rather than a portal notice.

A vendor that has just reversed its flagship promise on one line item has forfeited the benefit of the doubt on the others.

The one piece of good news is that Value Shift business rules are unchanged under True Up, and Cisco's FAQ is explicit that both newly added hardware and decommissioned hardware are considered, so the adjustment reflects the net change in the hardware install base.

That makes decommissioning your primary and, realistically, your only structural offset. Under True Forward the discipline was optional because growth cost nothing in the year it happened.

Under True Up, every device you retire and correctly remove from the install base directly reduces a retroactive invoice you will otherwise pay from ship date. Asset hygiene stopped being a housekeeping task and became a line item on the finance forecast.

The trap sits in the 90-day delisting window. Cisco's own language is that delisted hardware assets remain eligible for True Up billing after the 90-day delisting period, and that customers and partners get 90 days to review and clean up the delisted install base. Read that twice.

Miss the review and the asset stays billable, which means you pay retroactive hardware support on gear that left the building. This is where most organizations will lose money in year one, not on the growth itself but on the failure to close out retirements inside a window nobody owns.

Assign that ownership by name, tie it to your Services EA True Up hardware support process, and calendar it as a hard quarterly gate rather than an annual scramble before the milestone date.

The hard boundary is the no-true-down floor. Cisco's Buying Program Offer Description states that during the Suite Term the payment obligation will not decrease below the commitment established by the Initial Services Entitlement. Decommissions therefore offset growth but never cut the floor.

That has a precise consequence for how you set the deal: the Initial Services Entitlement is the number you are stuck with.

So understating it at signature is worth more than any discount you win on top of it, because savings above the floor are recoverable through Value Shift and savings below the floor do not exist.

Operationally, translate this into a quarterly rhythm rather than an annual reconciliation: pull the EAWS install-base report every quarter, reconcile it against your CMDB and your disposal records, file delistings inside the window, and log the serial numbers you expect to see removed.

Then hold the evidence. When the True Up invoice arrives at the annual milestone, you are checking Cisco's arithmetic against your own record instead of accepting it.

Across Services EA renewals and True Forward reconciliations we worked from 2024 into 2026, plus the three documents that now govern this (the Cisco Services EA customer FAQ on the True Up transition, the EA Service Portfolio Guide 2026.

And the Buying Program Offer Description for the Services Portfolio dated December 12, 2025), the same four defects show up in the paperwork.

Pattern one: the account team quotes the growth allowance as if it cushions hardware. It does not. The Offer Description is explicit that no services on hardware are eligible for growth allowance, and the 15% cushion attaches to licensed software amounts.

Every device is billable from unit one, and a proposal modeled on a 15% free band understates the milestone invoice by whatever your net-new hardware run rate happens to be. Pattern two: not-to-exceed language on Full Commit that omits the legacy price ceiling.

The old True Forward FAQ set the maximum True Forward price at the original price the EA partner set at the time of the original order.

NTE alone caps increases but does not pin the unit basis to your original partner price, and in our experience that gap is where install-base list pricing quietly replaces your negotiated rate. Pattern three: ship date versus install date.

Cisco defines consumption for new hardware at ship, and staging, regional customs delays, and phased rollouts routinely put 60 to 120 days between the two.

Pattern four: EAWS reports that do not reconcile to the customer CMDB, which is the same data problem Cisco itself concedes when it commits to an operational capabilities roadmap.

Each pattern is closed by different evidence: the Offer Description text kills the growth-allowance claim, the prior order's partner price sheet restores the ceiling, delivery receipts and asset tags settle the date.

And a signed CMDB extract taken at the milestone date forces the delisting correction inside the 90-day review window.

The fourth, the EAWS-to-CMDB gap, is different: it is a standing operational tax, not a one-time drafting miss. It recurs every milestone year and it is the reason the no-true-down floor hurts.

Decommissioned gear that never gets delisted keeps billing while your committed baseline stays fixed, so the error compounds rather than nets out.

Related advisory: the full topic guide.

What is the actual difference between True Up and True Forward on Cisco hardware support?

True Forward let you grow mid-term without a retroactive bill: the added hardware was captured at the next anniversary and billed forward only, so the first partial year cost nothing.

True Up bills retroactively for that growth at the annual milestone date, with the billable period starting from the ship date of a new asset or the date an existing asset is added to the EA contract.

The practical result is that a device shipped early in a milestone year now carries close to 12 months of support charge that previously would have been $0.

Does True Up apply to my existing Cisco Services EA?

No, provided nothing restructures the enrollment. Cisco states that existing EA customers under an existing EA ID retain the True Forward model for the duration of their remaining terms, including additional service purchases and upgrades.

True Up applies to Hardware Support on new and renewed Services EA bookings from July 26, 2026, so protect the EA ID and get the grandfathering position confirmed in writing before you sign any amendment or co-term.

Does the 15% growth allowance protect me from a True Up bill on new hardware?

It does not. Cisco's Services Portfolio offer description is explicit that no services on hardware are eligible for growth allowance; the 15% cushion applies to licensed software amounts.

That means True Up on HW CX bills from the first device with no buffer, and any exposure model that assumes a 15% headroom on hardware will understate the first milestone invoice materially.

When does the retroactive clock start for a new switch or router?

For a new asset, consumption is defined at the point the hardware device is shipped, not when it is racked, configured, or placed in production. For an existing asset, the clock starts when the asset is added to the EA contract.

Buyers with long staging or deployment cycles should negotiate to have the billable event tied to a documented in-service date, and at minimum should track ship dates in procurement so the exposure is visible before the milestone.

Can I reduce a True Up bill by decommissioning hardware?

Partly. Value Shift business rules are unchanged, and both newly added and decommissioned hardware are considered, so the adjustment reflects net change in the install base.

However, your payment obligation will not fall below the commitment established by the Initial Services Entitlement during the suite term, so decommissions offset growth but cannot cut your floor.

You also have only a 90-day window to review and clean up the delisted install base, after which delisted assets remain eligible for True Up billing.

What happens if my hardware support falls below the $200k ACV minimum?

You either raise contract value or move Hardware Support out of the Services EA. Cisco's stated paths to raise value are expanding scope, buying more suites, upgrading the support tier, adding Professional Services, or accepting smaller discounts.

The threshold is calculated as Net ACV after discounts and is enforced only when at least one HW CX suite is in the proposal, which creates the perverse outcome that a deeper discount can push you below eligibility. Below-threshold customers can still buy HW CX outside an EA.

Will Cisco extend True Up to software licenses and software support?

Cisco states there are currently no plans to implement True Up for Software Licenses and Software Support in the EA, and Software Support remains under True Forward. Treat that as a statement of present intent, not a contractual commitment.

If the software side of your estate is material, ask for term-length language that fixes the software billing model for the duration of the enrollment rather than relying on the FAQ.