eSign – New restrictions when using QES
Overview
esign-003-2026
Product: Scrive eSign
Published: 2026-11-19
Change: Highlighting and forwarding are disabled for processes using Qualified Electronic Signature (QES)
Environment: All
Type: Mandatory, action required
Enforced as of: 2026-12-09
Description
Stricter validation rules will apply to Scrive eSign processes where a signing party uses a Qualified Electronic Signature (QES) method. The options to highlight sections in the document and to forward an invitation to sign will be disabled for these parties.
Highlighted sections can at this stage not be stored reliably in PDF files signed with QES. QES signature fields are added to the document when the signing process is started. Forwarding an invitation adds a new signature field and duplicate form fields for the party it was forwarded to, while the original party’s signature field remains unsigned.
Currently, highlighting can be used during signing with QES, but highlighted sections are not added to a sealed document. With this upcoming change, the validations are enforced when a signing process is started and when an invitation is forwarded.
The changes are mandatory and will be enforced starting 9 December 2026.
Impact
If you are using QES methods in your Scrive eSign processes, you must comply with the new validation rules. This applies both when creating new processes and when using existing templates.
Failure to do so will disrupt your processes as of 9 December 2026. Starting a non-compliant process will return an error from the API.
Already signed documents remain unaffected.
Changes
The following restrictions will apply to parties with a signatory_role set to signing_party using a QES method for authentication_method_to_sign:
allows_highlightingcannot be set totrue.can_forwardcannot be set totrue.- It will not be possible to start a signing process for a document with any of these settings. The API will return a validation error.
- API calls to
/forwardsigningwill return an error for these parties.
For pending documents, the option to highlight will no longer be shown in the sign view when signing with a QES method.
NB! Parties with signatory_role set to approver are not affected and can still forward.
Recommendation
These changes require action from all Scrive eSign users creating processes with QES methods for authentication to sign.
We recommend the following steps:
Review and update your processes
Check all templates and integrations where a signing party uses a QES method for authentication to sign. Make sure that allows_highlighting and can_forward are set to false for these parties.
Update your integration
Make sure that your integration handles the new validation errors from the API, both when starting a signing process and when calling /forwardsigning. Complete these updates before 9 December 2026.
You can find more information on the general standard restrictions for signing with QES in our Help Center.
Contact
If you have any further questions, feel free to reach out to Scrive Tech Support by emailing support@scrive.com referring to esign-003-2026.