90+ enterprise clients · 25+ countries
Every company in the group, one Odoo.
Several companies, countries and currencies on one database, with inter-company transactions posted automatically, each entity on its own country's tax set-up, and a consolidated view for the board without a month of spreadsheets.
Group consolidationone Odoo database
Sample data1 SGD = 43.50 PHP · 20,200 VND · 3.30 MYR
Consolidated, one Odoo
What Odoo for groups covers
Odoo for groups runs several companies, countries and currencies on one Odoo database. Inter-company transactions post automatically, each entity keeps its own books and local tax rules, and the board sees one consolidated set of numbers in the group currency. TechNext rolls it out in phases: one company first, then country by country.
Odoo multi-company consolidation, from local books to one group P&L.
A sample group on one Odoo database: a Singapore holding with companies in the Philippines, Vietnam and Malaysia, each keeping its own books and currency. An intercompany invoice creates the mirror bill in the other company, a group loan accrues interest, and at month-end the figures are translated into SGD and the intercompany lines are eliminated. Switch companies in and out of the group view or move the exchange rate, and the consolidated P&L TechNext sets up for you updates line by line.
| P&L | SG | PH | VN | MY | Elim. | Group |
|---|
The group: a holding company in Singapore (SGD) owning companies in the Philippines (PHP), Vietnam (VND) and Malaysia (MYR), each with its own books on one Odoo database.
Intercompany: Vietnam sells goods to the Philippines, and the invoice creates the matching vendor bill in the Philippine company; Singapore lends to Vietnam and charges Malaysia a management fee.
Month-end: each company closes its books, figures are translated into SGD, intercompany revenue and cost, receivables and payables, the loan and its interest are eliminated, together with the profit still sitting in the buyer's stock, and the group P&L is produced.
Illustrative figures for a fictional group, wholly owned, one rate per currency. Your consolidation rules, rates and eliminations are set up with your accountants.
Everything a group needs on one database.
One system for every entity, with each company's books, users and local rules intact, and the group view built on top rather than typed up each month.
Multi-company setup Per entity
Each entity keeps its own books, users and approval rules; you share products, partners and reports only where you choose to.
Country localisations Per entity
The right chart of accounts, tax and statutory reporting per country, with group reporting rolled up in one currency.
Inter-company flows Between entities
A sale in one entity raises the matching purchase in another; the invoice and bill reconcile automatically.
Multi-currency Entity to group
Transactions in local currency, revaluation and reporting in the group currency, exchange rates managed in one place.
Consolidation Group
Group P&L, balance sheet and cash on demand, with eliminations handled by the system rather than a spreadsheet.
Access and governance Entity and group
Granular access rights, record rules, approval chains and audit trails: segregation of duties enforced by configuration.
Each entity files in its own country: BIR here, GST there.
In a group with a Philippine company, that company keeps its own books, BIR filings and e-invoicing plan, while a Singapore entity keeps its GST returns, and neither is rebuilt in a spreadsheet for the group view. E-invoicing is due by 31 December 2026 for covered taxpayer groups and applies to every branch, so we check the Philippine entity's group and branches in discovery.
What each entity keeps Sample group
- SingaporeGST returns; InvoiceNow through the Access Point you choose.
- PhilippinesCAS / CBA books, the 2307 per payee, SLSP, SAWT and QAP, the 2550Q, and invoices set up for the EOPT rules; e-invoicing is planned separately.
- Vietnam, MalaysiaTheir own country localisation for tax and statutory reporting.
- The groupOne consolidated view in the group currency, read from the same database.
Pilot one entity, then template the rest.
We prove the model on a single company, turn its setup into the group standard, and roll out entity by entity, with local changes only where the law demands them.
- 1
Group discovery
We map the entities, the flows between them, the currencies in play and exactly what the board needs to see, plus which systems stay.
- 2
Pilot entity
One company implemented end to end (Accounting, Sales, Inventory and whatever it needs), running on real data.
- 3
Group template
The pilot's setup becomes the standard: chart-of-accounts mapping, shared masters, inter-company rules and consolidated reports.
- 4
Phased rollout
Entity by entity and country by country, with local tax and statutory reporting, trained local teams and one shared support plan.
One platform, every entity, staged safely.
Group deployments need custom modules, safe places to test them, and data-residency choices made on purpose. We size and set up the platform with you.
The platform 12 items, one database
- All entities on one Odoo database with a shared master-data model.
- Production, staging and development branches on Odoo.sh.
- Custom modules built, tested on staging and version-controlled.
- Inter-company rules that post the matching document automatically.
- Multi-currency with revaluation and group-currency reporting.
- Consolidated P&L, balance sheet and cash with eliminations handled.
- Country localisations for tax and statutory filing per entity.
- Granular access rights and a role model per company.
- Single sign-on across the group where you use it.
- Backups, monitoring and a clear version-upgrade path.
- Data residency by region where regulation requires it.
- One support plan covering every entity.
How groups usually ask it.
Do all entities have to go live at once?
No. We implement a pilot entity first, then roll the template out company by company. Each entity goes live when it's ready.
How does consolidation work?
Group P&L, balance sheet and cash are produced from the same database, with inter-company eliminations handled by the system. There's no separate month of spreadsheet consolidation.
Can each country keep its own tax rules?
Yes. Every entity uses its country's localisation for chart of accounts, tax and statutory reporting, while the group reports roll up in one currency.
Who can see what?
Access is controlled by granular rights and record rules per entity, with approval chains and audit trails. People see their company's data and only the group views you grant.
Where does the group's data live?
Usually on Odoo.sh, with staging and version control; on your own cloud where data residency requires it. We decide per region during discovery.
How is a group project priced?
By the entities, countries, integrations and custom work involved, so it's scoped and quoted rather than listed. Tell us how the group is structured and we'll come back with a phased quotation.
What this connects to.
Tell us how the group is structured.
Entities, countries and what the board needs to see: that's enough for a first architecture and a phased quotation from an adviser.