When intercompany balances will not eliminate in consolidated results

The most common failure in reporting consolidated results is an intercompany balance that will not eliminate. It starts when the payer and the receiver book a cross-border payment at different exchange rates or on different dates. It surfaces at elimination. The fix is a shared rate and a shared cut-off.

How it starts

A subsidiary pays a sister entity in another currency. The paying side converts the amount when the payment run goes out, using whatever rate its treasury system pulls that morning. The receiving side records the cash when the bank statement arrives, often later, and converts at the rate on that date. Both entries are correct by local rules. Together they disagree.

Timing makes it worse. If the payment leaves before period close and lands after it, the payer shows a settled balance while the receiver still carries an open receivable. Nobody did anything wrong. The process simply has no agreed moment when the transaction counts for both parties.

Invoices add another layer. Where intercompany charges for shared services or recharged costs are raised as ordinary invoices, the receiving entity may hold them for approval. Until approval is complete, the liability sits outside its ledger. The selling entity has already booked revenue and a receivable.

How it shows up

The first visible symptom is a difference on the elimination schedule. Consolidation software will usually push the gap into a suspense or plug account so the group still balances. That is the dangerous part. A balanced trial balance hides the fact that each entity is telling a different story.

Other signals appear before anyone looks at eliminations:

• Cash forecasts from the subsidiaries do not net to zero for internal flows, even though money only moved inside the group.
• Cost reports by cost center show recharges arriving in a later period from when they were sent.
• Reviewers keep asking the same entities for explanations every close, and the answers are always about rates or timing.

A plug account that never clears down to nothing is the clearest warning. When it carries a balance from one period into the next, the problem is structural.

Why the quick fix backfires

The tempting response is a top-side adjustment at group level. Someone books the difference to foreign exchange gain or loss and the report goes out. This works once. Repeated, it creates a group number that no local ledger supports, and auditors eventually ask for the reconciliation. Rebuilding it after the fact is slow and unpleasant.

Writing off small differences under a tolerance has a similar effect. Tolerances are sensible for genuine rounding. They become a hiding place when the underlying cause is a rate mismatch that recurs every period.

Fixing it properly

Start with the rate. Set a single group rate table for intercompany conversions and require both entities to use it, whatever their local treasury feed says. The difference between that rate and the actual settlement rate then belongs to the paying entity alone, as a realized gain or loss, and stops polluting the intercompany accounts.

Next, fix the cut-off. Agree that an intercompany transaction exists for both parties from the date the originating entity books it. The receiving entity accrues on that basis, using a confirmation from the sender, without waiting for its own approval workflow or the bank statement.

Then move matching earlier. Intercompany balances should be confirmed between entities before the close deadline, not discovered afterward at group level. Many teams run a pre-close matching step in which each pair of entities agrees its balances and clears differences locally. Anything unresolved is escalated with an owner and a reason, never parked in suspense.

Finally, route recurring recharges outside the normal invoice approval queue. A standing agreement between entities can authorize them in advance. That removes the most common source of one-sided postings.

Questions to ask the people who run it

Documentation often describes the intended design. These questions surface what actually happens:

• When an intercompany payment goes out, which rate does your system apply, and who chose that source?
• On the receiving side, do you book the entry when the sender tells you, when the invoice is approved, or when the cash arrives?
• What happens to a difference on the elimination schedule? Who books it, and to which account?
• Is there a suspense or clearing account that carries a balance between periods? Who looks at it, and when?
• Have you ever adjusted the group figures without a matching entry in a local ledger? How was that recorded?
• Do you confirm balances with sister entities before close, or only when someone at group level asks?
• Which intercompany charges are held up for approval most often, and why?

Watch for answers that mention spreadsheets kept by a single person, informal email confirmations, or a standing journal that gets copied forward each period. Those are where the documented process and the real one part ways, and where any redesign needs to begin.

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.