Cisco Services EA hardware support carries a 0% Growth Allowance under True Up, so the first asset above baseline bills retroactively at the annual milestone date
From July 26, 2026, all new and renewed Services EA bookings move hardware support from True Forward to True Up, and Cisco's own program documents confirm that no services on hardware qualify for the 115% Growth Allowance that shields software suites. That means growth is not buffered, it is banked, and the entire year of it lands in one invoice at your annual milestone. Your only real defenses are a milestone date you chose, a monthly install base reconciliation, and the two cleanup clocks (6 months at inception, 90 days per delisting) run on schedule.
Prepared by Redress Compliance · September 3, 2026 · Cisco advisory. Services EA and ELA renewal engagements, 2024 to 2026.
Executive summary
The single most important modeling fact is that hardware support gets 0% Growth Allowance, while software suites keep up to 115% of initial entitlement.
Cisco's Buying Program Offer Description for the Services Portfolio states plainly that no services on hardware are eligible for Growth Allowance, so a spreadsheet built on the familiar 15% cushion will understate hardware exposure by the entire value of that cushion.
True Up bills once per year at the annual milestone date, and that single invoice covers up to 12 months of accumulated growth retroactively.
Under True Forward you paid for growth going forward from the adjustment; under True Up you pay backwards for every month the asset sat on contract, which turns an ordinary refresh cycle into a lump-sum budget event.
The offsetting buyer win is the removal of the semi-annual exceptional growth trigger, which under EA 3.0 let Cisco act at the next quarterly anniversary once consumption passed 105% in the first six months.
True Up fires only at the annual milestone, so a mid-year 40% install base spike no longer produces an out-of-cycle bill, it produces a deferred one you can forecast and fund.
Two separate cleanup clocks decide whether decommissioned gear nets against your True Up: 6 months from the services start date at inception, and 90 days per delisting event thereafter.
Assets removed from the final quote but not decommissioned inside the 6 month reconciliation window are counted as increased Use, and delisted hardware not cleaned up within 90 days remains eligible for True Up billing anyway.
How the annual milestone date actually works
The mechanic is simpler than Cisco's documentation makes it look, and that simplicity is exactly what hurts. Cisco's own Services EA FAQ states that consumption is defined when the asset is added to the EA contract, not when it ships, not when it racks, and not when it passes user acceptance.
From that moment the asset accrues hardware support cost silently. Nothing invoices, nothing alerts, nothing appears on a quarterly statement.
At the annual milestone date, Cisco generates one True Up invoice covering hardware support growth for the entire preceding year, and because Cisco confirms that no services on hardware are eligible for the 115% Growth Allowance.
The very first serial above your entitled baseline is billable from its add date.
Three dates get confused constantly in renewal meetings: the EA start date (when the agreement legally begins), the services start date (when coverage on the baseline install base actually commences, often weeks later), and the annual milestone date (the only date that triggers a True Up invoice).
Buyers routinely assume all three are the same. They are not, and the gap between them is where the first year of exposure is created.
Two cleanup clocks run alongside: a six month reconciliation window at inception to purge assets that should never have been on contract, and a 90 day window per delisting action, after which Cisco's FAQ is explicit that delisted hardware remains eligible for True Up billing.
Decommissions do net against additions, because Value Shift business rules are unchanged under True Up, but only if the decommission is processed inside its window.
| Mechanic | True Forward (pre July 26, 2026) | True Up (new and renewed from July 26, 2026) |
|---|---|---|
| Trigger frequency | Annual, plus a semi-annual exceptional growth event | Annual milestone date only, no mid-year event |
| Retroactivity | None, growth is priced forward from the trigger | Full, growth bills back to each asset's contract add date |
| Growth buffer on hardware | 105% initial growth cap logic, then negotiated headroom | 0%, hardware is excluded from the 115% Growth Allowance |
| Mid-year exposure signal | Exceptional growth event surfaces overshoot early | None, exposure is invisible until the invoice lands |
| Netting treatment | Decommissions net at the trigger | Decommissions net at the milestone, Value Shift rules unchanged |
| Cleanup obligation | Loose, corrected at next trigger | 6 months at inception, 90 days per delisting, then it bills |
Read the table as a trade, because that is what Cisco did. You gained the removal of the semi-annual exceptional growth event, which was a genuine irritant, and you gave up the entire forward-only pricing principle plus any buffer on hardware.
The net is unfavorable for any organization growing its install base faster than it retires it. The loss of the mid-year event is not just a billing simplification, it removes your early warning system.
Under True Forward, an exceptional growth trigger told you that your estimate was wrong while you could still act. Under True Up, the first authoritative signal is an invoice you cannot dispute, for months you cannot undo.
The operational consequence: your milestone date is no longer an administrative field, it is the single most consequential number in the contract after price. Model it deliberately.
See our breakdown of the financial difference between True Up and True Forward on hardware support before you accept a default date from the paperwork.
Forecasting hardware growth with no buffer underneath it
Start with a hard baseline, not an estimate. Extract the entitled serial count at contract signature, by device family, and freeze it as your reference. Then reject the blended percentage entirely.
A single "we grow 10% a year" figure is useless here because access switching, wireless access points, routing, and data center compute grow on completely different curves and carry completely different net ACV per serial.
Build the model from the last 24 months of purchase orders, converted to monthly net adds per family. Twenty-four months matters because 12 months hides the biennial refresh pulse that most enterprises run.
The arithmetic of retroactivity is what changes the answer. Under True Forward, a 12% annual hardware growth rate produced a forward-only charge, so the cost impact started at the trigger and ran forward.
Under True Up, that same 12% spread evenly across twelve months means the average added asset has been accruing for roughly six months when the milestone hits, so you owe approximately six to seven months of support on the full year's growth in a single invoice, on top of the forward-year run rate.
If your adds are front-loaded into the first quarter, that average climbs toward nine or ten months. That is a pure cash timing shock with no offsetting benefit.
Refresh projects are the worst offender and the easiest to fix. In our experience across Cisco renewal engagements, new gear is added to contract 60 to 120 days before the legacy platform is decommissioned, so both generations sit on the EA simultaneously and both accrue.
Because decommissions only net at the milestone and the 90 day delisting window is unforgiving, a sloppy cutover can double-count an entire campus for a full quarter. Sequence the delisting action against the milestone date, not against the project close date.
The specific inputs your model needs are: net ACV per serial by suite tier (not list, since the $200k threshold and your pricing both run on net), planned refresh cutover dates by site, M&A and new site openings with their expected add months, and lab, spare.
And staged gear that is on contract but not in production.
That last category is where we find the most recoverable spend, and the six month inception reconciliation is the only cheap chance to remove it. Reconcile the install base monthly against the contract, not quarterly.
Our Cisco EA sizing model gives a structure for converting these inputs into a milestone exposure figure you can budget against.
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 →Why the milestone date is the most negotiable term nobody negotiates
Under True Forward, the adjustment date was an administrative timing detail. You grew, Cisco caught up at the next anniversary, and you paid forward from that point.
Nobody lost sleep over whether the anniversary fell in March or September because the exposure was prospective and the 115% Growth Allowance absorbed ordinary drift on software suites. True Up inverts that arithmetic entirely for hardware support.
Cisco's own program documents are explicit that no Services on Hardware are eligible for Growth Allowance, which means the first switch, the first access point, the first UCS chassis added above your Initial Services Entitlement is billable from the day it lands on the contract.
The milestone date is now the only thing standing between that first asset and the invoice, and every week between the two is a week of retroactive liability quietly accruing on a ledger you cannot see in real time.
That reframes the term completely. The milestone date determines two things that matter to a CFO: how much liability piles up before it converts to cash, and which fiscal year absorbs it.
In our experience across Cisco renewal engagements, account teams propose milestone dates that suit Cisco's booking rhythm, typically clustered to support the July fiscal year end or the quarter in which the deal was closed, not the quarter in which you have budget authority.
Nobody on the Cisco side is being devious about it. The date is simply set by the paperwork and nobody on the buyer side objects, so it sticks.
The worst possible outcome is a milestone that falls one month after your budget lock. You approve next year's operating plan in October, the milestone hits in November, and eleven months of accumulated hardware growth bills against a number you finalized before you knew what it was.
You then spend the year explaining an unbudgeted seven-figure variance that was entirely predictable and entirely avoidable.
Move that same milestone to sit four to six weeks after your capital approval cycle closes and the mechanics reverse: you walk into the approval meeting with a measured install base delta, a calculated True Up figure, and a line item. The invoice does not change. The surprise does.
Sequencing extends the same logic into the refresh calendar, and this is where the real money sits.
A buyer who completes a campus refresh in the eight weeks immediately preceding the milestone pays for roughly a full year of retroactive coverage on that hardware at the very next invoice, because consumption is defined when the asset is added to the EA contract, not when it enters production.
The identical refresh executed in the eight weeks immediately after the milestone accrues only a few weeks of liability before that milestone passes, then rolls into a full contract year that you have had twelve months to forecast and fund.
Same equipment, same discount, materially different cash timing. Once you accept that hardware support is now banked rather than buffered, refresh scheduling becomes a treasury decision as much as an engineering one, and it belongs in the same forecast model you use for sizing the suites themselves.
Here is the leverage point. Moving the milestone date costs Cisco nothing. It does not change the ACV, the discount, the suite mix, the term length, or the commission. It is a field on a form.
Yet it is treated as fixed by both sides because it arrives pre-populated on the quote and buyers assume it is systemically determined. It is not. Raise it at quote stage, in writing, alongside your entitlement baseline discussion, and it will almost always move.
Raise it at signature, when legal is queuing and the quarter is closing, and you will be told the paperwork is already through desk approval.
The reading is uncomfortable but simple: the milestone date is the highest return per minute of negotiating effort available anywhere in a Services EA, and it is the term buyers most reliably leave on the table.
A discount point takes weeks of escalation and gets clawed back through suite composition. A milestone shift takes one email at quote stage and permanently changes which fiscal year carries your retroactive exposure.
Ask for a milestone date that sits 30 to 60 days after your capital approval cycle closes, name it in the quote request, and get it confirmed in the ordering document before desk approval. If Cisco resists, ask them to state in writing what commercial constraint prevents it.
In our experience there is not one.
The two cleanup clocks and how retroactive bills actually happen
Retroactive bills almost never come from growth nobody expected. They come from assets that stopped existing physically but kept existing contractually. Cisco runs two cleanup clocks, and both fail in the same direction.
The first is the six month reconciliation window at inception, during which assets stripped from the final quote at signature must actually be decommissioned; if they are still sitting in the install base after six months, they count as increased Use and land in your first True Up.
The second is the 90 day delisting window: Cisco's FAQ states plainly that delisted hardware assets remain eligible for True Up billing after the period of 90 days of the delisting action. Delist and walk away, and the asset is swept straight back into eligibility.
Then there is the compliance-flagged serial trap, where flagged serials are excluded from Initial Services Entitlement, sit invisible in your baseline, and get captured the moment any subsequent change touches that record.
| Failure mode | Clock | What actually bills |
|---|---|---|
| Gear removed from the rack, never delisted in the install base | None running, so no clock protects you | Full annual support on decommissioned hardware at milestone |
| Delisted but left past the 90 day window | 90 days per delisting action | Asset re-enters True Up eligibility and bills as growth |
| Stripped from the final quote at signature, not physically decommissioned | 6 months from inception | Counted as increased Use against baseline |
| Compliance-flagged serials excluded from Initial Services Entitlement | No window, triggered by any change | Captured on the next contract change, unbudgeted |
The fix is unglamorous and it is a cadence, not a project. Run a monthly three way reconciliation between the Cisco install base export, the CMDB, and the asset disposal record, with a named owner for each source and a single accountable owner for the variance report.
Anything present in one system and absent from another gets a disposition inside 30 days, which is the only cadence that keeps every delisting comfortably inside its own 90 day clock.
Ninety day reviews do not work here, because a delisting made on day two of the quarter has already burned its entire window by the time anyone looks.
Treat the flagged serial list as a separate register reviewed at the same monthly meeting, and take the same discipline into your renewal baseline discussions so the entitlement you sign matches the estate you actually operate.
The $200k ACV gate and its interaction with your milestone
Effective July 26, 2026, hardware support (HW CX) inside a Services EA carries a hard floor: $200k minimum net ACV, calculated after discounts, enforced whenever at least one HW CX suite appears in the proposal.
Software support (SW CX) and Professional Services sit at a separate $100k TCV platform-level requirement. Below the hardware floor, Cisco's FAQ language is blunt: you are not eligible to include HW CX in the Services EA at all. The word that matters in that sentence is net.
Because the threshold is measured after discounting, discount percentage and eligibility are not two independent negotiation levers, they are the same variable pointed in opposite directions.
Push your Cisco account team hard enough on price and you can discount yourself out of the vehicle, at which point the remediation menu Cisco publishes is entirely upward: expand customer scope, buy more suites, upgrade to a higher support tier, add Professional Services, or decrease discounts.
The sixth option, the only one that runs the other direction, is to move hardware support outside the EA entirely, and Cisco confirms HW CX remains purchasable a la carte. We have seen sellers use the first five options as a scoping conversation and never mention the sixth.
Note also that the gate fires on modification, not just at renewal: an active software-only EA customer adding hardware support after implementation is subject to the threshold at that moment, which resets the eligibility math mid-term.
See our breakdown of the $200k hardware and $100k software thresholds for the full mechanics.
The interaction with your milestone is what nobody models. If you are sitting near the floor, every decommission you process to reduce True Up exposure also reduces net ACV, and a clean install base that saves you money on the milestone invoice can push you under $200k at the next renewal.
That is a genuine conflict of interest built into the program design.
Model both numbers together before you sign. Build a floor-to-milestone sensitivity table showing net ACV at your target discount, then run it again assuming a 10% and 20% install base reduction from cleanup.
If the lower case falls under $200k, negotiate a contractual eligibility floor holiday or plan the a la carte exit now, at renewal leverage, rather than in year three when you have none.
What we see across renewal engagements
Cisco's Buying Program Offer Description states plainly that no Services on Hardware are eligible for Growth Allowance, so asset one above entitlement bills.
Across the Services EA renewal drafts we have reviewed since 2024, the milestone date proposed by Cisco is almost never contested by the buyer.
The primary sources here are Cisco's own documents: the Services EA Customer FAQ (2026), the Enterprise Agreement Service Portfolio Guide, and the EA 3.0 Buying Program Offer Description last modified December 12, 2025.
We read those against renewal engagements run from 2024 through 2026, and three patterns repeat with enough consistency to plan against.
First, install base records overstate live assets by a material margin in nearly every environment we touch, because decommissioned gear is physically removed long before anyone updates the contract record, and under True Up that gap is now billable rather than cosmetic.
Second, the milestone date is treated as an administrative field rather than a commercial term, which surrenders the single control that determines whether your reconciliation cycle finishes before or after the invoice generates. Third, and most consequential, is the grandfathering asymmetry.
A five year Services EA signed before July 26, 2026 retains True Forward for its full remaining term, deferring True Up exposure to as late as 2031, including on additional service purchases and upgrades. The identical agreement renewed on July 27, 2026 does not.
That is a multi-year, multi-million dollar difference driven entirely by a signature date, and it is the strongest argument available for pulling a renewal forward. Our guide to the July 2026 hardware support change covers the timing decision in detail.
- 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 the grandfathering answer in writing. Ask your account team to confirm, by EA ID and in email, whether your current agreement retains True Forward for the remaining term and the exact expiry date that ends it, because Cisco's own FAQ says existing EA IDs keep True Forward until next renewal, and a five year Services EA booked before July 26, 2026 can defer hardware True Up exposure as far out as 2031.
- Negotiate the milestone date into the quote, not the paperwork. Insist the annual milestone appear as an explicit dated term and position it 30 to 60 days after your capital approval cycle closes, so the one annual invoice for hardware growth lands in a budget cycle you have already funded rather than in the middle of one you have not.
- Rebuild the hardware forecast at a 0% buffer. Pull 24 months of purchase orders, model growth by device family, and remove every assumption borrowed from software, since Cisco states plainly that no services on hardware are eligible for the 115% Growth Allowance, so the first asset above baseline is billable from the date it is added to the contract.
- Stand up monthly install base reconciliation before the 6 month inception window closes. Name an owner per device family, reconcile additions against decommissions monthly, and calendar every 90 day delisting cleanup window, because unreconciled delisted assets bill regardless. Our Services EA True Up guide sets out the tracking cadence.
- Run the $200k net ACV test at every discount scenario. Discount depth and eligibility are coupled, so model the threshold after discounts and price a la carte SmartNet as a genuine walk-away number with independent negotiation support.
Frequently asked questions
When does Cisco's Services EA True Up change take effect?
July 26, 2026. From that date, all new and renewed Services EA bookings move hardware support from the True Forward model to True Up. Bookings placed before that date under an existing EA ID keep True Forward for the remainder of the term, including additional service purchases and upgrades.
Does the Growth Allowance apply to hardware support under True Up?
No. Cisco's Buying Program Offer Description for the Services Portfolio states that no services on hardware are eligible for Growth Allowance.
The 115% of initial entitlement buffer applies to eligible software services suites only, so on hardware the first asset above your baseline entitlement is billable.
What is the annual milestone date on a Services EA?
It is the once-per-year point at which Cisco generates the True Up invoice for hardware support growth. Consumption is measured from when an asset is added to the EA contract, not when it is deployed, and additions are netted against decommissions under existing Value Shift rules.
Under True Up there is no semi-annual exceptional growth event, so the milestone is the only billing trigger.
Can Cisco bill me mid-year for hardware growth under True Up?
No. True Up fires only at the annual milestone date. This removes the EA 3.0 exceptional growth mechanism, under which consumption above 105% of initial entitlement in the first six months gave Cisco the right to initiate a True Forward at the next quarterly anniversary.
The tradeoff is that the accumulated growth bills retroactively in one invoice.
How long do I have to clean up decommissioned hardware?
There are two clocks. At contract inception you have six months from the services start date to decommission hardware removed from the final quote, or it is counted as increased Use.
After a delisting action you have a 90 day window to review and clean up the delisted install base, after which the asset remains eligible for True Up billing.
What happens if my Services EA falls below the $200k hardware threshold?
You are not eligible to include HW CX in the Services EA. Cisco's remediation options are to increase contract value (expand scope, buy more suites, upgrade support tier, add professional services, or reduce the discount) or move hardware support coverage outside the EA.
Hardware support remains purchasable a la carte, which is why the standalone SmartNet comparison should be priced before you agree to raise value.
Should I renew my Services EA before July 26, 2026?
If your renewal is anywhere near that date, model it. A multi-year Services EA signed before July 26, 2026 retains True Forward for its full term, so a five year deal can defer True Up exposure as late as 2031.
Weigh that against whatever concessions Cisco asks for in exchange for an early renewal and against the $200k threshold you will still face at the next cycle.
