About the service
When a group grows, deploying each branch separately means lost time and growing process divergence. After a few such projects, the group maintains several different configurations of the same system.
ANEGIS runs Dynamics 365 rollouts on a core model + localisation approach:
we build the shared process core once, with the first branch or on the basis of a working implementation, and in each country we add only the local layer: taxes, regulations, and language. In Poland with KSeF, JPK, and the Polish Localisation Pack, with programme governance and risk control.
Every next company deployed from scratch means lost time and growing process inconsistency
Without a shared template, each branch is deployed differently, and knowledge from previous projects does not carry over to the next ones. This problem starts as early as the first implementation.
- Inconsistency between companies. Different configurations, charts of accounts, and processes in the same system. There is no single source of truth, and group control becomes harder.
- Localisation repeated from scratch. Taxes, reporting, and e-invoicing developed separately in each country, even though most of this work only needs doing once.
- The standard versus local requirements. Without clear governance, the group standard gradually gives way under the pressure of local legal obligations.
- No learning effect. Each country takes about as long as the first, and costs grow instead of falling.
- Consolidation outside the system. Intercompany transactions and currency conversions done by hand, because data between companies is inconsistent.
- No supplier coordination. Many local partners without a shared standard take control of quality and cost away from head office.
From the shared core to go-live in every country
Global template
Shared processes, chart of accounts, roles, and configuration as the group standard, built with a pilot or from a live deployment.
Localisation for each country
Each country's taxes, law, and reporting. In Poland, KSeF, JPK, and the Polish Localisation Pack.
Fit-gap for each company
Comparing local requirements against the template and deciding what is standard and what is a justified exception.
Multiple companies in one instance
A multi-company structure, intercompany transactions and eliminations, and currency consolidation across the group.
Data migration and local integrations
Opening balances for each entity and local systems connected to the shared core.
Testing, training, and go-live
UAT, a trial cutover, and go-live in each wave, with a contingency plan.
Post-launch care and handover
Heightened support in the first weeks after go-live and the transition into ongoing managed support.
The value a core-model-based rollout delivers
- One standard across the whole group. Consistent processes, chart of accounts, and reporting in every company.
- Each further country faster and cheaper. The core stays shared, and only the local layer requires work.
- Full local compliance. Taxes and e-invoicing compliant with each country's law, in Poland KSeF and JPK.
- Consolidation in the system. Intercompany settlements and currency conversions done where the data is created.
- Head-office control and local flexibility. A shared standard with room for justified exceptions.
- Lower cost of ownership. One instance and a shared core instead of separate systems in each country.
Products that help us drive change
We run rollouts on the Dynamics 365 applications, Finance and Supply Chain Management, with localisations for over 200 countries and Globalization tools where the standard is missing. The Polish compliance layer is added by ANEGIS accelerators: KSeF, JPK, and the Polish Localisation Pack. Power Platform and Power BI support the whole.
Proven performance, reliable results
We work according to our proven delivery method, based on Microsoft Success by Design and aligned with the FastTrack approach. We run the project in stages, with decision gates and architecture reviews, so that risks surface early and decisions are deliberate.
- Blueprint and governance at the start. We establish what is global and what is local before the first country begins.
- Core model before the waves. The core is built once, with a pilot or on the basis of an existing implementation.
- Deployment in waves. Country by country, by risk and local readiness. Lessons from each wave feed into the next.
- Go-live with heightened care. Go-live with a contingency plan and intensive support in the first weeks
Why entrust the rollout to us
- A focus exclusively on Dynamics 365. Experience in multi-company and multi-country implementations.
- The Polish part of the rollout. KSeF, JPK, and the Polish Localisation Pack. A natural partner for the Polish part of an international programme.
- A presence in Poland and the UK. International rollouts and communication with head office in its language.
- Governance and risk control. A methodology based on Success by Design. We also take over stalled rollouts.
- Our own accelerators. They shorten localisation and go-live in each further country.
From the initial consultation to a fully operational system
Switching systems doesn't have to mean chaos. We guide you through five steps so that at every stage, it’s clear what is happening, why, and what the next step will be.
Discovery call
Free consultation: we learn about your situation, goals, and constraints. No strings attached and no sales pitch.
Analysis and recommendation
We map processes and requirements, assess platform fit, and recommend the scope, path, and approach.
Plan and decision
Schedule, budget, roles, and decision gates. You make project decisions based on facts, not assumptions.
Phased implementation
We implement step-by-step, with testing, risk control, and reviews at every milestone.
Stabilization and support
Launch with a contingency plan, post-launch support, and transition to ongoing maintenance.
See how we transform tech companies
Becker Manufacturing: ERP transformation
Microsoft Dynamics 365 Sales implementation for Georg UTZ
Microsoft Dynamics 365 modernisation for a global advertising holding
Nicols
Each further country faster than the last
We build a shared core (core model), add the local layer, and deploy in waves. In Poland with KSeF and JPK. The result: one group standard and a falling cost for each further implementation.
How we structure a rollout
There is no single right model, we match it to the group's structure. The principle is shared: the first wave builds the core, each further one is mainly the local layer.
The first implementation as the foundation
a start in one branch, designed from the outset as a template to replicate.
Core model first, then waves
once the core exists, further companies receive it in waves.
Hub-and-spoke
a rollout run from a competency centre out to the regions, with local teams for the fit-gap.
Wave by wave (wave-based)
country by country, by risk and readiness; lessons from each wave feed into the next.
Big-bang or stages
a full switch all at once only where scale allows; for groups we recommend phases.
The Polish part, or a programme takeover
we run only the Polish leg of an international rollout, or take over a stalled programme.
Collaboration models
See other services
Managed support
We will provide ongoing care for your Dynamics 365 environment, responding to tickets and keeping the system stable and trouble-free.
Frequently asked questions about the Dynamics 365 rollout
How does a rollout differ from an ERP implementation?
An implementation is a single go-live for one organisation. A rollout is a multi-entity programme; even if it starts with the first branch, we design that first system as a repeatable pattern (a core model) with a local layer and further waves in the plan.
We already have Dynamics 365 in one company; will you roll it out to the rest?
Yes. Your live deployment becomes the starting point for a shared template, which we apply to the remaining entities with localisation for each country.
Will a single Dynamics 365 handle multiple countries at once?
Yes. One instance can run multiple companies, and legal features switch on based on each company's country. Dynamics 365 supports local requirements for more than 200 countries and regions.
How long does each additional country take?
Less time than the first. The first wave builds the core; in the following ones we repeat the template, and most of the work is in the local layer.
Can you handle just the Polish part?
Yes. We deliver the Polish part of an international rollout, covering KSeF, JPK, and the Polish Localisation Pack, working with your global integrator, or we take over a stalled programme.
Let's plan the rollout across your group
