Updated 6 October 2026.
A successful NetSuite OneWorld implementation starts with an agreed financial model: which legal entities will transact, how each keeps its books, and how the group reports their results. Settle those questions before creating large volumes of records. A neat organisation chart alone cannot show whether the design will support local reporting, intercompany trade and a dependable group close.
This guide gives group CFOs and controllers a practical workshop structure. The output should be a signed design pack and a tested representative close. Accounting conclusions, including functional currency and consolidation treatment, belong to the group's qualified finance advisers.
List each legal entity, its parent, country, ownership relationship, planned start date, business activities and statutory reporting owner. Record entities that are dormant or due to be acquired separately from entities needed for the first release. Ask which level must produce standalone accounts and which management views span several entities.
Then distinguish legal entities from branches, warehouses, product lines and cost centres. A new reporting requirement does not automatically justify another subsidiary. Conversely, a department label should not conceal a legal entity that needs its own transactions and books. Record the rationale for every proposed subsidiary and every reporting-only dimension.
Oracle recommends planning the hierarchy before creating subsidiary records and treats currencies and tax jurisdictions as setup dependencies. Use that sequence to organise decisions rather than copying an old account's structure.
Document three different questions for every entity: its accounting base currency, the currencies in which it trades, and the currency in which the parent reviews consolidated results. Have finance approve the first; have sales and purchasing provide evidence for the second; agree the third with group reporting.
Base currency is an early design gate. Oracle warns that currency-linked records can prevent changing it. That is a reason to resolve the decision before migration, rather than assuming it can be corrected after transactions arrive.
Give exchange-rate maintenance a named owner and backup. Record the approved source, review process, effective dates and exception handling. Currency rates used for transactions and rates used for consolidation serve different purposes; the close design should show how each is reviewed.
After finance approves base currencies, have the administrator confirm the account's Multiple Currencies capabilities. Customer and vendor currency options can differ in older feature configurations.
Base-currency approval remains a separate design gate.
Build a common account dictionary with account purpose, expected transaction types and permitted subsidiaries. Preserve meaningful local reporting requirements through an agreed mapping or supported accounting design. Avoid inserting every country name into every account merely to reproduce an old spreadsheet.
Define departments, classes and any custom segments around stable management questions. Ask who owns each value and how it reaches the transaction. A segment that is mandatory for reporting but absent from invoices, journals or integration messages will create recurring close work.
Review access alongside reporting. Local accountants should test what they can enter and see, while group reviewers should test consolidated access. Include exported reports and scheduled outputs in that review. An administrator's successful demonstration does not establish that an ordinary finance role can perform the same job safely.
For every recurring intercompany flow, name the selling and buying entities, document types, transaction currency, account mapping, settlement process and reconciliation owner. Loans, shared-service charges and inventory sales may need different workflows and accounting analysis.
Plan elimination subsidiaries as part of the hierarchy. Oracle specifies that an elimination subsidiary has the same country and base currency as its direct parent and accepts journal entries rather than ordinary operating transactions. This makes its placement a consolidation-design choice.
Agree the evidence needed before elimination: paired documents where relevant, balances by counterparty, explained currency differences and approved corrections. Do not treat elimination as a way to hide missing source transactions. The finance team needs both entity-level accuracy and a supportable consolidated result.
Assume a US parent owns Singapore and Australian operating companies. For this fictional design exercise, finance has approved USD, SGD and AUD respectively as their base currencies. The Singapore company buys services from the parent in USD and sells locally in SGD. These assumptions illustrate system design; they do not determine the correct currencies for another group.
The workshop produces three tests. First, enter a local Singapore sale and confirm the customer's document, GST treatment approved by the local adviser, receivable and management segment. Second, process the parent's service charge and match the two entities' documents in the agreed transaction currency. Third, run the group close using approved rates and inspect the consolidated statements and elimination entries.
Suppose the Singapore expense is coded to an undefined department while the parent's income is correctly classified. The group total may appear reasonable, yet the management report cannot explain the charge. The response is to repair the source-data rule and repeat the test, not to accept the missing classification as a reporting adjustment.
For each entity, keep a compact worksheet containing:
Attach unresolved decisions with an owner and due date. Keep assumptions visible until the right person confirms them. Questions that affect base currency, the subsidiary hierarchy or statutory reporting should be resolved before dependent data loads.
Run a representative month that includes a credit note, late bill, foreign-currency settlement and intercompany exception. Reconcile local trial balances to the consolidation and check that reviewers can trace an unexpected figure back to its originating entity and document. Repeat key reports under the roles that will use them.
Before adding another country, revisit the same evidence: entity design, localisation dependencies, banking, tax review, support coverage and group reporting. Reusing an approved template is useful, but the new entity still needs local acceptance.
They determine the legal and consolidation contexts in which transactions and balances are reviewed. Management dimensions can add other views, but their usefulness depends on complete transaction-level data and a tested reporting design.
When finance has approved its important accounting decisions and the implementation team can show how representative transactions reach accepted local and group outputs. A list of enabled features is insufficient evidence.
Bring the entity worksheet and the hardest intercompany flow to a OneWorld implementation discussion. Those two inputs make a design workshop much more productive.