Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Subsidiary Transaction Imports (tax nexus locked with wrong value in foreign subs)
Please note-
If a user CSV imports transactions (any type of opportunity through invoice) for a foreign subsidiary Netsuite will automatically assume that the user wants to use the US tax nexus (or whatever the base tax nexus of the person doing the import is).
This is a MAJOR issue/bug because if somebody were to import transactions for a foreign subsidiary subsidiary (Australia perhaps), the transactions that were created become 100% worthless as the Australian tax codes cannot be used with them (the tax code dropdown will only display USA tax codes for these imported transactions, despite the customers being Australian!!) Essentially the transactions will be really screwed up...
0