My bank's ATMs only lets me punch out cash in $20 increments. They used to dispensed both 20s and 5s, but sometimes they mixed them up and created problems (this was just human error when stocking the ATM with cash).
So, okay. I can understand and live with that limitation.
But when I enter the amount I want, the ATM records it to the cent. So if I want $100, and I type in 100, it reads it (and displays it) as $1.00.
I can understand it requiring me to type in exactly how many dollars I want – any shortening of that would invite errors. For example, if I only had to type in the number of 20s I wanted, because that’s all they dispense at these ATMs, then I’d have to do some math in my head to compute how many 20s in, say, $100. Not very difficult for me and probably not for you, but a likely source of errors for many people, especially those in a rush in the rain.
The ATM could auto-fill the units place, so that typing a 2 would read as $20, but that also might invite errors, because if I want $20, I’m likely to type in 20 without thinking – short-cuts that go against how we are used to thinking about things require new learning and invite errors, at least in the short run. And if we are forced to think about what to type into the ATM in a different way than we think in other common situations, then it just makes life needlessly complex (like having dozens of different passwords would, if anyone always used different passwords like they’re supposed to).
But there is no good reason why it requires me to type in the cents. People are quite good at thinking in whole dollars. In fact, I suspect that the current method causes errors, as when people type in the number of whole dollars they want without checking the read-out, and then get an error message because the amount they entered is less than $20.
One could write it off as just the natural product of bankers' retentiveness, but I see it as another small example of designers and builders working with no attention to users and product usability.