CheckReader

Spider 2.0 CheckReader

Add-on module designed for reading checks

Spider 2.0 Home Edition / Spider 2.0 Enterprise / Spider.Net

The Spider 2.0 Check Reader application is part of a family of applications designed for document management, the common determinant being Spider 2.0. Conceptually, the Spider 2.0 Check Reader is an add-on module for the application of Spider 2.0 Enterprise, but can also be used independently. It is primarily intended for banks and other institutions which deal with domestic or foreign checks as part of their business operations.

The application offers users the ability to quickly and efficiently collect data from a large number of checks organized into groups (specifications), where the very reading of data is done using the powerful OCR / ICR mechanisms on scanned checks. The application also allows you to control the number of checks processed and the total amount in each specification, as well as the validation of each individual check.

An overview of how the Check Reader operates

When first working with the Spider 2.0 Check Reader, a new specification should be formed. As each bank has its own checks, with different placements of data entry spaces, and the position of the check number and the checking account number, the application already contains a large number of profiles that match the checks of certain banks. The profiles are basically templates, which already have marked spaces which the Check Reader will read the data from.

It is important to mention that creating new profiles is not complicated and that the process revolves around marking the spaces that are to be read. Here it is also possible to define the minimum and maximum amount on the check, as well as the type of printing per check number (i.e. matrix printing) or per module (i.e. module 10).

Scanning is done by connecting the check scanner to the computer via a USB 2.0 port, for maximum speed. Upon scanning completion, the process of reading and verification of the scanned checks begins. The verification, which is the checking of values read, is multifold. The application first checks whether all the numerical values were read and are correct. Then comes the test phase following the algorithm defined in the profile (eg, If the check number follows module 10). In the third stage of verification, the application checks whether the monetary values of the check are within the minimum / maximum range. In addition to these three stages, the application also checks the total value and number of checks per specification, as well as performs an additional check following a different algorithm, if the user has the need for it.

Following check processing is the export of data. The data can be exported in three different types of files, XML, CSV or TXT, according to user needs. In addition, if the user chooses the Spider 2.0 Enterprise Edition application, Home Edition or Spider.Net, the data can be exported directly into one of these applications, along with images of checks. This means that the data is exported into a specific "File Type" where the images of all the checks will be visible, while the values read from the checks will be automatically entered into the annotation fields and will be immediately available for search.

The options for implementation of the Check Reader into your system

The MFC-Mikrokomerc company offers 5 different options for the implementation of Spider 2.0 Check Reader into your system.

• Installing the Spider 2.0 Check Reader application to a computer where scanning and processing of checks will be done simultaneously. In this case it is possible to export the data in one of the mentioned file types (XML, CSV, TXT), but the user does not have future access to the archive of scanned checks, nor can he use it for future processing, as he would be able to do with Spider 2.0 Home Edition, nor is it possible to use network resources. In this case, the scanned images of checks may be deleted after processing, as they no longer have a function.
• Listen
• Read phonetically

• The second option also includes the installation of the applications on a single workstation, but together with the application for filing documentation - Spider 2.0 Home Edition. This allows the user to make future check searches, with visible images.

• Option three contains the same features as option 1, but in a networked environment. This means that it is possible to install one or more scanners at individual workstations where scanning will be performed, while the processing of checks can be done at other workstations. As in option 1, this application for archiving of documentation disallows future searches of checks and data; it only allows export to one of the file types stated in 1.

• Option four includes the application for archiving of documents - Spider 2.0 Enterprise Edition, which is intended for a networked environment. This, as with option 3, will enable scanning and processing of checks on multiple workstations, as well as future access to data, as with Option 2, but in a networked environment.

• The difference between options 4 and 5 is that option 5 includes the Spider.NET application intended for work in an intranet and internet environment. You will have all the possibilities presented in option 4, but with the ability to access data from any part of the world via the intranet or the internet.