Dear customer,
Last weekend we deployed a major update to the ValidSign platform. With this migration we are transitioning to a completely new signing engine. This is a necessary step to future-proof ValidSign, with better performance, higher security and new functionalities. Part of this change is the mandatory enforcement of two-factor authentication (2FA) for all accounts.
Unfortunately, this transition is causing issues for a significant number of customers with logging in, signing and the use of integrations. We deeply regret this and offer our sincere apologies.
The reality is that we currently have hundreds of reports in progress. Some have been resolved, but many issues are still open. For a number of integrations we are also dependent on our integration partners, which means the resolution time is outside our direct control.
Our team is working around the clock to resolve all reported issues as quickly as possible.
The current status and a full overview of known issues can be found at:
https://status.validsign.eu
Do you have an urgent issue? Contact us via support@validsign.eu, call +31 85 303 3676, or use the chat function on our website for direct assistance.
We understand you rely on us and thank you for your patience.
Kind regards,
John Lageman
Managing Director ValidSign
This page contains an overview of the most reported issues in the new ValidSign v2.0.0 environment. The list is based on incoming support tickets and is updated regularly.
Last update: May 25, 2026, 14:30 — 1 tickets processed today.
# | Subject | Component | Status | Impact | Reports | Expected |
|---|---|---|---|---|---|---|
1 | Signing confirmation/completion not working | Frontend | Resolved | After placing a signature or initials, the confirmation process gets stuck. The transaction cannot be completed. | — | — |
2 | Login issues after migration | Frontend | Under investigation | Users cannot log in after the migration. Password forgotten or account not recognized. Try resetting your password via the login page. Expected resolution: to be determined. | 0 | |
3 | 2FA/MFA issues | Frontend | Under investigation | Two-factor authentication is not working correctly. Users do not receive SMS codes or the authenticator app is not accepted. Contact support for a 2FA reset. | 0 | 1 |
5 | SSO connections not working | Integration | Under investigation | Single Sign-On connections (SAML/SURF) are not functioning correctly after the migration. Contact support for reconfiguration of your SSO connection. Expected resolution: to be determined. | 1 | |
6 | Template and transaction issues | Frontend | Under investigation | Templates do not correctly inherit settings (reminder schedule, recipients, radio buttons). Check settings manually after creating a transaction. Expected resolution: to be determined. | 0 | |
8 | Incorrect branding/logo applied | Frontend | Under investigation | The frontend and emails display an incorrect logo or branding. The cause is known and we are working on a fix. | 0 | |
9 | Dashboard counts and role display incorrect | Frontend | Under investigation | The counts on the dashboard and role assignments are temporarily incorrect. This does not affect actual transactions or permissions. Expected resolution: to be determined. | 0 | |
10 | ValidSign app temporarily unavailable | App | Under investigation | An update for the ValidSign app has been submitted to the Google Play Store and Apple App Store. The app will be available again once the update is approved. | 0 | |
11 | AFAS integration not working correctly | Integration | Resolved | The AFAS integration was not functioning correctly after the migration. This has been resolved. | — | — |
12 | Qualified Cloud Signing stops after QR code scan | Frontend | Resolved | The qualified cloud signing process stopped after scanning the QR code, preventing completion. This has been resolved. | — | — |
13 | No SSO button in Word Add-in | Integration | Under investigation | SSO login is temporarily unavailable in the Word Add-in. Login is temporarily only possible with username and password. Expected resolution: to be determined. | — | TBD |
14 | Cloning templates for new transaction not possible | Frontend | Resolved | Creating a new transaction based on a template was temporarily not possible. This issue has been resolved. | — | — |
15 | Transaction filter shows incorrect counts | Frontend | Under investigation | When filtering transactions, incorrect counts are displayed. The actual transactions are still correct. Expected resolution: to be determined. | — | TBD |
17 | AuditCase integration not working correctly | Integratie | Resolved | The AuditCase integration was not working correctly after the migration. This has been resolved. | — | — |
18 | BCT/MyCorsaNxt integration not working correctly | Integratie | Resolved | The BCT/MyCorsaNxt integration was not working correctly after the migration. This has been resolved. Note: SMS verification issue within this integration is still open. | — | — |
20 | External signer verification with AFAS | Integratie | Resolved | External signers could not be verified when using the AFAS integration. This has been resolved. | — | — |
21 | Auto-provisioning with SSO not working | Integratie | Under investigation | Auto-provisioning of users via SSO is not working correctly after the migration. Expected resolution: 29 May 2026. | — | 29 May 2026 |
22 | Salesforce integration not working | Integration | In progress | The Salesforce integration was not working correctly after the migration. This has been resolved. Expected resolution: to be determined. | — | TBD |
23 | Microsoft Dynamics integration not working | Integration | In progress | The Microsoft Dynamics integration was not working correctly after the migration. This has been resolved. Expected resolution: to be determined. | — | TBD |
24 | FastTrack not working | Frontend | Resolved | The FastTrack functionality was not working correctly after the migration. This has been resolved. | — | — |
25 | Bulk sending not working | Frontend | In progress | The bulk sending functionality was not working correctly after the migration. This has been resolved. Expected resolution: to be determined. | — | TBD |
26 | Delegation/authorization issues | Frontend | In progress | Setting up and using delegations was not working correctly after the migration. This has been resolved. Expected resolution: to be determined. | — | TBD |
27 | Pinkweb integration | Integration | In progress | Pinkweb SBR is resolved. PDF signing: issue identified, hotfix from Pinkweb is being deployed. | — | TBD |
29 | iBabs: documents are not offered for signing | Integratie | In progress | Issue identified together with partner iBabs. All tests have passed. iBabs will deploy the fix to production tomorrow. Expected resolution: 21 May 2026. | — | — |
30 | Rx.Mission integration not working correctly | Integratie | In progress | The Rx.Mission integration is not working correctly after the migration. The issue has been identified and a fix will be deployed later today. | — | TBD |
31 | DocuFlow/Documizers integration not working | Integratie | In progress | Issues have been identified. Expected resolution: 21 May 2026. | — | 21 May 2026 |
32 | DigiOffice integration not working | Integratie | In progress | The DigiOffice integration is working in most cases. Some remaining issues are under investigation. | — | — |
33 | Djuma: document write-back not working | Integratie | Under investigation | Signed documents are not being written back to Djuma after the migration. This is being investigated. | — | TBD |
34 | Centric CLO: document write-back | Integratie | Under investigation | Signed documents are not written back to Centric CLO after the migration. Expected resolution: 22 May 2026. | — | 22 mei 2026 |
35 | Centric Burgerzaken: document write-back | Integratie | Under investigation | Signed documents are not written back to Centric Burgerzaken after the migration. Expected resolution: 22 May 2026. | — | 22 mei 2026 |
36 | XXLLNC: document write-back | Integratie | Under investigation | Signed documents are not written back to XXLLNC after the migration. Expected resolution: 22 May 2026. | — | — |
37 | Graphical signature is displayed too small | Frontend | In progress | After the migration, the graphical signature is displayed much smaller than before. | — | 27 May 2026 |
38 | Huris integration issues | Integratie | In progress | The Huris integration is not working correctly after the migration. Expected resolution: to be determined. | — | TBD |
39 | Document upload with Exact Audition issues | Integratie | Under investigation | Uploading documents via Exact Audition is not working correctly after the migration. This is being investigated. | — | TBD |
40 | TOPdesk integration issues | Integratie | In progress | The TOPdesk integration is not working correctly after the migration. | — | TBD |
41 | SMTP: customers with custom SMTP server may experience issues | Frontend | Resolved | Customers with a configured SMTP server could experience issues sending emails. Known SMTP issues have been resolved through SES routing. If you still experience issues, please create a ticket with 'SMTP' in the subject. | — | — |
42 | Reminder service: reminders are being sent incorrectly | Frontend | Under investigation | Reminder emails are being incorrectly sent for already signed or deleted transactions. The reminder service has been temporarily disabled. Priority 1. Expected resolution: 21 May 2026. | — | — |
43 | Search function for setting up delegations not working | Frontend | Resolved | The search function for setting up delegations was not working correctly. This has been resolved. | — | — |
44 | Documents are sometimes displayed in landscape | Frontend | In progress | In some cases, documents are displayed in landscape instead of portrait. | — | 22 May 2026 | — | TBD |
46 | Change signer and email delivery settings are not saved | Frontend | In progress | The toggle switches for change signer and email delivery are not being saved. A hotfix has been created and will be deployed today. | — | — |
47 | Signer SSO not working correctly | Frontend | In progress | Signer SSO currently only works if the signer has an existing ValidSign account. Signing via Signer SSO without an account is not possible. | — | TBD |
48 | Name prefixes and special characters not accepted | Frontend | Resolved | Name prefixes and special characters (such as brackets, accents) were not accepted when creating signers. This has been resolved. | — | — |
49 | Alure CRM integration not working | Integratie | Resolved | The Alure CRM integration was not working correctly after the migration. This has been resolved. | — | — |
50 | HomeCtrl integration not working | Integratie | Resolved | The HomeCtrl integration is operational and working correctly. | — | — |
This table is updated by the team based on incoming support tickets. Found an issue? Report it via support@validsign.eu.