Exact Outage History

Started Apr 01, 2026, 11:02 AM UTC· resolved Apr 03, 2026, 07:28 AM UTC

1. investigating Apr 01, 2026, 11:02 AM UTC

   You may experience that the custom fields on the client card cannot be edited. Depending on the format of the field, the answer is greyed out or the answer selection will not be saved. We are investigating this issue, and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. resolved Apr 03, 2026, 07:28 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

Read the full incident report →

Started Apr 01, 2026, 08:47 AM UTC· resolved Apr 03, 2026, 07:50 AM UTC

1. investigating Apr 01, 2026, 08:47 AM UTC

   You may experience an issue with the calculation of the actual return in an 2025 income tax return. Foreign withholding tax is not taken into account when calculating the actual return. We are investigating this issue and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. resolved Apr 03, 2026, 07:50 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

Read the full incident report →

Started Apr 01, 2026, 08:44 AM UTC· resolved Apr 07, 2026, 07:27 AM UTC

1. investigating Apr 01, 2026, 08:44 AM UTC

   You may experience that the delivery address is not visible on the purchase order or delivery note for dropshipment orders. We are investigating this issue, and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. identified Apr 01, 2026, 12:35 PM UTC

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

3. resolved Apr 07, 2026, 07:27 AM UTC

   This issue has been resolved and the shipping address is now displayed again. Our apologies for the inconvenience.

Read the full incident report →

Started Apr 01, 2026, 07:48 AM UTC· resolved Apr 01, 2026, 09:25 AM UTC

1. investigating Apr 01, 2026, 07:48 AM UTC

   You may experience performance issues via different menupaths. We are currently investigating this issue. You can expect status updates as soon as new information is available. Our apologies for the inconvenience.

2. investigating Apr 01, 2026, 09:25 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

3. resolved Apr 01, 2026, 09:25 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

Read the full incident report →

Started Apr 01, 2026, 06:10 AM UTC· resolved Apr 01, 2026, 07:54 AM UTC

1. investigating Apr 01, 2026, 06:10 AM UTC

   You may experience that not all options are available when creating or editing a project in Exact Bouw. This includes, but is not limited to, categories, statuses, and custom attributes. We are investigating the issue and will and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. resolved Apr 01, 2026, 07:54 AM UTC

   This issue has been resolved. All fields are working as intended again when creating or editing a project. Our apologies for the inconvenience.

Read the full incident report →

Started Mar 31, 2026, 07:53 AM UTC· resolved Mar 31, 2026, 01:15 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 30, 2026, 10:26 AM UTC· resolved Apr 01, 2026, 08:00 AM UTC

1. investigating Mar 30, 2026, 10:26 AM UTC

   You may experience that on the distribution page of the 2025 income tax return, an amount to be received is displayed as an amount to be paid at "Te betalen of terug te krijgen inkomstenbelasting en volksverzekeringen” because the - sign is missing. If the amount is inconsistent on this page, you can verify whether it concerns an amount to be paid or to be received on the overview page. We are investigating this issue and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. resolved Apr 01, 2026, 08:00 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

Read the full incident report →

Started Mar 30, 2026, 08:33 AM UTC· resolved Mar 30, 2026, 10:41 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Mar 25, 2026, 03:47 PM UTC· resolved Jun 15, 2026, 07:12 AM UTC

1. investigating Mar 25, 2026, 03:47 PM UTC

   You may experience errors in Multivers Online stating the memory use has been exceeded (Geheugengebruik overschreden). We are investigating this issue. Our apologies for the inconvenience.

2. investigating Apr 01, 2026, 04:59 AM UTC

   We are continuing to investigate this issue.

3. monitoring Apr 15, 2026, 12:36 PM UTC

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

4. identified May 05, 2026, 11:26 AM UTC

   A fix has been deployed to mitigate issues regarding memory exceeded errors but has not delivered the required results. We are still investigating and working on mitigating the issue. Our apologies for the inconvenience.

5. identified May 20, 2026, 08:13 AM UTC

   We are continuing to investigate this issue.

6. identified May 26, 2026, 01:35 PM UTC

   We are continuing to investigate this issue.

7. resolved Jun 15, 2026, 07:12 AM UTC

   The issue has been resolved. The configuration has been optimized, and new instances of this issue will no longer occur. Please note that you may still experience this issue with existing cases. If you have an open support case regarding this matter, we will keep you updated via the existing ticket. If you do not have an open support case and are currently still experiencing this issue, please contact the support department.

Read the full incident report →

Started Mar 25, 2026, 03:45 PM UTC· resolved Apr 17, 2026, 03:03 PM UTC

1. investigating Mar 25, 2026, 03:45 PM UTC

   You may experience slowness when working in Multivers Online. We are investigating this issue. Our apologies for the inconvenience.

2. investigating Apr 01, 2026, 04:59 AM UTC

   We are continuing to investigate this issue.

3. resolved Apr 17, 2026, 03:03 PM UTC

   The environment has been optimized to improve performance. Customers who are still experiencing performance issues have been informed that they will be contacted personally. Our apologies for the inconvenience.

Read the full incident report →

Started Mar 25, 2026, 03:43 PM UTC· resolved Apr 01, 2026, 08:00 AM UTC

1. investigating Mar 25, 2026, 03:43 PM UTC

   You are currently unable to select the option 'Maximering van het lage tarief tot € 30.000 toepassen' with a 17% addition if you declare private use of a car in the calculation of taxable profit in an income tax (W) 2025. We are investigating this issue, and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. resolved Apr 01, 2026, 08:00 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

Read the full incident report →

Started Mar 25, 2026, 10:37 AM UTC· resolved Apr 01, 2026, 08:08 AM UTC

1. identified Mar 25, 2026, 10:37 AM UTC

   You may experience an issue with the calculation of real estate in Box 3 when actual return is enabled which results in an incorrect calculated actual return. In some scenarios, the value at 31‑12‑2025 is not included in the specification (calculator) of the real estate, which causes the system to calculate a negative actual return equal to the starting value of the residential property. The actual return specification on the overview page of the return will also display an incorrect lower actual return. We have identified the issue and are working on implementing a fix. We will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. resolved Apr 01, 2026, 08:08 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

Read the full incident report →

Started Mar 24, 2026, 02:38 PM UTC· resolved Apr 01, 2026, 01:19 PM UTC

1. investigating Mar 24, 2026, 02:38 PM UTC

   As of the 23th of March sent Peppol invoices can return the status “Error” in the overview “electronic invoicing service”. These invoices are not sent to the debtor. We are investigating this issue and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. identified Mar 27, 2026, 09:13 AM UTC

   The issue has been identified and a fix is being implemented. Current workaround is to set a "E-invoicing type identifier" and a "E-invoicing identifier" in the debtor maintenance. After setting this identifier new invoices will be processed correctly. Our apologies for the inconvenience.

3. resolved Apr 01, 2026, 01:19 PM UTC

   A change in the software has been made. When no E-invoicing type identifier is defined for a debtor, the software will now default to the identifier 0208. This change is included in Globe+ release 506SP5 and 505SP12. For Exact Globe Next the change is available in release 424SP46 downloaded after the 1st of April 11:00 hours CET. Our apologies for the inconvenience.

Read the full incident report →

Started Mar 21, 2026, 06:50 AM UTC· resolved Apr 24, 2026, 08:18 AM UTC

1. identified Feb 23, 2026, 10:47 AM UTC

   You are currently unable to send declarations to "De Eendracht" through the post office (postkantoor). This concerns the Social Fund for Industrial Bakeries, Social fund for Recreation and Social fund for Confectionary. We have identified the issue and are working on a fix. Our apologies for the inconvenience.

2. identified Mar 21, 2026, 06:50 AM UTC

   We are still working on releasing the pension declaration for "De Eendracht" as soon as possible. In the meantime, we are coordinating with De Eendracht to resolve this situation with as little adverse impact as possible. We will update this page as soon as more information becomes available.

3. identified Apr 13, 2026, 02:27 PM UTC

   We are still working on releasing the pension declaration for "De Eendracht".

4. monitoring Apr 18, 2026, 05:45 AM UTC

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

5. resolved Apr 24, 2026, 08:18 AM UTC

   This issue has been resolved. You can send the pension declaration to "De Eendracht" as of today. Our apologies for the inconvenience.

Read the full incident report →

Started Mar 09, 2026, 08:55 AM UTC· resolved Apr 15, 2026, 07:50 AM UTC

1. investigating Mar 09, 2026, 08:55 AM UTC

   You may experience that the automatic distribution is not calculated optimally. If Box 2 and/or Box 3 income is present, you cannot use the automatic distribution. We advise you to manually allocate the income. We are investigating this issue, and we will update this page as soon as more information becomes available. Our apologies for the inconvenience. Het kan voorkomen dat de automatische verdeling niet optimaal wordt berekend. Daarnaast kun je bij de aanwezigheid van box 2 en/of box 3 inkomen nog geen gebruik maken van de automatische verdeling. Wij adviseren voor nu om de verdeling handmatig toe te passen. We onderzoeken dit issue en zullen deze pagina bijwerken zodra er meer informatie beschikbaar is. Onze excuses voor het ongemak.

2. identified Mar 17, 2026, 09:48 AM UTC

   We are currently working on a solution. For this reason, automatic distribution has been temporarily disabled for all situations in the 2025 income tax return. We will update this page as soon as more information is available. We werken momenteel aan een oplossing. Om die reden is de automatische verdeling voor nu uitgeschakeld voor alle situaties in de aangifte inkomstenbelasting van 2025. We zullen deze pagina bijwerken zodra er meer informatie beschikbaar is.

3. monitoring Mar 20, 2026, 09:08 AM UTC

   We have implemented a fix and the automatic distribution has been enabled if only a Box 1 income is present. If Box 2 and/or Box 3 income is present, you cannot yet use the automatic distribution. You can manually allocate the income. We will update this page as soon as further information becomes available. We hebben een oplossing geïmplementeerd en de automatische verdeling is nu mogelijk als er alleen inkomsten uit Box 1 aanwezig zijn. Als er inkomsten uit Box 2 en/of Box 3 aanwezig zijn, kan je de automatische verdeling nog niet gebruiken. Voor deze situaties kan je voor nu de verdeling handmatig toepassen. We zullen deze pagina bijwerken zodra er meer informatie beschikbaar is.

4. monitoring Apr 01, 2026, 10:32 AM UTC

   It is now possible to apply the automatic distribution if there is Box 1 income and/or Box 3 income below the tax-free allowance. If Box 2 income and/or Box 3 income above the tax-free allowance is present, you cannot use the automatic distribution. In these situations, we advise you to manually allocate the income. We will update this page as soon as further information becomes available. Het is nu mogelijk om de automatische verdeling toe te passen als er Box 1 inkomen is en/of Box 3 inkomen onder het heffingsvrije vermogen. Als er Box 2 inkomen en/of Box 3 inkomen boven het heffingsvrije vermogen aanwezig is, kan je de automatische verdeling nog niet gebruiken. Voor deze situaties kan je voor nu de verdeling handmatig toepassen. We zullen deze pagina bijwerken zodra er meer informatie beschikbaar is.

5. monitoring Apr 07, 2026, 10:14 AM UTC

   Due to an issue in our software the automatic distribution in the 2025 income tax return may not have been calculated optimally. To ensure that your clients always receive the best possible outcome, we advise checking the tax returns where automatic distribution was applied between March 2 and March 16. It may be possible that a tax return was created before March 2 or submitted after March 16, but that the automatic distribution was applied between March 2 and March 16. On the page overview “werkvoorraad”, you can adjust the filters on the left side, “opgaaftype > IB” and “opgavenjaar 2025” and make an export via the icon with the two arrows in the top right of the page. The Partner Last Name (O) column shows which tax returns include a partner. If after checking it appears that a more favorable allocation is possible, you can resubmit the tax return. We will update this page as soon as further information becomes available. Door een issue in onze software begin maart kan in enkele uitzonderlijke gevallen mogelijk de automatische verdeling in de inkomstenbelasting 2025 niet optimaal zijn uitgevoerd. Om te garanderen dat jouw cliënten altijd de best mogelijke uitkomst ontvangen, adviseren we om de aangiften te controleren waarbij tussen 2 en 16 maart automatisch een verdeling is toegepast. Het kan zijn dat een aangifte eerder dan 2 maart is aangemaakt of na 16 maart is verstuurd, maar dat de automatische verdeling wel tussen 2 en 16 maart is toegepast. In het tabblad Werkvoorraad kun je de filtering links aanpassen voor IB 2025 en rechtsboven eenvoudig een export maken. De Kolom Partner Achternaam (O) laat zien bij welke aangiften er een Partner aanwezig is. Blijkt na controle dat een gunstigere verdeling mogelijk is, dan kun je de aangifte opnieuw indienen. We zullen deze pagina bijwerken zodra er meer informatie beschikbaar is.

6. resolved Apr 15, 2026, 07:50 AM UTC

   Due to an issue in our software the automatic distribution in the 2025 income tax return may not have been calculated optimally. We advise you to check the 2025 income tax returns which are automatically distributed between March 2 and March 16, 2026. For more information, see the update below from April 7. Our apologies for the inconvenience. Een issue in onze software heeft in uitzonderlijke gevallen invloed gehad op de automatische verdeling. Deze situatie heeft uitsluitend betrekking op IB‑aangiftes 2025. Wij adviseren automatisch verdeelde aangiftes die je tussen 2 en 16 maart 2026 hebt verdeeld te controleren. Voor meer informatie zie de update hieronder van 7 april. Onze excuses voor het ongemak.

Read the full incident report →

Started Feb 24, 2026, 10:04 AM UTC· resolved Apr 28, 2026, 07:49 AM UTC

1. investigating Feb 24, 2026, 10:04 AM UTC

   You are currently unable to establish a connection between Exact Audition and Multiverse Offline. When creating the connection, you can select an entity. After selecting the entity, nothing happens and you will not receive an error message. As a workaround, you can manually import an Auditfile or .CSV file. We are investigating this issue and we will update this page as soon as more information becomes available. Our apologies for the inconvenience.

2. identified Mar 09, 2026, 09:03 AM UTC

   This issue has been identified, and a fix is being implemented. If you encounter this issue and have not yet reported it through a support request, we advise you to report it in a support request.

3. monitoring Apr 13, 2026, 01:12 PM UTC

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

4. resolved Apr 28, 2026, 07:49 AM UTC

   This issue has been resolved. Our apologies for the inconvenience.

Read the full incident report →

Started Feb 16, 2026, 07:36 AM UTC· resolved Jun 15, 2026, 08:21 AM UTC

1. investigating Jan 22, 2026, 10:38 AM UTC

   The employment conditions groups linked to APG are not updated for 2026 yet and will not be updated in time for the calculation deadlines for the first payroll period. This affects the following employment conditions groups: ‘NL-0301a/b Bouw & Infra ‘, ‘NL-0302a/b Hellende daken’, ‘NL-0601 Timmerindustrie’, ‘NL-1801 Schoonmaak- en Glazenwassersbedrijf’, ‘NL-4501 Woondienst’, ‘NL-5701a/b Afbouw’, ‘NL-5801a/b Bitumineuze en Kunststof Dakbedekkingsbedrijven’ and ‘NL-6001 Natuursteen Vakwerkbedrijven in de Bedrijfstak’. Please be aware that you can calculate and finalize the first payroll period of 2026 with the current settings, which are still based on the 2025 pension schemes. If you choose to proceed with processing the first payroll period of 2026 with the current settings, you will need to correct retroactively with the new pension settings after the employment conditions groups are updated. In that case refrain from sending in the pension declaration for the first payroll period until further notice. Be aware that the retroactive correction will cause a lower net amount to be paid to the employees in the second payroll period. The tax settings are up to date for all employment conditions groups. Processing the first payroll period with the current settings has limited impact on the tax declaration, which will be corrected automatically in the next payroll tax declaration after the retroactive correction. We are working on updating the employment conditions groups as soon as possible. This page will be updated when new information becomes available. Our apologies for the inconvenience.

2. investigating Feb 13, 2026, 08:56 AM UTC

   We are still working on making these employment condition groups available as soon as possible. This page will be updated when new information becomes available. Our apologies for the inconvenience.

3. identified Feb 16, 2026, 07:36 AM UTC

   The following employment conditions groups have been released and will follow the calculation rules for 2026: - ‘NL-0301a/b Bouw’, - ‘NL-0302a/b Hellende daken’, - ‘NL-0601 Timmerindustrie’, - ‘NL-5701a/b Afbouw’, - ‘NL-5801a/b Bitumineuze en Kunststof Dakbedekkingsbedrijven’ and - ‘NL-6001 Natuursteen Vakwerkbedrijven in de Bedrijfstak’. To calculate retroactively with the correct settings, make a correction request via [employees > payroll > correction requests] with start date 1-1-2026. A recalculation will then take place in the next payroll calculation. In case you calculated period 1 with the 2025 settings, you may notice counter entries of the originally used payroll components. The following employment conditions groups are still under maintenance and awaiting release: ‘NL-1801 Schoonmaak- en Glazenwassersbedrijf’ and ‘NL-4501 Woondienst’. We will update this page as soon as more information is available.

4. identified Feb 26, 2026, 02:34 PM UTC

   We are still working on releasing the remaining employment condition groups as soon as possible. In the meantime, we are in consultation with APG to resolve this situation with as little adverse impact as possible. We will update this page as soon as more information is available.

5. identified Mar 16, 2026, 02:32 PM UTC

   Employment conditions group ‘NL-1801 Schoonmaak- en Glazenwassersbedrijf’ has been released and is now following calculation rules for 2026. To calculate retroactively with the correct settings, create a correction request via [employees > payroll > correction requests] with start date 1-1-2026. A recalculation will then take place in the next payroll calculation. In case you calculated period 1 and 2 with the 2025 settings, you may notice counter entries of the originally used payroll components. For all pension declarations sent to APG (also including employment conditions groups that were released earlier), please be informed you might get processable errors (NL: verwerkbare fouten). Declarations are being accepted while indicating potential issues. These known alerts are being discussed with APG and you can proceed with the submission of your pension declarations as normal. APG is reviewing these signals and, once declarations have been processed, will consult with Exact to determine whether any adjustments are necessary. In case you encounter unprocessable errors (NL: onverwerkbare fouten), do not hesitate to reach out to our support department. This page will be updated as soon as more information becomes available.

6. identified Apr 09, 2026, 03:02 PM UTC

   In consultation with APG, it has been agreed that the product hours are the determining factor; however, this is currently causing discrepancies resulting in processable error messages (NL: verwerkbare fouten). We are working to correct this in the pension declaration as soon as possible. The invoices sent by APG ex officio (NL: ambsthalve nota's) concern the expected pension premiums for the first periods, which you are required to pay. This page will be updated when we release the corrected pension declaration. Subsequent submissions may result in (limited) corrections and will be settled through new invoices. There is currently an issue in Exact Online that causes an unprocessable error. This occurs only when employees who have reached retirement age are included in the payroll. For these employees, certain mandatory contributions are not calculated, and as a result, they are not correctly included in the pension report. We are working on a solution.

7. identified May 20, 2026, 01:37 PM UTC

   You may have experienced errors on your pension declaration. We have identified 3 known issues in these reports: - Employees with leave When you calculate employees which have sick or wazo leave in a period you have to take extra steps. Go to the employeecard > open the employee specific components > find Productloon (or in case of Schoonmaak ecg: Productloon Schoonmaak) > fill in a historical hourly wage. If you have missed these steps previously you might have encountered errors regarding hourly wages being too low. In that case you can correct this retroactively by taking these steps and creating a correction request. This correction will take place in your next calculation and then in next declaration. - 4 – weekly payment When you use a 4 weekly payment you might have encountered errors regarding an incorrect ‘Premiegrondslag’ or ‘Premie’. This can be corrected by creating a correction request per the first of your payroll year. This correction will take place in your next calculation and then in next declaration. - Edited components When using edited component regarding your pension and related funds you might run into various errors. We cannot update edited components which might result in you using old settings regarding the calculation, ‘regelingkenmerk’ and other declaration settings. You can find these edited components and deactivate them by entering an end date in the previous payroll year with the following steps: Master Data > HR > Employment conditions groups > Open your ecg > Monitor > Components > use filter: Created by user > Open the edited components > Edit. Then you can correct your declaration by creating a correction request per the first of your payroll year. This correction will take place in your next calculation and then in next declaration.

8. resolved Jun 15, 2026, 08:21 AM UTC

   The known errors regarding APG declarations are resolved. If you encounter issues still, make sure to follow the steps already mentioned. Our apologies for the inconvenience.

Read the full incident report →