What happens to the group close when the group itself changes?
An acquisition in June, a disposal in September, an ownership percentage that shifts from 55 to 80. NetSuite carries the close. The Consolidation Extension carries the history of the scope it was closed against.
Can you still reconstruct, two years from now, which group structure a given period was closed against?
If the answer is a spreadsheet somebody maintains, that is the gap. Ownership percentages, consolidation methods and scope membership change during the year. NetSuite models the entity hierarchy as a data structure rather than an org chart in Excel — but a fully specified ownership structure with its history over time goes beyond that. That is exactly the layer we built.
Two layers, and the lower one does most of the work.
Layer 1 — NetSuite standard
Entity structure, multi-currency and group currency, intercompany foundations, one chart of accounts as a consolidated data foundation.
This is genuinely a lot, and most groups need nothing more. Entities and their hierarchy live in the data structure. Local and functional currencies per entity are the basis for translation. Intra-group accounts and transactions exist as their own structure — the basis for matching and later elimination.
If your group is stable in composition, this layer closes your books. Read that sentence as an invitation to stop here.
Layer 2 — Consolidation Extension
Scope over time, and capital consolidation with the parts that make an auditor comfortable.
It becomes relevant at exactly one point: when the composition of the group changes and the change has to remain traceable afterwards, period by period.
One group close, from 22 days to 8.
Most of that result came from architecture, not from the extension. We would rather say so than let a number do work it did not do.
When you need this — and when the standard is enough.
Your group composition is stable. No acquisitions, no disposals, ownership percentages that have not moved in years.
You consolidate fully, at one hundred percent, without minority interests and without equity-method holdings.
Your close is slow for reasons that live in intercompany or in the close calendar. Fix those first — they are cheaper and they are usually the real cause.
The scope changed during the year and the prior-year comparison has to survive it.
You carry minority interests, or holdings that move between full, proportional and equity method.
An auditor has asked which structure a given period was closed against and the answer took more than a minute to produce.
In most stalled group closes the extension is not the answer. Intercompany billing that was never structured, a close calendar nobody is bound by, and consolidation running through a parallel Excel model account for more lost days than any missing feature. We look at those first, and we say so when that is where it sits.
Short answers first.
Can NetSuite consolidate without an additional tool?
Yes, for most group structures. Entity hierarchy, multi-currency, intercompany foundations and one consolidated chart of accounts are part of the platform. A separate consolidation tool becomes unnecessary far more often than it gets sold. The Extension addresses a narrower question: what happens when the scope itself changes.
Do we need Multi-Book for consolidation?
No. Multi-Book is a separate accounting topic — neither a component of nor a prerequisite for consolidation. It becomes relevant when an entity posts in parallel to local and group GAAP, for example a German entity with both HGB and IFRS obligations. The two get conflated often enough that it is worth stating plainly.
We acquired a company mid-year. What breaks?
Usually the comparison, not the close. The current period closes. What gets hard is the prior-year comparison and the question of which structure each period was measured against. Mapping scope changes on a time basis is precisely what Layer 2 does.
Our close takes three weeks. Will this fix it?
Probably not on its own. In the case above the close went from 22 days to 8, and most of that came from a redesigned intercompany billing structure, a binding close calendar and moving consolidation out of a parallel Excel model. Start with a diagnosis, not with a component.
Which consolidation architecture does your ownership structure force?
Bring your entity list, your ownership percentages and the changes of the last two years. That is usually enough to say whether this is an architecture question, a process question, or genuinely a component question.