Every intercompany transaction is two entries in two sets of books. That is where the trouble starts.

Intercompany journal entries are the mechanism by which transactions between related entities get recorded, and they are among the most friction-heavy entries in a multi-entity close. Every intercompany expense, cash movement, or allocation has to be booked on both sides of the transaction, in the right entity, at the right amount, and often in two different currencies.

The volume compounds with scale. A ten-entity group with cash pooling, management fees, and shared services generates intercompany entries every day, each one doubling the line count of a normal entry and each mismatch surfacing later as a reconciliation exception or an out-of-balance elimination.

This article covers what intercompany journal entries are, worked examples including the multi-currency case, the process and controls, and what changes when an agent prepares them. For entry types, packet standards, and the approval matrix that applies to every journal entry, see the definitive guide to journal entries in accounting.

Key takeaways:

• Intercompany journal entries record transactions between entities in the same corporate group. Each transaction requires mirror entries in both entities’ books.

• The common types are loans and cash transfers, management fees, shared-service allocations, intercompany sales, and cash pooling or sweep activity.

• Multi-currency intercompany entries add FX remeasurement under ASC 830, which is where manual processes break down first.

• Because these entries feed eliminations at consolidation, an error on either side surfaces downstream, at the worst time.

  
  

Intercompany journal entries definition

Intercompany journal entries are the entries that record transactions between two or more entities within the same corporate group: one entity records its side of the transaction (a receivable, an expense, a cash outflow) and the counterparty records the mirror image (a payable, income, a cash inflow). At consolidation, these balances are eliminated so the group does not report transactions with itself.

What makes them harder than ordinary entries is the duplication under different conditions. The two sides may sit in different subsidiaries in the ERP, use different charts of accounts, and report in different currencies. In NetSuite, this is why Advanced Intercompany Journal Entries exist as their own transaction type, often with double the lines of a standard entry, and why teams without automation end up adjusting subsidiaries, accounts, and currencies line by line or through error-prone CSV imports.

A worked example: management fee between two entities

A US parent charges its subsidiary a $45,000 monthly management fee. Two entries, two sets of books:

Parent (Entity A):

Subsidiary (Entity B):

The entries must mirror: same amount, same period, opposite direction. If Entity B books its side in April while Entity A booked March, the intercompany reconciliation shows a timing difference and the elimination will not tie until it resolves. The memo standard from the journal entries guide applies doubly here: both entries should reference the intercompany agreement, the period, and the counterparty entity, so a reviewer on either side can verify the pair without a call across time zones.

The multi-currency case: where manual breaks first

Now make Entity B a Japanese subsidiary reporting in JPY. The fee is invoiced in USD; Entity B books the payable at the spot rate, and at month-end the open balance must be remeasured at the period-end rate under ASC 830, with the difference booked to FX gain or loss. Multiply that by cash pool interest, bank sweeps, rent settlements, and zero-balance transfers moving between a USD account and a JPY account daily, and the preparation becomes a genuinely hard workbook: currency tabs, a manual transfer schedule, a rollforward, and a CTA calculation, all cross-referenced, before the entries can even be drafted.

The scale is what breaks manual process. Rippling automated reconciliation across 148 bank accounts and $55 billion in transaction volume, cut cash reconciliation time by more than half, and moved four people to higher-value work. That is a volume of daily multi-currency movement no team books line by line.

The intercompany journal entry process

1. Establish the recording logic once

Which entity initiates, which accounts on each side, what rate source and rate date for FX, and whether settlements are recorded gross or net. Most intercompany reconciliation pain traces back to two entities answering these questions differently.

2. Prepare both sides from the same source data

Both entries should derive from one source: the intercompany invoice, the cash pool report, the allocation schedule. Preparing each side independently from separate exports is how the $45,000 becomes $45,000 on one side and $44,998 on the other.

3. Build the supporting schedule

For recurring intercompany activity, the support is a workbook: activity by currency, transfers, a rollforward from beginning to ending balance, and the FX calculation. The entries derive from the schedule, and the schedule ties to source statements, which is what makes the pair re-performable at audit.

4. Route both entries for approval before posting

The approval matrix from the journal entries guide puts consolidation and elimination entries at high risk: they must tie to confirmed intercompany balances, and the preparer is never the approver. In multi-entity ERPs, approval may apply per subsidiary, so track both sides. An entry approved in one entity and pending in the other is not done.

5. Reconcile and eliminate

After posting, the intercompany reconciliation confirms the mirror balances agree, and elimination entries are prepared from the confirmed balances for consolidation. Entries that skip this sequence are how out-of-balance consolidations happen.

Multi-entity journal entries: the same problem, more of it

For the full picture of how these entries fit the wider group process, see the guide to intercompany transactions.

Multi-entity journal entries is the broader label for entries that must be booked across several sets of books, intercompany or not: a shared invoice allocated across four subsidiaries, payroll split by entity, a top-side adjustment pushed down. The mechanics and controls are the same as above, with one addition: the more entities an entry touches, the more valuable a single prepared source of truth becomes, because line-by-line adjustment across entities is where both errors and hours multiply.

What automating intercompany journal entries looks like

In an agent-prepared workflow, the intercompany task starts from a documented procedure, not a blank workbook. The agent reads the task’s source data (bank statement PDFs in each currency, the consolidated trial balance check, the GL account detail), presents its plan, and waits for approval. It then builds the supporting workbook: a tab per currency with every transaction recorded, the manual transfer schedule, a formula-driven rollforward with cross-references, and the FX settlement calculation. From that support it drafts the journal entries in the correct currencies, and routes them into the journal entry automation workflow, where they wait as proposed entries, balanced and rule-tagged with debit and credit totals tied, until a named reviewer approves them for posting. Exceptions stop the workflow and surface rather than posting silently; even a misconfigured validation rule gets flagged for a human before anything moves.

The accountant’s role is the review: check the rollforward, challenge the rate source, approve the entries. The currency conversion, the schedule assembly, and the double-sided drafting stop being human work.

Intercompany journal entries with Maxima

Maxima prepares intercompany entries with two engines: a deterministic engine that handles the rule-based bulk in seconds, and Max, an agentic engine that handles the judgment cases, reading bank statement PDFs and unstructured documents, resolving ambiguity, and asking a human when it is unsure. Max reads the task procedure, pulls source statements, builds the multi-currency workbook and rollforward, drafts the entries in each entity’s currency, and routes them for approval before posting natively to NetSuite, with a reasoning trail covering every step and every source referenced.

See how Maxima prepares multi-entity journal entries.

Frequently asked questions

What is an intercompany journal entry? An intercompany journal entry records a transaction between two entities in the same corporate group. It always exists as a pair: one entity records a receivable, income, or cash movement, and the counterparty records the mirror payable, expense, or inflow. The pair is eliminated at consolidation so the group does not report transactions with itself.

What are common examples of intercompany journal entries? Intercompany loans and cash transfers, management fees, shared-service and cost allocations, intercompany sales of goods or services, royalty charges, and cash pooling or zero-balance sweep activity. High-volume groups also generate intercompany entries from payroll allocations and centralized procurement.

How do intercompany journal entries work across currencies? The transaction is booked at the spot rate, and open foreign-currency balances are remeasured at the period-end rate under ASC 830, with differences recorded as FX gain or loss. Both sides remain correct in their own reporting currencies; the consolidation accounts for the translation difference. Documenting the rate, source, and date with the entry is what keeps the pair auditable.

Can intercompany journal entries be automated? Yes, and the preparation layer is the strongest candidate. An agent can pull source statements, build the multi-currency supporting schedules, draft both sides of each entry, and route them for approval before posting. The judgment stays human: approving the recording logic, reviewing the rollforward, and signing off on the entries.