Optical Sorter Rejection Faults: Prevent Teller Cash Variances
A single misread note in the rejection bin will blow your entire shift reconciliation wide open, and the optical sorter is almost always the culprit. I have walked into cash rooms where tellers swore the machine was "fine" while the variance log climbed past six figures over a quarter. The fault is rarely the sensor itself β it is the rejection logic, the calibration drift, and the operator override culture that lets bad notes cycle back into the good stack. πΈ
Here is the hard truth: an optical sorter does not fail loudly. It fails politely, spitting a genuine note into the reject pocket because the UV or IR signature was marginally off, and the teller β under time pressure β re-feeds it by hand without logging the event. That single habit destroys your optical sorter rejection faults traceability and turns a hardware glitch into a permanent teller cash variance.
Where the Rejection Logic Actually Breaks
Most rejection faults trace to three subsystems: the transport path, the sensor array, and the firmware thresholds. The transport skews notes by a fraction of a millimeter, the optical head reads a partial image, and the firmware β running thresholds set months ago β rejects a perfectly valid note. Multiply that by a few thousand notes per shift and you have a systematic variance that no amount of teller retraining will fix. Audit the skew rollers first, then the sensor calibration log, then the threshold table. In that order. No exceptions.
Sensor drift is the silent killer. UV lamps degrade, IR filters accumulate dust, and the machine keeps rejecting with the same confidence it had on day one. If your rejection rate on a given denomination jumps from 1.2% to 3.8% without a note-quality explanation, you are looking at a calibration fault, not a counterfeit problem. Pull the reject-bin journal and cross-reference against the denomination mix. π―
The Teller Override Trap
Operators override rejections because the machine "looks wrong" β and that is exactly how variances get laundered. Every manual re-feed must generate a logged exception with a timestamp, a denomination, and an operator ID. If your sorter firmware does not enforce that, replace the workflow before you replace the hardware. The variance does not come from the machine; it comes from the gap between what the machine rejected and what the teller silently reinserted.
Run a controlled rejection test weekly: seed known-good notes with deliberate skew and partial occlusion, record the rejection behavior, and compare against the threshold table. If the machine rejects more than 0.5% of clean, well-oriented notes, the optical head or the transport is out of spec. That is a mechanical verdict, not a debate.
Firmware Thresholds and the Variance Ledger
Firmware thresholds are where the real money hides. A threshold set too tight rejects genuine notes and inflates the reject pocket; set too loose and you pass suspect notes into circulation. The sweet spot is denomination-specific and must be re-validated after every sensor cleaning. Tie the sorter's rejection journal directly to the cash variance ledger so every rejected note has a downstream reconciliation entry. When those two ledgers diverge, you have found your fault β not in the teller's drawer, but in the machine's decision log.
Physical inspection still matters. A cracked transport belt or a misaligned stacker wheel will produce rejection patterns that look random but are actually geometric β always the same corner, always the same skew angle. Map the rejection coordinates over a week and the fault pattern will expose itself. That is the difference between guessing and auditing. π