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.
Time entry/timebill integration from OpenAir to NetSuite not working
After NS moved us to a new data center Aug 18, we have issues with vendor timebill integration from OA to NS.
After some digging I confirmed that if I manually export a vendor timesheet from OA to NS everything works as it should (time entry goes to NS, creates corresponding time record on NS, a custom script runs to create a linked JE, then NS sends the NS time entry ID back to OA) and the timesheet is marked as exported in OA.
However, when the OA NetSuite Integration script runs as scheduled (or I manually start the integration) with the checkbox to include Time Entries checked, approved un-exported OA vendor timesheets do not export to NS as they should. To make matters worse, the OA time entries do export to NS and corresponding NS time records are created, BUT the custom script that creates a linked JE is not created, and the NS time entry ID is not sent back to OA. Because of this last point, the time entries are exported to NS every time scheduled OA NS integration runs.