> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/product-guides/compliance-studio/e-signatures.md).

# eSignatures

### eSignatures Overview

ComplyCube eSignatures enables businesses to collect legally binding electronic signatures as part of **KYC**, **AML**, and customer onboarding workflows.

Create signature document templates from uploaded **PDFs** or generate them dynamically through Smart Forms. These templates can later be used to generate signature envelopes for a live signing journey.

This lets you combine identity verification, compliance declarations, agreement capture, and electronic signing within a single verification journey.

ComplyCube supports **Simple Electronic Signatures (SES)**, **Advanced Electronic Signatures (AdES)**, and **Qualified Electronic Signatures (QES)**, allowing you to select the appropriate level of assurance and legal weight for each use case.

Under the **EU eIDAS Regulation**, SES, AdES, and QES are all legally recognized electronic signatures, offering increasing levels of identity assurance, security, and evidential value.

Integrated with [Workflows](/documentation/product-guides/compliance-studio/workflows.md) and [Smart Forms](/documentation/product-guides/compliance-studio/smart-forms.md), eSignatures supports end-to-end onboarding, compliance, and agreement execution processes.

{% hint style="info" %}
Please get in touch with your **Account Manager** to enable this feature.
{% endhint %}

### Common use cases

Use eSignatures to capture legally relevant agreements, declarations, and approvals as part of onboarding and compliance journeys:

* **Customer onboarding agreements**: Send terms, mandates, account opening forms, and customer agreements for signature.
* **KYC and AML declarations**: Capture attestations, source of funds statements, risk disclosures, and regulatory acknowledgements.
* **Identity verification workflows**: Combine verification, declarations, and electronic signing within a single customer journey.
* **Dynamic signing flows**: Generate agreements and signature steps from Smart Form responses and business rules.

### How eSignatures work

eSignatures follows a workflow-based template flow. You define the document template inside the workflow first, then the live envelope is created when a workflow session starts and the customer reaches the signing step.

The process works as follows:

1. Choose the **signature level** (**SES**, **AdES**, or **QES**).
2. Create a document template from a **PDF** or dynamically using a [Smart Form](/documentation/product-guides/compliance-studio/smart-forms.md).
3. Configure the Smart Form and any additional verification or compliance steps within the workflow.
4. When a workflow session is created and the customer reaches the signing step, ComplyCube generates a live signature request from the document template.
5. Present documents, clauses, and signature steps to the customer.
6. Capture the signature and supporting evidence.
7. Store signed documents and audit records as part of the verification journey.

{% hint style="info" %}
For the lifecycle after creation, see [envelope statuses](#envelope-statuses).
{% endhint %}

***

<figure><img src="/files/cmZSiQW7DDe26Q7D9Jz4" alt="eSignatures document template builder"><figcaption><p>eSignatures - Signing Configuration</p></figcaption></figure>

***

<figure><img src="/files/nKEnBOKtZHhL3wJ2Ay6H" alt="eSignatures signing configuration"><figcaption><p>eSignatures - Document Template Builder</p></figcaption></figure>

### Signature levels

ComplyCube supports multiple signature levels to accommodate different legal, regulatory, and evidential requirements.

<table><thead><tr><th width="130.953125">Signature level</th><th>What it is</th><th>Typical use cases</th></tr></thead><tbody><tr><td><strong>SES</strong></td><td>A simple electronic signature suitable for most business and onboarding scenarios.</td><td>Customer onboarding, agreements, declarations, acknowledgements, and consent capture.</td></tr><tr><td><strong>AdES</strong><br>(or AES)</td><td>An electronic signature with additional evidential measures and signer linkage.</td><td>Compliance documentation, regulated onboarding, and higher-assurance signing flows.</td></tr><tr><td><strong>QES</strong></td><td>A qualified electronic signature designed for use cases requiring qualified signing frameworks.</td><td>Jurisdictions or processes that mandate qualified signatures or maximum legal assurance.</td></tr></tbody></table>

### Envelope statuses

An envelope moves through a defined lifecycle from creation to completion or closure.

<table><thead><tr><th width="131.2421875">Status</th><th>Description</th></tr></thead><tbody><tr><td><strong>Created</strong></td><td>The envelope has been generated, but signing has not started yet.</td></tr><tr><td><strong>In progress</strong></td><td>The envelope is active and the customer is reviewing or signing it.</td></tr><tr><td><strong>Completed</strong></td><td>The signing process finished successfully.</td></tr><tr><td><strong>Failed</strong></td><td>The signing flow did not complete because of a system or delivery failure.</td></tr><tr><td><strong>Declined</strong></td><td>The signer actively refused to sign the envelope.</td></tr><tr><td><strong>Expired</strong></td><td>The envelope was not completed before its validity window ended.</td></tr></tbody></table>

### Audit trail and evidence

When signing is completed, ComplyCube links the signed document and supporting signature evidence to both the **client** and **workflow session** records.

This gives teams a clear audit trail for:

* Compliance reviews and regulatory audits.
* Customer investigations and dispute handling.
* Internal approvals and record-keeping.

<figure><img src="/files/AAQzJL1lD1StiWVBkdN1" alt=""><figcaption><p>eSignatures - Workflow Session View</p></figcaption></figure>

### Frequently asked questions

<details>

<summary>What is an eSignature envelope?</summary>

An envelope is the live document package sent for signature.

It is generated from a document template and used within the signing journey.

</details>

<details>

<summary>Can I create document templates from PDFs and Smart Forms?</summary>

Yes.

eSignatures supports **PDF-based** templates and **Smart Form-based** templates.

This gives you a fixed-document option and a dynamic questionnaire-driven option before generating envelopes later in the flow.

</details>

<details>

<summary>What is the difference between a document template and an envelope?</summary>

A document template defines the document, fields, clauses, and signing structure in advance.

An envelope is the live signature package generated from that template for a specific signing journey.

</details>

<details>

<summary>What is the most common type of electronic signature?</summary>

For most customer onboarding and agreement flows, **SES** is the most commonly used option.

It is typically the right fit for general agreements, acknowledgements, declarations, and other common use cases.

</details>

<details>

<summary>How do eSignatures fit into KYC and AML onboarding?</summary>

Yes.

eSignatures can sit alongside identity verification, AML screening, declarations, and policy evaluation in the same [workflow](/documentation/product-guides/compliance-studio/workflows.md).

This helps you move from verification to agreement capture and approval in one journey.

</details>

<details>

<summary>Can the documents or clauses change based on customer answers?</summary>

Yes.

[Smart Forms](/documentation/product-guides/compliance-studio/smart-forms.md) supports **conditional logic**, so documents, clauses, and signature steps can change based on previous answers or workflow conditions.

</details>

<details>

<summary>What evidence is stored after signing?</summary>

ComplyCube stores the signed output and links signature evidence to the verification journey.

This supports audit, review, and downstream compliance processes.

</details>

### Related topics

* [Workflows](/documentation/product-guides/compliance-studio/workflows.md) to orchestrate eSignatures with verification and compliance steps.
* [Smart Forms](/documentation/product-guides/compliance-studio/smart-forms.md) to generate dynamic signing journeys and agreement content.
* [Compliance Policies](/documentation/product-guides/compliance-studio/policies.md) to apply rule-based evaluation around signed journeys.
* [AML Screening Check](/documentation/product-guides/watchlist-pep-and-adverse-media/aml-screening-check.md) and [Identity Check](/documentation/product-guides/biometric-and-liveness-verification/identity-check.md) to combine verification and signing in one customer journey.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.complycube.com/documentation/product-guides/compliance-studio/e-signatures.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.