Intercompany Reconciliation

By Nupur Mittal

Co-founder at OCTA — works with accounting firms on month-end close and reconciliation automation.

Intercompany reconciliation is the process of matching the receivable and payable balances that group entities carry against each other, resolving any difference, and producing the journal entries that eliminate those balances on consolidation. Because each entity keeps its own books — often in its own currency — the same intercompany relationship rarely lands on the same number twice without work. This page walks through the full reconciliation process, a worked FX/timing example, the controls a rigorous reviewer applies, and how accounting and consolidation teams run it faster with OCTA Flow while a human approves every entry.

Why intercompany reconciliation matters, and where it goes wrong

Every group with more than one legal entity generates intercompany transactions — management fees, cost recharges, inventory transfers, loans, cross-charges for shared services. Each side of the transaction gets booked independently, by different people, in different systems, sometimes in different currencies and different periods. Left alone, those two independent bookings drift: one entity records a charge before the other records the matching expense, an exchange rate moves between the transaction date and period end, a payment is remitted but not yet applied on the receiving side. None of that is unusual — it's the normal mechanics of a multi-entity group. What's not optional is catching every one of those differences before consolidation, because an unreconciled intercompany balance doesn't net to zero on the consolidated balance sheet — it either overstates the group's assets and liabilities or, worse, leaves unrealized intercompany profit sitting in the numbers.

For a controller or consolidation team, the pain is coordination as much as arithmetic. Reconciling IC balances means matching pairs of entities against each other, often across a currency boundary, then chasing down whoever on the other side can explain a gap — a process that gets slower and more error-prone the more entities and currencies are in the group. A stale, unresolved IC difference that gets carried forward quarter after quarter is one of the most common findings in a consolidation review, and one of the most avoidable. The goal is a fully reconciled, fully explained IC balance for every entity pair, every period, with clean elimination entries ready for consolidation — not a plug that gets buried in a "miscellaneous" line.

The intercompany reconciliation process, step by step

A rigorous intercompany reconciliation follows the same sequence regardless of group size. The steps below are the full procedure OCTA Flow executes; they also stand alone as a best-practice process any consolidation team can follow.

1. Map the group structure. Identify every entity in the group, its functional currency, its ownership percentage, and the consolidation currency the group reports in. Note any partially owned entities — they matter for minority-interest treatment later, even though the IC elimination itself is unaffected by ownership percentage.

2. Load the exchange rates. Gather the period-end (closing) rate and the average rate for each functional-currency pair in the group. Both matter: the closing rate translates IC balances for the balance sheet; the average rate is used for IC revenue and expense flowing through the income statement.

3. Match each IC balance pair. For every intercompany relationship — Entity A's receivable from Entity B against Entity B's payable to Entity A — convert both amounts to the consolidation currency at the period-end rate and compare them. A difference of $0 means that pair is reconciled. Anything above zero needs investigation.

4. Diagnose the source of each difference. In practice, nearly every IC difference falls into one of four categories:

• In-transit items — one entity has recorded and remitted a payment; the counterparty hasn't yet recorded the receipt. A timing difference that typically clears in the next period.
• Foreign currency translation — each entity books the transaction in its own functional currency at its own transaction-date rate; retranslating to the consolidation currency at the period-end rate produces a gap even when the underlying transaction is identical.
• Unrecorded transactions — one entity has booked a charge, fee, or credit that the counterpart hasn't recorded yet.
• Incorrect entity coding — a transaction posted against the wrong intercompany entity code, which shows up as a mismatch on both sides.

5. Drill into transaction-level detail on anything unresolved. For pairs that don't tie, match individual intercompany transactions between the two entities by reference number, date, and amount to isolate the specific item causing the gap, rather than treating the whole balance as one unexplained figure.

6. Reconcile intercompany revenue and expense, not just balance-sheet balances. Confirm that IC revenue recorded by one entity equals the corresponding IC expense recorded by the counterpart, translated to the consolidation currency. A mismatch here means unrealized intercompany profit is sitting in the group's numbers and needs to be eliminated, not just the balance-sheet receivable and payable.

7. Produce the elimination entry for every reconciled pair. Once an IC pair ties — after FX and timing items are explained — prepare the consolidation elimination: Dr IC Payable / Cr IC Receivable for the agreed amount, by entity pair.

8. Document what doesn't reconcile. For any pair that can't be fully tied out before the close deadline, record the difference amount, the probable cause, and whether the group needs an adjusting entry before consolidation or can carry a documented, immaterial timing difference into next period.

A worked example: an FX and timing difference, reconciled

Most real IC differences are a mix of a currency translation effect and a timing item, not one clean cause. Here's a worked example for a single entity pair at period-end, where the group's consolidation currency is USD.

The setup: Octa US, Inc. (the parent, functional currency USD) has an intercompany receivable from Octa UK Ltd. (a wholly owned subsidiary, functional currency GBP), for a GBP 100,000 management-fee balance. Octa US booked its USD receivable at the transaction-date rate (GBP 1 = $1.2578); consolidation retranslates GBP balances at the period-end closing rate (GBP 1 = $1.2500). During the period, Octa UK Ltd also remitted part of the balance — GBP 4,000 — on the last business day, which Octa US had not yet applied to its receivable ledger as of period-end.

Both sides tie at $125,000.00. The $780 gap was a pure FX translation effect — the same GBP 100,000 balance, retranslated at two different points in time — and gets recorded as a cumulative translation adjustment rather than an IC correction. The $5,000 remittance is a timing item that will show as a cleared receipt on Octa US's books next period.

Because the pair is now reconciled, the consolidation elimination entry is:

Memo: Eliminates the Octa US ↔ Octa UK Ltd. intercompany management-fee balance for Q4. $780 FX translation difference recorded to CTA; $5,000 in-transit remittance expected to clear in the following period.

Key controls and red flags

Matching two numbers is the easy part of intercompany reconciliation. What separates a reliable IC close from a rubber-stamped one is what a careful reviewer specifically watches for:

• IC differences above the group's tolerable threshold — commonly a fixed dollar amount (e.g., $5,000) or a percentage of the balance (e.g., 1%), whichever is more conservative for the pair
• Differences that persisted from a prior period — an IC gap that shows up two periods running is no longer a timing item; it's an unresolved error
• IC receivables and payables denominated in different currencies — inherent translation risk that needs to be tracked pair by pair, not assumed away
• Unrealized intercompany profit in inventory — IC revenue/expense mismatches that indicate profit embedded in inventory hasn't been eliminated
• IC balances against parties outside the group — a balance coded as intercompany that belongs to a third party, or vice versa, which points to a misclassification
• Intercompany loans without a confirmed agreement — a loan balance neither entity has formally confirmed the terms of
• Transfer-pricing exposure — IC pricing that looks inconsistent with an arm's-length standard, which is a tax and audit risk beyond the reconciliation itself

Catching these consistently, for every entity pair and every period, is what turns intercompany reconciliation from a spreadsheet exercise into an actual consolidation control.

What a completed intercompany reconciliation produces

A finished IC reconciliation isn't just a matched balance — it's a documented package a consolidation reviewer can sign off on and an auditor can follow end to end. A complete intercompany reconciliation package includes:

How OCTA Flow automates intercompany reconciliation

OCTA Flow does the matching, the currency translation math, and the entity-pair diagnostics for you, and leaves the judgment calls — and the sign-off — with your team. The workflow mirrors the process above:

1. Pick the Intercompany Reconciliation Skill. Flow already knows the full procedure: map the group structure, translate balances to the consolidation currency, match entity pairs, diagnose FX and timing differences, and draft the elimination entries.
2. Connect your data. Point Flow at the group's accounting systems, or upload the period's files — the group structure and functional currencies, the IC receivable/payable balances by entity pair, exchange rates, and transaction-level detail where you have it.
3. Run. Flow translates every IC balance to the consolidation currency, matches each entity pair, and sorts the differences into FX translation, in-transit, unrecorded, or miscoded — building the entity-pair matrix as it goes.
4. Review findings by severity. Instead of a wall of matched pairs, Flow surfaces the entity pairs and transactions that need attention — ranked by severity, each with a plain-English explanation and a recommended action: resolve the entry, notify the counterparty entity's finance team, record the elimination, or escalate to group finance. Your team works the exceptions, not every pair.
5. Sign off. Once every pair ties out or is documented, Flow assembles the elimination entries and the full reconciliation package with the audit trail intact.

The result: the entity-by-entity matching and rate math that used to eat a consolidation team's week gets done in a fraction of the time, and your people spend their hours on the handful of pairs that actually need a phone call.

Control and trust: Flow proposes, you approve

This matters most in a multi-entity close, where a wrong elimination entry doesn't just misstate one set of books — it misstates the consolidated financials for the whole group. OCTA Flow never writes to your books on its own. Every elimination entry and every correction is a proposal that a person reviews and confirms before anything is posted. Flow does the matching and the currency math and shows its reasoning; your team makes the call.

That control model runs through the whole reconciliation:

• Findings, not silent changes. Flow raises what it found and what it recommends for each entity pair — you decide.
• Severity and escalation built in. A persistent, unresolved IC mismatch is flagged as critical and can be escalated to group finance or an external auditor rather than quietly carried forward another period.
• A complete audit trail. Every match, every proposed elimination, every approval and override is logged, so the reconciliation is fully traceable end to end — exactly what a consolidation review and an audit both need.

You get the speed of automated entity-pair matching with the accountability of human sign-off on every elimination that touches the consolidated financials.

What the reconciliation draws on

To run an intercompany reconciliation, Flow uses the same sources a consolidation preparer already works from:

• Group structure — the entities in the group, their functional currencies, and ownership percentages (required)
• IC receivable/payable balances — each entity pair's intercompany balance as carried on both sides (required)
• Exchange rates — period-end and average rates for each functional-currency pair in the group (optional, but needed wherever an IC pair crosses a currency)
• Intercompany transaction detail — individual IC transactions, used to drill into a pair that doesn't tie at the balance level (optional)
• IC revenue and expense data — to confirm intercompany revenue on one entity's books equals the matching expense on the counterpart's (optional)

Flow works from whatever the group has connected — it matches each input by its purpose, so it doesn't matter which ERP or accounting system each entity runs, or what the exported files are named.

Related skills and terms

Frequently Asked Questions

What is intercompany reconciliation? It's the process of matching the receivable and payable balances that entities within the same group carry against each other, explaining any difference, and producing the journal entries that eliminate those balances when the group's financials are consolidated. It's a required step before any multi-entity close.

What is an intercompany elimination entry? It's the journal entry that removes an intercompany balance from the consolidated financials once both sides of the entity pair have been reconciled — typically Dr IC Payable / Cr IC Receivable for the agreed amount. Without it, the same balance would appear twice in the group's numbers: as an asset on one entity's books and a liability on another's.

Why don't intercompany balances match automatically? Each entity keeps its own books, often in its own functional currency, and records its side of a transaction independently. Exchange-rate movement between the transaction date and period-end, payments in transit, and simple timing lags between when each entity posts its side are the most common causes — not fraud or error, just the normal mechanics of separate ledgers.

How do you handle FX differences in intercompany reconciliation? Translate both sides of the IC balance to the group's consolidation currency at the period-end rate before comparing them. A gap that remains purely because one entity booked at a historical rate and the other retranslated at the closing rate is a translation difference, not an error — it typically gets recorded as a cumulative translation adjustment rather than corrected in either entity's ledger.

How often should intercompany balances be reconciled? At least every reporting period, before consolidation. Groups with high IC transaction volume or multiple currencies often reconcile monthly even if they only report quarterly, so differences don't compound across periods.

Can intercompany reconciliation be automated? The entity-pair matching, currency translation, and diagnosis of FX versus timing differences can be automated and reviewed, while the judgment on what to escalate and how to resolve a genuine mismatch stays with your team. That's the model OCTA Flow uses.

Does OCTA Flow post elimination entries directly? No. Flow proposes every elimination and adjusting entry; a person on your team reviews and approves before anything is posted. Nothing is written automatically to any entity's books.

See how consolidation teams tie out intercompany balances faster, with human sign-off on every elimination → start a 30-day OCTA Flow trial.