Completing a Request, Certificates & Verification

What happens on completion

Once every required signer has signed, Frappe Sign automatically:

1. Sets the request's status to Completed.
2. Stores the final signed PDF and its hash.
3. Generates an audit certificate (and its hash).
4. If Append Audit Certificate is enabled, appends it to the signed PDF to produce a final verification package.
5. If Enable Certificate Based PDF Signing is enabled, cryptographically signs that final package.
6. Creates Frappe Sign Certificate evidence records for the audit certificate and (if produced) the final verification package.
7. Emails a completion notification to the creator and signers.
8. Submits the request itself.
9. If configured for the source DocType, attaches the signed PDF back to the source document and/or submits it - see Configured Source DocTypes.

Once completed, the whole document locks - see the Evidence Certificates shortcut in the menu:

Frappe Sign Certificate

Each certificate record is an immutable evidence snapshot - it doesn't own any files itself, just URL and hash references to files owned by the request. Two types exist: Audit Certificate and Final Verification Package.

Because everything here is hash-based, you can independently confirm a signed PDF is genuine at any time - see Validating Documents.