An overview of the most important new functionality, changes and resolved issues in ValidSign between 9 and 23 September 2026.
New functionality
The table below lists the new functionality that becomes available with this release.
| Functionality | Component | Description |
|---|---|---|
| Sent reminders in the evidence document | PLATFORM Admin / Sender |
A new account setting includes sent reminders in the evidence document. For each reminder the date, time and recipient are recorded in the audit trail, so it is demonstrable when a signer was reminded. |
| Signature type shown in the evidence document | PLATFORM All users |
The evidence document now states, per signature, which type was used. A qualified electronic signature (QES) via the Token Reader or a qualified cloud certificate is thereby clearly distinguishable from a click signature, including the identity from the certificate and the issuing trust service provider. |
| Field validation on text fields (IBAN) | PLATFORM Admin / Sender / API |
A validation type can be attached to a text field. The first built-in validation is the Dutch IBAN (check digits and 11-test). A signer can only confirm the field once the input is valid. The available validation types can be retrieved via the API, so new types become available automatically. |
Changed functionality
The table below lists existing functionality that has been changed in this release.
| Change | Component | Description |
|---|---|---|
| Mandatory two-factor authentication once per 24 hours | PLATFORM All users |
Before: with mandatory two-factor authentication a code was requested at every login. Now: per user-and-device combination the code is requested at most once every 24 hours. Environments with mandatory SSO are unchanged. |
| Accept only per recipient | FRONTEND Admin / Sender |
Before: the “Accept only” option in the designer applied to the whole document, so all recipients either signed or only accepted. Now: the option applies only to the selected recipient. One recipient can accept a document without a signature while a subsequent recipient signs the same document. |
Bug fixes
The table below lists the issues resolved in this period.
| Subject | Component | Description |
|---|---|---|
| Signature date in the wrong time zone | PLATFORM | The date and time stamped next to the signature on the document ignored the transaction's time zone and showed UTC. Around midnight the document could therefore show the previous day while the evidence document showed the correct date. Both now show local time. |
| Group member could not sign from another sub-account | PLATFORM | A transaction sent to a group could be opened from another sub-account, but signing returned “User not authorized for this recipient”. Group members can now sign from any sub-account they have access to. |
| Automatic provisioning to a specific account | PLATFORM | When logging in via SSO, new users were not always created in the configured account. This has been corrected. |
| Token Reader detects the operating system more reliably | PLATFORM | The Token Reader only recognised a fixed list of operating system names. On Windows Server and newer macOS versions, among others, this led to an unclear error. The operating system and version are now detected correctly. |
| Shared templates visible in sub-accounts | PLATFORM | Templates marked as shared in a parent account also appeared in the template list of sub-accounts and produced an error when used. Sub-accounts now only show their own templates. |
| Stale profile details in drafts and templates | PLATFORM | After a change to a signer's organisation, function, first name or language in their profile, the old details remained in draft transactions and templates. They are now resolved again. |
| “Pending” status in user management | PLATFORM | The user overview showed “Pending” for senders who were already active. The status is now displayed correctly. |
| Wording of the signer-changed email | PLATFORM | The email sent when a signer transfers their responsibilities always used the possessive pronoun “his” (Dutch “zijn”) and the term “ValidTransaction™”. The text has been made gender-neutral and the term has been replaced. |
| Clearing a date field caused an error | PLATFORM | When a signer cleared a filled date field, the server returned an error and the old value remained without any message. Conditional logic on “field is empty” therefore stopped working once the field had been filled. An optional date field can now simply be cleared and the logic is re-evaluated. |
| Radio button “not selected” in conditional logic | PLATFORM | A condition on “radio button is not selected” no longer became true once the group had been touched. After switching to another option the condition is now re-applied correctly. |
| Signing screen not updated after a radio button choice | PLATFORM | When choosing an option without conditions of its own, the conditions of the other options were reverted, but the server reported that nothing had changed. The signing screen therefore remained stale. The changes are now fully reported. |
| Complementary conditions wrongly rejected | PLATFORM | The combination “if empty then disable” and “if filled then required” on the same field was rejected as a conflict, although both can never apply at the same time. Such complementary conditions are now accepted. |
| Contradictory actions on one field | PLATFORM | Two contradictory actions on the same target field (for example enable and disable on the same condition) were saved without warning and applied arbitrarily. This is now handled consistently and flagged on save. |
| Text-tag extraction with mixed approvals | PLATFORM | With text tags containing both a signature and form fields in one approval, the signature took the position of the first form field and form fields could be dropped when approvals were split. Extraction now places all fields correctly. |
| SSO users and password expiry | PLATFORM | Before: users logging in via SSO/SAML wrongly received a “password expired” email and were blocked at login with a request to set a new password. Now: SSO users are excluded from the local password policy and simply log in via their own identity provider. |
| Signing in Safari inside an iframe | FRONTEND | When a customer embedded the signing ceremony in an iframe on their own website, filling in fields and signing failed in Safari with an error. The required cookies are now set so that Safari also accepts them inside an iframe. |
| Date field in the wrong format while signing | FRONTEND | While filling in, a date field with the format dd-MMM-yyyy showed a weekday abbreviation instead of the day of the month (for example “Fr-Aug-2026”). The signed document was correct. The signing screen now uses the same format. |
| Header covering the document on mobile signing | FRONTEND | On a mobile phone the fixed header slid up along with the on-screen keyboard, hiding the document and the field being filled in. This has been resolved. |
| Date stamp showed minutes instead of month | FRONTEND | In the signing ceremony the automatic date field next to the signature showed the minutes in the month position (for example “11-58-2026” instead of “11-09-2026”). The signed document was correct. The rendering has been corrected. |
| Invisible loading overlay in the Designer | FRONTEND | After opening the Designer, an invisible loading layer covered the document for about 50 seconds, so placed fields disappeared without any message. The loading layer no longer blocks field placement. |
