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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
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.