At 6:30 PM on the last day of the month, a group finance team discovers a ₹5 lakh discrepancy between two subsidiaries. The Indian entity reports a ₹48 lakh receivable, while its European counterpart records only ₹43 lakh as payable.
Both teams have completed their entries, yet the balances do not match. The difference is delaying the month-end close, and finance needs to find out why.
The problem could be a missing invoice, an incorrect posting, a timing difference, or a currency conversion error. Simply adjusting the closing balance will not solve it. The team must trace the discrepancy back to the transaction that caused it.
Start by comparing the intercompany ledger entries of both entities for the same reporting period.
Review invoice numbers, posting dates, transaction amounts, currencies, and counterparty details. Instead of comparing only closing balances, match individual transactions to identify missing or inconsistent entries.
In our example, the Indian entity has recorded three invoices worth ₹20 lakh, ₹16 lakh, and ₹12 lakh. The European entity has recorded the first two but shows only ₹7 lakh against the third.
The difference is now linked to a specific invoice, giving the team a clear starting point.
Once the unmatched transaction is identified, check the original invoice, purchase order, goods receipt, or journal entry.
The European team may have received an invoice for ₹12 lakh but recorded only ₹7 lakh because one line item was excluded during processing. Reviewing the source document confirms the error.
The receiving entity can then correct the entry, retain the supporting evidence, and rerun the reconciliation.
The key is to correct the original transaction rather than post an unexplained adjustment to force the balances to agree.
Sometimes, both entities record a transaction correctly but in different accounting periods.
For example, one subsidiary records a sale on 30 September, while the receiving entity records the purchase on 2 October after receiving the goods. The September balances may not match even though both entries are valid under their respective processes.
Compare posting dates, invoice dates, goods receipt records, and month-end cut-off policies. Document legitimate timing differences and track them until the corresponding entry appears. If the cut-off was handled incorrectly, assess the required correction.
Foreign exchange can complicate reconciliation when entities operate in different functional currencies.
Suppose a subsidiary invoices another group entity €50,000. Both record the same invoice, but their reported amounts differ because of an incorrect exchange rate or inconsistent application of accounting policies.
Check the original transaction currency, the exchange rate applied, and the resulting functional-currency amounts. If the invoice values match in the original currency, investigate translation or revaluation differences before treating the discrepancy as a posting error.
A transaction may exist in both ledgers but be assigned to the wrong group entity or general ledger account.
For example, a subsidiary records a payable against the wrong counterparty because two group entities have similar names or codes. The total payable may be correct, but the balances between the intended entities will not match.
Compare counterparty codes, account mappings, and journal references. Correct the coding error and verify that the relevant balances now agree.
Maintain an exception list that records the transaction, discrepancy amount, suspected cause, responsible team, corrective action, and resolution date.
For instance, the ₹5 lakh difference in our opening scenario can be assigned to the European accounts payable team, with invoice correction as the required action.
Classify recurring issues as missing entries, timing differences, currency variances, or coding errors. This helps finance teams identify patterns instead of investigating the same problems every month.
Resolving a discrepancy is only part of the job. Finance teams must also address the process that caused it.
Repeated invoice errors may require stronger validation checks. Timing issues may call for earlier cut-off procedures, while counterparty errors may require standardised codes across ERP systems.
Automated reconciliation tools can match transactions using agreed criteria, flag exceptions, and route them to the right teams. This reduces manual comparison work and allows finance professionals to focus on discrepancies that require judgement or further investigation.
Effective Intercompany Reconciliation requires tracing unmatched transactions to their source rather than clearing discrepancies through unexplained adjustments. By reviewing individual entries, verifying supporting documents, checking timing and currency differences, and correcting coding errors, finance teams can resolve mismatches accurately.
Addressing recurring issues at their source, supported by clear ownership, consistent controls, and automated transaction matching, helps businesses streamline intercompany reconciliation, reduce manual effort, and improve the accuracy and reliability of month-end financial reporting.
