Docexp

Does Your Bank Statement Look Edited? The Checks a Lender Runs, and How to Run Them Yourself

A rental application, a loan, a freelance platform's identity check, all of them increasingly want a bank statement, and a growing number of landlords, lenders and background check services now run that statement through automated review before a person ever looks at it. That review is not reading your transactions for judgment. It is checking a short list of mechanical things that a genuine statement almost always gets right and an edited one tends to get wrong, even when the edit looks fine to the eye.

Here is what those checks actually look for, and a free, offline way to run the same checks on your own statement before you send it.

The balance has to add up, every single row

A bank statement with a running balance column is really a chain: each row's balance should equal the previous row's balance plus or minus that row's own transaction amount. Change one transaction amount without recalculating every balance below it, and the chain breaks at exactly the point of the edit, even if every other number on the page looks completely normal.

This is simple enough to show with plain numbers. A genuine sequence of transaction amounts and the running balance that follows from them:

Amount Balance
+100.00 1100.00
-50.00 1050.00
+200.00 1250.00
-30.00 1220.00
+75.00 1295.00

Every balance matches the one before it plus that row's amount. Now change only the last amount from 75.00 to 175.00, without touching the balance column, the kind of edit someone might make to inflate a deposit:

Amount Balance
+100.00 1100.00
-50.00 1050.00
+200.00 1250.00
-30.00 1220.00
+175.00 1295.00

Visually, almost nothing changed. Arithmetically, the last row now claims a 175.00 increase but the balance only moved by 75.00. That single mismatch is the strongest signal a deterministic check has, because it does not depend on recognising fonts or logos, it is pure subtraction.

A spliced number often sits in a different font object than everything else

A PDF embeds its fonts as objects, and every character drawn with a given font references the same object. If someone edits one number with image or PDF editing software rather than regenerating the whole document from the original banking system, that number is often placed using a different font object than the rest of the figures on the page, even when the typeface looks identical on screen. A handful of digits in a different font among hundreds in the same one is the kind of thing nobody checks by eye and exactly the kind of thing a mechanical pass over the file's own font references can catch.

The file's own metadata can name the tool that touched it

Every PDF carries producer and creator fields in its metadata, usually naming the software that generated it. A statement a bank's own system produced says so. A statement that has since been opened in image editing software, and had that software re-save it, often carries that software's name in the same field, Photoshop, GIMP, Canva and similar tools all leave this trace. The file's modification timestamp is worth the same kind of look: a statement that was created once and never touched again is normal; one modified days after it was created is the kind of gap worth a second look, on its own it proves nothing, but combined with anything else on this list it adds up.

What none of this proves, and what it cannot check yet

None of these checks is a verdict. A broken balance chain, an odd font, or editor metadata are each things to look into, not proof of anything on their own, and a statement with none of these flags has not been certified genuine, only that the specific things that can be checked mechanically came back clean. These checks also only work on a digital, text based statement. A scanned photo or printout has no text layer and no font objects to compare, so there is nothing mechanical to check, and that absence is not itself suspicious.

Checking your own statement before you send it

Bank statement trust check runs every check described above (the balance chain, the font comparison, the metadata trace) entirely in your browser the moment you drop a PDF in. Nothing leaves your device while it reads the file, and every finding comes with the specific line it is based on, so you can verify it by hand rather than trust a label.

The most common reason an honest statement trips one of these flags is editing it yourself before sending it, cropping out other accounts, blacking out a balance you'd rather not share, or re-saving it from one format to another. Any of those can leave the same kind of trace an actual splice does. If your own statement comes back with a flag and you know exactly why, because you edited it yourself, that is worth mentioning to whoever asked for it rather than resending the file quietly: a reviewer who runs the same kind of check you just did will see the same trace either way.

Frequently asked questions

Can this tool tell me for certain whether a bank statement is fake?

No, and it does not claim to. It runs a specific, mechanical set of checks, balance arithmetic, font consistency, metadata, and shows you exactly what each one found. A clean result means those particular checks found nothing, not that the document is certified genuine. Treat it as one input into a decision, the same way the checks themselves are described inside the tool.

Why did my own genuine bank statement get flagged?

The most common honest reason is that it was edited after the bank issued it, redacted, cropped, converted between formats, or re-saved from a different application. Any of those can leave a metadata or font trace that looks identical to what an actual edit leaves, because mechanically it is the same kind of change.

Does this work on a scanned bank statement or a photo of one?

Not yet. These checks need a digital statement with a real text layer: actual characters with position and font data, not a picture of characters. A scanned or photographed statement has no such layer, so there is nothing for the balance, font or metadata checks to read.

What should I do if a statement comes back with a critical finding?

Treat it as a reason to look closer, not a verdict. Open the specific line the finding points to and check the arithmetic yourself; the tool shows its evidence precisely so that step is possible. If the document came from someone else and the finding holds up, that is a conversation to have with them or the institution the statement claims to be from, not something to decide from a label alone.


Bank statement trust check reads your file entirely in your browser. Nothing is uploaded, which matters doubly here: a bank statement carries your account number and your balance, not just your name.