Before you connect
- Access to the e-Boekhouden administration, to create an API token.
- An owner or admin account in Northdeck.
Connect e-Boekhouden.nl
- In Northdeck, open Data → Sources and choose e-Boekhouden.
- In e-Boekhouden, go to Settings, open API and choose e-Boekhouden API (not API/SOAP (old)).
- Create an API token.
- Paste the token in Northdeck.
- Click Connect e-Boekhouden. The first sync adds invoices, purchase invoices and the ledger to the Finance module.
Someone else holds the access? In Data → Sources, click Send an invite link: they fill in the key without a Northdeck account. The link is valid for 7 days and works once.
Keeping it up to date
Northdeck reads your accounts every night; Sync now reads them again at any time. The first sync of a large administration runs over a few hours.
Troubleshoot
The message in Northdeck says what went wrong. These are the most common ones.
e-Boekhouden did not accept the API token.
Check that you copied all of it, or create a new one under Settings, e-Boekhouden API.
The e-Boekhouden API token has expired.
Create a new one and connect again.
e-Boekhouden blocked signing in after too many tries.
Wait the minutes the message mentions, then connect again. Northdeck never retries a refused token by itself.
The e-Boekhouden token may not read this.
Create a token with access to the bookkeeping.
Good to know
- History from 1 January two years ago is read; e-Boekhouden books in euros.
- Did you import a ledger file by hand earlier? Delete it after connecting, or the ledger counts twice.
- Cost centres and bank transactions are not read yet.