Insight for US Businesses | Logiframe US

Multi-Currency & Intercompany in NetSuite: Deep Setup

Written by Wienanto Tanuwidjaja | Aug 27, 2026, 11:58:45 AM

 

Table of Contents:

1. Beyond the Basics: Technical Setup That Most Businesses Get Wrong
2. Intercompany Transaction Recording: The Foundation
3. The Choice: Manual vs. Automated
4. Currency Revaluation: The Mechanics
5
. Currency Translation in Consolidation: The Complicated Part
6. Intercompany Elimination Rules: Setting Them Up Right
7. Common Configuration Mistakes
8. The Consolidation Checklist
9. Multi-Currency Challenges Specific to Intercompany
10. Reporting: Making Sense of the Complexity
11. How Logiframe Approaches Multi-Currency & Intercompany Setup
12. Frequently Asked Questions

Beyond the Basics: Technical Setup That Most Businesses Get Wrong

Posts #2 and #3 covered the architecture decisions around OneWorld subsidiaries and international expansion. This post goes deeper: the actual technical configuration that makes multi-currency and intercompany work correctly.

Most NetSuite implementations handle the basics—currency feeds sync, subsidiaries exist, bank accounts are separate. But the nuance is in the details:

  • How do you configure intercompany transactions so they eliminate correctly?

  • When a subsidiary pays another subsidiary in different currencies, how does that reconcile?

  • What happens to currency translation differences in consolidation?

  • How do you prevent intercompany balances from going unreconciled for months?

Get these details wrong and your close is fragile, your consolidation is manual, and auditors will flag issues.

Intercompany Transaction Recording: The Foundation

Let's start with a concrete scenario: Subsidiary A (US) provides services to Subsidiary B (Germany). SubA bills €50K for the work.

The question: How does this get recorded so that:

  1. SubA recognizes revenue

  2. SubB recognizes an expense

  3. When consolidated, the intercompany transaction eliminates

  4. There's an audit trail showing what happened

Intercompany Accounting (The Traditional Way)

SubA's bookkeeper records:

Debit: 1200 Intercompany AR – €50,000
Credit: 4000 Service Revenue – €50,000

SubB's bookkeeper records:

Debit: 5000 Consulting Expense – €50,000
Credit: 2100 Intercompany AP – €50,000

What happens:

  • SubA has €50K in AR

  • SubB has €50K in AP

  • When you consolidate, you eliminate account 1200 (IC AR) against account 2100 (IC AP)

  • The revenue and expense cancel out

Pros:

  • Clear visibility: you can see exactly which transactions were intercompany

  • Auditor-friendly: clean paper trail

  • Flexible: works for any type of intercompany transaction

Cons:

  • Requires discipline: both subsidiaries have to record it

  • Manual work: someone has to build the elimination entries

  • Error-prone: if one subsidiary records it and the other doesn't, balances don't match

Option 2: Automated Intercompany Accounting (NetSuite Native)

NetSuite has an "Intercompany Account" feature. You configure it once:

Step 1: Define intercompany account pairs
  Subsidiary A's IC AR account (1200) ↔ Subsidiary B's IC AP account (2100)

Step 2: Record the transaction
  SubA posts: Debit 1200 IC AR, Credit 4000 Revenue
  NetSuite automatically posts to SubB: Debit 5000 Expense, Credit 2100 IC AP

What happens:

  • One transaction creates entries in both subsidiaries automatically

  • Balances always match by definition

  • When you consolidate, eliminations are already set up

  • Minimal manual work

Pros:

  • Eliminates manual matching errors

  • Automatic and balanced

  • Reduces close time

Cons:

  • Requires upfront configuration

  • Less visibility into which transactions are intercompany (they're embedded in normal transactions)

  • Harder to troubleshoot if something goes wrong

The Choice: Manual vs. Automated 

Use manual intercompany accounting if:

  • You have a small number of intercompany transactions (< 20/month)

  • Your subsidiaries are far apart operationally (minimal interaction)

  • Your team prefers transparency and clear audit trails

  • You don't have someone dedicated to configuring NetSuite

Use automated intercompany if:

  • You have frequent intercompany transactions (> 20/month)

  • Your subsidiaries interact heavily (shared services, management charges, etc.)

  • You want to minimize close time

  • You have someone to configure it correctly upfront

Most mid-market businesses moving to OneWorld should consider automated. The upfront configuration work (1-2 weeks) saves 5+ hours every close.

Currency Revaluation: The Mechanics

Now let's layer in currency complexity. Subsidiary A (US) has an intercompany AR of €50K due from Subsidiary B (Germany). It's recorded on March 1 at EUR/USD = 1.10, so it's worth $55,000.

By March 31, EUR/USD = 1.15. The same €50K is now worth $57,500.

Question: Does your profit change?

The answer is: yes, but it depends on accounting standards and whether you want that change in operating income or elsewhere.

NetSuite's Currency Revaluation Features:

Feature 1: Automatic Monthly Revaluation

NetSuite can run a month-end process that:

  1. Identifies all open AR/AP balances in foreign currency

  2. Calculates what they're worth at month-end rates

  3. Posts a revaluation journal entry showing the change

Example:
€50K AR recorded at 1.10 = $55,000
€50K AR revalued at 1.15 = $57,500
Difference = $2,500 gain

NetSuite posts:
  Debit: 1200 IC AR – $2,500 (to increase balance to $57,500)
  Credit: 8000 FX Gain – $2,500

Feature 2: Separating Realized vs. Unrealized

You can configure where FX gains/losses land:

  • Unrealized FX (open items) → Goes to OCI (Other Comprehensive Income), doesn't hit P&L

  • Realized FX (closed items) → Goes to operating income

How NetSuite knows:

  • If the AR is still open (customer hasn't paid), it's unrealized

  • If it's been collected and converted to USD, it's realized

Feature 3: By-Currency Reporting

You can run reports showing:

  • Exposure by currency (total EUR exposure, GBP exposure, etc.)

  • YTD FX impact (how much did currency movements affect profit?)

  • Open AR/AP by currency and age

Intercompany Settlement: The Tricky Part

Here's where most businesses struggle. SubA is owed €50K from SubB. But instead of SubB paying SubA directly (which would involve a bank transfer and FX conversion), they settle it on the books.

Scenario 1: Direct Settlement (Easiest)

SubB pays SubA the €50K. That's straightforward—it's a normal payment, FX conversion happens at the bank, everyone's AR/AP goes to zero.

Scenario 2: Netting (NetSuite has features for this)

SubA owes SubB $30K for something else. SubB owes SubA €50K. Instead of two payments, they net: SubB pays SubA €50K minus the USD equivalent, and everything is settled.

NetSuite can handle this, but you need to:

  1. Identify cross-subsidiary payables/receivables

  2. Define a netting rule (which gets offset against which)

  3. Calculate the net amount considering FX rates

  4. Post one settlement entry that eliminates both

Scenario 3: Holding Balances (The Problem)

Some companies don't settle intercompany balances. SubA is owed €50K, SubB owes it, but it stays on the books indefinitely. This creates:

  • Bloated intercompany AR/AP accounts

  • Reconciliation headaches

  • Audit questions ("Why is this still open?")

NetSuite can help: Set up automatic reconciliation reports showing old intercompany items. Flag anything over 60 days old for settlement.

Currency Translation in Consolidation: The Complicated Part

Now you're consolidating. SubB's financial statements are in EUR. You need them in USD for the consolidated group P&L.

Step 1: Choose Translation vs. Remeasurement

Translation method (subsidiary is independent, operates in EUR):

Assets: €10M × 1.15 = $11.5M
Liabilities: €6M × 1.15 = $6.9M
Equity: €4M × 1.15 = $4.6M

Difference from last period: EUR/USD changed from 1.10 to 1.15 Last month's USD equity: €4M × 1.10 = $4.4M This month: €4M × 1.15 = $4.6M Currency Translation Adjustment: $0.2M

This CTA usually goes to OCI, not operating income. Why? Because it's not an operating gain/loss; it's a currency fluctuation.

Remeasurement method (subsidiary's functional currency is USD even though it operates in EUR):

Different accounts remeasure differently:

  • Balance sheet accounts (AR, AP, fixed assets) → current rate

  • Historical accounts (inventory, fixed assets) → historical rate

  • This creates complexity but is appropriate for certain business structures

Step 2: Configure NetSuite Consolidation Rules

In NetSuite, you define:

For Subsidiary B (Germany):
  Functional Currency: EUR (so use translation method)
  Reporting Currency: USD
  Translation Method: Current Rate Method
  
Consolidation will:
  Convert P&L at average exchange rate for the period
  Convert balance sheet at period-end rate
  Calculate and capture CTA in a separate OCI account

Step 3: Test It

Run a trial consolidation with sample data:

  • Does translated equity match last period equity adjusted for net income and CTA?

  • Does CTA make sense (positive or negative, matches currency movement direction)?

  • Do intercompany balances eliminate correctly after translation?

Most businesses skip testing. Don't. One error in translation setup creates monthly headaches.

Intercompany Elimination Rules: Setting Them Up Right

Once everything is translated, you eliminate intercompany balances. Here's how to configure it in NetSuite.

Rule 1: Eliminate Intercompany AR/AP

Rule Name: Eliminate IC Receivables and Payables

Define:
  Debit Account: 1200 (IC AR, all subsidiaries)
  Credit Account: 2100 (IC AP, all subsidiaries)
  
Conditions:
  Matching criteria: Amount + Invoice Number
  Allow partial matches: No
  
Action:
  Every consolidation, automatically eliminate matched pairs

When this works: IC AR in SubA matches exactly with IC AP in SubB.

When this breaks:

  • Amount matches but invoice numbers don't (data entry error)

  • IC AR in SubA for $100K, but IC AP in SubB for $105K (rounding or FX issue)

  • One subsidiary recorded it; the other didn't

Prevention: Reconcile intercompany accounts monthly (not just at consolidation). Flag mismatches immediately.

Rule 2: Eliminate Intercompany Sales/Purchases

Rule Name: Eliminate IC Sales and Purchases

Define:
  Debit Account: 5000 (Intercompany Purchases, SubB)
  Credit Account: 4000 (IC Revenue, SubA)
  
Amount: Auto-match based on invoice amount

The tricky part: If SubA sold inventory to SubB at a markup, and SubB hasn't sold it yet, that profit is unrealized and should be eliminated too.

Example:

  • SubA sells 100 units to SubB for $10K (cost was $8K, so $2K profit to SubA)

  • SubB records this as $10K inventory

  • At consolidation, if SubB still has this inventory, the $2K profit is unrealized and should be eliminated

This requires additional configuration:

Rule 3: Eliminate Unrealized Profit in Inventory

When:
  IC inventory is still on hand at period-end (not yet sold to external customers)
  
Do:
  Eliminate the internal profit by:
    Debit: 4000 IC Revenue (reverse the profit)
    Credit: 1500 Inventory (reduce to cost)

Common Configuration Mistakes

Mistake 1: Forgetting the CTA (Currency Translation Adjustment)

You translate the balance sheet but forget to capture the CTA. Now your consolidated balance sheet doesn't balance—assets don't equal liabilities + equity.

Fix: NetSuite has a specific "Currency Translation Adjustment" account type. Use it. Configure consolidation to automatically post CTAs.

Mistake 2: Mixing Realized and Unrealized FX

You have an open AR in EUR that's been revalued. Then the customer pays and you get a different FX rate at the bank. Now you have both unrealized loss (from revaluation) and realized gain (from payment). You forget to net them and report both.

Fix: Reconcile realized vs. unrealized FX monthly. Understand which account receives which.

Mistake 3: Intercompany Transaction Recorded in Wrong Period

SubA records the intercompany charge in March. SubB doesn't record it until April. Now March doesn't eliminate, April has weird numbers.

Fix: Require both subsidiaries to record intercompany transactions in the same period. Use a checklist or approval workflow to enforce this.

Mistake 4: No Intercompany Reconciliation Until Close

You let intercompany AR/AP accumulate all month. At close, you discover they don't reconcile. You spend 8 hours figuring out which transactions match.

Fix: Reconcile IC AR/AP weekly. It takes 30 minutes and catches errors immediately, not on close day.

The Consolidation Checklist

Before you run consolidation each month:

  • [ ] All subsidiaries have closed their books

  • [ ] Intercompany AR/AP reconciles (each SubA balance has corresponding SubB balance)

  • [ ] Currency revaluation has been run

  • [ ] Intercompany transactions recorded in both subsidiaries (no one-way entries)

  • [ ] Unrealized profit in inventory has been identified and reserved

  • [ ] Elimination rules tested with sample data (same test as last month + new activity)

  • [ ] Consolidated trial balance ties to subsidiary trial balances after eliminations

  • [ ] CTA is calculated correctly (matches change in FX rates)

  • [ ] P&L makes sense (consolidation revenue = sum of subsidiaries minus IC)

If you check all boxes, consolidation is mechanical. If you skip any, it's detective work.

Multi-Currency Challenges Specific to Intercompany

Challenge 1: Changing Exchange Rates Mid-Period

SubA records a €50K invoice to SubB on March 1 at 1.10 rate. On March 15, the rate moves to 1.15. On March 31, it's 1.20.

Question: Which rate do you use for monthly reporting? ASC 606 says the rate on the transaction date (1.10), but for consolidation purposes, you might revalue to 1.20.

NetSuite solution: Lock rates for each period. For March, all EUR transactions use the March month-end rate (1.20), regardless of transaction date. This keeps consolidation clean.

Challenge 2: Intercompany Settlement Timing Differences

SubA records payment on March 31. SubB doesn't record receipt until April 1. Intercompany balances don't reconcile for March.

NetSuite solution: Use an intercompany clearing account. Both record at the same time, even if cash hasn't moved. Then when cash actually settles, it's a separate entry.

March 31:
  SubA: Debit IC Clearing Account, Credit Cash
  SubB: Debit Cash, Credit IC Clearing Account
  
April 2 (when actual transfer clears):
  Both subsidiaries: Reconcile clearing account to zero

Challenge 3: Multi-Currency Intercompany

SubA (US) and SubC (Singapore) are interacting. SubA records in USD. SubC records in SGD. The intercompany transaction is in EUR (maybe they trade on EUR-based markets).

Question: How does this reconcile?

NetSuite approach: All intercompany transactions should be recorded at a standard rate (e.g., the rate from the date of the transaction). Then in consolidation, they eliminate at that rate. Separate FX gains/losses on the eventual payment are captured separately.

Reporting: Making Sense of the Complexity

Once this is all configured, you need reports that show:

Report 1: Intercompany Reconciliation

  • Shows AR in SubA vs AP in SubB

  • Highlights unmatched items

  • Shows aging (which balances are old?)

Report 2: Currency Exposure

  • Total EUR exposure by subsidiary

  • Total GBP, CAD, etc.

  • Open items vs. closed items (realized vs. unrealized)

Report 3: FX Impact

  • How much did FX movements affect the month's profit?

  • Broken down by currency

  • Separate realized from unrealized

Report 4: Consolidated P&L vs. Subtotals

  • Sum of all subsidiaries

  • Minus intercompany eliminations

  • Equals consolidated total

  • CTA shown separately

How Logiframe Approaches Multi-Currency & Intercompany Setup

We start by mapping your actual intercompany flows (what gets charged between subsidiaries, how often, in what currencies). Then we design the consolidation architecture to match that reality, not force it into a generic template.

Most setups take 4-6 weeks to configure, test, and stabilize. The upfront work (intercompany reconciliation, currency revaluation rules, elimination setup) determines whether your close is smooth or manual.

Frequently Asked Questions

Should we use automated or manual intercompany accounting?

Automated is better if you have > 20 intercompany transactions per month or if subsidiaries interact frequently. Manual is fine for light intercompany activity. Most businesses outgrow manual and migrate to automated after a year or two.

How do we handle intercompany transactions in different currencies?

Record them at a standard rate (usually the rate on the transaction date or period-end rate, consistently). Separate the FX gain/loss on eventual payment/settlement from the transaction itself. This keeps intercompany reconciliation clean.

When should intercompany AR/AP be reconciled?

Weekly is ideal; monthly minimum. Reconcile before consolidation, not during it. If you reconcile monthly for the first time at close, you'll find mismatches that take hours to untangle.

What's the difference between CTA and a normal FX gain or loss?

CTA (Currency Translation Adjustment) is the change in equity value purely from FX rate changes on foreign subsidiary net assets. It's not an operating gain or loss. FX gains/losses on actual transactions (paying vendors, collecting customers) are operating and usually hit P&L. They're separate and should be tracked separately.