Key takeaways
- Intercompany balances must agree between counterparties before consolidation; differences delay the close and can distort group results.
- Most mismatches come from a few predictable causes — timing, exchange rates and one-sided entries — so prevention beats monthly firefighting.
- A group intercompany policy, a common calendar, a single rate source and a mismatch log with owners solve most problems.
- ERP features such as trading-partner fields and automated matching make reconciliation faster and auditable.
In a group with several legal entities — a parent, a trading company abroad, manufacturing units and service companies — a large share of transactions happen inside the group: sales of goods, recharges of services, management fees, loans, interest and dividends. In consolidated accounts, all of these must be eliminated. Elimination only works if both sides of each transaction agree: entity A’s receivable must equal entity B’s payable, and A’s sale must equal B’s purchase.
When they do not agree, the close slows down while teams in different countries exchange spreadsheets and emails, and unexplained differences end up in a suspense account or a consolidation adjustment that nobody fully understands. This guide sets out a practical approach to intercompany reconciliation that I have seen work in multi-entity, multi-currency groups.
1. Why intercompany differences happen
Swipe sideways to see the full chart →
Root causes of 100 intercompany mismatches over one quarter (illustrative)
View the data behind this chart
| Item | Value | Share |
|---|---|---|
| Timing / cut-off differences | 38 | 38% |
| Exchange-rate differences | 27 | 27% |
| One-sided or missing entries | 18 | 18% |
| Wrong counterparty or account | 9 | 9% |
| Price, quantity or service-period disputes | 8 | 8% |
- Timing and cut-off: the seller invoices on 30 September, the buyer records it on 3 October.
- Exchange rates: each entity translates the same USD invoice at its own bank or central-bank rate on different dates.
- One-sided entries: a recharge or accrual is booked by one entity without informing the other.
- Wrong counterparty or account: the transaction is posted against a third-party account or the wrong group company.
- Disputes: the receiving entity does not accept the price, quantity or period being charged.
The mismatch data and balances in this article are illustrative, not data from any specific group.
2. Start with a group intercompany policy
Most intercompany problems are agreements that were never written down. A short policy, approved by group finance, should cover:
| Policy area | What to define |
|---|---|
| Transaction types | Goods, services, recharges, loans, interest, dividends — and which accounts each uses |
| Invoicing | Who invoices, when, in which currency, with what supporting detail |
| Cut-off | Last date for intercompany invoices each month; rule that the receiver books in the same period |
| Exchange rates | One group rate table (for example, month-end and average rates) used by all entities for intercompany balances |
| Confirmation | Monthly balance confirmation deadline and format |
| Disputes | Escalation route and the rule that the receiver books the charge and disputes separately |
| Settlement | Payment terms and netting arrangements |
| Transfer pricing | Pricing method and documentation, consistent with tax requirements in each country |
The most powerful single rule is often the simplest: the receiving entity must record whatever the issuing entity has invoiced, in the same period, and raise a dispute separately if it disagrees. This removes most one-sided balances immediately.
3. Build intercompany into the close calendar
- Day −3: intercompany invoice cut-off; issuing entities send listings of all intercompany invoices for the month.
- Day −1: receiving entities confirm all invoices are booked; recharges and accruals agreed in advance.
- Day 1: balances translated at the group rate; entities submit intercompany balances by counterparty and account.
- Day 2: automated or spreadsheet matching; mismatches above threshold logged with an owner.
- Day 3: mismatches resolved or agreed adjustments booked; remaining differences explained and approved for consolidation.
This fits within the broader day-by-day plan in my month-end close checklist.
4. Matching: by balance and by transaction
Matching at balance level (receivable vs payable, sale vs purchase, loan vs borrowing, interest income vs interest expense) quickly shows which pairs disagree. When they do, matching at transaction level — invoice by invoice — shows exactly which items cause the difference. Keep a standard template with columns for entity, counterparty, account, transaction currency, amount in transaction currency, amount in group currency, invoice reference and date. Matching in the transaction currency first separates true differences from exchange-rate differences.
| Pair | Entity A (USD) | Entity B (USD) | Difference | Explanation |
|---|---|---|---|---|
| A receivable / B payable | 1,250,000 | 1,180,000 | 70,000 | Invoice 30 Sep booked by B on 3 Oct (timing) |
| A sales / B purchases (YTD) | 8,400,000 | 8,372,500 | 27,500 | B used a different rate for two invoices (FX) |
| A recharge income / B expense | 45,000 | 0 | 45,000 | Management fee not accrued by B (one-sided) |
5. The mismatch log
Every unresolved difference above the threshold goes into a single log, shared by all entities, with: the pair, the amount, the root-cause category, the owner on each side, the agreed action and the target date. Reviewing the log monthly by root cause — not just by amount — reveals which process rules are not being followed. In the illustration below, the group introduced a confirmation calendar, a common rate table and the mismatch log in June.
Swipe sideways to see the full chart →
Unmatched intercompany balances at month-end (illustrative, USD million)
View the data behind this chart
| Period | Unmatched intercompany balance |
|---|---|
| Apr | 14.2 |
| May | 12.8 |
| Jun | 9.6 |
| Jul | 6.1 |
| Aug | 4.3 |
| Sep | 3.2 |
6. Using ERP features
Modern ERPs support intercompany accounting directly. In SAP S/4HANA, the trading-partner field on postings identifies the counterparty company, intercompany reconciliation tools match open items across company codes, and consolidation functions use trading-partner information for eliminations. Even without advanced tools, three configuration steps help any system: dedicated intercompany accounts per counterparty or a mandatory partner field; a single, centrally maintained exchange-rate table; and standard document types for intercompany invoices. My article on SAP FICO implementation controls covers how to design these during an implementation.
7. Settlement and netting
Unsettled intercompany balances that grow month after month create foreign-exchange exposure, complicate cash planning and can raise tax and regulatory questions. Settle regularly according to the policy. Where regulations permit, a periodic netting process — offsetting what each entity owes and is owed so only net amounts are paid — reduces the number of cross-border payments and bank charges. In Bangladesh, cross-border settlements are subject to foreign-exchange regulations, so any netting or settlement arrangement should be reviewed with the bank and advisers before it is implemented.
8. KPIs for intercompany health
- Unmatched balance at month-end (value and number of pairs).
- Percentage of pairs matched by Day 2.
- Mismatches by root cause.
- Age of open intercompany balances and of open disputes.
- Consolidation adjustments caused by intercompany differences.
Frequently asked questions
What is intercompany reconciliation?
It is the process of agreeing balances and transactions between entities in the same group — receivables and payables, sales and purchases, loans and interest — so that they can be eliminated correctly in the consolidated financial statements.
How do you handle exchange-rate differences on intercompany balances?
Use a single group exchange-rate table for intercompany balances and match in the transaction currency first. Remaining differences can then be identified as true exchange differences and treated consistently under the group's accounting policy.
Who should resolve intercompany disputes?
The group policy should name owners on both sides and an escalation route to group finance. A common rule is that the receiving entity books the charge as invoiced and raises a dispute separately, so balances agree while the dispute is resolved.
Conclusion
Intercompany reconciliation is a coordination problem more than an accounting one. Write a clear policy, use one rate table, put intercompany steps into the close calendar, match by balance and by transaction, keep a single mismatch log by root cause, and use your ERP’s partner functionality. Groups that do this close faster, consolidate with confidence and spend their time on analysis instead of chasing differences across time zones.
Written by Liakat Hossain
Finance and accounts professional with experience in FP&A, SAP FICO, Power BI, internal control, reporting, audit, tax, VAT and export-oriented business operations.
This article is original educational content based on professional finance practice. Real-project examples are anonymized, and scenario figures are identified as model outputs rather than guaranteed results.