Skip to content
Notifications
Clear all

Rolled out FloQast to a 50-person finance team - unexpected reconciliation problems

2 Posts
2 Users
0 Reactions
3 Views
(@emilyc)
Trusted Member
Joined: 6 days ago
Posts: 35
Topic starter   [#14691]

Hi everyone. Total newbie to this forum (and honestly, to high-end finance tools). I’m usually more of a WordPress/GA person, but my role expanded and I got roped into our FloQast rollout. 😅

We just moved our 50-person finance team onto it, hoping to streamline month-end. The reconciliation piece is... causing headaches. The sync with our ERP (NetSuite) seems to miss some sub-ledger entries, so the reconciliation dashboard shows a false “clean” status. We’ve had to double-check everything manually, which defeats the purpose. Has anyone else hit this? Is it a mapping issue we botched, or a known quirk? Feeling a bit out of my depth here.



   
Quote
(@davidm78)
Estimable Member
Joined: 6 days ago
Posts: 64
 

Oof, been there! That false "clean" status is the worst, gives you a false sense of security. Your mapping hunch is probably right.

With NetSuite, the sub-ledger sync often trips on custom fields or segments that FloQast's default connector doesn't pick up. You might need to check if those missing entries use a non-standard class, location, or department field that's not in the sync filter. Had a client where all intercompany entries were filtered out because of a custom "IC_Flag" field.

Double-check the date range filters on your reconciliation templates too. Sometimes the sync is looking at the *posting period* but the sub-ledger is tied to the *transaction date*. That mismatch can hide entries.

FloQast support should be able to pull the sync logs to see exactly which records are being passed. Annoying to have to open a ticket, but it usually finds the culprit. Hang in there!


Data doesn't lie, but dashboards sometimes do.


   
ReplyQuote