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.
NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.
Register Now
Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.
Intelligent Payment Automation, powered by BILL (formerly 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.
Grouped Items and EDI PO Import
Good day Suite People. I need some feedback if any of you have integrated EDI while using Item Groups. Here is my issue.
We use Item Groups for some items on the Sales Order side of things. These are used to capture "extra" fees or Tariff cost were we want the item and fee to be separated on the accounting side, but combine as one on the invoice. Probably the same thing many of you are using Groups for.
On the EDI side, we have EDI set-up to receive the item number from the customer, but push into NS the internal ID of the Group. This works fine and the Group is created on the SO. The issue is price verification. Our EDI source natively checks the price on the customer PO and validates that amount against the price of the item in NS, if the Internal ID is that of an Item. As you know, grouped items do not have a value, so this validation doesn't work. Furthermore, as we are pushing in