JP6251320B2 - Apparatus, method, and computer program for executing processing relating to a business contract - Google Patents

Description

The present invention relates to an apparatus, a method , and a computer program for executing processing related to a transaction contract.

  Conventionally, in various contract procedures such as opening an account at a financial institution's window, cash withdrawal, address change, etc., the customer signs and stamps the documents according to the various procedures, fills in the necessary items and applies to the window Is doing. For example, in cash withdrawals, the person in charge of the window checks the form of the application document and confirms the identity of the application. After checking the seal by eye inspection, if there is no problem, the person in charge performs a transaction based on the application document.

Japanese Patent No. 4307606 Japanese Patent No. 4603675

  However, in such a conventional service form, the customer needs to bring a seal and a passbook, and the conventional service is not necessarily safe considering the risk of loss or theft. In addition, the customer needs to select and describe documents according to various procedures by himself / herself, and there is a problem that an incorrect document is selected or a description defect occurs. Furthermore, since it is necessary to store the signature / imprint of the customer, it is necessary to use a paper-based application document. In addition, since the application documents are written by the customers themselves, the person in charge of the window does not actually confirm the contents of the application, but only performs a formal confirmation. Therefore, for example, even if the withdrawal amount of the application document is written incorrectly, the customer may not notice until after the transaction is executed, and the procedure has been redone.

  On the other hand, a law concerning electronic signatures and authentication business (electronic signature law) stipulates that electronic signatures have the same legal effect as handwritten signatures and seals. Therefore, there is a need for a new transaction contract method and system using an electronic signature that can solve the above problems.

In order to achieve such an object, the present invention is a server computer that executes a process related to a transaction contract with a customer at a financial institution, and the server computer includes:
Receiving application content data, which is data relating to the application content of the transaction contract, from the first computer;
Receiving authentication data of the customer from the first computer or the second computer;
If there is no problem in the verification result of the authentication data and pre-registered master data, based on the application content data and the authentication data, create transaction contract data that is data related to the execution content of the transaction contract,
Based on the transaction contract data, the processing related to the transaction contract is executed.

  In the invention described in the preceding paragraph, the authentication data includes at least one of handwritten signature data, seal imprint data, and biometric authentication data by the customer.

  Furthermore, the server computer described in the preceding two paragraphs is further configured to collate the authentication data with the master data.

  The server computer described in the preceding three paragraphs is further configured to receive the master data from the first computer, the second computer, or a third computer.

  Further, the server computer described in the preceding four paragraphs is further configured to create a contract file for the purpose of saving a contract as a real image based on the authentication data and the transaction contract data. Features.

  Furthermore, the server computer described in the preceding paragraph is further configured to give a time stamp to the master data and / or the contract file.

  Further, the server computer described in the preceding six paragraphs creates customer copy data, which is data related to the customer copy of the transaction contract, based on the transaction contract data when the transaction contract is executed normally. It is further configured.

Further, the present invention is a method for executing a process related to a transaction contract with a customer at a financial institution, wherein the method includes:
Receiving, from the first computer, application content data that is data relating to the application content of the transaction contract;
Receiving authentication data of the customer from the first computer or the second computer;
When there is no problem in the verification result between the authentication data and the master data registered in advance, the step of creating transaction contract data, which is data related to the execution content of the transaction contract, based on the application content data and the authentication data When,
And a step of executing a process related to the transaction contract based on the transaction contract data.

Furthermore, the present invention is a computer program that causes a server computer to execute a method for executing a process related to a business contract with a customer at a financial institution, and the computer program is executed by the server computer. In the server computer,
Receiving application content data, which is data relating to the application content of the transaction contract, from the first computer;
Receiving authentication data of the customer from the first computer or the second computer;
If there is no problem in the verification result between the authentication data and the pre-registered master data, based on the application content data and the authentication data, the transaction contract data that is data related to the execution content of the transaction contract is created,
A process related to the transaction contract is executed based on the transaction contract data.

  As described above, the present invention provides a new transaction contract method and system using an electronic signature. As a result, in various contract procedures at financial institutions, the customer can make an application without bringing a seal or passbook at the window. In addition, paper-based application documents can be abolished, reducing the burden of filling in customers and writing deficiencies. Further, the customer and the person in charge of the window can confirm the application contents together, and the efficiency of the procedure can be improved.

It is a figure which shows the system configuration | structure which concerns on one Embodiment of this invention. It is a flowchart which shows the transaction contract process which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the application content data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the transaction contract data storage part which concerns on one Embodiment of this invention. It is a figure which shows the data stored in the customer copy data storage part which concerns on one Embodiment of this invention. It is an image of the contract document file which concerns on one Embodiment of this invention.

  An outline of a transaction contract management 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, a transaction contract management server 101 installed in a data center or the like is connected to one or a plurality of window terminals 103a to 103n (hereinafter collectively referred to as window windows) via a network 102 (for example, an intranet of a financial institution). 103 ”). In FIG. 1, the transaction contract management server 101 is shown as a single server, but it can also be configured as a distributed system with a plurality of servers.

  The window terminal 103 is a terminal used by a window person in charge at a financial institution. The person in charge of the counter conducts a hearing regarding the transaction from the customer and inputs the application contents using the counter terminal 103. The application contents during or after the input are displayed on the display 104 connected to the network 102 and can be confirmed by the customer. In addition, the customer can input a handwritten signature used as an electronic signature using the signature input terminal 105 connected to the window terminal 103. Further, the customer can confirm and input the application contents by using a tablet PC (not shown) wirelessly connected to the network 102 instead of the display 104 or in addition to the display 104.

  The sign input terminal 105 includes a touch panel unit and can input a handwritten signature using an attached stylus pen or the like. Further, the sign input terminal 105 can also include a stamp photographing unit that can photograph the stamp part of the seal and convert the photographed impression into image data (electronic data).

  The handwritten signature data input via the signature input terminal 105 is transmitted to the transaction contract management server 101 by the window terminal 103, and the master data registered in advance (hereinafter, the master data of the handwritten signature data is referred to as “master signature data”). ). On the other hand, for the seal imprint data input via the sign input terminal 105, the contact terminal 103 requests the transaction contract management server 101 for corresponding master data (hereinafter, master data of the seal imprint data is referred to as “master seal imprint data”). Then, the master imprint data transmitted is displayed on the window at the window terminal 103, so that the window person in charge collates (checks) the stamp data input through the sign input terminal 105. However, the transaction contract management server 101 or the window terminal 103 can also calculate the coincidence rate by image matching between the input seal data and the master seal data, and automatically collate them. Note that registration of the master signature data and the master seal stamp data can also be performed by the signature input terminal 105 without using a conventional application form (paper base) when a customer account is opened. Further, the master seal data can be registered by photographing the seal stamped on the paper without using the sign input terminal 105.

  The verification result of the handwritten signature data is transmitted from the transaction contract management server 101 to the window terminal 103 and displayed on the window terminal 103. The verification result of the seal stamp data is input by the counter person in charge through the counter terminal 103. If there is no problem in the verification result, the person in charge of the window uses the window terminal 103 to transmit a transaction contract execution instruction to the transaction contract management server 101. When receiving the execution instruction, the transaction contract management server 101 creates transaction contract data and executes transaction contract processing. When the transaction contract is executed normally, the transaction contract management server 101 can create customer copy data and print the customer copy (paper base) via a network printer (not shown). Additionally or alternatively, the customer copy can be transmitted and stored on a terminal owned by the customer.

  Next, the configuration of the transaction contract management server 101 will be described in detail. In FIG. 1, only a necessary configuration is shown assuming a single server computer system.

  The transaction contract management server 101 includes a CPU 110, a RAM 111, an input device 112, an output device 113, a communication control device 114, and a storage device 116, each connected via a system bus 115. The storage device 116 is composed of a nonvolatile storage medium (ROM, HDD, etc.), a program storage area that stores a software program for performing each function of the transaction contract management system, and data that stores data handled by the software program Storage area. Each means in the program storage area described below is actually an independent software program, its routine or component, and is stored in the storage device 116. Each means is called from the storage device 116 by the CPU 110 at the time of execution and is expanded in the work area of the RAM 111, so that each function can be exhibited while appropriately accessing a database or the like.

  The software programs stored in the program storage area in the storage device 116 list only those related to the present invention. The application reception means 120, the authentication means 121, the time stamp assignment means 122, the transaction contract execution means 123, and the customer A copy issuing means 124 is provided. These means are executed by the CPU 110.

  The application receiving unit 120 receives application content data from the window terminal 103 and stores it in the application content data storage unit 130.

  The authentication unit 121 receives handwritten signature data from the signature input terminal 105 via the window terminal 103 and verifies it with master signature data registered in advance. Further, the authentication unit 121 transmits the verification result to the window terminal 103. Further, the authentication unit 121 responds to a request from the window terminal 103, acquires master seal data registered in advance, and transmits it to the window terminal 103. The master imprint data is collated (checked) with the imprint data by the person in charge of the window.

  The time stamp assigning means 122 assigns a time stamp at the time of registration to handwritten signature data, seal stamp data, and a contract file in order to prevent data alteration.

  The transaction contract execution means 123 creates transaction contract data and stores it in the transaction contract data storage unit 131. Further, the transaction contract execution means 123 executes transaction contract processing based on the created transaction contract data.

  The customer copy issuing means 124 creates customer copy data and stores it in the customer copy data storage unit 132 when the transaction contract is executed normally. Further, the customer copy issuing means 124 transmits the created customer copy data to a network printer or other terminal.

  Next, the data storage area in the storage device 116 includes an application content data storage unit 130, a transaction contract data storage unit 131, and a customer copy data storage unit 132, if only those related to the present invention are listed. Both are fixed storage areas secured in the storage device 116.

  The application content data storage unit 130 stores data relating to the application content of the transaction contract. The data is interviewed by the person in charge of the customer who applies for the transaction contract, and is registered through the window terminal 103 by the person in charge of the window. Alternatively, the customer can register using another terminal (for example, a tablet PC for customer input). FIG. 3 is a diagram illustrating data stored in the application content data storage unit 130 according to an embodiment of the present invention. The application content data in FIG. 3 includes “application date and time” indicating the date and time when the transaction was applied (strictly the date and time when this data was registered by the contact person), “customer name” indicating the name of the customer, “Customer Kana” that indicates the reading of the name, “Customer Account Branch Code” that uniquely identifies the branch of the customer account, “Customer Account Number” that uniquely identifies the customer account, and “ “Customer Account Item”, “Transaction Type” that uniquely identifies the type of transaction, “Transaction Account Branch Code” that uniquely identifies the branch of the account that is the object of the transaction (hereinafter referred to as “Transaction Target Account”), and Account for Transaction “Transaction account number” that uniquely indicates the transaction, “transaction account item” that uniquely indicates the item of the transaction target account, and “transaction amount” that indicates the amount of the transaction. In the “customer account subject” and “transaction account subject”, codes indicating the type of deposit in each account, for example, 1: normal deposit, 2: current account, 3: savings deposit,... Are stored. “Transaction type” stores a code indicating the type of transaction content, for example, 1: cash withdrawal, 2: deposit, 3: transfer,. This data has a common format for the transaction type, and the data item (data column) related to the transaction target account stores the account data of the transfer destination when the transaction content is transfer, and allows for cash withdrawal and deposit In this case, the account data of the customer is stored. That is, when the transaction content is cash withdrawal or deposit, the data item related to the customer account and the data item related to the transaction target account have the same content. Therefore, this data can be configured as a separate format for each transaction type. For example, when the transaction content is a cash withdrawal or deposit, the data item related to the customer account is sufficient, so that the data item related to the transaction target account may not be provided. As described above, the data items shown in FIG. 3 are merely examples, and do not prevent the addition or deletion of the data items (the same applies to each data shown below).

  The transaction contract data storage unit 131 stores data relating to transaction details agreed upon by the customer. FIG. 4 is a diagram showing data stored in the transaction contract data storage unit 131 according to an embodiment of the present invention. The transaction contract data in FIG. 4 includes a “transaction number” for uniquely identifying a transaction, a “customer name” indicating the name of a customer who makes a transaction contract, a “customer name” indicating a kana reading of the customer name, and a customer used. “Customer account branch code” that uniquely identifies the branch of the account, “Customer account number” that uniquely identifies the customer account, “Customer account item” that uniquely identifies the account of the customer account, and the transaction type that is uniquely identified “Transaction type”, “Transaction account branch code” that uniquely identifies the branch of the transaction target account, “Transaction account number” that uniquely identifies the transaction target account, “Transaction account item” that uniquely identifies the transaction account item, Transaction "Transaction amount" indicating the amount of the transaction, "Contract document file" for storing the contract file related to the transaction contract, or indicating the storage location of the file, the date and time when this data was registered (that is, the transaction content has been agreed Indicating the date and time) "registration date and time", and uniquely indicates the responsible person that was in charge of the trading agreement stores "the responsible code". The “transaction number” is a sequence number, and is numbered and stored every time a record of this data is created. The “customer account item”, “transaction type”, and “transaction account item” are the same as the data items of the same name in the application content data (FIG. 3).

  Further, the “contract document file” in the transaction contract data (FIG. 4) can store the contract file itself (for example, a PDF file), or can store address data of the storage destination. Here, FIG. 6 is an image of a contract document file (for example, PDF file) according to an embodiment of the present invention. As described above, the contract document file is stored as an actual image of the contract document (paper base) by embedding the handwritten signature data and / or seal imprint data input via the signature input terminal 105. In order to prevent data alteration, the contract document file can be hash-converted and then stored by adding an electronic signature and a time stamp.

  The customer copy data storage unit 132 stores data related to a customer copy issued when a transaction contract is made. FIG. 5 is a diagram illustrating data stored in the customer copy data storage unit 132 according to an embodiment of the present invention. The customer copy data in FIG. 5 includes “customer name” indicating the name of the customer who made the transaction contract, “customer name” indicating the customer name reading, and “customer account branch code” uniquely indicating the branch of the customer account. ”,“ Customer account branch name ”indicating the branch name of the customer account used,“ Customer account number ”uniquely indicating the customer account used,“ Customer account item ”indicating the item of the customer account,“ Transaction details ”indicating the transaction details ”,“ Transaction account branch code ”that uniquely identifies the branch of the account to be traded,“ transaction account branch name ”that represents the branch name of the account to be traded,“ transaction account number ”that uniquely identifies the account to be traded, The “transaction account item” indicating the item, the “transaction amount” indicating the transaction amount, and the “procedure date” indicating the date when the transaction contract is made are stored. “Customer account branch name” and “Transaction account branch name” are obtained from account data (not shown) storing data related to the account, using “Customer account branch code” and “Transaction account branch code” as search keys, respectively. can do. In the same way, "Customer account item" and "Transaction account item" are obtained from the account data using the code that uniquely identifies the item ("Customer account item" and "Transaction account item" in the transaction contract data (Fig. 4)) as a search key. can do.

  Next, a transaction contract 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 FIGS. 3-5. In this process, a series of transaction contract processes from acceptance of application for various contract procedures such as cash withdrawal at a financial institution to execution of a contract are performed via a computer system.

  FIG. 2 is a flowchart showing a transaction contract process according to an embodiment of the present invention. This processing flow starts when the customer in charge presents a passbook or cash card at the window and the person in charge of the window interviews the customer after the identity verification is completed. Further, in the processing in this processing flow, as a general rule, a counter person in charge operates a Web site (or may be an intra site) provided by the transaction contract management server 101 via the counter terminal 103, and the counter terminal 103 It is assumed that the transaction is executed by the transaction contract management server 101 based on the execution instruction from.

  First, in step 201, the application receiving unit 120 receives application content data (FIG. 3) from the window terminal 103 or another terminal and stores it in the application content data storage unit 130. The application content data is data relating to the application content interviewed by the customer, through the window terminal 103 by the window manager or by another terminal (for example, a tablet PC for customer input) by the customer. Input and sent.

  After step 201, the authentication means 121 receives the authentication data of the customer that is input using the sign input terminal 105 via the window terminal 103 or another terminal (step 202). The authentication data includes at least one of handwritten signature data input by a customer, seal stamp data, and biometric authentication data such as fingerprints, veins, irises, and retinas.

  After step 202, the authentication unit 121 determines whether the received authentication data is seal impression data (step 203). If the authentication data is not imprint data, the process proceeds to the No route of step 203, and the authentication unit 121 collates the handwritten signature data with the master signature data registered in advance (step 204). The handwritten signature data is collated based on the trajectory drawn on the touch panel portion of the sign input terminal 105 by the stylus pen and its writing pressure, as in the prior art disclosed in Patent Literature 1 and Patent Literature 2. It is automatically determined whether the user is the customer. Although step 204 has been described on the assumption that the authentication data is handwritten signature data, step 204 is also executed when the authentication data is biometric authentication data. Master data of biometric authentication data is also acquired using a dedicated device and registered in advance in the transaction contract management server 101 (or can be registered in an IC cash card with a biometric authentication function).

  On the other hand, if the authentication data is imprint data, the process proceeds to a Yes route in step 203, and the contact person in charge verifies the imprint data. The collation of the seal stamp data is, for example, that the stamp person in charge compares the seal stamp data displayed on the counter terminal 103 with the master seal stamp data registered in advance, and determines whether or not they match. It is. On the other hand, the imprint data can be collated by calculating the matching rate between the input imprint data and the registered master imprint data by image matching processing by the authentication unit 121.

  Here, the master signature data of a handwritten signature and the master imprint data of a seal are registered in advance when the account is opened by the customer, for example, and stored in association with the account data in the transaction contract management server 101 or another database server. The Registration of each master data is performed using the signature input terminal 105 (or the signature imprinted on the paper can be photographed and registered without using the signature input terminal 105). It should be noted that in order to give an allowance to match rate determination, a plurality of inputs can be made and a plurality of master data can be stored. Thus, by comparing the authentication data with a plurality of master data at the time of verification, if the authentication data matches any master data, it can be determined that the verification is OK. Alternatively, a single master data can be created and stored in consideration of the allowable range from a plurality of master data. Note that the master data can improve the authentication accuracy by reflecting a change over time from the authentication data acquired for each authentication or storing the history. In addition, the master data is encrypted and hashed data for data leakage and alteration countermeasures, and can be stored by adding an electronic signature and a time stamp. The time stamp is generated, for example, by transmitting a hash value of master data to an external time stamp server (not shown), and the time stamp server combines time information with the hash value.

  After verification of handwritten signature data (step 204) and / or verification of seal impression data, the authentication unit 121 determines whether the verification result is OK or NG (step 205). The collation result is based on the result data in the case of automatic determination, and on the result data input and transmitted by the window terminal 103 in the case of an inspection by the person in charge of the window. If the verification result does not confirm that the authentication data belongs to the user (the verification result is NG), the process proceeds to No route in step 205 and the process ends. In this case, the authentication unit 121 notifies the window terminal 103 that the collation result is NG, and the authentication data is input again, so that the processing can be started again from step 202.

  On the other hand, when the verification result confirms that the authentication data is the original data (the verification result is OK), the process proceeds to the Yes route in Step 205, where the transaction contract execution means 123 receives the received application content data (FIG. 3) and Based on the authentication data and the like, transaction contract data (FIG. 4) is created and stored in the transaction contract data storage unit 131 (step 206). At this time, a contract document file (for example, a PDF file as shown in FIG. 6) in which handwritten signature data and / or seal imprint data is embedded is created together with the created transaction contract data.

  After step 206, the transaction contract execution means 123 executes a transaction contract process based on the created transaction contract data (step 207). Note that step 207 can be executed after waiting for an execution instruction from the window terminal 103 for verification (final confirmation) by the window staff.

  After step 207, the time stamp assigning means 122 acquires a time stamp and assigns it to the contract file in order to prevent modification of the created contract document file (step 208). More specifically, for example, the time stamp assigning means 122 performs hash conversion on the contract document file and then transmits it to an external time stamp server. Thereafter, the time stamp server generates a time stamp by combining time information with the hash value of the received contract document file, and transmits the generated time stamp to the time stamp assigning means 122 (transaction contract management server 101). . The time stamp assigning unit 122 assigns the received time stamp to the contract document file, and stores the contract document file with the time stamp in the transaction contract management server 101 or another database server.

  After step 208, the customer copy issuing means 124 creates customer copy data (FIG. 5) based on the transaction contract data and stores it in the customer copy data storage unit 132 (step 209). Further, the customer copy issuing means 124 can print the customer's copy (paper basis) by transmitting the created customer copy data to the network printer. Furthermore, the customer copy issuing means 124 can transmit and store the customer copy data to a terminal owned by the customer. Alternatively, the customer copy data stored in the customer copy data storage unit 132 can be referred to when the user logs in to the Web site provided by the transaction contract management server 101 via the user terminal or the like. . After step 209, the process ends. Note that steps 201 to 209 are merely an embodiment, and the order of steps is not limited to the flow of FIG. 2 (for example, the order of steps 201 and 202 may be reversed, and both steps are received as one reception). It can also be executed simultaneously as a process). Further, not all of the steps are indispensable steps (for example, the creation and output processing of the customer copy data in step 209 may be executed as necessary).

  As described above, the present invention provides a new transaction contract method and system using an electronic signature. As a result, in various contract procedures at financial institutions, the customer can make an application without bringing a seal or passbook at the window. In addition, paper-based application documents can be abolished, reducing the burden of filling in customers and writing deficiencies. Further, the customer and the person in charge of the window can confirm the application contents together, and the efficiency of the procedure can be improved.

Claims (9)

An apparatus for executing processing related to a transaction contract with a customer at a financial institution, wherein the apparatus
Receiving application content data, which is data relating to the application content of the transaction contract, from the first computer;
Receiving authentication data of the customer from the first computer or the second computer;
If there is no problem in the verification result between the authentication data and pre-registered master data, based on the application content data and the authentication data, the transaction contract data and the contract file that are data related to the execution content of the transaction contract The contract file is image data of a contract in which handwritten signature data and / or seal imprint data, which is the verified authentication data, are embedded,
An apparatus configured to execute processing related to the transaction contract based on the transaction contract data. Apparatus according to claim 1, characterized in that it comprises the authentication data further biometric data. The apparatus of claim 1 or 2, further configured to verify the authentication data with the master data. The apparatus according to claim 1, further configured to receive the master data from the first computer, the second computer, or a third computer. A plurality of pieces of master data are registered for one piece of the authentication data, and the verification of the authentication data and the master data can be performed by comparing the authentication data with the plurality of master data and satisfying a predetermined matching rate. if, it is determined that there is no problem with the check result, the master data, claim, characterized in that it is further configured to so that is updated based on the check completed authentication data acquired for each collation 1 The apparatus in any one of thru | or 4. 6. The apparatus of claim 5, further configured to provide a time stamp to the master data and / or the contract file. 2. The apparatus according to claim 1, further configured to create customer copy data, which is data related to a customer copy of the transaction contract, based on the transaction contract data when the transaction contract is successfully executed. The apparatus in any one of thru | or 6. A method in which the apparatus executes processing related to a transaction contract with a customer at a financial institution, wherein the method includes:
Receiving, from the first computer, application content data that is data relating to the application content of the transaction contract;
Receiving authentication data of the customer from the first computer or the second computer;
If there is no problem in the verification result between the authentication data and pre-registered master data, based on the application content data and the authentication data, the transaction contract data and the contract file that are data related to the execution content of the transaction contract The contract file is image data of a contract embedded with handwritten signature data and / or seal imprint data that is the verified authentication data; and
And a step of executing a process related to the transaction contract based on the transaction contract data. A computer program for executing a method of performing processing according to the contracts with use customers in window of the financial institution to the apparatus, the computer program, when executed by said device, said device,
Receiving application content data, which is data relating to the application content of the transaction contract, from the first computer;
Receiving authentication data of the customer from the first computer or the second computer;
If there is no problem in the verification result between the authentication data and pre-registered master data, based on the application content data and the authentication data, the transaction contract data and the contract file that are data related to the execution content of the transaction contract The contract document file is image data of a contract in which handwritten signature data and / or imprint data, which is the verified authentication data, are embedded,
A computer program for executing processing related to the transaction contract based on the transaction contract data.

Images