ERP & Accounting
SAP Business One
AvailableBring Business One context into field sales.
Explore data & scopeERP & Accounting · Microsoft Dynamics 365Custom integration — assessment required
Start with the Dynamics application your team actually uses.
Business Central, Finance and Operations, and Dynamics 365 Sales have different data models and interfaces. We assess the exact application before proposing a SalesTOS workflow. No universal Dynamics connector is verified.
Microsoft Dynamics 365Authorised source / destination
01
Accounts or customersDynamics → SalesTOS
02
Items and unitsDynamics → SalesTOS
03
ReceivablesDynamics → SalesTOS
SalesTOSField customer identity
Record ownership and direction are defined below. No universal two-way sync is implied.
The operational need
Why connect these systems?
Customer codes can repeat across legal entities.
Field teams need a defined subset of item and account data.
CRM opportunities and accounting invoices have different ownership.
Direction, ownership, prerequisites
What data can be exchanged?
Each row is a separate scope decision. Supported workflows still require configuration; proposed records require assessment and implementation.
| Record or object | Direction | System of record | Purpose | Availability / prerequisites |
|---|---|---|---|---|
| Accounts or customers | Dynamics → SalesTOS | Selected Dynamics application | Field customer identity | Assessment: application and legal entity |
| Items and units | Dynamics → SalesTOS | ERP application | Product context | Assessment: catalogue and unit mapping |
| Receivables | Dynamics → SalesTOS | ERP application | Collection context | Assessment: financial application and balance rules |
| Order handoff | SalesTOS → Dynamics | Destination ERP for accepted order | Office review | Separate custom scope; no automatic posting |
Connection design
How the connection works
Business Central has documented REST APIs; Finance and Operations has distinct data-management interfaces. Select the supported interface for the actual deployment, then agree the service identity, company scope and synchronisation approach.
Illustrative working scenario
From system context to a useful next action.
A regional team receives customers for one legal entity, records visits in SalesTOS and sends an agreed order summary for office review. Accounting continues to own the posted documents.
What happens to writeback?
The proposed customer feed does not automatically create sales orders, invoices or payments in Dynamics.
Before implementation
Setup requirements
- Exact Dynamics product and deployment
- Company or legal-entity identifiers
- Authorised interface and service account
- Sample objects and an owner for field mapping
Use an authorised setup process for credentials. The enquiry form does not request passwords or API secrets.
Operating the agreed scope
Reliability & access
Define composite record keys, retry boundaries and entity-level access in the assessment. No Dynamics-specific monitoring or duplicate prevention is claimed as already implemented.
A clearer scope starts here
Questions, answered.
Microsoft Dynamics 365 integration
Does Business Central equal Dynamics 365 Sales?
No. They serve different purposes and need different mappings.
Can several legal entities share one customer list?
That requires explicit ownership and identifier rules, plus access review.
Is a Microsoft licence included?
Provider licences and API access must be confirmed separately.
Can orders flow back?
Potentially as a separately assessed workflow with validation and office acceptance.
What should we prepare for a Microsoft Dynamics 365 discussion?
Exact Dynamics product and deployment; Company or legal-entity identifiers; Authorised interface and service account; Sample objects and an owner for field mapping. Share redacted examples through an agreed channel, never passwords or API secrets in the public form.
How is Microsoft Dynamics 365 integration scope confirmed?
Review the objects and prerequisites on this page, then agree mapping, access, refresh timing and acceptance criteria. The proposed customer feed does not automatically create sales orders, invoices or payments in Dynamics.
No matching questions. Clear your search or discuss your requirements with us.
Explore the adjacent workflow
Related integrations
ERP & Accounting
Tally
Custom integration — assessment requiredKeep ledger context close to collection follow-up.
Explore data & scopeERP & Accounting
Zoho Books
Custom integration — assessment requiredGive field collections the right accounting context.
Explore data & scopeYour systems. A defined scope.
Discuss This Integration Discuss Microsoft Dynamics 365 with SalesTOS.
Bring your business workflow and current setup. We’ll use them to assess the right data scope.