How to Catch Bank Errors and Unauthorized Charges
The reliable way to catch bank errors and unauthorized charges is to keep your own transaction log and compare it, line by line, against your bank statement on a regular schedule. Scanning your bank app's pending list and assuming it's correct isn't enough. A duplicate charge, a miscoded fee, or a fraudulent purchase can sit unnoticed for weeks if the only record you're checking is the one the bank itself produced.
None of this is about distrusting your bank. It's about having an independent record. If the only account of what you spent lives inside the bank's own app, you have no way to notice when that record is wrong, since you'd just be comparing the bank's numbers to the bank's numbers. A separate, self-maintained ledger gives you something to check the statement against, which is the entire point of catching an error instead of just seeing a balance and moving on.
Why the bank app alone won't catch these problems
Banking apps are good at showing you what's happened. They're not designed to flag what shouldn't have happened. A pending charge that posts twice, a subscription that renewed at the wrong price, a $4 'convenience fee' you never agreed to: none of these trigger an alert from the bank, because from the bank's side, the transaction looks like any other.
The app shows you a number. It doesn't tell you whether that number matches what you actually authorized.
There's also a timing problem. Pending charges can change amount or disappear before they settle, and pending and cleared aren't the same thing. If you're only glancing at pending activity, you can miss a charge that posts for a different amount than what was authorized, or miss that a pending authorization never cleared at all when it should have. Fraud, in particular, tends to hide in the gap between 'I glanced at my balance' and 'I actually checked every transaction against what I expect to see there.'
The core method: keep your own running ledger
The habit that catches these problems is simple to describe, even if it takes discipline to maintain: record every transaction yourself, as close to the time it happens as possible, with the date, payee, and amount. This becomes your source of truth: a list of what you believe should show up on the statement, written down before you see what the bank says actually happened.
It's the same principle behind a checkbook register, a running record you keep yourself, separate from any single institution's version of events. The value isn't nostalgia for paper checks. It's that a second, independent record is the only thing that lets you notice when the bank's record and your record disagree.
Comparing your log against the statement
Once you have your own log, the comparison itself is a line-by-line reconciliation: go down your list, find the matching entry on the bank statement, and mark it off when the two agree. Anything on the statement you can't match to something in your own log is worth stopping on. Anything in your log that never shows up on the statement is worth stopping on too.
We cover the mechanics of that process, entering a statement ending balance, ticking off cleared items, watching the difference shrink to zero, in detail in how to reconcile a bank statement step by step, so we won't repeat the full walkthrough here. What matters for this habit specifically is what you're looking for while you do it: not just 'does this balance,' but 'does every single line belong to me.'
What a running difference during reconciliation is telling you
When your running total and the statement don't match at the end, the mismatch is a symptom, and different symptoms point to different causes:
- A small, consistent gap that traces back to one missing entry, a transaction you forgot to log or a fee you didn't know about, is usually just an incomplete ledger. Add the missing line and the difference disappears.
- A statement entry with a payee, date, or amount that doesn't match anything you recognize, and that you're certain you didn't authorize, is a candidate for an unauthorized charge rather than a bookkeeping gap.
- A transaction that appears twice, or one where the posted amount differs from what you were quoted or authorized at the time of purchase, points toward a bank or merchant processing error rather than fraud.
- A check or transfer that cleared for a different amount than what you wrote down is worth checking against the original receipt or confirmation before assuming either side made a mistake.
The distinction matters because it changes what you do next. A missing entry is fixed by updating your own records. A charge you don't recognize or didn't authorize is a dispute to raise with the bank, not something to resolve by just editing your log to match.
What to do once you've found a discrepancy
Before contacting anyone, write down what you found while it's fresh: the date and amount on the statement, the payee name exactly as it appears, and why it doesn't match your log, whether it's missing, duplicated, wrong amount, or unrecognized entirely. If you have a receipt, confirmation email, or photo of the original charge, keep it alongside this note. Banks and card issuers generally ask for these specifics when you file a dispute, and having them ready saves a second round of back-and-forth.
Once you've got that written down, contact your bank or card issuer directly. Most have a dispute or fraud reporting process built into their app or available by phone, and they can walk you through their specific timelines and requirements.
It's worth saying plainly that this article can tell you how to spot a discrepancy, but what to do about a specific disputed charge, a specific bank's policies, or a specific fraud case depends on your situation and your institution. That's a conversation for your bank, or where appropriate, a legal or financial professional, not something a general guide can responsibly tell you to do.
Why doing this regularly matters more than doing it well once
A single thorough reconciliation catches whatever has already gone wrong up to that point. Doing it on a regular cadence, monthly, or whenever a new statement arrives, is what catches problems while they're still small and still disputable.
Most banks and card issuers have a limited window for reporting unauthorized charges, so the gap between when something happens and when you notice it isn't neutral. It's the difference between an easy fix and a harder one. How often you reconcile is worth deciding on purpose rather than leaving to whenever you happen to think of it.
Keeping the habit low-friction also makes a real difference. If logging a transaction and reconciling later both take real effort, the habit slips the first busy week.
A register you can update from your phone right after a purchase, with a reconciliation view that shows a live running difference as you tick off cleared items, keeps the whole process closer to a quick check-in than a monthly chore.
LedgerFlow is built around that manual register-and-reconcile habit: you log each transaction yourself, mark items cleared as they settle, and run a reconciliation against your statement ending balance with a live difference and saved reconciliation history. A mismatch shows up as soon as you look, rather than months later.
If you want a straightforward way to keep your own ledger and reconcile it against each statement, LedgerFlow supports that workflow. Download LedgerFlow free on iOS and Android to keep a running balance across all your accounts, reconcile against your statement, and always know what you can actually spend.
Track it all in one place
LedgerFlow keeps a running balance across every account — free on iPhone and Android.