When intercompany balances fail to eliminate

A common failure in general accounting is intercompany balances that do not agree between entities. It starts when each side books the same deal differently, surfaces when eliminations leave a residual at consolidation, and is fixed by agreeing balances before close instead of plugging the gap.

How it starts

Two entities in the same group trade with each other. One charges a management fee, lends cash or ships stock. The other should record the mirror image. Often it does not, at least not in the same period or the same way.

The causes are ordinary. The selling entity raises its invoice on the last day of the month, while the buying entity only sees it after its own ledger has closed. One side books the charge to a trading account and the other treats it as a loan. A recharge of shared costs is calculated by an allocation run in one ledger and keyed by hand in the other, with a different rate. Currency adds its own drift when each entity translates at a rate picked from a different source.

None of these looks serious on its own. Each entity's books balance. Each local controller can sign off with a clear conscience. The problem only exists in the gap between them.

The chart of accounts can make it worse. If intercompany accounts are not tagged with a partner entity code, nobody can see which counterparty a balance relates to without opening the detail. Mismatches hide inside a single receivable line.

How it gets spotted

The first visible sign is usually at consolidation. Eliminations are meant to cancel every receivable against its matching payable and every internal sale against the internal purchase. When the two sides disagree, the elimination leaves something behind. That residual lands in the consolidated trial balance with no obvious owner.

Other signals appear earlier for anyone looking. Intercompany accounts that are reconciled within an entity but never against the partner. Aged items in intercompany clearing that nobody can explain. A suspense or difference account at group level whose balance grows quietly from one close to the next. Reviewers asking the same question about the same pair of entities every period.

Auditors notice too, though usually late.

Why the usual fix makes it worse

Under close pressure, the group team posts a management adjustment to clear the residual. It goes to an unallocated difference account, or it is pushed into one entity's expenses. The consolidation balances and the report goes out.

That entry hides the cause. The two local ledgers still disagree. Next period the same mismatch rolls forward, joined by new ones. Over time the plug account becomes a mix of timing differences, genuine errors and items that should have been written off long ago. Untangling it then needs transaction detail that may no longer be easy to find.

Fixing it properly

The durable fix moves agreement earlier, so that mismatches are settled between entities before anyone at group level sees them.

Start with structure. Give every intercompany account a partner attribute in the general ledger, so each balance can be matched pair by pair. Agree which account types each kind of internal transaction should use, and write that down where both sides can find it.

Then set a cut-off for intercompany activity that sits ahead of the main close. Charges raised after it wait for the next period, on both sides. A single agreed source for currency rates removes another source of drift.

Next, make matching a step in the close calendar. Each pair of entities confirms its balances with the other before local sign-off. Where a difference remains, one party owns it, with a reason and an expected clearing date recorded alongside the item. Netting tools or a shared matching report help, though the discipline matters more than the software.

Finally, clean up what is already sitting in the plug. Trace each piece back to the entities involved, correct what can be corrected in local books, and get approval to write off what cannot. After that, any new posting to the difference account should need sign-off and an explanation.

Expect the first closes under the new routine to feel slower. That eases once the backlog is gone.

Questions to ask the people who run it

The documented process and the real one often part ways here. Ask the people doing the work:

• When an intercompany invoice arrives after your ledger closes, what actually happens to it?
• Who decides which account an internal charge goes to, and do both sides follow the same rule?
• Where do you get the exchange rate for intercompany items, and does the partner entity use the same one?
• Do you ever talk to the counterparty before signing off your reconciliation?
• What goes into the group difference account, and who approves it?
• Which entity pairs cause trouble every period, and why do you think that is?
• If an elimination does not clear, how long does it stay before someone writes it off?
• Are any allocations or recharges calculated outside the ledger and keyed in by hand?

The answers usually show where the mismatch is born. They also show which fixes people will actually adopt and which will be quietly worked around at the next tight close.

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.