JP6087452B1 - Paper document management system - Google Patents

Abstract

[PROBLEMS] To verify the presence / content of a necessary document according to a contract while managing a paper document storage state of the contract document. The method includes receiving image data and contract type information of a contract document from a first client computer, acquiring contract document rule data based on the contract type information, and the contract document rule data. Acquiring individual document rule data based on the contract document information, verifying the contract document corresponding to the image data based on the verification rule information included in the individual document rule data and the image data, and contract management Updating the data to a value indicating that the contract document has been verified; transmitting a cover page output message to the first client computer; and receiving the cover page image data from the second client computer. Based on the step and image data, the contract management data It is updated to a value indicating a and a step. [Selection] Figure 3

Description

  The present invention relates to a contract document management system, and more particularly to a contract document management system that manages physical paper documents such as contract documents.

  In a loan business performed by a financial institution such as a bank, a financial institution creates a contract that is a paper document, and a customer (loaner) stamps and signs the contract, thereby establishing a loan contract. In recent years, insurance contracts such as non-life insurance are increasingly being established through online transactions (ie, electronic media) via the Internet, etc., but there are still more transactions through paper documents as described above in loan contracts. ing. This is because the amount of funds covered by the loan contract is higher than that of non-life insurance, and the decision-making rights in the loan on the customer (loaner) side are limited to some managers. This is because a face-to-face transaction between a customer and a transaction representative of a financial institution is desired.

  Explain the current typical loan contract process in financial institutions. First, at a primary verification base such as each sales office of a financial institution, a loan (credit) is deliberated, and a contract and ancillary documents (hereinafter referred to as contract documents) necessary for a loan contract are created (contract creation).

  Next, the person in charge of the transaction brings the contract document to the customer, conducts a face-to-face loan transaction between the customer and the person in charge of the transaction, and seals the contract document (contract establishment).

  Next, the person in charge of the transaction takes the contract document stamped back to the primary verification base, and seal verification is performed at the primary verification base (primary verification base verification). Then, a contact form for sending the contract document to the secondary verification base for verifying whether the contract document is incomplete is created. When the contact form is created, the contract document is sent to the secondary verification base by mail or the like (secondary verification base transmission). This delivery takes several days.

  Next, when the contract document arrives at the secondary verification site, the secondary verification site verifies that the content of the contract document is complete (for example, whether the contract document is complete or not) (Whether the necessary information is described in the column or is a seal) (secondary verification site verification). Here, if the contract documents are incomplete, the primary verification base is informed that the incompleteness is in place, and if necessary, the person in charge of the transaction visits the customer again to provide supplementary correspondence to the contract documents.

  After verification at the secondary verification site is completed, the contract document is converted into image data (scanned with a scanner and converted into an electronic document, etc.), and the paper document of the contract document is stored in a document storage site that centrally stores paper documents. Will be sent. The paper document sent to the document storage base is stored and stored in a safe or the like (document storage).

JP 2013-131039 A

  The following problems exist in the above-described current loan contract work process. First, each paper document is verified each time it is physically moved, such as from the primary verification base to the secondary verification base, or from the secondary verification base to the document storage base. There is nothing. Due to this, it is impossible to manage whether the document is sent in a state of being verified at each site, or whether the document has normally arrived at the document storage site. In particular, the paper documents of the contract documents required for the loan contract are very confidential and are required to be strictly managed.

  In addition, the second problem is that at each base, it is verified by human judgment that necessary documents are prepared for each loan contract and that the contents of each document are verified. For this reason, work efficiency in the loan contract business is poor, and there is a risk of human error. In particular, contract documents differ depending on the products, options, guarantor attributes, etc. in the loan contract, and the necessary documents including incidental documents differ depending on the experience of the verifier.

  Patent Document 1 discloses a document management system that digitizes and manages paper documents such as documents and forms. In the invention according to Patent Document 1, a plurality of items to be used as search keys are determined in advance according to the type of document, and item content identification information (for example, an identifier indicating each item and the content of the item is included) , Barcode) is displayed on a paper document to be imaged by stamping or attaching a sticker.

  However, the invention according to Patent Document 1 does not manage the state of sending and storing paper documents. Further, the invention does not verify whether a necessary description item is included in each document.

  The present invention has been made in view of such a problem. Each contract is managed while managing the state from when the contract is established between the transaction person and the customer until the paper document is stored. The purpose is to provide a contract document management system that supports the verification of the existence and content of necessary documents.

  In order to solve the above problems, a contract document management system according to the present invention is a computer system connected to one or more first client computers and one or more second client computers. Data storage unit storing contract document rule data in which contract type information and contract document information are associated, contract management data for managing the status of each contract, and individual document rule data including verification rule information for each contract document A receiving unit that receives first image data and contract type information of a contract document from the one or more first client computers, and a contract from the data storage unit based on the received contract type information Document rule data is acquired, and based on the contract document information included in the acquired contract document rule data. And acquiring the individual document rule data from the data storage unit, and corresponding to the first image data based on the verification rule information included in the acquired individual document rule data and the received first image data A control unit configured to determine whether the contract document to be entered is correct and to update the contract management data stored in the data storage unit to a value indicating that the contract document has been verified; and A transmission section configured to transmit a cover page output message to one or a plurality of first client computers, and the reception section receives a cover page from the one or more second client computers. The controller is further configured to receive second image data, and the controller is configured to receive a trigger stored in the data storage unit based on the received second image data. Management data, characterized in that it is further configured to update the value indicating that the cover sheet has arrived.

  The contract document management system according to the present invention manages the status of each document from when the contract is established until the paper document is sent and stored, so that important paper documents such as contract documents are properly stored and managed. be able to. In addition, since it assists in verifying the presence / absence / content of necessary documents according to each contract, work efficiency can be improved and human errors can be largely prevented from occurring.

It is a figure which shows the example of the whole structure of the contract document management system based on one Embodiment of this invention. It is a figure which shows the example of a detailed structure of the contract document management system based on one Embodiment of this invention. It is a flowchart which shows the example of the document verification process which the contract document management system based on one Embodiment of this invention performs. It is a figure which shows the example of the contract information input interface based on one Embodiment of this invention. It is a figure which shows the example of a contract document rule data table based on one Embodiment of this invention. It is a figure which shows the example of the contract management data table based on one Embodiment of this invention. It is a figure which shows the example of the individual document rule data table based on one Embodiment of this invention. It is a flowchart which shows the example of the document verification execution interface based on one Embodiment of this invention. It is a flowchart which shows the example of the cover sheet output and contract document dispatch management process which the contract document management system based on one Embodiment of this invention performs. It is a figure which shows the example of a cover sheet output selection interface based on one Embodiment of this invention.

<System configuration>
With reference to FIG. 1, the example of the whole structure of the contract document management system based on one Embodiment of this invention is demonstrated.

  The contract document management system according to the present embodiment includes a contract document management server 1, a document verification terminal 2, and a document storage management terminal 3. The contract document management server 1 is connected to the document verification terminal 2 and the document storage management terminal 3 via a network 4 including a dedicated line or a public line such as the Internet.

  The contract document management server 1 is installed in a business provider (hereinafter referred to as “business operator”) that provides a service related to the contract document management system according to the present embodiment (hereinafter referred to as “contract document management service”). The contract document management server 1 executes contract document verification processing based on an input request from the document verification terminal 2. The contract document management server 1 also manages document storage management. Based on an input request from the terminal 3, the database information related to the contract document is updated to manage the storage state of the document.The contract document management server 1 is a single computing device or a plurality of computing devices. It may be implemented on a device.

  The document verification terminal 2 is one or a plurality of client computer terminals that are installed in a business office that verifies contract documents of a business operator, and for a verification person to verify the contract documents. In the present embodiment, the establishment where the document verification terminal 2 is installed and verifies the contract document is referred to as a “verification base”. The document verification terminal 2 displays an input interface provided by the contract document management system. On the input interface, the verification person inputs necessary information and verifies the contract document. Note that the verification base may exist across a plurality of business offices, and in this case, a plurality of document verification terminals 2 exist over a plurality of verification bases.

  The document storage management terminal 3 is installed in the business office that stores the paper documents of the contract documents of the business operators, and the storage manager updates the database information related to the contract documents to be stored and manages the storage status of the documents. One or more client computer terminals. In the present embodiment, a business establishment where the document storage management terminal 3 is installed and stores paper documents of contract documents is referred to as “storage base”. The document storage management terminal 3 displays an input interface provided by the contract document management system. On the input interface, the storage staff inputs necessary information and manages the storage state of the contract document. Note that the storage base may exist across a plurality of offices, and in this case, a plurality of document storage management terminals 3 exist over a plurality of storage bases.

  The input interface may be installed on the document verification terminal 2 and the document storage management terminal 3 or may be a WEB screen transmitted from the contract document management server 1. The document verification terminal 2 and the document storage management terminal 3 may be information communication terminal devices such as a personal computer, a workstation, and a PDA having a communication function. A computing device and an information communication terminal device are a computing device including a central processing unit (CPU), a memory, a storage device, and the like, and are integrated by a CPU processing a computer program stored in the memory or the storage device. The functions according to the present invention can be executed and the functions can be realized. Note that the above-described system configuration is for illustration, and does not limit the system configuration capable of executing the present invention.

  Next, an example of a detailed configuration of the contract document management system according to an embodiment of the present invention will be described with reference to the block diagram of FIG. The contract document management server 1 includes a communication unit 11, a control unit 12, a main storage unit 13, and an auxiliary storage unit 14, and these elements are connected via a system bus.

  The communication unit 11 is a network interface that transmits and receives control information and data between the document verification terminal 2 and the document storage management terminal 3.

  The control unit 12 is also called a central processing unit (CPU), and controls each of the above components and calculates data. In addition, the control unit 201 reads various programs stored in the auxiliary storage unit 14 for executing various processes according to the present embodiment to the main storage unit 13 and executes them.

  The main storage unit 13, also called a main memory, stores input data received by the contract document management server 1, computer-executable instructions, data after arithmetic processing by the instructions, and the like.

  The auxiliary storage unit 14 is a storage device represented by a hard disk (HDD) or the like, and stores a program (not shown) for causing the control unit 12 to execute various processes according to the present embodiment. Further, the contract document management server 1 is implemented with a DBMS (Database Management System), and stores a database table 14a storing data such as a contract management data table.

  The document verification terminal 2 includes a communication unit 21, a control unit 22, a main storage unit 23, an auxiliary storage unit 24, a display unit 25, and an I / O interface 26, and these components are connected via a system bus. Has been. The document verification terminal 2 includes a scanner 27 and a printer 28 connected via an I / O interface 26. The document storage management terminal 3 has the same configuration as the document verification terminal 2 and includes a communication unit 31, a control unit 32, a main storage unit 33, an auxiliary storage unit 34, a display unit 35, an I / O interface 36, and a scanner 37. ing.

  Each of the communication units 21 and 31 transmits and receives data to and from the contract document management server 1 connected via the network 4.

  Each of the control units 22 and 22 is a central processing unit, and controls each of the above components and calculates data.

  The main storage units 23 and 33 are also called main memories, and store input data, data recognized by the scanners 27 and 37, and the like.

  Each of the auxiliary storage units 24 and 34 is a storage device such as a hard disk, and stores a program for displaying each input interface and the like.

  The display units 25 and 35 display input interfaces on the displays of the document verification terminal 2 and the document storage management terminal 3, respectively.

  Each of the I / O interfaces 26 and 36 is an interface for connecting the scanners 27 and 37 by a method such as USB, and transmits and receives data to and from the scanners 27 and 37.

  Each of the scanners 27 and 37 is a reading device that reads a paper document (contract document) existing at the verification base, an image of the paper document sent to the storage base, a two-dimensional barcode, and the like. The scanners 27 and 37 transmit images read from the paper document to the control units 22 and 23, respectively.

  The printer 28 is a printing device that outputs a cover sheet sent from the verification base to the storage base. The printer 28 prints out a cover sheet based on the data received from the control unit 22.

<Document verification processing>
Next, a document verification process executed by the contract document management system according to an embodiment of the present invention will be described with reference to the flowchart of FIG. In this embodiment, when a financial institution (operator) concludes a loan contract with a customer, an example of verifying a contract document that has been filled in and stamped by a customer will be described. The contract document management system is not limited to the example of the loan contract.

  First, a business person in charge of a business deals with a loan contract with a customer, and takes the contract document with the seal etc. back to the verification base. The contract document will be verified at the verification site. Contract documents (including incidental documents) differ depending on the products, options, and guarantor attributes (hereinafter referred to as “contract type”) in the loan contract.

  In step S301, all the contract documents including the incidental documents are read by the scanner 27 at the verification base. Here, the contract document has a code (hereinafter, “document identification reading code”) (for example, a one-dimensional barcode, a two-dimensional barcode, etc.) for identifying a document type (hereinafter, “document type”). Includes what is printed. The contract document is read not only by the document identification reading code but also by the whole including the necessary information entry field and the seal field of each contract document. The read contract document rule data is transmitted to the control unit 22.

  Next, contract information is input by the verification person from the contract information input interface displayed on the display unit 25 of the document verification terminal 2 (step S302). The contract information is information indicating the contract type of the contract document to be verified. An example of the contract information input interface 400 will be described with reference to FIG.

  As shown in FIG. 4, the contract information input interface 400 includes a product selection field 401, an option selection field 402, a credit transaction presence / absence selection field 403, a debtor attribute selection field 404, a guarantor (individual) attribute selection field 405, a guarantor. (Corporate / conflict of interest) attribute selection field 406 and guarantee form selection field 407 are included. The loan contract in the present embodiment includes each item selected in these selection fields, and by selecting each of these selection fields, the contract type is determined and the necessary contract documents are determined accordingly. The items in each selection column shown in FIG. 4 are merely examples, and are not limited to these items.

  When the contract information is input, the contract document rule data (including image data of each contract document, document identification reading code, etc.) read in step S301 and the contract information (contract information input interface 400) input in step S302. The contract data including the data indicating the selection value of each selection field selected in (1) is transmitted to the contract document management server 1 by the communication unit 21 (step S303).

  When the communication unit 11 of the contract document management server 1 receives the contract data transmitted in step S303, the control unit 12 reads the target record from the contract document rule data table based on the contract information included in the received contract data. Is acquired (step S304). An example of the contract document rule data table 500 will be described with reference to FIG.

  As shown in FIG. 5, the contract document rule data table 500 includes a product code, an option, a code, a credit transaction presence / absence, a debtor attribute, a guarantor (individual) attribute, a guarantor (corporate / conflict of interest) attribute, and a guarantee form ( These items indicate items selected in each selection column of the contract information input interface 400, and the contract type is specified by a combination of these items), and documents 1 to X (X is an arbitrary number of 1 or more) Integer value). Each of the documents 1 to X is set with a document code for identifying documents corresponding to all contract documents required in the target contract type. That is, the contract document rule data table 500 includes the contract type and the contract code. It is a data table in which all corresponding necessary contract documents are stored in association with each other.

  Returning to the explanation of FIG. 3, in step S305, the control unit 12 adds a record to the contract management data table. An example of the contract management data table 600 will be described with reference to FIG.

  As shown in FIG. 6, the contract management data table 600 includes a management code, a customer code, a document 1 to a document X (X is an arbitrary integer value of 1 or more), and a status. As the management code, a numerical value uniquely assigned when a record is added to the contract management data table 600 in step S305 is set. That is, the identification number for managing the contract concluded in this embodiment and the contract document necessary for it is set.

  For the documents 1 to X, the values of the documents 1 to X included in the contract document rule data record acquired in step S305 are set. That is, by managing these values in the contract management data table 600, necessary contract documents can be managed for each contract concluded.

  The status is set to a value for managing each process until the contract document is stored in the verification base, sent to the storage base, and stored in the storage base. For example, in this step, “0: Verification base storage” is set. Is set. That is, by managing these values in the contract management data table 600, it is possible to manage the state of the paper documents of the contract documents necessary for each concluded contract.

  Returning to the description of FIG. 3, in step S306, the control unit 12 acquires all the records from the individual document rule data table based on the documents 1 to X included in the contract management data record acquired in step S305. (Step S306). That is, 1 to X individual document rule data records corresponding to the corresponding contract management data record are acquired. An example of the individual document rule data table 700 will be described with reference to FIG.

  As shown in FIG. 7, the individual document rule data table 700 includes document codes, item 1 (item name, verification format, range, automatic) to item Y (Y is an arbitrary integer value of 1 or more) (item name, verification). Format, range, auto-validation flag). In the document code, a number for identifying all contract documents is set. Items 1 to Y correspond to the entry items (store number, seal, etc.) of the corresponding contract document. The verification format verifies the format of the entry, such as the type for verifying the item entered in the corresponding item, for example, whether the entered store number matches the store number for the corresponding customer (for example, “ 1: Format ”is set), or an item to be verified (for example,“ 2: Content ”is set), such as whether the content of the contract document is correct. The entry position indicates the position of the corresponding item in the corresponding contract document in the XY coordinate format. The automatic verification flag indicates whether or not the entry of the corresponding item is automatically checked (for example, whether the entry is character-recognized and the correct item is entered). Is set.

  In this way, by managing the individual document rule data table 700, it is possible to manage the verification items and the verification format of each document.

  Returning to the description of FIG. 3, in step S307, the control unit 12 recognizes the document identification reading code of the contract document included in the contract data transmitted in step S303, and identifies the corresponding document. Here, some contract documents do not have a document identification reading code printed. In such a document, the entire document data of the contract document included in the contract data is read, and the corresponding document is read. Identify (for example, by recognizing the document name printed on the contract document).

  Next, the control unit 12 selects a record corresponding to the document identified in step S307 from the individual document rule data records acquired in step S306 (step S308).

  Next, the control unit 12 applies the contract transmitted in step S303 to all the items 1 to X included in the individual document rule data record selected in step S308 based on the XY coordinates indicated by the entry position. The characters of the image data are recognized from the image data of each contract document included in the data (step S309).

  Next, based on the character recognized in step S309, the control unit 12 for the item in which “1: with automatic check” is set in the automatic verification flag included in the individual document rule data record selected in step S308. , Determine whether the relevant items are correctly entered. Further, the control unit 12 determines whether the corresponding item is not filled in based on the character recognized in step S309 (that is, the item in which character recognition could not be performed in step S309) (step S310).

  The processes in steps S307 to S310 are executed a number of times corresponding to the number of individual document rule data records acquired in step S306. That is, the determination process in steps S307 to S310 is executed for all contract documents necessary for the corresponding contract type.

  Next, the communication unit 11 performs document verification data including the contract management data record acquired in step S305, all the individual document rule data records acquired in step S306, and data indicating the determination result for each item in step S310. Is transmitted to the document verification terminal 2 (step S311).

  When the communication unit 21 of the document verification terminal 2 receives the document verification data transmitted in step S311, the display unit 25 displays the document verification execution interface 800 based on the received document verification data (step S312). An example of the document verification execution interface 800 will be described with reference to FIG.

  As shown in FIG. 8, the document verification execution interface 800 includes a verification document list display screen 801, a selection verification document check screen 802, and a selection verification document image screen 803. On the verification document list display screen 801, image data of the document (read in step S301) corresponding to the individual document rule data record included in the received document verification data is displayed in an icon format. That is, all image data of contract documents required for the corresponding contract type is displayed. Here, the contract document that has not been read in step S301 does not have image data corresponding to the individual document rule data record. As described above, the verification document list display screen 801 can display the fact when the contract document is insufficient, and can indicate to the verification person that the contract document is incomplete.

  When a document to be verified is selected on the verification document list display screen 801 (for example, by clicking the corresponding icon), each verification target item of the selected contract document is displayed on the selection verification document check screen 802. On the selected verification document check screen 802, based on the individual document rule data record included in the received document verification data, the item name of each verification target item, the verification format, and the determination result in step S310 are displayed (automatic verification is performed). If there is an item that is not filled in, the verification result is displayed. The selected verification document image screen 803 displays a read image of the selected verification document.

  The person to be verified verifies each verification item on the selected verification document check screen 802, and presses an “OK” button when the entered contents are correct. In this way, all items for all contract documents are verified (step S313), and if the “OK” button is pressed for all items, a verification result message indicating that the contract documents are not incomplete. Is transmitted to the contract document management server 1 by the communication unit 21 (step S314). The verification result message includes a management code corresponding to the contract management data record included in the document verification data received in step S312.

  When the communication unit 11 of the contract document management server 1 receives the verification result message transmitted in step S314, the control unit 12 selects a corresponding item in the contract management data table 600 based on the management code included in the received verification result message. For the record, the status is updated to “1: verification completed” (step S315).

  As described above, the contract document management system according to the present embodiment determines whether all contract documents required for each contract type are available, and further, there is an omission in each item of each contract document. This is automatically determined and the verification person's verification is supported, so the verification work of the verification person can be greatly reduced.

<Outlet cover output / contract document delivery management>
Next, a cover sheet output / contract document delivery management process executed by the contract document management system according to an embodiment of the present invention will be described with reference to the flowchart of FIG.

  First, in the document verification terminal 2, when the display unit 25 displays a cover sheet output screen (not shown), the control unit 12 of the contract document management server 1 changes the status from the contract management data table 600 to “1: verification complete”. Are acquired and transmitted to the document verification terminal 2 (step S901).

  When the communication unit 21 of the document verification terminal 2 receives the contract management data record transmitted in step S901, the display unit 25 displays the cover sheet output selection interface 1000. As shown in FIG. 10, the cover page output selection interface 1000 is an input interface that displays a list of contracts that have been verified and for which a cover sheet has not yet been output. When a contractor who selects a cover sheet output target is selected by a verifier and a cover sheet output execution button (not shown) is pressed, the communication unit 21 transmits a contract code corresponding to the contract to the contract document management server 1. (Step S902).

  When the communication unit of the contract document management server 1 receives the contract code transmitted in step S902, the control unit 12 sets the status of the corresponding record in the contract management data table 600 to “2: based on the received contract code. It is updated to “send storage location” (that is, the contract document is sent from the verification location) (step S903).

  Next, the communication unit of the contract document management server 1 transmits a cover sheet output message indicating that a cover sheet is output on the document verification terminal 2 to the document verification terminal 2 (step S904).

  When the communication unit 21 of the document verification terminal 2 receives the cover sheet output message transmitted in step S904, the control unit 12 generates cover sheet data based on the contract management data record received in step S903, and the printer 28 Send cover page data to. The printer 28 that has received the cover sheet data prints out the cover sheet (step S905). The cover sheet data is a document on which the name of the contract document of the contract is printed, and is generated based on the received contract management data record. On the output cover sheet, a code for identifying the corresponding contract (hereinafter referred to as “contract identification reading code”) (for example, a one-dimensional barcode, a two-dimensional barcode, etc.) is printed.

  When the cover letter is printed out, it is mailed to the storage base together with the paper document of the contract document for the contract. When the cover sheet is mailed to the storage base, the contract identification reading code of the cover sheet is read by the scanner 37 of the document storage management terminal 3 (S906).

  Next, the communication unit 31 of the document storage management terminal 3 transmits the contract identification reading code read in step S906 to the contract document management server 1 (S907). The communication unit 11 of the contract document management server 1 recognizes the contract identification reading code transmitted in step S907 (the management code of the corresponding contract can be recognized from the contract identification reading code), and based on the recognized management code. Then, the state of the corresponding record in the contract management data table 600 is updated to “3: arrival at storage base” (step S908).

  As explained above, each contract manages the status from the conclusion of the contract between the transaction representative and the customer until the documents necessary for the conclusion of the contract arrive at the storage base. Can always figure out where and where is stored.

  As described above, the description of the contract document management system according to the present invention has been described in detail, but the specific data structure such as the contract document rule data table 500 described in the embodiment is merely an example, and the patent Changes may be made without departing from the claimed matters. Moreover, the order of each step in the flowchart demonstrated in FIG. 3 and FIG. 9 may be changed in the range which does not deviate from the matter claimed.

DESCRIPTION OF SYMBOLS 1 Contract document management server 2 Document verification terminal 3 Document storage management terminal 4 Network 400 Contract information input interface 401 Product selection column 402 Option selection column 403 Credit transaction existence selection column 404 Debtor attribute selection column 405 Guarantor (individual) attribute selection column 406 Guarantor (Corporate / Conflict of Interest) Attribute Selection Column 407 Guarantee Form Selection Column 500 Contract Document Rule Data Table 600 Contract Management Data Table 700 Individual Document Rule Data Table 800 Document Verification Execution Interface 801 Verification Document List Display Screen Screen 803 Selection verification document image screen 1000 Cover page output selection interface

Claims (6)

A computer system connected to one or more first client computers and one or more second client computers,
Data storage unit storing contract document rule data associated with contract type information and contract document rule information, contract management data for managing the status of each contract, and individual document rule data including verification rule information for each contract document When,
A receiving unit for receiving first image data and contract type information of a contract document from the one or more first client computers;
Based on the received contract type information, obtain contract document rule data from the data storage unit,
Based on the contract document rule information included in the acquired contract document rule data, obtain individual document rule data from the data storage unit,
Based on the verification rule information included in the acquired individual document rule data and the received first image data, it is determined whether or not the contract document corresponding to the first image data is entered, and the data storage unit A control unit configured to update the contract management data stored in the table to a value indicating that the contract document has been verified;
A transmission unit configured to transmit a cover sheet output message to the one or more first client computers, and
The receiving unit is further configured to receive second image data of a cover page from the one or more second client computers;
The control unit is further configured to update the contract management data stored in the data storage unit to a value indicating that a cover page has arrived, based on the received second image data. A computer system characterized by the above.   The said control part is further comprised so that the contract management data memorize | stored in the said data memory | storage part may be updated to the value which shows that the said contract document is sent. Computer system. The verification rule information includes a verification rule for each entry item of the contract document and a coordinate position of the entry item in the contract document.
Recognizing the entry from the first image data based on the coordinate position;
The computer system according to claim 1, further comprising: determining whether or not the recognized entry item is correct based on the verification rule. A method performed by one or more first client computers and a server computer connected to one or more second client computers comprising:
The server computer includes contract document rule data associated with contract type information and contract document rule information, contract management data for managing the status of each contract, and individual document rule data including verification rule information for each contract document. A stored data storage unit,
The method
Receiving first image data and contract type information of a contract document from the one or more first client computers;
Obtaining contract document rule data from the data storage unit based on the received contract type information;
Acquiring individual document rule data from the data storage unit based on the contract document rule information included in the acquired contract document rule data;
Determining whether the contract document corresponding to the first image data is correct based on the verification rule information included in the acquired individual document rule data and the received first image data;
Updating the contract management data stored in the data storage unit to a value indicating that the contract document has been verified;
Sending a cover page output message to the one or more first client computers;
Receiving second image data of a cover page from the one or more second client computers;
Updating the contract management data stored in the data storage unit to a value indicating that a cover sheet has arrived, based on the received second image data.   A program for causing a computer to execute the method according to claim 4.   A computer-readable storage medium storing the program according to claim 5.