Integrations per accounting package

Every package opens its door differently, and that decides what an integration can do.

Why the package sets the timeline

How an integration works is the same everywhere: your software signs in to the API with a key, then reads or writes data. What differs per package is everything that has to happen before a single line of code can be written.

Four things decide that. How you get a key, how many calls you are allowed per day, who inside your organisation grants access, and whether you can test without touching your live administration. Those four set the timeline more often than the integration itself does.

This page covers what applies per package. The general explanation, about the flows an integration can handle and what happens when something fails, is in the article on connecting your accounting.

The four packages side by side

All four offer a REST API with public documentation. The differences are in access and in limits.

Four packages and what their API asks, as of September 2026
Package	Access	Limit
Exact Online	Register an app in the App Center, then OAuth 2.0	60 calls per minute, 5,000 per day per app and per administration
Moneybird	Personal token for your own administration, OAuth for an app others use	150 calls per 5 minutes per IP address, 50 for reports
e-Boekhouden.nl	Create a token under Beheer, Koppelingen, API	Not published
AFAS	AppConnector token and connectors from your administrator	Not published

Testing without touching the live administration

This is where the four differ most, and in practice it is what saves the most time. Moneybird offers sandbox administrations with every feature, where invoices carry a watermark so they cannot pass as real.

The other three have no separate environment for it. A new Exact app also works only inside the environment that created it until Exact has reviewed it. What is left is testing in a second administration, or in the live one with cleanup afterwards.

So ask about it before anything is built. It decides whether trying things is cheap or expensive, and that changes how an integration is delivered.

What to check before we start

These points cost you half an hour and cost us a week otherwise. They decide whether an integration is running in two weeks or waiting on an application first.

Whose subscription holds the administration: if it sits with your accountant, your accountant grants the access
Whether API access is part of your current plan, or needs a module or a higher tier
Who is allowed to create a key or a connector inside the package, and whether that person is available
Whether the vendor reviews the integration before it can go live, and how long that takes

Sources

Frequently asked questions

Which package is fastest to connect?

Moneybird, if it is your own administration: you create the token yourself and can start the same day. AFAS needs an administrator to set up connectors first, and Exact Online reviews a new app before it may work at other customers.

Our package is not listed. Does that rule it out?

Usually not. These four are the most common, but any package with documented API can be connected. We work that out first in the intro call, because the whole plan depends on it.

Can you connect to two packages at once?

Yes. That comes up during a migration, when old and new run side by side for a while. Do agree up front which system is the source, otherwise the two administrations drift apart.

What if the vendor changes their API?

It happens, usually with notice and a transition period. On a maintenance plan we track those announcements and adjust the integration before the old version stops.