How to connect Exact Online (NL)

Connecting Exact Online (NL) is a single action: click Authorize and sign in with your Exact Online account. There are no credentials to type or paste, and there is no region to choose — this connector is pinned to the Dutch instance, start.exactonline.nl. Apideck runs the OAuth flow and keeps the short-lived access token refreshed afterwards, so the connection keeps working without you re-entering anything.

Because the host is fixed, the one thing worth confirming before you start is that the Exact Online account you will authorize with signs in on the Dutch instance. If you sign in on a Belgian, British, German, Spanish or US domain, a different Exact Online connector is the one you want — see Troubleshooting.

Prerequisites

• An active Exact Online subscription on the Dutch instance (start.exactonline.nl).
• A user account that can authorize third-party app connections. If you are not sure whether yours can, check with your Exact Online administrator before you start.
• Switch to the target administration before you authorize. Exact Online calls a company an administration (a division in the API). A connection is anchored to exactly one of them, and the one captured is whichever administration your account is currently in at the moment you authorize. If your account has access to more than one, sign in to Exact Online and switch to the administration this connection is for first — see step 2.

1. Authorize with Exact Online

If your Exact Online account has access to more than one administration, switch to the one this connection is for before you start (see Prerequisites) — that choice is captured during this step.

1. Open the Exact Online (NL) connection in Apideck Vault and click Authorize. Vault redirects you to the Exact Online sign-in page on start.exactonline.nl.
2. Sign in with the Exact Online account this connection should use.
3. Review the access the app asks for and grant it.

You are never asked for a redirect URL, a client ID, or a client secret. Those belong to the Exact Online app registration held by the provider of the integration.

2. Your administration is detected automatically

Right after authorization, Apideck reads the current division of the account you just signed in with and stores it as the connection's default administration. You never type a division number, and there is no dropdown to fill in.

Because it is your current division that gets captured, the administration you were in when you authorized is the one now stored on the connection. If the wrong one was captured, switch administration in Exact Online and click Authorize again.

One connection can still serve several administrations, but the connection itself stays bound to the single administration captured at authorization — there is no administration picker on the connection to change that. An integration that works across several administrations can list the administrations the authorized account can reach (the Accounting companies endpoint) and target a different one per request by sending its division id in the x-apideck-company-id header. Requests without that header use the administration stored on the connection. To change which administration the connection itself defaults to, re-authorize while in that other administration.

3. Optional connection settings

None of these are required to save the connection, but two of them are needed in practice before certain records can be created.

Setting	Needed for	Notes
Purchase Journal	Creating bills (purchase invoices)	Dropdown, read live from the journals in your administration.
Bank Journal	Creating payments and bill payments	Must be an actual bank journal (Exact journal type 12), not a general or sales journal.
Balance-Sheet / Profit-and-Loss titles	Balance sheet and profit-and-loss reads on an administration that does not use the standard Dutch RGS classification titles	See the Balance Sheet and Profit and Loss configuration guide.

Without a Bank Journal, creating a payment or bill payment fails with Invalid journal. Without a Purchase Journal, bills cannot be created. Both dropdowns list every journal in your administration, so choose deliberately: the journal you pick here is the default that entries post to. An integration can override it on an individual request as an exception, so if you see entries in a journal other than the configured one, ask whoever built the integration whether it sets the journal per request.

The Balance-Sheet and Profit-and-Loss title fields only matter when your administration's first-level classification headings differ from the built-in Dutch RGS headings. Most Dutch administrations use the standard scheme, so these fields are normally left empty; the linked guide walks through reading your own headings and entering them if yours are custom.

Notes

• Token refresh is automatic. Apideck refreshes the short-lived access token for you; there is nothing to re-enter while the connection is in regular use.
• A connection left unused for 30 days needs re-authorizing. Exact expires a refresh token after 30 days without use, and each refresh replaces the previous one — they are single-use. Regular use keeps the connection alive. Restore a dormant one by opening it in Vault and clicking Authorize again.
• Payments are recorded, not reconciled. Creating a payment or bill payment writes a bank entry in the bank journal you configured. It does not match that entry against the invoice, so the invoice status does not change to paid — do the matching in Exact Online.
• This connection lives on the Dutch instance only. The authorization, the tokens behind it and the division id stored on it are all issued by start.exactonline.nl and are not valid on another country's Exact Online instance. A company that also runs administrations on another instance needs a connection on the connector for that region.
• The connection's reach is the authorizing user's reach. What it can read and write follows that Exact Online user's permissions and administration access. If their access is reduced or their account is disabled later, the connection is affected too.

Troubleshooting

My Exact Online login is rejected, or the sign-in page is not the domain I normally use. This connector only accepts accounts on the Dutch instance, start.exactonline.nl. If you sign in on start.exactonline.be, .de, .es, .co.uk or .com, ask the provider of the integration which Exact Online connector covers your region — Apideck offers a multi-region Exact Online connector and other region-pinned ones alongside this Dutch one.

Authorization completed but the connection returns another company's data. The division captured at authorization was not the one you wanted (step 2). Sign in to Exact Online, switch to the right administration, and click Authorize again on the connection.

Exact Online will not let me authorize the app at all. Two things to check, in order. First, that your user is allowed to authorize third-party app connections — your Exact Online administrator can confirm. Second, that the app has been approved by Exact for use outside the Exact instance it was registered in; until it is, only accounts on that same instance can connect. The second one is not yours to change — report it to the provider of the integration, who owns the app registration and its review.

Creating a payment or bill payment fails with Invalid journal. The Bank Journal setting is empty, or points at a journal that is not a bank journal. Open the connection, pick a bank journal from the dropdown, and save.

Bills cannot be created. Set the Purchase Journal on the connection (step 3).

The balance sheet or profit-and-loss sections look wrong or empty. Your administration's first-level classification headings differ from the built-in Dutch RGS defaults. The Balance Sheet and Profit and Loss configuration guide shows how to read your own headings and which fields to enter them in.

Requests start failing with 429. Exact meters calls per app per administration, and that budget is used up for now. Retry after the reset indicated in Exact's response — this connector passes Exact's per-minute rate-limit reset back on the response as a retry-after header — and send requests sequentially rather than in parallel. The connection itself is fine — nothing needs re-authorizing. The current limits are listed in this connector's overview.

The connection worked and later stopped. The usual causes, in order:

1. It sat unused for more than 30 days — re-authorize (see Notes).
2. The Exact Online user who authorized it lost access, or the subscription lapsed — re-authorize with an account that has the access.
3. The Exact Online app credentials behind the integration changed. That sits with the provider of the integration, not with you, and affects every connection using them — report it to them.

Still stuck? Contact Apideck Support.