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.
Erratic behaviour of timestamps
For a test saved search of type "Transaction", we've discovered that the timezone setting in user preferences affects custom fields and tranDate.searchValue in a way that seems to be inconsistent. Quoting from the XML response, with timezone -03:00:
<platformCommon:lastModifiedDate>
<platformCore:searchValue>2017-10-16T06:39:00.000-07:00</platformCore:searchValue>
</platformCommon:lastModifiedDate>
<platformCommon:tranDate>
<platformCore:searchValue>2017-03-28T19:00:00.000-07:00</platformCore:searchValue>
</platformCommon:tranDate>
and with timezone +02:00:
<platformCommon:lastModifiedDate>
<platformCore:searchValue>2017-10-16T06:39:00.000-07:00</platformCore:searchValue>
</platformCommon:lastModifiedDate>