Forgery detection for bank statements and transaction histories
We detect: edited transactions or amounts · running-balance breaks · deleted or inserted rows · swapped pages · dates that contradict the weekday · edited account-holder details. Current accounts and credit cards, every bank.
| 01.09 | Salary | +14,200 | 18,450 |
| 03.09 | Rent | -5,600 | 12,850 |
| 07.09 | Deposit | +19,000 | 21,850 |
| 10.09 | Card | -3,120 | 18,730 |
What we check
- Running-balance continuity, row by row
- Row height, fonts, column and decimal alignment
- Value and transaction dates versus weekdays
- Account holder, bank code and branch
- Pages added, swapped or re-saved
- Credit-card statements and current-account histories
Forgery types we detect
- 01
Inflated income
A salary or deposit increased — and the following balances not updated, or updated with an arithmetic slip.
- 02
Deleted debts
Loan repayments or charges removed, with the table "closed" leaving a suspicious gap.
- 03
Swapped page
One page from another file with a different font, resolution or issue date.
Bank statements
How many pages can you check?
The whole PDF is checked; continuity runs over every transaction we extract.
Does it work on scanned statements?
Yes, though scanning limits file-structure checks. Logic and visual review still apply.
Can I compare against an expected income?
Yes — enter an expected amount and we check whether it appears.
Have a document like this to check?
10 free checks every month. No credit card.