Tennant's original SAP program budget was approximately $5 million. Projected 2026 remediation cost is now above $20 million. That is the disclosed number, on the record. And every month inside the 3–8 month window before H1 2027 adds to it — the compounding cost of running manual workarounds, incorrect signals, and order-to-cash disruption while SAP is remediated underneath.
Computed from Tennant's disclosed $20M+ remediation against a rolling 3–8 month horizon from October 2026. The counter accrues in real time from the disclosed baseline.
Tennant disclosed the original budget as a program number. And then disclosed the projected remediation as a materially different number. The gap between them is the cost of the disruption — and it is still moving.
The budget Tennant established at the start of the North America SAP implementation. This was the number the program was approved against.
Tennant's disclosed remediation cost projection for 2026. This is not the total disruption cost — it is the disclosed remediation spend against the original budget.
The disclosed $20M+ is not one number. It is a stack of costs — some capitalized, some expensed, some carried as ongoing operating burden. Click any allocation to see the specific cost profile and what the parallel layer avoids.
Direct spend on the SAP remediation program itself — configuration work, integration rebuilds, and parallel system construction to restore functionality.
Costs recognized immediately against operating results — labor, vendors, and program overhead that cannot be capitalized under standard accounting.
Tennant disclosed "manual oversight and manual purchase orders" as the operating workaround. Every manual PO is a labor cost that automation should have eliminated.
When demand signals are incorrect, materials arrive off-schedule. Expedited freight is the cost of moving them back in phase with production.
Tennant disclosed a $30M sales impact directly tied to the disruption. This is the revenue side of the equation — orders that did not close on time, or at all.
EMEA deployment was deferred beyond 2026 as remediation focuses on North America. The cost of the deferral is the value of the region staying on legacy systems.
The disclosed remediation is $20M+. The window before H1 2027 is 3–8 months. Every month inside that window carries a monthly operating cost — manual PO correction, expedited freight, and lost sales impact. Drag the slider below to model the compounding cost against the disclosed baseline.
Computed from Tennant's disclosed $20M+ remediation against an estimated monthly burden across the window. Drag the slider to see the projection change.
Tennant's remediation budget is committed. The $20M+ is being spent to restore SAP. What is not yet committed is whether Tennant carries the operational cost of the wait — manual POs, expedited freight, and lost sales — for the full 3 to 8 months until H1 2027, or whether the parallel layer absorbs that cost while remediation proceeds.
The layer does not add to the remediation spend. It does not duplicate SAP's work. It operates in parallel, restoring order-to-cash during the window, and hands back control when remediation completes. The delta between those two paths is the number the meter above is showing.
The parallel layer closes order-to-cash inside the 3–8 month window that SAP remediation leaves open. The delta is what you recover.