DESC:FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
[SEE SECTION 10, RULE 13]

AN AUTOMATED SCANNING SYSTEM AND A METHOD THEREOF

KORES INDIA LIMITED
A COMPANY INCORPORATED UNDER THE COMPANIES ACT, 1913, WHOSE ADDRESS IS: C-7/1B, TTC INDUSTRIAL AREA, MIDC PAWANE, NAVI MUMBAI, MAHARASHTRA - 400 705, INDIA

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.
TECHNICAL FIELD
[001] The present invention relates generally to scanning systems. The present invention, more particularly, relates to an automated system for scanning and verifying documents having attributes.
BACKGROUND
[002] Conventionally, financial institutions manually accept documents having attributes. The attributes may include transaction specific data such as personal details, special codes, account details, bar codes, and the like. The special codes include Quick Response (QR) codes, codes having special characters, and other encrypted codes. For example, a financial institution manually accepts cheque(s) or currency from those customers, who have their accounts in the same financial institution. To deposit the cheque/ currency in the financial institution, a customer has to visit the financial institution physically, stand in long queues, fill deposit slips, and get the cheque/ currency deposited with the help of an officer/ attender, and take a stamped receipt from the officer/ attender.
[003] In other words, the financial institution consists of many individual manual operations as well as an apparatus/ machine(s). The operations include financial institution branch operations including currency deposit/ withdrawal, cheque deposit, and other documents submission and processing, and the like.
[004] Today, a manual cheque drop box (for example, a cheque collection box) and a cheque deposit kiosk (i.e., an automated cheque deposit kiosk) are available, and the cheque(s) can be deposited in the same. The cheque deposit kiosk has a deposit apparatus in which the customer can deposit the cheque without visiting the financial institution. The cheque deposit apparatus is a self-service terminal that allows the customer to deposit the cheque without any manual assistance or supervision. The apparatus will ask to the customer to identify himself/ herself by the way of a card / entering his/her account details. After swiping the card/ inputting the account details, the apparatus may transmit the information to a bank server for verifying the entered details. If the entered details are verified by the bank server, the customer can deposit the cheque in the apparatus, a receipt will be generated by the apparatus. After receiving the cheque, an image of the cheque is captured by the apparatus and pushed to a server to generate a customer receipt, as a proof of the cheque deposit. However, though the apparatus is used, but the process is manual with lot of operations performed redundantly at a bank end of the apparatus, thereby increasing the overall time and cost to complete the operation. For example, before putting the cheque(s) collected by the cheque deposit kiosk for clearance, the staff of the financial institution has to physically pull out all the cheques from the cheque deposit kiosk to verify the genuineness of an instrument along with a search for any alteration of amount, date (whether the cheque is pre/postdated cheque), and payee’s name. Apart from this, the process of a data entry has to be carried out at the back end to have maker- checker of the instrument. This data entry followed by verification of the data is a process conducted in the back-office for all cheques deposited in the existing type of cheque deposit kiosks.
[005] Additionally, the apparatus does not verify the authenticity of the cheque, and the cheque is then verified manually, either by physically verifying the details of the cheque using instruments. The manual verification of the cheque is cumbersome, and error-prone.
[006] In an example, a customer visits a financial institution to drop the cheque either in a cheque drop box or in an automated Cheque Deposit Kiosk installed there or nearest same bank’s ATM (Automated Teller Machine) center. However, the user cannot get a receipt if he drops the cheque in the drop box at ATM center. Normally, after closing the customer services at a particular time period, the bank staff picks up the cheques physically from the cheque drop box. The bank staff then manually enters the cheque and slip details in the financial institution`s application. Thereafter, it goes to the back office of the financial institution for scanning in case the financial institution has a scanner, or it goes to their nearest scanning hub through daily pickup logistic services to get it scanned. After getting the scanned image only the application allows to enter the relevant data mandatory to push it for clearance. The whole cheque processing cycle has multiple touch points and duplicate manual handling and processing of the same cheque, making it more error-prone and thereby taking more time.
[007] Apart from the problems in cheque deposit apparatus, there are also problems in queue management and data capture for cash deposit/ withdrawals at the branch operations.
[008] In case of queue management, a customer visits a branch and approaches queue management apparatus. In some cases, the customer selects transaction type and presses button to get token/ coupon number. The customer then approaches a bank teller that is displayed on the queue monitor against the token/ coupon number. The bank staff at teller counter does not get any data or information of the details of the transaction of the customer wants to execute. The only information passed on the teller is the transaction type the customer desires. The entire transaction is carried out manually once the customer reaches the teller counter.
[009] In case of cash transactions, a customer visits a financial institution follows the queue management process (if applicable at the branch). The customer brings / fills a deposit/ withdrawal slip. With the currency and slip, he has to wait in the line till his turn comes. The teller staff of the financial institution has no data or information of what the customer desires to execute except the type of transaction. At the counter, he gives the slip along with currency. The cashier checks the account number by manually entering the account no. written on the slip. On this verification he then counts the currency by hand first, then counts twice in the counting machine or vice versa. He then enters the information regarding the denomination of currency amount in the bank`s system. Once the entry is done, he then segregates in similar currency notes and keeps with him. The cashier gives a stamped deposit slip back to the customer. This whole deposit process takes on a lot of time as there are lot of manual tasks are involved like reading, entering verifying, counting, segregating etc. All these are error prone high risk and time consuming.
[0010] In other words, the overall process takes longer time, and it reduces productivity of the financial institution as well and may be converted into customer’s dissatisfaction. Also, there are many chances that counterfeit cannot be detected, and as a result the teller has to suffer the loss and he has to pay the same amount out of his pocket. It also increases the cost of operation.
[0011] Hence, there is a need of an invention which solves the above defined problems and provide an automated system for scanning, inputting data, and verifying documents having attributes.
SUMMARY
[0012] This summary is provided to introduce concepts related to providing an automated scanning system and a method thereof. This summary is neither intended to identify essential features of the present invention nor is it intended for use in determining or limiting the scope of the present invention.
[0013] For example, various embodiments herein may include one or more automated scanning systems and methods are provided. In one of the embodiments, the present invention discloses a method for automated scanning of documents includes a step of inserting, by an insertion module, a plurality of documents in a scanner device. The method includes a step of scanning, by the insertion module, the inserted documents and generating scanned data. The method includes a step of capturing, by a capturing module, one or more field inputs from the scanned data by running a pre-defined recognition technique. The method includes a step of storing, in a database, the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters. The method includes a step of counting, by a counter module, at least one set of documents from the plurality of documents based on the inputs and parameters, wherein the at least one set of documents includes currency notes. The method includes a step of identifying, by a counterfeit module, counterfeit currency notes from the counted currency notes and segregating the identified counterfeit currency notes. The method includes a step of dispensing, by an output module, the currency notes based on the segregated currency notes.
[0014] In another implementation, an automated scanning system includes an insertion module, a capturing module, a database, a counter module, a counterfeit module, and an output module. The insertion module is configured to insert a plurality of documents in a scanner device, and further scan the inserted documents and generate scanned data. The capturing module is configured to capture one or more field inputs from the scanned data by running a pre-defined recognition technique. The database is configured to store the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters. The counter module is configured to count at least one set of documents from the plurality of documents based on the inputs and parameters, wherein the at least one set of documents includes currency notes. The counterfeit module is configured to identify counterfeit currency notes from the counted currency notes and segregate the identified counterfeit currency notes. The output module is configured to dispense the currency notes based on the segregated currency notes.
BRIEF DESCRIPTION OF ACCOMPANYING DRAWINGS
[0015] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to reference like features and modules.
[0016] Figure 1 illustrates a block diagram depicting an automated scanning system, according to an implementation of the present invention.
[0017] Figure 2 illustrates a schematic diagram depicting functionalities of various modules of the automated scanning system of Figure 1, according to an exemplary implementation of the present invention.
[0018] Figures 3a-3b illustrate a schematic diagram depicting an architecture of a client-server arrangement, according to an exemplary implementation of the present invention.
[0019] Figure 4 illustrates a flow diagram depicting steps of scanning the documents, according to an exemplary implementation of the present invention.
[0020] Figure 5 illustrates a flowchart depicting a method for automated scanning of documents, according to an implementation of the present invention.
[0021] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present invention. Similarly, it will be appreciated that any flowcharts, flow diagrams, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
DETAILED DESCRIPTION
[0022] In the following description, for the purpose of explanation, specific details are set forth in order to provide an understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without these details. One skilled in the art will recognize that embodiments of the present invention, some of which are described below, may be incorporated into a number of systems.
[0023] The various embodiments of the present invention provide an automated scanning system and a method thereof.
[0024] Furthermore, connections between components and/or modules within the figures are not intended to be limited to direct connections. Rather, these components and modules may be modified, re-formatted or otherwise changed by intermediary components and modules.
[0025] References in the present invention to “one embodiment” or “an embodiment” mean that a particular feature, structure, characteristic, or function described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
[0026] In one of the embodiments, the present invention discloses a method for automated scanning of documents includes a step of inserting, by an insertion module, a plurality of documents in a scanner device. The method includes a step of scanning, by the insertion module, the inserted documents and generating scanned data. The method includes a step of capturing, by a capturing module, one or more field inputs from the scanned data by running a pre-defined recognition technique. The method includes a step of storing, in a database, the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters. The method includes a step of counting, by a counter module, at least one set of documents from the plurality of documents based on the inputs and parameters, wherein the at least one set of documents includes currency notes. The method includes a step of identifying, by a counterfeit module, counterfeit currency notes from the counted currency notes and segregating the identified counterfeit currency notes. The method includes a step of dispensing, by an output module, the currency notes based on the segregated currency notes.
[0027] In another embodiment, the method includes a step of reconciling, by a reconciliation module, data corresponding to the segregated currency notes.
[0028] In another embodiment, the segregated currency notes data include denominations, total number of currency notes, a total value of the currency notes, serial numbers of the currency notes, and start of the day (SOD) and end of day (EOD) reconciliation.
[0029] In another embodiment, the pre-defined recognition technique includes an Intelligent character recognition (ICR) technique, Optical character recognition (OCR) technique, Magnetic ink character recognition (MICR) technique, or vision artificial intelligence (AI).
[0030] In another embodiment, the pre-defined parameters include transaction types, reference numbers, a teller identification number, and a machine identification number.
[0031] In another embodiment, the method includes a step of generating, by a data receiver (208), an address link for the scanned data.
[0032] In another embodiment, the step of scanning, by the insertion module, the inserted documents use the pre-defined rules of scanning types.
[0033] In another embodiment, the pre-defined rules of scanning types include performing an image quality assurance test on the scanned data.
[0034] In another embodiment, the method includes a step of placing, in a pocket, the identified counterfeit currency notes.
[0035] In another embodiment, the method includes a step of establishing, by a networking device, a communication between the scanner device and a server.
[0036] In another implementation, an automated scanning system includes an insertion module, a capturing module, a database, a counter module, a counterfeit module, and an output module. The insertion module is configured to insert a plurality of documents in a scanner device, and further scan the inserted documents and generate scanned data. The capturing module is configured to capture one or more field inputs from the scanned data by running a pre-defined recognition technique. The database is configured to store the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters. The counter module is configured to count at least one set of documents from the plurality of documents based on the inputs and parameters, wherein the at least one set of documents includes currency notes. The counterfeit module is configured to identify counterfeit currency notes from the counted currency notes and segregate the identified counterfeit currency notes. The output module is configured to dispense the currency notes based on the segregated currency notes.
[0037] In another embodiment, the system includes a server which is communicatively coupled with the scanner device. The server includes the capturing module to capture the field inputs from the scanned data. In another embodiment, the server includes a reconciliation module which is configured to reconcile the data corresponding to the segregated currency notes.
[0038] In another embodiment, the scanner device includes the insertion module, the counter module, the counterfeit module, and the output module.
[0039] In another embodiment, the scanner device includes a scanner, a currency sorter, or a currency counter and sorting machine.
[0040] In another embodiment, the server includes a data receiver. The data receiver is configured to generate an address link for the scanned data.
[0041] In another embodiment, the insertion module is configured to scan the inserted documents by using the pre-defined rules of scanning types.
[0042] In another embodiment, the pre-defined rules of scanning types are configured to perform an image quality assurance test on the scanned data.
[0043] In another embodiment, the system includes a pocket. The pocket is configured to place the identified counterfeit currency notes.
[0044] In another embodiment, the system includes a networking device, which is configured to establish communication between the scanner device and the server.
[0045] Some of the objects of the present invention aimed to ameliorate one or more problems of the prior art or to at least provide a useful alternative are listed herein below.
[0046] An object of the present invention is to provide an automated scanning and processing system.
[0047] Another object of the present invention is to provide an automated scanning system that automatically verifies documents having attributes without human intervention.
[0048] Another object of the present invention is to provide an automated scanning system that verifies documents accurately.
[0049] Yet another object of the present invention is to provide an automated scanning system that is time efficient.
[0050] Another object of the present invention is to provide an automated scanning system that reduces the cycle time.
[0051] Another object of the present invention is to provide an automated scanning system that provides cost effective solutions.
[0052] Other objects and advantages of the present disclosure will be more apparent from the following description when read in conjunction with the accompanying figures, which are not intended to limit the scope of the present invention.
[0053] Figure 1 illustrates a block diagram depicting an automated scanning system (100), according to an implementation of the present invention.
[0054] The automated scanning system (hereinafter referred to as “system”) (100) includes a server (102), a scanner device (112), a database (110), and a network (108).
[0055] The server (102) is configured to cooperate with the scanner device (112) via the network (108). In an embodiment, the scanner device (112) is placed at a client side. In one embodiment, the server (102) includes a capturing module (104) and a reconciliation module (106). In one embodiment, the network (108) includes wired and wireless networks. Examples of the wired networks include a Wide Area Network (WAN) or a Local Area Network (LAN), a client-server network, a peer-to-peer network, and so forth. Examples of the wireless networks include Wi-Fi, a Global System for Mobile communications (GSM) network, and a General Packet Radio Service (GPRS) network, an enhanced data GSM environment (EDGE) network, 802.5 communication networks, Code Division Multiple Access (CDMA) networks, or Bluetooth networks.
[0056] The scanner device (112) further includes an insertion module (114), a counter module (116), a counterfeit module (118), and an output module (120). In an exemplary embodiment, the scanner device (112) can be a scanner, a sorter, or a counter and sorting machine.
[0057] In an exemplary embodiment, a teller (A) puts a document in the scanner device (112). In one embodiment, the document may be in the form of a slip, forms, cheque, note currency, voucher, or any type of documents.
[0058] The insertion module (114) is configured to insert a plurality of documents in the scanner device (112). The insertion module (114) is further configured to scan the inserted documents and generate scanned data In an embodiment, the insertion module (114) is configured to scan the inserted documents by using the pre-defined rules of scanning types. The pre-defined rules of scanning types are configured to perform an image quality assurance test on the scanned data.
[0059] In an exemplary embodiment, the teller (A) puts the document in the insertion module (114). The insertion module (114) is configured to scan and/ or sort the document taken from the teller (A) and generate scanned data. In one embodiment, the insertion module (114) is configured to scan the document and capture an image. In one embodiment, the insertion module (114) may be a scanning device, a sorter, or any type of counting and sorting machines, for example, iH110® or iH220®. The scanned data are transmitted to the server (102).
[0060] The capturing module (104) of the server (102) is configured to be communicatively coupled with the insertion module (114) to receive the generated scanned data. The capturing module (104) is further configured to capture one or more field inputs from the scanned data by running a pre-defined recognition technique. In an embodiment, the pre-defined recognition technique includes an Intelligent character recognition (ICR) technique, Optical character recognition (OCR) technique, a Magnetic ink character recognition (MICR) technique, or vision artificial intelligence (AI).
[0061] In an exemplary embodiment, the capturing module (104) is further configured to capture the details from the scanned image by running Intelligent Character Recognition (ICR) on the captured image. The captured details may include, but are not limited to, an account number of the user, amount, Magnetic Ink Character Recognition (MICR) code/ number, a cheque number, a form/ slip number, date, name of the user, and contact number and like. In an embodiment, the captured details, and the retrieved information are then stored in the database (110).
[0062] The database (110) is configured to store the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters. The pre-defined parameters include transaction types, reference numbers, a teller identification number, and a machine identification number. The database (110) is configured to store pre-defined parameters such as transaction types, transaction reference numbers, tellers’ identification numbers, and the like. In an embodiment, the data extracted from the capturing module (104) and Uniform Resource Locator (URL) of the scanned images is stored in the database (110). In an embodiment, the database (110) includes a look up table, which is configured to store the data. In an embodiment, the database (110) can be implemented as enterprise database, remote database, local database, and the like. The database (110) can be located within the vicinity of the system (100) or can be located at different geographic locations as compared to that of the system (100). Further, the database (110) may themselves be located either within the vicinity of each other or may be located at different geographic locations. Furthermore, the database (110) may be implemented inside the system (100), and the database (110) may be implemented as a single database.
[0063] The counter module (116) of the scanner device (112) is configured to be communicatively coupled with the capturing module (104) of the server (102) and the database (110) to receive the captured details and stored data. The counter module (116) is further configured to count at least one set of documents from the plurality of documents based on the inputs and parameters. In an embodiment, the at least one set of documents includes currency notes. In one embodiment, the currency data such as different denominations, exact number, total currency notes, a total value, serial numbers of the currency notes, and start of the day (SOD) and end of day (EOD) reconciliation, is stored in the database (110).
[0064] The counterfeit module (118) is configured to cooperate with the counter module (116) to receive the counted currency notes. The counterfeit module (118) is further configured to identify counterfeit currency notes from the counted currency notes and segregate the identified counterfeit currency notes from the good quality of notes.
[0065] The output module (120) is configured to cooperate with the counterfeit module (118) The output module (120) is further configured to dispense the currency notes based on the segregated currency notes.
[0066] In an embodiment, the system (100) includes a pocket (not shown in a figure). The pocket is configured to cooperate with the counterfeit module (118). The pocket is configured to place the identified counterfeit currency notes received from the counterfeit module (118). In an embodiment, the output module (120) includes one or more pockets and/or one or more trays. In one embodiment, the pocket which is configured to place the identified counterfeit currency notes can be the output module (120).
[0067] In an exemplary embodiment, the output module (120) can include trays/pockets in a range of, but is not limited to, 2 to 8. For example, in a case of 2 pockets, a first pocket is configured for correct/good currency notes and the second pocket is configured for the identified counterfeit currency notes, soiled notes, documents, such as a slip, cheque, form, and the like. In another example, in a case of 3 pockets, the two pockets are configured for different denomination/orientation and a third pocket is configured for the identified counterfeit currency notes, soiled notes, documents, such as a slip, cheque, form, and the like. The reconciliation module (106) of the server (102) is configured to be communicatively coupled with the counterfeit module (118) of the scanner device (112). The reconciliation module (106) is further configured to reconcile the data corresponding to the segregated currency notes. In an embodiment, the segregated currency notes data include denominations, total number of currency notes, and a total value of the currency notes. In an exemplary embodiment, the reconciliation module (106) is configured to generate the reports for a branch office, departmental head, and regional head. The cash available at the start of the day and all the cash transactions carried out throughout the day at each teller counter and at branch level will be recorded. Cash in hand at the branch level will be scanned, sorted and counted by the sorting and counting machine. At the end of the day balance is calculated by adding opening balance, cash deposited at bank, fresh cash issued to the bank and subtracting the withdrawal. The net cash available in hand at the end of the day will be reconciled in report, denomination wise, teller wise and branch wise.
[0068] In an embodiment, the system (100) includes a networking device (not shown in a figure), which is configured to establish communication between the scanner device (112) and the server (102).
[0069] In an embodiment, the system (100) is automated, and there will be no manual intervention. The system (100) gives accurate results without any error. The system (100) is configured to push date to the core banking systems (for example, a server (102), to store data, and the stored data can be used anytime or available for authorized person to analyses it. The system (100) also increases productivity of the financial institution, saves time, and cost.
[0070] Figure 2 illustrates a schematic diagram depicting functionalities of various modules of the automated scanning system (100) of Figure 1, according to an exemplary implementation of the present invention.
[0071] In an embodiment, the server (102) has a rest API (application programming interface) (202), modules (204) including the capturing module (104), the reconciliation module (106), a data receiver (208), and a folder for images (210). In one embodiment, the server (102) is configured to store the images captured by the insertion module (114) of the scanner device (112) in the folder (210).
[0072] The data receiver (208) is configured to push the data gathered by the different modules (204) to the database (110) and the server (102). The rest API (202) is configured with a user interface (206) for fetching the data from the server (102) and the database (110). In an embodiment, the data receiver (208) is configured to generate an address link for the generated scanned data. In an exemplary embodiment, the address link is a uniform resource locator (URL) link.
[0073] In an exemplary embodiment, a teller (A) puts the form/ slip/ cheque/note currency/ document/voucher in the insertion module (114) of the scanner and/or sorting machine (112). The insertion module (114) is configured to scan and/ or sort form/ slip/ cheque/note currency/ document/voucher taken from the teller (A) and generate scanned data/ image. The scanned image is stored in a folder (210) on the server (102) and its URL of the scanned image is stored on the database (110) via the database receiver (SIM) (208).
[0074] The capturing module (104) is configured to capture the details from the scanned image by running Intelligent Character Recognition (ICR) on the captured image. The captured details, include, but are not limited to, an account number of the user, amount, Magnetic Ink Character Recognition (MICR) code/ number, a cheque number, a form/ slip number, date, name of the user, and contact number. In an embodiment, the captured details and the retrieved information are then stored in the database (110). The database (110) is also configured to store pre-defined parameters such as transaction types, transaction reference numbers, tellers’ identification numbers, and the like. In an embodiment, the data extracted from the capturing module (104) is stored in the database (110).
[0075] The counter module (116) of the scanner and/or sorting machine (112) is configured to cooperate with the data receiver (SIM) (208). In an embodiment, the counter module (116) is configured to count currency notes. The currency/ cash data such as different denominations, exact number, total currency notes, a total value, serial numbers of the currency notes, and start of the day (SOD) and end of day (EOD) reconciliation, is stored in the database (110) via the data receiver (208) on the server (102).
[0076] The counterfeit module (118) of the scanner and/or sorting machine (112) is configured to cooperate with the counter module (116) to receive the counted currency notes and result. The counterfeit module (118) is further configured to identify counterfeit currency notes. The counterfeit module (118) is configured to segregate the identified counterfeit currency notes in a separate pocket (not shown in a figure). In an embodiment, the teller (A) may verify amount details with the slip/ form/ cheque and give permission to go ahead for withdrawing money by using his associated computing device (212). In an embodiment, the computing device includes, but is not limited to, a laptop, personal computer, tablet, mobile phones, palmtop, and any other similar device. In another embodiment, on completion, a transaction receipt can be printed by a configured printer (214) for a customer’s record.
[0077] The reconciliation module (106) of the modules (204) present at the server (102) is configured to generate the reports for a branch office, departmental head, and regional head. The cash available at the start of the day and all the cash transactions carried out throughout the day at each teller counter and at branch level will be recorded. Cash in hand at the branch level will be scanned, sorted and counted by the machine, for example, iH110®/iH220®. At the end of the day balance is calculated by adding an opening balance, cash deposited at the bank, fresh cash issued to the bank and subtracting the withdrawal. The net cash available in hand at the end of the day will be reconciled in report, denomination wise, teller wise and branch wise.
[0078] In an exemplary embodiment, various scenarios have been described with respect to the system (100).
[0079] Scenario 1: Cash Deposit- In an exemplary embodiment, a customer gives a deposit slip/ challan/ voucher and cash to a teller (A). The teller (A), by using, an insertion module (114), at a branch site, scans the deposit slip/ challan/ voucher by using the scanner and/or sorting machine (112). The insertion module (114) then transmits the scanned image to the data receiver (SIM) (208). The image is stored in a folder (210) on the server (102). The parameters, such as a transaction type, teller identification number, machine identification number, and URL (Uniform Resource Locator) of the scanned image of the deposit slip/ challan/ voucher is stored the database (110) via the data receiver (SIM) (208). The capturing module (104) extracts data from the scanned image of the deposit slip/ challan/ voucher, such as account number and total amount, by running Intelligent Character Recognition (ICR) and stores it in the database (110). The teller (A) at a User Interface (UI) server (206) calls the Rest API (202) by passing parameters such as a transaction type, a teller identification number, a Machine ID, and the like. The Rest API (202) fetches the URL of the scanned image and data extracted by the capturing module (104) like an account number and a total amount from the database (110). The teller (A) verifies the data. If the scanned image of the deposit slip/ challan/ voucher is not clear or the data extracted by capturing module (104) is incorrect, the teller (A) can reset the transaction or can manually correct the extracted data by using the personal computer (PC) (212). The manually corrected extracted data will be stored when the posting is done by the teller (A). Once verified, the teller UI prompts the teller (A) to insert the cash received from the account holder/ customer in the insertion module (114). The counter module (116) and the counterfeit module (118) both run simultaneously. The counter module (116) is configured to count the cash. The counterfeit module (116) is configured to identify the counterfeit currency notes and places them in a reject pocket of the machine (112). Once the cash is removed by the teller (A) from the counter (116), gathered cash data like denominations wise count, total value, serial number of currency notes, URL of currency snippet, counterfeit currency note data will be stored on the database (110) via the data receiver (SIM) (208). The insertion module (114) captures and stores the image of currency snippets in a folder (210) on server (102). The teller UI calls the Rest API (202) by passing parameters such as a transaction type, a teller identification number, a machine ID, which is configured to fetch the corrected data of the deposit slip/ challan/ voucher like an account number and a total value and cash data of the counter module (116) for displaying on the teller UI with an amount tally flag from the database (110). If the amount is tallied, then posting can be done on the teller UI and the final corrected data is stored in the database (110). If the amount is not tallied, then the UI has provision for correcting the cash data. After correction, the teller can post the data. On completion of the transaction receipt can be printed by a configured printer (214) for a customer’s record. In a case, if the teller (A) or a user wants to cancel the transaction, the teller UI calls the Rest API (202) for by passing a cancel transaction flag.
[0080] Scenario 2: Cash Withdrawal- In an exemplary embodiment, a customer gives a cheque for cash withdrawal to a teller (A). The teller (A), by using, an insertion module (114), at a branch site, scans the cheque. The insertion module (114) then transmits the scanned image of the cheque to a data receiver (SIM) (208) of the server (102). All the images are stored in a folder (210) at the server (102). The parameters like a transaction type, a teller identification number, a machine ID, and URL (Uniform Resource Locator) of the scanned image is stored in the database (110) via the data receiver (SIM) (208). The capturing module (104) extracts data from the scanned image of the cheque such as Magnetic Ink Character Recognition (MICR) code/ number, account number, date and amount, by running Intelligent Character Recognition (ICR) and stores it in the database (110). The teller (A) on the user interface (UI) server (206) calls the Rest API (202) by passing parameters such as a transaction type, a teller identification number, and machine ID to fetch the extracted data and the URL of the scanned image and displays it on the teller user interface (UI). If the scanned image is not clear or the data read by the ICR is incorrect, the teller (A) can reset the transaction and scan again using the insertion module (114) and/ or edit the captured data. The edited data will be stored in the database (110) after posting is done by the teller (A). In one embodiment, signature verification will be done by the teller (A). In an embodiment, after capturing and validating the data, the teller UI sends the transaction for authorization to the server (102). The teller (A) may create a new transaction in the meantime. The server (102) authorizes the previous transaction. Once the authorization is completed, the teller (A) can continue the same transaction. The UI server (206) prompts the teller (A) to count the cash using the counter module (116). Once the cash is placed, the counter module (116) and the counterfeit module (118) both run simultaneously. The counter module (116) is configured to count the required cash. The counterfeit module (118) is configured to identify the counterfeit currency notes and places them in the reject pocket of the machine (sorter/scanner or combination of both) (112). Once the cash is collected back by the teller (A) from the machine (112), gathered cash data like denominations wise count, total value, serial number of currency notes, URL of currency snippet, counterfeit currency note data will be stored in the database (110) via the data receiver (SIM) (208). The Rest API (202) fetches cash data for displaying on the teller UI with an amount tally flag from the database (110). The teller (A) verifies the extracted data and cash data. If the amount is tallied, then posting can be done on the teller UI and the final corrected data is stored in the database (110). If cash data not tallied, then the UI has provision for adding cash by placing in the insertion module (114). After correction, the teller (A) can post the data. On completion of the transaction receipt can be printed by the configured printer (214) for a customer’s record. In a case, if the teller (A) or a user wants to cancel the transaction, the teller UI calls the Rest API (202) by passing the parameters for reset transaction.
[0081] Scenario 3: Cheque Deposit (Transfer)- In an exemplary embodiment, a customer gives a cheque and a slip for transfer to a teller (A). The cheque has an account number to be debited and the slip has an account number to be credited. The teller (A), by using the insertion module (114), at the branch site, scans the cheque followed by the slip or vice versa. The insertion module (114) then transmits the scanned images to the data receiver (SIM) (208). All the images are stored in a folder (210) on the server (102). The parameters like a transaction type, a teller identification number, a machine ID and URL (Uniform Resource Locator) of the scanned image are stored in the database (110) via the data receiver (SIM) (208). The capturing module (104) extracts data from the scanned images, such as a Magnetic Ink Character Recognition (MICR) code/ number, an account number (debit account), date and amount from the cheque, an account number (credit account), and amount from a slip by running Intelligent Character Recognition (ICR) and stores it in the database (110). The teller (A) on the user interface (UI) calls the Rest API (202) by passing parameters such as a transaction type, teller identification number, machine ID to fetch the data extracted by the capturing module (104) and URL of the scanned images and displays it on the teller user interface (UI). Once the teller (A) verifies the data, the posting can be done. On completion of the transaction receipt can be printed by the configured printer (214) for the customer’s record. On posting, the transaction is sent for authorization to a user server. In a case, scanned image(s) is/are not clear, or the data read by the ICR is incorrect, the teller (A) can reset the transaction and scan again using the insertion module (114) or edit the captured data. The edited data will be stored in the database (110) after posting is done by the teller (A). In a case, if the teller (A) or a user wants to cancel the transaction, the teller UI calls the Rest API (202) by passing the parameters for reset transaction.
[0082] Scenario 4: Real-time gross settlement (RTGS), National Electronic Funds Transfer (NEFT), Immediate Payment Service (IMPS)- In an exemplary embodiment, a customer gives a RTGS/NEFT/IMPS form/ slip to a teller (A). The teller (A), by using an insertion module (114) at a branch site, scans the RTGS form. The insertion module (114) then transmits the scanned images to the data receiver (SIM) (208). All the images are stored in a folder (210) on the server (102). The parameters like a transaction type, a teller identification number, a machine ID and URL (Uniform Resource Locator) of the scanned image is stored in the database (110) via the data receiver (SIM) (208). The capturing module (104) extracts data from the scanned images such as debit and credit account numbers, total amount, name of payee and beneficiaries, IFSC (Indian Financial System Codes), and the like from the RTGS form by running the Intelligent Character Recognition (ICR) and stores it in the database (110). The teller (A) on the user interface (UI) calls the Rest API (202) by passing parameters such as a transaction type, a teller identification number, a machine ID to fetch the data extracted by the capturing module (104) and URL of the scanned images and displays it on the teller user interface (UI). Once teller (A) verifies the data, the posting can be done. On completion of the transaction receipt can be printed by the configured printer (214) for the customer’s record. On posting, the transaction is sent for authorization to the user server. In a case, the scanned image(s) is/are not clear, or the data read by the ICR is incorrect, the teller (A) can reset the transaction and scan again using the insertion module (114) or edit the captured data. The edited data will be stored in the database (110) after posting is done by the teller (A). In a case, if the teller (A) or a user wants to cancel the transaction, the teller UI calls the Rest API (202) by passing the parameters for reset transaction.
[0083] Scenario 5: Cheque Truncation System (CTS)- In an exemplary embodiment, a teller (A) uses a CTS application for capturing a CTS cheque. The teller (A), by using an insertion module (114), at a branch site, scans the cheque(s) by selecting an appropriate scanning type such as CMS, Retail, LIC, with or without vouchers, etc. The insertion module (114) then transmits the scanned images to the data receiver (SIM) (208). All the images are stored in a folder (210) on the server (102). The parameters like a transaction type, a teller identification number, a machine ID and an URL (Uniform Resource Locator) of the scanned image are stored in the database (110) via the data receiver (SIM) (208). According to the predefined rules of scanning types, an IQA (Image Quality Assurance) test and all validations are performed and if test passes the capturing module (104) extracts data from the scanned images, such as a Magnetic Ink Character Recognition (MICR) code/ number, an account number, date and amount from the cheque by running Intelligent Character Recognition (ICR) and stores it in database (110). If IQA fails, it asks for rescanning. The teller (A) on the User Interface (UI) calls the Rest API (202) by passing parameters such as a transaction type, a teller identification number, a machine ID to fetch the data extracted by capturing module (104) and URL of the scanned images and displays it on the teller user interface (UI). Once the teller (A) verifies the data, posting is done to the server. In a case, the scanned image(s) is/are not clear, or the data read by the ICR is incorrect, the teller (A) can reset the transaction and scan again using the insertion module (114) or edit the captured data. The edited data will be stored in the database (110) after posting is done by the teller (A). In a case, if the teller (A) or a user wants to cancel the transaction, the teller UI calls the Rest API (202) by passing the parameters for reset transaction.
[0084] Figures 3a-3b illustrate a schematic diagram depicting an architecture of a client-server arrangement, according to an exemplary implementation of the present invention.
[0085] In an exemplary embodiment, referring to Figure 3a, (300a), the client includes a server (302) which may be a local/first server. In an embodiment, the client may include a financial institution or any branch of the financial institution. The server (302) may also include a web server. The server (102) is a global/ second server, which is used by the branch. The server (102) includes the rest API (202) (as explained in Figure 2), an application server, the folder for images (210) (as explained in Figure 2). In an embodiment, the database (110) is configured to store all fetched and retrieved data of various modules. In one embodiment, the system (100) uses a multiprotocol label switch (MPLS) (304) for communication between the client (i.e., a branch) (306), the server (102, 302), and the database (110).
[0086] Figure 3b illustrates a schematic diagram (300b) depicting an architecture of a client-server arrangement between multiple clients and a server, according to an exemplary implementation of the present disclosure.
[0087] In an exemplary embodiment, the client includes a server (302) which may be a local/first server of multiple clients. In an embodiment, the client may include a financial institution or any branch of the financial institution. The server (302) may also include a web server. The server (102) is a global/ second server, which is used by the multiple branches (i.e., branch 1, branch 2, and branch 3). The server (102) includes the rest API (202) (as explained in Figure 2), an application server, the folder for images (210) (as explained in Figure 2) In an embodiment, the database (110) is configured to store all fetched and retrieved data of various modules. In one embodiment, the system (100) uses a multiprotocol label switching (MPLS) technique for communication between the client (i.e., each branch), server (102, 302), and the database (110). In Figure 3b, each client (i.e., branch 1, branch 2, and branch 3) (306a, 306b, 306c) is connected with the MPLS switch (304a, 304b) by using a wide area network (WAN) connection. In an embodiment, the clients (306) are connected with the server (302), the server (102), and the database (110) by using different switches (304a, 304b), respectively to protect it from network traffic and allows the data to flow in speed.
[0088] Figure 4 illustrates a flow diagram (400) depicting steps of scanning the documents, according to an exemplary implementation of the present invention.
[0089] The flow starts from a step (402). At a step (404), a customer gives a cheque, deposit slip/ challan/ voucher and cash to a teller (A). At a step (406), the teller (A), by using, an insertion module (114), at a branch site, scans the cheque, deposit slip/ challan/ voucher by using the scanner and/or sorting machine (112). At steps (408) and (410), the insertion module (114) transmits the scanned image to the data receiver (SIM) (208). At a step (412), the image is stored in a folder (210) on the server (102) The parameters, such as a transaction type, teller identification number, machine identification number, and URL (Uniform Resource Locator) of the scanned image of the cheque, deposit slip/ challan/ voucher is stored the database (110) via the data receiver (SIM) (208), as shown at the step (418). At the steps (414, 416), the capturing module (104) extracts data from the scanned image of the cheque, deposit slip/ challan/ voucher, such as account number and total amount, by running Intelligent Character Recognition (ICR) and stores it in the database (110). At the steps (420, 422), the teller (A) at a User Interface (UI) server (206) calls the Rest API (202) by passing parameters such as a transaction type, a teller identification number, a Machine ID, and the like. At a step (424), the Rest API (202) fetches the URL of the scanned image and data extracted by the capturing module (104) like an account number, a total amount, MICR, date and like from the database (110). The teller (A) verifies the data. At a step (426), the teller (A) checks whether the data and image are fetched and scanned properly. If not at a step (428), by using the insertion module (114), the teller A scans again as shown at a step (430) and goes back to the step (406) and the flow is repeated; or the teller (A) can reset the transaction as shown in the step (430) and process ends. In an embodiment, if the data extracted by capturing module (104) is incorrect, the teller (A) can manually correct the extracted data by using the personal computer (PC) (212). The manually corrected extracted data will be stored when the posting is done by the teller (A). In an embodiment, at a step (432), depending on a transaction type Server (102) checks whether transaction involves cash or not. For example, in the Scenarios 1 and 2 explained in Figure 2 involve the document and cash both and Scenarios 3 to 5 involve documents. If the cash is not involved in the transaction, the data validation takes place at a step (446), if the data is correct the transaction can be posted, and final data is stored in the database (110) via the Rest API (202) as shown in a step (454). If the data fetched is incorrect at a step (448), it can be manually edited by the teller (A) (step (462)) or the transaction can be reset and data can be stored in the database (110) via the Rest API (202), as shown at a step (450), and process ends at a step (452). Once the transaction is posted, the receipt can be printed for the customer’s record as per the steps 456 and 458. If the cash is involved, the server (102) checks whether the cash data is available, as shown at a step (436). If the cash data is not available at the step (436). At a step (442), the teller (A) is prompted to inserts cash in the insertion module (114), where the insertion module (114) captures an image and stores for a while. At a step (444), the counter module (116) and the counterfeit module (118) both run simultaneously and goes to the step (410) and repeat the process. The counter module (116) is configured to count the cash. The counterfeit module (118) is configured to identify the counterfeit currency notes and places them in a reject pocket of the machine (112). The steps (420) to (432) have to be repeated. At a step (432) transactions involves cash and cash data is available, and the step (438) is executed. The data of the images of a slip/ voucher/ cheque is validated against the cash data at the step (446). If the data is correct, the transaction is posted and it is stored in the database (110) via the rest API (202), as shown in the step (454). The receipt can be generated by the printer (214) for the customer’s record, as shown in the steps (456) and (458) and process ends at a step (460). If the cash data is not validated (as shown at a step (448), the server (102) resets the transaction and the data stored in the database (110) via the Rest API (202) (as shown at a step (450)) This process ends at a step (452). The teller (A) edits the data manually/ adds cash (as shown at a step (462) and the steps (446) and (442) are repeated. Once the data is validated, the transaction can be posted, and receipt can be printed as shown in the steps (454) to (458). The process ends at a step (460).
[0090] Figure 5 illustrates a flowchart (500) depicting a method for automated scanning of documents, according to an implementation of the present invention.
[0091] The flowchart (500) starts from a step (502), inserting, by an insertion module, a plurality of documents in a scanner device. In an embodiment, an insertion module (114) is configured to insert a plurality of documents in a scanner device (112). At a step (504), scanning, by the insertion module, the inserted documents and generating scanned data. In an embodiment, the insertion module (114) is configured to scan the inserted documents and generating scanned data. At a step (506), capturing, by a capturing module, one or more field inputs from the scanned data by running a pre-defined recognition technique. In an embodiment, a capturing module (104) is configured to capture one or more field inputs from the scanned data by running a pre-defined recognition technique. At a step (508), storing, in a database, the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters. In an embodiment, a database (110) is configured to store the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters. At a step (510), counting, by a counter module, at least one set of documents from the plurality of documents based on the inputs and parameters, wherein the at least one set of documents includes currency notes. In an embodiment, a counter module (116) is configured to count at least one set of documents from the plurality of documents based on the fetched inputs and parameters. At a step (512), identifying, by a counterfeit module, counterfeit currency notes from the counted currency notes and segregating the identified counterfeit currency notes. In an embodiment, a counterfeit module (118) is configured to identify counterfeit currency notes from the counted currency notes and segregating the identified counterfeit currency notes. At a step (514), dispensing, by an output module, the currency notes based on the segregated currency notes. In an embodiment, an output module (120) is configured to dispense the currency notes based on the segregated currency notes.
[0092] It should be noted that the description merely illustrates the principles of the present invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described herein, embody the principles of the present invention. Furthermore, all examples recited herein are principally intended expressly to be only for explanatory purposes to help the reader in understanding the principles of the invention and the concepts contributed by the inventor(s) to furthering the art and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.
,CLAIMS:We Claim:

1. A method for automated scanning of documents, comprising:
inserting, by an insertion module (114), a plurality of documents in a scanner device (112);
scanning, by the insertion module (114), the inserted documents and generating scanned data;
capturing, by a capturing module (104), one or more field inputs from the scanned data by running a pre-defined recognition technique;
storing, in a database (110), the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters;
counting, by a counter module (116), at least one set of documents from the plurality of documents based on the inputs and parameters, wherein the at least one set of documents includes currency notes;
identifying, by a counterfeit module (118), counterfeit currency notes from the counted currency notes and segregating the identified counterfeit currency notes; and
dispensing, by an output module (120), the currency notes based on the segregated currency notes.

2. The method as claimed in claim 1, comprising: reconciling, by a reconciliation module (106), data corresponding to the segregated currency notes.

3. The method as claimed in claim 2, wherein the segregated currency notes data include denominations, total number of currency notes, a total value of the currency notes, serial numbers of the currency notes, and start of the day (SOD) and end of day (EOD) reconciliation.

4. The method as claimed in claim 1, wherein the pre-defined recognition technique includes an Intelligent character recognition (ICR) technique, Optical character recognition (OCR) technique, Magnetic ink character recognition (MICR) technique, or vision artificial intelligence (AI).

5. The method as claimed in claim 1, wherein the pre-defined parameters include transaction types, reference numbers, a teller identification number, and a machine identification number.

6. The method as claimed in claim 1, comprising: generating, by a data receiver (208), an address link for the scanned data.

7. The method as claimed in claim 1, wherein scanning, by the insertion module (114), the inserted documents using the pre-defined rules of scanning types.

8. The method as claimed in claim 7, wherein the pre-defined rules of scanning types include performing an image quality assurance test on the scanned data.

9. The method as claimed in claim 1, comprising: placing, in a pocket, the identified counterfeit currency notes.

10. The method as claimed in claim 1, comprising: establishing, by a networking device, a communication between the scanner device (112) and a server (102).

11. An automated scanning system (100), comprising:
an insertion module (114) configured to insert a plurality of documents in a scanner device (112), the insertion module (114) configured to scan the inserted documents and generate scanned data;
a capturing module (104) configured to be communicatively coupled with the insertion module (114), the capturing module (104) configured to capture one or more field inputs from the scanned data by running a pre-defined recognition technique;
a database (110) configured to store the captured field inputs, one or more pre-defined rules of scanning types, and one or more pre-defined parameters;
a counter module (116) configured to be communicatively coupled with the capturing module (104) and the database (110), the counter module (116) configured to count at least one set of documents from the plurality of documents based on the inputs and parameters, wherein the at least one set of documents includes currency notes;
a counterfeit module (118) configured to cooperate with the counter module (116), counterfeit module (118) configured to identify counterfeit currency notes from the counted currency notes and segregate the identified counterfeit currency notes; and
an output module (120) configured to cooperate with the counterfeit module (118), the output module (120) configured to dispense the currency notes based on the segregated currency notes.

12. The system (100) as claimed in claim 11, comprising: a server (102) communicatively coupled with the scanner device (112), the server (102) includes the capturing module (104) configured to capture the field inputs from the scanned data.

13. The system (100) as claimed in claim 12, wherein the server (102) includes a reconciliation module (106) configured to be communicatively coupled with the counterfeit module (118), the reconciliation module (106) configured to reconcile the data corresponding to the segregated currency notes.

14. The system (100) as claimed in claim 11, wherein the scanner device (112) includes the insertion module (114), the counter module (116), the counterfeit module (118), and the output module (120).

15. The system (100) as claimed in claim 11 or 14, wherein the scanner device (112) includes a scanner, a currency sorter, or a currency counter and sorting machine.

16. The system (100) as claimed in claim 12, wherein the server comprising: a data receiver (208) configured to generate an address link for the scanned data, and the generated address link is stored in the database (110).

17. The system (100) as claimed in claim 11, wherein the insertion module (114) is configured to scan the inserted documents by using the pre-defined rules of scanning types.

18. The system (100) as claimed in claim 17, wherein the pre-defined rules of scanning types is configured to perform an image quality assurance test on the scanned data.

19. The system (100) as claimed in claim 11, comprising: a pocket configured to place the identified counterfeit currency notes.

20. The system (100) as claimed in claims 12 and 15, comprising: a networking device configured to establish communication between the scanner device (112) and the server (102).

Dated this 27th day of April, 2022

For Kores India Limited
By their Agent

ANSHUL SUNILKUMAR SAURASTRI) (IN/PA 3086)
KRISHNA & SAURASTRI ASSOCIATES LLP