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.
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.
Thousands of Date/Period mismatches
My account is cleaning house, closing old periods, etc. He asked Today for the permission to resolve Date/Period mismatches. While I wasn't exactly sure what permission he needed (I suspect it's the "Override Period Restrictions") I was more concerned that we had the problem in the first place.
I did a couple quick sample searches to test a few monthly periods and they have hundreds of transactions with Date that are way out of the range of the period. For example, for period May 2004 we have some Transactions dated 2007!
Now I've created many of these transactions myself and I KNOW I would never explicitly change a Period - I just let NetSuite select the correct one when I set the Transaction Date. So I'm puzzled how this could happen on such a large scale. We haven't done a large import of data or any migration that would cause this.
Steve Klett | Senior Developer
NetValue Technology
