Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
OneWorld FX Implementation Considerations
From my experience with OneWorld it seems like one of the main benefits of the module is the foreign currency, translation and consolidation engines. However this benefit really accrues for companies where the functional currency of subsidiaries is different than the parent's currency. When the functional currency of the subsidiary is the same as the parent's, the benefit of translation and foreign currency no longer accrues as much (although consolidation is easier than say using a dimension in a regular instance).
In almost all my experiences with existing NS customers who have implemented OneWorld, it seems like in almost all cases the module was implemented by setting all foreign subs to the local currency, without any accounting consideration given to the functional currency. Actually in all the cases I've seen, the functional currency was indeed the same as the parent's company and the fact that the sub was implemented in the local currency resulted in incorrect accounting. This make me wonder if a large majority of NS OneWorld customers even have the FX setup right from an accounting perspective. Given the