# Bank Error on Bank Statement: Prove It and Get It Fixed

- Author: PreciseBankFlow (https://precisebankflow.com)
- Published: 2026-10-17
- Category: Finding reconciliation errors
- Canonical: https://precisebankflow.com/blog/bank-error-on-bank-statement

> What to do about a bank error on a bank statement: proving it, reporting deadlines, showing it on the reconciliation until the bank corrects it.
A bank error on a bank statement is a line the bank recorded wrongly, such as a debit posted twice or a deposit credited for the wrong amount. Prove it with your own source documents, report it in writing within the deadline that applies, and carry it on the bank side of the reconciliation until the bank corrects it.

## Is it really a bank error on the statement?

Before you call anything a bank error, rule out your own books. Most differences that look like the bank's fault turn out to be ledger mistakes, timing items or transactions someone at your end authorised and forgot. A true bank error survives a comparison with your source documents, not just with your ledger.

Ask four questions about the line that looks wrong:

1. **Does the source document agree with the statement?** If the deposit slip says $2,140.00 and the statement says $2,140.00, the ledger's $2,410.00 is your error, however sure you were.
2. **Could it be timing?** A deposit made late on the last day may post on the next statement. A check written in one month can clear months later.
3. **Did someone else at your end start it?** An automatic payment set up by a colleague, a card charge from a renewed subscription or a transfer between your own accounts can all look unfamiliar.
4. **Is the gap tiny?** A difference of a few cents is more often rounding in interest or a fee than a bank mistake. The usual sources of those are covered in [why a reconciliation is off by a few cents](/blog/reconciliation-off-by-a-few-cents).

If the statement disagrees with a source document you trust, you probably have a bank error. Common types include the same debit posted twice, a deposit encoded for the wrong amount, a check paid for more than its written amount, a transaction belonging to a different customer, and a fee charged at a rate that does not match the account agreement.

Also check the statement's opening balance against last month's closing balance. If the bank's own figures do not carry forward, the problem is in the bank's statement, not your reconciliation. If instead your reconciliation's opening figure has drifted away from the statement, see [what to do when the beginning balance does not match the bank statement](/blog/beginning-balance-does-not-match-bank-statement), because that is almost always a change on your side.

## Evidence that proves a bank statement error

Evidence of a bank error is any record, created outside the bank's posting system, that shows what the transaction should have been. A bank will want a document it can check against its own records, not your ledger, which only shows what you believed. The stronger the document, the faster the correction.

Gather what fits the error:

- **Deposit errors:** the validated deposit slip or receipt, a remote deposit confirmation, the image of each deposited check.
- **Check errors:** the paid check image from the bank, your check register entry and, if you have it, the vendor's receipt or invoice for the written amount.
- **Duplicate debits:** both statement lines, with dates, amounts and reference numbers, and the single invoice or authorisation behind them.
- **Electronic payment errors:** the payment confirmation, the authorisation you gave, and the trace or reference number the statement prints.
- **Fee errors:** the fee schedule or account agreement page that sets the rate, and the line that departs from it.

Put the case on one page: account number, statement date, the line in dispute, what it should have been, the difference and the documents attached. A bank officer handling dozens of claims can act on a page like that without calling you back.

## Reporting deadlines for a bank error: consumer and business accounts

The reporting deadline is the time you have to notify the bank before you lose some or all of your right to a correction. It depends on the account type and the kind of transaction. Electronic transfers on consumer accounts follow federal rules; checks follow state law, and business accounts rely mostly on state law and the deposit agreement.

For consumer accounts, Regulation E covers electronic fund transfers such as debit card, ACH and ATM transactions. Under [the CFPB's text of Regulation E, section 1005.11](https://www.consumerfinance.gov/rules-policy/regulations/1005/11/), the bank must receive notice of the error no later than 60 days after it sends the statement on which the error first appeared. The bank then has 10 business days to decide whether an error occurred. It may take up to 45 days if it provisionally credits the account for the disputed amount within those first 10 business days.

For checks on any account, the rules come from Article 4 of the Uniform Commercial Code as adopted by each state, plus the account agreement. Regulation E does not cover business accounts, so for their electronic payments the deposit agreement sets the notice period. [UCC section 4-406, published by Cornell's Legal Information Institute](https://www.law.cornell.edu/ucc/4/4-406), requires the customer to exercise reasonable promptness in examining the statement. It sets an outside limit: a customer who does not discover and report an unauthorized signature or an alteration within one year after the statement is made available is barred from asserting it against the bank. The deposit agreement can set its own notice periods, so read the one for your account.

The practical rule is simple. Report in writing as soon as you find the error, during the same month-end close if you can. Keep a copy of the notice and the date you sent it. A reconciliation done promptly each month is what makes these deadlines easy to meet.

## Showing an uncorrected bank error on the reconciliation

An uncorrected bank error is shown on the bank side of the reconciliation as an adjustment to the statement balance. You do not change the books, because the books are right. The item stays on the reconciliation each month until the bank's correction appears on a statement.

The direction follows the error. If the bank took too much out, add the amount back to the bank balance. If the bank credited too much, subtract it. Label the item with what happened, when you reported it and to whom.

### A worked reconciliation with a duplicate bank debit

The figures are an example. A company's April statement closes at $26,415.80. The bank posted a $1,250.00 vendor ACH payment twice on April 12. The company authorised one payment.

| Line | Amount |
| --- | --- |
| Balance per bank statement, April 30 | $26,415.80 |
| Add: deposit in transit, April 30 | $3,180.00 |
| Less: outstanding checks 2214 and 2219 | ($1,906.40) |
| Add: bank error, duplicate ACH debit April 12, reported in writing May 2 | $1,250.00 |
| Adjusted bank balance | $28,939.40 |
| Balance per books, April 30 | $28,964.40 |
| Less: April service charge not yet booked | ($25.00) |
| Adjusted book balance | $28,939.40 |

The service charge is a book-side item, so it gets a journal entry. The duplicate debit is a bank-side item, so it does not. When the bank reverses the duplicate on the May statement, the reversal and the duplicate offset each other and the item drops off the May reconciliation.

One trap: do not book the duplicate and then book the bank's refund. That records two entries for something that never happened in your business, and anyone reading the cash account later sees a payment and a receipt with no invoice behind either.

## What if the bank will not correct the statement error?

If the bank refuses to correct an item you believe is wrong, ask for its decision in writing, with the documents it relied on. Then decide whether to escalate or to accept that your own records were wrong. The open item cannot sit on the reconciliation forever.

Under Regulation E, a bank that finds no error must explain its findings in writing, and it must send a consumer copies of the documents it relied on when asked. A business has no matching federal right for most transactions, but a written request through the relationship manager or branch manager usually gets a fuller answer than the first phone call.

Then compare the bank's evidence with yours. If the paid check image shows the amount the bank charged, and your register shows a different one, the register was probably wrong. If the bank's documents do not support its position, escalate: first a written complaint to the bank, then to the agency that supervises it. For a large amount, a business may also need legal advice.

At some point the item has to leave the reconciliation. If you accept the bank's position, move the amount to the book side and record it as a loss or an expense, with the bank's letter as support. Keep a list of every open bank-error item with its report date, so a reviewer can see none has been parked for months without follow-up.

## When a suspected bank error turns out to be fraud

A suspected bank error is sometimes not an error at all but a payment someone made on purpose without authority: a forged or altered check, an ACH debit from a party you never authorised, or a transfer by an insider. The handling changes, because the deadlines are short and the evidence must be preserved.

Signs that point away from a simple error include a payee you have never paid, a check number used twice with different payees, round-dollar debits repeated across months, and an altered check image where the payee line or amount looks rewritten. If an employee prepares the reconciliation and also has payment authority, an "error" they explain away deserves a second look by someone else.

When fraud is possible, report it to the bank as unauthorized, not as an error, and say so in writing. Keep the original statements and images unchanged. Stop the reconciler from editing anything in the period. For methods an investigator would use to test the account further, see [fraud detection techniques in forensic accounting](/blog/fraud-detection-techniques-in-forensic-accounting).

Under UCC 4-406, the customer's delay in reviewing statements can shift losses from repeated unauthorized items by the same wrongdoer onto the customer, which is one more reason the monthly review should be done by someone without access to payments.

PreciseBankFlow is designed to flag possible duplicate charges and differences against the statement and list them with their evidence, which gives you the one-page case for the bank sooner. Firms can [ask to join the early access group](/get-started).