Document verification

How Can You Tell If a Bank Statement Has Been Altered?

November 16, 20265 min read

An unusual font or inconsistent balance can justify a closer look, but neither proves a bank statement is fake. Use a repeatable review process that checks the source, reconciles the figures, and escalates unresolved concerns without accusing the client.

1. Start with what the statement can actually prove

You cannot reliably tell whether a bank statement has been altered from its appearance alone. A convincing PDF can contain changed figures, while a genuine statement can look unusual after scanning, translation, or file conversion. The practical approach is to combine visual checks, arithmetic checks, and source verification, then have a staff member decide whether the evidence is sufficient.

First, define why you need the statement. Are you checking an account holder’s name, confirming an account relationship, or reviewing financial activity over a particular period? That purpose determines which details matter. A statement showing the expected name does not, by itself, establish the presenter’s identity or prove that the funds remain available.

Set your acceptance criteria before reviewing individual files. Specify the required period, acceptable formats, necessary pages, and permitted redactions. Bank statements usually have a statement period rather than an expiry date: an older document may be genuine but too old for your process. These are general operational practices, not legal advice; your organization’s applicable obligations and approved policies should guide the final requirements.

Keep authenticity, identity matching, and document recency as separate checks. Passing one does not mean the others have passed.

2. Check the document’s structure and visible details

Start with the whole file before inspecting individual numbers. Confirm that the statement period, account holder, bank name, and page sequence are present where expected. Check whether the file contains all pages needed for your review. A missing page might hide relevant activity, but it could also be an ordinary upload mistake.

Next, look for inconsistencies within the document. A balance printed in a noticeably different font, a name that sits above the surrounding text, or an abrupt change in image quality deserves attention. Compare similar fields within the same statement rather than assuming every bank uses one fixed template. Banks change layouts, and business, personal, and regional statements can differ.

Treat PDF properties and text-selection behavior as supporting clues only. An editing application listed in the metadata is not proof of fraud, and an image-only PDF is not automatically suspicious. Scanning, accessibility tools, and legitimate document processing can all change how a file looks or behaves.

  • Look for inconsistent spacing, alignment, font size, or background shading around names, dates, and balances.
  • Check for clipped text, unexplained blank areas, repeated transaction lines, or broken page numbering.
  • Review date formats and account identifiers for unexplained changes between pages.
  • Note the exact page and field involved rather than writing a vague comment such as “looks fake.”

3. Reconcile the figures without making assumptions

Arithmetic checks can reveal inconsistencies that visual inspection misses. Where the statement provides the necessary totals, test whether opening balance plus credits minus debits equals closing balance. Use the bank’s labels carefully: fees, interest, overdrafts, and separate account sections can affect how figures are presented. Do not count a fee twice if it already appears in total debits.

If the statement shows running balances, check whether each listed transaction changes the balance as expected. If you have consecutive statements for the same account, compare one period’s closing balance with the next period’s opening balance. Investigate discrepancies, but first check for missing pages, overlapping periods, different currencies, or a corrected statement.

Avoid treating unusual financial behavior as evidence of document alteration. A large deposit, round-number payment, or low balance may matter to your business assessment, but it does not prove the file was edited. Keep two questions separate: “Do these figures reconcile?” and “Does this activity meet our acceptance criteria?” A mathematically consistent statement can still be fabricated, so reconciliation is a screening step, not authentication.

If text extraction or a spreadsheet produces a mismatch, compare the result with the visible document before escalating. Extraction errors can misread decimal points, minus signs, and column positions.

4. Resolve concerns through a trustworthy source

When a concern remains, choose a proportionate verification step. If your process allows it, ask for a fresh statement downloaded from the bank’s authenticated portal rather than another screenshot or edited copy. This can reduce conversion problems and missing information, but a client-provided download is still not independent proof of authenticity.

For higher-risk cases, use an approved independent verification route where available, with any required client authorization. Obtain the bank’s contact details independently rather than relying only on a phone number or link printed on the questionable statement. The bank may not disclose information to you, and a refusal or lack of response does not establish that the document is false.

Keep communications neutral and specific. Explain which detail cannot be reconciled and what evidence would resolve it. Do not ask for online banking passwords, one-time codes, or unrestricted account access. Limit additional collection to what your review needs, and avoid uploading financial records to unapproved online “fake document detectors.” Those tools can introduce privacy risks without providing a dependable answer.

  • Use a clearer or complete copy when the problem is readability or missing pages.
  • Use an approved source-verification process when the concern is possible alteration.
  • Escalate unresolved, material discrepancies to a designated reviewer.
  • Follow your retention and access policies for the original file and any supporting evidence.

5. Make the review decision consistent and auditable

Give reviewers a short checklist and clear outcomes: accepted, pending clarification, escalated, or not accepted under policy. Record what was checked, the specific concern, the evidence considered, and who made the decision. “Could not verify” and “confirmed alteration” are different conclusions; do not use them interchangeably. Where practical, have a second reviewer assess material concerns before taking an adverse action.

DocumentLane can support the intake stage by sending clients a document checklist with a secure upload link. Its AI checks uploaded documents for the right type, correct name, whether they are expired, and signs of tampering. These checks can help staff identify files needing attention, but a tampering flag is not proof of fraud, and staff make the final approval.

The goal is not to turn every reviewer into a forensic examiner. It is to catch inconsistencies, avoid unfair assumptions, and know when routine screening is insufficient. A clean-looking file should not bypass your checks, and an awkward-looking file should not automatically fail them. Use the same evidence-based process for both.

Frequently asked questions

Can a PDF bank statement be edited?

Yes. PDF format does not prevent changes to text, figures, or images. A professional-looking file is not proof of authenticity; combine document checks with source verification when needed.

Does a screenshot prove that a bank statement is fake?

No. A screenshot may be genuine, but it can omit pages and context. Decide whether it meets your acceptance criteria rather than treating the format alone as evidence of fraud.

Can AI confirm that a bank statement is genuine?

AI can flag possible inconsistencies or tampering, but it cannot guarantee authenticity. Staff should assess flags, consider legitimate explanations, and use an approved verification route when the risk warrants it.

Stop chasing subcontractor COIs.

Send a COI checklist with a secure upload link, review what comes back, and let expiry reminders go out on their own. Registration is invite-only.

Request early access

Free: the two-page subcontractor COI checklist

What to collect before a sub mobilizes, how to read a certificate in sixty seconds, and a short version to send with the contract.

Get the checklist

Keep reading

Questions about your own requirements? Email hello@documentlane.ai.