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
issue with transaction number
Hi
i have noticed following issue which i wonder any solution or explanation available. if available, Please refer netsuite documentation or suiteAnswerID.
The "transaction number" (Not Document number) is a running sequence across subsidiaries. in other words , one sequence per transaction type is used across our 10 subsidiaries. this is causing us various issues.
issue listed below:
VENDBILL1 SubsidiaryA
VENDBILL3 SubsidiaryA
VENDBILL2 SubsidiaryB
and so on messed up for 10 subsidiaries.
in addition to help inputs from the community i will receive, appreciate help by refering netsuite documentation or suiteAnswerID.
0