How are Bulk Link transactions counted when signing is not completed?

This article explains how Bulk Link transactions are counted when a recipient starts but does not complete the signing process. It also describes how returning signers are handled and how to prevent multiple transactions from being counted for the same signer.

How transactions are counted?

When a recipient opens a Bulk Link and starts a signing session, a transaction may be counted even if the signing process is not completed.

The following scenarios may result in transaction usage:

• A recipient opens a Bulk Link and starts signing but does not complete the document.
• A recipient leaves the signing session before finishing the document.
• The same recipient later returns and starts a new signing session using the same Bulk Link.

If a new signing session is created, an additional transaction may be counted. As a result, multiple transactions can be counted for the same signer when multiple signing sessions are created using the same Bulk Link.

How to prevent multiple transactions for the same signer?

To help prevent additional transactions from being counted for the same signer:

1. Create or edit the Bulk Link.
2. Open the Bulk Link Settings section.
3. Disable Allow users to sign multiple times.
4. Save the Bulk Link.

When Allow users to sign multiple times is disabled, returning signers are directed back to their existing incomplete signing session instead of starting a new signing session.

Example

Allow users to sign multiple times enabled

1. A signer opens the Bulk Link and starts signing.
2. The signer leaves before completing the document.
3. The signer later opens the Bulk Link again.
4. A new signing session is created.

Result: An additional transaction may be counted.

Allow users to sign multiple times disabled

1. A signer opens the Bulk Link and starts signing.
2. The signer leaves before completing the document.
3. The signer later opens the Bulk Link again.
4. The signer is redirected to the existing incomplete signing session.

Result: A new signing session is not created.

Best practices

• Disable Allow users to sign multiple times when signers should complete only one submission.
• Encourage signers to resume existing signing sessions instead of starting over.
• Review Bulk Link settings before sharing the link publicly.
• Monitor transaction usage when using Bulk Links with a large number of recipients.