How do I reconcile intercompany AP allocations across subsidiaries?

Split the vendor bill at entry, allocating each line to the subsidiary that actually benefited, and book the offsetting intercompany payable/receivable pair on each side. ASC 810 requires intercompany balances and transactions to be eliminated in full at consolidation — reconciliation means each entity's books tie out individually before that elimination, not just the consolidated total.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the accounts payable and invoice processing guide.

The governing rule	ASC 810-10-45-1: intra-entity balances and transactions shall be eliminated in consolidation
What that requires operationally	Each subsidiary's allocated share, plus a matching intercompany payable/receivable pair, tracked separately before elimination
Where allocation happens	At bill entry — split by benefiting entity, not after the fact
Common break	One side books the allocation, the other doesn't, leaving an unmatched intercompany balance
What reconciliation checks	That every intercompany payable on one entity's books has a matching intercompany receivable on the other's, before consolidation elimination

Why a shared vendor bill needs splitting in the first place

A vendor bill that covers services shared across subsidiaries — a group insurance policy, a shared software license, a management fee — doesn't belong entirely to whichever entity happened to receive the invoice. Allocating it to the entities that actually benefited, at the point of entry, is what makes each subsidiary's standalone financials accurate before any consolidation step happens. Booking the whole bill against one entity and never allocating it understates that entity's expense allocation to the others and overstates its own.

The accounting rule behind the reconciliation requirement

FASB ASC 810-10-45-1 is direct: in the preparation of consolidated financial statements, intra-entity balances and transactions shall be eliminated. That's the consolidation-level rule, but it presumes something has to be true first — that each entity's own books show the intercompany balance clearly enough to eliminate. If Subsidiary A books an intercompany receivable from Subsidiary B for its share of the allocated bill, but Subsidiary B never books the corresponding intercompany payable, there's nothing clean to eliminate — the mismatch has to be found and fixed before consolidation, not discovered during it.

What reconciliation actually checks

Reconciling intercompany AP allocations means confirming, entity by entity, that every intercompany payable booked on one side has an equal and opposite intercompany receivable booked on the other — not just that the consolidated total nets to zero, which can mask an offsetting pair of unrelated errors. This is typically a monthly close step: pull each entity's intercompany balances, match them pairwise against the counterparty entity's corresponding balance, and investigate any pair that doesn't tie before the elimination entry is posted.

Next step

Map the finance workflow with the most exposure and prove the automation path.

Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.

Book a workflow review

Worked example

A $30,000 shared software bill, split three ways

A $30,000 annual software bill arrives addressed to the parent entity, but three subsidiaries actually use the tool. AP allocates it by headcount: Subsidiary A (50 employees) gets $15,000, Subsidiary B (30 employees) gets $9,000, Subsidiary C (20 employees) gets $6,000. The parent books an intercompany receivable of $15,000 from A, $9,000 from B, and $6,000 from C. If Subsidiary B's books only show $6,000 in intercompany payable to the parent instead of $9,000, that $3,000 gap is exactly what a pairwise intercompany reconciliation is built to catch — checking the consolidated total alone wouldn't reveal it if another unrelated $3,000 error happened to offset it elsewhere.

Frequently Asked Questions

Consistency matters for comparability and auditability — an allocation method that changes arbitrarily period to period makes it harder to explain variances and harder for an auditor to verify the split was reasonable. Document the method and apply it consistently, changing it only with a stated reason.

The reconciliation principle doesn't change, but the mechanics do — intercompany balances have to be pulled from each system separately and matched manually or through an integration, rather than relying on a single system's built-in intercompany matching.

It's the step before that entry, not the entry itself — reconciliation confirms the intercompany balances are accurate and matched; the ASC 810 elimination entry then removes those matched balances from the consolidated financials. Eliminating balances that were never actually reconciled just propagates the underlying error into the consolidated numbers.

Sources

How-to

How do I run intercompany elimination during period close in NetSuite?

Complete currency revaluation for every subsidiary first, then run NetSuite's Intercompany Elimination process, which nets out intercompany receivables, payables, and transactions so they don't double-count in the consolidated financials. Any currency revaluation left undone before elimination runs is the most common reason a residual balance is left over afterward.

Diagnostic

What causes a currency delta that won't eliminate in intercompany close?

Almost always, currency revaluation either didn't run before elimination, used a stale exchange rate, or the elimination subsidiary's consolidated exchange rate isn't set to 1 relative to its direct parent. Any of these leaves the two sides of an intercompany balance valued at different rates, so they can't net to exactly zero.

Topic

AP & Invoice Processing

Accounts payable and invoice processing is the set of steps a vendor bill goes through between arriving at a company and turning into a payment: capturing what the vendor sent, checking it against wha…

Definition

What's the difference between a standard PO and a blanket PO for recurring services?

A standard purchase order covers one specific transaction — a fixed quantity, at a fixed price, for a fixed delivery. A blanket purchase agreement, as federal procurement regulation defines it, is a simplified method of filling anticipated repetitive needs by establishing pre-agreed terms with a vendor, so individual releases against it don't each need a full new purchasing cycle.