ValidSign
Release notes

ValidSign release notes - 23 to 30 September 2026

New functionality, changes and bug fixes in ValidSign between 23 and 30 September 2026.

2 min readLast updated: 2026-09-30

An overview of the most important new functionality, changes and resolved issues in ValidSign between 23 and 30 September 2026.


New functionality

The table below lists the new functionality that becomes available with this release.

FunctionalityComponentDescription
Archive Manager: archive documents from within ValidSign PLATFORM

Admin / Sender
For accounts with the Archive Module, archiving is now available directly within the existing ValidSign environment, using the same login and visible to users with the “transaction.archive” permission. You compose an archive request based on scope (your own transactions, or an organisation/department), status (completed, archived, trash, drafts, declined, expired) and period, and review the selection before confirming the request. The request is processed automatically and immediately into a single ZIP file per request, containing the signed documents and evidence summary per transaction, with a clear file and folder structure and a bundled CSV export; transient failures are retried automatically. The dashboard shows the status of running and completed requests, and the archives ready to download; a ready archive stays available for 30 days.

Changed functionality

The table below lists existing functionality that has been changed in this release.

ChangeComponentDescription
Bulk send limit PLATFORM

Admin / Sender
Before: a bulk send was capped at 200 transactions, because synchronous processing risked a timeout for larger batches.
Now: bulk sends are processed asynchronously, so the 200-transaction cap has been removed. A mailing to, for example, 1,000 recipients no longer needs to be split up manually.
iDIN with itsme branding FRONTEND

All users
Before: the iDIN screen used the old look.
Now: the iDIN screen follows the new guidelines (iDIN x itsme), with a new logo, itsme link and adjusted bank selection.

Bug fixes

The table below lists the issues resolved in this period.

SubjectComponentDescription
SSO in the Word Add-in PLATFORM For organisations that restrict SSO access, logging in via SSO did not work in the Word Add-in, preventing these users from using the Add-in. This has been fixed.
Font changes on fill-in fields in the signed PDF PLATFORM Text fields in a signed document could switch font when clicked (on focus), because the stored font reference (/DA) did not match the fonts embedded in the document (/DR). This has been corrected.
Fillable fields shown incorrectly after flattening PLATFORM When uploading a document with fillable fields, the filled-in values were sometimes shown incorrectly after flattening. This has been fixed.
Language error in the default “Transaction completed” e-mail PLATFORM The default Dutch e-mail used “bewaard” where “bewaart” was meant. This has been corrected.

Was this article helpful?

Need help?

Contact our support team

Contact us