The finance team is preparing the month-end report when a discrepancy appears. The Indian subsidiary reports a receivable of ₹48 lakh from its UAE counterpart, but the UAE entity shows a payable of only ₹45 lakh.
Both teams check their ledgers. The invoices seem correct, yet ₹3 lakh remains unexplained. Closing is delayed while accountants compare entries and search for the cause.
This is not an isolated process concern. In a survey of more than 260 finance, accounting, tax, and treasury stakeholders at multinational companies, 35% identified delays in closing the books as a negative business outcome of intercompany challenges. The research was conducted by Dimensional Research and sponsored by BlackLine.
The underlying discrepancy could stem from a missed transaction, an incorrect exchange rate, inconsistent accounting practices, or differences in transaction timing. If these issues remain unresolved, they can complicate consolidation, distort intercompany balances, and delay reliable financial reporting.
Understanding where these errors originate is the first step towards preventing them. Here are six common intercompany reconciliation errors that finance teams should identify and address.
Consider a parent company that supplies raw materials to its manufacturing subsidiary on 30 September. The parent records the sale before closing its September books. The subsidiary, however, records the purchase in October when the goods arrive at its warehouse.
When the finance teams compare their September ledgers, the sale has no corresponding purchase entry.
Neither team may have made an obvious data-entry mistake. The difference stems from the timing of recognition, which can depend on the transaction terms and applicable accounting policies. But if the teams fail to identify and account for that difference, it can complicate period-end reconciliation and reporting.
Why it matters: Timing differences can leave intercompany receivables and payables unmatched and affect the period in which revenue, expenses, inventory, or other balances are reported.
How to prevent it: Establish clear transaction cut-off procedures across entities. Agree on submission deadlines, share transaction details before closing, and maintain a record of timing differences that require follow-up. Where recognition dates legitimately differ, document the reason and account for the difference in accordance with the applicable accounting framework.
A shared transaction should have corresponding values in both entities’ records, subject to legitimate accounting differences. In practice, that is not always what happens.
Suppose a group company’s IT division invoices a subsidiary ₹12 lakh for technology services. The receiving entity records only ₹11.5 lakh because it uses an outdated service agreement or excludes a charge included in the invoice.
The ₹50,000 difference may appear manageable. But multiply that discrepancy across several subsidiaries, recurring service charges, and monthly allocations, and the reconciliation workload can grow quickly.
Why it matters: Incorrect transaction values can leave receivables and payables unmatched, distort expense allocations, and require additional investigation before consolidation.
How to prevent it: Use approved intercompany pricing rules, current service agreements, and consistent invoice references. Both entities should verify the amount, currency, and supporting documentation before posting. Automated matching can flag value differences early, allowing teams to investigate them before the closing deadline.
For a multinational group, even a correctly recorded transaction can produce different reported balances if currency conversion is handled inconsistently.
Imagine an Indian parent invoicing its European subsidiary €20,000. Both entities record the transaction, but one uses the applicable exchange rate on the transaction date while the other uses an incorrect rate or conversion date.
The result is a mismatch that cannot be explained by comparing invoice amounts alone.
Foreign currency accounting adds another layer of complexity because the appropriate rate may differ depending on whether the team is initially recognising a transaction, remeasuring a monetary balance, or translating financial statements for consolidation.
Why it matters: Incorrect currency treatment can create unexplained differences, misstate relevant balances, and complicate the reporting of foreign exchange gains and losses.
How to prevent it: Define approved exchange-rate sources and document the rules for initial recognition, settlement, period-end remeasurement, and consolidation translation. Reconciliation tools should distinguish exchange-related differences from genuine transaction errors so that finance teams can investigate the correct issue.
Sometimes, the mismatch exists because one entity has recorded a transaction and the other has not.
A shared services centre, for example, allocates ₹8 lakh in payroll costs to a subsidiary. The service centre records the recharge and recognises the amount due. The subsidiary’s finance team misses the entry while processing month-end transactions.
The originating entity now has a receivable, but the corresponding payable and expense are absent from the subsidiary’s ledger. If the issue is discovered only during consolidation, the team must determine whether the transaction was overlooked, delayed, or sent to the wrong entity.
Why it matters: Missing entries can leave intercompany balances unmatched and affect the completeness of reported expenses, liabilities, and other relevant accounts.
How to prevent it: Maintain a central register of intercompany transactions and compare entries initiated by one entity with postings in the corresponding entity. Use alerts for missing entries and overdue confirmations, and assign responsibility for resolving exceptions before the reporting period closes.
The amounts may match, the transaction dates may be correct, and both entities may have recorded their entries. Yet the reconciliation still fails.
The reason could be account mapping.
For example, the parent company records an intercompany loan under a designated intercompany receivable account. Its subsidiary records the corresponding liability under a general trade payable account rather than the appropriate intercompany account.
The transaction exists on both sides, but inconsistent classification makes it harder to identify the relationship and apply the correct consolidation treatment.
This problem often surfaces after an ERP migration, an acquisition, or a change in the group’s chart of accounts. Local entities may continue using legacy account structures even after the group introduces new reporting requirements.
Why it matters: Incorrect mapping can affect balance-sheet classification, complicate matching, and lead to incorrect or incomplete consolidation elimination entries.
How to prevent it: Establish a standard group chart of accounts or a common mapping structure that links local accounts to group reporting categories. Validate intercompany account mappings whenever systems or account structures change, and review them periodically to catch inconsistencies before month-end.
It is the final hour of closing, and a ₹3 lakh difference remains unexplained. The finance team posts an adjustment to get the balances aligned and meet the deadline.
The following month, the same discrepancy appears again.
The adjustment may have helped complete the immediate task, but the underlying issue remains. Perhaps a recurring service charge is being calculated incorrectly, or one entity is consistently missing an entry. Without further investigation, the finance team may continue correcting the same difference every month.
Over time, unsupported or poorly documented adjustments can make account movements harder to explain and weaken the audit trail.
Why it matters: Repeated adjustments can conceal recurring errors, increase audit effort, and reduce visibility into the actual causes of reconciliation differences.
How to prevent it: Require supporting evidence and appropriate approval for every adjustment. Classify differences by cause, assign an owner and resolution deadline, and track recurring issues across reporting periods. Temporary adjustments should include a clear explanation and a follow-up process to ensure the original problem is corrected.
Preventing these six errors requires more than asking accountants to check their spreadsheets carefully. The process must connect transaction recording, exception management, and consolidation across the group.
Finance teams can strengthen reconciliation by focusing on five areas:
Return to the finance team facing that ₹3 lakh discrepancy. The amount itself may not be the biggest problem. The real concern is that the team cannot explain the difference quickly enough to complete the close with confidence.
That is what makes intercompany reconciliation an important financial control rather than simply another month-end task.
When transactions are recorded in different periods, values do not match, exchange rates are inconsistent, or adjustments remain unexplained, the effects can extend into consolidated reporting and audit preparation.
The objective is not to force every balance to match through a last-minute adjustment. It is to understand why differences arise, distinguish legitimate timing and currency variations from genuine errors, and resolve exceptions with the right supporting evidence.
For organisations managing multiple legal entities, standardised accounting practices, clear ownership, and integrated reconciliation tools can help reduce recurring discrepancies and make financial reporting more reliable.
