Your Signed Document Was Rejected. Here Is What Usually Went Wrong

Drop your document here and sign it now. PDF, Word and Excel all work: a .docx or .xlsx is laid out in your browser exactly as it was written, so there is nothing to convert first. Add a signature, a date, a company stamp or a watermark, then download it sealed. Free to start, no account, and the file is never uploaded to do it.

You sent a signed document to a bank, a registry, a landlord or a client, and it came back rejected. The reason given, if there was one, was a sentence long and told you nothing. This is the most frustrating failure in the whole business of signing, because the document looks perfectly fine to you. Rejections cluster into a small number of causes, and once you know what the person on the other side is actually checking, they stop being mysterious.

The signature is there but nothing stands behind it

The most common cause is that the document carries a picture of a signature and nothing else. No record of who applied it, no time, no way to tell whether the pages around it are the ones that were signed. An organisation that has been burned before is not looking at the squiggle, it is looking for the evidence, and a pasted image has none.

A signed document with an audit certificate attached answers the question before it is asked: who signed, when, from what address, which verification steps they passed, and the fingerprint of the exact file. That is what turns "we cannot accept this" into "fine".

The wrong person signed, or the right person could not be shown to have signed

Plenty of rejections are about authority rather than technology. A contract signed by somebody who is not a director where a director was required, a form signed by an office manager where the account holder was required, a document signed on behalf of a company by somebody the recipient has no record of. No signing tool can fix this, and it is worth checking the requirement before signing rather than after.

The related version is identity. Where the recipient needs to know the signer was the person named, an email link on its own is thin: it proves the link reached an inbox. A one-time code to a phone raises it considerably, and a checked ID raises it further. Which level you need is set by the recipient, not by you, so ask.

The form was right but the format was wrong

Some rejections are purely mechanical, and these are the most annoying because nothing was actually wrong with the agreement. A file that is too large for an upload limit. A .docx where a PDF was specified. A scan at a resolution the intake system cannot read. Pages out of order, or a page missing because the scanner double-fed.

It is worth reading whatever the recipient publishes about accepted formats before sending, and worth sending a PDF by default. PDF is the only format that everybody can open and that fixes the layout, which is why it is what almost every institution asks for.

The document had been edited after signing, or looked as though it had

Adding a page, re-saving through another tool, or flattening a signed file will all break a cryptographic signature that was applied earlier, and a reader that checks will show a warning. From the recipient’s side that warning is indistinguishable from tampering, so they refuse it. The order matters: assemble the document, then sign it, then do nothing else to it.

This is also why sending the verification link alongside the file is worth the extra sentence. It lets the recipient check the document rather than take a view on it, and a check that passes ends the conversation.

What to do with the rejection you already have

Ask one question: "which part was the problem, the signature, the signer or the file?" It sounds obvious and almost nobody asks it, and the answer decides whether you are re-signing, getting a different person to sign, or just re-exporting.

Then fix it once. Send the corrected document with the audit certificate and the verification link, which pre-empts the two most common causes in one go.

A note on what this page is and is not

These are the operational patterns behind most rejections, not legal advice about your document. Requirements differ by country, by institution and by document type, and the party asking is the authority on what they will accept. Where a rejection has consequences, ask them what they need in writing and take advice if the document matters.

Questions people ask about this

Why was my electronically signed document rejected?

Usually one of four things: the signature had no audit trail behind it, the wrong person signed or their authority could not be shown, the file format or size did not meet the recipient's requirements, or the document had been re-saved after signing so a checker flagged it as altered.

What is an audit trail on a signed document?

The record around the signature: who signed, when, from what address, which verification steps they passed, and the fingerprint of the exact file. It is issued as a certificate alongside the document, and it is the thing most often missing when a signed document is refused.

Are electronic signatures legally binding for banks and registries?

Electronic signatures are recognised under the ESIGN Act, UETA and eIDAS for most business documents, but the party receiving your document decides what it will accept, and some require a specific tier of signature or a specific format. Ask them in writing what they need rather than reading across from a general rule.

How do I prove a document was not altered after signing?

By its fingerprint. A SHA-256 hash of the finished file is recorded at signing, and any change at all produces a different hash. Recompute it and compare, which is what the verification page does when somebody scans the QR code or uploads the file.

Make a signature free →

What PDF Verified is, and what it is not

Electronic signature law is settled in broad terms and specific in the details. The ESIGN Act, UETA, eIDAS and their equivalents recognise electronic signatures across more than 190 countries, and what decides a particular case is intent to sign plus evidence connecting the signature to the signer, which is what the audit certificate records. Certain document types carry their own formalities wherever you are: deeds, wills, some property instruments, and anything requiring a witness or a notary. Sign only what you are authorised to sign, since applying another person signature without their authority is forgery whatever tool is used.

PDF Verified is a tool for preparing, signing, stamping and checking documents. It is not a law firm, a compliance service or a forensic examiner, and nothing here is legal, financial or compliance advice. Requirements differ by country, by document type and by the party asking, so check what applies to your document before you rely on it, and take advice where the document matters. You are responsible for the documents you create, sign and send, and for having the authority to do so: signing or stamping in somebody else name, or as an organisation you do not represent, is forgery whatever tool is used. To the extent the law allows, we accept no liability for how a document made with this tool is used or relied on. The full position is in our terms of service.

More on esignatures & signing

Tools