The federal clock doesn't start on a sharp question. You need a qualifying notice first. That notice carries your name, the account, and why you believe an error exists. A status question is not that notice.
Regulation E lets you call or write. It covers debit purchases, ATM withdrawals, ACH debits, many prepaid transactions, and qualifying person-to-person payments. Credit cards follow a stricter rule, and Regulation Z is the one that covers open-end credit billing errors. Written notice has to be received within 60 days after the statement that first showed the error. The bank's form is not the on-switch.
Ordinary wires and merchant refund policies do not start either clock, no matter how often you raise them on a call. Where do most of these disputes stall? On what counts as a real notice, and on what never opens a file.
How a bank error dispute actually starts
Federal rules do not park a disputed charge as a complaint ticket. They turn a qualifying notice into a clock the bank has to run.
Two regulations do that work. They cover different rails. Thing is, the rail decides the file.
Regulation E, in 12 CFR Part 1005, covers electronic fund transfers, including debit purchases, ATM withdrawals, ACH debits, many prepaid transactions, and qualifying person-to-person payments. That is the debit side of it. Regulation Z, 12 CFR 1026.13, covers billing errors on open-end credit. A qualifying call can open an EFT file. It won't open the credit-card one.
A merchant refund policy doesn't start either clock, and a card-network chargeback doesn't replace the federal process. Ordinary wires sit outside Regulation E, and remittance transfers use a separate subpart, so don't carry the debit deadlines over to either rail. Keep each clock on its rail.
You can call or write for an EFT error. The notice needs your name, the account number, and why you believe an error exists. Include the type, date, and amount if you can. The bank may still ask for an affidavit, but it must investigate anyway, and the clock starts when the notice is received rather than when you mail the form back. You don't have to wait on that form.
Credit cards are stricter. Regulation Z wants a written notice, received within 60 days after the creditor sent the first statement that shows the error. A phone call won't start that clock.
Not every gripe qualifies, even when the charge annoys you. Unauthorized use does count. A wrong amount counts too, and so does a missing credit, a bookkeeping mistake, or a short ATM payout. Say why you believe an error exists.
Goods you refused, or goods that were not delivered as agreed, can be a billing error on a credit card. Quality complaints after you accepted the goods aren't covered. Acceptance is a state-law question. It gets awkward if you only wanted the charge gone.
Key Metrics / Benchmark Ticker
| Rail | Notice window | First deadline | Outer limit | Money during review |
|---|---|---|---|---|
| Debit, ACH, prepaid, covered P2P (Reg E) | 60 days after the statement is sent | 10 business days (20 for a new account) | 45 days, or 90 in set cases | Provisional credit within 10 business days to extend (20 if new) |
| Credit card billing error (Reg Z) | Written notice received within 60 days of sending | Acknowledge in 30 days unless resolved | 2 billing cycles, never past 90 days | Disputed amount and related charges generally stay uncollected |
Debit, ACH, prepaid, and covered P2P live on the first row. You get 60 days after the statement is sent to put the bank on notice. After that, 10 business days is the first deadline, unless the account is new, in which case it is 20. Many files can run to 45 days once provisional credit is posted within those 10 business days. Set cases stretch the outer limit to 90. A new account gets 20 days for that provisional credit.
Credit-card billing errors are the second row, and the notice has to be written. It must be received within 60 days of sending. The creditor has 30 days to acknowledge unless the error is already resolved. The review can take 2 billing cycles, but it never runs past 90 days. The disputed amount and related charges generally stay uncollected during that time.
New account, for the 20-day figure, means the transfer fell within 30 days after the first deposit. Use that definition, not a guess. The 90-day cap also covers point-of-sale debit and transfers started outside the United States.
Skip a required written confirmation and provisional credit can be withheld, though the investigation still runs. Those numbers come from the regulation, not from a bank promise.
Finding an EFT error starts a short correction clock. The correction is due within one business day of that finding. Results go out within three business days after the investigation ends. A skipped form can't pause the start of that review.
Even a no-error result requires a written explanation, and you get a chance to see the documents the bank used. Ask to see those documents. Those duties don't begin if the contact never asserted an error.
When the textbook steps never actually start
You hang up convinced the review is underway. A lot of those calls never left the question stage.
Checking on a payment is not an error notice. If you only ask whether a payment was debited or a deposit was credited, and you never assert an error, the CFPB commentary says the procedures do not apply. Nothing in that call starts the clock.
Someone may type a note on the account. That note is not an error file. Days pass, no letter arrives, and the procedures simply never started.
What the first call actually opened
A lost-card report triggers the process only if you also allege possible unauthorized use, and if you say the card is missing and stop there you may have a fraud flag with no investigation behind it, which is easy to miss if you thought later charges would be covered on their own. You still have to allege unauthorized use.
The duty survives a closed account. On a proper notice, the institution still has to follow the procedures. Restate the error if a rep treats a shut account as the end.
A missing receipt is a separate dead end. On a transfer of $15 or less, no terminal receipt is not an error, so the slip will not carry a dispute.
What you said versus what the file is
What you asserted is what the commentary sorts. The feeling you left with doesn't decide it.
| What you did | What it felt like | What the commentary treats it as | Where it stalls |
|---|---|---|---|
| Asked whether a debit or deposit posted | A dispute was opened | A status check, not an error notice | Inquiry only, so the clock never starts |
| Reported a lost or stolen card and nothing more | Later charges would be covered on their own | Procedures apply only with an unauthorized-use allegation | Theft note only, no error investigation |
| Asked for a statement copy for taxes | The bank must explain the charge | Not an error, if it is clearly a record-keeping copy | The request never opens an error file |
| Sent a proper error notice after the account closed | Closure ended the bank's duty | Procedures still apply to that notice | The file stops unless you restate the error |
Turns out the clean sequence, notice then investigation then correction, assumes the notice already exists, and the first conversation is often a muddle where you don't recognize the charge, or maybe you do recognize it, and you only ask if it posted, which never becomes the assertion the commentary wants. The clock never starts on that ask.
Don't assume this electronic-transfer process controls a wire or a credit-card billing fight. Those are different tracks.
If you actually assert the error, a phone notice can count. Put the transfer, the amount, the date, and the exact problem in one short note, then send it by secure message or to the address on your statement. Keep a copy of that note.
Use that note if the call never became a file. Once the notice exists, count the deadlines from the statement and from the day the bank receives it.
The clock, from the day you notice it
Same-day calls matter on this rail. Oral notice starts a Regulation E review for debit cards, ATM transfers, ACH debits, and many account-linked payments, so call the bank the day you see the error.
Skip the account number if they can still identify you. Still say who you are, how to find the account, the date, the amount, and what looks wrong. The bank must get that notice within 60 days after sending the statement.
- Same day: Report it. Save the reference number, the date, and the name.
- Within 10 business days: The bank must decide or post provisional credit and continue.
- If the review runs long: That credit lets many cases go 45 calendar days. New accounts and some debit or cross-border transfers get longer.
- When they finish: A real error gets corrected. A no-error finding comes in writing. Ask for those documents.
You'll want that reference number if day 10 arrives with no decision and no credit, so save it. Calendar days, not business days, are what the 45-day stretch uses, and it is the extension provisional credit buys in many cases, not a promise that every file runs that long. Some of those transfers get longer.
Regulation Z is the credit-card path. Wires don't use this clock either.
Where people lose time
The bank can ask for a signed statement, and that request is fine. You don't have to wait on it. The investigation starts even if the form is still sitting on your counter.
Miss the written follow-up and they can hold the provisional credit. The review itself still has to move.
A police report is not your ticket into the investigation. Calling the merchant doesn't get you in either. Your carelessness doesn't set liability, and neither a contract nor a card-network rule can shrink it.
A charge you okayed and then regretted usually isn't an error, which is annoying, but it's a refund fight, not this one. Asking if a payment posted, without saying you think it's an error, doesn't open this process.
Business accounts sit outside Regulation E. If a scammer got your login, the CFPB's FAQ treats the transfer as unauthorized. That's different from a payment you sent on purpose.
They can reverse provisional credit after a no-error finding. They have to tell you.
How long do I have to dispute a bank error?
The purchase date is the wrong starting line. Count 60 days from the statement that first listed the error, not from the purchase, and that statement date is what matters. That's the Regulation E window.
Miss it, or report an unauthorized transfer late, and you can lose protection or owe more.
Can my bank make me file a police report first?
No.
A police report can't be a condition of the investigation. The CFPB's FAQ is plain on that.
Do debit disputes have to be in writing?
A call is enough to start the process if they can identify the account, so debit disputes don't have to be in writing. To be honest, skip the written follow-up and they can hold the temporary credit. The investigation should still move.
Can I dispute a bank error after I closed the account?
Yes, if the notice was on time. Closing the account doesn't end the duty.
Keep a copy.
Other consumer payment and billing topics often depend on a different rail. Don't treat a wire or a credit-card billing error as if this same clock applies.
If 10 business days pass with no decision and no credit, call back with the notice date. If they still refuse, complain to the CFPB with that timeline.