How do you reconcile intercompany accounts across entities and currencies?

Your matching report shows nearly every intercompany line paired, yet the US receivable still disagrees with the German payable. Matched transactions explain activity, but they do not support an ending balance when entity records, currency treatment, or posting periods differ.

Direct answer

Reconcile each entity's intercompany account at the balance level by tying both sides to source and to the identified counterparty account. Bridge them through transaction, functional, and reporting currencies, and classify every residual by cause. Treat an exception as closed only when evidence supports it, and keep everything else open with an owner and an age, even if a matching rule paired the underlying lines.

Three conditions for a substantiated balance

• Both balances tie to source. Tie each entity's ending GL balance to its supporting activity and the identified counterparty account, rather than treating matched transactions as the completed reconciliation.

• The currency bridge is explained. Show how transaction, functional, and reporting currency amounts connect, using the applicable rates and posted journals.

• Residuals stay visible. Keep every remaining difference visible with its cause, owner, aging, supporting evidence, and reviewer decision.

Trace the difference to an entity, account, book, and currency

Before you classify a break, you need to know exactly where it lives, because "intercompany is off by $40K" is not something anyone can fix.

Build a two-sided account bridge

Put both entities on one page, side by side, for the same period and the same counterparty pair. Most breaks become obvious once the two ledgers sit next to each other at account level.

• Show the period, book, legal entity, counterparty, GL account, opening balance, period activity, adjustments, and ending balance for each side.

• Tie each ending balance to source detail, then identify items that appear on only one side. ERP intercompany reports, such as Oracle's, let you drill from a receivable/payable difference to the journal lines behind it.

• Preserve separate account-level balances even when a group-level net looks immaterial. A $300K overstatement and a $295K understatement net to noise, but they are two problems.

• Record the extraction date so the preparer and reviewer compare the same posting population. Late journals on day 4 of close can quietly change the answer.

Compare like currency amounts before calling a break FX

Distinguish the transaction currency from each entity's functional currency and the group reporting currency. Retain the rate type, rate date, and remeasurement or translation journal used in the bridge, consistent with how IAS 21 separates those layers.

Take a $100 receivable against a €92 payable: at an illustrative €0.90 per $1 comparison rate, the receivable equals €90, and the €2 difference needs a rate-and-journal explanation or remains open. Do not label it FX solely because the entities use different currencies.

Classify exceptions without hiding unresolved balances

Once you locate the difference, classify it by the evidence that explains it, not by the label that closes it fastest.

Which type of break is it?

If a break fits no row cleanly, it belongs in the last one.

When is an exception still open?

A proposed match, consolidation elimination, or offsetting group total does not by itself support either entity's GL balance. An item remains open whenever its cause or balance-sheet treatment lacks evidence, even if a transaction-matching rule pairs the underlying lines.

Substantiate the ending balance and retain the review trail

Classification tells you what a difference is, and substantiation proves the account balance is right despite it.

Tie the account, not just its matched transactions

The preparer reconciles opening balance plus activity and posted adjustments to the ending GL balance. Then they tie supported open items to the counterparty's detail, so both entities agree on what is in transit.

Show supported timing items separately from unexplained differences, with amounts and aging in each relevant currency bucket. Oracle Account Reconciliation's balance summary makes this split explicit, distinguishing adjustments from unexplained differences.

What must the reviewer be able to re-perform?

• Dated GL extracts, counterparty support, and source-to-journal links.

• The rate source, calculation, policy basis, and any posted FX adjustment.

• Exception decisions, owners, aging, and evidence of subsequent clearing.

• Preparer and independent reviewer identities, notes, approvals, and any changes made after review.

Do not sign off an unexplained amount as cleared merely because it falls below a matching tolerance.

Which account reconciliation software handles large-enterprise currency exceptions in 2026?

The category is growing fast, with one 2026 comparison sizing the close automation market at $5.8 billion with 12% CAGR, so compare tools by the work they perform, not by feature lists.

Compare the work each operating model performs

The same comparison expects AI-driven reconciliation to cut close times by 30% to 50%. The gain comes from shifting teams toward exception-focused accounting, not from pushing match rates higher.

Where does Maxima fit, and where is the boundary?

Vendors set high automation benchmarks; Trintech, for example, claims a 99% reduction in preparation time. Maxima's approach is different in kind. Its agents prepare the reconciliation itself, pulling GL detail, tying it to source, and carrying unreconciled items forward with lineage, while accountants review.

• Fit: Continuous preparation surfaces exceptions the day they occur, and transaction-level lineage lets you review a supported balance instead of assembling evidence during close week.

• Boundary: An agent-prepared match does not settle an intercompany dispute or set FX policy. Nothing posts without human approval, and the independent reviewer remains the control.

What matters more than a match rate?

• [ ] Can you trace both entity balances to source records and the GL?

• [ ] Can you see the currency bridge and a separately aged residual by account?

• [ ] Can the reviewer inspect the evidence and withhold sign-off on an unexplained balance?

Frequently asked questions

What should account reconciliation software for a large enterprise prove?

Gartner frames reconciliation solutions as standardized workflows that replace manual effort, but at enterprise scale the software must prove more: account-level completeness, entity and currency visibility, and owned exceptions. It should produce independently reviewable support for every balance, not just transaction-match volume.

How does account reconciliation automation in 2026 handle entity-currency exceptions?

Automation collects balances, calculates currency bridges, flags differences, and prepares the evidence package. Accountants still decide whether a residual is supported timing, a genuine FX effect, or an unresolved balance.

Which top accounting automation software handles complex balance-sheet reconciliation?

It depends on your bottleneck: Oracle Account Reconciliation suits currency-bucket certification, and BlackLine or Trintech suit dedicated intercompany resolution. If agent-prepared, evidence-linked account work is the priority, consider Maxima.

Conclusion

A matched transaction explains activity, while a substantiated intercompany account reconciliation explains both ending balances, every currency bridge, and every entity exception. Hold that standard through review, and the unsupported receivable stops surviving another close.