Revoke an acceptance when you intend that particular signature record to stop counting as valid. The record remains available and is marked revoked; this is different from archiving the agreement or publishing revised wording.

Identify the exact record

Open PD Modules → Agreements → Agreements and choose Signatures on the intended document, or open the signed-agreements section and select its document filter.

Check the customer, accepted version, signed date and current Status. If you are uncertain which record needs attention, inspect its Evidence PDF first rather than revoking a similarly named entry.

Revocation acts on one acceptance row. A customer can have other non-revoked acceptances for the same agreement, so review the records before assuming this action will create a new signing request.

Revoke the acceptance

1. On the intended valid row, choose Revoke.
2. Read Revoke signature and confirm only when the record is correct.
3. Check the returned result.
4. Revisit the signature list and confirm that this row’s status is Revoked.

The staff action records a revocation reason identifying the acting staff member and a time. The dialog does not offer a separate free-text reason field. Do not rely on the success message alone if the row’s status has not changed; inspect the record before repeating the operation.

Check whether another signature is required

The module evaluates the customer’s remaining non-revoked acceptances, the current version and its re-acceptance decision. If no valid acceptance remains for an applicable published agreement, it can become outstanding again.

If an older valid acceptance remains and the current version does not require earlier signers to re-accept, revoking a newer row may leave that earlier acceptance sufficient. It does not automatically invalidate every signature that customer has supplied for the document.

Request timing and audience still apply. A checkout request is handled during an applicable order; a required On next login request uses the account-visit flow. An archived, optional or on-demand document should not be treated as a guaranteed account-blocking request.

Keep the record and replacement separate

The revoked row remains part of the history. There is no Restore signature control on this screen. A later customer acceptance is another recorded interaction; staff do not sign on the customer’s behalf through this action.

Your hosting team should retain the document/version and acceptance reference, intended action, original attempt time and redacted status while checking the exact row and remaining valid acceptances. Do not revoke additional records as an experiment or send real signatures and confidential document contents unnecessarily.

Check acceptance status and remaining requests

Your hosting team should compare the exact acceptance row’s status after Revoke with the original operation result, remaining valid acceptances, current version’s re-acceptance choice, audience and request timing. A success message alone does not establish the row changed or that every earlier acceptance stopped counting. Do not revoke additional records or sign for the customer as an experiment.

See the PD Agreements WHMCS guide for related tasks, or explore PD Agreements.