Intercompany reconciliation: automating the most painful part of the close

If you ask a controller to name the single most painful task in the monthly close, the answer is almost always the same: intercompany reconciliation. Not because it is conceptually difficult - debits on one side should equal credits on the other - but because the practical reality of reconciling across entities, currencies, and time zones makes it consistently harder than it should be.

Intercompany accounts are where the close breaks down. They are the last accounts to reconcile, the most likely to have unexplained variances, and the primary source of consolidation breaks that delay reporting. Understanding what intercompany elimination is and how it connects to financial consolidation is essential context for the automation strategies below.

Why intercompany reconciliation is uniquely painful

Standard account reconciliation, comparing your GL to a bank statement, for example,, involves two data sets that you control. You have the GL. You have the bank feed. Both are available on your timeline.

Intercompany reconciliation involves data that someone else controls. Entity A posts an intercompany receivable. Entity B needs to post the corresponding payable. If Entity B has not posted yet, or posted a different amount, or used a different exchange rate, or recorded it in a different period. You have a variance.

The specific pain points are predictable and recurring:

Entity pair complexity. A company with 20 entities has up to 190 unique entity pairs (n × (n-1) / 2). Each pair may have multiple intercompany accounts: receivable/payable, revenue/expense, loan/borrowing. The number of reconciliation points grows quadratically with the number of entities.

A 50-entity organization has 1,225 entity pairs. If each pair has three intercompany account types, that is 3,675 reconciliation points per period. The scale is punishing.

Currency mismatches. Entity A in the US records an intercompany sale in USD. Entity B in Germany records the corresponding purchase in EUR. Both are correct in their local currency, but when you translate to the reporting currency, the balances do not match because the entities used different exchange rates or translated on different dates.

Currency-related intercompany variances are among the most time-consuming to investigate because the root cause is not an error. It is a legitimate difference in accounting treatment that needs to be quantified and eliminated properly.

Timing differences. Entity A posts an intercompany invoice on March 28. Entity B processes the invoice on April 3. At March 31, Entity A has a receivable that Entity B does not have a corresponding payable for. The variance is real but temporary.

The challenge is distinguishing timing differences (which resolve next period) from genuine mismatches (which require correction this period). When you have hundreds of timing items across dozens of entity pairs, classification takes hours.

Dispute resolution. Entity A says the intercompany charge is $50,000. Entity B says it should be $45,000 because they dispute $5,000 of the allocation. Who is right? How do you resolve it before the close deadline? Who has the authority to approve the adjustment?

In many organizations, intercompany disputes are resolved through email chains that nobody can track. The same disputes recur period after period because there is no systematic resolution process.

How automation addresses each pain point

Arvexi's intercompany reconciliation module is purpose-built for multi-entity organizations. It automates the specific tasks that make intercompany reconciliation slow.

Auto-matching on reversed pairs

The engine automatically identifies matching intercompany transactions by looking for reversed pairs: Entity A's debit to Entity B should match Entity B's credit to Entity A. It matches on amount, date range, reference, and description using the same multi-layered matching logic as standard transaction matching: exact, tolerance, fuzzy, and pattern-based.

For each entity pair, the engine pulls both sides of every intercompany account, runs the matching, and presents the results: matched items (green), suggested matches (yellow), and unmatched items (red). Matched items are auto-reconciled. Suggested matches need one-click confirmation. Unmatched items trigger investigation.

Auto-match rates for intercompany transactions typically reach 85-92% after the first period, higher for organizations with standardized intercompany billing processes.

Currency translation alignment

The engine applies a consistent translation methodology across all entities. When both sides of an intercompany transaction are translated at the same rate, the variance disappears. When rate differences exist, the engine quantifies the FX variance separately from the operational variance.

This separation matters. An FX variance of $3,000 on a $500,000 intercompany balance is a translation artifact, not a process failure. A $3,000 operational variance on the same balance is a posting discrepancy that needs investigation. Lumping them together, which is what happens in a manual process,, obscures the real issue.

Timing difference classification

For unmatched items, the engine checks whether the counterparty entity posted the corresponding transaction in a subsequent period. If a debit posted by Entity A on March 28 has a matching credit posted by Entity B on April 3, the engine classifies it as a timing difference, estimates the resolution date, and carries it forward automatically.

Timing items that persist beyond the expected resolution window are escalated. Chronic timing differences on the same entity pair are flagged as process issues, prompting upstream correction rather than repeated manual reconciliation.

Dispute workflow

When two entities disagree on an intercompany balance, the engine creates a structured dispute with the variance amount, both entities' supporting documentation, and an assignment to the responsible party. Disputes are tracked with status, aging, and escalation rules.

The dispute workflow replaces the email chains. Both entities can see the dispute, attach documentation, propose resolutions, and approve final amounts. The full history is preserved for audit.

Netting and settlement

For organizations that settle intercompany balances periodically, the engine calculates netting amounts across all entity pairs. Instead of 50 entities each making bilateral payments to every counterparty (potentially 1,225 payments), the engine computes a netting schedule where each entity makes one net payment or receives one net receipt.

Netting reduces the volume of intercompany cash movements, which in turn reduces the volume of timing differences in subsequent periods. Fewer cash movements means fewer items to reconcile.

Elimination at first common parent

The end goal of intercompany reconciliation is not just matching. It is intercompany elimination. Intercompany balances and transactions must be eliminated in consolidation so that the consolidated financial statements reflect only external activity.

Arvexi generates elimination entries automatically at the first common parent entity in the organizational hierarchy. If Entity A and Entity B are both subsidiaries of Entity C, the elimination entry posts at Entity C. If Entity A is a subsidiary of Entity C and Entity B is a subsidiary of Entity D, and both C and D are subsidiaries of Entity E, the elimination posts at Entity E.

This hierarchy-aware elimination is automatic. As intercompany transactions are reconciled and matched, the corresponding elimination entries are generated and staged for review. By the time your team gets to consolidation, the elimination entries are already prepared.

The consolidation connection

Intercompany reconciliation and consolidation are two stages of the same process. Organizations that reconcile intercompany in one tool and consolidate in another create a handoff point where data can break, formats can mismatch, and time is lost.

Arvexi handles both in the same platform. Intercompany reconciliation feeds directly into financial close and consolidation. Elimination entries generated during reconciliation flow into the consolidation process without export, transformation, or re-entry. Currency translation uses the same rate tables. The organizational hierarchy is defined once and used everywhere.

The result: your close has one fewer handoff, one fewer data migration, and one fewer potential point of failure. This unified approach is a core advantage of Arvexi's Account Reconciliation platform: intercompany reconciliation and consolidation share the same data model, the same entity hierarchy, and the same audit trail.

Getting started with intercompany automation

If your organization has more than 5 entities, intercompany reconciliation is likely one of your most time-consuming close tasks. If you have more than 20 entities, it is almost certainly the bottleneck.

The starting point is mapping your entity pairs, identifying the intercompany account structure, and understanding where the current process breaks down. Is it matching? Currency? Timing? Disputes? Usually, it is all four.

Explore intercompany reconciliation in Arvexi's platform or request a demo to see how auto-matching, dispute workflow, and elimination generation work with your organizational structure.

Related reading

• What is Intercompany Elimination?
• What is Financial Consolidation?
• Intercompany Elimination - automated matching and elimination entries
• Intercompany Reconciliation - glossary definition