How to run the period-end close in NetSuite OneWorld

Prerequisites

These steps assume the Administrator role with Use Classic Interface enabled. NetSuite menu paths are role- and centre-dependent, so a custom role may surface different navigation.

• A NetSuite OneWorld account with the subsidiary hierarchy and each subsidiary's base currency set, and the accounting periods generated for the year (Setup > Accounting > Manage Accounting Periods > Set Up Full Year).
• The Administrator role, or a role with Manage Accounting Periods, Period Close Management and the relevant transaction-locking permissions.
• Multiple Currencies and Automated Intercompany Management enabled if the close involves foreign-currency translation or intercompany elimination.

Steps

1. Confirm the shared period calendar. Go to Setup > Accounting > Manage Accounting Periods. In OneWorld the accounting-period calendar is a single, account-wide record shared by every subsidiary — there is no separate calendar per subsidiary. Confirm the period you are closing exists and that prior periods are already closed so the close runs in sequence.
2. Lock the sub-ledgers progressively. On the period record (or the Period Close checklist) lock transaction types in stages — Lock A/P, Lock A/R, Lock Payroll, then Lock All — as each team finishes. Locking stops new postings into the period while you still allow the close tasks to run, before the final close.
3. Work the Period Close checklist. Open the checklist (Setup > Accounting > Manage G/L > Period Close Management, or the Checklist link on the period). Complete the operational tasks first — review negative inventory and inventory cost accounting, and resolve any date or exchange-rate problems flagged for the period — so the consolidation tasks run on clean data.
4. Revalue open foreign-currency balances. Run the Revalue Open Currency Balances task so unrealised FX gains and losses on open foreign-currency balances post into the period being closed. Run this before consolidation so each subsidiary's base-currency figures that feed translation are accurate.
5. Run the intercompany and consolidation tasks. Work the OneWorld-specific checklist tasks in order: Create Intercompany Adjustments, Eliminate Intercompany Transactions (via the elimination subsidiary and Automated Intercompany Management), then Calculate Consolidated Exchange Rates so the period's current, average and historical rates exist for translation.
6. Generate period-end journals and close. If Period End Journals are enabled, generate them so closing entries post per subsidiary; otherwise NetSuite calculates retained-earnings roll-forward automatically. Apply GL Audit Numbering where statutory numbering is required, then run the final Close task — which closes the period for every subsidiary at once.

Gotchas

• The accounting period is a single global record, so the Close action closes the period for every subsidiary at the same time. You cannot close one subsidiary's month and leave another open — track per-subsidiary readiness with checklist task completion and Period End Journals, but plan the close as one coordinated, account-wide event.
• Calculate Consolidated Exchange Rates must run (or the rates be reviewed) for the period before any consolidated report is meaningful. A period closed without reviewing the consolidated rates produces translation variances that look like posting errors.
• Eliminate Intercompany Transactions only works if the elimination subsidiary exists and Automated Intercompany Management is on, with intercompany accounts flagged to eliminate. Missing any of these means intercompany balances survive into the consolidated numbers.
• If you post adjustments after generating Period End Journals, the generated journals are stale — you must delete and regenerate them before closing, or the per-subsidiary closing entries will not match the adjusted balances.
• Reopening a closed period needs the Override Period Restrictions permission and forces you to re-run the downstream close tasks (revaluation, elimination, consolidated rates). Treat the close as final and keep the override permission tightly held.

Where this bites in an implementation

This bites at the first multi-subsidiary month-end. Teams used to a single-entity close assume they can close subsidiaries independently, then discover the period is global and the intercompany, revaluation and consolidated-rate tasks all have to be sequenced before one account-wide Close. Skip the revaluation or the consolidated-rate review and the consolidated statements show variances that look like booking errors but are really close-sequence gaps. In an implementation, write the OneWorld close as an ordered runbook — lock, revalue, intercompany, eliminate, consolidated rates, period-end journals, close — and rehearse it before the first live period.

Frequently asked questions

Can I close a period for one subsidiary but not another in OneWorld?

No. The accounting period is a single account-wide record, so closing it closes the period for every subsidiary at once. You track readiness per subsidiary through checklist task completion and Period End Journals, but the Close itself is global — so the close has to be coordinated across all subsidiaries against the one shared calendar.

What order should the OneWorld period-close tasks run in?

Lock the sub-ledgers, work the operational checklist tasks, then run Revalue Open Currency Balances, Create Intercompany Adjustments, Eliminate Intercompany Transactions and Calculate Consolidated Exchange Rates, generate Period End Journals if enabled, and finally Close. Revaluation and elimination run before the consolidated rates so translation works on clean base-currency balances.

Do I need Period End Journals enabled to close in OneWorld?

No — without the feature NetSuite rolls income and expense into retained earnings automatically. The Period End Journals feature is for entities that need explicit, auditable closing journals posted per subsidiary, which many international subsidiaries require for statutory reporting. Enable it during implementation if any subsidiary needs visible closing entries.