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.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
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