Integrating Business Central with Third-Party Applications

Updated June 26, 2026 · Originally published August 12, 2010

TL;DR

Integrating Business Central with third-party applications is one of the most common and most impactful things an organization can do after implementing the platform. No ERP handles every business function in isolation. Payroll, eCommerce, CRM, EDI, point-of-sale, field service and industry-specific tools all generate data that needs to flow into and out of Business Central. Here is how those integrations work, what to consider before building them and where things typically go wrong.

In This Article

• Why integration matters for Business Central users
• Integration approaches for Business Central
• Common third-party integrations for Business Central
• What to consider before integrating
• What goes wrong with poorly planned integrations
• Common questions about integrating Business Central with third-party applications

Integrating Business Central with third-party applications is not a nice-to-have. It is a practical necessity for most organizations running Business Central in a real business environment. The ERP handles financials, inventory, purchasing, production and sales well. But it does not replace every system the business depends on. Payroll runs in a dedicated system. eCommerce runs on a separate storefront. Field service may run in a specialized tool. CRM data lives in Dynamics 365 Sales or Salesforce.

Without integration, data moves between those systems manually. Someone exports a file, reformats it and imports it somewhere else. Or they re-key transactions. Or they reconcile two systems at month-end and try to figure out why the numbers do not match. Every one of those processes takes time, creates errors and scales badly as volume grows. Business Central has a well-developed integration framework that eliminates that manual overhead when the integrations are designed and built correctly.

Why Integration Matters for Business Central Users

The goal of integrating Business Central with third-party applications is a single, accurate view of the business. When every system that generates financial transactions connects to Business Central, the general ledger reflects reality. When inventory updates in real time across every channel, the business makes better decisions. When customer data flows between CRM and ERP, sales and finance work from the same information.

The alternative is islands of information. Each system has its own version of the data, updated on its own schedule, with its own definitions of customers, vendors and products. Reconciling those islands takes time and rarely produces perfect results. Integration eliminates the islands and the overhead that comes with them.

Integration also affects how the business scales. A manual process that works at low volume stops working when transaction counts increase. An automated integration scales with the business without adding headcount or creating new bottlenecks.

Integration Approaches for Business Central

Business Central supports several integration approaches depending on the systems involved and the data that needs to flow between them:

Native connectors. Business Central includes built-in connectors for several common systems. The Shopify connector syncs orders, customers, products and inventory between Shopify and Business Central natively. Microsoft 365 integration connects Business Central to Outlook, Teams and Excel without any additional configuration. Power Platform integration lets organizations build Power Apps and Power Automate flows that interact directly with Business Central data.

AppSource extensions. The AppSource marketplace has hundreds of pre-built integration extensions for Business Central. Payroll systems, EDI platforms, eCommerce tools, shipping carriers, CRM systems and industry-specific applications all have AppSource connectors built and maintained by certified Microsoft partners. These extensions are the fastest and lowest-risk integration path when they cover the specific systems and data flows the business needs.

API-based custom integrations. Business Central exposes a comprehensive REST API that allows developers to read, write and update any data in the system. Organizations with proprietary internal systems, industry-specific platforms or requirements that AppSource does not cover can build custom integrations against the Business Central API. These integrations require more upfront design and development work but give the most flexibility.

Power Automate flows. For lighter-weight integration scenarios, Power Automate connects Business Central to hundreds of systems through pre-built connectors and custom flows. This approach works well for notification workflows, approval routing and data sync scenarios that do not require real-time transaction processing.

Common Third-Party Integrations for Business Central

A few categories of third-party integration come up consistently for Business Central users:

Payroll. Payroll systems like ADP, Paychex and Ceridian generate journal entries that need to post to the Business Central general ledger. Integration automates that posting and eliminates the manual import process that most organizations use when the systems are not connected.

eCommerce. Shopify has a native connector. WooCommerce, Magento and other platforms connect through AppSource extensions or custom API integrations. The integration keeps orders, inventory and customer data in sync between the storefront and Business Central without manual intervention.

EDI. Organizations that buy or sell through EDI trading partners need to connect those transaction streams to Business Central. EDI integration handles purchase orders, advance ship notices, invoices and other documents in the standard EDI formats trading partners require.

CRM. Dynamics 365 Sales has a native integration with Business Central that connects customer records, sales orders and invoices across the two systems. Salesforce and other CRM platforms connect through AppSource extensions or custom API integrations.

Point-of-sale and field service. Organizations with physical retail locations or field service operations often run specialized tools for those functions. Integrating those systems with Business Central keeps transaction data current in the ERP without requiring manual entry at the end of each day or shift.

Shipping and fulfillment. Shipping carriers and 3PL platforms connect to Business Central to automate label generation, tracking updates and fulfillment confirmation. This keeps order status accurate in Business Central and reduces the manual touchpoints in the fulfillment process.

Reporting and analytics. Power BI integrates natively with Business Central and pulls live data for dashboards and reports. Tools like Solver extend Business Central's reporting capabilities with more configurable financial reports and budgeting tools for organizations that need more than the native reporting provides.

What to Consider Before Integrating

Before building an integration between Business Central and a third-party system, work through a few key questions:

What data needs to flow and in which direction? Some integrations are one-way. Others need to sync data bidirectionally. Defining the data flows clearly before development begins prevents scope changes during the project and ensures the integration actually meets the business need.

How frequently does the data need to sync? Real-time integration is not always necessary or appropriate. Some data flows work well on a scheduled basis. Others need to happen in real time to support the business process they enable. Getting that requirement right affects the integration architecture significantly.

What does the data look like in each system? Item numbers, customer identifiers, account codes and vendor records rarely match perfectly between systems. Mapping those fields and handling exceptions is a significant part of integration design. Discovering those mismatches during development rather than before it adds time and cost to the project.

What happens when the integration fails? Every integration fails at some point. A well-designed integration has error handling, alerting and a recovery process so the business knows when something goes wrong and can address it before it creates downstream problems.

Technology Management Concepts (TMC) has been building integrations for Microsoft Dynamics ERP systems since the earliest versions of GP and NAV. That experience includes payroll integrations, eCommerce connections, EDI implementations, CRM syncs and the kind of custom API work that organizations with proprietary systems need when AppSource does not cover the requirement.

Talk to TMC about integrating Business Central with your third-party applications.

What Goes Wrong with Poorly Planned Integrations

Integration projects that run into problems almost always share the same root causes:

Undefined data mapping. When nobody defines how data fields in one system map to fields in the other before development begins, developers make assumptions. Those assumptions produce integrations that work technically but do not match how the business actually uses the data.

No error handling. Integrations without error handling fail silently. A transaction that does not post to Business Central because of a validation error disappears without anyone knowing. By the time the discrepancy surfaces, it is already a reconciliation problem.

Treating integration as an afterthought. Organizations that add integrations after go-live rather than designing them as part of the implementation often find that the system configuration does not support the integration cleanly. Building integration requirements into the implementation scope from the start produces better results at lower cost.

Not testing against real data. Integration testing with sample data misses the edge cases that real transaction data produces. Testing with actual data from the systems being connected surfaces the mapping issues, validation failures and volume considerations that clean sample data hides.

Frequently Asked Questions

Does Business Central have an API for third-party integrations?

Yes. Business Central exposes a comprehensive REST API that supports reading, creating, updating and deleting data across the system. The API follows OData standards and covers all major business objects including customers, vendors, items, sales orders, purchase orders, journal entries and more. Organizations with development resources can build integrations against the Business Central API directly. Those without development resources can use AppSource extensions or work with a partner like TMC to build what they need.

What is the difference between an AppSource integration and a custom integration?

An AppSource integration is a pre-built extension developed by a certified Microsoft partner and available through Microsoft's marketplace. It covers a specific system or category of integration and updates with the Business Central platform. A custom integration is built specifically for the organization's requirements when AppSource does not cover them. Custom integrations offer more flexibility but require more upfront development and ongoing maintenance. For most common third-party systems, AppSource is the faster and lower-risk starting point.

How do we handle integration errors when data does not sync correctly?

A well-designed integration includes error logging, alerting and a defined process for handling failed transactions. When a record fails to sync, the integration should log the failure with enough detail to identify the cause, alert the appropriate person and either retry automatically or queue the record for manual review. Integrations without error handling make problems invisible until they become reconciliation failures.

Can Business Central integrate with our legacy or proprietary system?

Yes, in most cases. Business Central's REST API supports integration with virtually any system that can make HTTP requests or accept data through a connector. Legacy systems that cannot connect via API can often integrate through file-based methods, though that approach requires more careful design to handle timing, error handling and data validation correctly. TMC has experience integrating Business Central with a wide range of systems including proprietary databases, legacy ERP platforms and industry-specific applications.

Should we build integrations during implementation or after go-live?

During implementation whenever possible. Integration requirements affect system configuration decisions, data migration scope and go-live timing. Discovering that an integration is needed after go-live often means reconfiguring something that was already built, which adds cost and disruption. Including integration requirements in the implementation scope from the start produces better outcomes and lower total cost than treating integrations as a post-go-live project.