Program, information processing device, information processing system, information processing method

Abstract

The present invention provides a program, information processing device, information processing system, and information processing method for electronically concluding a single contract based on multiple contractual documents prepared by multiple contracting parties. [Solution] The contract confirmation processing program executes the following steps: a first reception step of receiving input of first contract terms from a first user; a first presentation step of presenting the first contract terms to a second user; a second reception step of receiving input of second contract terms from a second user in relation to the first contract terms; a storage step of associating and storing the first contract terms and the second contract terms as a single set of contract terms relating to a single contract procedure; and an approval step of storing information indicating that the first contract terms and the second contract terms have been approved by at least one of the first user or the second user.

Description

Technical Field

[0001] The present disclosure relates to a program, an information processing apparatus, an information processing system, and an information processing method.

Background Art

[0002] With the development and spread of computer technology, documents that have hitherto been in paper form are being digitized. For example, it is conceivable to manage documents such as contract documents that require the signature and seal of the parties concerned in electronic data. And there are cases where one contract is concluded as a single entity based on documents related to a plurality of contracts prepared by a plurality of contracting parties respectively. For example, when placing an order for construction work or the like, the orderer creates a subcontracting contract, the contractor creates a specification document and an estimate based on the content of the subcontracting contract, and the orderer concludes one contract by confirming and agreeing to the content of the specification document and the estimate. For example, in an employment contract, the employer creates an employment contract, the worker prepares a certificate of identity, confirmation of residence status, and other certificates of qualifications based on the content of the employment contract, and the employer concludes one contract by confirming and agreeing to the content of the certificate of identity, confirmation of residence status, and other certificates of qualifications. For example, in an insurance contract, the insurance company creates an application form and a contract document, the customer prepares a medical examination report or the like based on the content of the application form and the contract document, and the insurance company concludes one contract by confirming and agreeing to the content of the medical examination report or the like. Patent Document 1 discloses a data storage destination restriction device that can restrict the data storage destination in units of user groups within a company. Patent Document 2 discloses an information processing system related to a digital contract including a creator terminal, a confirmation company terminal, and a contract document management server.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

[0004] In the electronic contract system, only one user (creator) could create contract documents and draft contract procedures. The recipient could review the contents of the contract documents created by the creator and enter the necessary information into the input fields set in the contract documents. However, in contract procedures where multiple contracting parties need to prepare their own contract documents, these parties must send their documents in advance to a single user designated as the document creator, who then compiles all the documents and drafts the contract procedure. This resulted in cumbersome communication between the contracting parties. Furthermore, such communication between contracting parties often took place via telephone, email, or chat tools, leading to the problem that records of these communications were not stored in the electronic contract system. Therefore, this disclosure has been made to solve the above-mentioned problems, and its purpose is to enable electronic contract systems that allow multiple users to execute electronic contract procedures, in which multiple contracting parties prepare multiple contractual documents and then electronically conclude a single contract as a whole. [Means for solving the problem]

[0005] A program comprising a processor and a memory unit, for causing a computer to execute an electronic contract procedure between multiple users, the program causing the processor to execute: a first reception step of receiving input of first contract terms from a first user; a first presentation step of presenting the first contract terms received in the first reception step to a second user; a second reception step of receiving input of second contract terms from a second user in relation to the first contract terms presented in the first presentation step; a storage step of storing the first contract terms received in the first reception step and the second contract terms received in the second reception step as a unified set of contract terms relating to a single contract procedure; and an approval step of storing information indicating that the first contract terms received in the first reception step and the second contract terms received in the second reception step have been approved by at least one of the first or second user. [Effects of the Invention]

[0006] According to this disclosure, based on document information containing the contract terms and conditions that each contracting party prepares, it is possible to conclude an electronic contract as a single entity, with the contract defined by multiple contract terms and conditions. [Brief explanation of the drawing]

[0007] [Figure 1] This is a diagram showing the overall configuration of information processing system 1. [Figure 2] This block diagram shows the functional configuration of Server 10. [Figure 3] This is a block diagram showing the functional configuration of the first user terminal 20. [Figure 4] This is a block diagram showing the functional configuration of the second user terminal 30. [Figure 5] This diagram shows the data structure of user table 1012. [Figure 6] This diagram shows the data structure of group table 1013. [Figure 7] This diagram shows the data structure of contract table 1014. [Figure 8] It is a diagram showing the data structure of document table 1015. [Figure 9] It is a diagram showing the data structure of confirmation table 1016. [Figure 10] It is a diagram showing the data structure of input item table 1017. [Figure 11] It is a flowchart showing the operation of contract document creation processing. [Figure 12] It is a flowchart showing the operation of contract document confirmation processing. [Figure 13] It is an example screen showing the operation of contract document creation processing. [Figure 14] It is an example screen showing the message notified to the second user terminal 30. [Figure 15] It is an example screen presented to the second user in contract document confirmation processing. [Figure 16] It is an example screen presented to the first user in contract document confirmation processing. [Figure 17] It is a block diagram showing the basic hardware configuration of computer 90.

Mode for Carrying Out the Invention

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for describing the embodiments, common components are denoted by the same reference numerals, and repeated descriptions are omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure. Also, each figure is a schematic diagram and is not necessarily drawn precisely.

[0009] <Configuration of System 1> System 1 in the present disclosure is an information processing system for realizing an electronic contract conclusion service among a plurality of users. System 1 includes information processing devices of server 10, first user terminal 20, second user terminal 30, and third user terminal 40, which are connected via network N. FIG. 1 is a diagram showing the overall configuration of information processing system 1. FIG. 2 is a block diagram showing the functional configuration of server 10. FIG. 3 is a block diagram showing the functional configuration of first user terminal 20. FIG. 4 is a block diagram showing the functional configuration of second user terminal 30.

[0010] Each information processing device is composed of a computer including an arithmetic device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of server 10, first user terminal 20, second user terminal 30, and third user terminal 40, descriptions overlapping with the basic hardware configuration of the computer and the basic functional configuration of the computer to be described later will be omitted.

[0011] <Configuration of Server 10> Server 10 is an information processing device that provides an electronic contract conclusion service among multiple users. Server 10 includes storage unit 101 and control unit 104.

[0012] <Configuration of Storage Unit 101 of Server 10> The storage unit 101 of server 10 includes application program 1011, user table 1012, group table 1013, contract table 1014, document table 1015, confirmation table 1016, and input item table 1017.

[0013] Application program 1011 is a program for causing the control unit 104 of server 10 to function as each functional unit.

[0014] User Table 1012 is a table that stores and manages information about member users (hereinafter referred to as "users") who use the service. When a user registers to use the service, their information is stored in a new record in User Table 1012. This allows the user to use the service related to this disclosure. Note that users who use the service in this disclosure do not necessarily need to be registered in User Table 1012. User table 1012 is a table with User ID as the primary key and containing columns for User ID, Username, Email Address, and Group ID. Figure 5 shows the data structure of user table 1012.

[0015] The User ID is an item that stores user identification information to identify a user. User identification information is an item that is set to a unique value for each user. The username field is used to store the user's real name. However, the username can also be a nickname or any other string of characters. The email address field is where the user's email address is stored. The Group ID is an item that stores the group identification information of the group to which the user belongs. A user may belong to multiple groups.

[0016] Group table 1013 is a table that stores and manages information about the groups to which a user belongs (group information). A group can be any group to which a user belongs, such as a corporation, company, club, organization, or department within a company. Group table 1013 is a table with Group ID as the primary key and containing columns for Group ID, Group Name, and Administrator ID. Figure 6 shows the data structure of group table 1013.

[0017] The Group ID is an item that stores group identification information used to identify a group. This group identification information is a unique value assigned to each group. The group name is an item that stores the name of the group. The group name can be set to any string. The Administrator ID is an item that stores the user identification information of users who have administrator privileges within a group. Users with administrator privileges can arbitrarily define and set administrator IDs for users who have a certain level of status or authority or higher within a group such as an organization.

[0018] The contract table 1014 is a table for storing and managing information (contract information) related to electronic contracts exchanged between multiple users. In this disclosure, contract information includes the information stored in the contract table 1014 and the document information stored in the document table 1015, which is associated with the contract ID in the contract table 1014. Contract table 1014 is a table that has Contract ID as its primary key and contains columns for Contract ID and Contract Type. Figure 7 shows the data structure of contract table 1014.

[0019] The contract ID is an item that stores contract identification information used to identify contract information. The contract identification information is an item with a unique value assigned to each piece of contract information. The contract type field stores the type of contract information (contract type information). Specifically, the contract type information stores values ​​related to the type of contract information, such as real estate or goods lease agreements, confidentiality agreements, joint research agreements, contract work agreements, employment agreements, and insurance agreements.

[0020] Document table 1015 is a table for storing and managing document information that defines the contract terms and conditions of a contract exchanged between multiple users. In this disclosure, multiple document information entries are associated and stored with a single contract information entry. Document table 1015 is a table with Document ID as the primary key and containing columns for Document ID, Contract ID, Document Data, Document Type, Creator ID, and Creation Date and Time. Figure 8 shows the data structure of document table 1015.

[0021] The document ID is an item that stores document identification information used to identify document information. The document identification information is an item with a unique value assigned to each piece of document information. The contract ID is an item that stores the contract identification information of the contract information to which the document information is associated. In this disclosure, multiple document information items are associated and stored with a single contract ID. Document data is an item that stores document information (binary or text data) that specifies the terms and conditions of a contract. The document type field stores information about the type of document (document type information). Specifically, the document type information stores information about the type of document, such as contracts, design drawings, templates, specifications, quotations, and medical examination reports. This field stores user identification information to identify the creator of the document (e.g., the first user or second user). The creation date and time field stores the date and time when the document data was saved in document table 1015 by the creator.

[0022] Confirmation table 1016 is a table that stores and manages information (confirmer information) including the email address of the user who will be confirming the contract information. Confirmation table 1016 is a table that has columns for document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time. Figure 9 shows the data structure of confirmation table 1016.

[0023] The document ID is an item that stores the document identification information of the contract information to be reviewed by the verifier. The "Verification Order" field stores information about the order in which contract information is reviewed by the reviewers. For example, contract information stored by the first user is circulated to the reviewers in the order specified in the verification order, and each reviewer is then reviewed. The verifier email address field stores the email address of the person who verifies the contract information. The verifier email address does not need to be registered in advance to use the services related to this disclosure. In other words, the verifier email address does not need to be included in user table 1012. The confirmation flag is an item that stores confirmation identification information to determine whether the confirmation procedure for contract information has been completed by the verifier. When the confirmation of contract information is completed by the verifier, information indicating that the confirmation has been completed, such as a value of True, is stored in the confirmation flag item. Language data is an item that stores information about the verifier's language (language information). The access code is an item that stores the access code set for the verifier. The date and time field stores the date and time when the verifier performed the contract information verification procedure. Specifically, it stores the date and time when the verification identification information was stored in the verification flag field.

[0024] Input item table 1017 is a table that stores and manages information about input items associated with contract information (input item information). Input item table 1017 is a table that has columns for input item ID, document ID, inputter ID, input data, input rules, and date and time. Figure 10 shows the data structure of input item table 1017.

[0025] The input field ID is an item that stores input field identification information used to identify an input field. The document ID is an item that stores the document identification information of the contract information to which the input item is associated. The Inputter ID is a field that stores the user identification information or email address of the person who entered the data into the input field. For example, the Inputter ID may store the First User ID, the email address of the user identified by the First User ID, and the Confirmer's email address. Input data is an item that stores the input data entered by the user into the input fields. An input rule field is an item that stores information about the input rules for an input item. Input rules can store information about data types such as date, datetime, text, and integer, as well as, for strings, the number of characters, regular expressions for strings, and other arbitrary input rules for any input item. The date and time field stores the date and time when the user entered data into the input field.

[0026] <Configuration of the control unit 104 of server 10> The control unit 104 of the server 10 includes a user registration control unit 1041, a contract creation unit 1042, and a contract confirmation unit 1043. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0027] The user registration control unit 1041 processes information of users who wish to use the services related to this disclosure and stores it in the user table 1012. Information stored in the user table 1012 is obtained when a user opens a web page operated by the service provider from any information processing terminal, enters information into a designated input form, and sends it to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, and user registration is completed. As a result, users stored in the user table 1012 can use the service. Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a prescribed review and restrict whether or not the user can use the service. The user ID may be any string or number that can identify the user, and may be any string or number that the user wishes, or may be automatically set by the user registration control unit 1041.

[0028] The contract creation unit 1042 executes the contract creation process. Details will be described later.

[0029] The contract verification unit 1043 executes the contract verification process. Details will be described later.

[0030] <Configuration of the first user terminal 20> The first user terminal 20 is an information processing device operated by a user of the service. The first user terminal 20 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile device such as a smartphone or tablet. It may also be a wearable device such as an HMD (Head Mount Display) or a smartwatch. The first user terminal 20 includes a storage unit 201, a control unit 204, an input device 206, and an output device 208.

[0031] <Configuration of the storage unit 201 of the first user terminal 20> The storage unit 201 of the first user terminal 20 includes a first user ID 2011 and an application program 2012.

[0032] The first user ID 2011 is the user's account ID. The user transmits the first user ID 2011 from the first user terminal 20 to the server 10. The server 10 identifies the user based on the first user ID 2011 and provides the services related to this disclosure to the user. The first user ID 2011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the first user terminal 20.

[0033] The application program 2012 may be pre-stored in the memory unit 201, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. The application program 2012 includes applications such as a web browser application. The application program 2012 includes an interpreted programming language such as JavaScript® that is executed on the web browser application stored in the first user terminal 20.

[0034] <Configuration of the control unit 204 of the first user terminal 20> The control unit 204 of the first user terminal 20 comprises an input control unit 2041 and an output control unit 2042. The control unit 204 realizes each functional unit by executing the first user ID 2011 stored in the storage unit 201.

[0035] <Configuration of the input device 206 of the first user terminal 20> The input device 206 of the first user terminal 20 includes a camera 2061, a microphone 2062, a position information sensor 2063, a motion sensor 2064, and a touch device 2065.

[0036] <Configuration of output device 208 of the first user terminal 20> The output device 208 of the first user terminal 20 includes a display 2081 and a speaker 2082.

[0037] <Configuration of the second user terminal 30> The second user terminal 30 is an information processing device operated by a user of the service. The second user terminal 30 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile device such as a smartphone or tablet. It may also be a wearable device such as an HMD (Head Mount Display) or a smartwatch. The second user terminal 30 includes a storage unit 301, a control unit 304, an input device 306, and an output device 308.

[0038] <Configuration of the storage unit 301 of the second user terminal 30> The storage unit 301 of the second user terminal 30 includes a second user ID 3011 and an application program 3012.

[0039] The second user ID 3011 is the user's account ID. The user transmits the second user ID 3011 from the second user terminal 30 to the server 10. The server 10 identifies the user based on the second user ID 3011 and provides the services related to this disclosure to the user. The second user ID 3011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the second user terminal 30.

[0040] The application program 3012 may be pre-stored in the storage unit 301, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. The application program 3012 includes applications such as a web browser application. The application program 3012 includes an interpreted programming language such as JavaScript (registered trademark) that is executed on the web browser application stored in the second user terminal 30.

[0041] <Configuration of the control unit 304 of the second user terminal 30> The control unit 304 of the second user terminal 30 comprises an input control unit 3041 and an output control unit 3042. The control unit 304 realizes each functional unit by executing the second user ID 3011 stored in the storage unit 301.

[0042] <Configuration of the input device 306 of the second user terminal 30> The input device 306 of the second user terminal 30 includes a camera 3061, a microphone 3062, a position information sensor 3063, a motion sensor 3064, and a keyboard 3065.

[0043] <Configuration of the output device 308 of the second user terminal 30> The output device 308 of the second user terminal 30 includes a display 3081 and a speaker 3082.

[0044] <Operation of Information Processing System 1> The following describes each process of Information Processing System 1. Figure 7 shows the data structure of contract table 1014. Figure 11 is a flowchart showing the operation of the contract creation process. Figure 12 is a flowchart showing the operation of the contract verification process. Figure 13 shows an example screen illustrating the operation of the contract creation process. Figure 14 shows an example screen displaying a message notified to the second user terminal 30. Figure 15 shows an example of a screen presented to the second user during the contract verification process. Figure 16 shows an example of a screen presented to the first user during the contract confirmation process.

[0045] <Contract creation process> The contract creation process involves the first user creating contract information and sending it to the second user. In this disclosure, the first user is the user who creates the contract information, and the second user is the user who verifies the contract information. It is possible to set multiple users as verifiers when creating the contract information. Furthermore, in this disclosure, the second user can also create the document information included in the contract information. In this disclosure, the first user is a user belonging to a different organization or group from the second user.

[0046] Figure 13 shows an example screen illustrating the operation of the contract creation process. The screen 50 displayed on the display 2081 of the first user terminal 20, which is used to create contract information, displays a status 510 indicating the current status of contract information creation, buttons 521, 522, and 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, and 534, and a send button 540.

[0047] <Overview of the contract creation process> The contract creation process is a series of steps in which the first user creates contract information, sets the second user to whom the contract information will be received, sets the input fields for the contract information, sets input rules for the input fields, receives input data for the input fields from the first user, and sends the contract information to the set second user.

[0048] <Details of the contract creation process> In step S101, the contract creation unit 1042 of the server 10 receives input of the first contract terms from the first user. In other words, it receives contract information that is the subject of a contract to be concluded between the first user and the second user. Specifically, the first user operates the input device 206 of the first user terminal 20 to create contract information, including document data related to the contract. The document data can be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and can be included in the contract information. The document data specifies the contract terms and conditions that are the subject of the agreement between the first user and the second user. The first user operates the input device 206 of the first user terminal 20 and sends the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 receives the first user ID 2011 and document data and creates a new contract information record in the contract table 1014. This initiates the first contract procedure. The contract creation unit 1042 of the server 10 stores the contract ID of the created contract information record, the received first user ID 2011, and the document data in the contract ID, creator ID, and document data fields of the new record in the document table 1015, respectively. In other words, the document data is stored in association with the contract information. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the contract table 1014 and the document table 1015.

[0049] In this disclosure, the first user may include multiple document data in the contract information. In this case, the contract creation unit 1042 of the server 10 receives the first user ID 2011 and the multiple document data, and creates a new record of one contract in the contract table 1014. The contract creation unit 1042 of the server 10 stores the contract ID of the created record, the received first user ID 2011, and the multiple document data in the contract ID, creator ID, and document data fields of the multiple new records in the document table 1015, respectively. In other words, multiple document data are stored associated with one piece of contract information.

[0050] The first user may include contract type information in the contract information sent to server 10. The contract confirmation unit 1043 of server 10 may be configured to accept the contract type of one contract procedure. For example, the first user selects the type of contract information they wish to conclude with the second user from a list of multiple contract type information and sends it to the server 10. Alternatively, the contract creation unit 1042 of the server 10 may be configured to identify the contract type information based on the file name of the document data received from the first user, the wording of the contract terms contained in the document data, the title of the contract document contained in the document data (such as the name of the contract, like a non-disclosure agreement), and the names of the clauses of the contract document contained in the document data. The contract creation unit 1042 of server 10 stores the received or identified contract type information in the contract type field of the newly created contract information record.

[0051] The first user may include document type information in the contract information sent to the server 10. For example, the first user selects the type of document information to include in the contract information from multiple document type information sources and sends it to the server 10. Alternatively, the contract creation unit 1042 of the server 10 may be configured to identify the document type information based on the file name of the document data received from the first user, the wording of the contract terms included in the document data, the title of the contract document included in the document data (such as the name of the contract, like a non-disclosure agreement), and the clause names of the contract document included in the document data. The contract creation unit 1042 of server 10 stores the received or identified document type information in the document type field of the same record as the target document data in document table 1015. Furthermore, if the contract information includes multiple document data, the contract creation unit 1042 of the server 10 may be configured to store the document type information for each document data in the document type column of the document table 1015.

[0052] Depending on the contract type of the contract procedure in step 1, the system may be configured to accept first document information having a first document type assigned to the first user. Specifically, if the first user selects the type of contract information they wish to conclude with the second user from among multiple contract type information, the system may be configured such that the document type information of the document data that the first user can include in the contract information is restricted according to the contract type information selected by the first user.

[0053] For example, if the contract type of contract procedure 1 is a lease agreement for real estate or goods, the system may be configured to accept document data related to the lease agreement for real estate or goods. Specifically, if the first user selects "Lease Agreement for Real Estate or Goods" as the contract type information, the document type information of the document data that the first user can include in the contract information may be limited to "Lease Agreement for Real Estate or Goods," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent proceeding to step S102 if it determines that the document type information identified by the received document data is other than "Lease Agreement for Real Estate or Goods." In this case, a message may be displayed to the first user prompting them to include document data with document type information of "Lease Agreement for Real Estate or Goods" in the contract information.

[0054] For example, if the contract type of contract procedure 1 is a contract in which an individual contract is made in relation to the basic contract, the system may be configured to accept document data related to the basic contract. Specifically, if the first user selects "a contract that associates an individual contract with the basic contract" as the contract type information, the document type information of the document data that the first user can include in the contract information may be limited to "basic contract," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent proceeding to step S102 if it determines that the document type information identified by the received document data is other than "basic contract." In this case, a message may be displayed to the first user prompting them to include document data with document type information of "basic contract" in the contract information.

[0055] For example, if the contract type for contract procedure 1 is a contract for ordering construction work, the system may be configured to accept document data related to the contract for work. Specifically, if the first user selects "Contract for construction work, etc." as the contract type information, the document type information of the document data that the first user can include in the contract information may be limited to "Contract for Work," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent proceeding to step S102 if it determines that the document type information identified by the received document data is other than "Contract for Work." In this case, a message may be displayed to the first user prompting them to include document data with document type information of "Contract for Work" in the contract information.

[0056] For example, if the contract type for contract procedure 1 is an employment contract, the system may be configured to accept document data related to the employment contract. Specifically, if the first user selects "employment contract" as the contract type information, the document type information of the document data that the first user can include in the contract information may be limited to "employment contract," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent proceeding to step S102 if it determines that the document type information identified by the received document data is other than "employment contract." In this case, the first user may be presented with a message prompting them to include document data with document type information of "employment contract" in the contract information.

[0057] For example, if the contract type for contract procedure 1 is an insurance contract, the system may be configured to accept application forms and contract-related document data. Specifically, if the first user selects "insurance contract" as the contract type information, the document type information of the document data that the first user can include in the contract information may be limited to "application form, contract," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent proceeding to step S102 if it determines that the document type information identified by the received document data is other than "application form, contract." In this case, the first user may be presented with a message prompting them to include document data with document type information of "application form, contract" in the contract information.

[0058] The screen 50 for creating contract information displays the document data 531 stored in the document table 1015.

[0059] In step S102, the first user operates the input device 206 of the first user terminal 20 to select and identify the user who will be the verifier (recipient) of the contract information. In this disclosure, the first user selects and identifies the second user as the recipient. The first user operates the input device 206 of the first user terminal 20 to enter the email address of the second user, who will become the second user, and sends it to the server 10. The contract creation unit 1042 of the server 10 stores the received email address and the document ID of the document information created and stored in step S101 in the verifier email address and document ID fields of the verification table 1016, respectively, and stores the document information in association with the second user's email address. The first user may also set the language and access code of the second user and store them in association with the second user's email address. At this time, the value 1 is stored in the confirmation order field of confirmation table 1016. In step S102, the first user may select and set multiple users to be verifiers. In this case, the value of the confirmation order field for the second user is incremented by one according to the selection order and stored. This sets the circulation order for the second user in the contract confirmation process described later. Note that setting the circulation order is not mandatory.

[0060] In step S103, the first user operates the input device 206 of the first user terminal 20 to set the input items for the document information. Specifically, the first user operates the input device 206 of the first user terminal 20 to set multiple input fields for the document information created and stored in step S101. The input fields can be any fields, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a checkbox field for selecting check items, and a date field for entering the date. The first user operates the input device 206 of the first user terminal 20 and sends a request to the server 10 to add an input item. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the document information in the document ID of the new record in the input item table 1017. In this way, the newly added input item information is stored in association with the contract information. The first user can store multiple input item information in association with document information.

[0061] In step S104, the first user sets input rules for each input item to be added. The first user specifies the input rules for each input item information set in step S103 by operating the input device 206 of the first user terminal 20 and sends them to the server 10. The contract creation unit 1042 of the server 10 stores the received input rules in the input rule field of the record of each input item information in the input item table 1017. This allows input rules to be set for each input item.

[0062] In step S105, the contract creation unit 1042 of the server 10 receives input data for multiple input items entered by the first user. Specifically, the first user inputs input data for each input item set in step S104 by operating the input device 206 of the first user terminal 20. For example, the first user may input data for a number used to manage contract information, such as a reference number within the group to which they belong, into the input item where a management number is set. The first user may also input data for the date of the contract signing of the contract information into the input item where a contract signing date is set. Once the first user has finished inputting data into the input items, they send the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of server 10 stores the received input data in the input data field of the input item information in the input item table 1017, which is identified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1017.

[0063] In step S106, the contract creation unit 1042 of the server 10 receives an instruction from the first user to request the second user to conclude a contract regarding the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 and sends a request to the server 10 to send contract information by pressing the send button 540 displayed on the screen 50 for creating contract information. When the contract creation unit 1042 of the server 10 receives the request, it sends a message to the second user notifying them that the first user has sent a request to confirm contract information. For example, the contract creation unit 1042 of the server 10 sends a message to the second user's email address notifying them that the first user has sent a request to confirm contract information via email or other means of communication. The message sent to the second user will include information about a URL (Uniform Resource Locator) containing a contract ID to identify the contract information. The URL may directly contain the contract ID, or it may contain information such as an encrypted string of the contract ID, or a string that can identify the contract ID by referring to an unillustrated table. The URL may also contain information to identify the second user. For example, if the second user has not registered for the service related to this disclosure, the URL must contain information to identify the second user.

[0064] If the first user sets an access code for the second user, the first user will communicate the access code to the second user via email or other means. This ensures that even if the message sent to the second user is intercepted by a third party, the third party cannot perform the contract verification process unless they obtain the access code.

[0065] Figure 14 shows an example screen displaying a message notified to the second user terminal 30. The message screen 60 displayed on the display 3081 of the second user terminal 30 includes a message 61 and information about a URL 62 containing a contract ID for identifying contract information.

[0066] <Variation> If the first user selects and sets multiple verifiers in step S102, the system may be configured to allow different input field information to be set independently for each of the multiple verifiers in step S103. For example, if the first user sets two users, a second user and a third user, as the second user, the input fields for the contract start date and contract end date may be set for the second user, and the input field for the contract signing date may be set for the third user. In this case, in the contract confirmation process described later, the second user can input data for the contract start date and contract end date, but not for the contract signing date. On the other hand, the third user cannot input data for the contract start date and contract end date, but can input data for the contract signing date. The system may also be configured to allow multiple verifiers to be selected and set for a single input field.

[0067] On screen 50 for creating contract information, input fields 532, 533, and 534 are drawn as drawing objects. For input fields 532 and 533, the user identification information "USER-B" of the user who has been selected and set to input the input field is drawn as the assignment, and the input field type is drawn as "Text". For input field 534 related to stamping, the user identification information "USER-C" of the user who has been selected and set to stamp is drawn as the assignment, and the input field type is drawn as "Stamp".

[0068] <Contract Verification Process> The contract verification process involves a second user confirming the contents of the contract information received from the first user. If the second user includes new contract terms in the document information, the first user will then perform the same verification process.

[0069] <Overview of contract verification process> The contract verification process is a series of operations that accepts access from a second user, presents the second user with a screen displaying contract information, accepts input data from the second user for the input fields, and accepts data from the second user regarding the verification of the contract information.

[0070] <Details of contract verification process> In step S301, the second user can open the web page specified by the URL by operating the input device 306 or the like of the second user terminal 30 and selecting the URL contained in the received message, thereby opening the web page specified by the URL in the browser application of the second user terminal 30. As a result, the second user terminal 30 sends a request to the server 10 to execute the contract confirmation process. The contract verification unit 1043 of server 10 searches the contract ID field in contract table 1014 and document table 1015 based on the contract ID included in the received request, and retrieves the contract information and the document information included in the contract information. The contract verification unit 1043 of server 10 searches the document ID field in the verification table 1016 based on the document ID contained in the acquired document information and obtains the second user information. The contract verification unit 1043 of server 10 searches the document ID field in the input item table 1017 based on the document ID contained in the acquired document information and obtains the input item information associated with the document information.

[0071] In step S302, the contract verification unit 1043 of the server 10 identifies the second user. The second user may be identified based on the second user ID 3011 included in the request received from the second user terminal 30, or based on identification information for identifying the second user included in the URL. If the second user has not registered for the service related to this disclosure, it is necessary to identify the second user from the URL. For example, the URL may include information for identifying the second user, such as the second user's email address or user ID.

[0072] The contract confirmation unit 1043 of server 10 generates a screen for confirming the contract information based on the acquired contract information, second user information, and input item information, and sends it to the second user terminal 30.

[0073] In step S303, the contract terms received from the first user are presented to the second user. Specifically, the display 3081 of the second user terminal 30 displays a screen for confirming the contract information received from the server 10 and the document information that specifies the contract terms included in the contract information. The second user confirms the contract information displayed on the display 3081 of the second user terminal 30.

[0074] Figure 15 shows an example screen illustrating the operation of the contract confirmation process. The screen 70 displayed on the display 3081 of the second user terminal 30, which is used to confirm contract information, displays the status 710 indicating the current status of contract information creation, the contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, an agreement button 740, an add document button 750, and a document switching button 760.

[0075] In step S304, the contract confirmation unit 1043 of the server 10 receives input of contract conditions from the second user in relation to the contract conditions presented in step S303. The contract verification unit 1043 of server 10 accepts input for one or more input fields of contract information. Furthermore, the contract verification unit 1043 of server 10 can also accept new document information that specifies contract terms. Specifically, the second user operates the input device 306 of the second user terminal 30 to input data to input items 732, 733, 734, and 735 set in the contract information. In this disclosure, input item 736 is not assigned to input by the second user, so it is visually indicated that the second user cannot input data for that item.

[0076] Furthermore, the second user can add document information (second document information) containing contract terms and conditions to the contract information by operating the input device 306 of the second user terminal 30 and pressing the document addition button 750. Similar to step S101 of the contract creation process, the second user operates the input device 306 of the second user terminal 30 to create contract information, including document data related to the contract. The document data can be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and can be included in the contract information. The document data specifies the contract terms and conditions that are the subject of the agreement between the first user and the second user. The contract confirmation unit 1043 of server 10 stores the first document information containing the first contract terms received in step S101 of the contract creation process and the second document information containing the second contract terms received in step S304, as a single, associated set of contract terms relating to the contract procedure. Specifically, the second user operates the input device 306 of the second user terminal 30 and sends the created document data and the second user ID 3011 to the server 10. The contract creation unit 1042 of the server 10 receives the second user ID 3011 and the document data, and stores the contract ID, the received second user ID 3011, and the document data received in step S301 in the contract ID, creator ID, and document data fields of the new record in the document table 1015, respectively. In other words, the document data is stored in association with the contract information. As a result, the contract creation unit 1042 of the server 10 stores the second document information, which specifies the new contract conditions selected by the second user, in the document table 1015.

[0077] The contract creation unit 1042 of server 10 retrieves the first user's email address (first email address) by searching the user ID field in user table 1012 based on the first user's user ID. The contract creation unit 1042 of server 10 stores the document ID and first email address of the second document information in the document ID and verifier email address fields of confirmation table 1016, respectively. At this time, the confirmation flag field is stored with the value False. As a result, the second document information newly stored by the second user will contain information that has not been confirmed by the first user. The second user may also set the first user's language and access code and store them in association with the first user's email address. At this time, the "Confirmation Order" field in the confirmation table 1016 is incremented by one from the "Confirmation Order" field of the user who will be the confirmer, and stored. This sets the circulation order of the confirmers in the contract confirmation process. The circulation order may be incremented for each piece of contract information, or for each piece of document information. Note that setting the circulation order is not mandatory.

[0078] In this disclosure, the second user may include multiple document data in the contract information. In this case, the contract creation unit 1042 of the server 10 stores the contract ID, the received second user ID 3011, and the multiple document data in the contract ID, creator ID, and document data fields of multiple new records in the document table 1015, respectively. In other words, multiple document data are stored associated with one piece of contract information.

[0079] The second user may include document type information in the document information sent to the server 10. For example, the second user selects the type of document information to include in the contract information from multiple document type information sources and sends it to the server 10. Alternatively, the contract creation unit 1042 of the server 10 may be configured to identify the document type information based on the file name of the document data received from the second user, the wording of the contract terms included in the document data, the title of the contract document included in the document data (such as the name of the contract, like a non-disclosure agreement), and the clause names of the contract document included in the document data. The contract creation unit 1042 of server 10 stores the received or identified document type information in the document type field of the same record as the target document data in document table 1015. Furthermore, if the contract information includes multiple document data, the contract creation unit 1042 of the server 10 may be configured to store the document type information for each document data in the document type column of the document table 1015.

[0080] Depending on the contract type of the contract procedure in step 1, the system may also be configured to accept second document information having a second document type assigned to the second user. Specifically, if the first user selects the type of contract information they wish to conclude with the second user from among multiple contract type information, the system may be configured such that the document type information of the document data that the second user can include in the contract information is restricted according to the contract type information selected by the first user.

[0081] For example, if the contract type of the contract procedure in step 1 is a lease agreement for real estate or goods, the system may be configured to accept document data related to identity verification documents to be presented to the first user. Specifically, if the first user selects "Lease Agreement for Real Estate or Goods" as the contract type information, the document type information of the document data that the second user can include in the contract information may be limited to "Identity Verification Documents," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent the document information from being stored if it determines that the document type information identified by the received document data is other than "Identity Verification Documents." In this case, the second user may be presented with a message prompting them to include the document data for which the document type information is "Identity Verification Documents" in the contract information.

[0082] For example, if the contract type of contract procedure 1 is a contract in which an individual contract is made in association with a basic contract, the system may be configured to accept document data related to the individual contract. Specifically, if the first user selects "a contract that associates an individual contract with a basic contract" as the contract type information, the document type information of the document data that the second user can include in the contract information may be limited to "individual contract," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent the document information from being stored if it determines that the document type information identified by the received document data is other than "individual contract." In this case, a message may be displayed to the second user prompting them to include document data with document type information of "individual contract" in the contract information.

[0083] For example, if the contract type for contract procedure 1 is a contract for ordering construction work, the system could be configured to accept document data related to specifications and estimates. Specifically, if the first user selects "Contract for construction work, etc." as the contract type information, the document type information of the document data that the second user can include in the contract information may be limited to "Specifications, Quotations," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent the document information from being stored if it determines that the document type information identified by the received document data is anything other than "Specifications, Quotations." In this case, a message may be displayed to the second user prompting them to include document data with document type information of "Specifications, Quotations" in the contract information.

[0084] For example, if the contract type for contract procedure 1 is an employment contract, the system may be configured to accept document data related to personal guarantees, residence status verification, and other qualification certificates. Specifically, if the first user selects "employment contract" as the contract type information, the document type information that the second user can include in the contract information may be limited to "guarantee letter, residence status confirmation, and other qualification certificates," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent the document information from being stored if it determines that the document type information identified by the received document data is other than "guarantee letter, residence status confirmation, and other qualification certificates." In this case, a message may be displayed to the second user prompting them to include document data with document type information of "guarantee letter, residence status confirmation, and other qualification certificates" in the contract information.

[0085] For example, if the contract type for contract procedure 1 is an insurance contract, the system may be configured to accept document data related to a health examination report. Specifically, if the first user selects "insurance contract" as the contract type information, the document type information of the document data that the second user can include in the contract information may be limited to "health examination report," and other document type information may not be included in the contract information. The contract creation unit 1042 of the server 10 may stop processing and prevent the document information from being stored if it determines that the document type information identified by the received document data is other than "health examination report." In this case, a message may be displayed to the second user prompting them to include the document data with document type information of "health examination report" in the contract information.

[0086] Furthermore, the document information stored by the first user in step S101 of the document creation process (first document information) and the document information stored by the second user in step S304 of the document verification process (second document information) may be document information having different document types in relation to the same contract procedure.

[0087] The screen for creating contract information displayed on the display 3081 of the second user terminal 30 is the same as the example screen showing the operation of the contract creation process shown in Figure 13, so its explanation is omitted.

[0088] The second user can set input items for the second document information, similar to step S103 in the document creation process. The detailed process is the same as in step S103 in the document creation process, so the explanation is omitted. The second user can set input rules for each additional input field, similar to step S104 in the document creation process. The detailed process is the same as in step S104 in the document creation process, so the explanation is omitted. The second user can receive input data for multiple input fields entered by the second user, similar to step S105 in the document creation process. The detailed process is the same as in step S105 in the document creation process, so the explanation is omitted.

[0089] In step S305, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to conclude the contract as requested by the first user. The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30. If the second user agrees to or accepts the contents, they operate the input device 306 of the second user terminal 30 and press the consent button 740 displayed on the screen 70 for confirming the contract information. This causes the server 10 to execute a request that includes the document ID, information identifying the second user, and the input data for each input item entered in step S304. The information identifying the second user may also be the second user ID 3011. Specifically, the contract verification unit 1043 of server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Based on the received contract ID and information identifying the second user, the contract verification unit 1043 of server 10 searches the verification table 1016 and stores the value of True in the verification flag field of the record. For example, if the information identifying the second user is an email address, it searches the document ID and verifier email address fields in the verification table 1016 and stores the value of True in the verification flag field of the record. If the information identifying the second user is user identification information, it searches the document ID and verifier email address fields in the verification table 1016 based on the email address of the second user identified by searching the user ID field in user table 1012, and stores the value of True in the verification flag field of the record. Furthermore, the contract verification unit 1043 of server 10 may search the verification table 1016 for all document IDs associated with the received contract ID in the document table 1015, based on information identifying the second user, and store the value of True in the verification flag field of the relevant record. In other words, it stores the value of True in the verification flag field of all records in the verification table 1016 where the second user's email address is stored as the verifier email address identified based on the contract ID via the document ID. Furthermore, the contract verification unit 1043 of server 10 may accept the operation of the document switching button 760 by the second user and store the value of True in the verification flag field only for the document information actually presented to the second user. The contract confirmation unit 1043 of server 10 stores the received input data in the input data item of input item table 1017, which is identified by the input item ID associated with the input data. As a result, in step S304, the input data entered by the second user is stored as input item information in input item table 1017.

[0090] In step S306, the contract verification unit 1043 of the server 10 stores information indicating that the first document information containing the first contract terms, which was received in step S101 of the contract creation process, and the second document information containing the second contract terms, which was received in step S304 of the contract verification process, have been approved by at least one of the first user or the second user.

[0091] Specifically, when the contract verification unit 1043 of server 10 has completed the contract verification process by all users, it sends a message to the first user and the second user notifying them that the contract verification process is complete. For example, the contract creation unit 1042 of server 10 sends a message to the first user's email address notifying them that the second user has completed the verification of the contract information via email or other means of communication. The message sent to the first user includes information about a URL containing a contract ID to identify the contract information. Specifically, the contract verification unit 1043 of server 10 determines that the contract verification process has been completed by all users when the verification flag of the verification information associated with all document information included in the contract information stored in the verification table 1016 has a value of True. If multiple users are set as verifiers, the contract verification unit 1043 of server 10 may send a message to all users except the user who last performed the contract verification process, notifying them that the contract verification process is complete. This allows the verifiers to also receive notification that the contract verification process has been completed by all users. Furthermore, the contract verification unit 1043 of server 10 may send a message to a user with administrator-level privileges in a group to which the first user or multiple verifiers belong, notifying them that the contract verification process has been completed. This allows the administrator in a group to which the first user or multiple verifiers belong to be notified that the contract verification process has been completed. The contract verification unit 1043 of server 10 retrieves the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. Based on the retrieved group ID item, the contract verification unit 1043 of server 10 retrieves the group ID item in the group table 1013, retrieves the administrator ID item, identifies a user with administrator-level privileges by searching the user ID in the user table 1012 based on the administrator ID, and sends a message notifying them that the contract verification process has been completed.

[0092] The contract verification unit 1043 of server 10 searches for document information included in the contract information, and if there is any document information for which the contract verification process has not been performed, it sends a message to the verifier email address associated with the verification table 1016 prompting the verification of the document information. Specifically, the contract verification unit 1043 of server 10 searches the document table 1015 for the contract ID and retrieves the document ID. The contract verification unit 1043 of server 10 searches the verification table 1016 for the document ID and retrieves the verifier email address and verification flag. The contract verification unit 1043 of server 10 identifies the verifier email addresses from the retrieved verifier email addresses for which the verification flag has a value of False. In other words, the contract verification unit 1043 of server 10 identifies and retrieves the verifier email addresses of users who have not verified the document information. For example, if a second user newly stores second document information in step S304, the first email address of the first user associated with the second document information is identified as the email address of the user who has not performed the contract verification process on the second document information, since the contract verification process has not been performed on the second document information by the first user.

[0093] The contract verification unit 1043 of server 10 sends a message to the first user notifying them that a request for confirmation of contract information has been sent by the second user. For example, the contract verification unit 1043 of server 10 sends a message to the first user's email address notifying them that a request for confirmation of contract information has been sent by the second user, via email or other means of communication. The message sent to the first user will include information about a URL (Uniform Resource Locator) containing a contract ID to identify the contract information. The URL may directly contain the contract ID, or it may contain information such as an encrypted string of the contract ID, or a string that allows the contract ID to be identified by referring to an unillustrated table.

[0094] If the second user sets an access code for the first user, they will then communicate the access code to the first user via email or other means. This ensures that even if the message sent to the first user is intercepted by a third party, the third party cannot execute the contract verification process unless they obtain the access code.

[0095] The screen displaying the message notified to the first user terminal 20 is similar to the example screen displaying the message notified to the second user terminal 30 shown in Figure 14. The message screen 60 displayed on the display 2081 of the first user terminal 20 includes the message 61 and information about a URL 62 containing a contract ID for identifying contract information.

[0096] <Contract Verification Process (by the First User)> The contract verification process performed by the first user is described below. Note that steps S301 to S306 of the contract verification process (by the first user) differ only in that they are performed by the first user instead of the second user, and the processing content is the same as steps S301 to S306 of the contract verification process, so the explanation is omitted.

[0097] In step S301, the first user can open the web page specified by the URL by operating the input device 206 or the like of the first user terminal 20 and selecting the URL contained in the received message, thereby opening the web page specified by the URL in the browser application of the first user terminal 20. As a result, the first user terminal 20 sends a request to the server 10 to execute the contract confirmation process. The contract verification unit 1043 of server 10 searches the contract ID field in contract table 1014 and document table 1015 based on the contract ID included in the received request, and retrieves the contract information and the document information included in the contract information. The contract verification unit 1043 of server 10 searches the document ID field in the verification table 1016 based on the document ID contained in the acquired document information and obtains the first user information. The contract verification unit 1043 of server 10 searches the document ID field in the input item table 1017 based on the document ID contained in the acquired document information and obtains the input item information associated with the document information.

[0098] In step S302, the contract verification unit 1043 of the server 10 identifies the first user. The first user may be identified based on the first user ID 2011 included in the request received from the first user terminal 20, or based on the identification information for identifying the first user included in the URL.

[0099] The contract confirmation unit 1043 of server 10 generates a screen for confirming the contract information based on the acquired contract information, first user information, and input item information, and sends it to the first user terminal 20.

[0100] In step S303, the contract terms received from the second user are presented to the first user. Specifically, the display 2081 of the first user terminal 20 displays a screen for confirming the contract information received from the server 10 and the document information that specifies the contract terms included in the contract information. The first user confirms the contract information displayed on the display 2081 of the first user terminal 20.

[0101] Figure 16 shows an example screen illustrating the operation of the contract confirmation process. The screen 80 displayed on the display 2081 of the first user terminal 20, which is used to confirm contract information, displays the status 810 indicating the current status of contract information creation, the contract information display area 830, document data 831, an agreement button 840, an add document button 850, and a document switching button 860. The first user can selectively switch between multiple document information associated with contract information and display them on the display 2081 of the first user terminal 20 by operating the input device 206 of the first user terminal 20 and pressing the document switching button 860. For example, the first user can display the document information for the "Lease Agreement" in the contract information display area 830 by selecting "Lease Agreement". The first user can also display the document information for the "Identity Verification Document" in the contract information display area 830 by selecting "Identity Verification Document". Furthermore, screen 80, which is used to check contract information, may be configured to identify document information for which the user, as the verifier, does not have a True value stored in the verification flag, and to display that document information on screen 80 as the default document information. In other words, it may be configured to present unverified document information to the first user as the default document information. This allows the first user to prioritize checking document information they have not yet reviewed, enabling them to perform the document review process conveniently.

[0102] In step S304, the contract confirmation unit 1043 of the server 10 receives input of the contract conditions from the first user in relation to the contract conditions presented in step S303. The contract verification unit 1043 of server 10 accepts input for one or more input fields of contract information. Furthermore, the contract verification unit 1043 of server 10 can also accept new document information that specifies contract terms.

[0103] In step S305, the contract confirmation unit 1043 of the server 10 stores information indicating that the first document information specifying the first contract terms and the second document information specifying the second contract terms have been approved by the first user, in response to the input operation from the first user regarding the second document information specifying the second contract terms and Specifically, the contract confirmation unit 1043 of server 10 receives an instruction from the first user to agree to conclude a contract in response to a confirmation request from the second user. The first user confirms the contract information and input data displayed on the display 2081 of the first user terminal 20. If the first user agrees to or accepts the contents, they operate the input device 206 of the first user terminal 20 and press the consent button 840 displayed on the screen 80 for confirming the contract information. This causes the server 10 to execute a request that includes the document ID, information identifying the first user, and the input data for each input item entered in step S304. The information identifying the first user may be the first user ID 2011. Specifically, the contract confirmation unit 1043 of server 10 stores information indicating that the first user has confirmed the contract information based on the received request. Based on the received document ID and information identifying the first user, the contract confirmation unit 1043 of server 10 searches the confirmation table 1016 and stores the value of True in the confirmation flag field of the record. For example, if the information identifying the first user is an email address, it searches the document ID and confirmer email address fields in confirmation table 1016 and stores the value of True in the confirmation flag field of the record. If the information identifying the first user is user identification information, it searches the document ID and confirmer email address fields in confirmation table 1016 based on the email address of the first user identified by searching the user ID field in user table 1012, and stores the value of True in the confirmation flag field of the record. For example, in confirmation table 1016, the document ID and confirmation email address of the second document information, and the confirmation flag field of the record where the first user has stored this information, will be set to True. This indicates that the second document information has been confirmed by the first user. The contract confirmation unit 1043 of server 10 stores the received input data in the input data item of input item table 1017, which is identified by the input item ID associated with the input data. As a result, in step S304, the input data entered by the first user is stored as input item information in input item table 1017.

[0104] The contract verification unit 1043 of the server 10 stores information indicating that the first document information containing the first contract terms, which was received in step S101 of the contract creation process, and the second document information containing the second contract terms, which was received in step S304 of the contract verification process, have been approved by the first user and the second user.

[0105] <Electronic signature processing> Step S305 may include an electronic signature process. The contract verification unit 1043 of the server 10 affixes an electronic signature to the first and second contract terms and stores them in response to the input operation for the second contract terms from the first user. Specifically, the contract verification unit 1043 of server 10 affixes an electronic signature to the first document information containing the first contract terms and the second document information containing the second contract terms, based on the received request, and stores them. Based on the contract ID, the contract verification unit 1043 of server 10 searches the contract ID fields in the contract table 1014 and the document table 1015 to obtain the contract information and the document information contained in the contract information. The contract verification unit 1043 of server 10 affixes an electronic signature to the acquired document information and stores it in the contract data item of the document table 1015. The contract verification unit 1043 of server 10 may update (overwrite) the document information with the electronically signed document information, or it may store the document information before the electronic signature was added in a separate storage device (not shown). The contract verification unit 1043 of server 10 may include any of the following information in the electronic signature: document ID, email address of the first user, email address of the second user, approval date and time, confirmation date and time, authentication method for the approval date and time, authentication method for the confirmation date and time, input data values ​​for each input item, consent (approval) of the first user and the second user, and a timestamp. This means that the first user's agreement to an electronic contract comprising multiple contractual conditions, such as the first and second contractual conditions, is stored as an electronic signature in the first and second document information containing the first and second contractual conditions. This prevents third-party impersonation or tampering with the contractual conditions.

[0106] <Variation> In step S304 of the contract confirmation process, the system may be configured to receive modification instructions from the first user or the second user regarding the first document information containing the first contract terms received in step S101 of the contract creation process, or the second document information containing the second contract terms received in step S304. The contract confirmation unit 1043 of the server 10 may be configured to attach an electronic signature to the first contract terms or the second contract terms that are the subject of the modification instructions and store them in accordance with the received modification instructions. Specifically, the second user may operate the input device 306 of the second user terminal 30 to modify (edit) the first document information containing the first contract terms and conditions, and store it in the document table 1015. In this case, the contract verification unit 1043 of the server 10 may be configured to attach an electronic signature to the first document information that includes information indicating that it has been modified by the second user, and store it in the document table 1015. Similarly, the first user may operate the input device 206 of the first user terminal 20 to modify the second document information containing the second contract terms and conditions, and store it in the document table 1015. In this case, the contract verification unit 1043 of the server 10 may be configured to attach an electronic signature to the second document information that includes information indicating that it has been modified by the first user, and store it in the document table 1015. Furthermore, the system may be configured so that a second user can modify the second document information containing the second contract terms and store it in the document table 1015. Similarly, the system may be configured so that a first user can modify the first document information containing the first contract terms and store it in the document table 1015. This allows for the electronic signature to be stored on the amended first and second contract terms in response to modification instructions from the first or second user. This prevents third-party impersonation or tampering with the contract terms.

[0107] <Basic Computer Hardware Configuration> Figure 17 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 includes at least a processor 901, main memory 902, auxiliary memory 903, and a communication interface IF991. These are electrically connected to each other by a communication bus 921.

[0108] The processor 901 is hardware for executing the instruction set written in a program. The processor 901 consists of an arithmetic unit, registers, peripheral circuits, etc.

[0109] Main memory 902 is used to temporarily store programs and data processed by programs, etc. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0110] Auxiliary storage device 903 refers to a storage device for saving data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

[0111] The IF991 communication interface is an interface for inputting and outputting signals for communication with other computers via a network using wired or wireless communication standards. A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0112] Furthermore, by distributing all or part of each hardware configuration across multiple computers 90 and connecting them to each other via a network, a computer 90 can be virtually realized. Thus, the concept of computer 90 includes not only a computer 90 housed in a single enclosure or case, but also a virtualized computer system.

[0113] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 (Figure 17) will be explained. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.

[0114] Furthermore, the functional units of computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 interconnected via a network. The concept of computer 90 includes not only a single computer 90 but also a virtualized computer system.

[0115] The control unit is realized when the processor 901 reads various programs stored in the auxiliary storage device 903, loads them into the main memory device 902, and executes processing according to those programs. The control unit can realize various functional units that perform information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0116] The memory unit is implemented by the main memory 902 and the auxiliary memory 903. The memory unit stores data, various programs, and various databases. The processor 901 can also reserve memory areas corresponding to the memory unit in the main memory 902 or the auxiliary memory 903 according to the program. The control unit can also cause the processor 901 to perform operations such as adding, updating, and deleting data stored in the memory unit according to the various programs.

[0117] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters. Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.

[0118] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.

[0119] The communication unit is implemented by the communication IF991. The communication unit provides the functionality to communicate with other computers 90 via the network. The communication unit can receive information transmitted from other computers 90 and input it to the control unit. The control unit can cause the processor 901 to perform information processing on the received information according to various programs. The communication unit can also transmit information output from the control unit to other computers 90.

[0120] <Note> The details described in each of the above embodiments are noted below.

[0121] (Note 1) A program comprising a processor and a memory unit, for causing a computer to execute an electronic contract procedure between multiple users, the program causing the processor to execute: a first reception step (S101) for receiving input of first contract terms from a first user; a first presentation step (S303) for presenting the first contract terms received in the first reception step to a second user; a second reception step (S304) for receiving input of second contract terms from a second user in relation to the first contract terms presented in the first presentation step; a storage step (S304) for storing the first contract terms received in the first reception step and the second contract terms received in the second reception step as a unified set of contract terms relating to a single contract procedure; and an approval step (S305) for storing information indicating that the first contract terms received in the first reception step and the second contract terms received in the second reception step have been approved by at least one of the first user or the second user. This allows for the electronic conclusion of a single contract defined by multiple contract terms, based on document information containing the contract terms and conditions prepared by each user for multiple contracting parties.

[0122] (Note 3) The first document information and the second document information are document information having different document types in relation to one contract procedure, as described in Appendix 2 of the program. This allows multiple users, each with their own contractual documents, to electronically conclude a single contract as a whole.

[0123] (Note 4) The first reception step is a step of receiving first document information having a first document type assigned to the first user according to the contract type of the first contract procedure, and the second reception step is a step of receiving second document information having a second document type assigned to the second user according to the contract type of the first contract procedure, and the program is as described in any of the appendices 1 to 3. This allows users involved in multiple contracts to electronically conclude a single contract by preparing the appropriate document type according to the contract type of the contract procedure. Users can then appropriately input the necessary document information.

[0124] (Note 6) The program described in any of Appendix 1 to 5, wherein the first reception step is a step to receive the first document information relating to the lease agreement for real estate or goods when the contract type of the contract procedure is a lease agreement for real estate or goods, and the second reception step is a step to receive the identity verification documents to be presented to the first user when the contract type of the contract procedure is a lease agreement for real estate or goods. As a result, when a user with multiple contracting parties enters into a lease agreement for real estate or goods, they can electronically conclude a single contract defined by multiple contracting conditions, based on document information containing the contracting conditions prepared by each of the contracting parties, without the need for cumbersome communication between the contracting parties.

[0125] (Note 8) The program is one of the programs described in any of Appendix 1 to 7, wherein the program causes the processor to perform a second presentation step (S303) in which it presents the second contract terms received in the second reception step to the first user, and the approval step is a step in which the program stores information indicating that the first contract terms and the second contract terms have been approved by the first user in response to the input operation from the first user regarding the second contract terms presented to the first user in the second step. This allows the first user to agree to enter into the contract after reviewing the second contract terms entered by the second user. It also prevents the contract from being entered into without the first user reviewing the second contract terms entered by the second user.

[0126] (Note 9) The second presentation step is the program described in Appendix 8, which presents the second contract terms to the first user as predefined document information. This allows the first user to prioritize checking document information they have not yet reviewed, enabling them to perform the document review process conveniently.

[0127] (Note 10) The program is the program described in Appendix 8 or 9, which causes the processor to perform a signing step (S305) in which it electronically signs and stores the first and second contract terms in response to an input operation from the first user regarding the second contract terms in the approval step. This means that the first user's agreement to the electronic contract, which is a single contract defined by multiple contract terms and conditions (First and Second Terms and Conditions), is recorded as an electronic signature in the First and Second Terms and Conditions. This prevents third-party impersonation or tampering with the contract terms and conditions.

[0128] (Note 11) The program is one of the programs described in any of the appendices 1 to 10, which causes the processor to execute a modification step (S304) which receives modification instructions from the first user or the second user regarding the first contract terms received in the first reception step or the second contract terms received in the second reception step, and a modification signature step (S305) which, in response to the modification instructions received in the modification step, affixes an electronic signature to the first contract terms or the second contract terms that are the subject of the modification instructions and stores them. This allows the first or second user to flexibly modify the first or second contract terms, and an electronic signature is stored on the modified first and second contract terms in response to modification instructions. This prevents third-party impersonation or tampering with the contract terms.

[0129] (Note 12) An information processing apparatus comprising a processor and a memory unit, wherein the processor is instructed to execute a program described in any of the appendices 1 to 11. This allows for the electronic conclusion of a single contract defined by multiple contract terms, based on document information containing the contract terms and conditions prepared by each user for multiple contracting parties.

[0130] (Note 13) An information processing system including an information processing device comprising a processor and a memory unit, wherein the system causes the processor to execute any of the programs described in appendices 1 to 11. This allows for the electronic conclusion of a single contract defined by multiple contract terms, based on document information containing the contract terms and conditions prepared by each user for multiple contracting parties.

[0131] (Note 14) An information processing method performed by a computer comprising a processor and a memory unit, wherein the processor is made to execute a program described in any of the appendices 1 to 11. This allows for the electronic conclusion of a single contract defined by multiple contract terms, based on document information containing the contract terms and conditions prepared by each user for multiple contracting parties. [Explanation of symbols]

[0132] 1 System, 10 Servers, 101 Storage Unit, 104 Control Unit, 106 Input Device, 108 Output Device, 20 First User Terminal, 201 Storage Unit, 204 Control Unit, 206 Input Device, 208 Output Device, 30 Second User Terminal, 301 Storage Unit, 304 Control Unit, 306 Input Device, 308 Output Device

Claims

1. A program comprising a processor and a memory unit, which causes a computer to perform electronic contract procedures between multiple users, The program is provided to the processor: The first reception step involves receiving input from the first user regarding the first contract terms, The first presentation step involves presenting the first contract terms received in the first reception step to the second user, In the first presentation step, the second reception step receives input from the second user regarding the second contract terms, in addition to the first contract terms presented in the first presentation step. A storage step that stores the first contract terms received in the first reception step and the second contract terms received in the second reception step, as a single set of contract terms relating to the contract procedure, An approval step that stores information indicating that the first contract terms received in the first acceptance step and the second contract terms received in the second acceptance step have been approved by at least one of the first user or the second user, A program that executes the command.

2. The first application step is the step of receiving the information for the first document in which the first contract terms are stipulated. The second application step is the step of receiving the information for the second document, which contains the second contract terms and conditions. The program according to claim 1.

3. The first document information and the second document information are document information having different document types in relation to the contract procedure described in item 1 above. The program according to claim 2.

4. The first reception step is a step of receiving first document information having a first document type assigned to the first user according to the contract type of the contract procedure in 1 above, The second reception step is a step in which the second document information having a second document type assigned to the second user according to the contract type of the contract procedure in step 1 above is received. A program according to any one of claims 1 to 3.

5. The program is provided to the processor: A contract type acceptance step that accepts the contract type for the contract procedure described in item 1 from the first user, The program according to claim 4 that causes to execute.

6. The first reception step is a step in which, when the contract type of the contract procedure in item 1 above is a lease agreement for real estate or goods, the first document information relating to the lease agreement for said real estate or goods is received. The second reception step is the step of receiving the identity verification documents to be presented to the first user when the contract type of the contract procedure in step 1 is a lease agreement for real estate or goods. A program according to any one of claims 1 to 5.

7. The first reception step is a step in which, when the contract type of the contract procedure in 1 above is a contract in which an individual contract is made in association with the basic contract, the first document information relating to the basic contract is received. The second reception step is a step in which, when the contract type of the contract procedure in step 1 is a contract in which an individual contract is made in association with the basic contract, the second document information relating to the individual contract is received. A program according to any one of claims 1 to 5.

8. The program is provided to the processor: The second presentation step involves presenting the second contract terms received in the second reception step to the first user, Make it run, The aforementioned approval step is, In the second step, in response to the input operations from the first user regarding the second contract terms presented to the first user, This is a step of storing information indicating that the first contract terms and the second contract terms have been approved by the first user. A program according to any one of claims 1 to 7.

9. The second presentation step is to present the second contract terms to the first user as predefined document information. The program according to claim 8.

10. The program is provided to the processor: A signing step in which, in response to the input operation of the first user regarding the second contract terms in the approval step, an electronic signature is applied to the first contract terms and the second contract terms and they are stored, A program according to claim 8 or 9 that causes to execute

11. The program is provided to the processor: A revision step in which the first contract terms received in the first acceptance step or the second contract terms received in the second acceptance step are modified by the first user or the second user, A modification signature step in which, in response to a modification instruction received in the modification step, an electronic signature is affixed to the first or second contract terms subject to the modification instruction and stored; A program according to any one of claims 1 to 10 that causes to execute.

12. An information processing device comprising a processor and a memory unit, The processor is made to execute the program described in any one of claims 1 to 11. Information processing device.

13. An information processing system including an information processing device comprising a processor and a memory unit, The processor is made to execute the program described in any one of claims 1 to 11. An information processing system that executes [this].

14. An information processing method performed by a computer comprising a processor and a memory unit, The processor is made to execute the program described in any one of claims 1 to 11. Information processing methods.

Images