Implementation · Enterprise
Enterprise: several entities, one governed system
For groups running multiple legal entities, countries or sites. Company structure, intercompany flows, access control and consolidated reporting, phased entity by entity — with governance your board can be shown and a template the next subsidiary can reuse.
Who it is for
The hard part is what the entities must share
A group project is not a bigger version of a single-company project. The technical work is comparable; the difficulty is political and structural: what has to be identical across entities, what stays local, and who decides. Get that wrong and you spend three years reconciling.
So the first phase is not a configuration. It is a core model: the chart of accounts, the product and partner data, the processes that must be common — and an explicit list of what each country is allowed to do differently, because local compliance is not negotiable and neither is group reporting.
Scope
What is included, and what is not
No price on this page: what you can hold us to is the scope. Here it is, from both ends.
Included
- a core model designed first: shared data, shared processes, and what each entity may localise;
- company structure in Odoo, access rights and data segregation between entities;
- intercompany flows across sales, purchasing, inventory and finance;
- consolidated reporting the group can close its books on;
- integrations with the systems you are keeping;
- a phased rollout, entity by entity, with a reusable template;
- programme governance: steering committee, decision log, risk register.
Not included
- statutory accounting advice — we implement what your auditors and local accountants define, we do not replace them;
- licences, billed by Odoo per user and per app;
- the group's own decisions: what is common and what is local is yours to arbitrate, and we will not pretend otherwise;
- change management inside entities that have not been given the time or the people for it;
- an unphased big-bang across all entities at once, which we decline to sell.
The last line is a genuine refusal, not a formality. A simultaneous go-live across entities concentrates every risk on one weekend, and there is no rollback plan that survives it.
How it runs
A programme, not a project
The six steps repeat per entity; what precedes them is the work that makes the repetition possible.
1. Core model before anything else
What is common, what is local, who arbitrates. Written down and signed off before a single entity is configured.
2. Pilot entity
One entity taken end to end, chosen for being representative rather than for being easy. It produces the template — and the list of what the core model got wrong.
3. Intercompany and consolidation
Flows between entities, eliminations, and the reporting the group closes on. Built once, on the pilot, then inherited.
4. Rollout, entity by entity
Each one reuses the template and localises only what it is allowed to. The tenth deployment should cost a fraction of the first; if it does not, the core model was wrong.
5. Governance across the programme
Steering committee, decision log, risk register — and one place where a local exception is either granted or refused.
6. Transfer to run
Internal competence built during the programme, then a support arrangement sized for a multi-entity estate.
Start your transformation
A multi-entity Odoo programme to structure?
Tell us how many entities and countries, and what already exists in each. The first conversation is about the core model, because everything else follows from it.
FAQ
Frequently asked questions
You can ask; we will argue against it and, on a large estate, decline. A simultaneous go-live puts every risk on the same weekend with no usable rollback. Phasing costs a little more in elapsed time and removes the scenario where the group cannot invoice on Monday.
Local requirements are non-negotiable and they are localised inside a common model rather than being allowed to fork it. Where a country genuinely needs a different process, it goes on the exception list with a reason attached. The country pages under About us list the entities where we have our own teams.
After the pilot, not after the last entity. The consolidation model is built with the pilot precisely so that each new entity joins an existing report rather than triggering a redesign.
That is the normal starting point. Some are migrated, some are kept and integrated, and a few are retired later than everyone would like. What matters is deciding which is which early, and writing it down rather than discovering it entity by entity.
You need a sponsor with the authority to arbitrate between entities. Without one, every local exception becomes a negotiation and the core model erodes. It is the single strongest predictor of whether a group programme lands.
Let's talk
Ready to put your group on one governed system?
Tell us the entities, the countries and what runs in each today. We will come back with a core model proposal and a phasing that starts with the right pilot.