[BG] Proof is the department of the bank (actually one person per branch) who scans the tickets (checks, deposit slips, etc.) into the computer and makes sure all the transactions balance. If the scanner doesn't read the items correctly, the proof operator has to look at the images and key in the amounts or whatever's missing. Sometimes, the scanner doesn't read the handwritten part of the item at all - maybe the customer used pink or green ink, for example. Then the proof operator has to pull out the original item and key in the missing information. [/BG]
We were informed on Monday that our branch has far more proof errors than any other branch, including the main one. (Maybe percentage-wise? It wasn't clear.) The solution they came up with is to pull reports off mainframe twice a month that show what the errors were and review them. It was heavily implied that the proof operator and the branch manager would be digging into the errors to see what they were and try to find a pattern in the hopes of reducing the number of errors.
But as our proof operator pointed out, a lot of the errors won't be fixable. Customers have terrible handwriting. Sometimes they use odd-colored ink. Or glitter ink. On those tickets that are printed/typed, sometimes the ink gets faint. Also, our proof machine isn't the greatest, so the tickets sometimes get stuck. Or any number of other things.
Still, we are being required to pull reports twice a month and review them. In order to reduce work for the proof operator, they're making more work for the proof operator and branch manager.
We were informed on Monday that our branch has far more proof errors than any other branch, including the main one. (Maybe percentage-wise? It wasn't clear.) The solution they came up with is to pull reports off mainframe twice a month that show what the errors were and review them. It was heavily implied that the proof operator and the branch manager would be digging into the errors to see what they were and try to find a pattern in the hopes of reducing the number of errors.
But as our proof operator pointed out, a lot of the errors won't be fixable. Customers have terrible handwriting. Sometimes they use odd-colored ink. Or glitter ink. On those tickets that are printed/typed, sometimes the ink gets faint. Also, our proof machine isn't the greatest, so the tickets sometimes get stuck. Or any number of other things.
Still, we are being required to pull reports twice a month and review them. In order to reduce work for the proof operator, they're making more work for the proof operator and branch manager.
Comment