JP6530330B2 - Loan administration automatic check system and method - Google Patents

Description

  The present invention relates to a loan administration automatic check system and method.

  With the expansion of Internet services, the entire loan transaction business is an on-the-fly (paper-based) process, so customers, as well as front offices (hereinafter referred to as “fronts”) and middle back offices (hereinafter referred to as “middles”) There are various burdens (such as increase in workload and time required) in the “back” and so on, and it is desirable to computerize the loan transaction business. The front is a department within a financial institution that determines the terms of a loan transaction by, for example, directly communicating with a customer, and enters into a contract. The middle back is a department that checks the contents of the contract concluded between the customer and the front desk, and performs the execution procedure (payment procedure, etc.) of the contract. Among the front desks, there are also cases where the department that performs check work such as formal check of approval documents and confirmation of the contents of required documents (hereinafter referred to as “requisition documents”) at the time of loan execution is called front middle.

  In particular, when making a loan contract request from the front desk to the middle back, the front desk sends the actual contract and claim documents to the middle back, and the middle back checks the contents of the contract. In addition, if there is a defect in the middleback inspection, the middleback points out the problem to the front desk, and the front desk makes a complementary response (such as re-creating a contract), and then the contract Are sent to the middle back. When I point out a defect, I put a sticky note on the actual item and grasp the point and the content of the defect.

  As described above, since the loan processing is carried out by the actual documents of the contract and the request documents, it takes time for the actual loan processing to move the physical items, the point that the early response to the incomplete content of the contract is not sufficient, the contract There is a problem in that information sharing between the front and middle back is not sufficient for content deficiencies. Therefore, it is desirable to convert the contract document and the required documents into electronic data by scanning and to make the loan processing paperless. In addition, electronic data conversion such as contracts is expected to utilize electronic signatures and seal matching for loan processing.

  However, while paperbacking of loan processing is desired, front staff and middleback staff work at physically separated locations, so in the case of paperless paperwork, information such as the content of deficiencies due to inspection There is a possibility that sharing can not be performed efficiently. Therefore, there is a need for a system and method for more efficiently sharing information between the front and middle back while making the check work of the contract contents paperless in the loan processing.

  In addition, in the inspection work, there are many types of inspection documents and inspection items, and the inspection documents and inspection items also change depending on the contract content. As a result, the efficiency of inspection work is likely to affect the experience and capabilities of the individual in charge. In addition, since it is a human visual check, there is a possibility that an inspection leak may occur.

The present invention relates to a server computer that manages loan processing at the front and middle back to achieve such an object, wherein the server computer is
Contact slip data for requesting a loan contract check from the first computer used by the front to the second computer used by the middle back, and the scanned request document data simultaneously or sequentially, As well as relating and registering,
Distributing the contact form data to the second computer in response to a circulation instruction from the first computer;
After the contact slip data is circulated to the second computer, an inspection screen for checking the claim document data associated with the contact slip data in response to a request from the second computer is displayed. The screen data for displaying on the second computer and displaying the inspection screen includes annotation data for annotating the inspection document,
Receiving inspection result data indicating an inspection result of the inspection document and the annotation data provided by the middle back from the second computer;
In response to a circulation instruction from the second computer, the communication slip data is circulated to the first computer, and after the communication slip data is circulated to the first computer, the first It is characterized in that the inspection screen including the attached annotation is displayed on the first computer in response to a request from a computer.

  In the invention described in the preceding paragraph, the inspection screen further includes an inspection list display unit for inputting an inspection result, and the inspection list displayed on the inspection list display unit is inspected in the requisition document data. It is a list of necessary inspection items and is characterized in that it can be customized.

  Furthermore, in the invention described in the preceding paragraph, the server computer determines the inspection result by comparing the inspection item with a predetermined comparison item to be compared with the inspection item, and the inspection determined It is further characterized in that the result is included in the inspection screen and displayed on the first computer and / or the second computer.

  In the invention described in any one of the preceding three paragraphs, the server computer may include a comparison document referred to for inspection of the inspection document and associated with the inspection document in the inspection screen. It is further characterized in that it is configured to be displayed on the second computer.

  Furthermore, in the invention described in any one of the preceding four paragraphs, the inspection of the claim document data includes seal collation, and a seal collation screen for performing the seal collation is displayed on the second computer. Further, the verification result of the seal verification is included in the inspection result data.

In addition, the present invention is a method executed by a server computer that manages loan affairs at the front and middle back, the method comprising
Contact slip data for requesting a loan contract check from the first computer used by the front to the second computer used by the middle back, and the scanned request document data simultaneously or sequentially, And the step of associating and registering,
Circulating the contact form data to the second computer in response to a circulation instruction from the first computer;
After the contact slip data is circulated to the second computer, an inspection screen for checking the claim document data associated with the contact slip data in response to a request from the second computer is displayed. A step of displaying on the second computer, the screen data for displaying the inspection screen including annotation data for annotating the inspection document;
Receiving inspection result data indicating an inspection result of the inspection document and the annotation data provided by the middle back from the second computer;
Circulating the contact form data to the first computer in response to a circulation instruction from the second computer;
Displaying the inspection screen including the attached annotation on the first computer in response to a request from the first computer after the contact form data is circulated to the first computer; It is characterized by having.

Furthermore, the present invention is a computer program that causes a server computer to execute a method of managing loan administration at the front and middle back, wherein the computer program is executed by the server computer to the server computer
Contact slip data for requesting a loan contract check from the first computer used by the front to the second computer used by the middle back, and the scanned request document data simultaneously or sequentially And let me associate and register,
Causing the contact form data to be circulated to the second computer in response to a circulation instruction from the first computer;
After the contact slip data is circulated to the second computer, an inspection screen for checking the claim document data associated with the contact slip data in response to a request from the second computer is displayed. The screen data for displaying on the second computer and displaying the inspection screen includes annotation data for annotating the inspection document,
The inspection result data indicating the inspection result of the inspection document and the annotation data provided by the middle back are received from the second computer,
Causing the contact form data to be circulated to the first computer in response to a circulation instruction from the second computer;
Displaying the inspection screen including the attached annotation on the first computer in response to a request from the first computer after the contact slip data is circulated to the first computer; It features.

  As described above, according to the present invention, it is possible to realize the paperless processing of the loan processing, and the information sharing between the front and middle back can be made more efficient. Further, according to the present invention, it is possible to reduce the influence on the efficiency of inspection work and the omission of inspection due to the experience and ability of each person in charge of middleback.

It is a figure showing the system configuration concerning one embodiment of the present invention. It is a flowchart which shows the loan office work process which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the document data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the contract document data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the claim document data storage part based on one Embodiment of this invention. It is a figure which shows the data stored in the contact slip data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the inspection item data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the inspection result data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the annotation data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the inspection history data storage part which concerns on one Embodiment of this invention. It is a figure which shows the screen image of the inspection screen which concerns on one Embodiment of this invention. It is a figure which shows the screen image of the seal | collar collation screen which concerns on one Embodiment of this invention.

  An outline of a loan administration system according to an embodiment of the present invention will be described. FIG. 1 is a diagram showing a system configuration according to an embodiment of the present invention. In FIG. 1, the loan administration server 101 installed in a data center or the like is configured to communicate with the front terminal 103 and the middle back terminal 104 via the network 102 (for example, an intranet of a financial institution). There is. In FIG. 1, the loan administration management server 101 is shown as a single server, but it may be configured as a distributed system with a plurality of servers.

  The front terminal 103 is a terminal used by a front staff in a financial institution. The front person in charge uses the front terminal 103 to create a proposal and a contract. The created approval document data and contract document data are transmitted from the front terminal 103 to the loan administration server 101. The transmitted approval document data and contract document data are stored in the loan administration server 101, circulated through the front terminal 103, and received approval from the front authority. In addition, the front person in charge creates a contact slip using the front terminal 103, and checks the contents of the contract and requests execution to the middle back person in charge. At this time, the front person in charge scans a contract document or a claim document using the front terminal 103 (or using another terminal), and electronic data (for example, a PDF file) of each document is sent to the loan administration server 101 Sent and stored.

  The middle back terminal 104 is a terminal used by a middle back person in charge at a financial institution. The middle back person in charge uses the middle back terminal 104 to check the contents of the contract based on the contact slip received from the front person in charge. The inspection result is registered by the person in charge of middleback via the middleback terminal 104 and stored in the loan administration server 101. If there is no defect in the contents of the contract, the loan execution processing will be carried out if there is no problem after receiving the verification by the person in charge of the Middleback.

  If there is a defect in the contents of the contract, the person in charge of middleback registers the reason for the defect using the middleback terminal 104, and points out the defect to the person in charge of the front via the loan administration server 101. After that, the front desk person in charge confirms the reason for the insufficiency using the front terminal 103, and after taking corrective action, registers the answer contents in the loan business management server 101. The content of the registered answer is confirmed by the person in charge of middle back via the middle back terminal 104 as to whether the defect is resolved.

  The middleback authority can use the middleback terminal 104 to customize the inspection list (inspection item data) used when checking the contract content. This can be freely edited by the Middle-Bright's authority on the required documents for inspection (hereinafter referred to as “inspection documents”), comparison documents that are referred to in the inspection of inspection documents, and linked to inspection documents, and inspection items. It is possible.

  Next, the configuration of the loan administration server 101 will be described in detail. Note that FIG. 1 assumes only a single server computer system, and shows only necessary functional configurations.

  In the loan administration server 101, the CPU 110 is provided with a storage device 116 including a RAM 111, an input device 112, an output device 113, a communication control device 114, and a non-volatile storage medium (ROM, HDD, etc.) via a system bus 115. It has a connected configuration. The storage device 116 includes a program storage area for storing a software program for performing each function of the loan administration management system, and a data storage area for storing data handled by the software program. Each means of the program storage area described below is actually an independent software program, its routine or component, etc., and is called from the storage device 116 by the CPU 110 and expanded in the work area of the RAM 111, while referring to the database etc. Each function is performed by being sequentially executed.

  The software programs stored in the program storage area of the storage device 116 may be listed in the statement data management means 120, the contract document data management means 121, the request document data management means 122, the contact slip, if only those related to the present invention are listed. Data management means 123, inspection item data management means 124, inspection result data management means 125, annotation data management means 126, and inspection history data management means 127 are provided. These means are executed by the CPU 110.

  The approval document data management means 120 receives the approval document data from the front terminal 103 and stores it in the approval document data storage unit 130. Further, in response to a request from the front terminal 103 or the middle-back terminal 104, the CPU 201 acquires the approval document data stored in the approval document data storage unit 130, and transmits it to each of the requested terminals.

  The contract document data management unit 121 receives contract document data from the front terminal 103, and stores the contract document data in the contract document data storage unit 131. Further, in response to a request from the front terminal 103 or the middle back terminal 104, the contract document data stored in the contract document data storage unit 131 is acquired and transmitted to each of the requested terminals. In addition, the contract document data management means 121 receives electronic data (for example, a PDF file) of a contract document from the front terminal 103, and stores it in the contract document data storage unit 131 (or stores the PDF file in another place). , And stores data indicating the storage location in the contract document data storage unit 131).

  The invitation document data management unit 122 receives electronic data (for example, a PDF file) of the invitation document from the front terminal 103, and stores the electronic document data storage unit 132 (or stores the PDF file in another location and stores it) Data indicating the place is stored in the requested document data storage unit 132).

  The contact slip data management unit 123 stores the contact slip data received from the front terminal 103 or the middle back terminal 104 in the contact slip data storage unit 133. Further, in response to a request from the front terminal 103 or the middle back terminal 104, the contact form data stored in the contact form data storage unit 133 is acquired and transmitted to each requested terminal.

  The inspection item data management means 124 responds to the inspection document upon receiving an inspection start request instruction from the middle back terminal 104 (for example, an instruction to display the inspection document on the inspection screen for inspecting the contract contents). The inspection item data to be acquired is acquired from the inspection item data storage unit 134. The inspection item data is transmitted to the middle back terminal 104 by the inspection item data management means 124, and displayed as an inspection list on the inspection screen. Further, the inspection item data management means 124 receives the customization data of the inspection list (the inspection document and its inspection item, and the comparison item in the case of the automatic inspection) from the middle back terminal 104 and reflects it in the inspection item data storage unit 134 Do. In this way, inspection documents, comparison documents to be referred to in inspection of inspection documents, and inspection items can be freely edited.

  The inspection result data management means 125 receives inspection result data (including seal collation data) of the contents of the contract from the middle back terminal 104, and stores the inspection result data in the inspection result data storage unit 135. Further, the inspection result data management means 125 extracts the inspection item to be automatically inspected from the inspection item data, and determines the inspection result by comparing the inspection item to be automatically inspected and the corresponding comparison item. Perform an automatic inspection. The automatic inspection result is stored in the inspection result data storage unit 135 by the inspection result data management means 125. Also, upon receiving a display request instruction of a claim document under inspection (temporary storage state) or inspection completed from the front terminal 103 or middle back terminal 104, the target inspection result data is acquired from the inspection result data storage unit 135, and the request is made. Send to the terminal that was

  The annotation data management unit 126 receives, from the middle back terminal 104, the annotation data input to the inspection document on the inspection screen, and stores the annotation data in the annotation data storage unit 136. Also, upon receiving a display request instruction for a document requiring inspection (temporary storage state) or inspection from the front terminal 103 or the middle back terminal 104, the target annotation data is acquired from the annotation data management means 126, and the request is received. Send to the other terminal.

  The inspection history data management means 127 stores all the inspection result data and the annotation data inputted by the front terminal 103 and the middle back terminal 104 in the inspection history data storage unit 137 as inspection history data. Further, when receiving a display request instruction of inspection history data from the middle back terminal 104, the target inspection history data is acquired from the inspection history data storage unit 137 and transmitted to the requested terminal.

  Next, when only the data storage area in the storage device 116 is related to the present invention, the approval document data storage unit 130, the contract document data storage unit 131, the request document data storage unit 132, and the contact slip data storage unit 133. , An inspection item data storage unit 134, an inspection result data storage unit 135, an annotation data storage unit 136, and an inspection history data storage unit 137. Both are fixed storage areas secured in the storage device 116.

  The approval document data storage unit 130 stores data related to the approved approval in the loan transaction. FIG. 3 is a diagram showing data stored in the document data storage unit 130 according to an embodiment of the present invention. The approval document data in FIG. 3 is a “admission number” for identifying the approval document data, and a “admission serial number” indicating the version of the approval document in the same case (ie, “admission number” and “admission serial number”) (Data) can be uniquely identified), "Responsible branch code" uniquely indicating the managing shop that created the approval document, "person-in-charge code" uniquely indicating the creator of the approval document (front administrator), "Approver code" that uniquely indicates the approver of the approval document (front middle manager), "determiner code" that uniquely indicates the approver of the approval document (person in charge of examination department), account store of the financial institution business partner The account number uniquely identifying the account number, the account number indicating the account number of the business partner, the business partner ID uniquely identifying the business partner, the “consent amount” indicating the approved conspiracy amount, and the execution of the loan The "scheduled execution date" indicating the scheduled date "Deadline for handling", "Annual interest classification" for indicating annual interest classification, "Other conditions" for showing other financing conditions, and storage destination for storing electronic payment file Store the "document file". For example, when the approval document data is updated and registered for the “admission number” and the “admission serial number”, the “admission serial number” is registered in the form of increasing sequentially. Therefore, when searching for the same approval document data (the same "admission number"), it is possible to obtain data with the largest number of "admission serial numbers" as latest revision data. The "annual interest classification" can be set to a numerical value (1: 365 days basis, 2: 360 days basis, etc.) indicating an annual interest rate basis for the loan. The “other condition presence / absence” can be set to a numerical value (0: no other condition, 1: no other condition, etc.) indicating the presence or absence of a loan execution condition other than the condition of this data. For example, in the case of "1: other condition is present", another condition data other than this data can be referred to. The “review document file” may be the review document file itself (for example, a PDF file) or an address of a storage destination. The data content is an example, and does not prevent addition and deletion of items (the same applies to each data described below).

  The contract document data storage unit 131 stores data related to the contract concluded between the customer and the financial institution after approval approval. FIG. 4 is a view showing data stored in the contract document data storage unit 131 according to an embodiment of the present invention. The contract data in FIG. 4 includes “contract number” for identifying contract data and “contract sequence number” indicating a version of the contract in the same case (ie, “contract number” and “contract sequence number”). (Data can be uniquely identified), “date of contract” indicating the date when the contract was concluded between the customer and the financial institution, “loan amount” indicating the amount of loan, and “execution "Scheduled date", "repayment date" which indicates the scheduled completion date of the loan amount, "applied interest rate" which indicates the interest rate applied to the loan amount, "base rate classification" which indicates the base interest rate, and "Classification", "funding method" indicating the funding method which is the fund placement method, "contract file" for storing the electronic contract document file or indicating the storage destination, "uniquely showing the applied approval document" Application discussion To store the issue ". For “Contract number” and “Contract sequence number”, for example, if the contract document is recreated with replacement support due to an incomplete contract and the contract document data is updated and registered, “Contract serial number” is registered in the form of increasing sequentially Ru. Therefore, when the same contract document data ("contract number" is the same) is searched similarly to the approval document data, data with the largest "contract sequence number" can be acquired as the latest contract data. "Base rate classification" is a numerical value indicating the base interest rate to the loan (1: short-term prime rate, 2: market interest rate, 3: market interest rate (others), 4: others can be set. "Funding method" You can set a number (1: online funding, 2: call funding, 3: other funding, etc.) indicating how to arrange the funds: online funding is the management of funds within the financial institution. For example, when placing funds online through a core system to a department that is carrying out a call, and in the case of call funding, you can not make arrangements with the department online. If there is a reason to arrange the funds by telephone, other funding means online funding and This is an arrangement method that does not correspond to call funding (for example, although online, it is necessary to make a final confirmation by a human for the period and amount of money arrangement in order to arrange funds through multiple linkage systems). The annual interest classification is the same as the approval document data (Fig. 3). The "contract file" is the same as the "admission document file" in the approval data (Fig. 3). A number uniquely indicating the applied approved approval document is stored, for example, a combination of a “consultation number” and a “consultation serial number” (for example, a congression number + “-” (hyphen) + Consciousness serial number).

  The invoice document data storage unit 132 stores data relating to the invoice documents (necessary documents for making a loan) attached to the contract and registered by the front staff. FIG. 5 is a diagram showing data stored in the requested document data storage unit 132 according to the embodiment of the present invention. The invoice document data in FIG. 5 indicates a “contract number” uniquely indicating the attached contract, a “document * type” indicating the invoice document type, and an electronic reminder document file for storage or storage destination. Store "Documents *". The “contract number” is the “contract number” in the contract document data (FIG. 4) to which it is attached. The “contract number” can also be stored in the form including the “contract sequence number” as well as the “applicable congression number” in the contract data (FIG. 4), or only the “contract number” is stored and supported. The contract document data can also be determined to be the data with the largest number of “contract sequence numbers”. "Documents * Type" is a numerical value indicating the type of documents required (1: Consent, 2: Bank statement, 3: Warranty, 4: Seal certificate, 5: Promissory note, 6: Personal information agreement, 7: Confirmation intention, 8: Other, etc. can be set. Note that “*” of “document * type” and “document *” is an identification number of the document in management, and for example, it exists in order from 1. Although only the document 9 is shown in FIG. 5, naturally 10 or more may be present, or may be less than 9. Also, the type of document can be managed as a data record for each document instead of being managed as a data string. In this case, in addition to the “contract number”, for example, “document number” is set in the request document data, and records are added for the number of documents. “Documents *” is the same as the “Consultation Document File” in the Consent Document Data (FIG. 3). “8” (Others) in “Documents * Type” indicates that the document is other than 1 to 7 and, in the case of automatic identification of the document by optical character recognition (OCR), it can not be judged normally. Is also set. In this case, the front clerk or middle back clerk will reset the document type to the correct one. Note that, in FIG. 5, data in which "Document * Type" and "Document *" are blank indicates that no document exists. The number of types of solicitation documents attached to a contract varies depending on the content of the contract. Although the request document is determined based on the content of the contract, a condition master (not shown) for determining it is separately stored in the loan business management server 101.

  The contact slip data storage unit 133 stores contact data for checking the contents of the contract in loan processing and requesting execution. FIG. 6 is a view showing data stored in the contact slip data storage unit 133 according to the embodiment of the present invention. The contact slip data in FIG. 6 includes “contact number” uniquely indicating the contact slip, “progress status” indicating the progress of the loan processing, “contract number” indicating the contract subject to inspection and execution, and contract content. "Failure" showing the type of defect when there is a defect, "Correspondence status" showing the response status to the defect, and "Contact to the front" showing matters to be notified from the middle back to the front (mainly supplementary explanation for the defect reason) Store the “Middleback Address Notification” that indicates the “front matter” to “Middleback” notification (mainly supplementary explanation for the complementary response). "Progress status" is a numerical value indicating the progress status of loan processing (1: Creating a contact card, 2: waiting for an inspection request, 3: waiting for an inspection, 4: waiting for an inspection, 5: checked, etc.) Can. The “insufficient cause” can be set to a numerical value indicating the type of the inadequacy (1: violation of conspiracy condition, 2: lack of requested documents, etc.). "Correspondence status" is a numerical value that indicates the response status to the deficiencies (1: Contact to the front has not been made, 2: contact to the front has been completed, 3: complementary on the front, currently in the middle, and 4 on the middle back) Etc) can be set. In addition, in FIG. 6, although it is described that only one “reason for failure” and “response situation” can be registered, “reason for failure 1”, “case for failure 2”, “case for failure 3” and so on. Multiple deficiencies can be registered by enabling multiple columns to be set, or creating a record for each deficiency, etc. (the same applies to the “response status”).

  The inspection item data storage unit 134 stores data related to the inspection list used when inspecting the contents of a contract. FIG. 7 is a view showing data stored in the inspection item data storage unit 134 according to the embodiment of the present invention. The inspection item data in FIG. 7 includes “document type” indicating the type of inspection document, “inspection No.” indicating the order of arrangement in the inspection list, “format” indicating the inspection method, and “item name” indicating the name of the inspection item , "Start position" and "end position" indicating the start position and end position of the inspection item on the inspection document, respectively, "comparison document uniquely indicating the comparison document to be referred to in the inspection of the inspection document and linked with the inspection document" And “comparison start position” and “comparison end position” indicating the start position and end position of the comparison item on the comparison document, respectively. "Document type" is a numerical value indicating the type of inspection document (1: Conspiracy book, 2: Bank statement, 3: warranty, 4: seal certificate, 5: promissory note, 6: personal information agreement, 7: warranty Confirmation letter, 8: Other, etc. can be set. “Inspection No.” is the order of inspection items in the inspection list on the inspection screen (FIG. 11) described later. The “type” can set a numerical value (1: content check, 2: seal verification, 3: automatic check, etc.) indicating the check method of the check item. Here, 1: In the content inspection, the person in charge of middleback checks whether the content of the inspection item is complete or refers to other items, etc., and checks whether the content of the inspection item is inconsistent etc. It is. Further, 2: in the seal verification, the middle back person in charge cuts out the seal impression on the inspection document displayed on the inspection screen (for example, the range including the seal impression is designated by the drag & drop of the mouse), and the master seal impression registered in advance To make a comparison. And 3: 3: The automatic inspection is, for example, an inspection that can be judged whether it is correct or not by comparing the numerical values, and the computer (the loan administration server 101) automatically performs the inspection. The “start position” and the “end position” are, for example, xy coordinates (pixel position) with (0, 0) at the upper left of the inspection document. The contents of the inspection item are described in the area defined by the "start position" and "end position" (a rectangular area is formed with the start position at the upper left and the end position at the lower right. This area is called "inspection area") It can be determined that the contents of an inspection item by optical character recognition (OCR) can be acquired. The “comparison start position” and the “comparison end position” are also coordinates on the comparison document indicated by the “comparison document ID” (the area on the comparison document is referred to as “comparison area” for the inspection area). When the “type” of the inspection item is “3” (automatic inspection), the inspection content in the inspection area and the comparison content in the corresponding comparison area can be obtained respectively and compared with each other to perform the automatic inspection. Also, if the inspection content in the inspection area and the comparison content in the comparison area have already been acquired and stored in a predetermined table, the "start position" and "end position", and "comparison start position" and "comparison" The “end position” may not be the xy coordinates but a value indicating the storage destination (for example, a table ID, a value obtained by connecting column IDs by commas).

  The inspection result data storage unit 135 stores data related to the inspection result of the content of the contract. FIG. 8 is a view showing data stored in the inspection result data storage unit 135 according to the embodiment of the present invention. The inspection result data in FIG. 8 includes “contract number” for identifying contract document data to be inspected, “document name” indicating the name of invoice document subjected to inspection, “item name” indicating inspection item name, and inspection Store the “Inspection Result” indicating the result and the “Inspection Date” indicating the date of inspection. The “contract number” can be linked, for example, with the same name string of contract data (FIG. 4). “Inspection result” is a numerical value indicating the inspection result (1: OK by content inspection (manual inspection), 2: NG by content inspection (manual inspection), 3: OK by automatic inspection, 4: NG by automatic inspection, 5: By automatic inspection, it is possible to set the occurrence of an error (that is, the inspection is not completed due to an error, etc.).

  The annotation data storage unit 136 stores data related to the annotation (annotation) given to the inspection document. FIG. 9 is a diagram showing data stored in the annotation data storage unit 136 according to an embodiment of the present invention. The annotation data in FIG. 9 includes “contract number” for identifying contract document data to be inspected, “document type” indicating the type of inspection document, and “annotation type” indicating the type of annotation attached to the inspection document, "Start position" and "end position" indicating the start position and end position of the annotation on the inspection document, "color code" indicating the color of the annotation, "transmittance" indicating the transmittance of the annotation, and the annotation Stores a "comment" indicating the content of the comment. The “contract number” can be linked, for example, with the same name string of contract data (FIG. 4). "Document type" is a numerical value indicating the type of inspection document (1: Conspiracy book, 2: Bank statement, 3: warranty, 4: seal certificate, 5: promissory note, 6: personal information agreement, 7: warranty Confirmation letter, 8: Other, etc. can be set. The “annotation type” can set numerical values indicating the type of annotation (1: normal sticky, 2: defective sticky, 3: stamp, 4: memo, 5: straight, 6: freehand). Here, 2: Insufficient sticky notes have basically the same function as normal sticky notes (can be attached on inspection documents and comments can be written), but the color of sticky notes is red, pink, etc. It is possible to provide additional functions such as initial setting and linking the corresponding "comment" to the "address to be addressed to the front" in the report data (FIG. 6). And 3: a stamp is a mark (o, x, mark, etc.) that can be pasted on the inspection document. Although one stamp is used in FIG. 9, a plurality of stamps may be provided by increasing the “annotation type”. 4: A memo is not attached on the inspection document but a memo that is associated with the inspection document itself, and basically it is one for one document (also because it is not attached, the start position etc. Nothing is set in the data item of "Start position" and "end position" indicate the position of the annotation on the inspection document. For example, it is xy coordinates (pixel position) where the upper left of the inspection document is (0, 0). In the case of a normal tag or the like, the "end position" is not set, and the coordinates of the predetermined position of the tag can be held as the "start position". The “color code” is, for example, a hexadecimal color code. “Transmittance” is, for example, a percentage value representing transmittance. Note that the data items for expressing the annotation are not limited to the items in FIG. 9, and for example, settings such as an annotation definition in a general GUI component such as a value indicating the size of the annotation can be performed.

  The inspection history data storage unit 137 stores history data of the input inspection result and annotation. FIG. 10 is a diagram showing data stored in the inspection history data storage unit 137 according to an embodiment of the present invention. The inspection history data in FIG. 10 includes “contract number” for identifying contract document data to be inspected, “document name” indicating the name of invoice document subjected to inspection, “item name” indicating inspection item name, inspection “Inspection result” showing the result, “Annotation type” showing the type of annotation added to the inspection document, “start position” and “end position” showing the start position and end position of the annotation on the inspection document "Color code" indicating a color, "transmittance" indicating the transmittance of the annotation, "comment" indicating the comment content described in the annotation, "input date and time" indicating the date and time when the inspection result or the annotation was input, and Stores the "input person-in-charge code" indicating the person in charge. The “contract number” to “transmittance” are the same as those described in the inspection result data (FIG. 8) and the annotation data (FIG. 9). Note that this data is history data, and a record is created for each input of inspection results and annotations. For example, in the case of updating an annotation that has been input (pasted) once, two records of a record for the first input and a record for the update are created. By leaving all the historical data in this way, data tracking can be performed if something goes wrong.

  Next, a loan execution process according to an embodiment of the present invention will be described along the flow with reference to the flowchart of FIG. 2 and the data of FIG. 3-6. In this process, the front clerk enters into a loan contract with the customer based on the approval document data (Fig. 3) that has been approved in advance, and uses the contact slip to request the middleback clerk to check the contents of the contract. A person in charge of middleback checks the contents of the contract, and if there is a defect in the contents of the contract, a series of loan administration operations are performed through the computer system.

  The contract is concluded on a paper basis (the customer concludes the contract by sealing the paper), and a pattern for converting the contract into electronic data by scanning and contract data (FIG. 4) are created in advance (FIG. 4). The customer confirms the contract data via the computer terminal, and concludes the contract by electronically signing the paperless pattern.

  In the case of a pattern in which the contract is converted into electronic data by scanning, the front clerk scans the paper-based contract and request documents, and uses the contact slip to make an inspection request to the middle back clerk.

  In the case of the paperless pattern, the front clerk inputs the contract contents (loan conditions such as interest rate information and recovery information) in the communication slip, scans the paper-based request documents, and then uses the communication slip to make a middleback clerk Make an inspection request to

  The person in charge of middleback who has received the inspection request from the contact form checks the contents of the contract and the terms of review, the existence of documents required, the confirmation of the contents, and checks such as seal verification.

  FIG. 2 is a flow chart showing a loan administration process according to an embodiment of the present invention. This processing flow starts with the front representative creating a contact card to the middle back representative in order to request inspection of the contents of the contract after the contract has been concluded between the front representative and the customer.

  First, in step 201, the contact slip data management means 123 receives, from the front terminal 103, the contact slip data newly created by the front person in charge, and stores it in the contact slip data storage unit 133. The contact slip data at this stage is such that the “progress status” is “1” (during the creation of the contact slip), as in the record of “contact number” of “4” in FIG. As a matter of course, "missing reasons" etc. have not been registered yet. The “contact number” in the contact slip data (FIG. 6) is numbered and stored when newly created in the contact slip data storage unit 133. The “contract number” in the contact slip data (FIG. 6) is a number for identifying the contract document data to be checked, and corresponds to (or is the same as the “contract number” in the contract document data (FIG. 4) When multiple “contract numbers” exist in the contract data, the “contract number” corresponds to the record having the largest number among the same “contract number” records). In addition, preparation and update of the communication slip data, the contract document data described in detail below, etc. can be performed via a website for loan paperwork (hereinafter referred to as “dedicated site”).

  Also, it is assumed that contract document data (FIG. 4) will be created at the same time or before or after the contact form is created. In the case of a paper-based contract, the front clerk scans the contract with the front terminal 103 or another terminal, and transmits electronic data (for example, a PDF file) of the contract to the loan administration server 101. The transmitted electronic data of the contract document is received by the contract document data management means 121 and stored in the contract document data storage unit 131 (or the PDF file is stored in another location, and data indicating the storage location (for example, The “contract file” in FIG. 4 is stored in the contract data storage unit 131). In the case of the paperless pattern of the contract, the front clerk prepares contract data using the front terminal 103 and sends it to the loan administration server 101 in conjunction with the contact slip creation. The transmitted contract document data is received by the contract document data management means 121 and stored in the contract document data storage unit 131.

  In addition, along with creation of contract electronic data or contract data, the front person in charge scans the paper-based request documents using the front terminal 103, and receives electronic data (for example, PDF file) of the request documents, It sends to the loan administration server 101. The electronic data of the sent request document is received by the request document data management means 122 and stored in the request document data storage unit 132 (or the PDF file is stored in another location, and data indicating the storage location (for example, “Document *” in FIG. 5 is stored in the requested document data storage unit 132). In addition, "Document * type" in the requested document data (Fig. 5) can be set manually based on the data selected by the person in charge of the front using the front terminal 103, the file name of the electronic data, and the optical character The type of the document can also be automatically determined and set by a predetermined code or the like in the document identified by the recognition (OCR). In addition, if it can not be determined automatically, by setting “Document * Type” to “8” (Others), for example, the correct document can be sent to the person in charge of the front desk or the person in charge of middle back at the time of confirmation. You can also set the type.

  Next, in order to receive the approval of the front desk authority with respect to the contact slip (data) created in step 201, the contact slip data management means 123 circulates the contact slip (step 202). This is because, for example, the front person in charge who created the contact slip designates the authorized person to receive approval using the front terminal 103, and only the designated authorized person can approve the contact slip by the contact slip data management means 123. To control. Further, at this stage, the "progress" in the contact slip data (FIG. 6) is updated to "2" (waiting for check request) by the contact slip data management means 123. If the approval of the front desk authority is not received, the contact slip data management means 123 does not execute steps 202 to 204, and the contact slip (data) created in step 201 is circulated to the middle back (step 205) You may

  The contact slip data circulated in step 202 (FIG. 6), the contract data to be checked (FIG. 4) and the claim document data (FIG. 5) are checked by the front authority, and if the check is OK, the step The process proceeds to the Yes route 203, and is circulated to the middle back by the contact form data management means 123 (step 205). In this case, the "progress" in the contact slip data (FIG. 6) is updated to "3" (waiting for inspection) by the contact slip data management means 123. On the other hand, in the case of a check NG, the process proceeds to the No route of step 203, and the front person in charge or authority corrects the communication slip etc using the front terminal 103 (step 204), and the problem is solved and then corrected. A contact slip or the like is circulated to the middle back by the contact slip data management means 123 (step 205).

  When the contact slip or the like is circulated to the middle back in step 205, the middle back person in charge checks the contract contents using the middle back terminal 104 (step 206). Specifically, the inspection request list of the dedicated site is displayed on the middle back terminal 104, and the content of the contract is inspected by selecting a contact slip to be inspected. The check of the contents of the contract, for example, confirms the contents of contact form data (FIG. 6), contract data (FIG. 4) and claim data (FIG. 5) created by the front staff. This refers to the content of the approval document data (FIG. 3) to check whether the content of the contract violates the terms of the approval, and whether there is an excess or a deficiency of required documents. Note that the approval document data, the contract document data, the request document data, and the contact slip data are associated by the approval number or the contract number as shown in FIG. 3-6, and according to the request instruction from the middleback terminal 104 The respective data can be associated and displayed on the middle back terminal 104. In addition, the loan administration server 101 calculates the collation rate (identity rate) by superimposing the seal imprint on the electronically converted contract and the seal imprint of the master seal registered regular seal, and the person in charge of middleback Seal verification can also be performed based on the verification rate.

  If a defect is confirmed by checking the contents of the contract in step 206, the process proceeds to the Yes route of step 207, and the person in charge of middleback registers the reason for the failure through the middleback terminal 104 and sends it to the front (step) 208). With the registration of the inadequacies, for example, “Income reasons” in the contact slip data (FIG. 6) is selected from the dedicated site displayed on the middle back terminal 104, and the detailed contents are registered in the “Contacts to Front”. . In addition, by giving a circulation instruction to the front by pressing a button on the dedicated site, etc., the contact slip data management means 123 notifies the “response status” in the contact slip data (FIG. 6) “2” (the front Update). In addition, when only the content of the deficiency is registered and the circulation instruction to the front has not been issued yet, the “response status” can be updated to “1” (contact to the front is not yet made).

  When circulation to the front is performed in step 208, the content of the defect is confirmed at the front, and after being complemented, it is recycled again to the middle back (step 209). The front person in charge corrects (updates) deficiencies in contact slip data (FIG. 6), contract data (FIG. 4), and request document data (FIG. 5) via the dedicated site displayed on the front terminal 103, The detailed contents of the complementation correspondence are registered in the "contact information for middle back" in the report data (FIG. 6). When the front person in charge re-creates a contract in the complementary support, the contract document data management means 121 newly receives contract data (FIG. 4) from the front terminal 103, and the contract document data storage unit 131. Store in In this case, a new record is added to the contract data, but the "contract number" of the newly added contract data is the same as the original contract data, and the "contract sequence number" is, for example, sequentially The added one is set. In addition, by giving a repeat instruction to the middle back, the contact slip data management means 123 converts the “response status” in the contact slip data (FIG. 6) to “4” (the front response has already been answered by the middle back as a complement). Update. Note that the “response status” can be updated to “3” (while the front is in the process of complementation) if the middleback instruction is not yet issued while the process is being complemented. If the middle bag is re-used, the middle back person in charge checks again (step 206) and repeats steps 206-209 until the defect is resolved.

  If the defect is not confirmed by the inspection of the contract contents in step 206, the process proceeds to No route of step 207, and after verification by the person in charge of middleback, if there is no problem, based on the contract data and request document data etc. , And a loan execution process to another computer etc. (step 210). In another embodiment, even if all the deficiencies have not been eliminated, it is permitted to complete the inspection at the discretion of the person in charge of middleback (for example, the inspection is completed with the deficiency remaining in the middleback terminal 104). At the time of verification, it is also possible to control not to be completed if all the deficiencies have not been eliminated. After step 210, the process ends.

  In addition, it is possible to manage the location of the contract and the request documents that have been converted into electronic data by this system or another system. From the front desk, middleback or a designated storage location, after the actual documents in the contract and claim documents have been checked by the middle back on the basis of the electronically converted contract, etc. and no problem (after step 210) Will be mailed. At this time, the system can issue a transmittal letter for mailing. For example, the transmittal letter can be issued at the timing when the "progress" in the contact slip data (FIG. 6) is updated to "5" (checked). Furthermore, it is possible to print a two-dimensional code (for example, a QR code (registered trademark)) on a transmittal letter, read the code when a transmittal letter is received, and update a status indicating a location or delivery status.

  Next, with reference to the data of FIGS. 7-10 and the screen images of FIGS. 11 and 12, the details of the inspection process according to the embodiment of the present invention will be described. The inspection process includes, in addition to the inspection process of step 206 in FIG. 2, communication to the front and a complementary response at the front (steps 207 to 209) when there is a defect.

  FIG. 11 is a view showing a screen image of an inspection screen according to the embodiment of the present invention. The inspection screen is a screen of a dedicated site for loan paperwork that is distributed from the loan paper management server 101 to the front terminal 103 and the middle back terminal 104. The inspection screen is, for example, a notification document linked by the communication slip and the contract number when the communication slip for the inspection request is circulated from the front to the middle back via the dedicated site (step 205 in FIG. 2) Is selected to perform an inspection of the selected request documents. The person in charge of middleback uses this screen to check the claim documents and input the check results. The person in charge of the front desk uses this screen to check the inspection results.

  Details of the inspection screen (FIG. 11) will be described. The inspection screen has an inspection object display unit 1101, a comparison document display unit 1102, an inspection list display unit 1103, and an annotation tool box unit 1104.

  The inspection target display unit 1101 is a portion for displaying one of the inspection documents. For example, the inspection document can be displayed on the inspection object display unit 1101 by selecting the invoice document to be inspected from the inspection list display unit 1103 described later. Moreover, in the case of a claim document which does not have an inspection list, it can also be displayed by selecting from an inspection document list (not shown) or the like. The documents for the request are all created or scanned by the front desk person using the front terminal 103, and stored on the loan administration server 101 or the like.

  Four buttons are displayed on the upper part of the inspection target display unit 1101. By pressing the “seal collation” button, it is possible to display a seal collation screen (FIG. 12) described later. By pressing the "inspection complete" button, the status can be advanced to the inspection completed state while saving the input inspection result and annotation (for example, "progress status" of the communication form data (FIG. 6) Update to (Checked). In addition, if all the deficiencies have not been resolved, the "completion of inspection" button is deactivated (unable to be pressed), or a message indicating that all the deficiencies have not been resolved at the time of pressing is displayed. It can also be controlled so that it can not be (in the case of a message display, it can be controlled so as to select whether or not the inspection is completed as it is). By pressing the “temporary save” button, the inspection status is not entered (the “progress status” of the contact card data (FIG. 6) is updated to “4” (under inspection)) Annotations can be saved. In the temporary storage state, it is possible to notify the front to a defect (step 208) using a contact form input screen (not shown). By pressing the “cancel” button, this screen can be closed (transition to the previous screen, etc.) without saving the input inspection result or annotation. In addition, the inspection result and annotation data that have been input are transmitted from the middleback terminal 104 to the loan business management server 101 by pressing the “inspection completed” button or the “temporary storage” button, and the inspection data management means 125 8) is created and stored in the inspection result data storage unit 135. At this time, the inspection history data storage unit 137 also stores inspection history data (FIG. 10) created by the inspection history data management means 127. Note that the “stamp verification”, “check complete”, and “temporary save” buttons can also be controlled to be hidden or not pressed by the login clerk authority of the loan administration system (for example, check results In the case of the front clerk, control is performed so that the "inspection complete" button can not be pressed.

  Four buttons are displayed at the bottom of the inspection object display unit 1101. By pressing the “enlarge” / “reduce” button, the inspection document displayed on the inspection object display unit can be enlarged / reduced and displayed at a predetermined rate. By pressing the “←” / “→” button, when the inspection document displayed on the inspection object display unit has a plurality of pages, it is possible to return / return the page. In addition, check document enlargement / reduction and page return / forward can be performed in synchronization with the comparison document. If the front terminal 103 or the middle back terminal 104 is a touch panel display or the like, it is possible to double-tap to zoom in / out and to swipe back / forward the page.

  The comparison document display unit 1102 is a portion that displays a comparison document that is referred to when checking the inspection document displayed on the inspection target display unit 1101 and that is linked to the inspection document. The comparison documents displayed in the comparison document display unit 1102 can be displayed by selecting from a comparison document list (not shown) or the like, or the comparison documents linked to the inspection documents can be searched and displayed. . When a comparison document is not necessary at the time of inspection, the comparison document display unit 1102 does not necessarily have to display the comparison document. Four buttons are also displayed at the bottom of the comparison document display unit 1102. As a result, enlargement, reduction, page return, or page feeding can be performed on the comparison document displayed in the comparison document display unit 1102 (similar to the description in the inspection target display unit 1101).

  The inspection list display portion 1103 is a portion where the inspection items necessary for each inspection document are displayed, and the person in charge of middleback inputs the inspection result. The inspection list display unit 1103 includes a header unit 1114 and a list unit 1115. The header unit 1114 is provided for each inspection document, and expands the list unit 1115 for each inspection document by pressing the header unit 1114 with a mouse click or the like. As shown in FIG. 11, there are three inspection documents, “○○○○○○ book”, “××××××× book”, and “ΔΔΔΔΔΔ book”, “○○○○○○ It shows a state in which the list portion 1115 of the "book" is expanded. Further, the inspection document displayed on the inspection object display unit 1101 can be changed to the corresponding inspection document by pressing the header unit 1114.

  The list unit 1115 displays an inspection list, that is, inspection items and inspection results of each inspection document. The inspection item is created by the inspection item data management means 124 based on the inspection item data (FIG. 7) acquired from the inspection item data storage unit 134. “No.”, “format”, and “item” of the list unit 1115 correspond to “inspection No.”, “format”, and “item name” of the inspection item data, respectively. “Auto” in the list unit 1115 displays the result in the case of the automatic inspection target. For example, the automatic processing result of No. 5 (contract document type) in FIG. 11 displays a warning mark indicating that an error such as an OCR reading error in automatic inspection has occurred. Moreover, the automatic processing result of No. 6 (contract date) displays the check mark which shows that it was OK by automatic inspection.

  The “inspection result” of the list unit 1115 has “OK” / “NG” button for each inspection item, and the inspection result can be input by pressing each button. When the "OK" / "NG" button is pressed, it remains pressed and the inspection result is set (it is possible to release the pressed state again by pressing the button). In order to highlight the pressed state of the "OK" / "NG" button, change the button color in the pressed state of the "OK" button to blue, and change the button color in the pressed state of the "NG" button to red or the like. You can also.

  The input inspection result (data) is sent to the loan administration server 101 by pressing the “inspection completed” or “temporary save” button, and the inspection result data management means 125 generates inspection result data (FIG. 8). It is created and stored in the inspection result data storage unit 135. When the inspection result stored in the inspection screen (FIG. 11) is opened again (strictly, the loan management server 101 displays a signal indicating that the inspection screen is displayed from the front terminal 103 or the middle back terminal 104). When received, it is acquired from the inspection result data storage unit 135 by the inspection result data management means 125 and displayed on the inspection list display unit 1103.

  In addition, by pressing each inspection item in the list portion 1115 by mouse click or the like, the corresponding inspection item and comparison item on the inspection document and the comparison document are highlighted (for example, the items are surrounded by a bold frame). It can also be done. This can be realized by specifying the position of each item using “start position” and “end position” in the inspection item data (FIG. 7) and “comparison start position” and “comparison end position”. it can. In addition, when the format of the inspection item is seal collation, the seal collation screen (FIG. 12) for the inspection item clicked can be displayed by clicking the inspection item in the list portion 1115 with a mouse.

  The header portion 1114 can display the inspection document name, the “all OK” button, and the implementation status. By pressing the “All OK” button, all check results of the target check documents are set to OK (Skilled middleback personnel need not input check results one by one from the check list display section 1103. , Batch input is possible with this button). For example, as shown in FIG. 11, the implementation status can display the number of OKs and the number of NGs of inspection results, the number of inspections that have not been performed, and the total number of inspection items. As a result, even in the case of an inspection document in which the list unit 1115 is not expanded, the implementation status of the inspection can be confirmed.

  The annotation tool box unit 1104 is an operation unit for a middleback person or the like to define an annotation and attach it to an inspection document. The annotation tool box unit 1104 has various buttons and an annotation setting field as shown in FIG. By pressing the “sticky note” button, a sticky note 1113 is displayed, and can be attached to an arbitrary place, for example, by dragging and dropping a mouse. Further, a comment can be input to the sticky note 1113 by mouse clicking the sticky note 1113 or the like. Furthermore, the tag 1113 can be enlarged or reduced by dragging and dropping the end of the tag 1113 with the mouse. By pressing the “poor sticky note” button, the defective sticky note 1112 is displayed. The incomplete sticky note 1112 basically has the same function as the sticky note 1113, but is set to a color that is easier to draw attention, such as an initial setting color such as red or pink.

  By pressing the "Restore" button, it is possible to return one operation (or return to the initial display state) to the currently operating (selected) annotation. By pressing the "delete" button, it is possible to delete the currently operating (selected) annotation.

  By pressing the “/” (straight line) button, a straight line is displayed, and the straight line can be expanded and contracted by dragging and dropping the mouse, and can be attached to any place. By pressing the "-" (freehand) button, a freehand line can be drawn by dragging and dropping the mouse, and the freehand can be attached to any place. The style of the straight line and the freehand line can be designated by an annotation setting field at the bottom of the annotation tool box 1104. The color of the line in the "color" column, the width of the line in the "width" column, and the transmittance of the line in the "transmittance" column can be specified.

  By pressing the “stamp” button, the stamp 1111 is displayed and can be attached to any place. The stamp 1111 can also be enlarged, reduced, and moved by dragging and dropping as in the case of the sticky note 1113.

  By pressing the “memo” button, for example, a memo input field is displayed, and a comment can be input in association with the inspection document. Although the memo is operated from the annotation tool box 1104, it is not a paste on the inspection document but a memo associated with the inspection document itself, and there is one memo in one inspection document.

  Next, for example, the seal collation screen to be called up by pressing the “seal collation” button on the inspection screen (FIG. 11) will be described. FIG. 12 is a view showing a screen image of a seal collation screen according to an embodiment of the present invention. The seal verification screen is a screen for performing seal verification performed by a person in charge of middleback as one of the inspection operations.

  The details of the seal verification screen (FIG. 12) will be described. The seal collation screen has a reading seal column 1201, a delivery seal column 1202, and a collation result column 1203. The read seal column 1201 is a column for displaying a seal imprint (hereinafter referred to as a “collation seal imprint”) extracted from the inspection document. Three buttons are displayed at the bottom of the read mark field 1201. By pressing the “rotate left” / “rotate right” buttons, for example, the collation imprint displayed in the read seal column 1201 can be rotated leftward / clockwise by 90 °, for example. By pressing the “cut out” button, the check document displayed on the check screen (FIG. 11) can be displayed again, and cut out can be performed by designating the range including the collation imprint by the drag and drop of the mouse. The cut out seal impression is displayed in the read mark field 1201.

  The delivery seal column 1202 is a column for displaying a pre-registered master seal impression to be compared with the collation seal impression. The master seal imprint is a seal imprint registered in advance in association with an inspection item (for example, “debtor” of No. 7 of the list unit 1115). Therefore, for example, No. 1 in the list unit 1115. When the column 7 is selected by a mouse click or the like and the seal collation screen (FIG. 12) is displayed, the master seal impression corresponding to the delivery seal column 1202 can be displayed.

  Four buttons are displayed at the bottom of the delivery mark column 1202. By pressing the “rotate left” / “rotate right” buttons, for example, the master seal imprints displayed in the delivery mark column 1202 can be rotated by 90 ° leftward / rightward, for example. By pressing the “cut out” button, for example, a comparison document list (not shown) can be displayed, a comparison document can be selected, and then a master imprint can be newly cut out from the selected comparison document. The stamped out seal is displayed in the delivery mark column 1202. By pressing the "switch" button, it is possible to display a master seal imprint list (not shown) and switch to another master seal imprint registered in advance. The seal imprint selected in the master seal imprint list is displayed in the delivery seal column 1202.

  The collation result column 1203 is a column for displaying the collation seal imprint displayed in the reading seal column 1201 and the master seal impression displayed in the delivery seal column 1202 in an overlapping manner to perform seal collation. The collation impression and the master impression displayed in the collation result column 1203 can be selected by mouse click or the like and moved by dragging and dropping. The seal collation using the collation result column 1203 can be visually confirmed by a person in charge of middleback, or the collation rate (coincidence rate) can be calculated from the overlap of the pixels of the collation seal and the master seal. Further, the background color of the collation result column 1203 can be changed according to the collation rate (for example, a collation rate of 30% or less is yellow indicating attention, and a color of 10% or less indicates red).

  Four buttons are displayed in the lower part of the collation result column 1203. By pressing the “enlargement” / “reduce” button, it is possible to enlarge / reduce the selected collation impression or master impression, respectively. The collation result can be registered by pressing the “collation OK” / “collation NG” button. The registered verification result is reflected on the "inspection result" of the corresponding inspection item in the list portion 1115 of the inspection screen (FIG. 11) (the "OK" button or the "NG" button is pressed depending on the collation result) ). By pressing the "cancel" button, it is possible to cancel the setting state of the seal collation screen (FIG. 12) and return to the inspection screen (FIG. 11).

  As described above, according to the present invention, paperless loan processing can be realized, and information sharing between the front and middle back can be made more efficient. Further, according to the present invention, it is possible to reduce the influence on the efficiency of inspection work and the omission of inspection due to the experience and ability of each person in charge of middleback.

Claims (6)

A server computer that manages the loan processing at the front and middle back, wherein the server computer is
Contact form data for requesting a loan contract check from the first computer used by the front to the second computer used by the middle back, and scan data of the request documents received simultaneously or in succession, and Associate and register,
Distributing the contact form data to the second computer in response to a circulation instruction from the first computer;
After the contact slip data is circulated to the second computer, a person in charge of middleback checks the scan data of the solicitation document associated with the contact slip data according to the request from the second computer. To display the inspection screen for the second computer on the second screen, and the inspection screen is annotated with the inspection list for displaying the inspection items to be inspected by the middle buck representative for each of the claim documents and the inspection screen Containing annotation data to give
Receiving inspection result data indicating inspection results for the inspection item and / or the annotation data from the second computer;
In response to a circulation instruction from the second computer, the communication slip data is circulated to the first computer, and after the communication slip data is circulated to the first computer, the first Displaying the inspection screen on the first computer in response to a request from the computer ;
The inspection result is determined by comparing the inspection item with a predetermined comparison item to be compared with the inspection item, and the determined inspection result is reflected in the inspection list to perform the first computer and / or the second server computer, characterized in that the is configured to Ru is displayed computer.   The inspection list is further for inputting the inspection result, and the inspection item can be customized and is associated with the corresponding portion in the scan data of the requisition document displayed on the inspection screen. The server computer according to claim 1, characterized in that A reference document for checking the scan data of the claim document, and a comparison document associated with the claim document are further included in the check screen and displayed on the second computer. A server computer according to claim 1 or 2 . The inspection of scan data of the claim document includes seal verification, and is further configured to display a seal verification screen for performing the seal verification on the second computer, and the verification result of the seal verification is the inspection server computer according to any one of claims 1 to 3, characterized in that the results included in the data. A method performed by a server computer that manages the financing operations at the front and middle back, said method comprising
Contact form data for requesting a loan contract check from the first computer used by the front to the second computer used by the middle back, and scan data of the request documents received simultaneously or in succession, and Associating and registering, and
Circulating the contact form data to the second computer in response to a circulation instruction from the first computer;
After the contact slip data is circulated to the second computer, a person in charge of middleback checks the scan data of the solicitation document associated with the contact slip data according to the request from the second computer. Displaying an inspection screen for the second computer on the second screen, the inspection screen displaying an inspection list for displaying the inspection items to be inspected by the A step including annotation data for annotating the inspection screen;
Receiving inspection result data indicating inspection results for the inspection item and / or the annotation data from the second computer;
Circulating the contact form data to the first computer in response to a circulation instruction from the second computer;
Displaying the inspection screen on the first computer in response to a request from the first computer after the contact slip data is circulated to the first computer ;
The inspection result is determined by comparing the inspection item with a predetermined comparison item to be compared with the inspection item, and the determined inspection result is reflected in the inspection list to perform the first computer And / or displaying on the second computer . A computer program that causes a server computer to execute a method of managing loan administration in front and middle back, wherein the computer program, when executed by the server computer, causes the server computer to
Contact slip data for requesting a loan contract check from the first computer used by the front to the second computer used by the middle back, and scan data of the request documents at the same time or before and after, and Associate and register,
Causing the contact form data to be circulated to the second computer in response to a circulation instruction from the first computer;
After the contact slip data is circulated to the second computer, a person in charge of middleback checks the scan data of the solicitation document associated with the contact slip data according to the request from the second computer. To display the inspection screen for the second computer on the second screen, and the inspection screen is annotated with the inspection list for displaying the inspection items to be inspected by the middle buck representative for each of the claim documents and the inspection screen Containing annotation data to give
Receiving inspection result data indicating inspection results for the inspection item and / or the annotation data from the second computer;
Causing the contact form data to be circulated to the first computer in response to a circulation instruction from the second computer;
After the contact slip data is circulated to the first computer, the inspection screen is displayed on the first computer in response to a request from the first computer ,
The inspection result is determined by comparing the inspection item with a predetermined comparison item to be compared with the inspection item, and the determined inspection result is reflected in the inspection list to perform the first computer and / or a computer program, characterized in that Ru is displayed on the second computer.