Skip to Content

Connect Microsoft Dynamics 365 BC and Izettle

Connecting Microsoft Dynamics 365 BC and Izettle for a business could allow transaction data captured in Izettle to be transferred into Microsoft Dynamics 365 BC for accounting or inventory management. This connection could support more accurate financial reporting and simplify reconciliation by reducing manual data entry between the two systems.

You can build this integration on the System2System platform. We design the connection between Microsoft Dynamics 365 BC and Izettle around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Microsoft Dynamics 365 BC and Izettle?

A company that uses both Microsoft Dynamics 365 BC and Izettle could benefit from connecting these systems to allow data to flow automatically between them. This connection could help ensure that sales transactions, inventory movements, and financial records are consistent across both platforms. Without such a connection, staff would need to enter the same data into each system separately, which increases the risk of errors and consumes valuable time. Over time, records in the two systems could diverge, leading to discrepancies in stock levels, sales figures, or accounting balances. This could result in decisions being made based on outdated or inaccurate information, affecting everything from cash flow management to customer service. The kinds of data that could be exchanged between systems like Microsoft Dynamics 365 BC and Izettle include sales transactions, inventory updates, customer details, and payment records. The specific data that can be exchanged depends on what each system makes available through its API and must be determined for each situation individually.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Microsoft Dynamics 365 BC and Izettle make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.

About these systems

Read more about each system and what it can be connected to

Looking to connect these systems?

Talk to us about what your setup needs. No obligation.

Contact us