A rollout is not ten projects with a steering committee
The usual failure looks organised. A global template is announced in the HQ country. Country two copies the company, then "adapts". Country three starts again because the template assumed one tax engine, one bank format and one payroll. A template designed once avoids that path: country four runs on the same tenant, the same chart and the same consolidation as country one.
One template means one legal-entity pattern, one chart, one security model, one ALM path, and a written list of what a country is allowed to change. Everything else is a statutory plug-in. A partner who can draw that line is delivering one global design with local plug-ins.
What the template owns — and what it must not
The template owns: the chart of accounts shape, financial dimensions, posting profiles, procurement and inventory policies, customer and vendor masters, the environment strategy, and the release cadence.
The country owns: tax codes and returns, bank files, e-invoicing (eTIMS, PEPPOL, whatever the authority requires), statutory reports, official language, and payroll calendars.
Cross that line in either direction and you lose. If HQ hard-codes Kenyan VAT into the template, Germany breaks. If Kenya is allowed to invent its own dimensions, group reporting dies. We write the line down in Discover and we staff the programme so a technical architect, not a local hero, enforces it.
Statutory books are products, not workshops
This is why we publish ISVs instead of promising "local knowledge". Payroll for Kenya, Nigeria and South Africa is a product. eTIMS signing inside posting is a product. Disbursements that validate accounts across 55 countries are a product. A country rollout that can subscribe to those is a week of configuration. A country rollout that rebuilds them is a quarter of risk.
A global partner who does not already run African statutory in production will learn it on your programme. We already run it. Europe then becomes another statutory pack on the same template — Electronic Reporting, tax configuration, bank formats — not a new methodology.
The sequence that actually works
Stand up the template in one demanding country, not the easiest one. Kenya plus a European IFRS book is a better first pair than two similar EU entities. Prove tax, payroll, bank and consolidation on that pair. Then clone the legal entity, load the next country's statutory pack, and refuse new dimensions.
Training is role-based and identical in shape: the AP clerk in Johannesburg and the AP clerk in Lyon take the same path, with country examples. Support is one Client Portal, one SLA, one product owner for the template. That is how five phases stay five phases when the map gets wider.
Who should run it
You want a partner who has already held both ends of the problem: African statutory reality and a group IFRS pack. You want architects who will say no to a local customisation. You want a commercial model that does not earn more money every time a country "needs a little extra".
That is the work Software Dynamics is built for — Nairobi and Johannesburg as the delivery spine, Europe as a travel advantage, one template, many books. If your board has approved a multi-country Dynamics 365 programme, the next decision is whether the template will survive country three. We design it so that it does. Book the conversation before someone copies company one and calls it a rollout.