Bank statement red flags: a checklist you can actually work through
Most checklists for spotting a forged bank statement are written as if you had an afternoon. You do not — you have the few minutes between receiving the file and having to make a decision. So this one is ordered by cost: the checks that take seconds first, the ones that take a phone call last. Work down it and stop when you have enough.
Thirty seconds: the numbers
Arithmetic is the cheapest evidence there is, and it is where hand-edited statements fail most often, because changing one transaction means changing every running balance below it.
- The running balance must move by exactly the amount of each transaction, line after line. Pick three rows at random in the middle of the statement and check them.
- The closing balance of one month must equal the opening balance of the next. Ask for three consecutive months and this becomes very hard to fake.
- Totals of credits and debits, where the statement prints them, must match the sum of the lines.
- A salary credit should recur on the same working day each month, from the same named payer, for a plausible amount. Round numbers arriving at irregular intervals from a person rather than a company are worth reading twice.
- Look for the mundane. Real accounts have subscriptions, card fees, small refunds, a declined direct debit. A statement composed entirely of large, tidy movements describes a life nobody lives.
Two minutes: the page
- Column alignment: forged rows are typed into a copy of a real one, and the decimal points drift. Hold a straight edge — or the cursor — against the amount column.
- Font weight and spacing inside a single line. When one figure is heavier, narrower or sits a fraction higher than its neighbours, it was pasted rather than printed.
- Date formats that change part-way through the document.
- The header block: sort code, account number, IBAN and address should be internally consistent and consistent with the account holder's other documents.
- Page numbering: "Page 2 of 4" on a four-page file that has a missing sequence, or a statement that starts mid-period.
- Transaction descriptions that read like a person wrote them. Bank systems produce terse, uniform, often abbreviated strings — not tidy sentences.
Two minutes: the file
- Producer and Creator fields naming a word processor, a design tool or an online PDF editor rather than a reporting engine.
- A modification date later than the creation date, especially when the gap is hours or days.
- Incremental update layers — evidence that the file was saved more than once, sometimes with the previous version still recoverable inside it.
- Text that will not select cleanly, or amounts that select as a block of image rather than as characters.
- A file that is a photograph or a screenshot of a statement instead of the statement. This is the most common evasion and the easiest to refuse.
A phone call: the only decisive check
Everything above narrows the odds. Only one thing settles them: getting the same information through a channel the applicant does not control. Ask for a bank-verified connection where the data comes from the bank directly, or ask the applicant to open the statement in their banking app while you watch, or request the file be sent from the bank's own portal rather than forwarded.
Four flags that look damning and are not
- A modification date later than creation. It happens whenever anyone adds a comment, prints to PDF, or re-saves the file unchanged — including the bank's own portal and the applicant's phone.
- A producer field naming a generic PDF library. Plenty of legitimate banking systems and export tools use exactly the same libraries a forger would reach for.
- No digital signature. Most banks do not sign statements at all, so its absence tells you nothing; and a signature only proves the file has not changed since it was signed, not that its contents were ever true.
- A tidy-looking document. Looking right has been free for years. Design quality stopped being a signal well before the generators got good.
This matters more than it sounds. A checklist that treats every anomaly as guilt produces a stream of false accusations against honest applicants — and the person who has been wrongly refused remembers it far longer than the fraudster you caught.