NetSuite OneWorld Multi-Subsidiary Close and Consolidation

A group close is where an ERP either proves itself or quietly does not.

Everything upstream has to be right before the consolidation can be. That is why consolidation problems are rarely solved in the consolidation.

What OneWorld is actually doing

OneWorld holds multiple legal entities inside one account, arranged in a hierarchy, sharing a chart of accounts and an accounting calendar. Each subsidiary keeps its own base currency and its own books. The group view is produced by rolling those books up, translating them into the parent currency, and eliminating what the group owes itself.

Read that sentence again, because it contains the whole problem. The group view is only as good as the subsidiary books beneath it.

Where it goes wrong, in order of frequency

The chart of accounts drifted. One entity created a local account because the existing one did not quite fit. It was reasonable at the time. Now two entities post similar activity to different accounts and the consolidated view is quietly wrong in a way that does not trigger an error.

Intercompany was entered twice, independently. The selling entity raised an invoice. The buying entity keyed a bill. Nothing linked them. They differ by a rounding difference, a rate, or a period, and somebody spends two days of every close finding out which.

Elimination was never properly configured. So it is done manually, so it is done differently each month, so nobody can explain last quarter without the person who did it.

Periods are closed at different times. One subsidiary is still posting while the group is being consolidated. Everything downstream is then provisional, and the provisional number is the one that reaches the board pack.

The fix is usually upstream

The instinct when a close is painful is to look at the consolidation. It is almost always the wrong place to look.

Governing the chart of accounts, so a local account cannot be created without a decision, removes a whole category of problem permanently. Using the intercompany features so that one transaction creates both sides removes another. Closing subsidiary periods in a defined sequence removes a third.

None of that is glamorous and all of it is cheaper than the alternative, which is a senior finance person spending several days a month reconciling things that should never have disagreed.

Currency, and the two things people confuse

Translation restates a subsidiary into the parent currency so the group can be reported. Revaluation adjusts open foreign currency balances in the subsidiary's own ledger to current rates.

They are different operations answering different questions, and when a close does not tie, it is worth confirming which one you are actually looking at before changing anything.

What good looks like

The group close finishes in a predictable number of days. Intercompany agrees without a reconciliation exercise. Nobody maintains a consolidation spreadsheet outside the system. The elimination entries can be explained by somebody who was not there when they were set up.

If you can say all four, the system is doing its job. If you cannot, the gap between those statements and your reality is a fairly precise description of the work.

Where to start

Time your next close properly. Not the total, but where the days actually go. Most teams discover that the reporting is fast and the finding and fixing is slow, which tells you exactly which of the four problems above you have.

TechCloudPro works on NetSuite OneWorld and multi subsidiary consolidation. The OneWorld implementation checklist covers setting this up correctly in the first place, and month end close optimisation covers the single entity version of the same problem.