Why intercompany transactions exist
A corporate group is a set of separate legal entities, and each one keeps its own ledger. Intercompany transactions follow decisions taken inside the group, and their price is agreed between the two entities rather than set by an open market. That price also carries a tax dimension known as transfer pricing: tax authorities generally expect it to follow the arm’s length principle, and the rules vary by jurisdiction. This entry does not cover them.
Why an intercompany transaction creates no new result for the group
The transaction moves value from one part of the group to another. In a corporate loan, the parent records a loan receivable and interest income while the subsidiary records a loan payable and interest expense, and the two results offset each other inside the group.
A result becomes real when the goods or services leave the group. Until an outside customer buys them, any margin recorded on a transfer stays inside the group. For that reason, IFRS 10 and ASC 810 require intragroup balances, transactions, income and expenses to be eliminated when the group prepares consolidated financial statements.
The six types of intercompany transactions
Classified by what moves between the entities, intercompany transactions fall into six types.
| Type of transaction | An example |
|---|---|
| Sale or purchase of goods and inventory | A manufacturing subsidiary sells finished goods to the group’s distribution subsidiary. |
| Services and management fees for administrative, technology, human resources or legal work | The parent charges a management fee for the finance team that runs group reporting. |
| Loans and intragroup financing | The parent lends working capital to a subsidiary and charges interest. |
| Royalties and licenses for intellectual property | A subsidiary pays a royalty to the entity that owns the group’s trademark. |
| Transfers of fixed assets and liabilities, and dividends | A subsidiary transfers a delivery fleet to a sister company, and later declares a dividend. |
| Cost allocation and shared services, and reimbursement of expenses | The group’s shared service center allocates its monthly cost across the entities it supports. |
Management fees, service recharges and allocated costs are often grouped under the name intercompany charges, because one entity bills another for something it provided rather than for goods.
The three main directions: downstream, upstream and lateral
When a source speaks of the three main types of intercompany transactions, it is classifying them by direction rather than by what moves. Direction describes where a flow starts in the group structure. A downstream transaction runs from the parent to a subsidiary, as when the parent licenses a trademark. An upstream transaction runs from a subsidiary to the parent, as when a subsidiary declares a dividend. A lateral transaction runs between two subsidiaries of the same parent.
Direction is a property of the flow rather than a separate type of transaction, and it tells the group which entity carries the profit. That matters most when the selling subsidiary is not wholly owned, because part of the internal margin it records then belongs to its noncontrolling shareholders.
How to account for intercompany transactions
Accounting for an intercompany transaction takes four steps, two inside each entity and two at group level.
- Identify the counterparty. The transaction is tagged as internal when it is created, so both entities know the other side is internal.
- Record each side in its own ledger. Each entity posts its own side, which leaves a pair: an intercompany receivable on one side and an intercompany payable on the other, each naming the counterparty.
- Match the reciprocal balances. Matching the two sides is a control that runs before consolidation and belongs to intercompany reconciliation.
- Clear the internal positions at consolidation. Elimination is an entry made during consolidation, not a type of intercompany transaction, and its rules belong to intercompany eliminations.
Intercompany transaction example: one internal sale and its entries
This example is illustrative and does not describe a product configuration. Alpha sells goods to its subsidiary Beta for USD 240,000. They cost Alpha USD 150,000, Beta still holds them at the end of the period, and no cash has changed hands.
Alpha records a receivable of USD 240,000 due from Beta, revenue of USD 240,000 and cost of goods sold of USD 150,000. Beta records inventory of USD 240,000 and a payable of USD 240,000 to Alpha.
| Where | Account | Debit (USD) | Credit (USD) |
|---|---|---|---|
| Alpha | Intercompany receivable from Beta | 240,000 | |
| Alpha | Intercompany revenue | 240,000 | |
| Alpha | Cost of goods sold | 150,000 | |
| Alpha | Inventory | 150,000 | |
| Beta | Inventory | 240,000 | |
| Beta | Intercompany payable to Alpha | 240,000 | |
| Consolidation | Intercompany revenue | 240,000 | |
| Consolidation | Cost of goods sold | 150,000 | |
| Consolidation | Inventory | 90,000 | |
| Consolidation | Intercompany payable to Alpha | 240,000 | |
| Consolidation | Intercompany receivable from Beta | 240,000 |
The reciprocal pair agrees: USD 240,000 – USD 240,000 = USD 0. Consolidation removes the USD 240,000 internal revenue, reverses the seller’s USD 150,000 cost of goods sold and reduces inventory by the USD 90,000 internal margin. The adjustment balances because USD 150,000 + USD 90,000 = USD 240,000. Consolidation also offsets the USD 240,000 receivable against the USD 240,000 payable. Consolidated inventory remains at the USD 150,000 cost to the group, with no revenue from an outside sale.
Intercompany payments, transfers and settlement
An intercompany payment settles a balance that an intercompany transaction created; it is not a separate type of transaction. In the example above, a payment from Beta to Alpha would clear the receivable and the payable without changing the sale or its margin.
Intercompany transfer has two common meanings. It can be a transfer of goods or assets, which is one of the six types in the table. It can also be a cash transfer that funds an entity, which the group records as a loan or a funding balance under its own policy. When groups net reciprocal balances, one transfer settles several invoices, and each of them still has to be traceable. A settlement that arrives short because of bank fees or another exchange rate leaves a difference that needs its own entry.
What an intercompany transaction is not
It is not an elimination, which is a consolidation entry that removes an internal balance rather than a type of operation. It is not a reconciliation, which compares the two sides of an internal relationship before consolidation as a control. It is not the journal entry either, because the entry records the transaction. The full record-keeping process around these operations belongs to intercompany accounting, and the group statements that come out of it belong to financial consolidation.
Keeping the identity of each internal transaction
The same entity pair can exchange loans, invoices and expense reimbursements in one period. Comparing only their net balance can hide differences between those flows. Each record therefore needs a transaction reference, counterparty, type, currency and period that can be carried into each entity’s intercompany journal entry.
How Simetrik supports intercompany transactions
Simetrik, an AI-native financial control platform, works on the transaction and operational data underneath intercompany balances: the invoices, recharges, loans and cash transfers each entity records, together with the bank and internal-system records that settle them. Simetrik can prepare those records for configured comparisons that pair each internal transaction with its counterpart by reference, counterparty, type, currency and period. The deterministic engine gives the same result with the same inputs and rules, and what does not pair stays open as an exception for review.
Detecting a difference at transaction level is faster to trace than correcting it at balance level. A recharge booked by only one entity, a settlement that arrives short because of bank fees or a transfer converted at another rate shows up next to the transaction that caused it. Simetrik then connects that evidence with account-level balance review: its accounting operations controls compare each ledger balance with the reconciled balance by period, with a preparer who documents the evidence and a certifier who signs it. For the finance team, the practical check is whether a remaining balance can be traced to the transaction that created it and to the entity responsible for resolving it. When the correcting entries come from reconciled data, Simetrik’s automated journal entry management generates them under a configured posting model.