
NetSuite intercompany transactions: keeping related-entity accounting clean
When your business operates through multiple legal entities — subsidiaries in different countries, divisions structured as separate companies, or joint ventures — transactions between those entities create intercompany activity. Subsidiary A sells to Subsidiary B. The parent company charges management fees to its subsidiaries. One entity lends money to another.
TL;DR: NetSuite OneWorld handles intercompany transactions natively — intercompany sales orders and purchase orders, intercompany journal entries, and intercompany inventory transfers all create paired entries in both entities automatically. At consolidation, NetSuite eliminates intercompany revenue, expenses, receivables, and payables so the consolidated financial statements show only external activity. The key to clean intercompany accounting is disciplined use of NetSuite's intercompany transaction types rather than manual journal entries.
Types of intercompany transactions
Intercompany sales and purchases
Entity A sells goods or services to Entity B. In NetSuite, this creates:
- Intercompany sales order in Entity A (the seller) → Revenue and AR recorded
- Intercompany purchase order in Entity B (the buyer) → Expense/inventory and AP recorded
NetSuite creates both transactions from a single entry — you enter the intercompany sales order, and the corresponding purchase order in the buying entity is generated automatically.
The intercompany AR in Entity A and the intercompany AP in Entity B are contra accounts that offset at consolidation.
Intercompany journal entries
For non-transactional intercompany activity — management fees, cost allocations, loan advances and repayments:
- Create an intercompany journal entry that debits one subsidiary and credits another
- NetSuite ensures both sides balance
- Both entities see the entry in their own books
Common examples:
- Parent charges a monthly management fee to subsidiaries
- Shared services costs allocated across entities
- Cash advances between entities (loan receivable/payable)
- Tax sharing payments
Intercompany inventory transfers
Moving inventory between entity-owned warehouses:
- Transfer order from Entity A's warehouse to Entity B's warehouse
- Entity A records inventory reduction
- Entity B records inventory receipt
- If entities are in different countries, transfer pricing and customs duties may apply
Intercompany time charges
When employees of one entity work on projects belonging to another entity:
- Employee in Entity A logs time to Entity B's project
- Entity A bills Entity B for the labor (intercompany sales)
- Entity B records the cost against the project
Setting up intercompany in OneWorld
Prerequisites
- NetSuite OneWorld: Intercompany features require the OneWorld module for multi-subsidiary management
- Subsidiary hierarchy: Subsidiaries defined with proper parent-child relationships
- Intercompany GL accounts: Dedicated accounts for intercompany receivables and payables
Configuration
Intercompany accounts: Create GL accounts specifically for intercompany balances:
- Intercompany Receivable (by entity or pooled)
- Intercompany Payable (by entity or pooled)
- Intercompany Revenue
- Intercompany Cost of Goods Sold / Expense
These accounts are used exclusively for transactions between entities. This separation makes elimination straightforward.
Intercompany preferences: Setup > Accounting > Preferences > Intercompany Preferences:
- Enable intercompany auto-balancing
- Configure intercompany clearing accounts
- Set default intercompany accounts for each subsidiary pair
Intercompany pricing: For entities that trade goods or services, define transfer pricing:
- Market-based pricing (arm's length)
- Cost-plus pricing
- Resale minus pricing
- Predetermined fixed rates
Transfer pricing is critical for tax compliance — related-entity transactions must be at arm's length to satisfy tax authorities.
Elimination at consolidation
What gets eliminated
When preparing consolidated financial statements, intercompany activity must be eliminated so the consolidated entity only shows external transactions:
| Transaction | Entity A | Entity B | Elimination |
|---|---|---|---|
| IC Sale of $10,000 | Revenue: $10,000 | Expense: $10,000 | Revenue and expense eliminated |
| IC Receivable/Payable | AR: $10,000 | AP: $10,000 | AR and AP eliminated |
| IC Inventory (at markup) | Revenue: $12,000 (includes $2K markup) | Inventory: $12,000 | Eliminate markup from inventory |
| IC Dividend | Dividend income: $5,000 | Dividend paid: $5,000 | Both eliminated |
Automatic elimination in NetSuite
NetSuite can generate elimination entries automatically during the consolidation process:
- Identify intercompany balances: NetSuite identifies balances in designated intercompany accounts
- Generate elimination entries: Creates journal entries at the parent/consolidated level that offset intercompany amounts
- Verify zero net: After elimination, intercompany accounts should net to zero at the consolidated level
Configuration:
- Create elimination accounts at Lists > Accounting > Accounts > New (check "Eliminate Intercompany Transactions")
- Map which intercompany accounts eliminate against which via Intercompany Preferences
- Set the elimination subsidiary (usually the parent or a holding entity)
- Schedule elimination to run as part of the monthly close
Manual elimination adjustments
Some intercompany scenarios require manual elimination:
- Intercompany profit in inventory: If Entity A sold inventory to Entity B at a markup, and Entity B hasn't sold it to an external customer yet, the unrealized profit must be eliminated from consolidated inventory
- Intercompany fixed asset transfers: If one entity sells a fixed asset to another at a gain, the gain is eliminated and the asset is restated at original cost for consolidation
- Intercompany loans and interest: Long-term intercompany debt and related interest income/expense are eliminated
Reconciling intercompany accounts
Monthly reconciliation
At each month-end, intercompany receivable and payable accounts should balance across entities:
- Entity A's IC Receivable from Entity B = Entity B's IC Payable to Entity A
- Any mismatch indicates a transaction recorded in one entity but not the other
Common causes of mismatches:
- Timing differences (Entity A recorded the sale, Entity B hasn't recorded the purchase yet)
- Currency conversion differences (entities in different currencies)
- One-sided journal entries (someone posted to an IC account without the contra entry)
- Transaction corrections in one entity but not the other
Reconciliation process
- Run a saved search for intercompany account balances by subsidiary pair
- Compare each pair's receivable/payable — they should be equal and opposite
- Investigate and resolve differences
- Ensure resolution before running consolidation elimination
Tip: Run this reconciliation weekly, not monthly. Mismatches that compound over several weeks are harder to investigate.
Transfer pricing compliance
Tax authorities scrutinize intercompany transactions to ensure they're at arm's length — priced as if the entities were unrelated parties. Non-compliance results in:
- Transfer pricing adjustments (taxable income reallocated between entities)
- Penalties (20% of the adjustment under IRC 6662(e), increasing to 40% for gross valuation misstatements)
- Double taxation (one entity taxed, the other doesn't get a corresponding deduction)
Documentation in NetSuite
Maintain transfer pricing documentation within NetSuite:
- Pricing policies: Document the method for each type of intercompany transaction
- Benchmarking: Support arm's length pricing with comparable transaction analysis
- Transaction records: NetSuite's audit trail provides the transaction-level detail tax authorities require
- Reports: Generate intercompany transaction summaries by entity pair, transaction type, and period
Need help structuring compliant intercompany transactions?
We configure OneWorld intercompany workflows, elimination entries, and transfer pricing documentation for multi-subsidiary NetSuite environments.
Talk to our OneWorld teamBest practices
Always use intercompany transaction types. Don't record intercompany activity through regular sales orders or manual journal entries. Use the designated intercompany transaction types — they create both sides automatically and ensure proper elimination.
Reconcile intercompany weekly. Letting mismatches accumulate makes month-end close painful and consolidation unreliable.
Standardize transfer pricing methods. Each entity pair should have documented, consistent pricing for each type of transaction. Ad hoc pricing creates tax compliance risk.
Eliminate in real time, not at year-end. Run elimination entries monthly as part of the close process. Year-end-only elimination means your interim consolidated statements are wrong.
Separate intercompany accounts from external. Never mix intercompany and external transactions in the same GL account. Clean separation is the foundation of accurate elimination.
Frequently Asked Questions
Need help with your NetSuite project?
Whether it's integrations, customization, or support — let's talk about how we can help.

Gustavo Canete
Co-Founder & Development Director
Co-founder and Development Director at BrokenRubik overseeing technical excellence and development operations. 12+ years of experience leading NetSuite development teams and delivering complex enterprise solutions.
Get More Insights Like This
Join our newsletter for weekly tips, tutorials, and exclusive content delivered to your inbox.
Related Articles
NetSuite Accounting Services: Bookkeeping & Finance
Guide to NetSuite accounting services. Outsourced bookkeeping, managed accounting, month-end close, and how to find the right NetSuite accounting partner.
NetSuite AP Automation: Cut Manual Invoice Work
Automate NetSuite accounts payable with approval routing, three-way matching, and vendor bill workflows. Best AP add-ons compared.
NetSuite Advanced Financials: Features & Setup (2026)
NetSuite Advanced Financials guide. Statistical accounts, financial indicators, amortization, multi-book accounting, and when you need it.
Gustavo Canete