ComplyBar logoComplyBar
Financial Reporting

Your Intercompany Eliminations Are the Reason Consolidation Takes So Long

Every close has a moment where everything stops. You've posted the last journal entry, the subledgers tie, and then consolidation refuses to balance by $43,000 somewhere in the intercompany eliminations. Now four people are pulling tie-out schedules at 7 PM trying to figure out which entity booked what, and the CFO wants to know why the preliminary numbers slipped two days.

I've run close for entities ranging from three legal entities to twenty-two, and the pattern is almost always the same: intercompany eliminations are where time goes to die. Not because the concept is hard, but because the breaks surface at consolidation, which is the single worst place to discover them.

Why Eliminations Stall Consolidation Specifically

An intercompany elimination only works when both sides agree. Entity A books a $200,000 management fee receivable from Entity B. Entity B needs to book a $200,000 payable. When you consolidate, those two net to zero and disappear from the group financials.

The problem is that the two sides are recorded by different people, at different times, often in different currencies, sometimes under different account mappings. Entity A's controller books the fee on the 2nd. Entity B's controller is out sick and books the payable on the 4th at a stale FX rate. Now you have a $1,800 residual sitting in your consolidation that nobody planned for.

Multiply that across a dozen intercompany relationships — loans, cost allocations, inventory transfers, royalties, cash pooling — and consolidation becomes a hunt for dozens of small breaks instead of a clean rollup.

The breaks that eat the most time

  • Timing differences. One side records in the current period, the other in the next. Classic for goods in transit and services invoiced near period end.
  • FX mismatches. Both sides agree on local currency but translate at different rates. A $500,000 intercompany loan at a 0.0004 rate gap creates a $200 residual that still has to be explained.
  • Classification differences. Entity A calls it a management fee; Entity B books it as a cost reimbursement to a different account. Amounts match, mappings don't, elimination fails.
  • One-sided entries. Someone books a receivable and the counterparty never books anything at all.

The Reconciliation-First Approach

The fix is not a better consolidation worksheet. It's refusing to let unbalanced intercompany balances reach consolidation in the first place. You reconcile intercompany before you roll up, not after the elimination fails.

In practice this means every intercompany relationship gets matched counterparty-to-counterparty on a fixed cadence during close, with a tolerance threshold and a named owner on each side. The goal is that by the time you consolidate, every intercompany pair already nets to zero or carries a documented, approved residual.

A workflow that actually holds up

  1. Lock the submission date. All intercompany activity for the period must be posted by, say, Business Day 2. No late intercompany entries without a counterparty confirmation.
  2. Run a counterparty matching report by BD3. Pull every intercompany balance by entity pair and account category. Flag anything over your tolerance — I use $500 or 0.5%, whichever is lower.
  3. Assign both sides of each break. A break between Entity A and Entity B is owned by both controllers, not dumped on the consolidation accountant who has no idea what the transaction was.
  4. Resolve or document before BD4. Either both sides agree and correct, or you record a reconciling item with an explanation and let it flow as a known residual.
  5. Consolidate against clean balances. Eliminations now net cleanly because the matching already happened upstream.

When I moved a seven-entity group to this approach, consolidation went from a two-and-a-half-day fire drill to a half-day sign-off. The work didn't disappear — it moved earlier, to a point in the close where there was still time to fix things without missing the reporting deadline.

Why Excel Quietly Makes This Worse

Most teams run intercompany reconciliation in a shared workbook: one tab per entity pair, formulas that compare the two sides, a summary tab that totals the breaks. It works until it doesn't.

The failures are predictable. Someone overwrites a formula and the $43,000 break shows as zero. The FX rate on the loan tab is hardcoded from last month. Two people edit the same file and you reconcile against a version that's an hour stale. Worst of all, the workbook has no memory — it can't tell you that this same Entity A / Entity B royalty break has shown up three months running, which is the signal that the underlying process is broken, not just this month's entry.

Excel also can't enforce the cadence. Nothing in a spreadsheet stops a controller from posting a late one-sided entry on BD5 that blows up a consolidation you thought was clean. There's no owner assignment, no status, no trail of who confirmed what and when.

What a structured close platform changes

A platform like ComplyBar treats each intercompany reconciliation as a tracked task with two owners, a due date, a tolerance rule, and a status that has to move from open to matched to approved. The practical differences:

  • Automatic counterparty matching. The system pairs Entity A's receivable against Entity B's payable and surfaces the residual without someone building a comparison tab by hand.
  • Breaks can't hide. An unresolved intercompany break shows up on a dashboard as a blocking item, so consolidation can't quietly proceed on bad numbers.
  • Accountability on both sides. Both controllers see the same break with their name on it. No more lobbing it over to consolidation.
  • History that compounds. When the same break recurs, you see the pattern and fix the root cause — a wrong account mapping, a timing convention nobody agreed on — instead of re-reconciling it every month.
  • An audit trail by default. When your auditors ask how you supported a $12,000 intercompany residual, the explanation and approval are already attached.

The Takeaway

Your consolidation isn't slow because consolidation is hard. It's slow because unmatched intercompany balances arrive at the one stage of close where you have the least time to investigate them. Move the matching upstream, give every break two owners and a deadline, and consolidation becomes a rollup instead of an investigation.

Start with one change this month: pull an intercompany matching report on BD3 instead of waiting for eliminations to fail. The breaks you find will be the same ones that would have cost you two days later — except now you have time to fix them.

Keep reading

Ready to streamline your month-end close?

ComplyBar helps accounting teams close faster with less stress.

Start Free Trial