How to Spot a Fake or Edited Bank Statement

Forged statements are common in lending and rental applications. The arithmetic checks that catch them, and why edited PDFs usually fail them.

If you assess bank statements — as a lender, a landlord, an employer or an accountant — you will encounter edited ones. Modern PDF editors make the visual side easy: fonts match, alignment is perfect, nothing looks wrong.

What forgers consistently fail to do is keep the arithmetic consistent. A bank statement is a chain of dependent numbers, and changing one correctly means changing many.

The five checks that catch most forgeries

1. Walk the balance chain

For every row: previous balance, minus debit, plus credit, should equal this row's balance. Delete a transaction and every subsequent balance is wrong. Forgers who delete a row rarely rewrite the entire remaining balance column.

2. Compare rows against printed totals

Statements print total debits and total credits. Sum the rows and compare. An inserted deposit that wasn't added to the summary shows up immediately.

3. Check the closing balance against the last row

The balance on the final transaction should equal the closing balance in the summary box. Inflating the summary without touching the rows is one of the most common manipulations, and one of the easiest to catch.

4. Check date ordering against balance ordering

Transactions run chronologically and balances follow that order. An edited date frequently produces a row whose balance belongs somewhere else in the sequence.

5. Look at the PDF metadata

Genuine bank statements are generated by the bank's own systems and their metadata reflects that. A statement whose producer field names a consumer PDF editor, or whose modification date is much later than its creation date, deserves a much closer look.

Why this is hard to do by eye

On a 200-row statement, checking every balance by hand is an hour's work and mind-numbing enough that attention slips exactly where it matters. This is genuinely a job for a machine — not because the check is clever, but because it's repetitive and unforgiving.

Every conversion we run walks the full balance chain and compares against every printed total, and Verify transactions shows you the result. We've tested this against deliberately edited documents — deleted rows, altered dates, contradictory summaries — and arithmetic inconsistency is a remarkably reliable tell.

Frequently asked questions

Can a forgery be arithmetically perfect?

Yes, if someone rewrites the whole balance column and both summary totals consistently. It's rare, because it's tedious and one slip gives it away.

Does this work on scanned statements?

The arithmetic checks work on whatever is extracted, but OCR errors can cause false alarms. Metadata checks don't apply to a scan at all.

Convert a statement now

Bank Statement PDF to Excel, or see every format. More in the guides.