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.
Duplicate invoice number issues when loading AP as a csv import
I have many vendors that bill us on a weekly basis, so I found that it was quicker with this to load the invoices through an import. Before the upgrade, I knew that it was possible to load a duplicate invoice number for a specific vendor and had accepted that as a possible downfall - so if I received an invoice that wasn't current, I would verify before including on the import.
After the upgrade, if I am trying to load an invoice # that has previously been entered for any vendor - it will not import - and I get the failure message "A record with this ID already exists. You must enter a unique ID in order to create or update this record". Because we utilize a substantial number of small subcontractors - who number sequentially on their invoices - we do have a lot of duplications in the low numbers. Anybody else affected by this? Is there a work around?