An intercompany reconciliation template lists, for each pair of related entities, what one side shows as due from the other and what the other shows as due to it. The two balances should mirror each other exactly. Any gap goes on a difference schedule with a cause and an owner, so the balances eliminate cleanly at consolidation.
What does an intercompany reconciliation template track?
An intercompany reconciliation template tracks one pair of entities per sheet and gives each entity its own set of columns. Both entities report the same relationship from opposite ends, so the template puts the two views side by side and computes the gap between them.
Intercompany means a transaction or balance between two entities in the same group, such as a parent charging a subsidiary a management fee. In consolidation, these balances are removed, because the group cannot owe itself money. They can only be removed if the two sides agree.
A usable template has these columns for each entity:
- Entity name and ledger account. The legal entity and the account code where the balance sits, such as "Due from Entity B".
- Currency. The currency of the transaction and the currency of the ledger, which may differ.
- Document reference. The invoice, journal or transfer number, so each line can be found on both sides.
- Transaction date and posting date. These often differ across a month end.
- Amount in transaction currency and in ledger currency.
- Balance per ledger. The closing figure in the general ledger for that account.
Then add shared columns: the difference, its cause, the entity that owns the fix, the expected clearing date, and the preparer and reviewer sign-off. If you keep the template in Excel, give each pair its own tab and add a summary tab that lists every pair's difference, so a reviewer sees the whole group on one page.
Setting up the pairs
List every entity pair that trades with each other before the close begins. Three entities produce three pairs, four produce six, and the count grows quickly. Name the pairs the same way each month, and agree who is the lead for each pair, meaning the entity that prepares the template and chases the other side.
Matching intercompany balances: due-to versus due-from
Matching intercompany balances means checking that every receivable one entity records from a related entity has an equal payable on the other entity's books. The receivable is "due from", the payable is "due to", and the two should be equal in amount and opposite in sign.
Take two entities in the same currency. Entity A shows $48,300.00 in "Due from Entity B". Entity B should show $48,300.00 in "Due to Entity A". When you add the two together, treating the receivable as positive and the payable as negative, the result is zero. That zero is what lets the consolidation remove both lines.
The matching rules are short:
- Match on the document, not on the total. Two balances can be equal by accident while the lines underneath disagree. Match each invoice or journal by reference first, then compare the totals.
- Match in the same currency first. Compare in the currency of the transaction, then translate. This separates real errors from exchange differences.
- Compare as of the same date. Both entities must use the same cut-off. A balance at March 31 on one side and April 1 on the other will never match.
- Net only within a pair. Do not offset a gap in one pair against a gap in another. Each pair must clear on its own.
- Keep the sign convention fixed. Pick one, such as receivable positive, and use it on every sheet.
For a finished layout, here is a two-entity example with a gap. All values are examples.
| Line | Entity A: Due from B | Entity B: Due to A | Difference |
|---|---|---|---|
| Balance per ledger, March 31 | 48,300.00 | 47,060.00 | 1,240.00 |
The difference schedule explains the 1,240.00:
| Reference | Cause | Amount | Who books the fix |
|---|---|---|---|
| MF-0331 | Management fee booked by A on March 31, booked by B on April 2 (timing) | 900.00 | B, in March |
| TR-0330 | Transfer sent by B on March 30, received by A on April 1 (cash in transit) | 340.00 | A, in March |
| Total explained | 1,240.00 | ||
| Unexplained | 0.00 |
The unexplained line is the one that matters. It must reach zero before the pair is signed off. A schedule that explains 1,100.00 of a 1,240.00 gap has not finished, whatever the explained items look like.
Why intercompany transactions disagree: timing, FX and one-sided entries
Intercompany transactions disagree for three main reasons: the two entities record the same event in different periods, they translate it at different exchange rates, or only one of them records it at all. Each cause leaves a different mark on the difference schedule.
Timing differences
One entity books an invoice on the last day of the month and the other books it when the paper arrives. Cash behaves the same way: a transfer leaves one bank on the 30th and lands in the other on the 1st. These gaps reverse by themselves next month, but they still need a booking in the current month so the balances match at the cut-off.
Exchange rate differences
When the entities keep their books in different currencies, each translates the same amount at its own rate. If the rates come from different sources or different dates, the amounts differ even though the transaction is identical. The fix is to agree one rate source and one date, such as the month-end rate from a named provider, before the close starts.
One-sided entries
A one-sided entry exists on one entity's books only. A cost recharge raised by the parent that the subsidiary never booked is the classic case. These have no pair to match against, so they appear as an unexplained difference until someone finds the document. They are also the entries most likely to be wrong, because nobody on the other side has seen them.
Other causes worth checking
- Wrong account. The amount was booked, but to an ordinary payable instead of the intercompany account.
- Wrong entity. The charge went to Entity C when it belonged to Entity B.
- Duplicate posting. The same document was entered twice on one side. For ways to catch that, the guide to accounts payable duplicates and missing credits uses the same logic.
- Rounding. Translation can leave a cent or two per line; set a tolerance for it.
How do you settle intercompany differences before consolidation?
You settle intercompany differences by deciding who is right, then having the entity that is wrong book a correcting entry in the open period. The owner of the source document decides. The other side adjusts to match it.
Follow this order for each item on the difference schedule:
- Find the source document. The signed invoice, the bank advice or the contract decides the amount and date.
- Agree the cause with the other entity. An email or a comment on the sheet is enough, as long as both preparers have seen it.
- Name the entity that books the fix. A timing item is booked by the entity that is late. A one-sided entry is booked by the entity that has no record of it, after the document is confirmed.
- Book it in the period being closed. Do not carry a known difference into the next month because the close is busy.
- Rerun the match. The pair is finished only when the difference is zero or fully supported.
If the gap cannot be resolved before the deadline, record it as an unreconciled difference with a clear note and an owner, rather than posting a plug to an unrelated account. A plug hides the problem and moves it to a place nobody is checking. How large a difference has to be before it is worth chasing is a policy decision; the guide to setting materiality thresholds for balance sheet reconciliations covers how to choose one.
If you are sizing up tools for this work, questions to ask before buying account reconciliation software lists what to test. For the underlying idea, what account reconciliation means explains why every balance needs support.
Edge case: an intercompany reconciliation example with a currency difference
An intercompany reconciliation example with a currency difference shows how a balance can be correct on both sides in its own currency and still not match in the group's reporting currency. The gap comes from the exchange rate, not from an error in either ledger.
Suppose Entity A keeps its books in US dollars and Entity B in euros. A invoices B for EUR 40,000, and A books the invoice at 1.0800 dollars per euro.
| Step | Entity A (USD books) | Entity B (EUR books) |
|---|---|---|
| Invoice date | Due from B: USD 43,200 (EUR 40,000 at 1.0800) | Due to A: EUR 40,000 |
| Month end rate 1.0900 | Due from B should be USD 43,600 | Due to A: EUR 40,000, translated at 1.0900 = USD 43,600 |
| Gap before revaluation | USD 400 |
Both entities agree on EUR 40,000. The USD 400 gap exists only because A still carries the receivable at the invoice-date rate. The receivable is in euros on A's books, so A remeasures it at the month-end rate and books the USD 400 as an exchange gain. Apply the same treatment every month and record the remeasurement entry on the difference schedule, so the gap shows as explained.
Keep the transaction currency amount on the template for this reason. When the euro amounts match, you know the underlying balance is right and only the rate needs attention.
Where bank evidence comes in
Many intercompany items settle through a bank account, and the transfer on the bank statement is the proof of when cash moved. PreciseBankFlow reads bank statements and checks that they foot, so the transfer dates you cite on a difference schedule come from lines you have already tested. You can see more on the PreciseBankFlow homepage.
Related: the same tie-out discipline applies to vendor balances, which the accounts payable reconciliation template covers line by line.