Skip to main content
How-To · 6 min read

I Suspect a Bank Statement Is Fake: What Can I Check Without Any Software?

Five checks need no software: recompute the running balance on sample rows, compare fonts and alignment, read the PDF properties, test the pattern against normal activity, and look for impossible dates.

Terra Insight
Terra Insight Editorial Team Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 14 October 2026
Domain expertise
TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops
Knowledge Card
Problem

An analyst suspects a bank statement PDF has been altered but has no forensic software available.

How It's Resolved

Run five quick checks: running balance on sample rows, fonts and alignment, PDF properties, activity pattern, and dates against bank holidays.

Configuration

The original PDF as received, a calculator, a PDF reader that shows document properties, and the RBI holiday list for the period.

Output

A pass or escalate result for each check, recorded in the credit file, with any failing file sent for forensic review.

You can run five useful checks on a suspect bank statement without any software. Recompute the running balance on a few sample rows, compare fonts and alignment, read the PDF properties, test the pattern against normal activity, and look for impossible dates. These catch crude edits. They will not catch every careful one, so a file that fails any check should go for forensic review.

These are detection steps only. They help you decide whether to trust a document; they say nothing about how a document might be changed.

What are the five manual checks?

CheckWhat to look forMinutes neededReading that means escalate
1. Running balancePrevious balance + credit − debit = printed balance5 to 10Any row that does not add up
2. Fonts and alignmentSame font, size and column position on every row3 to 5One row or figure that looks different
3. PDF propertiesCreator, producer, created and modified dates2An editing tool named, or a modified date later than created
4. Activity patternSalary or sales arrive on a regular rhythm5 to 10Income that suddenly changes with no reason
5. Impossible datesCheque clearing or branch entries on holidays or Sundays5Branch cash or cheque clearing on a closed day

A few notes on each:

  1. Running balance. Pick 10 to 15 rows across different pages, including the first and last row of each page.
  2. Fonts. Zoom in to 200% on amounts. Edited digits often sit slightly higher, lower or bolder than their neighbours.
  3. PDF properties. In most PDF readers this is under File, then Properties. A genuine net-banking download usually names the bank’s own reporting system.
  4. Pattern. A ₹45,000 salary that becomes ₹85,000 in the last two months without a new employer name in the narration needs a payslip.
  5. Dates. UPI and IMPS work every day, so digital entries on holidays are normal. Cheque clearing and branch cash on a national holiday are not.

When should you stop checking by hand?

Stop and refer when:

  • any running balance row fails;
  • PDF properties name an editing tool;
  • two or more of the other checks raise doubts;
  • the file is a scan and you cannot run checks 2 and 3 at all.

Also stop when volume makes manual work unrealistic. Checking every row of a twelve-month business statement with 2,000 entries by hand is not practical.

Worked example: a ₹1,000 break

Three consecutive rows from a statement:

DateNarrationDebitCreditPrinted balance
10 AugOpening for the row block₹48,200
11 AugNEFT from customer₹15,000₹63,200
12 AugUPI to supplier₹6,300₹57,900

Work it out: ₹48,200 + ₹15,000 = ₹63,200, which matches. Then ₹63,200 − ₹6,300 = ₹56,900. The statement prints ₹57,900, which is ₹1,000 higher. Genuine bank systems do not make this kind of error, so the file is referred. The break sits between the 11 August row, which is correct, and the 12 August row, which is not.

The running balance check is the most useful single test, so read how to check the running balance of a bank statement by hand next. For what careful edits look like, see PDF tampering detection for bank statements and bank statement PDF metadata inspection.

A bank statement analyzer runs these checks on every row of every file. TransactIQ, a managed service on Terra Insight’s AWS Mumbai infrastructure, includes fraud and anomaly signals among its 40+ engineered credit signals, each rule-traceable for your credit team.

Primary reference: Reserve Bank of India Master Directions — which set fraud risk management expectations for regulated lenders.

Frequently Asked Questions

Can I prove a statement is fake without software?
You can find strong signs, such as a broken running balance, but a final finding should come from your lender's fraud or forensic review process.
Which check should I do first?
The running balance check. It takes a few minutes and a single broken row is strong evidence of a problem.
Is a scanned statement automatically suspicious?
No. Many genuine statements are scans of branch printouts. A scan simply hides some signs, so ask for a net-banking download where possible.
What should I look for in PDF properties?
Look at the creator and producer fields and the created and modified dates. A bank-generated file usually names the bank's own system, and the modified date should match the created date.
What if the applicant offers to email a new copy?
Prefer a statement fetched through the Account Aggregator framework or downloaded in your presence, which comes directly from the bank.

See how TransactIG handles reconciliation for your industry

Configuration takes 2–4 weeks. No code development required. ISO 27001:2022 certified.