What to Do After a MODIFIED Result: How to Raise It With the Sender

This article is a snapshot – content was accurate as of January 2026 (code examples tested against the API as of October 2026). The product evolves actively; specific counts, examples, and detection rules may have changed since publication – see the changelog for the current state.
A PDF you received has come back as MODIFIED. It might be an invoice, a contract, a certificate or a payment confirmation. Before you write to anyone, one point shapes everything that follows: the result says something about the file, not about the person who sent it.
A MODIFIED verdict means the file was changed after it was first created. It does not say who changed it, why, or whether the change matters. Re-saving in another viewer, converting a format, filling a form or merging pages can all register as a change. The sender may not even know it happened. This guide covers what comes after the result: how to ask, what to attach, how to handle a disagreement and what to keep on record. For the reasons a legitimate file can show up as modified, see why a PDF shows as modified without anyone editing it. For how to run the check itself, see how to check if a PDF has been edited.
Decide what is at stake first
How hard you push depends on the document, not on the verdict alone.
| Situation | Reasonable response |
|---|---|
| Low-stakes file, no money or decision depends on it | Send the neutral request below and move on once you have an answer |
| An invoice, payment instruction or contract you are about to act on | Hold the payment or signature until the sender confirms through a channel you already trust |
| Bank details or amounts differ from what you expected | Treat it as a possible security incident and involve your finance or security team before replying to the thread |
| A signed document that now shows changes after signing | Ask for the signed original from the source system and keep the original file you received |
If money is involved, do not reply only to the email that carried the file. Use a phone number or portal you already had before the document arrived. Our guide on verifying a PDF before payment covers that step in detail.
Step 1: Keep the evidence as you received it
Before you write, preserve what you have.
- Keep the original file exactly as it arrived, with the email or message that carried it. Do not open it in an editor and save it again; that can add a further change of your own.
- Keep the result page link for the check. It stays available and shows the stored analysis, including any update after a review.
- Note the date and time you received the file and the date of your check.
Step 2: Share the result in neutral terms
The easiest way to keep the conversation factual is to give the sender the same information you have. Open the result in your dashboard and use Make Public & Copy Link to create a link that anyone holding it can open, or download the PDF report from the same page. The report links back to the live result, which is the version to trust if the PDF copy is ever edited.
The result page shows analysis findings only. It does not display or let anyone download the PDF itself, so sharing it does not hand your document to a third party.
Frame the message as a question about the document version, not about what anyone did.
Template 1: First message – request the original
Subject: Quick check on the version of [document name / reference]
Hi [Name],
Thanks for sending the [document type] dated [date]. As part of our routine document checks I ran the PDF through HTPBE?, and the result shows the file was changed after it was first created. That is common – for example, when a file is re-saved, converted or exported from another system – so I am only trying to make sure we are both working from the right version.
The result is here: [result link]
Could you:
- confirm whether this is the version exactly as your system produced it, and
- send a fresh copy exported directly from the source system (accounting software, e-signature platform, portal), if you can?
Once I have that, I will close this on my side. Thank you for helping me with it.
Best regards, [Your name]
Template 2: Ask for the source and the history
Use this when the sender replies that they did edit or re-save the file.
Subject: Re: [document name / reference]
Hi [Name],
Thanks for the quick reply. That makes sense. To complete our records, could you tell me what was done to the file after it was first created (for example, re-saved, converted, merged, signed), and send the original export from before that step if it still exists?
If the content is unchanged, a short confirmation from you plus the original export is all I need.
Best regards, [Your name]
Template 3: Gentle follow-up
Subject: Following up: [document name / reference]
Hi [Name],
A quick reminder about my message of [date] on the [document type]. I cannot [process the payment / countersign / file this] until I have the version exported from your system. If it is easier, I am happy to talk it through by phone on [number].
Best regards, [Your name]
Notice what these messages leave out. They do not use the words fraud, forged or tampered, they do not guess at motive, and they do not threaten. If the document turns out to be fine, the sender has nothing to be offended by. If it is not, you have lost nothing by being polite.
Step 3: Read the reply
The sender explains a normal cause. They re-saved, converted or signed it. Ask for the original export (Template 2) and compare it or run it through the check. If the fresh export comes back INTACT and the key details match what you expected, you can close the matter and record it.
The sender says nothing was changed and does not know why. This is information, not an accusation. Ask them to export the document again from the source system rather than from their email. Files often pass through scanners, mail gateways or viewers that re-save them without anyone noticing.
The sender cannot provide an original. Do not fill the gap with assumptions. Decide based on the stakes you identified above: for a routine file you may accept a written confirmation; for a payment or a contract, wait for the original or confirm the key details (amounts, account numbers, dates, parties) through a separate trusted channel.
No reply. Follow up once after two or three working days with Template 3 and try a second contact method. Do not act on the document in the meantime if a payment or signature depends on it.
If the details in the document are different from what you expected and the sender cannot account for it, escalate to your security, compliance or legal team. Our article on how invoice PDFs get altered in practice explains why that combination deserves a second look.
Step 4: If the sender disputes the result
A sender who says ‘I never touched it’ may be telling the truth. A file can pass through several systems between its creation and your inbox, and a few of them re-save it. Disagreeing about the result is not the same as disagreeing about intent.
Practical ways to move forward:
- Compare the originals. Ask them to run the version they hold through the same check and share the link. Two results side by side make the difference between the copies visible and give you something concrete to discuss.
- If you think the result itself is wrong, use Report an Incorrect Result on the result page in your dashboard (if the result was produced by an older engine version, re-check the file first). It re-analyses the file and replies to your account email. Only analysis metadata is submitted: filename, verdict and technical indicators. Your PDF content is never transmitted.
- Keep the language factual. ‘The file shows changes after creation’ is a statement you can defend. ‘You edited this document’ is not.
A reviewed result is an analysis of the file. It does not settle who is right in a commercial disagreement, and it is not legal evidence of intent. If the matter is likely to reach a contract dispute, a claim or a regulator, bring your legal team in before further exchanges.
Step 5: Record what happened
Keep a short record for every document you queried, whatever the outcome:
- Document name, reference, sender and date received
- Result link and the date of the check
- Date and wording of each message sent and each reply received
- The outcome: confirmed legitimate, replaced by an original export, escalated or rejected
- Who made the final decision
A clean record helps in an audit or a later disagreement, and it protects the sender too. A document that was queried, explained and closed is a normal part of a healthy process.
Making this routine
If you receive many documents, build the check into intake so that a MODIFIED result triggers the same polite request every time, rather than an improvised message. For high volumes, run the check automatically through the HTPBE? API and route verdicts into your workflow; the pricing page lists the current plans and pay-per-check packs. For occasional use, the web tool is enough.
Summary
- A MODIFIED result describes the file. It does not describe the sender’s intent.
- Keep the original file and the result link before you write.
- Ask for the original export from the source system, in neutral words, using the templates above.
- Verify high-stakes details through a channel you already trusted.
- If there is a disagreement, compare originals and keep the language factual.
- Write down what you did and how it ended.