Bank Teller

I treat balancing as something that happens throughout the day, not just at closing. I count my drawer at the start of every shift before I touch a single transaction, and I log the opening total. Through the day I keep large notes separated and organised by denomination so a miscount is easy to spot immediately rather than an hour later. For any transaction over a set threshold I double count before handing cash across the counter, even when there is a queue, because a rushed count costs more time later than a careful one does now. At close I count twice: once quickly to get a rough figure, then a slower count matching it against my transaction log. In three years as a teller I have balanced to the penny in all but two shifts, and both times I caught the discrepancy myself before it went to my supervisor.

I would stay calm and avoid alerting the customer in a way that could escalate the situation, since counterfeit detection at the counter needs to be handled discreetly for everyone's safety. I would use the standard checks I was trained on, watermark, security thread, colour shifting ink, and if I confirmed it was suspicious I would follow our branch protocol, which usually means quietly involving a supervisor rather than confronting the customer directly myself. I would never simply hand it back or process it through the till. At my last branch we had a training refresher on note security every six months, and I always keep the UV pen at my station rather than in a drawer, because the moment I need it is the moment I do not want to be searching for it.

I start by letting them explain fully without interrupting, because most of the frustration in that moment is about feeling unheard, not just the fee itself. I pull up the account and walk through exactly what triggered the charge in plain language, no jargon, so they understand the "why" rather than just being told "that is our policy." If the fee was applied correctly I explain it clearly and calmly, and if there is a reasonable case for a one off waiver within my authority, I offer it, since a customer who leaves feeling heard is far more likely to stay with the bank even if the answer is still "the fee stands." If it is outside what I can authorise, I bring in a supervisor immediately rather than letting the customer feel passed around. I closed out a very similar conversation last year with a customer who had been ready to close her account, and she stayed.

I am comfortable with it as long as it is genuinely relevant to what the customer is doing, not a script I recite regardless of context. If someone is depositing a large sum into a low interest current account, mentioning that we have a savings option with a better rate is useful information, not a sales pitch, and most customers appreciate it rather than resent it. I pay attention to cues: if someone is in a hurry or clearly not interested, I do not push. In my last role I was consistently in the top third of my branch for product referrals, not because I pitched aggressively but because I only raised things that actually made sense for that person's situation, which meant a higher share of my referrals actually converted.

A customer came in to deposit a cheque that on first glance looked normal, but the amount in words and the amount in figures did not match exactly, a difference of ten pounds that was easy to miss at a glance. I flagged it to the customer rather than processing it as written, and it turned out to be an honest mistake by whoever had written it, but if I had processed it as is it would have created a discrepancy that someone would have had to chase down later, possibly after the customer had already spent funds based on the wrong figure. I asked them to have it corrected and initialled before I processed it. It took an extra five minutes at the counter, which is a small cost against the alternative of an unwinding transaction days later.

A regular customer asked me to waive an overdraft fee for the third time in two months, which was outside what I was authorised to approve without escalation, and honestly outside what felt fair to other customers who were held to the standard policy. I explained clearly that I could not approve it myself given the pattern, but that I could refer him to a relationship manager to discuss his account setup, since repeated overdrafts sometimes point to a better fit product, like an overdraft buffer or a different account type. He was frustrated in the moment, but he took the referral, and the relationship manager ended up moving him to an account that suited his spending pattern better, which meant he stopped needing the waiver at all. Saying no well sometimes means pointing to a better answer, not just refusing.

Our branch has a predictable lunchtime rush between twelve and one, and one day we were down a teller because of illness, so three of us were covering what would normally take four. I focused on keeping my own line moving efficiently rather than trying to rescue the whole floor, since panicking about the overall queue would have slowed down my own transactions. I kept transactions crisp, greeted the next customer while finishing paperwork on the last where possible, and flagged to my supervisor early that we might need to open a fourth window if it got worse, rather than waiting until customers were visibly annoyed. We got through the rush without anyone waiting more than about fifteen minutes, and the branch manager specifically mentioned afterward that the queue had stayed calmer than she expected given we were short staffed.

I have worked daily with our branch's core banking platform for cash transactions, account lookups, and cheque processing, along with a separate till reconciliation tool we used at close of day. I am comfortable navigating account histories to answer customer questions quickly without making them wait while I search, and I know how to flag a transaction for review rather than forcing it through if something looks off in the system. I also used a queue management system that fed customers to the next available window, and I picked up a scanning tool for cheque imaging within my first week because the training was hands on and I asked questions immediately rather than guessing. I am confident that any system with similar transaction and reconciliation logic would take me a short time to learn properly.

At the teller level, my main responsibilities are recognising red flags and following reporting procedure rather than making the final compliance call myself. That means watching for things like structuring, where a customer makes several deposits just under a reporting threshold, unusual cash volumes relative to a customer's normal pattern, or a customer who is unusually reluctant to explain the source of funds. I know to verify identification properly on any transaction that requires it and never to skip that step even when a customer is in a hurry or a regular I recognise, since familiarity is exactly the situation where shortcuts creep in. If something looks off, I escalate to my supervisor or the branch's compliance contact rather than deciding myself whether it is significant enough to matter.

First I recount before assuming anything is actually wrong, since a simple miscount is far more common than an actual loss. I go back through my transaction log for the day and check it against the physical count, looking specifically at large transactions and anything processed near the end of the shift when fatigue makes errors more likely. If I still cannot find it, I flag it to my supervisor immediately rather than waiting or trying to quietly fix it myself, because a small discrepancy caught the same day is straightforward, while one left unreported compounds and gets harder to trace. I keep a written note of exactly what I checked and in what order so whoever helps me trace it is not duplicating steps I already ruled out.