This happens more than most finance teams admit. In BlackLine's 2023 survey of companies with international operations and revenue above $500 million, 97% of respondents had resolved material multi-million-dollar variances tied to intercompany accounting.
Intercompany accounting has four distinct stages: recording the transaction in each entity's books, reconciling reciprocal balances, settling amounts when appropriate, and eliminating internal activity during consolidation. Skip or rush any one of these, and the close slows down.
This guide walks through transaction recording, journal-entry logic, reconciliation steps, common exceptions, and the controls that keep intercompany accounting audit-ready.
Key Takeaways
- Intercompany transactions need matching entries in both ledgers: same counterparty, amount, date, currency, and documentation.
- Reconciliation means comparing reciprocal due-to/due-from, payable/receivable, and loan balances until every difference is explained.
- Reliable intercompany accounting runs on standardized policy, clear ownership, and an audit-ready correction trail.
- A growing reconciliation backlog usually signals a deeper close or systems problem, not a string of typos.
What Intercompany Reconciliation Means in Accounting
Intercompany reconciliation is the process of comparing transactions and balances recorded by two or more related entities to confirm reciprocal amounts agree before consolidation. If Entity A records a $50,000 receivable from Entity B, Entity B's books should show a $50,000 payable to Entity A. When they don't match, that's what reconciliation exists to catch.
This due-to/due-from relationship sits at the center of nearly every intercompany entry, whether it's a parent funding a subsidiary or two sister companies splitting shared costs.
Reconciliation vs. Settlement vs. Elimination
These three terms get used interchangeably. They shouldn't be:
- Reconciliation compares what each entity recorded and confirms the amounts agree.
- Settlement transfers or nets funds between entities after balances are agreed upon.
- Elimination removes intra-group revenue, expenses, receivables, payables, and loans from consolidated financial statements.
Under ASC 810, consolidated reporting rules require eliminating intra-entity balances and transactions, including open accounts, sales, purchases, and interest. A balance can reconcile perfectly and still need elimination at consolidation. These are separate steps, not synonyms.
Why This Process Matters
Clean intercompany reconciliation supports:
- Accurate entity-level financial statements for local reporting and tax filings
- Reliable consolidated results that auditors can rely on
- A documented trail for audit requests and technical accounting questions
- Management reporting that reflects true, not inflated, intercompany activity
- A month-end close that doesn't stall on unexplained variances
Transaction types that typically require reconciliation include:
- Intercompany services and management fees
- Shared-cost allocations and expense reimbursements
- Inventory or asset transfers
- Cash movements, loans, and interest
- Centralized payments made on one entity's behalf
How to Record Intercompany Transactions
Before anything gets posted, a handful of details need to be locked down: the legal entities involved, transaction type, counterparty, account mapping, currency, transaction date, settlement terms, and any tax or transfer-pricing considerations. Skipping this step is where most reconciliation headaches start.
Sales and Services
When one entity provides a service or sells goods to another:
- The providing entity generally records intercompany revenue or a receivable, depending on its accounting policy.
- The receiving entity records a corresponding expense, asset, or payable based on what it received.
The exact accounts and treatment depend on the transaction and the company's specific accounting policies. There's no universal journal entry that fits every scenario.
Loans and Funding
Intercompany loans follow a mirror-image structure:
- The lender records a receivable or loan asset.
- The borrower records a matching payable or loan liability.
Both sides need to align on principal, interest rate, maturity, currency, and repayment terms. A loan that's booked at 5% interest on one side and 4.5% on the other will surface as a reconciling item every single period until someone fixes it.
Shared Costs and Reimbursements
When one entity pays an expense that benefits multiple entities, it needs to coordinate the allocation or recharge with whoever ultimately bears the cost. The entity that pays shouldn't be left holding the full expense if another entity benefited from it.
Cash Transfers
A word of caution here: cash movement alone doesn't determine the accounting treatment. Moving money from Entity A to Entity B could be a loan, an expense reimbursement, a capital contribution, or a dividend. The underlying nature of the transaction drives the entry, not the wire transfer itself.
Illustrative Journal Entry
Say Entity A provides $10,000 in management services to Entity B.
Entity A's books:
- Debit: Intercompany Receivable – Entity B, $10,000
- Credit: Intercompany Revenue, $10,000
Entity B's books:
- Debit: Management Fee Expense, $10,000
- Credit: Intercompany Payable – Entity A, $10,000
At consolidation:
- Eliminate the $10,000 receivable against the $10,000 payable
- Eliminate the $10,000 revenue against the $10,000 expense
Unusual, material, cross-border, or tax-sensitive entries deserve a second look against company policy, and often a conversation with an accounting or tax adviser before they're finalized.
How to Perform an Intercompany Reconciliation
Before close even starts, scope the reconciliation: reporting period, entity pairs, accounts, transaction types, currencies, source systems, and who's preparing versus reviewing. A loosely scoped reconciliation turns into a scramble on day three of close.
Gather, Build, and Match
- Pull records from each entity : general-ledger detail, intercompany invoices, loan schedules, allocation files, and supporting agreements.
- Build a counterparty matrix mapping each entity pair to its reciprocal accounts (due-to/due-from, intercompany payables, loans, interest, clearing accounts).
- Match transactions using consistent identifiers: counterparty, amount, currency, posting date, invoice number, and transaction type.
Not every match is one-to-one. Batched payments, allocations, and consolidated charges often need a many-to-one or one-to-many matching approach instead.
Investigate Every Difference
Treating a variance as one lump "unexplained balance" doesn't solve anything. Break it down:
- Separate timing differences (expected to clear next period) from actual errors
- Trace missing, duplicate, or misclassified entries back to source documentation
- Recalculate currency conversions, fees, interest, and allocations that can create legitimate differences
Resolve, Approve, Document
- Post correcting entries to the right entity and period, or document clearly why no adjustment is needed
- Get review and approval on anything material or judgmental
- Keep workpapers, explanations, evidence, and approvals on file
PwC's intercompany process guide identifies completion checklists, segregation of duties, and correction logs as core elements of a disciplined process. Confirm completion by agreeing final reciprocal balances, updating the exception log, and flagging which items still need consolidation elimination.
Common Differences and How to Resolve Them
Most intercompany variances fall into a handful of predictable buckets. Knowing which bucket you're in determines the fix.
| Difference Type | First Response |
|---|---|
| Timing differences | Confirm cut-off dates and document the expected clearing period; don't "correct" a valid timing item |
| One-sided or missing entries | Identify which entity failed to record it, post the missing entry with documentation |
| Different amounts | Check gross-vs-net treatment, fees, allocations, interest, and currency conversion |
| Wrong counterparty or account | Correct the entity code or classification, check downstream elimination impact |
| Duplicate or unsupported activity | Trace the source, reverse duplicates, escalate unsupported items per policy |
A Worked Example
Entity A shows a $75,000 receivable from Entity B. Entity B's payable shows $72,000. The $3,000 gap traces to a bank fee Entity A deducted before remitting funds, which Entity B never recorded.
Correcting action: Entity B books the $3,000 fee as an expense, and the balances now agree at $72,000.
Currency Differences Need Special Handling
Not every foreign currency gap is an error. PwC's foreign currency guidance notes that when a U.S. parent makes a USD-denominated loan to a foreign subsidiary, the subsidiary remeasures the loan and recognizes a transaction gain or loss.
The loan principal eliminates in consolidation. The FX gain or loss generally doesn't. Treating that as a posting error wastes time chasing something that was never broken.
When to Escalate
Unresolved items should go to the controller, CAO, CFO, or an outside technical accounting adviser when they're material, judgmental, recurring, cross-border, or likely to affect consolidated reporting. Waiting until year-end to escalate a known problem rarely ends well.
Controls and Best Practices for Reliable Intercompany Accounting
Reliable intercompany accounting starts before close. The goal is to prevent the mess, not work harder cleaning it up.
Standardize the Policy
- Define permitted transaction types, required documentation, account mappings, counterparty codes, and currencies upfront
- Set exchange-rate sources, cut-off rules, and settlement terms consistently across entities
- Build a shared chart-of-accounts and counterparty reference where systems allow it, documenting necessary local exceptions
Assign Clear Ownership
Someone needs to own each step: initiating, recording, reconciling, reviewing, approving, settling, and eliminating. Without named owners, reconciliation becomes whoever-has-time-this-month, and that's how backlogs form.
Reconcile Throughout the Period, Not Just at Close
- Run pre-close checks on high-volume or high-value activity
- Perform formal reconciliations at a defined cadence
- Track aging, recurring exceptions, and late submissions to spot weak points early
Strengthen Source Data
Shared invoice numbers, payment IDs, and counterparty codes on both sides of a transaction make matching dramatically faster. Link every entry back to the agreement, allocation calculation, or approval that supports it.
Don't Skip FX and Complex Transaction Controls
Document your exchange-rate convention, remeasurement treatment, and rounding tolerance. Loans, interest, asset transfers, and acquisition-related entries deserve extra review. These are the items most likely to need a technical accounting judgment call.
Use Automation Where It Helps
Standardized data feeds, matching rules, exception queues, and approval workflows cut down on repetitive manual work. Automation should supplement judgment, not replace it. A workflow tool can flag a mismatch; it can't tell you whether the resulting entry is defensible under ASC 810.
When reconciliation backlogs keep recurring, or a control deficiency surfaces, the issue is often bigger than the spreadsheet. Stratum Advisory Partners works with finance teams facing exactly this: persistent reconciliation gaps, control deficiencies, complex technical accounting questions, or a gap in interim controller or CAO leadership. That kind of support can mean stepping in to rebuild the reconciliation process itself, or providing the technical accounting judgment a recurring exception requires.
Conclusion
Effective intercompany accounting connects accurate recording, disciplined reconciliation, appropriate settlement, and documented consolidation eliminations into one coherent process.
Start with a counterparty matrix. Standardize posting rules. Assign clear ownership. Keep an exception log that tracks root causes, not just closed items. These four moves resolve more backlogs than any single software purchase.
If your team is wrestling with recurring intercompany differences, a slow close, or a technical accounting question that needs a defensible answer, Stratum Advisory Partners provides tailored advisory support: strengthening reconciliation controls, or filling an interim controller or CAO role when you need extra capacity.
Frequently Asked Questions
How do you handle intercompany reconciliations?
Gather records from both entities, compare reciprocal balances, and investigate every difference rather than treating it as one lump variance. Post corrections or document why none is needed, get review and approval, and retain the workpapers as an audit trail.
How do you record intercompany transactions?
Both related entities record corresponding entries with aligned counterparties, amounts, dates, currencies, and account classifications. The exact accounts used depend on the transaction type and the company's accounting policy.
What is intercompany reconciliation in accounting?
It's the process of comparing transactions and balances between related entities to confirm they agree before settlement and consolidation. It's distinct from elimination, which happens later in the consolidated financial statements.
Why is intercompany reconciliation important?
It supports accurate entity-level books, reliable consolidated reporting, and a documented trail for auditors. Without it, the close stalls on unexplained balances that nobody can quickly trace.
What are the most common causes of intercompany reconciliation differences?
Timing differences, missing or one-sided entries, wrong counterparties or account mapping, different amounts from fees or currency conversion, and duplicate postings account for most variances.
How often should intercompany accounts be reconciled?
Cadence should match transaction volume, materiality, and risk. Most companies monitor high-activity accounts throughout the period and perform a formal reconciliation at every reporting close.
