Odoo 20 documents an intercompany clearing workflow for a specific multi-company accounting scenario: one company receives a customer payment for an invoice issued by another company in the same Odoo database. The system can reconcile the issuing company’s open invoice and create balancing accounting entries between the two entities. (Odoo 20.0 Docs: Companies Multi Company) Odoo announced Odoo 20 on 24 September 2026. (Meet Odoo 20)
The workflow addresses both sides of the transaction. In the company that issued the invoice, the customer receivable becomes a claim against the company that collected the payment. The receiving company records the corresponding amount as payable to the issuing company. This clears the customer balance while retaining the financial obligation between the two companies. (Odoo 20.0 Docs: Companies Multi Company)
What the workflow covers
The documented use case begins with an invoice belonging to one company and a payment received by another. Both companies must be configured in the same Odoo database. Processes involving separate databases or external accounting systems are not part of the documented workflow. (Odoo 20.0 Docs: Companies Multi Company)
When a payment is processed under the required configuration, Odoo reconciles the original customer invoice and generates the intercompany entries. The automation links invoice reconciliation to the internal balance between the participating companies. It does not eliminate that balance. Instead, it records the amount against the configured intercompany accounts. (Odoo 20.0 Docs: Companies Multi Company)
The accounting treatment separates the customer relationship from the relationship between the companies. After clearing, the issuing company no longer carries the settled amount as an open customer receivable. It records a receivable from the company holding the payment, while the receiving company recognises the matching payable. (Odoo 20.0 Docs: Companies Multi Company)
Required Odoo configuration
A multi-company database alone is not sufficient. Odoo’s Intercompany Payment - Account module must be installed, and Inter-Company Transactions must be enabled for every company participating in the workflow. (Odoo 20.0 Docs: Companies Multi Company) Existing multi-company implementations should check both requirements before attempting to process these payments.
Each participating company also requires a clearing journal and dedicated intercompany payable and receivable accounts. These accounts control where the obligations between the entities are recorded. (Odoo 20.0 Docs: Companies Multi Company) The design should be reviewed against the chart of accounts, entity-level reporting and intercompany reconciliation requirements before transactions are processed.
The payment method must use an outstanding receipts account. (Odoo 20.0 Docs: Companies Multi Company) This prerequisite should be checked in the current payment configuration, particularly where bank journals, receipt processing or account mappings have been customised. Installing the module and configuring intercompany accounts will not, by themselves, satisfy the documented requirements if the payment method lacks the required outstanding receipts account. (Odoo 20.0 Docs: Companies Multi Company)
Accounting implications
The workflow combines customer reconciliation and the creation of matching intercompany entries. (Odoo 20.0 Docs: Companies Multi Company) Without that connection, finance teams may need to handle the customer balance and the obligation between the companies as separate accounting steps. Whether the automated process is suitable depends on the organisation’s payment flows and its ability to support the required account structure.
A payment collected by one company for another company’s invoice is not treated by this workflow as revenue of the receiving company. The documented entries establish a payable in the receiving entity and a corresponding receivable in the issuing entity. (Odoo 20.0 Docs: Companies Multi Company) During testing, finance teams should inspect the generated journal entries and confirm that the customer, intercompany and outstanding receipts balances use the intended accounts.
Configuration applies to each participating company rather than operating as a single database-wide setting. (Odoo 20.0 Docs: Companies Multi Company) Companies sharing one Odoo environment may have different charts of accounts, journal structures or payment methods, so each entity’s setup should be validated separately.
Limits of the documented workflow
The documentation describes the accounting purpose of the workflow and identifies its module, company setting, journal, account and payment method requirements. (Odoo 20.0 Docs: Companies Multi Company) It does not establish how every customisation, localisation or external integration will behave with intercompany clearing. Those areas require implementation-specific review.
The workflow is documented for companies held in the same database. (Odoo 20.0 Docs: Companies Multi Company) The supplied sources do not confirm an equivalent automated process between separate Odoo databases. Organisations using separate instances should therefore verify their required cross-database process independently.
The supplied sources also do not define the workflow’s treatment of partial payments, refunds, foreign-currency settlements, payment reversals or chains involving additional companies. If these transactions are material to an organisation, each case should be tested before operational use.
What to verify before adoption
First, confirm that the invoicing company and the company receiving the payment are in the same Odoo database. Check that the Intercompany Payment - Account module is installed and that Inter-Company Transactions is enabled for every company intended to participate. (Odoo 20.0 Docs: Companies Multi Company)
Second, review the clearing journal and dedicated payable and receivable accounts for each entity. (Odoo 20.0 Docs: Companies Multi Company) The account choices should support the organisation’s reporting and reconciliation requirements. Users should be able to identify the amount due from the company that received the payment and the matching amount owed to the company that issued the invoice.
Third, inspect the payment method and confirm that it uses an outstanding receipts account. (Odoo 20.0 Docs: Companies Multi Company) Check the actual configuration rather than relying on the journal name or assumptions based on an existing receipt process.
Finally, run a controlled transaction using a representative invoice and payment. Confirm that Odoo reconciles the customer invoice, records the issuing company’s intercompany receivable and creates the corresponding payable in the company that received the money. (Odoo 20.0 Docs: Companies Multi Company) Review both company ledgers before wider use so that account mappings and entity-level balances can be checked.
The result should leave the customer invoice reconciled while showing the amount between the two companies in their respective intercompany accounts. That distinction is central to the workflow: customer settlement is completed, but the separate obligation between the issuing and receiving entities remains visible for later reconciliation. (Odoo 20.0 Docs: Companies Multi Company)