HOW IT WORKS · OVERVIEW
  1. Recipient requirements
  2. Format and variant
  3. Complete file set

Start with recipient requirements

Check the portal instructions or agreement with the recipient. Note the document format, signature format and required attachments. “Qualified signature” alone may not describe the complete delivery requirement.

For PDF documents

PAdES associates the signature with a PDF. The signed file remains readable in a compatible PDF application, with signature details available for validation. A visible mark does not establish the signature level or validity.

For XML structures

XAdES can associate signatures and content in different ways, including embedded and detached arrangements. A detached signature requires the correct original document and signature file. Establish the variant required by the specific service.

A filename does not convert a format

Renaming PDF to XML does not convert the content. Do not print a signed file into a new PDF to combine attachments. Return to the original document and appropriate signing settings when the output is unsuitable.

The solution and your next questions

Explore the solution and support
Why does a portal reject a signed document?

Possible causes include the format, attachments, certificate data or permissions. Inspect signature validation and the portal message separately. Signing does not establish compliance with every recipient requirement.

Have a similar case?

Tell QES what you need to accomplish and where you are in the process. We will match the right solution or identify what is missing.

Contact QES