NetSuite OneWorld for European Businesses: Multi-Subsidiary Management Explained

Instead of separate accounting systems in each country and a spreadsheet consolidation at month-end, group finance sees every entity in one place. Local teams still work in their own subsidiary, currency and, where needed, language.

That makes OneWorld a form of multi-entity accounting software, but with the rest of the ERP attached: inventory, order management, purchasing, CRM and e-commerce all run on the same subsidiary structure, so intercompany trading and group reporting come from the same transactions the business already records.

Standard NetSuite, sometimes called basic NetSuite, runs one legal entity. OneWorld adds the subsidiary layer on top of the same product.

OneWorld is usually worth evaluating if any of these apply:

• You have, or plan, more than one legal entity
• Month-end consolidation happens in spreadsheets
• Intercompany balances do not agree and take days to reconcile
• Each country runs its own accounting system
• The board waits weeks for group results
• You are opening a new country and want it live quickly

A single company that simply trades in several currencies does not usually need OneWorld. Standard NetSuite supports multi-currency transactions within one legal entity.

Subsidiaries sit in a parent-child hierarchy. Each one has its own base currency, address, tax registrations, fiscal calendar and accounting preferences. Results roll up from each subsidiary to any level above it, so a regional holding company can report its own consolidated view as well as the group.

Most groups also add an elimination subsidiary. It holds the entries that remove intercompany activity, so consolidated results show only trading with the outside world.

OneWorld sits on top of NetSuite's core financials; see our NetSuite financial management services for the wider finance set-up.

Because translation and elimination run inside NetSuite, consolidated reports are available as soon as transactions post. Month-end becomes a review of results rather than a rebuild of them.

Which exchange rate each account uses

NetSuite keeps a consolidated exchange rate table for every pair of parent and child subsidiaries with different base currencies, with three rate types per period. By default each account type uses one of them:

Because the three rates differ, the consolidated balance sheet carries a cumulative translation adjustment (CTA): the cumulative foreign currency gain or loss on the group's net investment in each subsidiary. Oracle warns that changing rate types away from the defaults can cause discrepancies in consolidated reports, so agree the policy with your auditors before go-live.

OneWorld gives every European subsidiary the same platform. What it cannot do is make every country's rules the same. Plan each of these layers for each country.

E-invoicing timelines across Europe

E-invoicing is the requirement most likely to change during a OneWorld project. These are the main timetables as at November 2026:

Since Brexit, UK and EU subsidiaries follow separate VAT regimes, so trade between them needs its own tax treatment, customs data and documents. Northern Ireland is a further exception: for goods it still follows EU VAT rules, so a Northern Ireland entity or warehouse needs its own tax set-up.

The UK subsidiary also needs Making Tax Digital (MTD) VAT returns and, from April 2029, Peppol-based e-invoicing. A UK parent consolidating EU subsidiaries in GBP will typically report under UK GAAP or IFRS at group level while each EU entity files local accounts, which is where account mapping or multi-book accounting earns its keep.

If you are still choosing who will build it, see how to choose a NetSuite implementation partner in Europe.

Getting the structure right at the start is far cheaper than restructuring later.

1. 1

   Map your legal entities

   List every entity, its country, functional currency, tax registrations and ownership, including entities planned in the next few years.

2. 2

   Design the hierarchy

   Reflect how you consolidate and report, including regional holding levels and an elimination subsidiary.

3. 3

   Agree a global chart of accounts

   Use one group chart of accounts and map it to local statutory charts, rather than separate charts per country.

4. 4

   Set currency and rate policies

   Decide rate sources, revaluation frequency, the rate type for each account and how consolidated exchange rates are maintained.

5. 5

   Define intercompany rules

   Agree which transactions are intercompany, how they are priced, settled and netted, and who approves them.

6. 6

   Plan tax and localisation per country

   Confirm VAT, reporting, SAF-T and e-invoicing needs for each country with local advisers before configuration.

7. 7

   Design roles and controls

   Restrict access by subsidiary and role, and define approvals for intercompany and period close.

8. 8

   Test a full close

   Run transactions, revaluation, eliminations and consolidated reports through a complete period in a sandbox.

Copying the legal structure blindly

Design the hierarchy around how you report and consolidate, not only the shareholding chart.

A chart of accounts per country

Separate charts make consolidation and group reporting much harder. Map local needs to one global chart.

Treating intercompany as an afterthought

Unclear intercompany rules are the main cause of balances that never agree.

Mixing rate types without a policy

Changing an account's rate type away from the default without a reason causes balance sheet differences in consolidated reports.

Assuming localisation is automatic

Each country's tax, reporting and e-invoicing needs must be confirmed and tested, not assumed.

Ignoring future entities

A structure that only fits today's companies makes the next acquisition or new country harder.

Skipping a full test close

Revaluation and eliminations often reveal configuration gaps only at the first real month-end.

Integrations need attention in both cases: each connected system must send the right subsidiary on every record. Our NetSuite integration guide covers how to plan and monitor them.

Oracle does not publish OneWorld prices. It forms part of your NetSuite subscription, and pricing can depend on factors such as the number of subsidiaries or countries. Ask for OneWorld and any country-related items to be listed separately in your quote, and budget for the design, localisation and testing work each country needs.

For the full budgeting picture, see NetSuite implementation cost in the UK.