An overview of the most important new functionality, changes and resolved issues in ValidSign between 26 August and 8 September 2026.
New functionality
The table below lists the new functionality that becomes available with this release.
| Functionality | Component | Description |
|---|---|---|
| Archive Manager | FRONTEND Admin / Sender |
A new Archive Manager is available in the Sender UI. It lets you compile an archive of completed transactions over a period of your choice and download it directly from the dashboard. |
| Hungarian language | FRONTEND All users |
Hungarian has been added as a language in both the Sender UI and the signing ceremony. It can be selected as the user's preferred language, as the transaction language, and by the signer in the language picker. |
| Captured initials in personal details | FRONTEND All users |
Under My account > Personal details you can now record handwritten initials alongside your signature. They are used for initials fields in the signing ceremony. |
Changed functionality
The table below lists existing functionality that has been changed in this release.
| Change | Component | Description |
|---|---|---|
| iDIN acquirer | PLATFORM All users |
The iDIN acquirer has been migrated to itsme®. Nothing changes functionally in the signing flow for end users. |
| Check for empty list fields before sending | PLATFORM Admin / Sender / API |
Before: a transaction containing a list field without options could be sent, leaving the signer with an empty field. Now: sending is refused with a message stating that a list field has no values, so you can add the options first. |
| Bookmarks in documents are preserved | PLATFORM All users |
Before: bookmarks were removed from a PDF on upload to keep signatures valid. Now: bookmarks remain in the document; signatures stay valid. |
Bug fixes
The table below lists the issues resolved in this period.
| Subject | Component | Description |
|---|---|---|
| Long-term validation (LTV) for qualified signatures | PLATFORM | For qualified electronic signatures (QES) via an external certificate provider, the validation data was not embedded in the PDF, so the signature could not be verified in the long term. This data is now added. |
| Text tag parent() bound fields to the wrong approval | PLATFORM | During text-tag extraction, form fields were attached to an arbitrary approval of the same signer instead of the approval given in parent(). A required field on the last page could therefore block initials on an earlier page without any visible field. Binding now follows the tag. |
| Text tag remained visible in PDF | PLATFORM | For certain PDF documents the text tag was not removed from the document and the signature was placed about 72 points below the tag. Tags are now removed correctly and fields are placed in the right position. |
| Filled date fields lost when uploading a PDF form | PLATFORM | When uploading a filled interactive PDF form with split date fields (such as the Dutch Tax Administration's payroll tax form), the filled dates disappeared and a ticked checkbox rendered as a black block. The values now remain visible. |
| ZIP file names on Windows | PLATFORM | ZIP downloads could contain a colon in a file name, which is not allowed on Windows. Extracting with the built-in Windows tool therefore failed. File names are now sanitised. |
| Evidence document timestamps in UTC | PLATFORM | Timestamps in the audit trail and the evidence document ignored the transaction's time zone and showed UTC, two hours earlier than the actual signing time. The configured time zone is now applied. |
| Attachment order in transactions created from a template | PLATFORM | When creating a transaction from a template, the requested attachments appeared in a different order than in the template for some users. The order now matches the template for all users. |
| Existing signature moved and mirrored | PLATFORM | When a previously signed PDF was uploaded again as a document, the existing signature was rendered in a different position and mirrored. The original rendering is now preserved. Note: re-offering a signed document invalidates the earlier signature legally; we advise against it. |
| Wrong captured signature in group or delegated signing | PLATFORM | When a group member or delegate completed a transaction that another signer had left open, the captured signature of the first signer was used. The signature of the actual signer is now always placed. |
| Signature rendered in black | PLATFORM | In the rendered document a captured signature was sometimes displayed as a black block. This has been resolved. |
| Error during text-tag extraction | PLATFORM | Uploading specific documents with text tags caused a server error, so the transaction could not be created. This has been fixed. |
| Font changed after signing | PLATFORM | After signing and conversion to PDF, the font of the source document was not always retained. The original font is now kept. |
| Sporadic server error while signing | PLATFORM | A briefly interrupted internal connection could make a signing action fail with a server error. Such calls are now retried automatically. |
| Repeated emails after a bounced delegation email | PLATFORM | When a delegation email bounced, it was sent again and again. This loop has been broken. |
| SMS verification via SDK integrations ignored | PLATFORM | SMS verification supplied through SDK integrations was stored as “no verification”. On accounts with mandatory verification, creating the transaction therefore failed with an error. SMS verification is now taken over correctly. |
| Selection lost in the logic editor | FRONTEND | The conditional logic editor lost the target fields of an existing condition as soon as a second condition was added to the same field, so saving failed. This has been resolved. |
| Doubled text field values while signing | FRONTEND | Text field values were rendered doubled or ghosted in the signing ceremony. This has been resolved. |
| Incorrect action after completion | FRONTEND | The post-completion screen incorrectly showed a “review documents” section with associated actions. It is no longer shown. |
| Template placeholder with SMS verification | FRONTEND | A placeholder recipient in a template could not be saved with SMS verification enabled, with a message that a phone number is required. Saving now works; the phone number is entered when the template is used. |
| Contrast in dark theme | FRONTEND | The document actions menu had a light background in the dark theme. The menu now follows the theme. |
