Do you need a second company in the Odoo application, or would a branch, warehouse or analytical view answer the question? Odoo documents a multi-company environment with shared records and company-specific transactions 1. The IFRS Foundation describes consolidated statements as presenting a parent and its subsidiaries as a single economic entity 2. Those are related decisions, but selecting several companies on a screen is not, by itself, a complete consolidation process. For a Saudi group, begin with document ownership and the report management needs; see the homepage for the wider implementation approach.

Define the entity before configuring the database

A second outlet or a new product line does not automatically require a new company. Ask who owns the goods, issues the invoice and keeps the books. If the distinction is operational rather than a separate entity, branches, warehouses or analytical reporting may be more suitable.

Write down the entities and the transactions between them before discussing screens. This makes a useful outcome possible: each finance team can explain its balances, employees know which entity owns a document, and management can distinguish external business from movement within the group.

Shared records still need company context

Odoo 19 distinguishes shared data from records belonging to a company. Selecting an active company affects the working context. A shared product can have company-specific cost information even while some common product fields are shared 1.

We review who may access each entity and where employees create documents. The aim is not simply to add choices to the company selector. It is to make the owner of each quotation, invoice, stock movement and balance understandable. A test user restricted to one company should be part of acceptance, alongside a user authorised to work across companies.

A counterpart document is not the entire transaction

Depending on configuration, a confirmed purchase order can create a sales quotation in the counterpart company, and a confirmed sales order can create a request for quotation. Counterpart bills, validation options and stock-move synchronisation are also documented 1. We therefore identify the trigger and approval owner rather than assume every step posts automatically or always requires custom development.

The implementation must also cover shared products, each company’s warehouse and financial localisation. Odoo’s documentation notes that adding a company does not automatically create its warehouse. Dispatch, receipt, reconciliation of the two financial documents and payment remain distinct handoffs whose evidence should be agreed.

Worked example: why simple totals can mislead

Assume A and B are subsidiaries wholly owned by a common parent, use one currency and have no opening inventory. VAT and other taxes, currency effects, additional costs and overheads are excluded. This is a simplified management illustration of duplication, not a complete set of consolidated statements or a tax conclusion.

  • A buys 50 units from an external supplier at 60 SAR each: 3,000 SAR.
  • A sells 30 units to B at 80 SAR each: an internal transaction of 2,400 SAR.
  • B sells 20 units to an external customer at 120 SAR each: 2,400 SAR outside the group.
Item Calculation Result
Inventory remaining at A 20 × 60 1,200 SAR
Inventory in B’s own books 10 × 80 800 SAR
Inventory balances added before adjustment 1,200 + 800 2,000 SAR
Internal margin in B’s remaining units 10 × (80 − 60) 200 SAR
Inventory in the simplified group view 2,000 − 200 1,800 SAR
Sales added without distinguishing their origin 2,400 + 2,400 4,800 SAR
External revenue in this example 20 × 120 2,400 SAR
Original cost of units sold externally 20 × 60 1,200 SAR
Simplified margin before overheads and tax 2,400 − 1,200 1,200 SAR

There are 30 units still inside the group (20 at A and 10 at B) at an external purchase cost of 30 × 60 = 1,800 SAR. This view does not mean deleting A’s invoice or rewriting B’s books. Each entity retains its documents; group-view adjustments are a separate process reviewed by finance. Revenue also does not establish cash collection. Use the implementation cost and savings calculators to scope the project, rather than treat the table as a promised saving.

What does a group report need beyond selecting two companies?

Odoo 19 documents consolidation tools including account mapping, consolidation adjustments and selection of the appropriate reporting ledger 1. We do not assume the capability is absent, or that combining screens is sufficient. First define the report management wants, who reviews adjustments and how figures can be traced back to entity books.

The IFRS Foundation explains the purpose of consolidated statements on a control basis and as a single economic entity 2. Establishing the applicable accounting framework and detailed adjustments needs a separately defined finance scope. An Odoo setting alone does not determine a group’s legal or tax position.

Review the subscription before activating another company

The Odoo 19 documentation says enabling multi-company on Standard triggers an upsell to Custom, excluding One App Free databases. It describes a 30-day limit on the upsell order for yearly or multi-year contracts, and the new rate applying on the next invoice for monthly contracts 1.

These are documented conditions, not a quotation for your project or a promise about a particular contract window. Check your plan, hosting and agreement with the subscription owner before implementation. Then separate licence cost from company setup, data preparation, integration and training effort.

Deliverables to agree before wider rollout

With your team, we map companies, branches and warehouses, record ownership, user access and the sequence of documents between entities. We then choose a sale, purchase, delivery and return sample and reconcile it with finance and warehouse owners. This clarifies the roles of Finance, Sales and Inventory in a retail and wholesale business.

Decide who starts the transaction, who approves the counterpart and how discrepancies in price, quantity or active company are handled. A project can begin with two entities and a representative transaction, then expand after acceptance. The sales and inventory demo shows the general interface only; multi-company and consolidation checks belong in an environment for the agreed licensed version and setup.

Acceptance checks

  1. Create a document in A and then B; compare company, account and warehouse with the intended owner.
  2. Use a single-company test user and check that other-company documents remain outside their permissions.
  3. Run an inter-company transaction and establish whether the counterpart is a draft or validated, according to configuration.
  4. Reconcile product, quantity, price, dispatch and receipt, then test the return.
  5. Reproduce the management example and explain 4,800 versus 2,400 revenue and 2,000 versus 1,800 inventory.
  6. Have finance accept the report and adjustment process rather than using access to several companies as the only completion criterion.

FAQ

Does every branch need another company? No. Start with the entity, books and ownership of documents, then use a branch, warehouse or analytical separation when that meets the need.

Are counterpart transactions automatically validated? That depends on configuration. Test which document is created, its state and its approval owner. Creating a draft, posting it and paying it are different events.

Is one database enough to consolidate the group? Odoo documents consolidation tools, but mapping, adjustments, the reporting ledger and review still need to be defined within the applicable scope and accounting framework.

Start with one transaction between two entities

Bring an entity map, a representative transaction and a report you need to review, then discuss them with us. That sample helps distinguish standard configuration from interfaces or additional work. Return to the Odoo application for your business and project cost estimate to build a clear scope.

Source notes

[1] Odoo 19 documentation on Multi-company and Consolidation: company context, shared records, counterpart transactions, plan conditions, mapping and adjustments.

[2] IFRS Foundation, the public definition and purpose of IFRS 10 Consolidated Financial Statements. Public standard overview.