How VeriStub works
How the check works, what each finding means, and what it can’t detect, in plain English.
VeriStub is a screening aid, not a decision. Always confirm income with the employer or bank before rejecting an applicant.
How the check works
Every PDF carries hidden information about its own history: which program made it, when it was created, when it was last changed and how many times it was saved. A statement downloaded straight from a bank or payroll system usually has a short, clean history. A document that was opened and changed in other software usually leaves traces.
- You add the PDF. Your browser opens the file on your own device. It is not uploaded to us.
- VeriStub reads the file’s history. It looks at the metadata, the save history and the text on the first page.
- You get a score and plain-English findings. Each finding is marked Passed, Caution or Red flag, and the score starts at 100 and goes down for each warning sign.
How to read the score
| Score | Result | What it means |
|---|---|---|
| 78–100 | No signs of tampering found | The file looks like it came straight from its source. Still check that the names, employer and amounts match the application. |
| 50–77 | Review recommended | Some signals need a closer look. Ask for a fresh download or confirm the figures with the employer. |
| 0–49 | Likely altered | Several strong signs of editing. Don’t rely on this document until you have verified it with the bank or employer. |
The score measures signs in the file, not whether the figures are true. A high score is not proof that a document is genuine, and a low score is not proof of fraud.
What each finding means
- Source software. The program that made the PDF. Bank and payroll systems (for example ADP, Paychex, Gusto or a bank’s statement system) are a good sign. Word, Photoshop, online PDF editors or “print to PDF” are a red flag, because that is how edited documents are usually re-exported. If the software is unknown to us, you get a caution.
- Missing producer and creator. Both fields are empty. Someone may have removed the metadata on purpose.
- Created vs. modified dates. If the file was changed more than 2 hours after it was created you get a caution, and more than 48 hours a red flag. A missing creation date is a caution.
- Save history. Each time a PDF is saved again, the earlier version can stay inside the file. One save is normal. Two is a caution. Three or more points to edits after the document was first made.
- XMP metadata. An extra record many system-generated statements include. If it is missing, you get a small caution.
- Text layer. Real statements contain digital text you can select. If the first page has almost no text, the file is probably a scan or a picture, which is much harder to verify.
- Author and title. An author field naming consumer software (such as Microsoft Word) is a red flag. A generic title like “Untitled” or “Scan” is a caution.
- Producer and creator differ. Often happens when a file is re-saved in a different program. Caution only.
Why honest documents are sometimes flagged
A warning sign means the file was handled after it was issued. That is often innocent. Common examples:
- Printed to PDF. The applicant opened the statement in their browser and used “Print → Save as PDF” instead of downloading it.
- Re-saved. The file was opened in Preview, Acrobat or a phone app to rotate, sign, compress or annotate it, then saved again.
- Merged. Several months of statements were combined into one PDF with an online tool.
- Password removed. A protected statement was unlocked and saved as a new copy.
- Scanned or photographed. A paper copy was scanned, so there is no digital history to check.
- Unusual provider. A small employer or bank uses software we don’t recognise yet.
If a document is flagged, don’t assume the worst. Ask the applicant for a fresh download sent directly from their bank or payroll portal, or verify with the source.
What VeriStub can’t check
- Printed and scanned documents. Scanning wipes the file’s history, so any edits made before printing can’t be seen. VeriStub flags scans as harder to verify, but it can’t tell what was changed.
- Fakes made from scratch without traces. A document built from nothing in software that leaves a clean, normal-looking history may pass.
- Whether the numbers are true. VeriStub checks the file, not the facts. Only the employer or bank can confirm someone’s income.
What to do next
- Ask for a fresh download from online banking or the payroll portal, sent to you directly.
- Verify with the source. Confirm pay with the employer’s HR or payroll team, or use the bank’s own verification service.
- Keep it consistent. Run the same check on every applicant and keep the report on file.