Skip to Content

Connect AFAS and Izettle

Connecting AFAS and Izettle for a company could enable the transfer of sales data from Izettle to AFAS, supporting automated financial reconciliation and improved reporting. Such a connection could reduce manual entry, help maintain up-to-date financial records, and provide management with timely insights into revenue and sales performance across platforms.

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

Contact us

Why connect AFAS and Izettle?

A company running both AFAS and Izettle could benefit from connecting these systems to enable data exchange between their financial, HR, and point-of-sale operations. Without such a connection, staff may be required to enter the same sales or transaction data into both systems separately, increasing the risk of errors and consuming valuable time. This manual process can result in records that do not match between systems, leading to discrepancies in financial reporting, inventory management, and payroll calculations. Decisions based on outdated or inconsistent figures can negatively impact business planning and day-to-day operations. If a connection were established, the types of data that could be exchanged include sales transactions, payment records, inventory updates, and customer information. For example, sales processed through Izettle could be sent to AFAS for accounting and reporting purposes, and updates to product or pricing data in AFAS could be reflected in Izettle’s point-of-sale environment. The specific data that can be transferred depends on what each system makes available through its API and is determined 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 AFAS 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