En bref

A first go-live is relevant experience, not an approval for the next entity. Phased ERP rollout governance separates what the design has proved from what the next country must still establish. That means its own data, its own regime and its own calendar. Before releasing the next wave, a sponsor needs resolved carry-over, named specialist capacity and a written record of open conditions. The decision is release, resequence or defer, and next-site readiness is the evidence behind it.

A first go-live proves the design works somewhere, not everywhere

The first entity closed its first period on the new system three weeks ago. The team has moved from cutover into support. The group plan shows the second country starting next month, with the same design and the same people.

The live site has proved that the common design can run a real business. It has not proved that the design fits a second tax regime or a second customer base. Tennant Company’s fourth-quarter 2025 results put a number on that gap. An ERP go-live in North America alone cut net sales by about $30 million. Adjusted EBITDA fell about $22 million and Americas organic sales dropped 22.3%.

Moving quickly after a successful launch is a reasonable instinct. The risk begins when confidence from one site carries over to a site with different dependencies. Phased ERP rollout governance exists to keep those two things apart.

Separating what transfers from what does not in a multi-country ERP rollout

The layer that genuinely transfers

A common design transfers. Chart of accounts structure, document types, master data rules and the cutover runbook carry forward. The lessons transfer too, provided someone recorded them while they were still uncomfortable. SPAR Group shows how far that learning can reach.

Its KwaZulu-Natal distribution centre went live on SAP in February 2023. ITWeb reported R1.6 billion of lost group turnover for the year to 30 September 2023. Lost regional profit was roughly R720 million, and SPAR wrote off R94 million of SAP asset under construction. A trading update of 23 February 2026 then described an amended rollout. SPAR moved to capability enablement rather than distribution centre integration, which changed the shape of the wave.

The layer that stays local

The second layer does not transfer, and it decides whether the next country can trade from day one. SAP states that it covers more than 130 countries with more than 1,000 local versions. Each version carries its own filing calendar.

Romania illustrates the point, because two regimes run on separate clocks. VATCalc reports that RO e-Factura has covered most domestic business-to-business invoicing since July 2024. Romania deferred full enforcement for small taxpayers below EUR 500,000 to 1 July 2026. The ANAF D406 reference shows SAF-T starting for large taxpayers on 1 January 2022 and small taxpayers in 2025.

Four local conditions therefore need their own evidence at the next entity:

• Statutory clearance and reporting, including Poland’s KSeF platform, its JPK_CIT accounting file and Hungary’s NAV Online Számla.

• Employee representation, including German co-determination under Betriebsverfassungsgesetz §87(1)(6) as the Bundesarbeitsgericht has read it.

• Fiscal rules still moving, such as the Wachstumschancengesetz and the German Federal Ministry of Finance e-invoicing decree.

• Local master data quality, customer contract terms and the entity’s own closing calendar.

Deferral carries its own cost. The Commission européenne adopted the VAT in the Digital Age package on 11 March 2025. Single VAT Registration applies from 1 July 2028, cross-border digital reporting from 2030. One-Stop-Shop and Import One-Stop-Shop changes sit inside that timetable.

Carry-over from the live site is group exposure, not local housekeeping

Open items from the first wave do not stay at the first site. Manual workarounds, unreconciled balances and unassigned support duties migrate into the group close. The question is not whether these exist, because they always follow a go-live. It is whether each has a named owner and a closing date. Carry-over is where phased ERP rollout governance earns its place.

Birmingham City Council shows the cost of leaving carry-over unresolved. The Register reported in January 2026 on the council’s Oracle programme. An initial estimate of £19 million reached an approved budget of £131 million in 2024. The forecast now stands at £144.4 million through 2027/28, and the council is rebuilding the system from scratch.

A quiet first site is not necessarily a stable one. The difference usually surfaces at the second period close rather than the first. Support duties between the programme and local finance often remain unassigned. The next wave then inherits an open question rather than a working service. Our note on failed ERP implementation recovery sets out the sequence that closes it.

Testing shared specialists across ERP deployment waves

The same people cannot stabilise one country and prepare another at full strength. Tennant’s recovery required cross-functional teams and additional on-site support. It also required a two-week manufacturing shutdown in early January 2026 for a full physical inventory. Those hours come out of the next country’s preparation unless the plan reserves them.

Clorox disclosed a comparable pattern on the commercial side. In its first-quarter fiscal 2026 results, net sales fell 19% to $1.43 billion. The company put the approximate ERP impact at minus 14 percentage points on net sales growth. Two of three phases were complete, inside a digital investment of about $580 million.

Capacity pressure is not confined to one company. The DSAG Investment Report 2026 surveyed 198 member companies between December 2025 and January 2026. It found 63% naming end of maintenance as a top challenge. DSAG’s chairman attributed slipping schedules to skills shortages, parallel transformation projects and limited budgets.

The external clock behind the capacity decision

SAP announced on 4 February 2020 that mainstream maintenance for Business Suite 7 ends in 2027. Optional extended maintenance runs to 2030, and S/4HANA carries a commitment to 2040. Duration is itself a measurable risk.

Budzier and Flyvbjerg studied 1,355 public sector IT projects. They found an average schedule overrun of 24%, with 18% exceeding budget by more than 25%. Each additional year of duration added 4.2 percentage points to average cost risk. Stretching the plan to protect one of the ERP deployment waves raises the risk behind it.

Phased ERP rollout governance comes down to one recorded decision

Approval is where this usually fails, not design. A steering committee reviews a status pack and hears that the first site is live. It then releases the next date without recording what the release assumed. Six months later nobody can reconstruct the evidence behind it.

A wave release note fixes that, and it fits on one page. It records six things, each with a named owner. The missing entry is usually the one that later matters.

1. The reusable lesson carried forward, and where it was tested.

2. The local condition at the next entity that the first site did not test.

3. The cross-wave dependency, including carry-over still open at the live site.

4. The shared owner and the named capacity committed to each of the ERP deployment waves.

5. The release option selected: release, resequence or defer.

6. The authorising sponsor, the open conditions and the evidence required at the next review.

The note is a record, not a scoring model, and it does not produce a number. It states which option a named person selected and on what evidence. That is the working content of phased ERP rollout governance.

Why next-site readiness is not site-level readiness

Site-level readiness asks whether one entity can run on the system. Next-site readiness asks whether the group can afford two states at once. One site stabilises while another prepares, drawing on the same specialists and the same sponsor. A site can be ready while the group is not. That is the condition a multi-country ERP rollout most often misreads.

The decision in front of the sponsor

There are three options and none of them is neutral. Release accepts that stabilisation and preparation will compete for the same people. Resequence means the design transfers but the local conditions do not yet. Defer means carry-over at the live site is still unowned.

Each option has a different owner. The Group CIO owns the design question and the Group CFO owns the statutory and close question. The COO owns the trading impact at cutover. The Country Managing Director owns whether the entity can still serve its customers. Across entities in Poland, Czechia, Slovakia, Hungary and Romania, those four signatures mean four different things. Ownership in Germany, Austria or Switzerland adds a fifth perspective.

A capable internal group programme team can own wave governance without outside help. The case for an interim ERP Programme Director arises in a narrower situation. It arises when local and shared decisions sit above the level the programme can coordinate. CE Interim, part of Valtus Alliance, places executives into that position across Central and Eastern Europe, DACH and the GCC. Its guide to ERP migration in manufacturing covers the surrounding ground.

The next release date is already in the plan. What is usually missing is a written statement of which option that date represents, and who authorised it. Without that record, the group approves the second country because the first one survived.

Questions group sponsors ask before approving the next wave

Does a successful first launch validate the next country?

No, it validates the common design under one set of conditions. The next entity has its own data quality, statutory regime, customers and closing calendar. The first launch does provide a tested runbook and a measured stabilisation period. That is evidence about the programme rather than about the next country.

Which lessons can be reused?

Design artefacts, integration patterns, test scripts, cutover sequencing and migration tooling reuse well. Role definitions and the support model reuse with adjustment. Anything resting on local law, local master data or local customer behaviour does not. The practical test is whether the lesson concerned the system or the site.

What if stabilisation and the next launch need the same people?

Then the plan holds two jobs for one team, and the sponsor should price that first. Tennant’s results statement records added on-site support and a two-week manufacturing shutdown in January 2026. The options are to widen the gap between waves, add independent capacity, or reduce scope. Choosing between them is part of phased ERP rollout governance.

Who should approve a change in wave sequence?

The group programme sponsor, not the ERP Programme Director. A change in sequence is a capacity and commercial decision affecting more than one entity. It moves the group against fixed external dates, such as the SAP maintenance and ViDA timetables. At that point a multi-country ERP rollout stops being a plan and becomes a decision.