Understanding the 99 Error on work orders
What is the 99 Error?
When a work order shows status "99 Error", it means the integration export failed. OutSmart attempted to push the work order data to an external system (e.g. Visma e-Accounting, e-Boekhouden or Tribe) but the export was rejected or timed out.
Why does this happen?
Common causes include:
- Missing required data — the external system expected a field (e.g. VAT number, cost centre) that was empty.
- Expired authentication token — the integration's API token has expired and needs to be re-authorised.
- API error — the external system returned an error (e.g. rate limit, server downtime).
- Data mismatch — a product code or ledger account in OutSmart does not exist in the external system.
How to resolve it
- Navigate to BackOffice > Integrations and open the integration log.
- Find the failed export entry — it will show the error message returned by the external system.
- Fix the root cause (e.g. fill in the missing data, re-authorise the token, correct the mapping).
- Return to the work order and re-trigger the export.
Preventing future 99 Errors
- Set up required-field validation so work orders cannot be completed with missing data.
- Monitor token expiry dates and re-authorise proactively.
- Review integration logs regularly.