Odoo multi-company setup in Luxembourg: running a holding and its subsidiaries in one database

In short. Odoo handles multi-company natively: several legal entities live in one database, each with its own PCN 2020 chart of accounts, its own VAT rates and its own eCDF filings. For a typical Luxembourg group (a holding company and its operating subsidiary), it is the most direct way to get a group-wide view without mixing the books. The real point of attention is not technical: it is the discipline of keeping accounting and tax strictly separate per entity.

As soon as a second company appears (a holding above the operating business, a subsidiary per activity, a property company next to the trading one), the question comes up: two management tools, or one? Here is how Odoo deals with multi-company, and what the Luxembourg context requires you to configure properly.

What does Odoo's multi-company setup actually do?

Odoo's multi-company setup lets you run several companies in a single database: each entity keeps its own chart of accounts, journals, VAT rates and reports, while users switch between companies and some records (contacts, products) can be shared or kept separate.

In practice, an authorised user switches company from the selector at the top of the screen, without changing database or account. The owner sees both companies. So does the finance manager. The subsidiary's employee only sees their own. That segregation through access rights is the backbone of a healthy configuration.

One licensing detail to know before you start: at Odoo, multi-company is reserved for the "Custom" plan, the tier above Standard. The licence is still billed per user, not per company: adding an entity to the database adds no licence cost.

The typical Luxembourg case: a SOPARFI and its operating subsidiary

The most frequent pattern in Luxembourg SMEs: a holding company owns the shares, an operating company runs the business. A pure SOPARFI needs, in principle, neither a business permit nor a VAT number, but it keeps real accounts under the PCN 2020 and files with the RCS. The subsidiary carries the VAT, the staff and the day-to-day invoicing.

In Odoo, that translates into two companies in the same database. The holding generates few entries: participations, some costs, dividends. The subsidiary carries the volume. The classic mistake is configuring the holding "like a normal company", VAT switched on by default, when it is not a taxable person: the tax setup must reflect each entity's actual status, not a copy-pasted template.

Structuring a group with a holding and a subsidiary? The legal form, the taxation and the management tool are decided together, not one after the other. Advena frames all three in a single conversation. Book a 30-minute call.

Accounting per entity: PCN 2020, VAT and eCDF stay specific to each company

A single database does not mean a single set of accounts. Each company keeps its own balance sheet, its own P&L and its own filing obligations. VAT is declared per taxable person, under each entity's own registration number, on the eCDF platform. The FAIA audit file, if the authorities request it, is exported company by company. And each entity files its annual accounts with the RCS within the legal deadlines, a subject we covered in filing annual accounts in Luxembourg.

Odoo respects that logic: journals, invoice sequences and tax configuration exist per company. The foundation is the same as for a standalone entity, described in setting up Luxembourg accounting in Odoo; it is then duplicated cleanly for each company of the group, with the settings matching its own status.

Intercompany flows: recharges, management fees and VAT

This is where multi-company earns its keep. Odoo's intercompany feature can, when company A invoices company B, automatically generate the matching document at B (a draft supplier bill, to be validated). Less double entry, fewer year-end discrepancies: intercompany balances that don't match are one of the recurring pain points of group closings.

On VAT, two rules to keep in mind. Services invoiced between Luxembourg group companies are, in principle, subject to VAT at the standard 17 % rate. For groups with significant internal flows, Luxembourg law provides for the VAT group (article 60ter of the VAT law): members that are financially, economically and organisationally linked are treated as a single taxable person, and internal transactions fall outside the scope of VAT. The option comes with precise conditions and filing consequences: it is assessed case by case, with proper advice, not copied from a blog post.

One last guardrail: a holding that invoices management fees on a preponderant basis is no longer a pure holding. It shifts to a commercial regime, with a business permit and VAT registration as a consequence. The structure must stay consistent between the law, the tax position and what the Odoo database records every day.

Consolidation and group reporting: what Odoo does, and what remains accounting work

For steering, Odoo provides statements per company and aggregated views: revenue per entity, compared results, multi-company pivots. For most SME owners, that management reporting is enough to run the group month by month.

Statutory consolidation (consolidated accounts prepared and filed) is a different exercise: eliminating internal flows, restatements, defining the scope. Many small Luxembourg groups are exempt below size thresholds, to be checked for each situation. When it is due, it relies on books that are already clean and aligned across entities: which is exactly what a well-kept multi-company database prepares.

The classic pitfalls of a multi-company configuration

Four points concentrate most of the damage we see on badly configured databases:

• Access rights. An invoice posted in the wrong company happens fast when everyone sees everything. Access is mapped to real roles, from day one.
• Shared master data. Contacts and products can be common or company-specific. Two entities serving the same clients share their records; two distinct activities keep them separate.
• Sequences and documents. Each company issues invoices with its own numbering, letterhead and legal mentions. A document in the wrong entity's name is a formal error that becomes a substantive problem in an audit.
• Timing. Creating the second company in an existing database is simple. Merging two Odoo databases that lived separately for three years is much less so. If the group is foreseeable, the multi-company structure goes in from the start.

Illustrative case (provided as an example; it does not correspond to a real client). A two-company group in Leudelange: a SARL holding that owns the premises and the shares, a twelve-person operating subsidiary. One Odoo database, Custom plan, three multi-company users (the owner, the office manager, the external accountant). The quarterly rent recharge automatically generates the supplier bill at the subsidiary. At year-end, intercompany balances reconcile in an hour, and each company files its own accounts.

Frequently asked questions

Can you run several companies on a single Odoo licence?

Yes. Odoo licensing is billed per user, not per company. Multi-company requires the "Custom" plan; a user working across several entities only counts once.

Does each company keep its own VAT return?

Yes. VAT is declared per taxable person, under each company's own registration number, on eCDF. The shared database changes nothing about the obligations: a non-taxable holding files no return, the subsidiary files at the usual deadlines.

Does Odoo produce consolidated accounts?

Odoo delivers multi-company reporting: statements per entity and aggregated views for steering. Statutory consolidation, with eliminations and restatements, remains a specific accounting exercise, from which many small groups are in fact exempt under conditions.

One database or one database per company?

One database in most cases: shared master data, automated intercompany flows, a single environment to maintain. Separate databases are justified when confidentiality between entities, different shareholders or a planned disposal require it.

Why Advena?

• Formation, accounting and Odoo under one roof: the holding, each entity's books and the multi-company database are designed together, not across three providers.
• Luxembourg grounding: PCN 2020, eCDF, FAIA and each entity's VAT status handled with real local knowledge.
• Clear fixed prices, no hourly billing: you know what you pay before you start.
• Direct access to the founders: the partners support you, not a junior.

Read next: Odoo in Luxembourg: is it the right ERP for your SME? · Setting up a holding company in Luxembourg: the SOPARFI explained · Setting up Luxembourg accounting in Odoo · Filing annual accounts in Luxembourg · How much does an Odoo implementation cost?