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.
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Restrict class by ROLE (vs. user)
Goal: Restrict user access by classification based on the role they are using.
The classification setting is set on a given user. I have a need for a given user to be able to set a transaction level class, but want to leverage the restrictions as described here:
https://system.na1.netsuite.com/app/...opic=EDIT_ROLE
under each role.
Example: User has 2 roles available. Each role should force transactions to have a given class. Using the Restricting Accounts for Roles recommendation and Employee Restrictions and Class Restrictions I can restrict a user's access to 1 class only as the class setting is on the USER. So, in my implementation, I created 2 roles. One role is setup as described and successfully restricts a user's behavior such that all trans have the correct class. The second role is setup by naming convention to be the 2nd class, but in reality the users can select either class. Thus in that situation, the user is able to set the wrong class on a given transaction.