Skip to Content

Connect Medius and Izettle

Connecting Medius and Izettle for a company could enable the transfer of financial transaction data between the two systems. This could support more efficient expense tracking, invoice processing, and reconciliation of sales data. Such an integration could help reduce manual data entry and improve the accuracy of financial records across both platforms.

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

Contact us

Why connect Medius and Izettle?

A company that operates both Medius and Izettle could benefit from connecting these systems in order to streamline the flow of financial and transactional data. If a connection were established, it could reduce the need for manual data entry between the two platforms, which often leads to errors, duplicated work, and inconsistencies. Without such a connection, information such as payments, invoices, and sales records might be entered separately into each system, increasing the risk that records diverge over time or that decisions are made based on outdated or incomplete data. In environments where both systems are used, the types of data that could be exchanged include payment transactions, invoice statuses, sales data, and possibly customer information. For example, sales data captured in Izettle could be transferred to Medius for reconciliation with invoices or accounts payable processes. This exchange could help ensure that financial records remain aligned and support more accurate reporting and cash flow management. The specific data that can be shared between Medius and Izettle depends on the capabilities and limitations of each system's API, and must be evaluated on a case-by-case basis.

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 Medius 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