Search for "bank statement" plus almost any editing term and you'll find an entire cottage industry — template sites, "novelty document" sellers, editing services with same-day turnaround. Tenant-screening firms keep reporting that a meaningful share of the financial documents they see contain some level of alteration. The people relying on those documents — landlords, letting agents, small lenders, employers running background checks — mostly check them by eye.
An eye check catches almost nothing, because the visible page is the one part fraudsters polish. What they can't polish is everything underneath. There are really only three ways to fake a statement, and each fails differently.
Method one: edit a real statement
The most common approach, because it's the easiest. Take a genuine PDF statement, open it in an editor, and change what needs changing — inflate the balance, delete the gambling transactions, resize the salary. The letterhead, layout and account details are all real, which is exactly why people trust the result.
But this method fights the PDF format itself, and usually loses:
- The original may still be inside the file. Many editors save changes by appending them, leaving the pre-edit content recoverable. The forged statement can literally contain the real one. I've written more about this in the seven signs of PDF editing.
- The software trail changes. Banks generate statements with their own rendering systems, and the file says so. After a desktop editor touches it, the file says that too — or the producer field is suspiciously stripped.
- The fonts betray the edit. The editor rarely has the bank's exact font, so it substitutes a lookalike. The edited numbers are now typeset in a different font than the rest of the document — invisible to the eye, unmistakable at the glyph level.
- The edited value sits wrong. A fraction off the baseline, spacing slightly tight, weight slightly off. Anomalies that cluster on exactly the numbers that matter.
Method two: build one from a template
The "novelty statement" sites work this way: pick your bank, type in the transactions you wish you had, download a PDF. No editing traces at all — because nothing was edited. The whole thing is fake from the first byte.
Different method, different tells:
- Wrong fonts from the start. Template sites don't license the bank's real typefaces. The document is set in whatever the template used — often a font the bank has never printed a single statement in, sometimes one that didn't exist when the statement is dated.
- Wrong producer. The file admits it was made by a generic HTML-to-PDF converter or an office suite, not a bank's document system.
- Broken banking logic. Sort codes that fail checksum rules, transaction references in the wrong format, statement periods that don't match the bank's actual cycle dates.
Method three: the screenshot or the scan
Some fraudsters sidestep file forensics by submitting an image — a screenshot of "online banking" or a photo of a "printed" statement. Understand what this means for verification: an image has no digital paper trail. No revision history, no font data, no metadata worth the name. That cuts both ways — you can't prove tampering from the file, and the applicant chose the one format that can't be verified.
My rule, and the rule at most serious screening firms: an image where a PDF should exist is itself a finding. Every bank issues PDF statements. Ask for the PDF. Fraudsters mostly disappear at that request; honest applicants press two buttons in their banking app.
The check that needs no software
Before any forensics: re-do the arithmetic. Take the opening balance, walk every transaction, confirm the running balance column and the closing figure. Template users type transactions carelessly, and editors change one number while forgetting the three totals it feeds. It's astonishing how often the maths simply doesn't work. Five minutes, a calculator, no tools.
The only check that's final
Everything above tells you which documents deserve suspicion. It cannot certify one genuine — a careful fabrication with no editing history can pass file checks, and even a digital signature only proves what it proves. For decisions that matter, the last step is always verification at the source: ask the applicant for a read-only confirmation through their bank, or for the statement to be sent directly. A fraudster can survive an eye test. Surviving the issuer is much harder.
Upload a statement to the free checker and you'll get the full file analysis in about twenty seconds: recovered revisions, software trail, font verification against 70,000+ references, typography anomalies located on the page. Documents stay private to your account and auto-delete within 15 days.