Which packages and protocols we connect to

← Integrations

We connect accounting packages such as Twinfield and SnelStart, read bank statements through MT940 and speak REST, SOAP, SFTP and EDI. More important than the name of the package is whether there is an interface: an API, an export format, or a database we are allowed to reach. We establish that up front.

Updated on 28 August 2026

Packages

Twinfield

Connected for a financial services provider: pushing invoices and debtors through and keeping the bookkeeping data in step.

SnelStart

The same: retrieving and writing back data, with a SQL database underneath for automated processing.

Other accounting packages

Possible as soon as the package offers an API or a usable export format. What the supplier permits determines the route.

Webshops and order systems

A sale becomes an invoice straight away, without anyone retyping data.

TMS and logistics systems

Exchanging track and trace and order status between carrier, client and your own system.

File and message formats

MT940

The standard file banks use to deliver statements. Reading it automatically means matching payments without manual work.

CAMT.053

The XML successor to MT940. Banks still supply both; we process whatever you receive.

EDI

Message traffic between organisations, for instance between external parties and a central system over SSH and SFTP.

CSV and fixed width

The inevitable export file. Unremarkable until a field contains a semicolon — that is where the real work is.

XML and JSON

The common formats behind modern interfaces, each with their own pitfalls around dates and character sets.

Protocols and techniques

REST with JSON

The most common route to a modern package.

SOAP with XML

Still widely used by older and enterprise systems.

SFTP and SSH

For file exchange where no API is available, using keys rather than passwords.

Directly on the database

Sometimes the only way, for instance with a system that has no interface. Read-only where possible, and always in consultation with the supplier.

Scheduled export

The simplest solution that works: making data available and collecting it at fixed times.

A connection is more than the technology behind it. What finishes it is error handling, logging and monitoring: a record that does not add up is set aside and reported, and the rest carries on.

More on this →