How to Spot a Fake Bank Statement (the Test Most Checkers Miss)

If you lend money, rent property, hire staff or approve invoices, you have almost certainly been handed a bank statement as proof — and some of them are fake. The uncomfortable part: the usual "is this PDF edited?" tools wave most fakes straight through. A forger no longer edits a real statement; they type a fresh one in a template and export a clean PDF. Structurally it is spotless. But there is one thing forgers almost always get wrong, and it is not in the metadata. It is the maths. Here is the test that catches them, and how to run it on any statement for free.

Why metadata checks miss fake statements

Most fraud checks inspect the file: the producing software, the edit history, whether anything was changed after it was saved. Those checks are genuinely useful for a document that was altered — someone opening a real statement and changing a number. But a modern fake is not altered. It is built fraudulent from the first byte, typed into a lookalike template and exported once, cleanly. It has no suspicious edit history because it was never edited.

So a statement can pass every structural test and still be completely invented. Relying on "no signs of tampering" gives you false confidence. To catch a clean fake you have to stop looking at the file and start looking at what the numbers inside it claim.

The running-balance test

Every real bank statement has a running balance: after each transaction, the balance column shows the new total. That column is a chain — each figure must equal the one above it, plus any money in, minus any money out. It is simple arithmetic, and on a genuine statement it always holds, on every single row.

Forgers trip on this constantly. They change one transaction to inflate an income figure, or drop a payment to hide a debt, but they forget to re-compute every balance below it. The result is a statement where, somewhere in the middle, the balance stops adding up: the printed figure no longer matches the previous balance plus or minus that row's amount. A human skimming the page never notices. The maths does.

How to check it yourself

By hand: pick any row, take the balance on the line above it, add the credit or subtract the debit on the current row, and confirm it equals the balance printed on that row. Repeat down the page. If every row reconciles, the ledger is internally consistent; if one row breaks, ask why. Also sanity-check the opening and closing balances against the summary box, and confirm the totals of all credits and debits match any stated totals.

That is slow and error-prone across a 24-page statement, which is why it usually gets skipped. The point of automating it is simply that a computer will check every row, every time, without getting bored on page 19 — which is exactly where a forger hides the break.

Check a statement free on PDF Verified

PDF Verified now runs this arithmetic automatically. Drop a bank statement (or any ledger, invoice history or account summary) on the verify page and it extracts the running-balance column and re-checks the maths for you. If every row reconciles, you get a green "running balance reconciles across N transactions" result. If a row does not add up, it names the exact row, shows the balance it expected versus the balance printed, and flags the file as high risk — the tell-tale sign the figures were altered.

It runs alongside the structural forensics (edit history, producing software, incremental changes) and an AI-origin check that reads Content Credentials (C2PA) and AI-tool markers, so you get the file-level and the content-level picture in one report you can download. It is honest about its limits, too: the arithmetic check is layout-dependent, and a hash match against a sealed original is still the only absolute proof — but for an unsealed statement someone hands you, the balance test is the single most useful thing you can run.

For lenders, landlords and finance teams

If you assess bank statements at any volume — loan and credit applications, tenant referencing, KYC onboarding, expense and invoice approval — the running-balance test belongs in your first-pass screen. It is fast, it needs no special software, and it catches the specific fraud that structural checks cannot: the clean, typed-from-scratch fake. Pair it with the usual identity and affordability checks and you close the gap that most document-fraud tools leave wide open.

And when you are the one issuing documents people must trust — payslips, letters, statements of account — sealing them on PDF Verified gives every recipient a public verification link and a tamper-evident hash, so they can confirm your document is the genuine original in seconds, and cannot quietly forge a copy of it.