Short answer
A processing error means Autoboeker could not write the booking to the ledger. The message usually names what is missing: a financial year, a payment term, a VAT code that does not fit the GL account, or rights of the connection user. Fix that in the ledger or in Autoboeker and process the document again; Autoboeker does not create a duplicate.
Key takeaways
- Read the message: it usually names the missing field or rights.
- Many errors live in the ledger: year, journal, VAT code or connection account.
- Inclusive and exclusive VAT codes with the same name cause a total mismatch.
- Authentication failed or WrongDivision: reconnect Exact with the same user.
- After the fix you process the same document again; it counts as one booking.
What does a processing error mean?
A processing error means Autoboeker has read the document but could not write the booking to Exact Online, Twinfield, SnelStart or e-Boekhouden. Recognition is done; posting to the ledger failed. The message often includes technical details, the page and the time.
Fix what the message names first. Then process the same document again. Autoboeker does not create a second booking if the first one never landed.
Which messages appear most often?
Most messages fall into a few groups. Check those first, before you open a ticket.
| Message or symptom | Cause | What you do |
|---|---|---|
| Financial year or period closed | The ledger rejects a booking in that period | Open the year or book on an allowed date |
| Total amount does not match | Inclusive and exclusive VAT codes with the same name are both on | Switch the inclusive code off on VAT codes and process again |
| Payment term missing | The relation or administration has no payment term | Fill the term in the ledger or in Autoboeker |
| VAT code does not fit the GL account | The GL account allows a different VAT type | Pick a matching GL account or change the VAT setting in the ledger |
| Authentication failed / WrongDivision | The Exact connection expired or uses another user | Team name → Connections → Reconnect, with the connection account |
| Free text field 1 is not allowed | The Twinfield journal does not allow the free text field | Leave the field empty or change the journal in Twinfield |
| No rights to book | The connection account may not book in that administration | Give the connection account booking rights in the ledger |
How do you fix an Exact connection error?
You fix Authentication failed and WrongDivision yourself. Open the team name at the top left, choose Connections and click the refresh icon on the Exact connection. Sign in with the same Exact user as the connection account, not with your personal user. A different Exact user is rejected.
If your current Exact user cannot see some administrations, add an extra Exact connection with name and email. Disconnecting an Exact connection leaves the administrations linked in Autoboeker; you remove those by hand under Settings.
- 1Open Team name → Connections.
- 2Choose Reconnect on the right Exact connection.
- 3Sign in with the connection account, not another Exact user.
- 4Check that the administration syncs again and process the document once more.
What if the invoice total does not match?
When Autoboeker says the total does not match, an inclusive and an exclusive VAT code with the same name are often both on. Switch the inclusive code off on the VAT codes screen and process again.
Also check that subtotal, VAT and total on the document itself add up. An arithmetic error on the invoice is not fixed by switching codes; you mark it and adjust the lines until they match.
When is it not an error but a deliberate stop?
Autoboeker also stops without an error: at low confidence, a possible duplicate, a possible fixed asset, an illogical GL and VAT combination, or when a team member may not process. That is not a fault. The document stays ready for review.
A team member without the Process button has May process bookings switched off. That member submits bookings for review; a colleague who may book approves them.
FAQ
Questions about this topic.
No. If the first processing failed, there is no booking in the ledger. Processing again creates the first booking.
Not if the message, technical details and page are already visible. That text is usually enough.
No. You reconnect yourself with the firm's connection account.
Yes. Authentication failed and WrongDivision are Exact-specific; the free text field is Twinfield-specific.
No. Only a processed booking that is definitive in the ledger counts.
