How to Reconcile Intercompany Balances After an Acquisition

Why the two sides never agree the first time, and how Group Finance closes the gap

Intercompany balances are the first place Group Finance usually discovers that an acquired company’s accounting is not yet compatible with the Group’s. Every other balance can be reviewed on its own terms. An intercompany balance cannot: it has a counterparty, and that counterparty has its own ledger, its own cut-off, and its own view of the same transaction. When the two do not agree, consolidation cannot proceed cleanly, and the difference has to go somewhere.

This article walks through how to run that first reconciliation on a newly acquired subsidiary: how to build the population, how to pull both sides, how to classify what you find, and how to stop the same differences reappearing next month. It is a companion to the first 100 days finance integration roadmap, which sets out where this workstream sits in the wider integration sequence.

What Are Intercompany Balances, and Why Do They Break After an Acquisition

An intercompany balance is an amount receivable or payable between two entities inside the same Group. Because the Group cannot owe money to itself, these balances are eliminated on consolidation: the receivable in one entity cancels the payable in the other. That elimination only works if both sides carry the same number.

When both sides do not agree, the difference does not disappear. It lands somewhere in the consolidated accounts, usually in a reconciliation or suspense line, and it has to be explained to the auditors.

Before the acquisition, the company you bought had no reason to agree anything with your Group. It had no intercompany relationships with your entities at all. From the moment the deal closes, it does, and often retrospectively, because trading may have started before the systems were connected.

Three things are usually missing on day one:

• a shared reference for who the counterparty actually is, so the same entity is booked under two or three different names
• an agreed cut-off, so a shipment invoiced on the 30th is recorded in different months on each side
• any habit of confirming balances, because nobody has ever asked the local team to do it

None of these are accounting errors in the ordinary sense. They are the predictable consequence of joining two ledgers that were never designed to talk to each other.

Why the First Reconciliation Is Different From a Routine One

A routine monthly intercompany reconciliation in a mature Group is a control. You expect it to balance, and a difference is an exception. The first reconciliation after an acquisition is closer to an investigation. You expect differences, and the useful output is not a clean match but an explained one.

That distinction matters for planning. If you schedule the first reconciliation inside a normal three-day close, it will fail, and the local team will conclude that Group Finance does not understand their situation. Run it as a separate exercise with its own timeline, then fold it into the close once it balances.

The Reconciliation Process, Step by Step

The sequence below assumes you have access to the acquired company’s General Ledger and a named contact in its finance team. Both are prerequisites, not details.

1. Build the population of relationships. List every Group entity the acquired company could have transacted with, then confirm with both the local team and Group treasury which of those relationships are actually live. Do not assume the list in the system is complete. Newly acquired companies frequently trade with one or two Group entities through arrangements that were agreed commercially and never set up properly in the ledger.
2. Pull both sides of every balance at the same date. Take the acquired company’s sub-ledger detail and the counterparty’s, both at an identical cut-off date. Insist on transaction-level detail, not summary balances. A summary tells you a difference exists. Only the detail tells you why.
3. Normalise before you match. Convert both sides to the same currency at the same rate, map the counterparty names to a single code per entity, and align the sign convention. A large share of apparent differences vanish at this step, which is why it comes before matching rather than after.
4. Match and quantify. Match transaction by transaction. Produce, per counterparty pair, the gross difference and a list of unmatched items on each side. Do not net differences across counterparties: a EUR 200,000 overstatement against one entity and a EUR 200,000 understatement against another are two separate problems, not zero.
5. Investigate root causes. Assign every unmatched item to a cause from the list in the next section. This is the step that consumes the time, and it is the step that produces the value, because the cause determines the correction and the fix.
6. Agree, book and track. Agree in writing with the counterparty who books which correction. Book the agreed entries. Put anything still unresolved on a tracker with an owner and a date, and report it as an open item rather than absorbing it into a suspense account.

A Worked Example: Explaining a EUR 340,000 Difference

The figures below are illustrative, built to show the shape of a typical first reconciliation rather than to describe any real engagement.

A Group acquires a distribution business that has been trading with two of the Group’s manufacturing entities since the quarter before completion. At the first reconciliation, the acquired company records EUR 2.41 million payable to those two entities. The two entities together record EUR 2.75 million receivable. The gross difference is EUR 340,000.

Cause	Amount (EUR)	Side to correct	Type
Goods shipped 28 to 31 of the month, received and booked the following month	130,000	Acquired company	Cut-off
Freight recharges posted to a third-party supplier account instead of intercompany	96,000	Acquired company	Misclassification
Credit note issued by the manufacturer, never received or booked locally	64,000	Acquired company	Missing document
Invoices booked at contract rate rather than month-end rate	32,000	Both	FX convention
Duplicate posting of a single invoice	18,000	Manufacturing entity	Error
Total explained	340,000

Two things are worth drawing out of that table. First, only EUR 18,000 of the EUR 340,000, around 5 percent, is an error in the conventional sense. Everything else is a difference in practice, timing or classification. Second, the corrections are not all on the acquired company’s side. Presenting the reconciliation as a list of the subsidiary’s mistakes would be both inaccurate and damaging to a relationship you need for the next twelve months.

The Six Causes That Explain Most Differences

Almost every intercompany difference in a newly acquired company falls into one of six categories. Classifying each item on the way through turns a reconciliation into a repair list.

Category 5 is the one that stalls reconciliations. A disputed recharge is not a bookkeeping question, and Finance cannot settle it alone. Escalate those items early to whoever owns the commercial relationship rather than leaving them to age on the reconciliation.

Who Books the Correction

Decide this before the first reconciliation, not during it. The default that causes least friction is that each side corrects its own errors, and timing differences are corrected by the side whose accounting policy does not match the Group’s, which is almost always the acquired company.

Write the rule down and share it with both finance teams. Without it, every difference becomes a negotiation, and reconciliations that require negotiation do not get done monthly.

Set a materiality threshold for investigation as well. Investigating every difference to the last euro consumes capacity that is better spent on the balances that move the consolidated position. A common approach is a threshold per counterparty pair, with all unmatched items still listed and aged even when they sit below it, so that a pattern of small recurring differences stays visible.

Building a Cadence So It Does Not Recur

A first reconciliation that is not followed by a process simply has to be repeated from scratch next quarter. Four things convert the one-off exercise into a control:

• A fixed monthly confirmation date, before the close rather than during it, when both sides exchange balances.
• A single counterparty code per Group entity, applied in the acquired company’s ledger, so that matching does not depend on names.
• A documented cut-off rule that both sides apply, covering goods in transit and services spanning a period end.
• An open-items tracker with an owner and a target date per item, reviewed at each close.

The dependency worth naming: the counterparty coding fix usually cannot be completed until the acquired company’s chart of accounts has been mapped to the Group’s, because that mapping is what creates the intercompany account structure in the first place. Sequence the two together rather than treating them as separate projects.

Reconciliation also connects directly to the receivables work. Amounts an acquired company shows as due from Group entities sit inside the same aged balances you review in a post-acquisition accounts receivable review, and an unreconciled intercompany balance will distort the aging until it is separated out. For the wider set of balances to look at in the first weeks, see what a CFO should review immediately after an acquisition.

What Group Reporting Needs From the Reconciliation

The consolidation requirement is the reason the deadline exists. Under the EU Accounting Directive 2013/34/EU, consolidated accounts must present the Group as a single economic entity, which requires balances and transactions between consolidated undertakings to be eliminated. For groups applying IFRS, the equivalent requirement to eliminate intragroup balances in full sits in the standards adopted into EU law by Commission Regulation (EC) No 1126/2008, made applicable by the IAS Regulation (EC) No 1606/2002.

In practice that means an unexplained intercompany difference is not a tidiness problem. It is an amount that cannot be eliminated, so it stays in the consolidated result until somebody explains it.

Frequently Asked Questions

Why do intercompany balances not match after an acquisition?

Because the acquired company was never required to agree its balances with your Group before the deal. It has no shared counterparty coding, no agreed cut-off rule, and no habit of confirming balances monthly. Most first-time differences are timing, classification and missing documents rather than accounting errors.

How long does a first intercompany reconciliation take?

For a mid-market subsidiary with a handful of Group counterparties, plan four to six weeks from data request to agreed position. The matching itself takes days. Investigating unmatched items, chasing missing credit notes and agreeing who books what is what consumes the time.

What threshold should trigger investigation of a difference?

Set a materiality threshold per counterparty pair, agreed with Group Finance before you start. List and age every unmatched item regardless, including those below the threshold, so recurring small differences stay visible. Investigating every euro consumes capacity better spent on balances that move the consolidated position.

Who should book the correction, the subsidiary or the Group entity?

Agree the rule before the first reconciliation. The convention that causes least friction is that each side corrects its own errors, while timing and policy differences are corrected by the side whose accounting does not match Group policy, usually the acquired company. Document it and share it with both teams.

Who should own intercompany reconciliation during integration?

Group Finance should own the process and the reporting of open items, with a named counterpart in the acquired company responsible for local data and documents. Leaving ownership with the subsidiary alone tends to stall, because it has neither the authority nor the visibility to resolve differences on the Group side.