Discussions
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
OneWorld Subsidiary Structure, Functional Currency
Scenario :
For our organization, USD is the functional/base currency.
At implementation, our subsidiary structure was as follows :
A year after implementation, a single international subsidiary was added, along with an Elimination subsidiary :
Two years later, a generic International subsidiary was created, base currency USD, with 5 child subsidiaries under that international subsidiary, all in their local currencies, along with an Elimination subsidiary :
Last year, it was determined that the existing structure was not functioning as desired, and in an attempt to resolve exchange rate pain points, CTA inaccuracies, etc., was implemented. Five grandchild subsidiaries with base currency of USD were created under the International (grandparent) —> Parent (in local currencies) subs, and a grandchild was added under Sub B with a base currency of USD :
Melissa
NetSuite Certified Administrator