Ask the finance director of any multi-entity group what the worst part of month-end is, and you'll usually get the same answer: consolidation. Each entity closes on its own timetable, in its own currency, sometimes in its own system. Then someone spends the back half of close pulling it all together in a spreadsheet (translating currencies, stripping out intercompany, chasing the one subsidiary that hasn't finished) to produce a single group number that the board will scrutinise and the auditors will pick apart.
It's fragile, it's slow, and it's almost entirely manual. It's also exactly the problem NetSuite's multi-entity architecture was built to remove. Here's how it works, and where it still needs proper setup to deliver.
Why multi-entity consolidation breaks spreadsheets and entry-level systems
A single company on a decent accounting system is straightforward. Add a second entity (a new trading company, an overseas subsidiary, an acquisition) and the complexity doesn't just double, it compounds.
You now have:
- Multiple ledgers that each have to close before the group can.
- Multiple currencies, which means someone has to translate every entity into the group's presentation currency at the right rates, every period.
- Intercompany transactions – one entity billing, lending to, or recharging another – that have to be matched, agreed, and then eliminated so the group doesn't count the same activity twice.
- A consolidation hierarchy – which entities roll up into which, and at what ownership percentage.
Entry-level systems (Xero, QuickBooks, older Sage) simply don't do this. So the group builds the consolidation outside the system, in Excel. That spreadsheet becomes the most important financial document in the business and the least controlled: no audit trail, one broken formula away from a wrong board pack, and dependent on the one person who understands it.
That's the bottleneck NetSuite OneWorld is designed to eliminate.
How NetSuite OneWorld handles consolidation
NetSuite OneWorld is the multi-entity, multi-currency, multi-subsidiary edition of NetSuite. The crucial difference from running separate systems is that all entities live in one account, sharing one chart of accounts and one set of rules, so consolidation isn't a report you build after the fact, it's a state the system is always in.
Subsidiaries, currencies & the consolidation hierarchy
In OneWorld you define a subsidiary structure (a hierarchy of legal entities rolling up to a top-level parent) with each subsidiary assigned its own base currency, tax registration and local requirements. Transactions post at the subsidiary level where they belong, and roll up the hierarchy automatically. Add an entity, and it slots into the hierarchy rather than becoming a new spreadsheet tab.
Automatic currency translation
Every subsidiary keeps its own base currency; the group has a presentation currency. NetSuite translates automatically using the exchange-rate types accounting expects (average rate for the P&L, closing rate for the balance sheet) and posts the resulting cumulative translation adjustment for you. The multi-currency translation that eats hours of a group accountant's month happens continuously and consistently in the background.
Intercompany transactions & eliminations
NetSuite recognises intercompany activity between subsidiaries and supports automated eliminations at consolidation, so intercompany sales, purchases and balances are removed from the group view without a manual journal every period. For groups with heavy intercompany trading, this is often the single biggest time saver, and the biggest reduction in error risk.
Group reporting in real time
Because the entities share one system, consolidated reporting isn't a month-end event; it's live. A group P&L, balance sheet or cash-flow view is available at any point in the period, at any level of the hierarchy, in any currency you've configured.
That changes how the group operates. You can see the consolidated position on day two of close, not day nine. You can drill from the group number straight down to the originating transaction in a subsidiary without leaving the report. And the number the board sees is the number in the system, not a spreadsheet derivative that someone has to reconcile back to the ledger.
Where consolidation still needs proper setup
Here's the honest part. OneWorld makes consolidation possible to automate; it doesn't make it automatic by magic. Two areas decide whether you get the clean, fast close or a system that's technically consolidated but still needs manual patching.
Chart of accounts & subsidiary structure
Consolidation is only as clean as the structure underneath it. If subsidiaries use inconsistent chart-of-accounts logic, or the hierarchy doesn't reflect the real legal and ownership structure, the group view will need manual adjustment every period, which defeats the point. Getting the account structure, subsidiary hierarchy and segmentation right at implementation is the highest-leverage decision in a multi-entity build. It's hard to change later and it determines how much of the close is genuinely hands-off.
Intercompany netting & reconciliation
Automated eliminations depend on intercompany balances actually agreeing between entities before you consolidate. If entity A says it's owed £40k and entity B has recorded £38k, the elimination won't net cleanly and the difference lands in the group accounts. This is where a disciplined intercompany reconciliation step within the close matters, and where a proper close-management layer earns its place.
Consolidation and the group close: where MatchPoint fits
NetSuite gives you the consolidation engine. What it doesn't give you on its own is control over the close that feeds it: the assurance that every subsidiary has reconciled its balance sheet, agreed its intercompany positions, and been signed off before the group number is trusted.
That's what MatchPoint adds. MatchPoint is our NetSuite-native close-management platform: balance sheet sign-off, bank reconciliation, GRNI and an executive close dashboard, all with approval workflows and a complete audit trail. For a group, it means you can see the reconciliation and sign-off status of every entity in one view, so consolidation runs on numbers that have actually been checked, not numbers you're hoping are right. Intercompany balances get reconciled properly before elimination, and the whole group close is audit-ready by construction.
Consolidation and close control are two halves of the same job. NetSuite OneWorld handles the first; MatchPoint makes the second fast and controlled.
How Fowlers implements multi-entity NetSuite for UK groups
We implement OneWorld for UK groups the way it needs to be implemented: starting with the structure, because that's what determines whether your close is genuinely automated or quietly manual. We get the subsidiary hierarchy, chart of accounts and segmentation right, configure currency translation and intercompany eliminations to match how your group actually trades, and layer MatchPoint on top so the close that drives consolidation is controlled end to end.
The result is the outcome multi-entity groups come to NetSuite for in the first place: one system, one version of the group numbers, available in real time and ready for audit.
Closing a group across multiple entities? Talk to us about getting consolidation right in NetSuite.