+1 480 485 7373
Microsoft Teams
Where Salesforce stops and Business Central takes over
Sales teams live in Salesforce: leads, opportunities, activities, forecasts and quotes. Finance lives in Business Central: customers with credit terms, sales orders, shipments, invoices, payments and the ledger. An integration works when there is one clear handoff point. In most companies, that point is the moment a rep marks an opportunity Closed Won or a buyer accepts a quote.
Before that moment, nothing needs to reach the ERP. Pushing every prospect into Business Central fills the customer list with companies that never bought and makes credit control harder. After it, nobody should edit commercial terms in Salesforce. The order in Business Central is now the record that ships and bills.
Information then flows back. Reps want to see order status, ship dates, open invoices and whether the account is on credit hold, without emailing accounts receivable. That return flow is often what persuades the sales team to trust the integration at all.
The quote-to-cash handoff, step by step
- 1
Opportunity reaches Closed Won
A Change Data Capture event, a platform event or a scheduled query picks up newly won opportunities with products attached.
- 2
Account is matched or created
The integration looks up the Business Central customer by a stored Salesforce account ID. If none exists, it creates one with default posting groups and a credit hold until finance approves terms.
- 3
Sales order is created
Opportunity products become order lines using Business Central item numbers, and the order carries the opportunity ID so each side can find the other.
- 4
Fulfillment and invoicing run in the ERP
Warehouse, shipping and invoicing happen in Business Central as normal. Nobody edits quantities or prices back in Salesforce.
- 5
Status returns to the account
The integration writes order status, invoice numbers, amounts due and payment dates to the Salesforce account, so reps can see them.
Salesforce object mapping
Salesforce traps we plan around
API request limits
Salesforce allocates API calls per rolling 24 hours by edition and licenses. A chatty sync polling every minute can starve other connected apps, so use events or the Bulk API for volume.
Validation rules
Custom validation rules written for users also block the integration user. Every rule needs an agreed behavior for the moment the ERP writes status back.
Duplicate accounts
Many orgs hold one company two or three times. Clean up before go-live, or the ERP inherits the duplicates as separate customers with split balances.
Currency and tax
With multiple currencies enabled in Salesforce, send the opportunity currency explicitly. Leave tax to Business Central or a tax engine; CRM quotes should show it as an estimate.
Build options for Salesforce and Business Central
Connector apps
Connector apps on AppSource and on Salesforce AppExchange from several vendors offer prebuilt account, product and order sync. Confirm they support your custom objects and fields before committing.
- ✓Quicker start
- ✓Fixed object model
- ✓Licensed per org or per user
iPaaS, including MuleSoft
Integration platforms such as MuleSoft, which Salesforce owns, and other iPaaS products provide connectors for both systems with mapping, queueing and monitoring. They suit firms with several systems to join up.
- ✓Central monitoring
- ✓Reusable for other flows
- ✓Someone must maintain the platform
Custom API integration
A custom service using platform events or Change Data Capture with the Business Central APIs gives precise control over the handoff. It suits heavily customized orgs.
- ✓Exact fit to your process
- ✓Frugal with API allocations
- ✓You maintain the code
What to monitor once it runs
- ✓A daily count of won opportunities without a matching Business Central order
- ✓API usage against the Salesforce allocation, with an alert well before the ceiling
- ✓Records rejected by validation rules or missing item numbers, routed to a named owner
Salesforce and Business Central questions
Does Business Central have a built-in Salesforce connector?
No, the CRM integration built into Business Central is with Dynamics 365 Sales through Dataverse. For Salesforce you use connector apps, an integration platform or a custom build. If you are also reconsidering the CRM itself, our Dynamics 365 Sales vs Salesforce comparison lays out the trade-offs. Plenty of companies keep Salesforce and integrate it, which is a perfectly sound choice.
Should customers be created in Salesforce or Business Central?
Prospects belong in Salesforce, and customers should come into being in Business Central the first time they buy. The integration can create the customer automatically from the account, but finance should own credit limits, payment terms and posting groups from then on. Salesforce keeps the account for relationship data. Each record stores the other system's ID so the link survives a name change.
Can reps see invoices and payments in Salesforce?
Yes, by writing invoice and balance data back to the account. Most teams need open balance, overdue amount, last payment date and credit hold status rather than every ledger entry. Those fields fit on the account page or a related list. Keeping it to a summary also keeps API consumption low.
More Business Central Salesforce integration questions
What about quotes built in a CPQ tool?
Quotes from a configure-price-quote tool should hand Business Central the final accepted lines and prices. Business Central should not reprice them, but it should check that each item exists and is not blocked. Discounts approved in CPQ travel as line discounts. We look at the CPQ product rules during scoping, because they often reveal items missing from the ERP.
How do we test without touching live data?
Connect a Salesforce sandbox to a Business Central sandbox environment. Refresh both with recent data, then run won opportunities covering new customers, existing customers, parent accounts, several currencies and blocked items. Confirm each order lands exactly once, with the right prices, and that status returns to the account. Only then switch the integration user to production.
Talk to us about your project.
Tell us what you run today and what has to change. A senior consultant replies with a written next step.