The parent company records an amount due from a subsidiary, but the subsidiary reports a different amount payable. Both finance teams believe their records are correct. One points to invoices already issued, while the other refers to payments, disputed charges or documents received after its reporting deadline.
As the group reporting date approaches, the difference becomes a consolidation problem. Finance teams exchange spreadsheets, adjustments arrive late, and management struggles to identify which figures are final. A balance that should be straightforward begins delaying the wider reporting process.
Lee & Hew identifies group audits, holding companies, consolidation and accounting among its areas of focus. For businesses preparing group accounts, resolving intercompany differences requires a clear trail from the underlying transaction to each entity’s records. The objective is to establish what happened, determine the appropriate treatment and document any correction before relying on the consolidated results.
Start With the Same Reporting Date and Scope
Two balances cannot be compared meaningfully unless they cover the same period and transactions. A parent’s listing prepared after its final adjustments may differ from a subsidiary’s earlier submission even when both teams have processed the same underlying activity.
Agree the reporting date, the version of the ledger being used and whether the comparison includes subsequent adjustments. Identify the legal entities involved rather than relying on broad labels such as “head office” or “regional company.”
The scope also matters. One team may include trade invoices, funding advances and interest in a single account, while the counterparty reports them separately. Comparing only one category can create an apparent difference that disappears once the full breakdown is available.
Before investigating individual entries, establish a common basis for the reconciliation. This avoids spending time explaining differences caused by inconsistent reports rather than inconsistent accounting.
Compare the Transactions Behind the Total
An account total shows the size of the disagreement but rarely explains its cause. Obtain transaction-level listings from both entities, including references, dates, currencies, amounts and a description of each item.
Match common entries first, then isolate the remaining differences. A shared invoice reference or payment identifier makes this easier. Where references differ, supporting documents may be needed to establish whether two entries relate to the same transaction.
For example, a parent may record a recharge under a quarterly invoice number while the subsidiary records it under an internal journal reference. Without a cross-reference, the entries can look unmatched even though the amounts and underlying service agree.
Preserve the matching work so that another reviewer can follow it. A reconciliation should explain how the two balances connect, rather than merely show that someone has entered a balancing amount at the bottom of a spreadsheet.
Distinguish Timing Differences From Missing Entries
Some differences arise because one entity records a transaction before the other. That explanation needs to be supported by dates and documents, particularly when the transaction falls close to the reporting cut-off.
Consider a hypothetical parent company with a S$180,000 receivable from its subsidiary. The subsidiary reports a S$150,000 payable. Investigation identifies a S$30,000 service recharge recorded by the parent on the final day of the reporting period but not yet processed by the subsidiary.
The difference is now explained, but the accounting conclusion still requires review. The teams need to confirm the nature of the service, the relevant period and the basis of the charge. If the obligation belongs in the subsidiary’s reporting period, a supported adjustment may be necessary.
“Timing difference” should therefore describe the cause, not close the investigation. Record which entity must act, what entry is required and how completion will be confirmed. Otherwise, the same difference may return in the next reporting cycle.
Trace Payments Through Both Sides
Payments can create differences when the paying entity records a transfer before the receiving entity identifies or allocates it. The payment might also be applied to the wrong invoice or counterparty account.
Obtain the payment instruction, bank evidence and remittance details. Establish the amount sent, the currency, any deductions and the date the funds were received. These details help distinguish a payment in transit from an allocation error or an unexplained shortfall.
Where one payment settles several invoices, the receiving team needs an allocation schedule. Without it, the receipt may remain in an unapplied account while the intercompany receivable continues to appear outstanding.
Do not clear the difference simply because the payer confirms that money was sent. The reconciliation needs to show how the payment has been reflected in both sets of records and whether any remaining amount requires investigation.
Resolve Disputed Charges at the Appropriate Level
A subsidiary may deliberately leave a recharge unrecorded because its management disagrees with the amount or believes the service was not provided. This is a commercial or accounting dispute, rather than an administrative delay.
The responsible managers should review the agreement, supporting calculations and evidence of the underlying activity. Finance needs a documented conclusion that it can assess and implement.
For shared costs, the explanation should identify what was allocated and why the allocation basis is appropriate. A spreadsheet showing a percentage charge without supporting context may be insufficient for the receiving entity to understand the amount.
The group should avoid pressuring a local finance team to accept an entry solely to make the balances agree. Agreement should follow a supported assessment. Where a dispute remains unresolved, it needs escalation and a clear evaluation of its reporting implications.
Separate Currency Differences From Transaction Differences
Entities operating in different currencies may report different numerical amounts even when they agree on the underlying obligation. Begin by matching the balance in the transaction currency before examining its translation into each entity’s functional currency and the group’s presentation currency.
For example, both entities may agree that an invoice remains outstanding for US$100,000. Their local-currency balances can still differ because of the currencies and rates used in their respective reporting processes.
The review should establish whether the correct rates and accounting treatment have been applied. An outdated exchange rate is different from a missing invoice, and the corrective action will differ accordingly.
Foreign exchange effects should not automatically be removed as reconciliation errors. Under IAS 21, exchange differences arising from intragroup monetary items can remain in the consolidated financial statements even though the related receivable and payable are eliminated. Their presentation depends on the relevant circumstances and requirements.
Keep Loans, Interest and Trading Balances Identifiable
A single intercompany account can accumulate several types of activity over time. It may contain trading invoices, temporary advances, longer-term loans, interest and payments made on behalf of another entity.
Breaking the balance into these components makes the reconciliation more useful. Each category may have different supporting documents, settlement expectations and reporting considerations.
For loans, retain the relevant agreements and records of drawdowns and repayments. Where interest applies, both parties should understand the calculation period, rate and outstanding principal. Differences can arise when one entity updates the principal balance but the other continues calculating interest on an older amount.
The aim is not necessarily to create a large number of ledger accounts. It is to maintain enough detail to explain the balance and apply the appropriate accounting treatment to each component.
Correct the Records Where the Issue Arises
When an error belongs in an entity’s records, a consolidation adjustment alone may leave the underlying problem unresolved. The next reporting submission can reproduce the same error, forcing the group team to repeat its work.
Identify whether the correction belongs in the local ledger, a group reporting adjustment or the consolidation process. Document the reason for that decision and obtain the relevant approval.
A local accounting error should ordinarily be addressed through the appropriate local process. A difference between local reporting requirements and group accounting policies may instead require a documented adjustment in the group reporting package. These situations should not be treated as interchangeable.
Lee & Hew’s accounting and consolidation services are relevant to groups managing information across several entities. A clear distinction between local corrections and group adjustments helps preserve the reporting trail and reduces recurring reconciliation work.
Do Not Use Elimination Entries to Hide Differences
Consolidated financial statements present the parent and its subsidiaries as one economic entity. Intragroup balances and transactions within the consolidation scope are eliminated under the applicable requirements.
That process depends on reliable underlying records. If one entity reports a receivable that the other has not recorded as a payable, entering an unexplained offset can conceal a missing expense, an incorrect asset or another issue.
A difference should not be moved into a general account merely to make the consolidation worksheet balance. Establish the cause and assess the appropriate correction before preparing the elimination.
Also remember that matching receivables and payables is only part of consolidation. Intragroup income and expenses, cash flows and profits included in assets may require attention. A balance confirmation does not demonstrate that every related consolidation adjustment has been completed.
Assign Ownership and Escalation Deadlines
Intercompany reconciliations often stall because both teams are waiting for the other to act. Each entity pair should have named contacts responsible for preparing, reviewing and resolving differences.
Use a shared issue log that records the amount, cause, supporting evidence, proposed action and deadline. Distinguish items awaiting documents from items requiring management decisions or technical accounting review.
Escalation should happen early enough to influence the reporting outcome. A material unresolved charge should not remain in an email chain until the final day of consolidation.
The group finance team should monitor progress without becoming the default investigator for every transaction. Clear responsibilities allow local teams to resolve routine matters while directing significant or disputed items to the people authorised to decide them.
Confirm the Final Position After Adjustments
A reconciliation can become outdated when one entity posts an adjustment after the other has submitted its final figures. The teams should therefore confirm the agreed position using the revised balances, rather than relying on an earlier email.
Retain evidence that the required entries were posted and that the final reporting packages reflect them. Where an adjustment is made only at group level, ensure the consolidation team has the correct version and understands whether it needs to be reversed or repeated later.
This final confirmation prevents an approved correction from being lost between spreadsheets, ledgers and reporting packages. It also makes subsequent review more efficient because the file shows the original difference, the resolution and the final outcome.
Sign-off should be specific about any remaining exceptions. A general confirmation that balances are agreed is misleading if unresolved items have simply been excluded from the comparison.
Make Reconciliation Part of the Regular Close
Waiting until year-end allows small differences to accumulate and makes older transactions harder to investigate. Staff may have changed roles, documents may be difficult to retrieve, and the original reason for a charge may no longer be clear.
A regular reconciliation process helps identify missing invoices, allocation errors and disputed recharges while the information is still accessible. The frequency can reflect transaction volume and risk, with more active relationships receiving closer attention.
Groups can also reduce recurring issues by agreeing billing deadlines, shared transaction references and consistent reporting templates. These practical steps improve the information exchanged before the reconciliation begins.
Management should review recurring causes as well as outstanding amounts. If the same entity repeatedly submits late recharges or omits payments, correcting individual entries will not resolve the process weakness.
Build Group Reporting on Explained Balances
Intercompany differences are easier to manage when the group treats them as questions about transactions, responsibilities and reporting, rather than as numbers to remove during consolidation.
A dependable process establishes a common reporting basis, compares supporting entries, investigates exceptions and confirms the final position. It preserves legitimate currency effects and distinguishes local corrections from group adjustments.
Lee & Hew provides accounting, consolidation and audit services and highlights its work with holding companies and groups. Businesses reviewing their reporting process can discuss how to organise entity submissions, supporting schedules and reconciliation responsibilities.
The practical goal is that each material intercompany balance can be explained before the consolidated accounts are finalised. That gives directors a clearer basis for reviewing the group’s financial position and reduces the risk that unresolved local issues remain hidden within group reporting.