Intercompany reconciliation confirms that related legal entities have recorded corresponding transactions and balances on an agreed basis. A reported zero difference is not always proof of reconciliation: both sides may be missing, incorrectly paired or translated using unsupported exchange rates.
What makes a valid reciprocal pair?
Define an unambiguous transaction or settlement reference, posting entities, partner entities, document dates, settlement terms, currencies and signed amounts. The expected sign convention must be documented: for example, one entity’s receivable of $4,000 and the counterpart’s payable of −$4,000. Without consistent conventions, a simple sum-to-zero test can mislead.
Start with the source-currency bridge
Where both sides report in the same currency, compare directly first. For example:
| Entry | Reporting amount | Review |
|---|---|---|
| Entity A: receivable from B | +$4,000 USD | Source document required |
| Entity B: payable to A | −$4,000 USD | Counterparty posting required |
| Paired net difference | $0 USD | Not automatically approved |
The $0 difference is only one test. It must also be shown that exactly one eligible pair exists, the values are independently recorded, neither entry is zero merely because a field is blank, and both sides carry valid evidence and review decisions.
When the entities use different functional currencies
Use a controlled FX rate master with source currency, reporting currency, rate, effective date or period, rate type, source evidence and independent reviewer. Define whether a rate expresses 'reporting units per one source unit' or its reciprocal. Mixing the two conventions can magnify rather than resolve differences.
Fictional demonstration rate: if a permitted policy rate is 1 EUR = 1.10 USD, then €2,000 translates to $2,200. This is a teaching example, not a market rate or an approved production FX rate. Production translation requires the appropriate effective-dated rate, evidence and reviewer.
Six controls a reconciliation system must enforce
- Two-sided existence: no side may be called reconciled if the reciprocal entry is absent.
- Uniqueness: more than one potential matching counterpart is an ambiguity hold, not a successful match.
- Independent review: each side’s reviewer is independent of its preparer under policy; normalise names before comparison so trailing spaces do not bypass the rule.
- Evidence completeness: whitespace-only source references, names and review notes are effectively blank.
- Effective-dated FX: select an eligible rate for the transaction date and prescribed policy, not simply the newest entry in the workbook.
- Zero-amount protection: two zero postings must not inflate the count of reconciled value-bearing transactions.
What a good exception register tells management
Distinguish missing reciprocal entries, timing differences, wrong entity/counterparty, invoice-versus-credit sign mismatch, duplicate pair candidates, currency mismatch, unsupported FX source, expired review and material value differences. Assign each to an owner with next action and review date.
Example: A posts $5,000 receivable on 30 September and B records $5,000 payable only on 2 October. Depending on cutoff and consolidation policy, this may be an explained timing difference. It should still appear in a dated reconciling schedule rather than being fabricated as a matched September pair.
Frequently asked questions
Does a zero net difference mean reconciled?
No. It means the mathematical net is zero for the records included. Eligibility, evidence, pair uniqueness and approvals still matter.
Should a missing FX source stop reconciliation?
Yes when the control design requires a verified production rate; use a hold rather than inventing an exchange rate.
Can one person review both sides?
The organisation's segregation-of-duties policy determines reviewer assignment. The system should enforce the configured independence requirements and retain a review trail.
Related reading: month-end reconciliation workflow and free AP Month-End Checklist.
General control guidance. The example rate is fictional. Financial approval and FX policy remain with the customer.
Put this into practice: Multi-Entity Finance Control Hub reconciles intercompany balances across entities at verified FX rates, checked from both sides. Macro-free Excel with a Worked Example and a Blank edition, one-time payment, instant download. Or start with the free AP Month-End Close Checklist (printable PDF).