CadelAll Articles
Reconciliation

Intercompany Recon: 4 Failure Modes at Close

Intercompany recon breaks at consolidation, not the ledger. Timing, FX, coding, ownership — the four failure modes that push close past Day 5.

Cadel Team4 min read

Every controller running a multi-entity close knows intercompany reconciliation is the recon that pushes the mid-market month-end close from five days to seven. The math is straightforward — Entity A's intercompany receivable should equal Entity B's intercompany payable. The reality is that it almost never does on the first pass, and the four causes are always the same.

The four failure modes

Why intercompany doesn't tie at consolidation

01
Timing
Entity A invoices on Day 30. Entity B receives the invoice and posts on Day 2 of the next period. At consolidation, A has the receivable; B doesn't have the payable yet.
Fix: Agreed cutoff for IC invoicing, with confirmations exchanged before TB lock.
02
FX
Entity A is USD. Entity B is EUR. The same transaction sits on each ledger in different functional currencies, revalued at different rates. Even at the same date, the translation creates a reconciling difference.
Fix: Agreed transaction currency and revaluation rate by IC pair, applied consistently.
03
Coding
Entity A codes as management fee. Entity B codes as service fee. Both amounts are right; the elimination logic can't pair them. Consolidation eliminates the wrong amount.
Fix: Shared IC account taxonomy with mandated cross-entity codes on every IC transaction.
04
Ownership
Transaction booked between Entity A and C, but the consolidation system has the relationship as A→B→C. The elimination cascade fails because the legal entity map doesn't match what was booked.
Fix: Legal entity diagram synced to the consolidation system, reviewed quarterly.

Under FASB ASC 810-10-45-1, intra-entity balances and transactions must be eliminated in the preparation of consolidated financial statements. Each failure mode above prevents that elimination from completing cleanly.

What intercompany reconciliation actually involves

Intercompany AR/AP matching. For every pair of related entities, the receivable on one side should equal the payable on the other side at the same point in time, in the same currency. The matching engine pairs invoices, payments, and credit memos by transaction reference. Unmatched items go to an exception queue and are investigated against the four failure modes above.

Intercompany loans and interest. Parent loans capital to subsidiary. Subsidiary accrues interest expense; parent accrues interest income. Both sides should reconcile to the same amount on every accrual date. They won't if rates aren't synced, accrual conventions differ between entities, or one entity is on a different close calendar.

Transfer pricing entries. Management fees, IP royalties, shared services allocations — each is a journal entry on both sides that should eliminate at consolidation. The amounts should tie to the transfer pricing memo, and the memo should tie to the transfer pricing study. Mismatch between the JE and the memo is a common audit finding because the tax team and the accounting team maintain separate records.

The elimination matrix. At consolidation, every IC pair eliminates. A clean matrix has every cell tying within a defined materiality threshold, or with a documented timing or FX explanation. A growing "consolidation reconciling difference" line is the first sign the elimination matrix has untreated failure modes.

The structural fix

Intercompany reconciliation fails because IC transactions are tagged after the fact at consolidation, not at the point of entry. Cutoff dates get missed because there's no automated confirmation workflow. FX rates are applied from whichever source the preparer used that day. Coding taxonomy is stored in a wiki, not enforced by the posting system.

The same pattern appears in bank reconciliation close failures — the rec becomes hard because information that should have been captured at transaction time is being reconstructed days later from incomplete data. The structural fix is tagging IC transactions at posting with counterparty code, agreed currency, and elimination rule — so the consolidation run is a confirmation, not an investigation.

See how Cadel handles multi-entity reconciliation and consolidation — or get in touch to walk through your current IC elimination workflow.

#reconciliation#intercompany#consolidation#close-cycle#multi-entity
Intercompany Recon: 4 Failure Modes at Close — Cadel Blog