Intercompany Transactions: Journal Entries and Eliminations

Intercompany transactions are transfers of goods, services, or funds between entities inside the same corporate group. Because consolidated financial statements present the group as a single economic entity, US GAAP requires these transactions to be eliminated in full under ASC 810, regardless of the parent's ownership percentage. Leave them in and you overstate revenue, expenses, assets, and liabilities on the consolidated statements without changing net income by a cent of real profit.

They are also one of the most common reasons a month-end close runs long. Two entities record the same transaction differently, the intercompany accounts fail to agree, and someone spends three days chasing a variance that started as a mis-coded invoice. This guide covers the three types, the elimination entries with worked numbers, and the accounts payable controls that stop the mismatches from happening in the first place.

What are intercompany transactions?

An intercompany transaction happens whenever one entity in a group does business with another entity in the same group. A parent charging a subsidiary a management fee, one subsidiary selling inventory to another, a shared services center paying a supplier invoice on behalf of a sister company, a treasury loan from parent to subsidiary: all of these create matching entries in two sets of books that must later be removed on consolidation.

The key point is that no economic activity has occurred from the group's perspective. Cash moved from one pocket to another. The group is neither richer nor poorer, so the consolidated statements should look as though the transaction never happened.

The three types of intercompany transactions

The direction matters mainly when a subsidiary is not wholly owned. Under ASC 810 you still eliminate 100% of the transaction, but the profit elimination on upstream sales is shared proportionally with the non-controlling interest, while downstream eliminations fall entirely on the controlling interest.

Why do intercompany transactions have to be eliminated?

Because a company cannot earn revenue from itself. If a parent sells $2 million of goods to its subsidiary and both entities record the transaction, consolidated revenue would include $2 million that never came from an outside customer. Consolidated cost of goods sold would carry the matching amount, so net income looks roughly right, but revenue, expenses, and the balance sheet totals are all inflated. Anyone using those statements to judge scale, margin, or leverage is reading numbers that do not describe the business.

ASC 810 addresses this by requiring consolidated statements to reflect only transactions with parties outside the group. The elimination is complete: you remove the full amount even if the parent owns 60% of the subsidiary rather than 100%.

Intercompany elimination entries with examples

Eliminations are made on the consolidation worksheet, not in the individual entities' general ledgers. Each entity's standalone books stay intact, which is what statutory reporting and local tax filings require.

Eliminating intercompany receivables and payables

Subsidiary A owes Subsidiary B $250,000 at year end for services billed during the year. On the consolidated balance sheet the group owes itself nothing, so both sides come off.

Eliminating intercompany revenue and expense

The parent charges subsidiaries a $500,000 management fee for the year. It is revenue to the parent and expense to the subsidiaries, and nothing left the group.

Eliminating unrealized profit in inventory

This is the entry teams get wrong most often. The parent sells inventory costing $60,000 to a subsidiary for $100,000. At year end the subsidiary still holds all of it, so the $40,000 markup has not been realized through a sale to an outside customer. Consolidated inventory is carried at $40,000 more than the group actually paid for it.

Only the portion still sitting in inventory is eliminated. If the subsidiary had already sold 75% of the goods to outside customers, the profit on that 75% is realized and stays, and you eliminate only the $10,000 remaining in stock. The full intercompany sale and purchase amounts still come out of consolidated revenue and cost of goods sold separately.

Why do intercompany accounts never balance?

In theory every intercompany balance has an exact mirror in the counterparty's ledger. In practice they disagree, and almost always for one of a short list of reasons: timing, where one entity books the invoice in March and the other in April; foreign exchange, where each side translates at a different rate; disputed charges that one entity refuses to accept; missing entries, where the receiving entity never got the invoice at all; and coding errors, where a charge lands in a trade payable account instead of the intercompany account and disappears from the reconciliation.

The last two are accounts payable problems, not consolidation problems, and they are the ones worth fixing at the source. Our guide to general ledger reconciliation covers the mechanics of tying subledgers back to control accounts, and the accounts payable subsidiary ledger explains where per-vendor detail should live.

How to control intercompany transactions in accounts payable

Most intercompany pain is created upstream, when the invoice is first processed, and inherited by whoever runs the close. Four controls do most of the work.

Use dedicated intercompany accounts. Intercompany receivables and payables need their own GL accounts, separate from trade AR and AP, with a counterparty identifier on every posting. If intercompany charges sit inside the same payable account as third party supplier invoices, nobody can produce a clean reconciliation without manual filtering.

Agree charges before they are invoiced. Disputed intercompany charges are the slowest variances to clear because there is no external party forcing resolution. Service level agreements and agreed allocation methods set annually remove most of the argument.

Code to the right entity at capture. A shared services team processing invoices for eight entities has to decide which legal entity owns each cost, often from a document that does not say. Getting entity coding right at intake, rather than in a month-end journal, is the difference between a two day close and a two week one. Pulling structured data off invoices consistently across every entity is a document data extraction problem before it is an accounting one, and it is where the error rate is set.

Reconcile monthly, not at year end. Intercompany balances should be matched every month while both parties still remember the transaction. Annual reconciliation means researching twelve months of variances with people who have moved roles.

What about transfer pricing?

Elimination is a financial reporting exercise, and it does not make intercompany pricing a free choice. Where entities sit in different tax jurisdictions, US rules under Internal Revenue Code section 482 require intercompany charges to be set at arm's length, meaning the price unrelated parties would have agreed. The consolidated statements eliminate the transaction either way, but each entity's standalone books and local tax return do not, so the price directly affects taxable income by jurisdiction and is a standard audit target. Keep contemporaneous documentation supporting how each charge was set.

Common mistakes to avoid

Eliminating only the net balance rather than both gross sides, which understates revenue and expenses. Forgetting unrealized profit on assets other than inventory, including fixed assets transferred at a markup, where the elimination continues through the asset's remaining depreciation. Eliminating a percentage of the transaction to match the ownership stake instead of the full 100%. Booking eliminations into the entities' own ledgers rather than the consolidation worksheet, which corrupts statutory reporting. And treating intercompany variances as a close problem to be plugged, rather than an AP coding problem to be fixed, which guarantees the same variance returns next month.

The bottom line

Intercompany transactions are straightforward in principle and painful in practice, and the pain is usually created at invoice intake rather than at consolidation. Get dedicated intercompany accounts, correct entity coding at capture, and monthly reconciliation in place, and the elimination entries themselves become routine. Groups running several entities through one AP team should look at accounts payable software for large business, which covers entity level coding and approval routing, and at the accounts payable month-end close checklist for the wider close process.