Administrative Invalidation and Void Protocols

This guide provides technical instructions for the formal invalidation of an active transaction (voiding), including forensic implications and recipient notification.

Prerequisites

• Administrative or Owner-level permissions for the target envelope.
• The envelope must be in a Pending or Sent state. (Completed envelopes cannot be voided).

Strategic Overview

Voiding is the formal process of terminating a digital transaction before its completion. Unlike simple deletion, voiding is a recorded legal action that immediately revokes all outstanding signing tokens and notifies all participants that the document is no longer valid for execution. This protocol is essential for correcting errors in document content, recipient routing, or when a business agreement is terminated prior to final signature.

Implementation Sequence

1. Verification of Status

Ensure the envelope has not yet been finalized. Once the status transitions to Completed, the cryptographic seal is applied and the document becomes immutable; it can no longer be voided.

2. Execution of the Void Command

Navigate to the Envelope Details interface and select the Void action. The platform will initialize the Invalidation Wizard.

3. Specification of Reason for Invalidation

IUSign mandates the provision of a "Reason for Voiding." This string is:

• Communicated to Recipients: Included in the automated invalidation notification.
• Recorded in Audit Trail: Permanently stored as part of the forensic record of the transaction.

[!IMPORTANT] Use professional and precise language (e.g., "Revision required to Clause 4.2" or "Transaction terminated by mutual agreement") as this becomes part of the permanent legal record.

4. Finalization and Cryptographic Lock

Upon confirmation, the platform executes the following:

• Token Decommissioning: All recipient access links are immediately invalidated.
• Status Transition: The envelope state is updated to Voided.
• Forensic Logging: An ENVELOPE_VOIDED event is appended to the audit trail.
• Notification Dispatch: Automated emails are sent to all participants informing them of the invalidation.

Data Impact and Archival

Strategic Considerations for Enterprise Users

• Audit Defensibility: Always provide a detailed reason for voiding to ensure future clarity during legal or internal reviews.
• Alternative to Voiding: If only minor recipient data needs correction (and no signatures have been collected), consider using the Modify/Correction protocol instead of a full void and restart.
• Cleanup: Once an envelope is voided, it remains in your "Voided" filter. You may choose to Archive (Trash) it to maintain repository hygiene.

Diagnostic and Resolution Protocols

Related Documentation

• Modifying an Active Envelope (Correction)
• Archiving and Deleting Transactions
• Forensic Audit Trail Analysis
• Managing Declined Transactions