Salesforce Accounting Integration implementation · CloudX
Salesforce accounting integration: NetSuite, Priority, Hashavshevet and Rivhit
CloudX connects Salesforce to your accounting system or ERP: customers and deals closed in sales reach finance, and invoices, receipts and open balances flow back to the customer record in Salesforce. Our Salesforce-NetSuite integrations built in Workato run in production at clients, and CloudX is a certified Workato partner. For Priority, Hashavshevet, Rivhit and other systems we connect through the system's API, through Workato or with a dedicated service, depending on what your system and version support. The accounting document itself is always issued in the accounting system, under Israel Tax Authority rules.
Why connect Salesforce to your accounting system
When sales runs in Salesforce and finance runs in an accounting system or ERP, every gap between them becomes manual work and errors. A customer closed by sales is set up again in accounting, an order is typed twice, and the sales rep does not know whether the last invoice was paid before offering an expansion.
Questions we hear:
- "How can we see in Salesforce whether the customer has paid?"
- "Why is every customer created twice, once in sales and once in finance?"
- "Can we issue an invoice from Salesforce?"
- "We run Priority or Hashavshevet. Can they connect to Salesforce?"
What moves, and in which direction
| Data | Direction | Source of truth | When |
|---|---|---|---|
| Customer | Salesforce to accounting | Salesforce for commercial details, accounting for billing details | When the first deal closes |
| Order or closed deal | Salesforce to accounting | Salesforce | When the deal closes |
| Invoice | Accounting to Salesforce | Accounting | On issue, or on a schedule |
| Receipt and payment | Accounting to Salesforce | Accounting | When payment is recorded, or on a schedule |
| Open and overdue balance | Accounting to Salesforce | Accounting | Scheduled sync |
| Products and price lists | Decided during the specification | One system, never both | On change or on a schedule |
The core rule: money belongs to accounting. Salesforce shows invoices, receipts and balances, but never recalculates them. When sales and finance look at the same number, the conversation with the customer is accurate.
Accounting documents under Israeli Tax Authority rules
In Israel, tax invoices, tax invoice receipts, receipts and credit notes are issued by software that meets Israel Tax Authority requirements, with sequential numbering and retention under the rules. So in the right design, Salesforce does not issue the document itself. Salesforce requests it, through a button or a step in a process, and the document is issued in the accounting system. The document number, date, amount, VAT, status and a link to the PDF flow back to the Salesforce record.
The same applies to allocation numbers under the Israel Invoices model: when an invoice requires an allocation number, it is obtained as part of issuing the document in the accounting system, and Salesforce receives it with the rest of the document details.
For nonprofits, the same principle covers donation receipts under Section 46. The donation is recorded in Salesforce and linked to the donor, the receipt is issued in the system authorized to issue it, and the number and file flow back to the donation record.
IDs and customer matching
Records are matched by ID, not by name. Each customer in Salesforce stores its account number in the accounting system, and each account in the accounting system stores its Salesforce ID. Before creating a new customer, the integration checks by company number, VAT registration number or nonprofit registration number whether it already exists, because a Hebrew name is spelled differently in every system. Every write is an upsert by ID, so rerunning after a failure never creates a duplicate account.
Israeli details that shape the specification:
- Withholding tax: a receipt can be lower than the invoice because tax was withheld at source. That is why the open balance comes from accounting, not from a calculation in Salesforce.
- Currencies: a deal in dollars and an invoice in shekels, or the other way round. The exchange rate is set in accounting, and Salesforce shows the amount as recorded there.
- Hebrew: names, addresses and product descriptions in Hebrew move unchanged. With older systems we check encoding and field lengths before go-live.
The systems we connect
NetSuite
We have built Salesforce-NetSuite integrations in Workato that run in production: a Salesforce account becomes a NetSuite Customer, a closed deal becomes a Sales Order, and invoices, receipts and the open balance flow back to the account. We have also built a daily invoice sync from NetSuite in n8n, and email intake of purchase orders into Salesforce and NetSuite. More on our Workato page.
Priority
Priority exposes a REST API through which customers, orders and documents can be created and updated according to the user's permissions. A Salesforce-Priority integration we built runs in production at a client, directly from Salesforce or through Workato depending on the number of processes. We have already built a process running in production that creates orders and order lines in Priority from PDF and Excel files.
Hashavshevet
How you connect to Hashavshevet depends on the version and the deployment, cloud or on-premise: an API in versions that support one, or import of files in the structure the system defines. During the specification we check what your version allows, and build the connection through a dedicated service or an integration platform, with every run logged.
Rivhit
Rivhit is a cloud system with an API for issuing documents and retrieving customer and document data, depending on your plan and permissions. A Salesforce-Rivhit integration we built runs in production at a client: the document is issued in Rivhit, and the number and file flow back to the record.
Other systems
SAP Business One, other ERPs and online invoicing services connect the same way: through the system's API, through Workato, or with a dedicated service when no ready connector exists.
The tools
- Workato: ready connectors for Salesforce, NetSuite and many other systems, with run history, alerts and permission management. CloudX is a certified Workato partner.
- Code on the Salesforce side: Flow and Apex with a Named Credential holding the access details, and a Queueable job that throttles calls when the target system limits concurrent requests.
- A dedicated service: a small Node service when you need to translate between structures, import files or connect a system without a ready connector.
- n8n: for a focused sync, such as a daily pull of invoices.
- NOCA.AI: when the input is a document, such as a purchase order or supplier invoice in PDF, that has to be read before the data enters the system.
Error handling, reconciliation and monitoring
- Run log and alerts: every run is recorded, and a failure alerts a named owner in finance or operations.
- Controlled retries: a temporary failure is retried automatically. A data failure, such as a customer with no company number, stops and waits for a fix.
- Working within limits: NetSuite limits concurrent requests, and Salesforce limits daily API calls and locks parent records during updates. We throttle and batch accordingly.
- Reconciliation report: a periodic comparison of totals in both systems, so a gap surfaces before month-end close, not during it.
- Least privilege: a dedicated integration user in each system, with access only to what the process needs.
How a project runs
- Mapping with finance and sales: what each team needs to see, and who owns each piece of data.
- System review: version, available interfaces, permissions and a test environment.
- Specification: field table, directions, IDs, document types and edge cases: a credit note, a partial payment, a cancelled order, a merged customer.
- Build and test: against a Salesforce sandbox and a test environment or test company in the accounting system.
- Acceptance testing with finance: on real scenarios, including reconciliation of totals.
- Go-live and support: in the first weeks we watch every run, then continue with ongoing support.
What drives the cost
There is no fixed price, because cost depends on scope. The main drivers:
- The accounting system and the interfaces it offers. A system with a modern API is simpler to connect than one that requires file imports.
- The number of objects and document types that move, and in which directions.
- Edge cases: partial payments, currencies, withholding tax, split orders.
- The quality of existing data, and the need to match customers that already exist in both systems.
- An integration platform license when one is needed, and the scope of ongoing support.
Why CloudX
- Salesforce-NetSuite integrations running in production, and a certified Workato partnership.
- Depth in Salesforce: the integration respects your data model, permissions and existing automations.
- Experience with the limits of finance systems: throttling, record locks and document numbering.
- Finance inside the project: specification and acceptance testing with the finance team, not only with sales.
Using monday.com too? See Salesforce and monday.com integration. Want invoices, receipts and open balances inside Salesforce? Talk to us.
Work we have done
Cloud security company · In production
Salesforce-NetSuite in Workato: each customer created once
Sales closed deals in Salesforce, and finance then recreated each customer in NetSuite by hand, so the same customer often existed twice and reps kept asking finance whether an invoice had been paid. We built the integration in Workato: accounts and opportunities move from Salesforce to NetSuite with external IDs on both sides, and invoices, receipts and the open balance flow back onto the account. On top of the synced data we built Workbot and Workato AI agents that answer the team's questions. Finance no longer retypes customers, and a rep sees the payment picture before calling the customer.
Construction technology company · In production
Salesforce-NetSuite in Workato: the financial picture where sales works
Sales and Customer Success could not see the finance side: which invoice went out, what was paid and each customer's open balance. We built a Workato sync between Salesforce and NetSuite for accounts, opportunities, invoices, receipts and open balances, so financial data appears on the account in Salesforce. Workbot and Workato AI agents run on top of the integration, letting the team ask about a customer and trigger actions from the tools they already use. A renewal or collections call now starts with the whole picture in view, without going to finance.
Software security company · In production
Daily invoice sync from NetSuite to Salesforce
Invoices were created in NetSuite and never reached Salesforce, so the people working with the customer could not see what had been billed. We built an n8n workflow that runs every day, pulls invoices from NetSuite with a SuiteQL query over an authenticated connection, and creates them as records in Salesforce. n8n fit a focused need: one data type, one direction. Invoices now appear in Salesforce, and the team works from them without asking finance for reports.
B2B technology company · In production
Email purchase orders into Salesforce and NetSuite, at a pace NetSuite can take
Purchase orders arrived by email as PDF and Excel files, and a sales rep typed each one by hand. We built an Apex Email Service that receives the messages in Salesforce and a Queueable job that throttles the work one record at a time, so orders reach NetSuite within its concurrent request limit and without record locks. Document reading runs on NOCA.AI, which classifies each email as a new order, an update or a cancellation. The operations team now handles exceptions instead of typing orders.
Industrial company · In production
Orders and order lines created in Priority from files
Customer orders arrived by email as PDF and Excel files, and identifying the customer, products, prices and delivery dates was done by hand. We built a process that identifies the customer and products by internal SKU, then customer SKU and only then a generic SKU, checks that the price is within the defined tolerance and applies the delivery date rules. The process creates the order and its lines in Priority, including line numbering when the file has none. The team opens ready orders in Priority, and only lines that failed a price or date check wait for a decision.
Organization managing customers in Salesforce and accounting in Rivhit · In production
Salesforce connected to Rivhit: documents issued from the deal
Sales and customers live in Salesforce, and accounting documents are issued in Rivhit. We connected the two so the document is issued in Rivhit from data already in Salesforce, and the document number and file flow back to the record. Sales and finance see the same picture, without typing the customer twice.
Company selling in Salesforce and running operations and finance in Priority · In production
Salesforce connected to Priority: from sale to ERP without double entry
Customers and deals are created in Salesforce, and operations and finance run in Priority. We connected the two through the Priority REST API, so what closes in sales reaches Priority without double entry, with one source of truth set for each field.
FAQ
How do you integrate Salesforce with an accounting system?
First you define what moves in which direction: customers and orders from Salesforce to accounting, and invoices, receipts and balances back to Salesforce. The connection is built through the system's API, through Workato or with a dedicated service, with shared IDs, failure alerts and a reconciliation report. The accounting document itself is always issued in the accounting system.
Who integrates Salesforce with accounting systems in Israel?
CloudX is an Israeli consultancy and a certified Workato partner that builds integrations between Salesforce and finance systems. Our Salesforce integrations with NetSuite, Priority and Rivhit run in production at clients, and we also connect to Hashavshevet and other systems. Specification and acceptance testing are done together with the finance team.
Can Salesforce integrate with Priority ERP?
Yes. Priority exposes a REST API through which customers, orders and documents can be created and updated according to the user's permissions. We connect to it directly from Salesforce or through Workato, and we have already built a process running in production that creates orders and order lines in Priority.
Can Salesforce connect to Hashavshevet?
Yes. The method depends on the version and deployment: an API in versions that support one, or import of files in the structure Hashavshevet defines. During the specification we check what your version allows and build the connection through a dedicated service or an integration platform, with every run logged.
Can Salesforce connect to Rivhit?
Yes. Rivhit is a cloud system with an API for issuing documents and retrieving data, depending on your plan and permissions. An integration like this that we built already runs in production: the document is issued in Rivhit, and the number and file flow back to the Salesforce record.
What syncs between Salesforce and NetSuite?
In the pattern we build in Workato, a Salesforce account becomes a NetSuite Customer and a closed deal becomes a Sales Order. Invoices, receipts and the open balance flow back from NetSuite and appear on the account. These integrations run in production at clients.
Can we issue a tax invoice from Salesforce?
You can request it from Salesforce, through a button or a process step, and the document is issued in the accounting system, which meets Israel Tax Authority requirements. The document number, amount, status, a PDF link and the allocation number when required flow back to the record. That keeps numbering sequential and gives money one source of truth.
How can a sales rep see in Salesforce whether a customer has paid?
Invoices, receipts and the open balance sync from accounting to the customer record in Salesforce. The balance comes from accounting and is never recalculated, because withholding tax, partial payments and currencies affect it. Before a renewal or collections call, the rep sees exactly what is outstanding.
Workato or a direct coded integration?
Workato fits when there are several processes, when you need run history, alerts and permissions in one place, or when a ready connector exists for the system. Dedicated code fits a focused connection or a system with no connector. We build both ways and choose by what will hold up over time.
How much does a Salesforce accounting integration cost, and how long does it take?
There is no fixed price. Cost and timeline depend on the accounting system and its interfaces, the number of document types and directions, edge cases such as partial payments and currencies, and the quality of existing data. After the specification phase we give a grounded estimate.
How do you prevent duplicates and gaps between the systems?
Every record is written by a shared ID, and every new customer is first checked by company number, VAT registration number or nonprofit registration number. A failure is logged and triggers an alert, and a rerun never creates a duplicate. A periodic reconciliation report compares totals across the systems, so a gap surfaces before month-end close.
Nonprofits: how do Salesforce donations connect to Section 46 receipts?
The donation is recorded in Salesforce and linked to the donor, and the receipt is issued in the system authorized to issue it. The receipt number and file flow back to the donation record, so the fundraising team sees the donation and its receipt in one place.
Last updated: