PSP webhook should mark the invoice paid in bookkeeping, often fails.
Webhook failure typically comes from token expiry on the bookkeeping side, a temporary 5xx the PSP did not retry, or a match rule that does not connect amount to invoice.
Try this first
- 1Check the PSP dashboard webhook history, look for 4xx or 5xx responses over the last week.
- 2On 401/403 refresh the OAuth tokens for the bookkeeping link, these typically expire yearly or after a password change.
- 3On 5xx or timeout enable retries on the PSP, Mollie and Stripe support exponential-backoff retries that usually succeed.
- 4On 200 but not matched check the rule, does the package expect the invoice number in description or a custom field?
- 5Enable logging so you see per webhook which invoice it belongs to, otherwise forensics is almost impossible.
When to bring us in
If webhook failures rise above a few percent, we can log the chain end-to-end and fix it.
See also
- Switching from Exact Online to Yuki, open items and history do not matchPackage migrations stumble on ledger mapping and open AR/AP. Without a mapping table you lose context.
- Twinfield to Exact, dimensions and cost centres go missingTwinfield uses dimensions, Exact uses cost centres and projects. The mapping is not one-to-one.
- Accountant asks for RGS mapping, your ledger does not follow RGSRGS is the Dutch standard chart that SBR filings and accountant software expect. Without mapping, every year-end is manual.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.