Multi-Subsidiary & OneWorld
Multi-entity close is where most OneWorld implementations fall apart. We design the elimination rules, currency revaluation, and segment reporting before the first transaction posts.
From 3 subsidiaries to 15+. We've built the COA structures, elimination hierarchies, and intercompany billing workflows that hold up when the org chart doubles.
OneWorld is sold as a checkbox. It's actually an accounting architecture decision.
You turned on OneWorld, added three subsidiaries, and the consolidated trial balance looked right for a couple of months. Then someone set up a fourth entity with the wrong COA mapping. An intercompany transaction hit the wrong elimination sub. Currency reval ran against the wrong rate type. And now the consolidation doesn't tie, and nobody can trace where it broke.
We've been called into these situations more than we'd like to admit. The fix is almost always the same: the elimination structure was designed around the org chart as it existed at go-live, not around how it was going to grow.
Why doesn’t the consolidated P&L tie to the sub-level reports?
Usually intercompany elimination rules that don’t account for timing differences or partial-period entries.
We added a new entity and the close takes twice as long now.
The COA mapping and elimination structure wasn’t designed to scale. Every new sub creates manual reconciliation work.
Our auditors keep asking for the same intercompany documentation.
The elimination journal entries aren’t generating supporting detail. The transactions exist, but the audit trail doesn’t.
What we build inside OneWorld
“They onboarded two acquisitions into our OneWorld in under 30 days each. COA mapping, data migration, intercompany rules, go-live.”
— CFO, PE-Backed Portfolio Company · 2 tuck-in acquisitions
A consolidation structure that grows with the org chart.
Most OneWorld setups start with a flat subsidiary list. That works until the third acquisition, when you realize there's no regional rollup layer and the elimination entities don't account for cross-region intercompany activity.
We design the hierarchy with room for growth. Regional elimination entities, functional groupings, and a global consolidation layer that produces clean financial statements regardless of how many entities sit underneath it.
Mockup with fictional data. All subsidiary and entity names are fictional.
Situations we've seen before.
If any of these sound familiar, we've probably fixed it for someone else already.
Start from the legal structure. Work into NetSuite.
Your consolidation shouldn't be the last thing holding up the close.
Free 30-minute consolidation review. We'll look at your subsidiary structure, identify the elimination gaps, and tell you honestly whether the fix is configuration or architecture.