When one company records an amount due from a related entity, the other company should have a corresponding amount due to it—subject to the transaction, timing, currency and accounting treatment. The reconciliation starts by matching both sides of the same economic event.
Receivable / intercompany asset
Payable / intercompany liability
A difference can be caused by an invoice on only one side, a payment recorded on different dates, inconsistent currency treatment, a credit note, or an entry coded to the wrong intercompany partner. Comparing the ending balances is the starting point, not the full investigation.
List open receivables or amounts due from the related entity. Include invoice references, dates, currency and payments/credits applied.
Locate the corresponding payable or due-to entry. Confirm both sides refer to the same legal entities and transaction.
Classify each difference as timing, missing entry, payment application, currency/rounding, coding, or a genuine accounting correction. Assign an owner and resolution date.
The exact entries depend on the legal entities, agreements, tax considerations and accounting policies. These examples show the kind of counterpart trail to look for.
A services company charges a related operating company. The seller records the receivable and relevant income; the buyer records the payable and applicable expense or asset. The counterpart values and cut-off dates should be explainable.
One entity pays a vendor invoice that partly belongs to another entity. The allocation should be supported, documented, and recorded consistently on both sides.
The paying entity may record a transfer while the receiving entity hasn't entered or matched the receipt. Bank date, payment reference and reconciliation status help identify the gap.
Different currencies, exchange rates, transaction dates, rounding or period cut-off can create apparent differences even where the source transaction is understood.
Enter balances from both sides in the same comparison currency and for the same reporting scope. The result is a triage aid—not a journal-entry recommendation.
Confirm both balances relate to the same entities, date range, transaction population and currency basis.
Company A's balance is higher by $600.00. Investigate unmatched transactions before making an adjustment.
Work from source documents toward the ledger. Avoid posting a plug entry simply to make the two closing balances equal.
Use the same related entities, period-end date, currency basis and balance definition on both sides.
Capture invoice/bill number, date, partner, reference, currency, amount, due date and payment status where available.
Pair each seller-side receivable or recharge with the matching buyer-side payable, expense, asset or other relevant entry.
Separate timing, missing entry, payment matching, currency/rounding, partner coding and genuine accounting corrections.
Post approved corrections in the proper company and period. Preserve support and cross-reference the counterpart entry.
Confirm residual differences are zero or explicitly explained, assigned to an owner and approved for follow-up.
The receivable, payable, revenue, expense, asset, cash or loan entries must reflect the underlying transaction for each entity, based on the applicable agreements and accounting treatment.
Where consolidated financial statements are prepared, qualifying intercompany balances and transactions may need elimination under the applicable consolidation process. Do not assume that matching company ledgers automatically means consolidations or eliminations are configured or posted.
Odoo menus and automation depend on version, apps and database configuration. Validate these design points in a test environment before changing a live accounting workflow.
Confirm each legal entity is configured correctly, the intercompany partner is identifiable on transactions, and users post in the intended company context.
Review the accounts used for intercompany receivables/payables and related income, expenses, assets or liabilities. Confirm account types and reporting treatment.
If intercompany documents are generated automatically, test invoice/bill pairing, taxes, journals, references, partner selection and duplicate prevention.
Confirm transaction currency, company currency, date/rate logic and period-lock procedures are understood by both sides of the process.
Use one shared checklist for all related entities and maintain a clear exception log.
Common causes include an invoice or bill recorded on one side only, payment timing, unmatched credits, incorrect partner or account coding, currency differences, rounding, or transactions posted in different periods. Compare the source documents, not only the totals.
A due-from balance generally represents an amount one entity expects to receive from another. A due-to balance generally represents the related entity's obligation to pay. The two sides should be compared for the same transaction, date and currency basis.
Do not assume so. Automation and consolidation capability depend on the version, installed apps and configuration. Intercompany transaction creation, entity-level reconciliation and consolidation eliminations are separate controls that should be tested and documented.
Not before investigating the difference. Identify the unmatched source transaction and determine the correct entity, account, period and currency treatment. Corrections should be supported and approved, and both sides should be considered.
At minimum, set a documented review cadence aligned with the month-end close and reporting needs. High-volume or material intercompany activity may benefit from more frequent matching so exceptions do not accumulate until period-end.
Accountrise helps US businesses and accounting firms clean up Odoo accounting, reconcile intercompany balances, investigate ledger differences and build repeatable month-end procedures.
Accounting support starting at $10/hour. Final pricing depends on scope, transaction volume, complexity and engagement requirements.