NetSuite OneWorld is a multi-subsidiary module that lets you manage multiple legal entities—each with its own chart of accounts, bank accounts, and tax obligations—within a single NetSuite instance. Unlike Xero or QuickBooks (which require separate instances for each entity), OneWorld keeps all subsidiaries in one system with native consolidation, intercompany automation, and unified reporting. The architecture decision you make before go-li—how you structure subsidiaries, define intercompany accounting, and configure eliminations—directly shapes whether consolidation is automated or manual for the next five years. Most businesses get this wrong on the first try, which is why the setup phase is critical.
Table of Contents:
1. Why Multi-Entity Architecture Matters
2. The OneWorld Model: How It's Different From Separate Instances
3. The Critical Architecture Decisions
4. The Consolidation Rules: How Eliminations Actually Work
5. When OneWorld Makes Sense, and When It Doesn't
6. The Architecture Review: What to Do Before Go-Live
7. How Logiframe Approaches OneWorld Architecture
8. Frequently Asked Questions
When you're managing multiple legal entities—separate subsidiaries, business units across geographies, acquired companies, or holding companies—the way you structure them in NetSuite determines everything that comes after:
How fast your close happens. If intercompany transactions are configured correctly, eliminations run automatically. If not, someone's building them manually every month.
Whether reporting is accurate. If subsidiary chart of accounts are standardized, consolidation is clean. If they're not, you're reconciling mismatches perpetually.
How easy audit and compliance become. If subsidiary structure mirrors your legal and tax structure, compliance is straightforward. If it's a workaround, it's fragile.
Whether you can sell, divest, or restructure without rebuilding the system. If the architecture is rigid, every M&A activity requires reconfiguration.
Get this right on day one, and OneWorld becomes invisible—it just works. Get it wrong, and you're retrofitting for years.
You have three legal entities. You buy three separate Xero or QuickBooks instances. Each one is a silo—its own chart of accounts, its own bank feeds, its own reporting. Consolidation is manual: export trial balances, build eliminations in Excel, reconcile. Every close cycle involves this spreadsheet dance.
NetSuite OneWorld approach:
You have three legal entities. You buy one NetSuite instance with OneWorld enabled. Each entity is a "subsidiary" in OneWorld—separate books, separate P&L, separate tax treatment—but all within one system. Intercompany transactions are recorded in one place (not reconciled across systems). Eliminations run automatically based on rules you've configured. Consolidated reporting is a saved search away.
The key insight: One system of record, multiple legal entities.
This becomes increasingly valuable as you add complexity:
Intercompany transactions (subsidiary A selling to subsidiary B) are recorded once and automatically eliminated in consolidation.
Multi-currency transactions roll up with exchange rate handling built in.
Consolidated reporting gives you a group P&L instantly without exports or manual compilation.
Audit trail is unified—you can follow a transaction from origination through elimination across the entire group.
Before you configure OneWorld, you have to make several structural decisions. These can't easily be changed later without significant rework.
Decision 1: How Do You Define Subsidiaries?
A subsidiary in OneWorld is a legal entity. But the question is: do you model your structure as it is, or as you want to manage it?
Example 1: The real structure
You have:
Parent Company LLC (US holding company)
Subsidiary A Inc. (US operating company)
Subsidiary B GmbH (Germany operating company)
Subsidiary C Pte Ltd. (Singapore operating company)
OneWorld structure option A (mirrors legal structure):
Parent Company LLC (Corp)
├── Subsidiary A Inc. (subsidiary)
├── Subsidiary B GmbH (subsidiary)
└── Subsidiary C Pte Ltd. (subsidiary)
Pros:
Clear legal alignment
Easy for auditors and tax teams
Intercompany transactions between operating companies are clear
Cons:
The parent company is a separate P&L (might be just holding cash/debt)
You need to think about how intercompany loans, dividends, and management fees flow
OneWorld structure option B (consolidation-focused):
Consolidated Group (Corp)
├── Subsidiary A (subsidiary)
├── Subsidiary B (subsidiary)
└── Subsidiary C (subsidiary)
Pros:
Group P&L is the primary reporting entity
Subsidiary intercompany flows are automatic
Cons:
Parent company's own transactions (debt service, investments) might get lost in consolidation
Tax teams may prefer the clearer legal alignment of Option A
The right choice depends on:
How you're taxed (consolidated return vs separate filings)
Whether you have debt at the parent level that needs separate tracking
How your business units operate (independent profit centers vs integrated value chain)
Decision 2: Chart of Accounts Alignment
This is the biggest predictor of consolidation headaches.
Option A: Standardized Chart of Accounts
Every subsidiary uses the same chart of accounts structure (same account numbers, same naming conventions). Different subsidiaries might not use every account, but the numbering is consistent.
Example:
4000 – Sales (all subsidiaries use this)
4100 – Cost of Goods Sold (all subsidiaries)
5000 – Salaries & Wages (all subsidiaries)
Pros:
Consolidation is clean—eliminate account 4000 from SubA against account 4000 in SubB
Reporting is consistent
Reclassifications are minimal
Cons:
Requires discipline to maintain across multiple entities
Might not fit subsidiaries with different business models
Option B: Subsidiary-Specific Accounts
Each subsidiary has its own chart of accounts tailored to its business. SubA (retail) has different accounts than SubB (manufacturing).
Example:
SubA:
4000 – Retail Sales
4100 – Retail COGS
SubB:
4000 – Manufacturing Revenue
4100 – Manufacturing Materials Cost
Pros:
Flexibility for different business models
Natural fit for acquired companies
Cons:
Consolidation requires account mapping (which account in SubA maps to which in SubB?)
Every eliminating entry requires judgment
Reporting comparability suffers
The honest assessment: Standardized accounts are harder upfront but pay dividends forever. Subsidiary-specific accounts feel flexible but create perpetual reconciliation work. Most mid-market businesses wish they'd standardized earlier.
Decision 3: How Do You Handle Intercompany Transactions?
When Subsidiary A sells to Subsidiary B, or when one subsidiary pays expenses on behalf of another, how does that get recorded?
Option A: Separate Intercompany Accounts
You set up a dedicated intercompany account structure. When SubA invoices SubB for services, it's recorded as:
SubA: Debit 1200 (Intercompany AR)
SubA: Credit 4000 (Service Revenue)
SubB: Debit 5000 (Service Expense)
SubB: Credit 2100 (Intercompany AP)
When you consolidate, you eliminate 1200 AR against 2100 AP.
Pros:
Clear visibility into intercompany flow
Easy to audit
Flexible for complex transactions
Cons:
Requires discipline (if someone forgets to record the corresponding entry, the balance is wrong)
More data entry
Option B: Automated Intercompany Clearing
You set up NetSuite's automated intercompany accounting features. When SubA records a transaction affecting SubB, NetSuite automatically generates the offsetting entry.
Pros:
Eliminates manual data entry
Always balanced
Less room for error
Cons:
Requires careful configuration upfront
Harder to troubleshoot if something goes wrong
Less visibility into individual intercompany flows
Decision 4: Currency and Consolidation Timing
If your subsidiaries operate in different currencies, you need to decide:
Option A: Report Consolidated in Parent Currency (USD)
All subsidiary P&Ls are converted to USD at the reporting date. This is standard for most multi-national consolidations.
Pros:
Standard practice for audit and tax
Clear consolidated view
Cons:
Exchange rate fluctuations affect consolidated results
Currency translation adjustments need to be captured (and usually excluded from operating income)
Option B: Report Each Subsidiary in Its Own Currency
Keep subsidiary reporting in local currency with separate USD conversion.
Pros:
Subsidiary management sees their own performance in local currency
Clear separation of operating results from currency effects
Cons:
Requires dual reporting
More complex for group-level analysis
Once you've structured your subsidiaries, you need to configure eliminations. This is where the magic of OneWorld happens—if it's set up right.
What Gets Eliminated:
Intercompany receivables/payables – SubA's AR to SubB gets eliminated against SubB's AP to SubA.
Intercompany profits in inventory – If SubA sold goods to SubB at a markup and SubB hasn't sold them yet, that profit is unrealized and gets eliminated.
Intercompany sales and purchases – If SubA sold $1M to SubB and SubB sold $500K back to SubA, the group's external sales are reduced by the intercompany activity.
Dividends and profit transfers – If SubA transferred $100K to SubB as a dividend, that's eliminated in consolidation (since it's internal movement of capital).
Common OneWorld Mistakes (And How to Avoid Them)
Mistake 1: Modifying the Chart of Accounts Mid-Year
You go live, run through a couple of closes, then realize "we should have this account." You add it. Now your consolidated trial balance doesn't match prior months because the account structure changed.
Fix: Lock down your chart of accounts before go-live. Plan for flexibility (use sub-accounts or tracking categories), but don't change the core structure mid-year.
Mistake 2: Unreconciled Intercompany Balances
SubA recorded an IC payment to SubB, but SubB never recorded the receipt. Now SubA's AP to SubB doesn't match SubB's AR from SubA. Your elimination doesn't balance.
Fix: Reconcile intercompany accounts monthly, not annually. This catches errors early.
Mistake 3: Inconsistent Period-End Close Timing
You're consolidating three subsidiaries. SubA closes on the 15th, SubB on the 20th, SubC on the 28th. Intercompany transactions recorded in late January in one subsidiary don't match because the other subsidiary is still in December.
kStandardize close dates across all subsidiaries, or build a timing buffer into your eliminations.
Mistake 4: Using OneWorld for Non-Legal Entities
You use OneWorld subsidiaries for cost centers or divisions that aren't actually separate legal entities. This works but creates confusion: your OneWorld structure doesn't match your tax and legal structure, so auditors and lawyers have to translate constantly.
Fix: Use tracking categories for cost centers and divisions. Reserve subsidiaries for actual legal entities only.
OneWorld is the right choice if:
✓ You have 2+ legal entities with separate P&Ls and tax filings.
✓ You do intercompany transactions (one subsidiary charging another for services, goods, or expenses).
✓ You need consolidated reporting for investors, lenders, or auditors.
✓ You want to consolidate manually less than quarterly.
✓ You plan to grow through acquisition (new subsidiaries added regularly).
OneWorld might be overkill if:
✗ You have multiple cost centers or divisions but they're all one legal entity. (Use tracking categories instead.)
✗ Your subsidiaries are independent and you almost never consolidate.
✗ You don't have meaningful intercompany transactions.
✗ Your chart of accounts varies significantly between entities and you're not willing to standardize.
Before your NetSuite OneWorld instance goes live, you should complete this architecture review:
Map your legal structure. List every entity—holding companies, operating companies, foreign subsidiaries, JVs.
Define your OneWorld structure. How will these entities be represented as subsidiaries in NetSuite? Does it mirror your legal structure, or does it represent your reporting/management structure?
Standardize your chart of accounts. Identify account number ranges that apply to all subsidiaries vs those unique to specific entities. Document the mapping.
Document your intercompany flows. What transactions happen between subsidiaries? How do they get recorded today? How should they be recorded in NetSuite?
Configure elimination rules. For each intercompany flow, define an elimination rule. Don't leave this for after g.
Test a full consolidation. Before go-l, run a trial close with actual data (or representative test data) and consolidate. Does everything eliminate correctly? Are there surprises?
Most NetSuite implementation partners skip step 6, which is why first closes are messy. Don't skip it.
The architecture decisions happen in the first 2–3 weeks of a NetSuite engagement. We work with your CFO and accounting team to map the legal structure, standardize the chart of accounts, and configure intercompany automation—with the goal of making sure your first close works smoothly, not on the second attempt.
OneWorld is powerful, but it's only as good as the architecture underneath it. That's where most businesses need expert eyes before go-liv.
What's the difference between a NetSuite subsidiary and a separate NetSuite instance?
A subsidiary is a separate legal entity within a single NetSuite instance, with its own P&L and chart of accounts but automatic consolidation and intercompany automation. A separate instance is a completely independent NetSuite account. Subsidiaries cost less, consolidate automatically, and share data more easily. Separate instances are completely isolated.
Do all subsidiaries in OneWorld have to use the same chart of accounts?
No, but it's strongly recommended. If they use different account structures, consolidation becomes a mapping exercise, which adds manual work every month. Standardization is one-time pain that pays lifetime dividends.
How does currency translation work in OneWorld?
When you consolidate subsidiary P&Ls in different currencies, NetSuite converts them to the parent company's currency at the reporting date. Currency translation differences (gains/losses from rate fluctuations) are captured in a separate account, typically excluded from operating income per accounting standards.
Can you add a new subsidiary to OneWorld without disrupting existing consolidations?
Yes, NetSuite allows new subsidiaries to be added and included in consolidations going forward. However, adding historical data from a new subsidiary requires careful cutover planning to avoid consolidation errors in prior periods.