Most Salesforce and NetSuite integrations start with orders: a won deal becomes a sales order. The trouble starts when the business wants more, such as order status, invoices and payments flowing back to Salesforce, and accounts kept in step both ways. Celigo describes how custom integrations become hard to maintain at exactly that point.
The cost is visible in every account meeting: a rep calls a customer who is 60 days overdue without knowing it, finance updates a billing address that sales overwrites the next day, and nobody is sure which system is right.
Where two-way sync breaks
- No agreed owner per field, so updates ping-pong between systems.
- NetSuite invoices and balances never reach the Salesforce account.
- Duplicate customers created from slightly different names.
- Reps message finance to ask what a customer owes.
How engini keeps them in step
Every engini integration runs both ways, so this is one setup with a workflow in each direction. Account changes in Salesforce, checked as often as every 15 minutes, upsert the NetSuite customer, matched on the Salesforce account id. Invoice and payment changes in NetSuite, checked as often as every 15 minutes, update balance and status on the Salesforce account, in custom fields or a custom invoice object, since engini reads each org’s own custom objects and fields.
You write down which system owns which field once, and the workflows follow it. An AI agent step can handle the judgment calls, such as deciding whether two customers are the same company. For questions, reps add an engini MCP server to Claude or ChatGPT and ask what a customer owes and bought; the agent reads both systems live. The same pattern works with SAP S/4HANA, with SAP changes read on a schedule.
Salesforce
NetSuite
SAP S/4HANA