Seven Common Causes
1. Intercompany Differences Surface Too Late
Symptom: Intercompany balances between two entities don't match at month-end, and no one can say right away since when.
What should be checked: Whether an ongoing, in-year intercompany reconciliation exists, or whether differences only become visible during the close itself. Without continuous reconciliation, timing and posting differences accumulate until they all have to be resolved at once at close time.
Areas affected: Intercompany netting, consolidation.
2. Consolidation Adjustments Are Created Outside the System
Symptom: Some group-level adjustments — reclassifications, eliminations, segment alignment — are prepared in Excel and only transferred back into the system at the very end.
What should be checked: Whether top-side consolidation entries go through a defined, system-based process with tagging, approvals, and an audit trail, or whether they exist as Excel deltas running in parallel to the system.
Areas affected: Consolidation, reporting, audit trail.
3. Close Tasks Have No Binding Sequence
Symptom: Entities close in whatever order suits them, and consolidation regularly ends up waiting on the slowest one.
What should be checked: Whether a close calendar with task dependencies exists — entity close before intercompany reconciliation, reconciliation before consolidation, consolidation before group reporting — and whether it is actually enforced.
Areas affected: Close process, governance.
4. Multi-Book Ledgers Don't Run Consistently in Parallel
Symptom: Local GAAP and IFRS (or another book combination) diverge in places that can't be explained by genuine accounting differences.
What should be checked: Whether both books are consistently fed from the same posting, or whether certain items are booked twice or adjusted manually in specific spots.
Areas affected: Multi-book accounting, reporting.
5. Segregation of Duties Runs on Manual Approval Lists
Symptom: Approvals for postings, payments, or consolidation steps depend on individual people and email chains rather than a system-based role model.
What should be checked: Whether segregation of duties is enforced through the role and permission model — who posts, who approves, who has visibility — rather than through informal arrangements.
Areas affected: Governance, audit readiness.
6. Master Data Has Drifted Apart Between Entities
Symptom: The same dimension (department, class, segment) no longer means the same thing in two entities, or is maintained differently.
What should be checked: Whether a shared chart of accounts with consistent dimension logic applies across all entities, or whether local deviations have crept in.
Areas affected: Chart of accounts, consolidation, reporting.
7. Reporting Is Built in Parallel to the System
Symptom: Management reporting is produced in a separate Excel or BI model that regularly diverges from the NetSuite figures.
What should be checked: Whether native consolidated reports are actually used at every node of the subsidiary hierarchy, or whether reporting continues to be assembled manually out of habit.
Areas affected: Reporting, management information.
Fixing the architecture — reconciliation, sequencing, and book design — resolves the delay without requiring additional finance headcount.
Case Reference: 22 Days Down to 8
An industrial services group with 14 entities was closing the month in 22 working days. The improvement to 8 days came from three concrete changes: a redesigned intercompany netting structure, a binding close calendar, and consolidation moved entirely into NetSuite instead of running in a parallel Excel model.
When an Architecture Review or Health Check Makes Sense
If more than one of the causes above applies, or if no one on the team can say with confidence which one accounts for the largest share of the delay, a NetSuite System Health Check is the fastest way to a reliable diagnosis. Where it's already clear that the consolidation or intercompany architecture itself needs to be reworked, the direct route is an Architecture Review as part of a scope call.