Disclosure: NetSuiteForge may earn a commission through affiliate links in this article. We only recommend solutions we've personally implemented for ecommerce clients. Our editorial process is independent, and our recommendations are based on hands-on experience.

NetSuite Intercompany Transactions for Multi-Entity Ecommerce

When your ecommerce brand grows beyond a single legal entity, everything gets more complicated. Maybe you've incorporated a separate entity in the EU to handle VAT, or you've set up a holding company structure to separate intellectual property from operations, or you've acquired another brand that needs to share warehouse resources. Whatever the reason, the moment you have two or more legal entities transacting with each other, you need intercompany accounting in NetSuite.

I've implemented multi-entity NetSuite configurations for ecommerce brands operating across 2-7 subsidiaries, and the intercompany setup is consistently the most complex and error-prone part of the project. Done right, it automates the elimination of internal transactions and produces clean consolidated financials. Done wrong, it creates a reconciliation nightmare that takes days to unwind every month.

This guide covers everything you need to know about intercompany transactions in NetSuite for multi-entity ecommerce operations—from initial setup through transfer pricing, cross-subsidiary billing, and consolidated reporting.

Key Takeaways

• Intercompany transactions in NetSuite automatically generate paired entries across both entities, maintaining balanced books on both sides
• The OneWorld module is required for multi-entity NetSuite—it adds subsidiary management, intercompany elimination, and consolidated reporting
• Transfer pricing must be documented and defensible for tax compliance, especially for cross-border entities
• Intercompany elimination journal entries are automated through NetSuite's consolidation engine, removing internal revenue and expenses from consolidated financials
• The most common ecommerce multi-entity structure is a US selling entity + international fulfillment entity, requiring intercompany purchase orders and transfer pricing

What Is NetSuite OneWorld and Why Do You Need It?

NetSuite OneWorld is the module that enables multi-subsidiary management. Without OneWorld, your NetSuite instance supports a single legal entity. With OneWorld, you can manage unlimited subsidiaries, each with its own:

• Chart of accounts (or shared)
• Currency
• Tax jurisdiction
• Fiscal calendar
• Bank accounts
• Employees and vendors

When Ecommerce Brands Need OneWorld

You need OneWorld if any of these apply:

• International expansion: Selling and/or fulfilling in multiple countries requires local entities for tax, VAT, and regulatory compliance
• Brand portfolio: You own multiple ecommerce brands under a parent company
• IP separation: Your intellectual property (brand, technology) is held in a separate entity from your operating company
• Acquisition integration: You've acquired another ecommerce brand and need to consolidate financials
• Operational separation: Your warehouse/3PL operations are a separate entity from your selling operations

OneWorld Pricing

OneWorld adds approximately $999-2,000/month to your NetSuite license, depending on the number of subsidiaries. For a brand with 2-3 subsidiaries, it's typically $999/month. The cost scales with subsidiary count and transaction volume.

Cost-benefit consideration: The alternative to OneWorld is maintaining separate NetSuite instances (or separate accounting systems) for each entity and manually consolidating. This is cheaper in software costs but dramatically more expensive in labor—a full-time accountant spending 2 days per month on manual consolidation costs more than OneWorld.

Subsidiary Structure for Ecommerce

Common multi-entity structures I've implemented for ecommerce:

Structure 1: US + International

Parent Company (Holding)
├── US Operating Entity (sells on Shopify/Amazon US)
└── EU Entity (sells on Amazon EU, handles VAT)

Structure 2: Brand Portfolio

Parent Company
├── Brand A (supplements)
├── Brand B (beauty)
└── Brand C (fitness equipment)

Structure 3: IP + Operations

Parent Company
├── IP Holding Entity (owns trademarks, licenses to ops)
├── US Operations (sells, fulfills, manages inventory)
└── International Operations (local selling entities)

Structure 4: Post-Acquisition

Acquiring Company
├── Original Brand (existing ecommerce operations)
└── Acquired Brand (new entity, being integrated)

How Do Intercompany Transactions Work in NetSuite?

An intercompany transaction is any transaction between two subsidiaries within your OneWorld account. NetSuite handles these with paired transactions—when you create a transaction in one subsidiary, NetSuite automatically creates the mirror transaction in the other subsidiary.

Types of Intercompany Transactions

Intercompany Purchase Order / Sales Order

• Entity A creates a PO to Entity B
• NetSuite auto-creates a corresponding SO in Entity B
• Used for: inventory transfers between entities, cross-subsidiary fulfillment

Intercompany Journal Entry

• A journal entry that affects accounts in two or more subsidiaries
• Used for: cost allocations, shared expense distribution, transfer pricing adjustments

Intercompany Invoice / Vendor Bill

• Entity A invoices Entity B for services rendered
• Entity B receives the invoice as a vendor bill
• Used for: management fees, IP licensing fees, shared services charges

Intercompany Time Entry

• Employees in one entity charge time to projects in another entity
• Used for: shared teams working across brands

The Automatic Pairing Mechanism

When you create an intercompany transaction in Entity A that involves Entity B:

1. NetSuite creates the primary transaction in Entity A
2. NetSuite automatically creates the paired transaction in Entity B
3. Both transactions reference each other via the "Intercompany" fields
4. The intercompany receivable/payable accounts are automatically debited/credited

Example: Entity A (US) buys inventory from Entity B (China sourcing entity)

In Entity A's books:

• Debit: Inventory (asset)
• Credit: Intercompany Payable to Entity B

In Entity B's books:

• Debit: Intercompany Receivable from Entity A
• Credit: Revenue (or COGS, depending on transfer pricing method)

Setting Up Intercompany Accounts

Create these accounts in your chart of accounts:

Account	Type	Purpose
Intercompany Receivable	Accounts Receivable	Money owed to this entity by other entities
Intercompany Payable	Accounts Payable	Money this entity owes to other entities
Intercompany Revenue	Revenue	Revenue from selling to sister entities
Intercompany COGS	COGS	Cost of goods sold to sister entities
Intercompany Expense	Expense	Charges from sister entities for services
Elimination Account	Equity	Used during consolidation to eliminate IC balances

Configuration: Navigate to Setup → Accounting → Chart of Accounts. Create each account and mark it as an "Intercompany" account type. NetSuite uses these specifically tagged accounts when generating paired transactions.

How Do You Handle Transfer Pricing for Ecommerce?

Transfer pricing is the price one entity charges another entity for goods or services. It matters enormously for tax purposes—if your US entity buys inventory from your China sourcing entity at too low a price, the IRS will argue you're shifting profits offshore. If you charge too high a price, you're overpaying taxes in the US.

Transfer Pricing Methods

The IRS (and most international tax authorities) accept these transfer pricing methods:

Comparable Uncontrolled Price (CUP)

• Use the same price you'd charge an unrelated third party
• Most straightforward but requires comparable transactions to exist

Cost Plus

• Start with the cost incurred by the selling entity, add a markup
• Common for manufacturing/sourcing entities
• Example: China entity's cost is $5/unit, applies 15% markup, sells to US entity at $5.75/unit

Resale Price

• Start with the resale price (what the US entity sells to customers), subtract a margin
• Common for distribution entities
• Example: US entity sells at $25/unit, subtracts 35% margin, buys from sister entity at $16.25/unit

Transactional Net Margin Method (TNMM)

• Compare the net profit margin of the intercompany transaction to comparable independent transactions
• Used when simpler methods don't apply

Implementing Transfer Pricing in NetSuite

1. Document your transfer pricing policy: Create a formal document (usually with tax advisor assistance) that specifies the method and rationale for each intercompany transaction type
2. Configure item pricing: On each intercompany item, set the transfer price using a price level specific to intercompany transactions
3. Automate price updates: If your transfer pricing is cost-plus, create a scheduled script that recalculates transfer prices when costs change
4. Create audit trail: Every intercompany price should be traceable to the transfer pricing policy and underlying cost/price data

Transfer Pricing for Ecommerce-Specific Scenarios

Scenario 1: US entity sells, EU entity fulfills The EU entity fulfills orders for EU customers and charges the US entity for fulfillment services. Transfer price = EU entity's warehousing + shipping cost + 10% markup.

Scenario 2: Parent entity licenses brand to operating entities The IP holding entity charges a royalty fee (typically 3-8% of revenue) to each operating entity for using the brand name, trademarks, and technology.

Scenario 3: Shared services (accounting, marketing, technology) A shared services entity provides accounting, marketing, and technology services to all brands. Charges are allocated based on revenue share, headcount, or actual usage.

Important: Transfer pricing documentation is a tax compliance requirement, not optional. The IRS can impose penalties of 20-40% of underpayment if your transfer pricing is not properly documented. Budget $5,000-15,000 for a transfer pricing study from a qualified tax advisor.

How Do Intercompany Eliminations Work in Consolidation?

When you produce consolidated financial statements, intercompany transactions must be eliminated. Otherwise, internal transactions inflate your revenue and expenses.

What Gets Eliminated

• Intercompany revenue and COGS: Entity A's revenue from selling to Entity B is eliminated because it's not revenue from an external customer
• Intercompany receivables and payables: Entity A's receivable from Entity B nets to zero against Entity B's payable to Entity A
• Intercompany dividends and investments: Equity transactions between parent and subsidiaries

Example Elimination

Before elimination (individual entity financials):

	US Entity	EU Entity	Simple Sum
External Revenue	$1,000,000	$500,000	$1,500,000
Intercompany Revenue	$200,000	$0	$200,000
Total Revenue	$1,200,000	$500,000	$1,700,000
COGS	($600,000)	($350,000)	($950,000)
Intercompany COGS	$0	($200,000)	($200,000)
Gross Profit	$600,000	($50,000)	$550,000

After elimination (consolidated):

	Consolidated
External Revenue	$1,500,000
Intercompany Revenue	$0 (eliminated)
Total Revenue	$1,500,000
COGS	($950,000)
Intercompany COGS	$0 (eliminated)
Gross Profit	$550,000

The $200,000 in intercompany revenue and the $200,000 in intercompany COGS cancel out, leaving only external transactions.

Automating Eliminations in NetSuite

NetSuite's consolidation engine handles eliminations automatically:

1. Navigate to Reports → Financial → Consolidated Financial Statements
2. Select the parent subsidiary
3. Choose "Include eliminations"
4. NetSuite generates elimination journal entries that remove intercompany balances

Configuration requirements:

• Intercompany accounts must be properly tagged
• Subsidiaries must be in a parent-child hierarchy
• Intercompany transactions must use the designated IC accounts
• Currency conversion rates must be current (for multi-currency entities)

Manual Elimination Adjustments

Sometimes NetSuite's automatic eliminations don't catch everything:

• Timing differences: Entity A records an intercompany transaction on March 31, but Entity B doesn't record their side until April 1. The March consolidation shows an imbalance.
• Unrealized intercompany profit on inventory: If Entity A sells inventory to Entity B at a markup, and Entity B hasn't sold it to an external customer yet, the profit is "unrealized" and should be eliminated from consolidated COGS.
• Intercompany loan interest: Interest charged between entities needs elimination at the consolidated level.

Create manual elimination journal entries for these items as part of your monthly close process.

What Are Common Ecommerce Multi-Entity Scenarios?

Scenario 1: US Sells, EU Fulfills

A US-based ecommerce brand expands to Europe. They create an EU entity to handle VAT registration, local fulfillment, and EU customer service.

Transaction flow:

1. Customer in Germany orders from the website
2. Order is routed to the EU entity for fulfillment
3. EU entity ships the order and charges EU VAT
4. EU entity invoices the US entity for fulfillment services (intercompany)
5. US entity recognizes the revenue (or the EU entity, depending on the sales structure)

NetSuite configuration:

• Sales orders for EU customers are created in the EU subsidiary
• The EU subsidiary maintains its own inventory (received via intercompany PO from the US entity)
• Revenue is recognized in the EU subsidiary (because the EU entity is the seller for VAT purposes)
• The US entity earns a management fee from the EU entity

Scenario 2: Multi-Brand Portfolio

A parent company owns three ecommerce brands. Each brand is a separate subsidiary for legal and financial tracking, but they share warehouse space and operational resources.

Shared resource allocation:

• Warehouse costs allocated by cubic footage used per brand
• Shared marketing team costs allocated by revenue share
• Technology costs allocated equally or by usage

NetSuite configuration:

• Each brand has its own subsidiary with its own P&L
• Intercompany journal entries allocate shared costs monthly
• Consolidated reporting shows portfolio-level performance
• Brand-level profitability is tracked independently

Scenario 3: Post-Acquisition Integration

You acquire another ecommerce brand and need to integrate it into your NetSuite instance.

Integration steps:

1. Add the acquired brand as a new subsidiary in OneWorld
2. Migrate the acquired brand's historical data (chart of accounts mapping)
3. Set up intercompany accounts between the existing and acquired entities
4. Configure shared resource allocation
5. Establish transfer pricing for any intercompany services

Timeline: A post-acquisition NetSuite integration typically takes 3-6 months, depending on the complexity of the acquired business and the quality of their existing financial data.

Scenario 4: Amazon International Entities

Selling on Amazon's international marketplaces often requires local entities for VAT compliance, inventory ownership, and marketplace registration.

Structure:

US Parent
├── US Entity (Amazon.com)
├── UK Entity (Amazon.co.uk)
├── DE Entity (Amazon.de)
└── JP Entity (Amazon.co.jp)

Each entity:

• Owns inventory in the local Amazon FBA warehouse
• Registers for local VAT/tax
• Receives settlements from the local Amazon marketplace
• Reports to the US parent via intercompany transactions

Intercompany flow: US entity sells inventory to each international entity at transfer pricing. International entities sell to local customers and remit profits to the US parent via intercompany dividends (annual) or management fees (monthly).

How Do You Handle Multi-Currency Consolidation?

When your subsidiaries operate in different currencies, consolidation requires currency translation.

Currency Translation Methods

Current Rate Method (most common for ecommerce):

• Balance sheet items: Translate at the exchange rate on the balance sheet date
• Income statement items: Translate at the average exchange rate for the period
• Equity items: Translate at the historical exchange rate

Temporal Method:

• Monetary assets/liabilities: Current rate
• Non-monetary assets/liabilities: Historical rate
• Income items: Rate when recognized

NetSuite Currency Configuration

1. Navigate to Setup → Accounting → Currencies and add all currencies used by your subsidiaries
2. Set up exchange rate feeds: NetSuite can automatically import daily exchange rates from major providers
3. Configure the consolidation exchange rate type for each scenario (current, average, or historical)
4. Run the consolidation and review the Cumulative Translation Adjustment (CTA) account for reasonableness

Currency Gain/Loss on Intercompany Balances

When the US entity has a $100,000 receivable from the EU entity denominated in EUR, exchange rate changes create gains or losses:

• At creation: $100,000 USD = EUR 92,000
• At month-end: EUR 92,000 = $101,500 USD (euro strengthened)
• Unrealized gain: $1,500

Record these as unrealized currency gains/losses on the balance sheet. When the intercompany balance is settled, the gain/loss becomes realized and moves to the income statement.

Frequently Asked Questions

How much does NetSuite OneWorld cost?

OneWorld adds approximately $999-2,000/month to your base NetSuite license. The exact cost depends on the number of subsidiaries and your negotiated contract terms. Implementation of multi-entity configurations adds $25,000-75,000 in professional services, depending on complexity.

Can I add a subsidiary later without OneWorld from the start?

Technically yes, but it's expensive and disruptive. Upgrading a single-entity NetSuite to OneWorld requires data migration, chart of accounts restructuring, and reconfiguration of existing transactions. If there's any chance you'll need multiple entities within 2-3 years, get OneWorld from the start.

How do I handle intercompany inventory transfers?

Create an intercompany purchase order in the receiving entity from the sending entity. When the sending entity fulfills the order (intercompany item fulfillment), inventory moves from Entity A's location to Entity B's location. The transfer price determines the cost basis for the receiving entity.

Do I need separate Amazon Seller accounts for each subsidiary?

Not necessarily for domestic operations, but yes for international. Each international marketplace (Amazon.co.uk, Amazon.de, etc.) requires a separate seller account, which typically maps to a separate legal entity for tax purposes. Within the US, a single seller account can work even with multiple subsidiaries.

How do I handle shared employees across subsidiaries?

An employee can belong to one primary subsidiary but charge time or expenses to other subsidiaries. Use intercompany time entries and expense allocation workflows to distribute costs. For tax and HR purposes, the employee remains on the primary subsidiary's payroll.

What's the biggest mistake in multi-entity NetSuite implementations?

Not getting transfer pricing documentation done before going live. Brands set up intercompany transactions with arbitrary pricing, then scramble to justify the prices when their tax advisor or auditor asks. Engage a transfer pricing specialist during the implementation, not after.

Ready to Structure Your Multi-Entity Operations?

Multi-entity ecommerce operations unlock international markets, brand portfolio management, and tax-efficient structures—but only when the intercompany accounting is properly configured. NetSuite OneWorld provides the foundation, but the details of transfer pricing, elimination rules, and consolidation settings determine whether your month-end close is 3 days or 3 weeks.

Start with a clear entity structure diagram, engage a transfer pricing specialist early, and configure intercompany accounts correctly from day one. Retrofitting multi-entity accounting is far more expensive than building it right the first time.

Take our free NetSuite readiness assessment → to evaluate your multi-entity structure and get a customized implementation plan for intercompany operations in NetSuite.