Turning On Multi-Currency and OneWorld Mid-Year
A 180-employee distributor has run NetSuite for 14 months as a single-subsidiary, USD-based account with roughly 9,000 sales orders and 22,000 journal entries already posted. Finance has just acquired a Canadian entity and wants to invoice Canadian customers in CAD, keep two GBP bank accounts, and consolidate everything into USD for board reporting. The request that lands on the administrator's desk is 'turn on Multi-Currency and add the new subsidiaries this weekend so we can invoice Monday.' The account has never used departments, classes, or locations; the sandbox was last refreshed five months ago; and a SuiteBilling evaluation is in progress. The Canadian entity will use a different chart-of-accounts naming convention and needs its own tax codes. Only one administrator holds the Full Access role, and month-end close starts in nine days.
1. Which facts must be confirmed before anyone clicks 'Enable' on Multiple Currencies and OneWorld?
Read the worked answer
The critical point is reversibility. Enabling Multiple Currencies and OneWorld is permanent - NetSuite does not provide a supported way to turn either off, and the base currency is fixed at account creation. So before enabling, confirm three things:
- Base currency is genuinely USD for the parent. If finance ever wants to report natively in another currency, that is a consolidation decision, not a base-currency change.
- OneWorld is required, because multiple subsidiaries and a consolidated parent only exist under OneWorld. A subsidiary hierarchy must be designed up front (parent USD, Canadian child, elimination subsidiary for intercompany).
- Downstream dependencies. Currency records, exchange-rate sources, tax codes for Canada, and the SuiteBilling evaluation all behave differently once multi-currency is on. Bundles and scripts that assume a single currency should be reviewed.
A good answer also flags the sandbox problem: refreshing a sandbox copies production feature settings, so enabling in production first and refreshing later will silently propagate the change. Test in a refreshed sandbox, and sequence production enablement outside the close window.
2. Sequence the implementation and state what belongs in sandbox versus production.
Read the worked answer
The sequence matters more than the individual steps:
- Refresh sandbox from production now, while production is still single-currency, so the test copy is realistic.
- Enable OneWorld and Multiple Currencies in sandbox, then create the Canadian subsidiary, CAD currency record, GBP bank account currencies, tax codes, and the chart-of-accounts mapping.
- Test the full cycle - CAD invoice through to USD consolidation, consolidated exchange rates, intercompany elimination, and a trial balance at the parent. Confirm reports still reconcile against the pre-change numbers.
- Enable in production only after sign-off, ideally immediately after close and before the next period opens, with a change record and a rollback-of-process plan (not a rollback of the feature, which is impossible).
- Refresh sandbox again afterwards so test and production match, then re-test any SuiteBilling work.
The judgment being tested is that 'this weekend' is the wrong unit of time. Enabling features is minutes; designing subsidiary hierarchy, tax, and consolidation is weeks. Nine days before close, the correct answer is to invoice the Canadian customer from the existing entity (or delay) rather than rush an irreversible feature change.
3. What should finance be told about base currency, subsidiary currency, and consolidation?
Read the worked answer
Finance usually assumes 'multi-currency' means anyone can report in anything. Clarify the model:
- Each subsidiary has its own base currency; the Canadian subsidiary's books are kept in CAD, and the parent's books in USD.
- The parent's base currency never changes. Consolidation translates child subsidiary balances into USD using consolidated exchange rates (average, current, and historical rates by account type), not a manually entered single rate.
- Consolidated exchange rates must be maintained each period; stale rates produce a wrong consolidated balance sheet even when every subsidiary is individually correct.
- Intercompany transactions need an elimination subsidiary and matching intercompany accounts, or the consolidated P&L double-counts revenue.
Set expectations that the first consolidated close will take longer, require a rate-loading step in the close checklist, and should be rehearsed in sandbox against last month's actuals. Also warn that historical USD-only reports will not automatically restate; they will show consolidated values only from the enablement date forward unless conversion entries are posted.