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.
Unbalanced journal import - Mystery decimal (Floating point error?)
Good afternoon,
I'm wondering if anyone else has encountered this: One of our big monthly journals wouldn't import today, because it was unbalanced. I've seen journal imports fail before because of rounding errors, and usually if you Round the values in Excel, paste values, and re-import, you're fine.
But this time it was different. Round, RoundUp, Trunc, and MRound--all of them failed to get the debits and the credits to match. We were still off by 0.001. Looking through the values, none had any value displayed beyond the second decimal place.
I think this is a floating point error, by which I mean there's some number in our import file that isn't representable in Excel's 15 decimal place implementation of binary.