intercompany invoice matching across subsidiaries

TL;DR

Intercompany invoice matching pairs the seller subsidiary's receivable invoice with the buyer subsidiary's payable bill: same transaction, two books. Match on the intercompany transaction id or reference, amount, and currency; mismatches usually come from FX timing, different posting dates, or one side booking fees the other did not. Reconcile on a schedule (monthly at minimum) with an intercompany clearing account absorbing timing differences. Unmatched intercompany balances block consolidation, so treat them as close-blocking issues, not routine noise.

The query

intercompany invoice matching across subsidiaries

Use this when

• Reconciling intercompany payables and receivables
• Subsidiaries' books not tying on shared transactions
• Intercompany close blockers

Not for

• Third-party vendor invoice matching (different process)
• Transfer pricing policy itself (separate topic)

Steps

1. Pull both sides: the seller's AR invoice and the buyer's AP bill.

Expected output: Both records are in front of you.

1. Match on intercompany reference, amount, and currency.

Expected output: True pairs are identified.

1. Investigate mismatches: FX timing, posting-date differences, one-sided fees.

Expected output: Each variance gets a cause.

1. Book timing differences to the intercompany clearing account per policy.

Expected output: The books balance while timing resolves.

1. Run the match on a schedule and escalate unmatched items before close.

Expected output: Consolidation is never blocked by surprises.

Variant phrasings

intercompany invoice matching subsidiaries

intercompany payable receivable reconciliation

match intercompany transactions

Root cause

The two sides book independently in different systems or ledgers, so timing, FX, and coding differences are guaranteed; matching is the control that proves the group view is consistent. Without it, consolidation carries hidden imbalances.

Edge cases

• Netting agreements can settle intercompany balances without cash moving; know your policy
• Different charts of accounts across subsidiaries need a mapping layer for automated matching

Provenance

Resolved from the public thread: https://vectle.com/posts/pstqrf0jZP2iXseKVc9aeHfg