Intercompany Eliminations: A Practical Guide
Intercompany eliminations are the one close task that scales nonlinearly with entity count. A company with one legal entity doesn't have them at all. A company with three entities has them in one direction. A company with eight entities operating in multiple currencies has them in every direction simultaneously, with FX adjustments layered on top. And the risk isn't just complexity — it's that an uneliminated intercompany balance flows straight through to consolidated revenue, expenses, or assets, making the financial statements wrong in ways that aren't immediately obvious.
This guide walks through the mechanics of intercompany eliminations — what they are, where they break down, and how to run them consistently as your entity count grows.
What Intercompany Eliminations Actually Do
When one subsidiary sells to another, or loans money to another, both entities record the transaction. Entity A records revenue; Entity B records a corresponding expense. Entity A records a receivable; Entity B records a payable. At the consolidated level, those transactions offset each other — the group as a whole didn't transact with an external party, so the consolidated financials should show nothing.
The elimination entry removes both sides of the intercompany transaction so the consolidation reflects only external activity. Do it correctly, and the consolidated P&L shows true external revenue and expenses. Miss an elimination, and consolidated revenue is overstated by the intercompany sale amount. Miss the balance sheet side, and both consolidated assets and liabilities are overstated simultaneously.
Four categories of intercompany transactions require elimination at close:
| Transaction Type | Recorded By Selling Entity | Recorded By Buying Entity | Elimination Entry |
|---|---|---|---|
| Intercompany sale of goods/services | Revenue | Expense (or inventory/asset) | Debit revenue, credit expense |
| Intercompany loan | Intercompany receivable | Intercompany payable | Debit payable, credit receivable |
| Intercompany dividend | Dividend income | Dividend paid (retained earnings) | Debit dividend income, credit retained earnings |
| Intercompany asset transfer | Gain on sale (if any) | Asset at transferred cost | Eliminate unrealized gain, adjust asset basis |
The Matching Problem: Where Eliminations Break Down
In theory, every intercompany transaction recorded on one side has an equal and opposite entry on the other side, and they net to zero in consolidation. In practice, they almost never match exactly at period end — and the reasons are predictable enough that finance teams can build processes specifically to address them.
Timing differences
Entity A invoices Entity B on March 28. Entity B doesn't process the invoice until April 2. At the March 31 close, Entity A has recognized revenue and a receivable; Entity B has no corresponding expense or payable recorded yet. The elimination can't match what doesn't exist.
This is the most common source of intercompany imbalances. The solution is a clear intercompany cutoff policy: all intercompany transactions must be recorded in the same period by both entities, or the receiving entity must accrue the transaction at period end. Neither option is perfectly convenient, but inconsistent period recording is worse.
FX differences
When entities operate in different functional currencies, the intercompany transaction is recorded at the spot rate on the transaction date by each entity. By period end, each entity has also remeasured its intercompany balance at the closing rate. The resulting FX gains or losses on each side rarely match exactly, because each entity's remeasurement history is different.
The elimination must absorb the translation difference, typically through a cumulative translation adjustment (CTA) account in equity. Getting this right requires knowing which rate each entity used at each step — and that requires clear documentation of rate elections in advance, not reconstruction at month-end.
Inventory profit elimination
If Entity A manufactures goods and sells them to Entity B, which holds them in inventory at period end, the consolidation must eliminate the intercompany profit embedded in Entity B's inventory balance. The group hasn't sold those goods to an external customer yet — the profit is unrealized. Missing this step overstates inventory and retained earnings at the consolidated level.
This is a less common issue for service companies, but it's a material risk for any company with intercompany product flows. Most ERP systems don't automate this calculation — it requires a manual adjustment at consolidation.
Building a Repeatable Elimination Process
The finance teams that handle eliminations cleanly at scale don't approach it ad hoc. They build a repeatable process that runs the same way every period, with defined ownership and documented rules. The core components:
An intercompany account map. Every intercompany relationship should have designated GL accounts on each side — intercompany receivable on one, intercompany payable on the other; intercompany revenue and intercompany expense. When these transactions hit dedicated accounts rather than shared GL lines, they're visible for elimination matching. When they're buried in standard AP or revenue accounts, finding them requires a transaction-level search that consumes time your team doesn't have.
A pre-close intercompany confirmation process. Before the close window starts, both entities in each intercompany relationship confirm their open balances to each other. Differences surface before day 1 of close, not during it. This step alone, in our experience, reduces elimination-related close extensions by 1–2 days for companies with 3+ entities.
A single owner for consolidation adjustments. Intercompany elimination journal entries should be owned by one person — typically the corporate controller or consolidation accountant — not distributed across subsidiary controllers. Distributed ownership leads to entries posted from each entity's perspective that may not net correctly at consolidation.
The Automation Question: What Can Be Done Automatically?
For companies running NetSuite OneWorld, Sage Intacct, or similar multi-entity ERP configurations, some intercompany elimination happens within the ERP itself — particularly for simple intercompany loan balances where both sides live in the same system.
But the harder cases — cross-currency positions, intercompany profit in inventory, transactions between entities that don't share an ERP — still require manual processing at most mid-market companies. This is where automated matching logic helps: the system identifies transactions on both sides of an intercompany relationship, flags imbalances above a threshold, and suggests the elimination entry rather than requiring the accountant to construct it from scratch.
We've built Closegrove's multi-entity module around this pattern. Each entity's GL is ingested independently. The system identifies intercompany account pairs, runs matching across periods, and surfaces any out-of-balance positions with the suggested elimination entry. For a company with 5 entities and predictable intercompany flows, this typically reduces consolidation prep from 3–4 hours to under 90 minutes per close cycle.
The first time a company runs automated intercompany matching, they almost always find a historical imbalance that's been accumulating unnoticed for several periods. Not a crisis — but worth addressing cleanly before the next close.
FX Rate Governance: The Step Most Teams Skip
Currency translation for intercompany balances requires three rate elections: the transaction rate (usually spot rate on the transaction date), the balance sheet rate (usually closing rate at period end), and the income statement rate (usually average rate for the period). Each election affects both sides of the intercompany relationship and must be applied consistently.
Finance teams that document their rate elections in a simple governance document — one page, reviewed annually — eliminate most FX-related elimination disputes before they start. Teams that don't document rates end up renegotiating rate methodology at each close, which is time-consuming and introduces consistency risk over time.
The governance document should answer: Where do you source rates (ECB, Bloomberg, internal treasury)? When is the rate locked for a given period? What happens to the CTA balance — does it roll forward or get reclassified periodically? None of these are complicated decisions. But making them once and documenting them is far better than remaking them under close-day pressure.
What Happens When You Don't Eliminate
The consequences of missed eliminations range from embarrassing to material, depending on the dollar amounts involved.
On the income statement: unconsolidated intercompany revenue inflates consolidated revenue. For a company where management and investors are watching revenue growth closely, this is a significant accuracy problem — and it's also the kind of error that surfaces in due diligence and creates credibility damage at the worst possible time.
On the balance sheet: uncollected intercompany receivables and payables inflate total assets and total liabilities simultaneously. This doesn't affect net equity directly, but it distorts leverage ratios, working capital calculations, and any debt covenant that references gross asset or liability figures.
For companies preparing for audit, merger due diligence, or a financing round, clean intercompany eliminations aren't optional. They're foundational to financial statement accuracy. The effort to build a repeatable elimination process pays back many times over when those events arrive.
Start with the account map. Define ownership. Build the pre-close confirmation process. Document your rate elections. The mechanics of intercompany eliminations aren't complicated — the discipline to execute them consistently every period is what separates companies that consolidate cleanly from those that scramble every quarter.
