Part of the Financial consolidation series.
Intercompany reconciliation is the control that decides whether a group's consolidated numbers are defensible or not. Every unexplained difference that survives into the consolidation is an ownership failure, not a materiality judgement - and the size of the gap matters far less than whether anyone is accountable for closing it.
What are intercompany transactions, in plain English?
When one entity in a group sells goods or services to a sister entity, the seller records a receivable and the buyer records a payable. From the group's perspective, nothing has been sold to anyone outside the group - the transaction is internal. To produce accurate consolidated accounts, both sides of that transaction must be eliminated so that the group reports only what it has sold to third parties and only what it owes to third parties. For the elimination to net to zero, both entities must have booked the same amount in the same period. That agreement is what intercompany reconciliation tests. For a fuller picture of where eliminations sit in the consolidation process, see what financial consolidation is and how eliminations work.
Why is intercompany reconciliation important?
Intercompany reconciliation is important because a mismatch between what the selling entity has recorded and what the buying entity has recorded means the group elimination will be wrong - and a wrong elimination flows directly into reported profit, net assets or both. The risk is not purely technical. Auditors treat unexplained intercompany differences as a control weakness. Boards and lenders treat them as a sign that the group does not have a clear view of its own position. And because they surface mid-close, when there is least time to investigate, they have an outsized effect on the cost and reliability of the close. For the relationship between late intercompany agreement and close-day count, see how many days a group month-end close should take.
What causes intercompany reconciliation differences?
Intercompany differences almost always trace back to one or more of four root causes - not arithmetic error.
Timing and cut-off. The selling entity raises an invoice and books the revenue in period one. The buying entity receives the goods in period two and books the cost then. Both entries are locally correct; together they create a mismatch. Cut-off rules that specify the period in which intercompany transactions must be recognised - agreed between entities before the close, not negotiated during it - are the only reliable fix.
FX rate source and translation date. In a multi-currency group, the selling entity may translate an invoice at the rate on the invoice date; the buying entity may use the rate on the payment date or a monthly average. The invoice amount in local currency is identical on both sides; the reporting-currency equivalent is not. Groups that do not specify a single source rate and a single translation date for intercompany transactions will generate FX differences on every cross-border transaction, every period.
One-sided entries. One entity has booked the transaction; the other has not. This is the most common cause and the most dangerous, because half the intercompany balance simply does not exist in one ledger. It is usually a process failure - the invoice was not sent, was lost in a workflow queue, or was received after the entity's local close. The matching report will show a balance on one side and nothing on the other.
Mapping and account differences between systems. Groups running more than one ERP or chart of accounts will find that the same transaction is coded to different account types in each entity. The amounts match; the accounts do not. The elimination template cannot automatically net them, and the difference shows up as unexplained. This is a systems and governance problem, not a bookkeeping one. Groups that have grown through acquisition face this acutely - see intercompany complexity after a buy-and-build acquisition for the integration implications.
Intercompany reconciliation example
Consider two entities: Entity A (the seller, reporting in GBP) and Entity B (the buyer, reporting in EUR, translated to GBP for consolidation). Entity A raises a GBP 100,000 intercompany invoice on 28 March. The group closes on 31 March.
| Scenario | Entity A ledger | Entity B ledger | What the matching report shows |
|---|---|---|---|
| 1 - Cut-off difference | Receivable GBP 100,000 in March | Payable booked in April (goods arrived 2 April) | GBP 100,000 open on A's side; nil on B's side at March close |
| 2 - FX rate difference | GBP 100,000 (invoice date rate) | EUR equivalent translated at month-end rate = GBP 97,400 | GBP 2,600 unexplained difference; both sides exist but do not agree |
| 3 - Account mapping difference | Posted to intercompany receivables account | Posted to trade creditors (not flagged as intercompany) | Amounts match; accounts do not; elimination template misses the offset entirely |
Each scenario produces a different symptom on the matching report, and each requires a different fix. Scenario 1 is a cut-off governance issue. Scenario 2 is an FX policy issue. Scenario 3 is a chart-of-accounts or posting discipline issue. Treating all three as the same kind of problem - and chasing the number rather than the cause - is why intercompany differences recur every period.
Intercompany reconciliation process
The following numbered process is designed to be pasted directly into a close checklist. It assumes entities submit balances before the group controller runs the elimination.
1. Set and communicate the cut-off rule before the period opens. Every intercompany transaction must be booked in the same period by both entities. The rule is the seller's invoice date, not the buyer's receipt date, unless group policy specifies otherwise. This rule must be written, not assumed.
2. Specify a single FX rate source and translation date. For all intercompany transactions, the group controller designates one rate (for example, the closing rate published by the group treasury function on the last working day of the period). Both entities use it. No exceptions.
3. Entities submit intercompany schedules by a fixed internal deadline. The deadline must fall early enough that differences can be investigated before the group close deadline. Treat a late submission as a red flag, not an administrative inconvenience.
4. Run the matching report and apply the agreed threshold. The group controller sets a matching threshold by policy - for example, differences below a defined materiality level that are fully explained by an approved FX rounding rule are auto-cleared. Everything else is flagged for investigation. The threshold is a processing rule, not a permission to leave differences unexplained.
5. Assign ownership of every flagged difference immediately. Each open item is assigned to a named individual - either at the selling entity, the buying entity or both. Ownership is assigned within hours of the matching report running, not at the end of the close. An unowned difference is the group controller's problem by default.
6. Arbitration when entities disagree. When the two entities cannot agree on the correct treatment within one working day of assignment, the group controller makes the decision. The group controller's decision is final for the purpose of that close. The underlying disagreement is logged and resolved as a process or systems fix before the next period.
7. Escalation deadline. Any difference that remains unexplained after a defined number of hours before the group close deadline is escalated to the group financial controller and, if material, to the CFO. At that point the group controller has authority to post an adjusting entry to clear the elimination and the owning entity carries the difference in its local reconciliation until the root cause is fixed.
The spine of this process is ownership, not arithmetic. A small unexplained difference left standing is an ownership failure. The size of the difference determines whether it is material; the existence of an owner determines whether the control is working.
To see where your finance function's intercompany and consolidation maturity sits today, the Finance Value Score free Snapshot takes fifteen minutes and produces a board-ready read of where the gaps are and what they cost.
Common questions
Why is intercompany reconciliation important for group accounts?
Intercompany reconciliation is important because it determines whether the eliminations that produce consolidated accounts are complete and accurate. If one entity's intercompany balance does not agree with the other side, the elimination nets to a non-zero figure and the consolidated profit, assets or liabilities are misstated. Auditors treat unexplained intercompany differences as a control weakness, not a rounding issue.
What are the most common causes of intercompany reconciliation differences?
The four most common causes are timing and cut-off differences (one entity books a transaction in a different period to the other), FX rate mismatches (entities use different rates or translation dates), one-sided entries (only one entity has posted the transaction), and account mapping differences between systems. Each cause produces a distinct symptom on the matching report and requires a different fix.
Who is responsible for resolving an intercompany reconciliation difference?
Ownership of every flagged difference should be assigned to a named individual at one or both entities immediately after the matching report runs - not at the end of the close. If the two entities cannot agree within a defined period, the group controller makes the decision. An unowned difference defaults to being the group controller's problem, which is why clear assignment is the most important step in the process.
What is a matching threshold in intercompany reconciliation?
A matching threshold is a policy-set tolerance below which a difference that is fully explained by an approved rule - for example, a defined FX rounding treatment - can be auto-cleared without manual investigation. It is a processing efficiency rule, not a permission to leave differences unexplained. Any difference that is not covered by the policy explanation must be investigated regardless of its size.
How does intercompany reconciliation affect the length of the group close?
Late intercompany agreement is one of the most common reasons a group close runs over its target day count. When entities submit balances late or differences are not resolved before the elimination stage, the group controller cannot run a clean consolidation and the close stalls. Groups that set and enforce an internal intercompany submission deadline that falls well before the group close deadline consistently run shorter closes.