Business Central integration with the systems around it
We connect Business Central to e-commerce platforms, CRMs, banks, logistics providers, government portals and internal applications, using whichever pattern suits each integration: API, web service, file exchange or middleware.
The challenge
Integrations rarely fail loudly. A missed webhook, a retry that duplicates an order or an expired token can go unnoticed for days. The design questions (who owns each piece of data, what happens on failure, how do we reconcile) matter more than the connector itself.
Technology we use
How we approach it
The same four steps apply whether the project is a rollout, an integration or a fix. Only the depth changes.
Map data ownership
Which system is the source of truth for customers, items, prices, stock and orders, and in which direction does each flow?
Choose the pattern
API pages, OData, outbound HTTP calls from AL, Azure Functions, Logic Apps, Power Automate or a file exchange, chosen per integration.
Build for failure
Idempotent operations, retry rules, error queues and clear logging so a failed message is visible and recoverable.
Monitor and reconcile
Alerts, reconciliation reports and documentation so support teams can run it without the original developer.
What is included
- Integration architecture and data-flow design
- Inbound and outbound APIs with authentication
- E-commerce, marketplace and CRM connectors
- Bank, payment and logistics integrations
- Government portal and e-invoicing connections
- Azure Functions, Logic Apps and Power Automate flows
- Error handling, retry and alerting design
- Documentation and support runbooks
What you get from it
- Orders, stock and invoices flow without re-keying
- Failures are visible and recoverable
- Systems can change without rebuilding every connection
- Support teams get runbooks, not mysteries
Related pages
Related services
- Business Central API integrationAPI pages, OData, HttpClient calls and OAuth 2.0 authentication.
- Business Central e-commerce integrationProducts, stock, orders and shipments synced with online stores.
- Business Central e-invoicingGenerate, submit and reconcile e-invoices for your country requirements.
- Microsoft AzureAzure Functions, Logic Apps, Service Bus and API Management around your ERP.
- API integrationREST, OData, OAuth 2.0 and webhooks across the Microsoft ecosystem.
Read more
Business Central API vs Web Services: What Is the Difference?
API pages, OData web services and SOAP compared, with URLs, authentication, limits and a simple decision guide.
Calling REST APIs From AL: HttpClient and JSON in Business Central
A practical pattern for outbound REST calls from AL: requests, responses, JSON parsing, errors and secrets.
Frequently asked questions
Can Business Central integrate with external applications?
Yes. Business Central exposes standard and custom APIs, OData and web services, and can call external services from AL. Azure Functions, Logic Apps and Power Automate are common middleware options.
What is the difference between integration and API integration?
Integration is the wider design of how systems exchange data. API integration is the building and consuming of the specific APIs. See our Business Central API integration page for the technical side.
Do you build real-time or batch integrations?
Both. The right choice depends on how quickly the other system needs the data and how much load Business Central can take.