Certified PDF against signed PDF

The order they appear in a file

A certifying signature has to come first because it makes a statement about everything that follows. Approval signatures then sit inside the space it permits, which is why a template certified to allow form filling and signing can still collect several signatures without breaking. Turn that around and the arrangement fails: a document with approval signatures already on it cannot be certified afterwards without invalidating them, since certification is itself a change. In a signing pipeline this dictates the sequence, with certification as the last operation performed on a file that is otherwise complete.

What a reader shows for each

Approval signatures appear as entries in the signature panel with the signer, the time claimed and the validity of each. A certifying signature is usually surfaced more prominently, since it speaks for the document as a whole, and a compliant reader will warn at open time if the permission has been violated. Both kinds report the same three underlying facts: whether the covered bytes are unchanged, whether the certificate chain is trusted on this machine, and whether a timestamp is present. Confusing the badge for the finding is the most common misreading.

Where the words get muddled

Everyday speech uses signed for anything with a mark on it, including a scanned image of a handwritten signature, which carries no cryptography at all. Certified is used loosely for anything a business asserts is authentic, including a stamped photocopy. Neither usage matches the format meanings, and that gap causes real confusion when a counterparty asks for a certified copy: they may want a notarised paper copy rather than a PDF with a certifying signature. Asking which of the two they mean saves a wasted trip. Procurement documents are the worst offenders, since a request for certified copies of the executed agreement can mean a PDF with a certifying signature, a paper copy stamped as a true copy by an authorised person, or simply a copy somebody in the business has confirmed is complete. The three cost wildly different amounts and take different lengths of time. One clarifying sentence in reply, naming the three options and asking which is required, resolves it before anybody books an appointment or pays a fee for something the counterparty never wanted. That reply is worth keeping in a template, since the request arrives in almost identical wording several times a year.

Choosing between them for real documents

For a template circulated to be completed, certify with form filling permitted so recipients can work without breaking anything. For a finished agreement, certify at the strictest level once everyone has signed, and accept that the file becomes inert. For internal review copies, an approval signature or no signature at all is usually right, because a certified review draft creates confusion about which version is final. The decision follows the document's stage rather than its importance.

Why a signed document can still be worthless as evidence

A signature covers bytes; it says nothing about who was behind the keyboard. A file can carry a perfectly valid certifying signature from a service while the humans involved were never identified beyond an email address. That is not a defect in the format, it is a division of labour: the file proves integrity, the signing record proves participation. Anyone assessing a document should look at both, and be suspicious of a claim resting entirely on one.

What arrives at the end of a signing here

Each signer's marks are stamped onto the document in turn, producing intermediate versions that are retained internally. When the last signer finishes, the file is signed and certified in one step at the strictest permission level, recorded as PAdES-SHA256-DocMDP. Every recipient and the sender receive that certified copy by email, and the certificate of completion is available as its own file, optionally appended to the document before certification. No second certification is possible afterwards, which is the intended end state. A recipient who asks for the file again therefore receives another copy of that same certified document rather than a freshly certified one, because certifying it a second time would produce a different file with a different hash.

Questions people ask