Pros and Cons of Implementing a Standalone Teller Cash Recycler
Determining the best way to operate teller cash recyclers (TCR) in your branch environment can be difficult. Understanding the available options is an elemental part of making an informed decision. Today, I'd like to discuss deploying TCRs in a standalone format.
Standalone implementations leverage application software, loaded on and driven by the local PC, to drive the TCR independent of the teller application. Tellers toggle between the two applications on their desktop (often employing “hot keys”), requiring double keying of amounts in both the standalone application and their teller application.
- Low cost - no need for development work or application customization
- Highly stable - applications designed specifically to support TCR functionality
- Application agnostic - not tied to specific application, protects investment
- Ease of use - simple to train, use, manage exception conditions
- Double-keying - creates opportunity for error in cash handling
- Balancing - creates need for added step in teller balancing
- Enterprise rollout - can be cost-prohibitive in larger implementations
- Support - generates need to support yet another application in branches
Depending upon your unique branch characteristics and goals for teller cash recycler adoption, standalone application deployment may be the best option. Be sure to take the time to weigh your software options before making any integration decision.