Audit trail & certificate · Updated
Proof of who signed what, and when, inside every PDF.
Every document records when it was sent, opened and signed, with IP address and device for each signer. The timeline is appended to the signed PDF as a certificate of completion, with a SHA-256 fingerprint anyone can check.
Timestamps, IP addresses and devices
Certificate of completion in the PDF
Public SHA-256 verification
What is in an eSignSimple audit trail?
Every document you send records a timeline of what happened to it: when it was uploaded and prepared, when it was sent and to whom, when each signer opened it, when they signed or declined, every reminder that went out, and when the document was completed or voided. Each event has a UTC timestamp, and events triggered by a person carry the IP address and the device and browser they used.
When the last person signs, that timeline is printed onto a certificate of completion page and appended to the signed PDF itself. You don't have to log in somewhere to prove what happened years later; the evidence travels inside the file you already keep.
Our take: an audit trail is the part of e-signature that actually matters when something goes wrong. Nobody disputes a signature on a good day. When a client says "I never agreed to that" eight months later, the question is whether you can show who received the link, when they opened it, and that the file hasn't changed since. That is what we built this for.
What does the certificate of completion show?
The certificate lists the document title and its ID, who sent it, when it was sent and completed, and the SHA-256 fingerprint of the original document before anyone signed. For each signer it shows their name and email, their place in the signing order, when they signed and from which IP address, the device and browser, and a line confirming they consented to use electronic records and signatures. Below that is the full event log.
Timestamps are always in UTC and in ISO format, in every language, because evidence should be unambiguous. The rest of the certificate follows the document's signer language, so a Spanish client gets a certificate in Spanish. On Gold, the certificate also carries your logo and brand colour (see team and branding).
How does the SHA-256 fingerprint protect the document?
We fingerprint the document twice. Before sending, the prepared PDF is hashed, and that value goes on the certificate as the original fingerprint. After the last signature, the finished PDF, certificate included, is hashed again and the value is stored with the audit trail. A SHA-256 fingerprint changes completely if a single byte of the file changes, so it is a precise way to tell whether a file is the one that was signed.
Anyone can check a file on our public verify page: drop the PDF there and your browser calculates the fingerprint locally, with only the 64-character value sent to us. If it matches a completed document, the page confirms it. The PDF itself never leaves the device, which matters when it is an employment contract or a lease. Our guide on how to verify an electronic signature explains what a match does and doesn't prove.
Is the audit trail enough to hold up in a dispute?
For everyday business documents in most countries, a simple electronic signature with a good audit trail is strong, practical evidence. The US ESIGN Act and UETA and the EU's eIDAS Regulation all say a signature can't be refused legal effect just because it is electronic; what a court then looks at is whether you can show who signed and that the record is intact. The audit trail and fingerprint answer exactly those questions.
Be honest about what it is, though. eSignSimple provides simple electronic signatures. Signers are identified by the unique link sent to their email address plus the IP, device and timing evidence; we don't do SMS codes or ID checks yet. If a process legally requires an advanced or qualified signature, or a notary, this isn't the right tool for that document. Our legality guides list the common exceptions by country, and the audit trail glossary entry explains the concept in more depth.
Which plans include it?
All of them, including Free. We think evidence shouldn't be a premium feature: a document signed on the Free plan gets the same audit trail, certificate and fingerprint as one sent from Gold. Documents you sign yourself with the free Sign PDF tool get them too.
What should you keep after a document is signed?
Download the final PDF from your dashboard or the completion email and store it with your other records. That one file is the signed document, the certificate and the evidence. Don't re-save it through another PDF app or "print to PDF" it: the content would look the same, but the fingerprint would change and the verify page would no longer match. If you need to annotate it, keep the original untouched next to your working copy.
If you are leaving another provider, download their audit trails and certificates too before you cancel; how to cancel a DocuSign subscription shows why that step matters.
What the audit trail records for each document
| Event | What is recorded | Why it matters |
|---|---|---|
| Uploaded and prepared | Time, original SHA-256 fingerprint | Fixes the exact wording that was sent |
| Sent and link created | Time, recipient for each signer | Shows who was invited, and in which order |
| Viewed | Time, IP address, device and browser | Answers "I never saw it" |
| Reminded | Time and reminder number | Shows the signer was chased, not ambushed |
| Signed or declined | Time, IP, device, consent to e-sign | The act of signing itself |
| Completed | Time, final SHA-256 fingerprint | Lets anyone check the file later at /verify |
Frequently asked questions
Does every document get an audit trail?
Yes, on every plan including Free. The certificate of completion with the audit trail is appended to the final PDF automatically.
What is a certificate of completion?
A page added to the end of the signed PDF that lists the document, its fingerprint, every signer with time, IP address and device, their consent to sign electronically, and the full event log.
Can someone change the PDF after it was signed?
They can edit a copy, but the SHA-256 fingerprint would change and our verify page would no longer confirm it. The original fingerprint is stored with the audit trail.
Does the verify page upload my PDF?
No. Your browser calculates the fingerprint locally and only sends the 64-character value to check against our records.
Do you verify signers' identity?
Signers are identified by their unique email link, IP address, device and timestamps. SMS codes and ID verification are not available yet.
Is the certificate in my client's language?
Yes. It follows the document's signer language, one of ten we support. Timestamps stay in UTC so they read the same everywhere.
Related reading
Get your next document signed today.
Start with 3 free documents a month. No card needed.