FrontierERP
Sign inTalk to Frontier
Applied guide

NetSuite intercompany eliminations: what breaks

What NetSuite OneWorld eliminates on its own, what still needs a manual journal, and why intercompany balances stop netting to zero across currencies.

Frontier · October 26, 2026

An applied guide for the controller who runs the close on NetSuite OneWorld.

The consolidated balance sheet is nearly done, and intercompany receivables and payables, which should be zero, are not. The amount is small enough to be annoying and large enough that somebody will ask about it.

NetSuite does eliminate intercompany activity on its own. It does it under specific conditions, for specific lines, at one moment in the close — and it leaves three kinds of work to you, plus a currency difference that nobody caused. Knowing which is which is most of the job.

The short answer.

  • Automatic. With Automated Intercompany Management enabled, NetSuite eliminates the intercompany lines marked for elimination: intercompany invoices and vendor bills, paired intercompany orders once they are billed, and advanced intercompany journal lines with Eliminate checked. It does this when someone runs Eliminate Intercompany Transactions from the Period Close Checklist. The entries post to the elimination subsidiary, and the A/R and A/P eliminations reverse automatically in the following period.
  • Not automatic. Lines NetSuite never knew were intercompany, a side that was never booked, and consolidation entries that are not intercompany activity at all — your investment in a subsidiary against its equity, non-controlling interest, and profit still sitting in inventory one subsidiary bought from another, unless the goods moved through NetSuite's arm's-length intercompany transfer flow, where Oracle says the elimination run revalues inventory and inventory costing balances.
  • Where it breaks across currencies. Each subsidiary books at its own rate and translates to the parent at its own consolidated rate. In the parent currency the two sides stop being equal, and the difference does not eliminate. Oracle's instruction for that amount is a manual journal entry. The same rate mechanics are one of five reasons a saved search or SuiteQL pull will not tie to the consolidated income statement; Why a saved search won't match NetSuite's P&L reconciles all five.

What NetSuite eliminates on its own.

Oracle's Intercompany Elimination Overview says the system "identifies transaction lines that require elimination" as you enter intercompany transactions and advanced intercompany journals, and its Multi-Subsidiary Vendor Support for Automated Intercompany Management page puts the mechanism in one sentence: NetSuite "automatically generates elimination journal entries based on the intercompany transaction lines and intercompany journal lines marked to be eliminated." Everything turns on the word marked. A line is marked in one of three ways.

  • By the account. An intercompany account carries the Eliminate Intercompany Transactions checkbox. An A/R or A/P account with it checked is used for intercompany transactions only, needs an intercompany customer or vendor, and cannot have the box cleared once transactions have posted to it.
  • By the transaction. The income, expense, A/R and A/P lines on intercompany invoices and vendor bills are marked automatically; there is no flag to set. Paired intercompany orders — a purchase order in one subsidiary linked to a sales order in the other — are non-posting, so they eliminate once they are billed.
  • By the journal. An advanced intercompany journal entry has an Eliminate column, defaulted from the account. It also forces the elimination lines to balance, which is the reason to use it.

None of this happens as you post. Elimination runs only from the Period Close Checklist — Setup > Accounting > Manage G/L > Manage Accounting Periods, then the period's Checklist icon — and only when someone clicks it. Oracle's instruction is to run it after all other period closing tasks: "Ensure that you have completed all other period closing tasks before you run elimination" (Running Intercompany Elimination). Oracle's pages differ on whether that makes it literally last: the Intercompany Elimination Overview calls it "the last task on the checklist", while the Period Close Checklist page lists Create Period End Journals and GL Audit Numbering after it when those features are on, and then Close. Read it as after the adjustments and revaluations, before the period closes. It can be run for a period as many times as needed, though never two runs at once, and the journals it creates belong to the elimination subsidiary — which is why you look there, not in the operating subsidiaries, to see what it did.

What it leaves to you.

Lines it was never told about. A regular journal entry used for intercompany activity is not checked: Oracle's wording is that regular journals "do not automatically balance lines to be eliminated." An intercompany charge posted that way, or to an expense account without the flag, sits in one subsidiary's books with nothing to eliminate it. Book-specific journals that touch A/R or A/P cannot be eliminated at all.

The side that was never booked. Elimination removes what is on both sides. It does not invent the missing half. An invoice raised on 30 October and a bill entered on 2 November are two correct entries in two different periods, and October's elimination sees one of them.

Consolidation entries that are not intercompany activity. Oracle's elimination documentation is about intercompany transaction and journal lines. It does not describe eliminating the parent's investment in a subsidiary against that subsidiary's equity, or recognising non-controlling interest in a subsidiary you do not wholly own, and the elimination run does not post them. For the margin on inventory one subsidiary sold another and has not yet sold outside the group, it describes an inventory revaluation by the run only for goods moved through the arm's-length intercompany transfer flow; for anything else, that entry is yours. Plan them as your own consolidation journals, every period, with their working kept — or, if a customisation or add-on posts them, confirm it ran. Intercompany eliminations: a worked example carries the investment, inventory-profit and dividend entries through a consolidation worksheet that foots.

Where it breaks across currencies.

This is the case worth working through, because nobody in it made a mistake.

A US parent owns Maple, which keeps its books in Canadian dollars, and Rhine, which keeps its books in euros. Maple invoices Rhine CAD 10,000 for shared services. Rhine enters the bill in Canadian dollars, so in its own books it holds a foreign-currency payable, recorded at the day's rate of 0.68: EUR 6,800.

At month-end, Revalue Open Foreign Currency Balances revalues Rhine's open payable at 0.66, to EUR 6,600, and books a EUR 200 unrealized gain. Maple's receivable is in Maple's own currency, so nothing on its side moves. Then Calculate Consolidated Exchange Rates sets the rates each subsidiary translates at — the current rate for balance-sheet accounts, the average rate for the income statement.

Line Local amount Translated at USD
Maple: intercompany A/R CAD 10,000 current, CAD→USD 0.7300 7,300
Rhine: intercompany A/P, revalued EUR 6,600 current, EUR→USD 1.1000 7,260
A/R less A/P 40
Maple: intercompany revenue CAD 10,000 average, CAD→USD 0.7350 7,350
Rhine: intercompany expense EUR 6,800 average, EUR→USD 1.0900 7,412
Revenue less expense −62

Illustrative rates, chosen to show the mechanism.

Every entry is right at the rate it used. The balance-sheet difference exists because Rhine's payable was revalued at 0.66, while the two consolidated rates imply 0.7300 ÷ 1.1000 ≈ 0.6636. The income-statement difference exists because Oracle defines the average rate as a weighted average over the transactions posted in the period, so each subsidiary's average follows its own activity — and neither is the 0.68 the bill was booked at.

These are two differences, not one, and they land in different places: USD 40 more receivable than payable on the balance sheet, USD 62 more expense than revenue on the income statement. With six subsidiaries the same arithmetic runs once for every pair that trades, which is why the reconciliation is done by pair: lay the subsidiaries down and across a grid, put each pair's net intercompany balance in US dollars in its cell, and the cells that are not zero are the work. A pair like Maple and Rhine, where neither side keeps its books in dollars, is the one to expect a difference from.

Rhine's EUR 200 gain is a third number, and the one to leave alone. It sits in an unrealized gain account, not an intercompany one, so elimination does not touch it: about USD 218 at Rhine's average rate, it stays in consolidated income as a foreign-exchange gain, unless your policy treats the balance as long-term funding of the subsidiary.

Finding the difference, and booking it.

Oracle is specific about the mechanics. The gains and losses that revaluation and the consolidated rates determine post to the Cumulative Translation Adjustment - Elimination account (CTA-E), which NetSuite creates the first time a qualifying transaction needs it. For whatever is still left — a currency delta, a difference that exists only because of exchange rates — the instruction is: "If there is an amount not eliminated due to a currency delta, make a manual journal entry to eliminate the amount."

NetSuite may already have posted part of a difference to CTA-E during the run. So the test afterwards is not the elimination journal; it is what is still sitting in the intercompany accounts, pair by pair, in US dollars. That amount, and only that amount, is yours to journal.

  • Prove it is a currency delta first. In transaction currency the pair should net to exactly zero: CAD 10,000 receivable against CAD 10,000 payable. If it does not, a side is missing or wrong, and that is a booking fix, not a journal.

  • Then journal it where the eliminations sit, in the elimination subsidiary, against CTA-E — the account Oracle names for currency effects in elimination — unless your policy names another. If the example's differences were still there after the run, the entry would be:

    Account Debit (USD) Credit (USD)
    Cumulative Translation Adjustment - Elimination 102
    Intercompany A/R 40
    Intercompany expense 62

    Both lines clear a translation difference, so both offset the same account; the 102 is only the sum of two entries, not a number to explain.

  • Write the policy down once — the account; whether the journal reverses next period, as NetSuite's own A/R and A/P eliminations do; and the amount below which you clear a delta without investigating it — and apply it every month. Your auditors will ask for it.

You can make the delta smaller. You cannot make it zero.

  • Denominate both sides in one currency. RSM names not denominating a single currency for an intercompany transaction as one of the most common causes of intercompany reconciliation issues — an invoice in one currency and its bill in another, each revalued against its own rate. The example above already follows the rule, with the pair in Canadian dollars, and still leaves a difference: one currency stops the two sides being revalued differently, not the side holding a foreign currency being revalued, and not translation. Pick one rule — the seller's currency, say — and apply it to every pair.
  • Settle intercompany balances on a schedule. A settled balance stops being revalued, which removes the balance-sheet half of the example; translating revenue and expense remains. Oracle's documentation limits intercompany netting to matched, linked transactions with the same amount on both sides — one more reason to pair them.
  • Take revaluation rates and consolidated rates from one source on one date. The balance-sheet difference above is the gap between the two.

A close order that keeps eliminations clean.

  1. Both sides booked, in the same period. Pair the transactions, or use an advanced intercompany journal entry rather than a regular one.
  2. Every intercompany account flagged. Intercompany customers and vendors on the A/R and A/P.
  3. Revalue Open Foreign Currency Balances.
  4. Calculate Consolidated Exchange Rates.
  5. Reconcile by subsidiary pair in the parent currency. Know the difference, and what it is made of, before elimination runs rather than after.
  6. Eliminate Intercompany Transactions. After every task above it on the checklist, as Oracle asks, and before the period is closed.
  7. Post what remains. The manual journal for the currency delta, then your own consolidation journals for investment and equity, non-controlling interest, and profit in inventory that the run did not revalue — Oracle's arm's-length transfer page has the run revalue inventory and costing balances for goods moved through that flow; confirm the margin is gone after the run, and anything else is your entry.

Step five is the one most closes skip, because it is the slow one: pull each subsidiary's intercompany accounts, translate them, line the pairs up, and find which lines make up whatever is left. And once the close is done, the first thing usually pulled from it is the board pack — what to automate there, and what to review.

The question to ask before the run.

Step five is a question, and Frontier answers it in plain language. It works from a panel inside your NetSuite and reads it through one integration role that you create and can revoke at any time: web-services only, view-level record permissions. Every answer carries the query and the rows behind it, so your team can check any figure against the ledger.

Its trial balance runs for one subsidiary at a time, so each side of a pair is one question; it is one of a small set of statements checked against a real NetSuite instance before they shipped, and it is held to one accounting book, so a multi-book account is not counted twice. The pair-by-pair question itself is answered with a query the agent writes for you. That query has not been checked in advance, which is why it comes back with the figure: read it, and the rows, before you post anything on the strength of them. Asking the ledger lists what is checked in advance and what is written per question.

Frontier does not run the elimination or post the journal. It answers the question that tells you which journal to post, and then you post it.

What to check before relying on any of this.

The behaviour described here is Oracle's documentation for NetSuite OneWorld. What your account actually does depends on which features are on — Automated Intercompany Management, Multi-Book Accounting — how its elimination subsidiaries are set up, and any customisation or SuiteApp that touches intercompany transactions. The currency example uses illustrative rates, and where a residual is booked is your policy and your auditors' call. Test a change to your elimination set-up in a sandbox before a real close depends on it, and treat any figure Frontier returns the way the documentation says to: check it before it affects your books.

Questions this raises

Does NetSuite eliminate intercompany transactions automatically?
Yes, with conditions. With Automated Intercompany Management enabled, an elimination subsidiary in place and the intercompany accounts flagged Eliminate Intercompany Transactions, NetSuite eliminates the lines marked for elimination when someone runs Eliminate Intercompany Transactions from the Period Close Checklist. It does not run on its own, and it only eliminates lines it knows are intercompany.
Why don't my intercompany balances net to zero after elimination?
Usually one of three things. One side was never booked, or was booked in a different period. A line went in through a regular journal entry or to an account without the elimination flag. Or the two sides were translated to the parent currency at rates that do not agree. The first two are booking fixes. The third is a currency delta, and Oracle's instruction for an amount left by one is a manual journal entry.
Where does the foreign-exchange difference from eliminations post?
Oracle's documentation says the gains and losses determined by Revalue Open Foreign Currency Balances and Calculate Consolidated Exchange Rates post to the Cumulative Translation Adjustment - Elimination (CTA-E) account, which NetSuite creates the first time a qualifying transaction needs it. An amount still in the intercompany accounts after the run because of a currency delta needs a manual journal entry — in the elimination subsidiary, against CTA-E unless your policy names another account.
Can I run intercompany elimination more than once for a period?
Yes. NetSuite lets you run it for a period as many times as you need, but not two runs at the same time. Oracle's guidance is to run it after every other close task, so a rerun belongs after a late correction rather than in place of finishing the close.

← All notes

Push the Frontier

Work alongside our team to establish your first operational capabilities, built around the problems that matter most to your business.

Explore the platformTalk to Frontier
FrontierERP

Set a new standard for how businesses operate.

Platform
Solutions
Resources
Company
© 2026 Frontier ERP, Inc.PrivacyTerms