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.
Tip: NetSuite will call your static methods
I'm always trying to avoid globals wherever I can, they can introduce very hard to find bugs when you stomp on another piece of code because of name conflicts, don't promote well organized code and make it more difficult to separate subsystems from one script file into another (when we have support for multiple files... hint hint NetSuite)
This might not be news but I wasn't sure if it work so I tried specifying a static object method in the script record and it works.
So instead of just have a global method: OnInit() you can have MyObjectName.OnInit
If your client object is stateful and requires an instance to function correctly you can still define static "entry point" methods that call instance methods internally.
Steve Klett | Senior Developer
NetValue Technology
