Rolling Out NetSuite OneWorld Across 100+ Subsidiaries: What Changes at Scale

Private Equity backed businesses tend to grow by acquisition and by spinning up Special Purpose Vehicle companies to hold assets, so the finance system ends up serving a lot of small legal entities across several countries. I led a NetSuite OneWorld implementation of exactly that shape: more than a hundred subsidiaries in six countries. The mechanics are the same as a five-entity rollout. The discipline you need is not.

Design the entity model before anything else

Subsidiary hierarchy, base currencies, elimination subsidiaries and tax registrations are expensive to change once transactions exist. Agree the group structure with finance and tax first, and keep a single source of truth for it. At this scale a register of entities, currencies, countries and tax registrations becomes the input for everything that follows.

One group chart of accounts, controlled local variation

A shared chart of accounts keeps consolidated reporting simple. Local statutory needs are better handled with mapping and segments (department, class, location) than by letting every country add accounts. Decide up front who can request a new account and the approval process. Otherwise the chart of accounts doubles in a year.

Migrate in waves with a repeatable template

Loading entities one by one by hand does not survive the fortieth subsidiary. Build the migration once as a template and run every entity through the same steps:

• Collect opening balances, open AP and AR (including intercompany transactions), fixed assets and master data (employees, customers, vendors and items) in a standard file layout.

• Cleanse and validate the file against rules (missing mappings, inactive accounts, unmatched currencies) before it gets near NetSuite.

• Load, then reconcile the loaded trial balance to the source, per entity, and keep the sign-off with the file.

Power Query or similar automation makes the cleanse step repeatable, and the reconciliation per entity is what finance will actually sign.

Sequence tax configuration deliberately

If you use SuiteTax, set up nexuses, tax codes and registrations per country and test sample transactions in each country before go-live. Tax set-up that looks right in one country can fail in another because of local rules such as reverse charge treatments.

Make sure customer and vendor records are populated with the VAT registration numbers and items/services have Tax Item Type populated.

Add automation after the core is stable

Invoice capture, approval workflows, bank reconciliation and treasury connectivity pay back at this scale, but they sit on top of a clean core. Implement them as post go-live improvements, one at a time, so you can tell what changed when something behaves differently. I have delivered Zone Capture, Zone Reconcile and Cobase banking connectivity this way.

Document as you go

With this many entities, the knowledge cannot live in one person’s head. Keep the entity register, migration templates, mapping rules and tax configuration written down, so a new finance team member or a future consultant can pick it up.

If you are planning a multi-entity NetSuite rollout, see how I approach NetSuite system set-up, or browse all services.