Just finished a rollout. The AP team loves the approval flows, but our accounting sync is a mess.
We're on NetSuite. Invoices are duplicating, GL codes are dropping, and the sync latency is killing our month-end close. Support's canned response is to "review our mapping," but everything was set up by their implementation team. Classic.
Anyone else in manufacturing hit these sync reliability issues? Specifically with job costing or inventory-related accounts? I'm about to scrap the whole thing and build a custom connector.
CRM is a means, not an end.
Classic is right. Their implementation team probably followed the generic playbook that ignores manufacturing-specific fields. They all do.
Scrapping it for a custom connector sounds good until you realize you're now on the hook for every Netsuite API change and Bill.com webhook "update". It's just swapping one vendor headache for a self-inflicted one.
The sync latency alone should've been a dealbreaker before rollout. Their marketing glosses over that for complex GL structures.
Just saying.
Oof, that sync latency for month-end sounds brutal. Our shop uses Salesforce and we get weird spikes sometimes, but not like that.
You mentioned job costing. Is the duplication happening only on transactions with specific manufacturing-specific GL codes? I'm wondering if it's a mapping issue with those particular segments.
Building a custom connector seems like a huge lift. Did your implementation team provide any mapping logs you can actually check, or is it totally opaque?
Trying to figure it out.
Ugh, yes, and I feel your pain on the GL codes dropping, especially around manufacturing accounts. That's usually the first sign the mapping wasn't built for your chart of accounts complexity. Before you go down the custom connector rabbit hole, have you tried pulling the *raw* sync logs from the Bill.com admin panel? Sometimes the generic implementation team maps a specific job costing segment to a "default" field, and it just gets dropped when that field is empty in their system.
Our fix was forcing a re-map of all inventory and WIP accounts manually in the connector settings, even though the implementation team said it was done. It was tedious, but it stopped the drops. The duplication, though... that's a tougher beast and often points to a trigger misconfiguration in NetSuite itself, not just Bill.com.