Bank Teller common mistakes
Bank Teller · Understand the traps and how to avoid them.
Counting a cash deposit or withdrawal only once and accepting the customer's stated amount instead of recounting and confirming the figure with the customer before the transaction is finalized.
Candidates rush through routine transactions and treat the customer's verbal amount as authoritative, forgetting that teller shortages and disputes are almost always resolved by an independently verified count.
What to do instead
Practice a fixed counting routine: count each denomination aloud or in view of the customer, recount the total a second time, state the confirmed amount back to the customer, and only then key the transaction. Drill this until it is automatic under time pressure.
Failing to place a hold on a large or unusual check, or releasing funds immediately because the customer is known or insistent, without checking the bank's funds-availability policy.
Candidates confuse good customer service with speed, and they do not know the difference between the regulatory maximum hold periods and their own institution's policy, which is often stricter.
What to do instead
Memorize the hold categories your bank uses (new account, large deposit, repeat overdraft, redeposited check) and the exception rules for the first $X available next day. On every check deposit, explicitly ask yourself which category applies before releasing funds.
Treating a Currency Transaction Report threshold as a judgment call, or structuring a customer's deposits into smaller amounts to avoid paperwork or to be helpful.
Candidates hear 'report only suspicious activity' and conclude that a large cash deposit is not their problem, or they fear embarrassing the customer and split the transaction.
What to do instead
Learn the rule as a bright line: cash transactions over the reporting threshold in a business day require a report regardless of whether the customer looks suspicious, and intentional structuring to evade reporting is itself a reportable offense. Never suggest splitting a deposit; escalate instead.
Not completing a Suspicious Activity referral because the transaction was small, the customer was polite, or the candidate assumed someone else would notice.
Candidates expect fraud to look dramatic and believe a report requires proof; in reality the standard is a reasonable suspicion, and the teller is often the only person who sees the pattern.
What to do instead
Adopt the mindset that a referral is a low-cost note, not an accusation, and that no dollar amount is too small. Keep a mental checklist of red flags (reluctance to give ID, unusual nervousness, third-party direction, sudden change in activity) and file the referral before the customer leaves the window.
Accepting an identification document without checking that the photo matches the person, that the document is unexpired, and that the name and signature are consistent with the account.
Candidates treat ID collection as a data-entry step and glance only at the name and date of birth, missing expired documents, mismatched signatures, and impostors.
What to do instead
Use a physical inspection sequence: hold the document, compare the photo to the face, check the expiration date, feel for texture and look for tampering, and compare the signature on the ID to the signature on the withdrawal slip or check. Rehearse this sequence on every transaction, not just new accounts.
Cashing or accepting a check without verifying the date, the written and numeric amounts matching, the payee name, the endorsement, and the presence of required signatures.
Candidates focus on the amount and skip the other fields, so they miss post-dated or stale-dated checks, altered figures, missing endorsements, and checks payable to someone other than the presenter.
What to do instead
Work through the instrument in a fixed order every time: date, payee, written amount versus figures, signature, endorsement, and any restrictive endorsement. If any field is inconsistent, stop and escalate rather than guessing which version is correct.
Leaving the cash drawer open, unlocked, or unattended, or allowing a non-teller behind the counter, because the candidate stepped away briefly to help a colleague.
Candidates underestimate how quickly an opportunity theft occurs and assume the branch is a low-risk environment; they also do not want to seem unhelpful to coworkers.
What to do instead
Treat the drawer as a locked asset: close and lock it, or lock the workstation, before leaving for any reason, even seconds. Learn and follow the branch's dual-control rules for vault access, and politely redirect anyone without authorization away from the teller line.
Handling a customer complaint or a disputed transaction by promising a specific outcome, such as a refund or reversal, before checking authority limits and the bank's dispute process.
Candidates want to de-escalate and please the customer, and they confuse empathy with commitment; they also do not know which resolutions require a supervisor.
What to do instead
Use language that acknowledges without committing: state what you can do now, what you will check, and when the customer will hear back. Know your transaction authority limits and the dispute timelines, and route anything beyond them to a supervisor immediately.
Discussing an account, balance, or transaction with a spouse, family member, or caller who is not an authorized signer, or confirming whether a person banks at the institution.
Candidates want to be helpful to a worried relative or a persistent caller and do not recognize that even confirming an account exists is a disclosure.
What to do instead
Apply a strict rule: no account information to anyone who is not verified as an authorized party, including confirming existence of an account. Practice a neutral refusal script and offer to take a message or direct the person to the account holder.
Making a cash-counting or keying error and then trying to correct the drawer balance quietly, or delaying the end-of-day proof, instead of reporting the outage immediately.
Candidates fear blame and believe a small difference will resolve itself, so they conceal or postpone the discrepancy, which destroys the audit trail and turns an error into a policy violation.
What to do instead
Report any outage to a supervisor as soon as it is detected, document the transaction involved, and complete the end-of-day proof on schedule. Understand that a promptly reported difference is treated as an error, while a concealed one is treated as misconduct.