When intercompany balances stop agreeing at consolidation

A frequent failure is an intercompany transaction that the paying and receiving entities record differently. One side books it and the other does not, or each converts it at a different exchange rate. The gap appears at consolidation, gets parked in suspense, and grows until each side is traced to source documents.

How it starts

It rarely begins with a big error. A subsidiary pays a shared service charge to the parent in its local currency. The payment clerk converts it using the rate on the payment date. The parent records the receivable using the rate from the invoice date. Both entries follow local policy. They simply do not match.

Timing makes it worse. One entity posts before its cutoff. The other receives the remittance advice late and books it in the following period. Now a balance sits on one side only.

Then come adjustments. A credit note or payment correction is entered in the sender's subledger and never communicated. The receiver keeps the original amount. Nobody notices, because each local trial balance ties to its own subledger and each local reconciliation passes.

That last point is the trap. Every entity can be clean on its own while the group is still wrong.

How it gets spotted

The first sign usually comes when eliminations do not net to zero. The consolidation team sees an unexplained difference between intercompany receivable and payable accounts. Under close pressure, someone posts a manual journal voucher to a suspense or clearing account so group numbers can be released.

That entry is the real warning. Two patterns tend to follow it:

• A suspense balance that never fully clears and drifts upward over successive closes.
• Counterparties disputing balance confirmations, each holding documents that support its own figure.

Unexplained foreign exchange gains and losses on intercompany accounts are another clue, especially when nobody can break them down line by line.

Auditors often find the problem before management does. They pick an elimination entry, ask for the underlying transactions, and the trail ends at a plug.

Fixing the backlog

Begin by freezing the suspense account to new entries. Clearing old items while fresh plugs keep arriving achieves nothing.

Pull transaction detail from both entities for each counterparty pair. Match at document level, pairing each invoice and each payment with its counterpart. Matching on totals hides offsetting errors and creates rework later.

Sort every unmatched item by cause. Rate differences need a decision on which rate group policy recognises, then a correcting entry on whichever side used the wrong one. Missing entries need the absent side to book them, supported by the counterparty's document. Unshared adjustments require the originator to send evidence so the receiver can record the same change. Period differences usually resolve once both sides agree which month the item belongs to.

Each correction should post through the entity's own ledger with an approved journal voucher. Correcting only at group level leaves local books wrong and guarantees the difference returns.

Once matched items are booked, reverse the suspense plugs tied to them. Whatever remains is genuinely unresolved residue, and it deserves named owners.

Stopping it coming back

Choose one group rate source and one rule for which date drives conversion. Publish both. Load them into payment and receivable systems so clerks are not picking rates by hand.

Agree an intercompany cutoff ahead of the local close, so both sides post in the same period. Require counterparty confirmation of balances before consolidation begins.

Treat any adjustment on an intercompany item as incomplete until the counterparty acknowledges it. A shared matching tool helps, though a disciplined confirmation routine works where tooling is thin.

Put a control on the suspense account itself. Any manual entry there should carry a reason code and a named owner, agreed at the moment of posting, with review at every close.

Questions to ask the people who run the process

Written procedures usually describe a tidy match. Desk reality is often different. Put these to the clerks and accountants directly:

• Which exchange rate actually gets used when a foreign intercompany payment is entered, and where does it come from?
• When a payment is corrected, who tells the other entity, and by what route?
• What happens at close when intercompany accounts do not agree?
• Who is allowed to post to the suspense account, and does anyone review those entries afterwards?
• Are there counterparties that get chased every close, or ones nobody bothers chasing any more?
• When auditors last queried an elimination difference, what was hard to find while assembling the explanation?

Listen for workarounds described as normal. Remarks about truing things up at group, or about an account that always carries a bit of residue, point straight at where the failure lives.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.