Bank Statement Red Flags: What Lenders and Accountants Look For

Below is what a careful lender, underwriter or accountant actually checks, plus how the reconciliation check in Export Bank Statement flags the structural ones before you trust the numbers.

Why people scrutinise bank statements in the first place

A bank statement is one of the few documents that's both easy to ask for and hard to fake convincingly. Lenders use it to verify income and spending. Accountants and bookkeepers use it as the source of truth their books have to match. Mortgage brokers, landlords and grant assessors lean on it for the same reason: it's a running record meant to be internally consistent.

That consistency is the weak point for anyone tampering with one. Change a single number and the running balance downstream stops making sense, unless you also edit every line after it. Most fakes don't. So the first thing to look at isn't the design. It's the arithmetic.

The red flags worth checking, in order

Here are the signs that pull a statement out of the "fine" pile. None is proof on its own. Two or three together is your cue to dig.

• The running balance doesn't reconcile. Take the opening balance, add every credit, subtract every debit, and you should land exactly on the closing balance. If you don't, a line was added, removed or altered. This is the strongest signal there is, because it's maths, not opinion.
• Round-number deposits. Real income is messy. Salary lands as 2,847.33, not 3,000.00. A run of suspiciously clean 500 or 1,000 credits, especially right before an application, deserves a closer look.
• Missing transactions. A gap where a regular payment should be (rent, a recurring direct debit, a loan repayment) can mean the line was deleted to hide an outgoing, or that the statement was cropped.
• Font and alignment mismatches. Banks generate statements from one template. If one transaction row uses a slightly different font, weight, or spacing, or the decimal points don't line up down the column, someone typed over the original.
• Inconsistent date formatting. Real statements use one date format throughout. A mix of 03/06/2026 and 3 Jun 26 in the same table is a classic edit tell.
• Balances that go negative without an overdraft, or impossible jumps. A balance that dips below zero on an account with no overdraft facility, or leaps by a large amount with no matching credit line, points to a deleted or fabricated entry.
• Mismatched account or contact details. Sort code, account number, address or bank logo that don't match the customer's other documents, or the bank's real current branding.
• PDF metadata that doesn't fit. A statement "from the bank" whose PDF properties show it was last saved in a photo editor, or created years after the statement date, is a problem.
• Totals that don't match the lines. A summary box claiming "total credits 8,200" when the transactions add to 7,950 means the summary and the detail were edited separately.
• Transactions out of chronological order. Genuine statements are time-ordered. A line that sits in the wrong place was usually inserted by hand.

If you only have time for one check, make it the first. A statement that reconciles can still be off in other ways, but one that won't reconcile is wrong, full stop, whether the cause is fraud or a scanning glitch.

How reconciliation exposes tampering and missing lines

This is where checking the maths beats checking the look of a document. A doctored statement and one with a quietly dropped transaction fail the same test: the running balance no longer ties out.

Export Bank Statement is built around that test. When you upload a PDF, it doesn't just pull the transactions into a spreadsheet. It treats the running-balance column as a checksum and verifies opening balance plus money in minus money out against the stated closing balance, line by line. If a transaction was deleted, edited or misread during extraction, the totals stop matching and the statement is flagged before you rely on it.

Be clear on what that does and doesn't prove. The reconciliation check is a completeness and consistency test, not a fraud verdict. It reliably tells you when the numbers don't hold together, which is the structural footprint that crude tampering and missing lines leave behind. It won't catch a sophisticated forgery where every downstream balance was also recalculated, and it can't confirm a statement is genuine, only that the arithmetic is internally consistent. Used properly, it narrows your manual review down to the statements that warrant it.

That's also why it earns its keep on honest documents. Most "doesn't reconcile" flags I've seen aren't fraud at all. They're a misread figure on a scanned page, a transaction lost off the bottom of page six, or a 1,180 that should have read 1,780. Catching that now is the difference between clean books and chasing a hole through your accounts a fortnight later.

What the analyser surfaces beyond the balance check

Reconciliation tells you the statement is complete and consistent. The built-in analyser tells you what's actually in it, which is where the softer red flags live.

• Income verification. It picks out recurring credits, so a salary that swings wildly month to month, or appears only just before an application, stands out.
• Recurring payment detection. Regular outgoings get grouped, so a missing rent or loan payment, or a new gambling pattern, is easy to spot. Same ground as detecting undisclosed debt.
• Expense categories and merchants. Spending sorted by category and counterparty, which makes unusual concentrations or out-of-character transactions visible.
• Cash flow over the period. An in-versus-out view that shows whether an account is as healthy as its closing balance suggests.

For a fuller walkthrough, there's a companion guide on how to analyse a bank statement, and one on financial behaviour analysis if you're assessing risk rather than just bookkeeping.

A practical review routine

When a statement lands on my desk and I need to trust it, this is the order I work in.

1. Reconcile first. Convert the PDF and let the running-balance check run. If it doesn't tie out, find out why before anything else.
2. Scan for round numbers and gaps. Look down the credits for unnaturally clean figures, and the debits for regular payments that should be there and aren't.
3. Check the formatting. One look down the amount column for alignment, fonts and date consistency. Edits usually announce themselves here.
4. Cross-check the details. Sort code, account number, address and branding against the customer's other documents.

Converting and reconciling front-loads the pure-arithmetic part, so your attention goes to the judgement calls.

One note on how the tool fits in: you convert the PDF to clean Excel or CSV, and where the destination is Xero, QuickBooks or Zoho Books you export their native bank-import CSV and import it as reconcilable statement lines. It's a convert-then-import path, not a live bank-feed connection, and it doesn't pretend to be one. Files are processed then deleted immediately, and never used to train AI.