Exact System Status

Identified: The issue has been identified and a fix is being implemented.

Investigating: You may get an Oops error when manually importing bank statements in Exact Online. We are investigating the issue. Our apologies for the inconvenience.

Identified: You may experience that the UBO's of your company are not filled in correctly when starting the Company screening in your company. We have identified the issue and we are investigating possible solutions. In the meantime, you can change the UBO's manually, but that may require additional verification by our Compliance department. If this is the case, we will reach out to you with further information and instructions. We will update this page as soon as more information becomes available. Our apologies for the inconvenience.

Resolved: This issue has been resolved. All BNP statements have been delivered by Codabox. Our apologies for the inconvenience.

Investigating: You may experience a delay in the Codabox bank statements for BNP. Codabox is currently investigating this issue. Our apologies for the inconvenience.

Identified: The issue is caused by reference fields in the subject of the e-mail text layout. To work around the issue, you can copy your e-mail text layout and remove the reference fields in the subject. When you leave the subject entirely empty you do get a reference number without extra characters as email subject. In the meantime we are working on a structural fix. As soon as the issue has been resolved, you can switch back to your original e-mail text layout.

Investigating: It is possible that the e-mail subject has ‘& #160;’ in it when sending documents from Exact Online. This includes, but is not limited to invoices, quotations, sales orders, purchase orders, delivery notes and shop orders. We are investigating the issue. This page will be updated once more information becomes available. Our apologies for the inconvenience.

Resolved: This issue has been resolved and the screening can now be completed in full. If the white screen still appears, it may help to refresh the session by logging out and logging back in, and then trying again. Our apologies for the inconvenience.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: When trying to confirm the company screening a 503 error or white screen is shown. We are working on a solution. Our apologies for the inconvenience.

Resolved: This issue has been resolved. All BNP statements have been delivered by Codabox. Our apologies for the inconvenience.

Investigating: You may experience a delay in the Codabox bank statements for BNP. Codabox is currently investigating this issue. Our apologies for the inconvenience.

Identified: The issue is caused by reference fields in the subject of the e-mail text layout. To work around the issue, you can copy your e-mail text layout and remove the reference fields in the subject. When you leave the subject entirely empty you do get a reference number without extra characters as email subject. In the meantime we are working on a structural fix. As soon as the issue has been resolved, you can switch back to your original e-mail text layout.

Investigating: It is possible that the e-mail subject has ‘& #160;’ in it when sending documents from Exact Online. This includes, but is not limited to invoices, quotations, sales orders, purchase orders, delivery notes and shop orders. We are investigating the issue. This page will be updated once more information becomes available. Our apologies for the inconvenience.

Resolved: The issue has been resolved. Exact Online Premium is available again. Our apologies for the inconvenience.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: Currently you may experience performance issues or a message ‘Login page not available’ in Exact Online Premium. We are investigating the issue. Our apologies for the inconvenience.

Resolved: This issue has been resolved and the screening can now be completed in full. If the white screen still appears, it may help to refresh the session by logging out and logging back in, and then trying again. Our apologies for the inconvenience.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: When trying to confirm the company screening a 503 error or white screen is shown. We are working on a solution. Our apologies for the inconvenience.

Resolved: The issues in the calculation have been fixed. To calculate retroactively with the correct calculation, create a correction request via [employees > payroll > correction requests] with start date 1-1-2025. A recalculation will then take place in the next payroll calculation. Our apologies for the inconvenience.

Identified: The issue has been identified and a fix is being implemented.

Investigating: In employment conditions group NL-2201 Binnenscheepvaart, the irregularity allowance ("onregelmatigheidstoeslag") is calculated over the hourly rate instead of the gross salary. We are working on a solution. Our apologies for the inconvenience.

Identified: The issue has been identified and a fix is being implemented.

Investigating: The supplementary payment for additional birth leave (Aanvulling uitkering aanvullend geboorteverlof) is currently being paid at the wrong rate for percentages higher than 70% and lower than 100%. We are working on a solution. Our apologies for the inconvenience.

Investigating: In employment conditions group NL-1001 Metalektro, the minimum holiday is pay not updated in the pensionable salary calculation. For employees eligible for the minimum holiday pay, the pensionable salary is therefore too low. We are working on a solution. Our apologies for the inconvenience.

Resolved: The issues in the calculation have been fixed. To calculate retroactively with the correct calculation, create a correction request via [employees > payroll > correction requests] with start date 1-1-2025. A recalculation will then take place in the next payroll calculation. Our apologies for the inconvenience.

Identified: The issue has been identified and a fix is being implemented.

Investigating: In employment conditions group NL-3301 Horeca- en Aanverwante Bedrijf, the HOP premium base should be calculated over the social security wage before pension calculation and not be influenced by the pension premium. We are working on a solution. Our apologies for the inconvenience.

Resolved: This issue has been resolved by the Tax Authority and it is now possible to retrieve the VIA data again. Our apologies for the inconvenience.

Identified: To clarify, this issue has been identified and the Tax authorities are working on a fix from their side. Once we have more information we will update this page.

Investigating: The Tax Authority (Belastingdienst) currently has an issue making it impossible to retrieve VIA-data. They are working on a solution. We will inform you when an update is available. Our apologies for the inconvenience.

Identified: We are continuing to work on a fix for this issue.

Identified: The Tax Authority (Belastingdienst) currently has an issue making it impossible to retrieve VIA-data. They are working on a solution. We will inform you when an update is available. Our apologies for the inconvenience.

Resolved: This issue has been resolved. Eliminations are saved in the consolidation statement again in the Annual Report. Our apologies for the inconvenience.

Investigating: We are continuing to investigate this issue.

Investigating: You may encounter that eliminations created in the consolidation statement are not saved in an Annual Report. This issue does not affect the Annual Report (New). We are investigating this issue and will update this page as soon as more information is available. Our apologies for the inconvenience.

Identified: The issue has been identified and a fix is being implemented.

Investigating: You may experience that the API links for linked clients are revoked. You are able to restore these links. We are currently investigating the cause of this issue. When an update is available, we will inform you. Our apologies for the inconvenience.

Identified: The issue has been identified and a fix is being implemented.

Investigating: Bank import files which are loaded in via KNAB 1.0 bank account connections are not being processed correctly. This results in an import failure status, and no transactions are loading in. For now, you could already process entries and invoices linking them to the related bank transactions when a solution is communicated. When an update is available, we will inform you. Our apologies for inconvenience.