Mirror the legal structure, then add management views
Subsidiaries in NetSuite generally correspond to legal entities, since each has its own tax registrations, currency, and statutory reporting. Management views, such as business units or regions that cut across entities, are usually better handled with segments than with extra subsidiaries. Mixing the two creates confusing hierarchies and elimination problems. Draw both structures on one page before configuring anything.
- One subsidiary per legal entity that keeps its own books.
- Segments such as department, class, or location for management reporting.
- A clear parent and child hierarchy that drives consolidation.
Currencies and revaluation
Each subsidiary has a base currency, and transactions may occur in others. Decide how exchange rates are sourced, how often they are updated, and how revaluation of foreign-currency balances is handled at period end. Consolidation translates subsidiary results into the parent currency, and translation differences appear in equity. Finance teams should agree on policies with their auditors and document them so the same method is used each period.
Intercompany transactions and eliminations
When one entity sells to or charges another, both sides should be recorded and later eliminated on consolidation. Automating intercompany transactions reduces mismatches, but the commercial agreements behind them, such as management fees and transfer pricing, should be set with tax advisors. Build a monthly routine that checks intercompany balances agree before the close, instead of discovering differences on consolidation day.
Implementation and integration services →Chart of accounts: shared or separate
A shared chart simplifies consolidation and training, while subsidiary-specific accounts handle local statutory needs. Most groups use a common core with the ability to add local accounts where necessary. Agree on a naming and numbering convention, and an approval process for new accounts, so the chart does not drift into a different structure per country.
Consolidated reporting and the group close
Leaders want one set of numbers for the group without waiting for a long close. Design the period-end routine so each subsidiary closes on a published schedule, intercompany balances are agreed, currency revaluation runs, and consolidation follows. Build the management reports around the segments you chose, so a regional or product view needs no spreadsheet reshuffling. A clear calendar, with named owners for each step, shortens the close more than any single feature.
Roles, access and approvals by entity
Users usually need access to only some subsidiaries. Design roles that combine function and entity, such as an accounts payable clerk for the Canadian entity, and set approval limits that reflect local authority. Shared-service teams that work across entities need broader roles with strong controls. Review access regularly, especially when people change positions.
Change management and adoption →Decisions to settle before you configure
- Entity list and effective dates. Document each legal entity, its currency, and when it joins the system.
- Elimination approach. Define which intercompany accounts eliminate and who reviews balances.
- Tax setup per entity. List registrations and filing responsibilities, and have local advisors confirm configuration.
- Future entities. Create a repeatable checklist for adding the next subsidiary.
A realistic first 90 days
- Days 1 to 30. Map legal and management structures, currencies, and intercompany flows, and design the chart and segments.
- Days 31 to 60. Configure subsidiaries, currencies, and roles, and test intercompany and consolidation with sample data.
- Days 61 to 90. Load balances for each entity, run a parallel consolidation, and review translation and elimination results with auditors.
Pitfalls to avoid
- Subsidiaries for every business unit. Extra subsidiaries multiply eliminations and roles. Use segments for management views.
- Manual intercompany. Re-keying both sides creates mismatches. Automate and review monthly.
- Unclear currency policy. Different methods in different entities make results hard to compare.
- No plan for acquisitions. Without a checklist, each new entity becomes a custom project.
