JP4354715B2 - Form terminal device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a form terminal device that performs payment at a counter of a financial institution such as a post office or a bank.
[0002]
[Prior art]
Devices that perform operations such as post offices and banks are known (Patent Documents 1 and 2). Among such businesses, there is a payment business. This work is a process in which a payer submits a payment as shown in FIG. In this OCR recognition, the account number and payment amount described in the payment handling slip on the left side of the payment slip are recognized.
[0003]
When the OCR is recognized by the form terminal device, those that cannot be recognized by OCR are corrected by rejected characters or manually.
[0004]
Further, the OCR-recognized data is accumulated in the form terminal device as form data and transmitted to the center.
[0005]
[Patent Document 1]
JP2001-184453
[0006]
[Patent Document 2]
Japanese Patent Application Laid-Open No. 08-30700
[Problems to be solved by the invention]
In the totaling process at the center, a settlement process is performed in which the sum of the paid amounts recognized by the OCR in each form terminal device is compared with the total amount actually paid.
[0008]
In the settlement process, if the two do not match, it is necessary to recognize the OCR again for all the form data processed by the form terminal device.
[0009]
When the form terminal device performs several hundred processes per day, there is a problem that the process takes time and is not efficient.
[0010]
The present invention has been made in view of the above points, and an object of the present invention is to provide a form terminal device capable of recording an error that occurs when recognizing a form.
[0011]
[Means for Solving the Problems]
The present invention relates to an image reading unit that captures image data of a form in a form terminal device having a key input unit and a display unit, and recognition for recognizing a description of the form from the image data of the form read by the image reading unit. Means, attribute information generating means for generating attribute information by setting a flag for each correction process associated with the recognizing means, and storage means for storing attribute information generated by the attribute information generating means for each form. It is characterized by having.
[0012]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a system configuration of a form terminal device.
[0013]
In FIG. 1, reference numeral 11 denotes a scanner unit that takes in the image data of the payout slip of FIG. 2 sucked from a suction port (not shown). The payment slip image data captured by the scanner unit 11 is sent to the OCR recognition unit (storage means) 12. In this OCR recognition unit 12, a partial image of the account number and the payment amount is extracted from the image data of the payment slip, and OCR recognition is performed.
[0014]
The result of OCR recognition is sent to the control unit 13 as form data. The control unit 13 includes a ROM 13a that performs the processing shown in the flowchart of FIG. 3, a data storage unit (storage unit) 13b that stores the above-described form data, and a storage unit 13c that stores the attribute information flag shown in FIG. It has been. As attribute information flags, there are a mismatch flag F1, a reject flag F2, and a manually corrected flag F3.
[0015]
Connected to the control unit 13 are a keyboard unit 14 provided with function keys such as a numeric keypad, an “insert” key, and an “item correction” key, a display unit 15, and a printing unit 16 that performs printing on a payment slip. Yes.
[0016]
Next, the payment slip will be described with reference to FIG. The payment slip 51 is composed of two parts. One (left side) is referred to as a payment handling slip (hereinafter also referred to as a main form portion) 52, and the other half (right portion) is referred to as a payment slip / receipt (hereinafter also referred to as a stub portion) 53.
[0017]
A form ID is printed as a numerical value on the left shoulder of the payment handling slip 52. For general forms, ID = “02” or the like, and for MT forms, ID = 03 or the like. Here, the MT form means a form on which payee account numbers 54 and 61 and payment amounts 55 and 62, which will be described later, are printed in advance. In the case of such MT forms, the misread rate due to OCR recognition is extremely small.
[0018]
In addition, the payment handling slip 52 includes a payment destination account number 54, a payment amount 55, a subscriber name 56 as a payment destination name, and a user address, name, and telephone number as payment information. A person column 57 is provided.
[0019]
Also, in the payment slip / receipt 53, as with the payment handling slip 52 as payment information, the payee account number 61, the payment amount 62, and the subscriber name 63 as the payment destination name are usually pre-printed. In addition, a client column 64 is provided in which the address, name, and telephone number of the user are written.
[0020]
Next, the operation of the embodiment of the present invention configured as described above will be described. When the form terminal device is activated, the processing shown in the flowchart of FIG. 3 is started. First, an initial screen for selecting a job is displayed on the display unit 15 (step S1).
[0021]
The clerk selects the business, that is, the payment business, from the business displayed on the display unit 15 (step S2).
[0022]
Then, clerk causes sucked payment slip 51 received from the user in the window through the inlet (not shown) (step S3).
[0023]
Thus, the payout slip 51 sucked from the suction port is checked for its own medium (step S4).
[0024]
Next, the image data of the payment slip 51 is captured by the scanner unit 11 (step S5). The image data of the payment slip 51 thus captured is displayed on the display unit 15 (step S6).
[0025]
Then, from this image data, an image corresponding to the account number 54 and the payment amount 55 of the main form portion 52 is extracted and recognized by OCR, and an image corresponding to the account number 61 and the payment amount 62 of the stub portion 53 is extracted. And OCR recognition is performed (step S7).
[0026]
The OCR recognition process in step S7 will be described with reference to the flowchart in FIG. That is, the account number 54 and payment amount 55 of the main form portion 52 are OCR recognized (step S21), and the account number 61 and payment amount 62 of the stub portion 53 are OCR recognized (step S22).
[0027]
Then, it is determined whether the account number 54 and the payment amount 55 of the main form portion 52 match the account number 61 and the payment amount 62 of the stub portion 53, respectively (step S24).
[0028]
If “NO” is determined in the determination in step S23, the mismatch flag F1 is set to “1” (step S24). Thereafter, the processing returns to the flowchart of FIG.
[0029]
In this way, by determining whether the account number 54 and the payment amount 55 of the form section 52 match the account number 61 and the payment amount 62 of the stub section 53, respectively, the accuracy of the items described in the payment form 51 is increased. Can do.
[0030]
If the result of the OCR recognition is that the OCR cannot be recognized, the reject character is corrected.
[0031]
In step S8, it is determined whether or not there is a reject character correction (step S8). If “YES” is determined in the determination in step S8, the reject flag F2 is set to “1” (step S9). Then, reject character correction processing is performed (step S10).
[0032]
When it is determined as “NO” in step S8 and when the reject character correction process in step S10 is completed, an OCR recognition result confirmation and correction screen is displayed on the display unit 15 (step S11).
[0033]
Next, it is determined whether the “insert” or “item correction” key has been operated (step S12). If it is determined in step S12 that the “item correction” key has been operated, the hand corrected flag F3 is set to “1” (step S13). Then, an item correction process is performed (step S14). That is, after the OCR recognition result displayed on the display unit 15 in step S11 is subjected to item correction processing by manual correction, the process proceeds to step S15. Note that attribute information generation means is configured by steps S24, S9, and S13.
[0034]
If it is determined in step S12 that the “insert” key has been operated, the process proceeds to step S15 in which it is determined that the content displayed on the display unit 15 is confirmed to be correct (step S15).
[0035]
In step S15, the transmission file as shown in FIG. 5 is stored in the data storage unit 13b.
[0036]
In this transmission file, the form image data, the OCR recognized account number, and the payment amount are stored as form data for each payment form 51, that is, for each form ID, and the hand corrected flag F3 from the top to the third bit is stored. The reject flag F2 and the mismatch flag F1 are stored.
[0037]
And the printing process which prints a predetermined matter by the printing part 16 in the margin parts 52a and 53a on the payment slip 51 is performed (step S16). Thereafter, the payment slip 51 is discharged, and a series of processing ends.
[0038]
As described above, the transmission files stored in the data storage unit 13b are sent to a center (not shown) and subjected to aggregation processing.
[0039]
If the total amount paid up and the total amount actually received at the window do not match in this tabulation process, it is necessary to check each form data again.
[0040]
In such a case, by checking the contents of the attribute information flags (manually corrected flag F3, reject flag F2, mismatch flag F1) stored in the transmission file, there is a problem in OCR recognition processing in which form data. It can be estimated.
[0041]
For example, when all of the hand corrected flag F3, the reject flag F2, and the mismatch flag F1 are “0”, it is estimated that all have been processed mechanically, and the possibility of misidentification can be determined to be minimal. .
[0042]
Further, when only the mismatch flag F1 is “1”, it is estimated that there is no stub, which is difficult to discriminate, and it can be determined that the possibility of misidentification is small.
[0043]
Further, when only the reject flag F2 is “1” (the disagreement flag F1 may be any), it is estimated that the determination is difficult, and it is possible to determine that the possibility of misidentification is moderate.
[0044]
Further, when only the hand correction flag F3 is “1” (the disagreement flag F1 may be any), it is estimated that there is an error in the processing content, and it is determined that the possibility of misidentification is moderate. it can.
[0045]
Further, when the manually corrected flag F3 and the reject flag F2 are “1” (the disagreement flag F1 may be any), it is estimated that the determination is extremely difficult.
[0046]
Thus, the cause of the error can be estimated from the state of the attribute information flag. In other words, the recheck priority is set according to the magnitude relationship such as the manually corrected flag F3> the reject flag F2> the mismatch flag F1. The priority of this recheck means the degree to indicate which form should be rechecked to find an error when the total of the amount paid in the aggregation process and the total amount actually received at the window do not match. To do. For example, when the manually corrected flag F3 is set to “1”, the highest error probability is set, so the recheck priority is set high.
[0047]
In any of the above-described embodiments, the scanner unit 11 that captures the image data of the payment slip 51 is used for OCR recognition. However, when a barcode is printed on the payment slip 51, A means for recognizing a bar code may be provided.
[0048]
【The invention's effect】
As described above in detail, according to the present invention, it is possible to provide a form terminal device capable of recording an error that occurs when recognizing a form.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a form terminal device according to an embodiment of the present invention.
FIG. 2 is a plan view of a payment slip according to the embodiment.
FIG. 3 is a flowchart for explaining the operation of the embodiment;
FIG. 4 is a flowchart for explaining recognition processing according to the embodiment;
FIG. 5 is a view showing an attribute information flag according to the embodiment;
FIG. 6 is a diagram for explaining an audit target method according to the embodiment;
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 11 ... Scanner part, 12 ... OCR recognition part, 13 ... Control part, 14 ... Keyboard, 15 ... Display part, 16 ... Printing part.

Claims (3)

In a form terminal device having a key input unit and a display unit,
Image reading means for capturing the image data of the form;
Recognizing means for OCR recognizing the items described in the form from the image data of the form read by the image reading means;
The hand modifications to OCR recognition result by the recognition unit and a reject flag is set when a rejected character modified unable OCR recognition by said recognition means and the hand correction flag is set when item modification process Attribute information generating means for generating attribute information including ,
A form terminal device comprising storage means for storing attribute information including the hand correction flag and the reject flag generated by the attribute information generation means for each form. Above the storage unit, form the terminal apparatus according to claim 1, characterized in that it is also stored image data and the OCR recognition result of a form read by further said image reading means for each form. The attribute information, form the terminal apparatus according to claim 1, characterized in that arranged in the priority order of the recheck embodiment.

Images