What is intercompany accounting?

Intercompany accounting is the practice of recording, reconciling, and eliminating transactions that occur between two or more entities under common ownership, such as a parent and its subsidiaries or two sister subsidiaries. It covers intercompany sales, loans, interest, cost allocations, management fees, and dividends. The defining feature is that these transactions are internal to the group, so they must be removed in consolidation to avoid overstating revenue, expense, assets, and liabilities. The group should report only what it transacts with parties outside the group. This guide is general information, not accounting, tax, or legal advice.

What are the main types of intercompany transactions?

The main types of intercompany transactions are: sales of goods or services between entities; intercompany loans and the related interest; cost allocations, management fees, and shared-service recharges; and dividends or capital transfers between a parent and a subsidiary. Each type creates matched entries on two sets of books that must agree. Intercompany accounting tracks both sides of every transaction so that, at consolidation, the offsetting entries can be eliminated in full and the group reports only third-party activity.

What are intercompany eliminations and why do they matter?

Intercompany eliminations are the consolidation entries that remove transactions and balances between group entities so they do not double-count in the consolidated financial statements. Under U.S. GAAP, ASC 810 requires that intercompany balances and transactions be eliminated in full. Without eliminations, internal sales would inflate group revenue, and an intercompany loan would appear as both an asset and a liability of the same group. Eliminations also remove unrealized intercompany profit, such as margin on inventory one entity sold to another that has not yet been sold outside the group.

Do intercompany transactions net to zero in consolidation?

Yes. Properly matched intercompany transactions net to zero at the consolidated level because each side has an equal and opposite entry: one entity records revenue and the other records cost, one records a receivable and the other a payable. The elimination entry cancels both. Net-to-zero only holds when the two sides match. If amounts, currencies, or periods differ, a residual remains, which is exactly why intercompany reconciliation exists. Unrealized intercompany profit is also eliminated, which can defer, not just cancel, group profit until the asset leaves the group.

What causes intercompany reconciliation problems?

Three issues drive most intercompany reconciliation problems. First, mismatches: one entity records a transaction the counterparty records differently or not at all, so the two sides do not agree. Second, currency differences: when entities use different functional currencies, the same transaction is booked at different rates or dates and produces an FX difference on elimination. Third, timing and cut-off: one entity posts in the current period and the other in the next, with goods in transit at period end as the common example. Distinguishing real errors from timing differences is the core of the work.

How does intercompany accounting work in an ERP system?

In a multi-entity ERP system, intercompany accounting is handled by tagging transactions with both the originating and receiving entity, automating the matched counterparty entries, and running eliminations as part of the consolidation routine. A multi-entity platform maintains a single chart of accounts and currency framework across subsidiaries, so intercompany pairs can be matched and FX handled consistently. This removes the spreadsheet reconciliation that fails at scale. Our guides on multi-entity accounting and what an ERP is cover how the underlying system supports this.

How does intercompany accounting differ from intercompany transfer pricing?

Intercompany accounting is the financial-reporting discipline of recording and eliminating internal transactions for consolidation. Transfer pricing is the tax discipline of setting the price at which group entities transact, so that profit is allocated across jurisdictions on an arm-length basis. They interact: the transfer price determines the amounts that intercompany accounting records and later eliminates, and the unrealized profit removed in consolidation depends on the margin built into that price. They are governed by different rules and different authorities, so they are managed together but not interchangeable.

Why is intercompany accounting harder for global, multi-entity groups?

Complexity scales with the number of entities, currencies, and jurisdictions. Each new subsidiary adds counterparty pairs to match, and each new functional currency adds FX differences to isolate. Cross-border groups also face transfer-pricing rules and local statutory reporting alongside group consolidation. The result is more transactions to reconcile, more timing differences across calendars, and a close that strains spreadsheets. This is why growing and global organizations move intercompany accounting into a multi-entity ERP with native consolidation and elimination tooling.

Why do intercompany balances still appear after running elimination in NetSuite?

Residual intercompany balances after an elimination run usually trace to a small number of causes. Intercompany journal entries recorded without a counterparty entity never pair, so they stay open and get picked up in monthly currency revaluation, which is why the residual often reads as a foreign-exchange amount. Transactions posted after the elimination run for a period never enter that period elimination. And accounts or journal lines that are missing the elimination flag are never included in any elimination at all. The remedy is to flag intercompany accounts correctly, specify the representing entity on journal entries so both sides pair, and run the close in order: post all transactions, then currency revaluation, then intercompany elimination.

JH Written by Jully Hayasaka with Robert LabardeeNetSuite Advanced Accounting Lead and Founder and CEO

Intercompany Accounting: Transactions, Eliminations, Reconciliation

Lightbridge ERP defines intercompany accounting as the recording, reconciliation, and elimination of transactions between entities under common ownership. It tracks sales, loans, cost allocations, and dividends that move between subsidiaries, then removes them in consolidation so the group reports only what it transacts with outside parties.

Talk to an ERP advisor Multi-entity accounting

This guide is general information, not accounting, tax, or legal advice. The authoritative consolidation guidance is the FASB Accounting Standards Codification (ASC 810) at asc.fasb.org.

Intercompany accounting records and eliminates transactions between entities under common ownership.

Intercompany accounting governs how a group handles transactions between its own entities: parent to subsidiary, subsidiary to subsidiary, or treasury to operating unit. These transactions are real and have to be booked on each entity's separate ledger. They are also internal to the group, which means they cannot count toward how the group performs against the outside world.

The principle behind it sits in consolidation guidance. Under U.S. GAAP, ASC 810 requires intercompany balances and transactions to be eliminated in full when preparing consolidated financial statements. International groups apply the parallel requirement under IFRS 10. A group with 5 subsidiaries and a parent has 6 sets of books to consolidate into one, and every transaction that crossed an internal boundary has to be found and removed.

The reason is double-counting. If one subsidiary sells inventory to another, recording that sale as group revenue would inflate the top line with money the group simply moved from one pocket to another. Intercompany accounting exists so the consolidated statements show only what the group transacts with third parties. To understand the wider system this runs inside, see our guides on multi-entity accounting and what an ERP is.

Intercompany transactions fall into four recurring types.

Most intercompany activity reduces to a small number of patterns. Each creates a matched pair of entries on two sets of books, and each must be tracked so it can be eliminated in consolidation. The four types below cover the bulk of what a multi-entity group records between its own entities.

Type 1

Sales of goods and services

One entity bills another for product, inventory, or services. Intercompany accounting records the revenue on the seller and the cost or asset on the buyer, then flags the pair so consolidation can remove both. Any profit the seller booked on inventory the buyer still holds is unrealized to the group.

Type 2

Intercompany loans and interest

A parent or treasury entity lends to a subsidiary. The lender carries a receivable and interest income; the borrower carries a payable and interest expense. In consolidation the loan principal, the receivable, the payable, and the matched interest all eliminate, since the group cannot lend to itself.

Type 3

Cost allocations and shared services

Headquarters spreads overhead, IT, or management fees across subsidiaries. Intercompany accounting routes the charge from the cost center to the receiving entity. The expense and the recharge offset at the group level, so consolidation strips the internal markup and reports only the original outside cost.

Type 4

Dividends and capital transfers

A subsidiary distributes profit upward, or the parent injects capital downward. Intercompany accounting records the dividend income at the parent against the distribution at the subsidiary. These eliminate in consolidation because a dividend inside the group is a transfer of equity, not income to the consolidated entity.

Each type sits on both entities' ledgers until consolidation removes it. NetSuite handles multi-subsidiary intercompany flows natively: see how NetSuite OneWorld manages subsidiaries, currencies, and intercompany transactions inside one system.

Intercompany eliminations remove internal activity so consolidation is not double-counted.

Eliminations are the consolidation entries that cancel intercompany transactions and balances. When the two sides match, they net to zero: one entity's revenue offsets the other's cost, one entity's receivable offsets the other's payable. ASC 810 requires this elimination in full, not a partial or proportional adjustment, so no trace of the internal transaction survives into the consolidated result.

Eliminations also reach profit that has not yet been earned by the group. If one subsidiary sells inventory to another at a markup, and the buyer still holds that inventory at period end, the seller's profit is unrealized to the group because nothing has left to an outside customer. Intercompany accounting defers that unrealized profit until the asset is sold externally. This is why eliminations can postpone group profit, not only cancel matched entries.

The mechanics matter at close. A group consolidating dozens of entities runs eliminations every period, and an elimination that does not net to zero signals a problem upstream. That residual is the entry point to reconciliation, the discipline that finds why the two sides disagreed in the first place.

Intercompany reconciliation fails on mismatches, currency, and timing.

Reconciliation is the process of confirming that both sides of every intercompany transaction agree before eliminations run. When they do not, the elimination leaves a residual that lands in the consolidated result and stalls the close. Three failure modes account for most of the pain, set out in the cards below.

Out-of-balance mismatches

Entity A books an intercompany sale that Entity B never records as a purchase, or records at a different amount. The two sides disagree, so the elimination does not net to zero and a residual lands in the consolidated result. Mismatches are the most common intercompany reconciliation failure and the first thing close teams chase.

Currency (FX) differences

When the two entities report in different functional currencies, the same transaction is booked at different exchange rates or on different dates. The pair no longer matches in either currency, so an FX difference appears on elimination. Intercompany FX has to be isolated and explained, not absorbed into operating results.

Timing and cut-off differences

One entity records a transaction in the current period and the counterparty records it in the next. Goods in transit at period end are the classic case. The accounts disagree until the timing difference clears, so reconciliation has to identify which mismatches are real errors and which are pure cut-off.

The deeper the entity count and the more currencies in play, the harder reconciliation becomes. A group on spreadsheets feels this first at the close, which is the signal that intercompany accounting belongs in a system, not a workbook.

Long-term intercompany balances can route currency gains to the CTA, not earnings.

Most intercompany balances denominated in a foreign currency produce a remeasurement gain or loss in net income each period as exchange rates move. There is an important exception. When an intercompany balance, typically a long-term advance or loan between a parent and a foreign subsidiary, is of a long-term-investment nature, meaning settlement is not planned or anticipated in the foreseeable future, ASC 830 and IAS 21 treat it as part of the net investment in the foreign operation. The exchange gain or loss on that balance is then reported in other comprehensive income as part of the cumulative translation adjustment, rather than in earnings, so it does not whipsaw the income statement period to period.

The test is substance, not labeling. A balance genuinely expected to be settled keeps its exchange gain or loss in earnings, while one that is permanent in nature follows the net investment to the cumulative translation adjustment, and reclassifies to income only when the foreign operation is sold or substantially liquidated. Groups should document the intent for each long-term intercompany balance and configure the ERP to flag those of a long-term-investment nature. For the underlying mechanics, see the guide to foreign currency translation and the cumulative translation adjustment; for how related entities set the prices behind these balances, see transfer pricing.

A multi-entity ERP runs intercompany accounting inside the system, not in spreadsheets.

In a multi-entity ERP, intercompany accounting is structural rather than manual. Transactions are tagged with both the originating and receiving entity, so the system knows each side of every pair. Matched counterparty entries can be automated, currencies are handled in one framework, and eliminations run as part of the consolidation routine instead of a month-end spreadsheet exercise. The mismatches, FX differences, and timing breaks that slow a manual close become exceptions the system surfaces, not balances a person hunts for.

This is where the right platform earns its keep. A system that maintains a single chart of accounts, a consolidated currency model, and native elimination logic across subsidiaries turns intercompany accounting from a recurring fire drill into a repeatable routine. Our multi-entity accounting guide covers the broader consolidation picture, and NetSuite OneWorld shows one platform's native approach to subsidiaries and intercompany flows.

NetSuite OneWorld runs intercompany accounting at scale through automated transactions, netting, and elimination subsidiaries.

NetSuite OneWorld is the multi-subsidiary edition of NetSuite, built so that intercompany accounting is a system routine rather than a spreadsheet exercise. Automated Intercompany Management, enabled under the accounting features, creates the matched counterparty entries automatically: intercompany sales orders, purchase orders, bills, and invoices post to both entities at once, so neither side of a pair is left to a person to remember. An arm-length intercompany flow can also run from paired intercompany invoices and bills alone when no goods physically move between entities. See NetSuite OneWorld and multi-entity accounting for the surrounding structure.

Elimination happens through elimination subsidiaries and account-level flags. An account is treated as an intercompany account only when its record carries the Eliminate Intercompany Transactions box, which is what keeps intercompany receivables, payables, and clearing balances out of consolidated results. An elimination subsidiary is created as a child of any parent that has children, and it is where NetSuite posts the reversing elimination journal entries at each parent-child level. When intercompany elimination runs, NetSuite generates those entries for every intercompany line flagged for elimination, so the internal activity nets out at consolidation. Public NetSuite documentation describes both the elimination subsidiary model and the account checkbox that drives it.

Two more features carry the load at volume. Intercompany Netting combines the mutual balances between two subsidiaries and settles the net position in a single transaction, which cuts the count of open intercompany transactions a close team has to revalue and reconcile. Consolidated exchange rates, calculated at each period-end close, translate each subsidiary into the parent currency so foreign-currency intercompany balances roll up consistently in consolidated reports. Consolidated reporting in OneWorld then rolls every subsidiary up through the elimination subsidiaries into a single group view. Currency revaluation of open intercompany balances is exactly where residuals appear, which the worked example below makes concrete.

A worked example: why intercompany balances still show up after elimination.

This example is illustrative, not a real engagement. Consider a group with a parent and two subsidiaries, one reporting in U.S. dollars and one in euros. The euro subsidiary lends to the dollar subsidiary and both entities book the loan through intercompany receivable and payable accounts. At consolidation, the receivable and the payable should offset and the elimination should net to zero. Instead, a residual keeps appearing in the consolidated report each month, and on inspection it is made up mostly of currency revaluation.

The pattern behind this is common and has a small number of root causes. First, when intercompany balances are recorded as journal entries without a counterparty entity specified, the two sides never pair, so they stay open and get picked up in every monthly currency revaluation, which is why the residual reads as an FX amount. Second, transactions posted after the elimination run for a period never enter that period's elimination and linger at the consolidated level. Third, if an intercompany account is missing the Eliminate Intercompany Transactions flag, or a specific journal line is not marked for elimination, those balances are never included in any elimination run at all.

The fix is configuration and sequence, not a bigger workbook. Intercompany accounts must carry the elimination flag, journal entries must specify the representing entity so the two sides can pair, and the close must run in order: post every transaction first, then currency revaluation, then intercompany elimination. Getting that order wrong is one of the most common reasons a residual survives into consolidated reporting. For the wider consolidation mechanics, see financial consolidation models, and for the currency side of long-term intercompany balances, see foreign currency translation and the cumulative translation adjustment.

Lightbridge ERP designs intercompany accounting that closes cleanly.

Knowing that intercompany transactions must eliminate in full is one thing. Building a multi-entity system where they actually do, every period, is another. Lightbridge ERP is an independent, vendor-neutral advisory firm whose senior finance professionals (CPAs, controllers, and former CFOs) design intercompany and consolidation structures that map matched entries, currency handling, and elimination logic to the platform that runs the group's books.

Because Lightbridge accepts no vendor kickbacks, no reseller quotas, and no partner-tier incentives, the platform recommendation follows fit, not commission. For organizations on NetSuite, the practice delivers multi-entity and intercompany configuration in-house. For other platforms, Lightbridge provides program governance and technical leadership while vetted partners execute. The aim is constant: an auditable consolidation where intercompany activity nets to zero and the close does not stall. This page is general information, not accounting, tax, or legal advice.

Intercompany accounting: frequently asked questions

What is intercompany accounting?: Intercompany accounting is the practice of recording, reconciling, and eliminating transactions that occur between two or more entities under common ownership, such as a parent and its subsidiaries or two sister subsidiaries. It covers intercompany sales, loans, interest, cost allocations, management fees, and dividends. The defining feature is that these transactions are internal to the group, so they must be removed in consolidation to avoid overstating revenue, expense, assets, and liabilities. The group should report only what it transacts with parties outside the group. This guide is general information, not accounting, tax, or legal advice.
What are the main types of intercompany transactions?: The main types of intercompany transactions are: sales of goods or services between entities; intercompany loans and the related interest; cost allocations, management fees, and shared-service recharges; and dividends or capital transfers between a parent and a subsidiary. Each type creates matched entries on two sets of books that must agree. Intercompany accounting tracks both sides of every transaction so that, at consolidation, the offsetting entries can be eliminated in full and the group reports only third-party activity.
What are intercompany eliminations and why do they matter?: Intercompany eliminations are the consolidation entries that remove transactions and balances between group entities so they do not double-count in the consolidated financial statements. Under U.S. GAAP, ASC 810 requires that intercompany balances and transactions be eliminated in full. Without eliminations, internal sales would inflate group revenue, and an intercompany loan would appear as both an asset and a liability of the same group. Eliminations also remove unrealized intercompany profit, such as margin on inventory one entity sold to another that has not yet been sold outside the group.
Do intercompany transactions net to zero in consolidation?: Yes. Properly matched intercompany transactions net to zero at the consolidated level because each side has an equal and opposite entry: one entity records revenue and the other records cost, one records a receivable and the other a payable. The elimination entry cancels both. Net-to-zero only holds when the two sides match. If amounts, currencies, or periods differ, a residual remains, which is exactly why intercompany reconciliation exists. Unrealized intercompany profit is also eliminated, which can defer, not just cancel, group profit until the asset leaves the group.
What causes intercompany reconciliation problems?: Three issues drive most intercompany reconciliation problems. First, mismatches: one entity records a transaction the counterparty records differently or not at all, so the two sides do not agree. Second, currency differences: when entities use different functional currencies, the same transaction is booked at different rates or dates and produces an FX difference on elimination. Third, timing and cut-off: one entity posts in the current period and the other in the next, with goods in transit at period end as the common example. Distinguishing real errors from timing differences is the core of the work.
How does intercompany accounting work in an ERP system?: In a multi-entity ERP system, intercompany accounting is handled by tagging transactions with both the originating and receiving entity, automating the matched counterparty entries, and running eliminations as part of the consolidation routine. A multi-entity platform maintains a single chart of accounts and currency framework across subsidiaries, so intercompany pairs can be matched and FX handled consistently. This removes the spreadsheet reconciliation that fails at scale. Our guides on multi-entity accounting and what an ERP is cover how the underlying system supports this.
How does intercompany accounting differ from intercompany transfer pricing?: Intercompany accounting is the financial-reporting discipline of recording and eliminating internal transactions for consolidation. Transfer pricing is the tax discipline of setting the price at which group entities transact, so that profit is allocated across jurisdictions on an arm-length basis. They interact: the transfer price determines the amounts that intercompany accounting records and later eliminates, and the unrealized profit removed in consolidation depends on the margin built into that price. They are governed by different rules and different authorities, so they are managed together but not interchangeable.
Why is intercompany accounting harder for global, multi-entity groups?: Complexity scales with the number of entities, currencies, and jurisdictions. Each new subsidiary adds counterparty pairs to match, and each new functional currency adds FX differences to isolate. Cross-border groups also face transfer-pricing rules and local statutory reporting alongside group consolidation. The result is more transactions to reconcile, more timing differences across calendars, and a close that strains spreadsheets. This is why growing and global organizations move intercompany accounting into a multi-entity ERP with native consolidation and elimination tooling.
How does NetSuite OneWorld handle intercompany eliminations?: NetSuite OneWorld handles intercompany eliminations through elimination subsidiaries and account-level flags. An elimination subsidiary is created as a child of any parent that has child subsidiaries, and it is where NetSuite posts the reversing elimination journal entries at that parent-child level. An account is treated as intercompany only when its record carries the Eliminate Intercompany Transactions box, which keeps intercompany receivables, payables, and clearing balances out of consolidated results. When intercompany elimination runs, NetSuite generates elimination journal entries for every intercompany line flagged for elimination. Automated Intercompany Management, Intercompany Netting, and consolidated exchange rates support the same process at scale. This description is grounded in public NetSuite documentation. Lightbridge ERP is an independent, vendor-neutral advisor and a former NetSuite partner.
Why do intercompany balances still appear after running elimination in NetSuite?: Residual intercompany balances after an elimination run usually trace to a small number of causes. Intercompany journal entries recorded without a counterparty entity never pair, so they stay open and get picked up in monthly currency revaluation, which is why the residual often reads as a foreign-exchange amount. Transactions posted after the elimination run for a period never enter that period elimination. And accounts or journal lines that are missing the elimination flag are never included in any elimination at all. The remedy is to flag intercompany accounts correctly, specify the representing entity on journal entries so both sides pair, and run the close in order: post all transactions, then currency revaluation, then intercompany elimination.

From intercompany chaos to a consolidation that nets to zero.

When the close depends on every intercompany pair agreeing, Lightbridge ERP designs the multi-entity structure and elimination logic that make it hold. Vendor-neutral, no kickbacks, senior finance talent.

Talk to an ERP advisor Read the multi-entity accounting guide