Business Central Salesforce integration for sales and finance
A Business Central Salesforce integration keeps customers, products, prices, orders and invoices consistent between your CRM and your ERP. Microsoft does not ship a Salesforce connector with Business Central. So we build the link on the Business Central API. We use a marketplace connector, an integration platform or custom code. We design, build and support that link.
Last updated
What a Business Central Salesforce integration moves
The usual design treats Salesforce as the place where sales people work. Business Central is the record for money and stock. Accounts and contacts flow to customers. Products and price books follow the item list. A won deal becomes a sales quote or order.
In the other direction, sales people see what finance knows: order status, shipments, posted invoices, open balance and credit limit. They can answer a customer's question about a delivery or an unpaid invoice. They do not need to leave Salesforce or ask accounting. That saves time.
Map your CRM data →
- ✓Accounts and customers
- ✓Products and items
- ✓Price books and prices
- ✓Opportunities to sales orders
- ✓Invoices and balances
When a Business Central Salesforce integration pays off
The warning signs are easy to see. Someone types orders won in Salesforce again into Business Central. Customer addresses differ between the two. Sales people quote prices that finance changed last month. They also promise stock that is already allocated. Finance then spends month-end on credits and fixes.
A link pays off once retyping happens daily, or when mistakes reach customers. If your team is small and orders are few, a simpler routine may be enough, and we will say so. If your company already runs Dynamics 365 Sales, Microsoft's built-in Dataverse connection is the easier path.
Describe your sales process →- ✓Orders keyed twice
- ✓Mismatched customer addresses
- ✓Outdated prices on quotes
- ✓No invoice view for sales
- ✓Stock promised blind
How we build the Salesforce integration
We start by agreeing which system owns each field. Without that rule, two people edit one address in two places and the sync wipes one edit. We write the ownership rules, the matching keys and the direction of every flow. We do this before we choose any tool.
Then we select the method. A packaged connector suits standard objects. An integration platform or Power Automate suits lighter, event-driven flows. Custom API pages in an AL extension cover fields the standard API does not expose. We build and test everything in a sandbox against a Salesforce sandbox.
Compare connector options →- ✓Packaged marketplace connector
- ✓Integration platform flows
- ✓Power Automate triggers
- ✓Custom API pages in AL
- ✓Webhooks for change events
What a Business Central Salesforce integration gives you
You get a running integration with the agreed flows. An error log shows which record failed and why. Alerts tell you about a broken sync the same morning. We match and de-duplicate existing accounts and customers before the first sync. So you do not start with doubles.
We hand over a data map in plain language and the ownership rules. We also leave notes for your Salesforce administrator. They list the fields and rules the link needs. Your team learns to retry a failed record alone. You fix most failures by correcting the record and retrying.
Request a data map example →- ✓Configured sync flows
- ✓Error log and alerts
- ✓De-duplicated starting data
- ✓Plain-language data map
- ✓Administrator handover notes
Mistakes that break CRM and ERP links
Duplicate records are the first. If a match uses a company name that people type differently, the sync makes a second customer. We match on stable identifiers and store each system's ID in the other. That way a renamed account, a merged contact or a changed address still points at the same record.
The next is syncing too much. Every extra object adds API calls, conflicts and maintenance, and Salesforce validation rules can reject records Business Central considers complete. We keep the scope to what people use. We respect API limits on both sides. After each Business Central release wave, we retest.
Get a second opinion →- ✓Duplicate customers
- ✓Two-way edit conflicts
- ✓API limit overruns
- ✓Rejected required fields
- ✓Untested release updates
Business Central Salesforce integration FAQ
Is there a built-in Salesforce connector in Business Central?
No. Microsoft's built-in CRM connection is for Dynamics 365 Sales through Dataverse. We connect Salesforce using the Business Central API. The route is a packaged connector from Microsoft's marketplace, an integration platform, Power Automate or a custom build. We help you choose.
Which system should own the customer record?
Commonly Salesforce owns prospects and contact details. Business Central owns anything financial, such as payment terms, credit limit and tax setup. A prospect becomes a Business Central customer at the first quote or order. The rule matters more than which answer you pick.
Does the sync run in real time?
It can run on events, such as an opportunity closing, or on a schedule. Orders usually need to move quickly, while prices and balances can refresh on a schedule. We set the timing per flow so the integration stays within API limits.
Can sales people see invoices and payments in Salesforce?
Yes. You can show posted invoices, open balances and shipment status on the account in Salesforce as read-only information. Finance keeps control of the records, and sales people stop asking accounting for updates. It is a view only.
Will custom Salesforce fields and objects be supported?
Usually yes. You can map custom fields on either side. Where Business Central's standard API lacks a field, we expose it through a small AL extension. We list every custom field during design, so nothing turns up late. That keeps a Business Central Salesforce integration on plan.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form