Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for what’s next!
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Join us
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.
0