megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.

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!
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe

Unbalanced journal import - Mystery decimal (Floating point error?)

edited Dec 3, 2019 1:13PM in Account Administration 2 comments

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.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders