E-signature audit trailSealed vs certificate of completion

Eight months after a client signed your service agreement, they dispute it. "I never signed that," the email says, or "that wasn't the version I agreed to." You open the signed PDF. Now what?

The answer is in two documents most people never look at until this moment: the audit trail and the certificate of completion. This guide explains what each one records, how they differ, and how to keep them so they're ready when you need them.

What is the difference between an audit trail and a certificate of completion?

The audit trail is the full, event-by-event log of a signing: every send, open, signature and completion, with times and IP addresses. The certificate of completion is the summary of that log, produced when everyone has signed and attached to or delivered with the signed document. One is the detailed record; the other is the readable proof sheet.

You don't choose between them. You keep both, together with the signed PDF.

What does an e-signature audit trail record?

A typical audit trail records who sent the envelope and to whom, each recipient's role, and events such as sent, opened, signed, declined, reminded and completed. Each event carries a date and time and the IP address it came from. Some platforms add browser or device details. Together they show what happened to the document, step by step.

Here's what a short audit trail looks like for a three-person envelope (example only; the names and IP addresses are made up):

Regulators think along the same lines. For tax returns e-signed through a practitioner, the IRS says e-signature software must capture a digital image of the signed form, the date and time of signing, the identity-check results and, for remote signing, the taxpayer's IP address and login username (IRS e-signature FAQ (opens in a new tab)). Your own documents may not need all of that, but it shows what a credible record contains.

What does a certificate of completion show?

A certificate of completion identifies the envelope and the document, lists each signer with their role, shows when they signed and from which IP address, and confirms the envelope was completed and sealed. It's the page a client, auditor or opposing lawyer reads first, because it tells the story of the signing on a single sheet.

What to look for on a certificate:

• An envelope or reference ID that matches your records
• The document name, so it can't be paired with the wrong file
• Every signer, with their role (client, agent, sponsor, employee)
• When each person signed, and from which IP address
• Completion time and whether the PDF was sealed

AppliFlo Sign adds a certificate of completion to every signed envelope, with an audit trail of who acted, when, and from which IP address.

How do signing order, roles and reminders show up in the record?

Roles tell the record who each person was in the transaction. Signing order shows whether people signed one after another or in parallel. Reminders show you followed up, which helps when someone later says they never saw the document. All three make the audit trail easier to read and harder to argue with.

Roles. "Priya Sharma, client" means more than an email address. When a dispute turns on whether the right person signed in the right capacity, roles answer it.

Order. In sequential signing, the agent signs, then the client, then the sponsor. The trail shows each person signed only after the one before. Parallel signing is faster but the record shows everyone signing independently.

Reminders. An automatic reminder, logged with its time, shows the signer was prompted.

Bulk send. When you send one template to many clients at once, each client gets their own envelope, with its own audit trail and certificate. That matters: one person's record never mixes with another's.

AppliFlo Sign supports roles, signing in order or in parallel, reminders and bulk send of one template to many clients, and each signed PDF gets a PAdES seal.

How do I prove who signed a document?

Combine three kinds of evidence: the audit trail showing the envelope went to the person's address and was signed at a given time and IP, the sealed PDF showing the document hasn't changed, and your own intake records showing how you confirmed their identity and email address. No single item proves identity; together they make a strong, consistent account.

A practical evidence pack:

1. The signed PDF with its seal intact. Our guide to PAdES vs simple e-signatures shows how to check it.
2. The certificate of completion attached to it.
3. The full audit trail, exported if your platform lets you.
4. Intake records showing how the client's identity and email were confirmed.
5. Correspondence where the client acknowledged the agreement or acted on it, such as paying an invoice.

The law cares about intent, identity and reliability. Our guide to whether e-signatures are legally binding covers the US and Australian tests. This is general information, not legal advice; a lawyer can advise on evidence in a specific dispute.

How should I store and share signing evidence?

Store the signed PDF, certificate and audit trail together, with the client or matter record they belong to, for as long as your professional rules require. Share the sealed original, never a re-saved or scanned copy. If a question comes up, send the original file and the certificate, and keep the full trail ready.

Storage habits that help:

• Keep originals. Don't print and re-scan, and don't re-save through "Print to PDF". Both remove the seal.
• File by client or matter. In practice, evidence gets lost between inboxes and shared drives.
• Know your retention period. Registered migration agents in Australia, for example, must take reasonable steps to keep client files for 7 years after the last action on them. Check the rules for your profession.
• Connect it back. With GlobalyOS connected to AppliFlo, the signed copy goes back to the client's record automatically.

Our migration agent paperwork playbook and tax-season playbook for accounting practices show where signing evidence fits in a full client file. Our security page explains how the seal and audit trail work in AppliFlo.

Common mistakes with signing evidence

Most evidence problems are about storage, not signing: keeping the PDF but losing the trail, sharing a modified copy, or not knowing which version was signed. They are easy to avoid if you decide where evidence lives before you need it.

• Downloading only the PDF. The certificate and trail stay in the platform, and nobody exports them.
• Signing links forwarded. A link forwarded to an assistant who signs muddies the record.
• Generic shared inboxes as signer addresses. "info@" tells you nothing about who signed.
• Editing after completion. Any change breaks the seal and starts a new story.
• Treating IP as location. It supports a timeline; it doesn't place a person in a room.