NetSuite Intercompany Elimination: What OneWorld Handles and What Needs Custom Scripts
How NetSuite OneWorld handles intercompany eliminations at consolidation and where custom SuiteScript fills the gaps for complex multi-entity structures.
Multi-entity NetSuite account with intercompany elimination issues? SuitePacific works with OneWorld accounts to fix what the native consolidation misses.
Quick answer
NetSuite OneWorld native intercompany elimination is the automated process by which OneWorld removes intercompany balances, such as receivables, payables, revenue, and expense transactions between subsidiaries, during the consolidated financial statement run. Custom SuiteScript additions are scripts and Suitelets built on top of OneWorld to handle what the native module cannot: detecting intercompany mismatches before close, automating accrual journal entries for intercompany loans, allocating shared services costs through management fee scripts, and surfacing a reconciliation dashboard showing every intercompany pair and whether it balances. OneWorld handles standard wholly-owned subsidiary eliminations well. It does not detect mismatches before the period locks, does not accrue intercompany interest automatically, and does not provide a reconciliation view by subsidiary pair. SuitePacific audits multi-entity accounts, identifies the gaps in the native elimination process, and builds the scripts that fill them. Plans start at $799 per month.
What does OneWorld handle natively for intercompany?
OneWorld automates the most common intercompany scenarios for straightforward multi-entity structures. For standard wholly-owned subsidiaries with clean transaction matching, the native automation is sufficient.
Automatic intercompany journal entries
OneWorld generates intercompany JEs automatically when transactions are posted between subsidiaries, such as an AP bill in one subsidiary that creates the intercompany payable in another.
Consolidation elimination
During the consolidated financial statement run, OneWorld eliminates intercompany balances: intercompany receivables against payables, intercompany revenue against expenses, and intercompany loans.
Currency translation
Translates subsidiary financials from local currency to the parent currency using the correct exchange rate method: current rate for assets and liabilities, historical rate for equity, average rate for P&L.
Works well for standard structures
Standard intercompany transactions between wholly-owned subsidiaries, straightforward structures where one subsidiary sells to another at cost or fixed markup, and standard loan structures between parent and subsidiaries.
Where does native OneWorld fall short for intercompany?
The native automation breaks down when ownership is complex, when subsidiaries post mismatched entries, or when the structure includes intercompany loans with interest and management fee allocations.
Complex ownership structures
Partial ownership such as a 60/40 joint venture, minority interest calculations, and step-acquisition accounting require manual journal entries outside the native automation.
Intercompany balance mismatches
If one subsidiary posts an intercompany transaction and the other does not, the elimination will not balance. NetSuite does not automatically detect and flag these mismatches before close.
Intercompany loan interest
Accruing and eliminating intercompany interest requires custom scripts or manual journal entries every period. There is no native automated accrual for IC loan interest.
Non-standard elimination entries
Complex allocation methodologies such as management fees allocated by headcount or shared services charged by usage require custom logic to post and eliminate correctly.
Capability comparison: OneWorld native vs. with custom SuiteScript
| Capability | OneWorld Native | With Custom SuiteScript |
|---|---|---|
| Standard IC elimination | Yes | Not needed |
| Currency translation | Yes | Not needed |
| IC mismatch detection | No | Yes (scheduled script) |
| IC loan interest accrual | No | Yes (scheduled script) |
| Management fee allocation | No | Yes (allocation script) |
| Complex ownership handling | Manual only | Partial (scripts for accruals; equity method manual) |
| Reconciliation dashboard | No | Yes (Suitelet) |
| Audit trail per IC pair | Partial | Yes (drill-through) |
When is OneWorld native intercompany sufficient?
OneWorld native elimination is sufficient when all subsidiaries are wholly owned, when intercompany transactions are standard (sales between entities at cost or fixed markup, straightforward loans with no interest accrual requirement), and when the controller can verify balance matching manually each period without it becoming a significant time burden. For accounts with three to seven subsidiaries in straightforward structures, the native automation typically handles the consolidation without gaps.
When do custom SuiteScript additions become necessary?
Custom additions become necessary when there are more than 10 to 15 subsidiaries and manual mismatch verification before close is taking meaningful time; when the structure includes intercompany loans with interest that needs to accrue monthly; when management fees or shared services are allocated across entities based on a driver; or when the close checklist includes a manual step for verifying IC balance status that risks being skipped under time pressure.
Intercompany mismatch detector
A scheduled script runs before close and produces a report showing every intercompany balance pair that does not net to zero, along with the originating transactions for each mismatch.
Automated IC interest accrual
A monthly script calculates interest on outstanding intercompany loans and posts the accrual journal entry in both subsidiaries, eliminating manual calculation and entry each period.
Management fee allocation script
Allocates shared services costs across subsidiaries based on a configurable driver such as headcount, revenue, or square footage, and posts intercompany billing JEs automatically.
IC reconciliation Suitelet
A dashboard showing intercompany balance status by subsidiary pair, with drill-down to the originating transactions so the controller can verify status before locking the period.
How SuitePacific helps
SuitePacific audits multi-entity NetSuite accounts to identify intercompany gaps, then builds the scripts and dashboards needed to close cleanly. This includes IC mismatch detection scripts, automated accrual JEs for intercompany loans, and a Suitelet that shows the controller the status of every intercompany pair before the books close. Month-to-month from $799.
Related reading
- NetSuite OneWorld support covers the full scope of OneWorld administration and multi-entity configuration.
- NetSuite month-end close: manual vs. automated covers how SuiteScript automation reduces close time, including intercompany checks.
- NetSuite SuiteScript development covers the full scope of custom script and Suitelet builds for live accounts.
Frequently Asked Questions
What is intercompany elimination in NetSuite?
Intercompany elimination is the process of removing transactions between related subsidiaries from the consolidated financial statements, so intercompany revenue, expenses, receivables, and payables do not inflate the consolidated totals. In NetSuite OneWorld, the elimination runs automatically during the consolidated financial statement generation. The consolidated P&L removes intercompany revenue against intercompany cost, and the consolidated balance sheet removes intercompany receivables against intercompany payables.
Does OneWorld automatically eliminate intercompany balances?
Yes, for standard intercompany transactions between wholly-owned subsidiaries. OneWorld generates intercompany journal entries when transactions are posted between subsidiaries and performs the elimination during the consolidated financial statement run. The automation works well for standard structures. It does not handle partial ownership equity accounting, does not detect intercompany mismatches before close, and does not automatically accrue intercompany loan interest.
What happens if intercompany balances don't match?
If one subsidiary posts an intercompany transaction and the counterparty subsidiary does not post the matching entry, the intercompany balances will not net to zero and the elimination will leave a residual. NetSuite does not natively detect or flag these mismatches before the period is closed. A custom mismatch detection script solves this by running before close and identifying every IC pair where the balances do not net to zero.
How does NetSuite handle partial ownership or minority interest?
NetSuite OneWorld does not automate partial ownership accounting or minority interest calculations. For joint ventures with non-100% ownership, step acquisitions, or entities requiring equity method accounting, the controller must post manual journal entries to record the minority interest and adjust the consolidation. SuitePacific can assist with building the manual journal entry templates and close checklists for these structures.
Can SuiteScript detect intercompany mismatches before the close?
Yes. A scheduled script queries the intercompany balances by subsidiary pair, calculates the net position for each pair, and flags any pair where the net is not zero. The script can email the controller a summary of mismatched pairs with the originating transactions, or post the results to a close status Suitelet, before the period is locked.
How many subsidiaries can NetSuite OneWorld handle?
NetSuite OneWorld supports hundreds of subsidiaries technically, but practical complexity grows with the number of entities and intercompany relationships. For accounts with more than 20 to 30 subsidiaries and complex intercompany structures, the manual verification work before each close grows significantly unless automation is in place to detect mismatches and verify balance status across all pairs.
Ready to get the right approach in place? SuitePacific works with live NetSuite accounts month-to-month.