JP7366168B2 - Program, information processing device, information processing system, information processing method - Google Patents

Description

The present disclosure relates to a program, an information processing device, an information processing system, and an information processing method.

With the development and spread of computer technology, documents that were previously paper-based are being digitized. For example, it is being considered that documents such as contracts that require the signatures and seals of the parties involved will be managed using electronic data.
In some cases, a single contract is concluded as a single entity based on multiple contract-related documents prepared by multiple contract parties.
For example, when placing an order for construction work, the ordering party creates a contract, the contractor creates specifications and estimates based on the contents of the contract, and the ordering party confirms the contents of the specifications and estimates and agrees. By doing so, contract 1 will be concluded.
For example, in an employment contract, the employer prepares the employment contract, the worker prepares a letter of guarantee, confirmation of residence status, and other qualifications based on the contents of the employment contract; The contract 1 is concluded by confirming qualifications and confirming and agreeing on the contents of other qualification certificates.
For example, in an insurance contract, the insurance company creates an application/contract, the customer prepares a health certificate, etc. based on the contents of the application/contract, and the insurance company confirms the contents of the health certificate, etc. Upon agreement, contract 1 is concluded.
Patent Document 1 discloses a data storage destination restriction device that can restrict data storage destinations for each user group within a company.
Patent Document 2 discloses an information processing system regarding digital contracts that includes a creator terminal, a confirming company terminal, and a contract management server.

JP2021-51345 JP2017-10096

In the electronic contract system, only one user (creator) could create contract documents and draft contract procedures. The recipient was able to check the contents of the contract document created by the creator and enter necessary information into the input items set in the contract document.
However, in contract procedures where multiple parties to a contract need to prepare their own contract documents, the multiple contract parties send the contract documents in advance to one user, who is the creator, and the creator compiles all the contract documents. , it was necessary to draft contract procedures, resulting in complicated communication between contracting parties. Further, such communication between contract parties is often carried out via telephone, e-mail, chat tools, etc., and there is a problem that communication records between contract parties are not stored in the electronic contract system.
Therefore, the present disclosure has been made to solve the above-mentioned problems, and the purpose is to provide a plurality of contracts that are prepared by a plurality of contracting parties in an electronic contract system that executes electronic contract procedures between a plurality of users. It is to conclude an electronic contract with one contract as one entity based on the documents related to the contract.

A program, comprising a processor and a storage unit, for causing a computer to execute electronic contract procedures between a plurality of users, the program receiving input of first contract conditions from a first user to the processor. a first reception step; a first presentation step of presenting the first contract conditions received in the first reception step to the second user; and a second user , a second reception step receives the input of the second contract conditions, the first contract conditions received at the first reception step, and the second contract conditions received at the second reception step are set as the contract conditions regarding the contract procedure of 1. a storage step in which the first contract conditions received in the first reception step and the second contract conditions received in the second reception step are stored in association with each other as a unit by at least one of the first user and the second user. An approval step for storing information indicating approval; and a program for executing the approval step.

According to the present disclosure, based on document information that specifies the contract conditions that are the subject of the contract prepared by multiple contract parties, an electronic contract is created as one contract that is defined by multiple contract conditions. can be concluded.

1 is a diagram showing the overall configuration of an information processing system 1. FIG. 1 is a block diagram showing the functional configuration of a server 10. FIG. 2 is a block diagram showing the functional configuration of a first user terminal 20. FIG. 3 is a block diagram showing the functional configuration of a second user terminal 30. FIG. 3 is a diagram showing a data structure of a user table 1012. FIG. 3 is a diagram showing the data structure of a group table 1013. FIG. 3 is a diagram showing a data structure of a contract table 1014. FIG. 3 is a diagram showing the data structure of a document table 1015. FIG. 3 is a diagram showing a data structure of a confirmation table 1016. FIG. 3 is a diagram showing the data structure of an input item table 1017. FIG. 3 is a flowchart showing the operation of contract creation processing. 3 is a flowchart showing the operation of contract confirmation processing. This is an example screen showing the operation of contract creation processing. This is an example of a screen showing a message notified to the second user terminal 30. This is an example of a screen presented to the second user in the contract confirmation process. This is an example of a screen presented to the first user in contract confirmation processing. 2 is a block diagram showing the basic hardware configuration of a computer 90. FIG.

Embodiments of the present disclosure will be described below with reference to the drawings. In all the figures explaining the embodiments, common components are given the same reference numerals and repeated explanations will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are essential components of the present disclosure. Furthermore, each figure is a schematic diagram and is not necessarily strictly illustrated.

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

Each information processing device is composed of a computer including an arithmetic unit 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. Regarding each of the server 10, the first user terminal 20, the second user terminal 30, and the third user terminal 40, explanations that overlap with the basic hardware configuration of the computer and the basic functional configuration of the computer, which will be described later, will be omitted.

<Configuration of server 10>
The server 10 is an information processing device that provides electronic contract conclusion services between multiple users.
The server 10 includes a storage section 101 and a control section 104.

<Configuration of storage unit 101 of server 10>
The storage unit 101 of the server 10 includes an application program 1011, a user table 1012, a group table 1013, a contract table 1014, a document table 1015, a confirmation table 1016, and an input item table 1017.

The application program 1011 is a program for causing the control unit 104 of the server 10 to function as each functional unit.

The 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 a service, the user's information is stored in a new record in the user table 1012. This allows the user to use the service according to the present disclosure. Note that in the present disclosure, users who use services do not necessarily need to be registered in the user table 1012.
The user table 1012 is a table having user ID as a primary key and columns of user ID, user name, email address, and group ID.
FIG. 5 is a diagram showing the data structure of the user table 1012.

The user ID is an item that stores user identification information for identifying a user. The user identification information is an item in which a unique value is set for each user.
The user name is an item that stores the user's name. The user name may be any character string such as a nickname instead of a full name.
The email address is an item that stores the user's email address.
Group ID is an item that stores group identification information of a group to which a user belongs. A user may belong to multiple groups.

The group table 1013 is a table that stores and manages information regarding groups to which users belong (group information). The group can be defined as any group to which the user belongs, such as a corporation, company, circle, organization, or department within a company.
The group table 1013 is a table having columns of group ID, group name, and administrator ID, with group ID as the primary key.
FIG. 6 is a diagram showing the data structure of the group table 1013.

Group ID is an item that stores group identification information for identifying a group. Group identification information is an item in which a unique value is set for each group.
Group name is an item that stores the name of the group. Any character string can be set for the group name.
The administrator ID is an item that stores user identification information of a user who has administrator authority in a group. A user with administrator authority can arbitrarily define and set a user who has a predetermined position or authority in a group such as an organization.

The contract table 1014 is a table for storing and managing information (contract information) regarding electronic contracts exchanged between a plurality of users. Note that in the present disclosure, contract information is information that includes information stored in the contract table 1014 and document information stored in the document table 1015 associated with the contract ID of the contract table 1014.
The contract table 1014 is a table that uses the contract ID as a primary key and has columns for contract ID and contract type.
FIG. 7 is a diagram showing the data structure of the contract table 1014.

The contract ID is an item that stores contract identification information for identifying contract information. The contract identification information is an item in which a unique value is set for each contract information.
The contract type is an item that 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 a lease contract for real estate or goods, a nondisclosure agreement, a joint research contract, a contract, an employment contract, and an insurance contract.

The document table 1015 is a table for storing and managing document information in which contract conditions that are the subject of a contract are defined regarding contract information exchanged between a plurality of users. In the present disclosure, a plurality of pieces of document information are stored in association with one piece of contract information.
The document table 1015 is a table having document ID as a primary key and columns of document ID, contract ID, document data, document type, creator ID, and creation date and time.
FIG. 8 is a diagram showing the data structure of the document table 1015.

The document ID is an item that stores document identification information for identifying document information. The document identification information is an item in which a unique value is set for each document information.
The contract ID is an item that stores contract identification information of contract information associated with document information. In the present disclosure, a plurality of pieces of document information are stored in association with one contract ID.
Document data is an item that stores document information (binary or text data) in which contract conditions are defined.
The document type is an item that stores the type of document information (document type information). Specifically, the document type information stores information regarding the type of document information, such as a contract, a blueprint, a template, a specification, an estimate, and a health certificate.
This item stores the creator ID and user identification information for identifying the user who is the creator (first user, second user, etc.) of the document information.
The creation date and time is an item that stores the date and time when the document data was stored in the document table 1015 by the creator.

The confirmation table 1016 is a table that stores and manages information (confirmer information) including the email address of a user who is a confirmer of contract information.
The confirmation table 1016 is a table having columns of document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time.
FIG. 9 is a diagram showing the data structure of the confirmation table 1016.

The document ID is an item that stores document identification information of the contract information to be confirmed by the confirmer.
The confirmation order is an item that stores information regarding the confirmation order when the contract information is confirmed by the confirmer. For example, the contract information stored by the first user is circulated to the confirmers in order of confirmation order, and confirmation is performed.
The confirmer email address is an item that stores the email address of the person who confirmed the contract information. The confirmer's email address does not need to be registered as a user in advance to use the service according to the present disclosure. In other words, the confirmer email address does not need to be included in the user table 1012.
The confirmation flag is an item that stores confirmation identification information for identifying whether or not the confirmation procedure for contract information by the confirmer has been completed. When the confirmation person completes confirmation of the contract information, information indicating that confirmation has been completed, such as a value of True, is stored in the confirmation flag item.
The language data is an item that stores information regarding the confirming person's language (language information).
The access code is an item that stores the access code set for the confirmer.
The date and time is an item that stores the date and time when the contract information confirmation procedure was performed by the confirmer. Specifically, the date and time when the confirmation identification information was stored in the confirmation flag item is stored.

The input item table 1017 is a table that stores and manages information regarding input items (input item information) associated with contract information.
The input item table 1017 is a table having columns of input item ID, document ID, input person ID, input data, input rule, and date and time.
FIG. 10 is a diagram showing the data structure of the input item table 1017.

The input item ID is an item that stores input item identification information for identifying the input item.
The document ID is an item that stores document identification information of contract information with which an input item is associated.
The input person ID is an item that stores the user identification information or email address of the input person who inputs the input data for the input item. For example, the input user ID stores a first user ID, an e-mail address of a user specified by the first user ID, a confirmer e-mail address, and the like.
The input data is an item that stores input data input into an input item by an inputter.
The input rule is an item that stores input rule information regarding input rules for input items. Input rules include data types such as date, datetime, text, and integer, as well as any input items such as the number of characters for strings and regular expressions for strings. Input rule information regarding input rules can be stored.
The date and time is an item that stores the date and time when the input data was input into the input item by the inputter.

<Configuration of 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.

The user registration control unit 1041 performs a process of storing information of users who wish to use the service according to the present disclosure in the user table 1012.
Information stored in the user table 1012 is transmitted to the server 10 by a user opening a web page operated by a service provider from any information processing terminal, inputting information into a predetermined input form, and transmitting the information to the server 10 . The user registration control unit 1041 stores the received information in a new record of the user table 1012, and the user registration is completed. This allows the users stored in the user table 1012 to 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 predetermined examination to restrict whether or not the user can use the service. The user ID may be any character string or number that can identify the user, and may be any character string or number desired by the user, or may be automatically set by the user registration control unit 1041. .

The contract creation unit 1042 executes contract creation processing. Details will be described later.

The contract confirmation unit 1043 executes a contract confirmation process. Details will be described later.

<Configuration of first user terminal 20>
The first user terminal 20 is an information processing device operated by a user who uses the service. The first user terminal 20 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The first user terminal 20 includes a storage section 201, a control section 204, an input device 206, and an output device 208.

<Configuration of storage unit 201 of 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.

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 user with the service according to the present disclosure. Note that the first user ID 2011 includes information such as a session ID temporarily given by the server 10 to identify the user using the first user terminal 20.

The application program 2012 may be stored in advance in the storage unit 201, or may be downloaded from a web server operated by a service provider via a communication IF. Application programs 2012 include applications such as web browser applications. Application program 2012 includes an interpreted programming language such as JavaScript® that is executed on a web browser application stored on first user terminal 20 .

<Configuration of control unit 204 of first user terminal 20>
The control unit 204 of the first user terminal 20 includes 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.

<Configuration of input device 206 of 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.

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

<Configuration of second user terminal 30>
The second user terminal 30 is an information processing device operated by a user who uses the service. The second user terminal 30 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The second user terminal 30 includes a storage section 301, a control section 304, an input device 306, and an output device 308.

<Configuration of storage unit 301 of 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.

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 service according to the present disclosure to the user. Note that the second user ID 3011 includes information such as a session ID temporarily given by the server 10 to identify the user using the second user terminal 30.

The application program 3012 may be stored in advance in the storage unit 301, or may be downloaded from a web server operated by a service provider via a communication IF. Application programs 3012 include applications such as web browser applications. Application program 3012 includes an interpreted programming language, such as JavaScript®, executed on a web browser application stored on second user terminal 30.

<Configuration of control unit 304 of second user terminal 30>
The control unit 304 of the second user terminal 30 includes 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.

<Configuration of input device 306 of 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.

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

<Operation of information processing system 1>
Each process of the information processing system 1 will be explained below.
FIG. 7 is a diagram showing the data structure of the contract table 1014.
FIG. 11 is a flowchart showing the operation of the contract creation process.
FIG. 12 is a flowchart showing the operation of the contract confirmation process.
FIG. 13 is an example of a screen showing the operation of the contract creation process.
FIG. 14 is an example of a screen showing a message notified to the second user terminal 30.
FIG. 15 is an example of a screen presented to the second user in the contract confirmation process.
FIG. 16 is an example of a screen presented to the first user in the contract confirmation process.

<Contract creation process>
The contract creation process is a process in which the first user creates contract information and sends it to the second user. In the present disclosure, it is assumed that the first user is a user who is a creator of contract information, and the second user is a user who is a verifier of contract information. Note that when creating contract information, it is possible to set multiple users as confirmers. Further, in the present disclosure, the second user can also create document information included in contract information.
In the present disclosure, the first user is a user who belongs to a group such as an organization different from the second user.

FIG. 13 is an example of a screen showing the operation of the contract creation process. A screen 50 for creating contract information displayed on the display 2081 of the first user terminal 20 includes a status 510 indicating the current creation status of contract information, and buttons 521, 522, 523 for specifying input items. , a contract information display area 530, document data 531, input items 532, 533, 534, and a send button 540 are displayed.

<Summary of contract creation process>
In the contract creation process, the first user creates contract information, sets the second user who will be the destination of the contract information, sets input items for the contract information, sets input rules for the input items, and the first user This is a series of processes in which input data for input items is received from the user, and contract information is sent to the set second user.

<Details of contract creation process>
In step S101, the contract creation unit 1042 of the server 10 receives input of first contract conditions from the first user. In other words, contract information for conclusion of a contract between the first user and the second user is accepted.
Specifically, the first user operates the input device 206 of the first user terminal 20 and creates contract information including document data related to the contract. The contract information can include document data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). The document data defines contract conditions that are the subject of a contract between the first user and the second user.
The first user operates the input device 206 of the first user terminal 20 and transmits 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 received first user ID 2011 and document data, and creates a new contract information record in the contract table 1014. As a result, contract procedure 1 is drafted. The contract creation unit 1042 of the server 10 converts the contract ID, received first user ID 2011, and document data of the created contract information record into the contract ID, creator ID, and document data of a new record in the document table 1015, respectively. Store in item. That is, document data is stored in association with contract information. As a result, the contract creation unit 1042 of the server 10 stores new contract information in the contract table 1014 and the document table 1015.

In the present disclosure, the first user can include a plurality of document data in the contract information. In this case, the contract creation unit 1042 of the server 10 receives the received first user ID 2011 and a plurality of document data, and creates one new record of contract information in the contract table 1014. The contract creation unit 1042 of the server 10 uses the contract ID of the created one contract information record, the received first user ID 2011, and the plurality of document data to create contract IDs of a plurality of new records in the document table 1015, respectively. It is stored in the user ID and document data items. That is, a plurality of document data are stored in association with one piece of contract information.

The first user may include contract type information in the contract information transmitted to the server 10. The contract confirmation unit 1043 of the server 10 may be configured to accept a contract type of one contract procedure.
For example, the first user selects the type of contract information that he/she wishes to conclude with the second user from a plurality of contract type information, and transmits the selected contract information to the server 10 . The contract creation unit 1042 of the server 10 also includes the file name of the document data received from the first user, the wording of the contract conditions included in the document data, the title of the contract document included in the document data (contract name such as non-disclosure agreement, etc.). ), the contract type information may be specified based on the clause name of the contract document included in the document data.
The contract creation unit 1042 of the server 10 stores the received or specified contract type information in the contract type field of the newly created contract information record.

The first user may include document type information in the contract information transmitted to the server 10. For example, the first user selects the type of document information of the document data to be included in the contract information from a plurality of pieces of document type information, and transmits the selected document information type to the server 10 . The contract creation unit 1042 of the server 10 also includes the file name of the document data received from the first user, the wording of the contract conditions included in the document data, the title of the contract document included in the document data (contract name such as non-disclosure agreement, etc.). ), the document type information may be specified based on the clause name of the contract document included in the document data.
The contract creation unit 1042 of the server 10 stores the received or specified document type information in the document type field of the same record as the target document data in the document table 1015.
Note that if the contract information includes a plurality of document data, the contract creation unit 1042 of the server 10 may be configured to store document type information for each document data in the document type field of the document table 1015. .

The first document information having the first document type assigned to the first user may be received according to the contract type of the first contract procedure.
Specifically, when the first user selects the type of contract information that he/she wishes to conclude with the second user from a plurality of pieces of contract type information, the first The document type information of the document data that the user can include in the contract information may be limited.

For example, when the contract type of one contract procedure is a lease contract for real estate or goods, a configuration may be adopted in which document data regarding the lease contract for real estate or goods is accepted.
Specifically, if the first user selects "lease contract 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 is "lease contract for real estate or goods." The contract information may be configured such that the contract information is limited to "lease contract" and other document type information cannot be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "lease contract for real estate or goods," it stops the process and prevents the process from proceeding to step S102. You can also do it. In this case, a message may be presented to the first user urging the first user to include document data whose document type information is "lease contract for real estate or goods" in the contract information.

For example, if the contract type of one contract procedure is a contract in which an individual contract for a basic contract is associated with the basic contract, document data related to the basic contract may be accepted.
Specifically, if the first user selects "a contract in which an individual contract for a basic contract is associated with the basic contract" as the contract type information, the document data that the first user can include in the contract information. The type information may be limited to "basic contract" and other document type information may not be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "basic contract," it may stop the process and not proceed to step S102. In this case, a message may be presented to the first user urging the first user to include document data whose document type information is "basic contract" in the contract information.

For example, if the contract type of the first contract procedure is an order contract for construction work or the like, the configuration may be such that document data regarding the contract is accepted.
Specifically, if the first user selects "order 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 is "contract contract". , and other document type information may not be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "contract contract," the contract creation unit 1042 may stop the process and not proceed to step S102. . In this case, a message may be presented to the first user urging the first user to include document data whose document type information is "contract form" in the contract information.

For example, when the contract type of the first contract procedure is an employment contract, a configuration may be adopted in which document data regarding the employment contract is accepted.
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 is limited to "employment contract", A configuration may be adopted in which other document type information cannot be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "employment contract," it may stop the process and not proceed to step S102. . In this case, a message may be presented to the first user urging the first user to include document data whose document type information is "employment contract" in the contract information.

For example, when the contract type of the first contract procedure is an insurance contract, a configuration may be adopted in which document data related to application forms and contracts are accepted.
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 is limited to "application form, contract". However, other document type information may not be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "application form, contract", it stops the process and does not proceed to step S102. Also good. In this case, a message may be presented to the first user urging the first user to include document data whose document type information is "application form, contract" in the contract information.

Document data 531 stored in document table 1015 is displayed on screen 50 for creating contract information.

In step S102, the first user operates the input device 206 of the first user terminal 20, etc. to select and specify a user who will be the confirmer (receiver) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies the second user as the recipient.
The first user operates the input device 206 of the first user terminal 20 and inputs the e-mail address of the second user, and transmits the e-mail address 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 confirmer email address and document ID fields of the confirmation table 1016, respectively, and stores the document information and the document ID in the confirmation table 1016. It is stored in association with the second user's email address. Note that the first user may set the second user's language and access code, and store them in association with the second user's email address.
At this time, a value of 1 is stored in the confirmation order item of the confirmation table 1016. In step S102, the first user may be able to select and set a plurality of users to be confirmers. In this case, the value of the confirmation order item of the user who becomes the second user is incremented by one and stored in accordance with the selection order. This sets the order of circulation for the second user in the contract confirmation process, which will be described later. Note that setting the circulation order is not essential.

In step S103, the first user operates the input device 206 of the first user terminal 20 and sets input items for the document information.
Specifically, the first user operates the input device 206 of the first user terminal 20 and sets a plurality of input items for the document information created and stored in step S101. Any input items can be set, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a check box 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 transmits a request to add an input item to the server 10. Upon receiving the request, the contract creation unit 1042 of the server 10 stores the document ID of the document information as the document ID of a new record in the input item table 1017. As a result, the newly added input item information is stored in association with the contract information. Note that the first user can store a plurality of pieces of input item information in association with document information.

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

In step S105, the contract creation unit 1042 of the server 10 receives input data for a plurality of input items input 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 or the like. For example, the first user may input input data of a number for managing contract information such as a reference number for a group to which the first user belongs to an input item set with a management number. The first user may input input data of the contract conclusion date of the contract information into the input item in which the contract conclusion date is set. When the first user completes inputting the input data to the input items, the first user transmits the input item ID and input data for each input item to the server 10.
The contract creation unit 1042 of the server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of the server 10 stores the received input data in the input data item of the input item information of the input item table 1017 specified by the received input item ID. As a result, the input data input by the first user is stored in the input item table 1017.

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 based on the contract information.
Specifically, the first user transmits the contract information by operating the input device 206 of the first user terminal 20 and pressing the send button 540 displayed on the screen 50 for creating contract information. Send the request to the server 10. Upon receiving the request, the contract creation unit 1042 of the server 10 sends a message to the second user notifying that the first user has sent a request to confirm the contract information. For example, the contract creation unit 1042 of the server 10 sends a message to the second user's e-mail address, using communication means such as e-mail, to notify that the first user has sent a request to confirm the contract information.
The message notified to the second user includes URL (Uniform Resource Locator) information including a contract ID for specifying contract information. The URL may directly include the contract ID, or may include information such as a character string obtained by arbitrarily encrypting the contract ID, or other information such as a character string that allows the contract ID to be identified by referring to a table (not shown). good. Further, the URL may include information for identifying the second user. For example, if the second user has not registered for the service according to the present disclosure, it is necessary to include information for identifying the second user in the URL.

When the first user sets an access code for the second user, the first user separately conveys the access code to the second user by means such as e-mail. As a result, even if a third party obtains the message to be notified to the second user, the third party cannot execute the contract confirmation process unless the third party obtains the access code.

FIG. 14 is an example of a screen showing 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 of a URL 62 including a contract ID for specifying contract information.

<Modified example>
When the first user selects and sets a plurality of confirmers in step S102, the first user may be configured to be able to independently set different input item information in step S103 for each of the plurality of confirmers. do not have. For example, when the first user sets two users, the second user and the third user, as the second user, the input items for the contract start date and contract end date are set for the second user, and the contract An input item for the conclusion date may be set for the third user. In this case, in the contract confirmation process described later, the second user can enter input data for the input fields of the contract start date and contract end date, but input data for the input field of the contract conclusion date. Can not do it. On the other hand, the third user cannot input data into the input fields of the contract start date and the contract end date, but can input data into the input field of the contract conclusion date. A configuration may be adopted in which a plurality of confirmers can be selected and set in duplicate for one piece of input item information.

Input items 532, 533, and 534 are drawn as drawing objects on the screen 50 for creating contract information. In the input items 532 and 533, the user identification information "USER-B" of the user who has selected and set input of the input item as the assignment, and the item "Text" as the type of the input item are drawn. In the input item 534 regarding stamping, the user identification information "USER-C" of the user who has selected and set the stamping as the assignment, and "seal" as the input item type are drawn.

<Contract confirmation process>
The contract confirmation process is a process in which the second user confirms the content of the contract information received from the first user. Note that when the second user includes document information in which new contract conditions are defined in the contract information, the same process is performed for the first user to confirm the document information.

<Summary of contract confirmation process>
The contract confirmation process accepts access from the second user, presents a screen displaying contract information to the second user, receives input data for input items from the second user, and receives the contract information from the second user. This is a series of processes for accepting confirmation data.

<Details of contract confirmation process>
In step S301, the second user selects the URL written in the received message by operating the input device 306 of the second user terminal 30, and specifies the URL using the browser application of the second user terminal 30. You can open the web page that was created. Thereby, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process.
The contract confirmation unit 1043 of the server 10 searches the contract ID item in the contract table 1014 and the document table 1015 based on the contract ID included in the received request, and acquires contract information and document information included in the contract information.
The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1016 based on the document ID included in the obtained document information, and obtains the second user information. The contract confirmation unit 1043 of the server 10 searches the document ID item in the input item table 1017 based on the document ID included in the acquired document information, and acquires the input item information associated with the document information.

In step S302, the contract confirmation 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 may be identified based on the identification information for identifying the second user included in the URL. good. If the second user has not registered for the service according to the present disclosure, it is necessary to identify the second user from the URL. For example, the URL may include the second user's email address, user ID, etc. as information for identifying the second user.

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

In step S303, the contract conditions 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 in which contract conditions included in the contract information are defined. The second user confirms the contract information displayed on the display 3081 of the second user terminal 30.

FIG. 15 is an example of a screen showing the operation of the contract confirmation process. A screen 70 for confirming contract information displayed on the display 3081 of the second user terminal 30 includes a status 710 indicating the current contract information creation status, a contract information display area 730, document data 731, and input items 732. , 733, 734, 735, 736, an agree button 740, an add document button 750, and a document switch button 760 are displayed.

In step S304, the contract confirmation unit 1043 of the server 10 receives input of contract conditions from the second user with respect to the contract conditions presented in step S303.
The contract confirmation unit 1043 of the server 10 receives input for one or more input items of contract information. Further, the contract confirmation unit 1043 of the server 10 can newly receive document information in which contract conditions are defined.
Specifically, the second user operates the input device 306 of the second user terminal 30 and inputs input data into input items 732, 733, 734, and 735 set in the contract information. Note that in the present disclosure, since input by the second user is not assigned to the input item 736, it is visually discernably displayed that the second user cannot input input data.

In addition, the second user operates the input device 306 of the second user terminal 30 and presses the add document button 750 to add document information (second document information) in which contract conditions are specified to new contract information. can be included in
Similar to step S101 of the contract creation process, the second user operates the input device 306 of the second user terminal 30 and creates contract information including document data related to the contract. The contract information can include document data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). The document data defines contract conditions that are the subject of a contract between the first user and the second user.
The contract confirmation unit 1043 of the server 10 receives the first document information in which the first contract conditions are defined, received in step S101 of the contract creation process, and the second document information in which the second contract conditions are defined, received in step S304. are stored in association with each other as a contract condition regarding the contract procedure 1.
Specifically, the second user operates the input device 306 of the second user terminal 30 and transmits 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 received second user ID 3011 and document data, and creates the contract ID, the received second user ID 3011, and document data received in step S301 as a new record contract in the document table 1015, respectively. It is stored in the ID, creator ID, and document data items. That is, document data is stored in association with contract information. Thereby, the contract creation unit 1042 of the server 10 stores in the document table 1015 the second document information in which the new contract conditions selected by the second user are defined.

The contract creation unit 1042 of the server 10 acquires the first user's email address (first email address) by searching the user ID item in the user table 1012 based on the first user's user ID. The contract creation unit 1042 of the server 10 stores the document ID and first email address of the second document information in the document ID and confirmer email address fields of the confirmation table 1016, respectively. At this time, a value of False is stored in the confirmation flag item. As a result, the second document information newly stored by the second user is stored as information that has not been confirmed by the first user. Note that the second user may 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 value of the confirmation order item of the user who is the confirmer is incremented by one and stored in the confirmation order item of the confirmation table 1016. This sets the order of circulation of confirmers in the contract confirmation process. The circulation order may be incremented for each contract information, or may be incremented for each document information. Note that setting the circulation order is not essential.

In the present disclosure, the second user can include a plurality of document data in the contract information. In this case, the contract creation unit 1042 of the server 10 converts the contract ID, the received second user ID 3011, and the plurality of document data into the contract ID, creator ID, and document data items of a plurality of new records in the document table 1015, respectively. to be memorized. That is, a plurality of document data are stored in association with one piece of contract information.

The second user may include document type information in the document information transmitted to the server 10. For example, the second user selects the document information type of the document data to be included in the contract information from a plurality of document type information, and transmits the selected document information type to the server 10. The contract creation unit 1042 of the server 10 also includes the file name of the document data received from the second user, the wording of the contract conditions included in the document data, the title of the contract document included in the document data (contract name such as non-disclosure agreement, etc.). ), the document type information may be specified based on the clause name of the contract document included in the document data.
The contract creation unit 1042 of the server 10 stores the received or specified document type information in the document type field of the same record as the target document data in the document table 1015.
Note that if the contract information includes a plurality of document data, the contract creation unit 1042 of the server 10 may be configured to store document type information for each document data in the document type field of the document table 1015. .

A configuration may also be adopted in which second document information having a second document type assigned to the second user is received according to the contract type of the first contract procedure.
Specifically, when the first user selects the type of contract information that he/she wishes to conclude with the second user from a plurality of pieces of contract type information, the second user The document type information of the document data that the user can include in the contract information may be limited.

For example, when the contract type of the first contract procedure is a real estate or goods rental contract, a configuration may be adopted in which document data regarding an identity verification document to be presented to the first user is accepted.
Specifically, if the first user selects "lease contract 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 is "identity verification document". , and other document type information may not be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "identity verification document," it may stop the process and disable the document information from being stored. . In this case, a message may be presented to the second user to urge the second user to include document data whose document type information is "identity verification document" in the contract information.

For example, if the contract type of one contract procedure is a contract in which an individual contract for a basic contract is associated with the basic contract, document data related to the individual contract may be accepted.
Specifically, if the first user selects "a contract in which an individual contract for a basic contract is associated with the basic contract" as the contract type information, the second user can select the document data that can be included in the contract information. The type information may be limited to "individual contract" and other document type information may not be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "individual contract," it may stop the process and disable the document information from being stored. In this case, a message may be presented to the second user urging the second user to include document data whose document type information is "individual contract" in the contract information.

For example, when the contract type of the first contract procedure is an order contract for construction work, etc., the configuration may be such that document data regarding specifications and estimates are accepted.
Specifically, if the first user selects "order 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 is "specifications, estimates, etc." It is also possible to adopt a configuration in which the contract information is limited to "document type" and other document type information cannot be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "specifications, quotation," it stops processing and prevents the document information from being stored. Also good. In this case, a message may be presented to the second user urging the second user to include document data whose document type information is "specifications, quotation" in the contract information.

For example, when the contract type of the first contract procedure is an employment contract, it may be configured to accept document data regarding a certificate of identity, confirmation of residence status, and other certificates of qualifications, etc.
Specifically, if the first user selects "employment contract" as the contract type information, the document type information of the document data that the second user can include in the contract information is "identity guarantee, residence status confirmation, etc." The contract information may be configured such that the contract information is limited to "certificates of qualifications, etc." and other document types cannot be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "certificate of identity, confirmation of residence status, other certificate of qualifications, etc.", the contract creation unit 1042 of the server 10 stops processing and The information may not be memorized. In this case, a message may be presented to the second user urging the second user to include document data whose document type information is "certificate of identity, confirmation of resident status, other certificate of qualifications, etc." in the contract information.

For example, when the contract type of the first contract procedure is an insurance contract, a configuration may be adopted in which document data regarding a health certificate is accepted.
Specifically, when 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 is limited to "health certificate", A configuration may be adopted in which other document type information cannot be included in the contract information. If the contract creation unit 1042 of the server 10 determines that the document type information specified by the received document data is other than "health certificate," it may stop the process and disable the document information from being stored. . In this case, a message may be presented to the second user urging the second user to include document data whose document type information is "health certificate" in the contract information.

Note that the document information (first document information) stored by the first user in step S101 of the document creation process and the document information (second document information) stored by the second user in step S304 of the document confirmation process are , 1 may be document information having different document types in relation to the contract procedures.

The screen for creating contract information displayed on the display 3081 of the second user terminal 30 is the same as the screen example showing the operation of the contract creation process shown in FIG. 13, so a description thereof will be omitted.

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 step S103 in the document creation process, so the explanation will be omitted.
The second user can set input rules for each input item to be added, similar to step S104 in the document creation process. The detailed process is the same as step S104 in the document creation process, so the explanation will be omitted.
The second user can receive input data for a plurality of input items input by the second user, similarly to step S105 in the document creation process. The detailed process is the same as step S105 in the document creation process, so the explanation will be omitted.

In step S305, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to the contract conclusion 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, and when agreeing or consenting to the contents, operates the input device 306 of the second user terminal 30, etc. By pressing the consent button 740 displayed on the screen 70 for confirming contract information, a request including the document ID, information for identifying the second user, and input data for each input item input in step S304 is sent to the server. 10. The information identifying the second user may be the second user ID 3011.
Specifically, the contract confirmation unit 1043 of the server 10 stores information indicating that the second user has confirmed the contract information based on the received request. The contract confirmation unit 1043 of the server 10 searches the confirmation table 1016 based on the received contract ID and information specifying the second user, and stores a value of True in the confirmation flag field of the record. For example, if the information specifying the second user is an email address, the document ID and confirmer email address fields of the confirmation table 1016 are searched, and a value of True is stored in the confirmation flag field of the record. If the information that identifies the second user is user identification information, the document ID and confirmation information in the confirmation table 1016 are determined based on the email address of the second user identified by searching the user ID item in the user table 1012. The user's email address field is searched, and a value of True is stored in the confirmation flag field of the record.
Note that the contract confirmation unit 1043 of the server 10 searches the confirmation table 1016 for all document IDs associated with the received contract ID in the document table 1015 based on the information specifying the second user, and confirms the record. A value of True may be stored in the flag item. That is, a value of True is stored in the confirmation flag item of all records in which the second user's email address is stored in the confirmer email address of the confirmation table 1016 specified based on the contract ID via the document ID. Note that the contract confirmation unit 1043 of the server 10 receives the operation of the document switching button 760 by the second user, and sets the confirmation flag item to True only for the document information actually presented to the second user. The value may be memorized.
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1017 specified by the input item ID associated with the input data. Thereby, in step S304, the input data input by the second user is stored as input item information in the input item table 1017.

In step S306, the contract confirmation unit 1043 of the server 10 uses the first document information in which the first contract conditions received in step S101 of the contract creation process and the second contract received in step S304 of the contract confirmation process. Information indicating that the second document information with defined conditions has been approved by at least one of the first user and the second user is stored.

Specifically, when the contract confirmation process has been executed by all users, the contract confirmation unit 1043 of the server 10 sends a message to the first user and the second user notifying them that the contract confirmation process has been completed. . For example, the contract creation unit 1042 of the server 10 sends a message to the first user's e-mail address to notify that the second user has completed confirmation of the contract information using communication means such as e-mail. The message notified to the first user includes URL information including a contract ID for specifying contract information. Specifically, the contract confirmation unit 1043 of the server 10 stores a value of True in the confirmation flag of the confirmation information associated with all the document information included in the contract information stored in the confirmation table 1016. , it is determined that the contract confirmation process has been executed by all users.
If multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 sends a message to notify users other than the user who last executed the contract confirmation process that the contract confirmation process has been completed. You may also send. Thereby, the user who is the confirmer can also receive notification that execution of the contract confirmation process has been completed by all users.
Additionally, the contract confirmation unit 1043 of the server 10 sends a message notifying that the contract confirmation process has been completed to a user who has authority equivalent to an administrator in the group to which the first user or the plurality of confirmers belong. Also good. Thereby, the administrator of the group to which the first user or the plurality of confirmers belong can receive notification that execution of the contract confirmation process has been completed. The contract confirmation unit 1043 of the server 10 acquires 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. The contract confirmation unit 1043 of the server 10 searches the group ID item of the group table 1013 based on the acquired group ID item, acquires the administrator ID item, and, based on the administrator ID, identifies the person who corresponds to the administrator. An authorized user is identified by searching the user ID in the user table 1012, and a message is sent to notify that the contract confirmation process has been completed.

The contract confirmation unit 1043 of the server 10 searches for document information included in the contract information, and if there is document information for which contract confirmation processing has not been performed, the contract confirmation unit 1043 sends the document to the associated confirmer email address in the confirmation table 1016. Send a message asking you to confirm your information.
Specifically, the contract confirmation unit 1043 of the server 10 searches the document table 1015 for the contract ID item based on the contract ID, and obtains the document ID item. The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1016 based on the document ID, and obtains the confirmer email address and confirmation flag items. The contract confirmation unit 1043 of the server 10 identifies, among the acquired confirmer email addresses, the confirmer email addresses whose confirmation flags have a value of False. That is, the contract confirmation unit 1043 of the server 10 identifies and acquires the confirmer email address of the user who has not confirmed the document information.
For example, if the second user newly stores the second document information in step S304, the contract confirmation process for the second document information has not been executed by the first user, so the second document information cannot be confirmed. The first email address of the first user associated with the second document information is specified as the email address of the user who has not done so.

The contract confirmation unit 1043 of the server 10 sends a message to the first user notifying that the second user has sent a request to confirm the contract information. For example, the contract confirmation unit 1043 of the server 10 sends a message to the first user's e-mail address to notify that the second user has sent a request to confirm the contract information, using communication means such as e-mail.
The message notified to the first user includes URL (Uniform Resource Locator) information including a contract ID for specifying contract information. The URL may directly include the contract ID, or may include information such as a character string obtained by arbitrarily encrypting the contract ID, or other information such as a character string that allows the contract ID to be identified by referring to a table (not shown). good.

If the second user sets an access code for the first user, the second user separately conveys the access code to the first user by means such as e-mail. As a result, even if a third party obtains the message to be notified to the first user, the third party cannot execute the contract confirmation process unless the third party obtains the access code.

The screen showing the message to be notified to the first user terminal 20 is similar to the screen example showing the message to be notified to the second user terminal 30 in FIG. The message screen 60 displayed on the display 2081 of the first user terminal 20 includes a message 61 and information of a URL 62 including a contract ID for specifying contract information.

<Contract confirmation process (by first user)>
The contract confirmation process (by the first user) executed by the first user will be described below. The only difference is that each step S301 to S306 of the contract confirmation process (by the first user) is executed by the first user instead of the second user, and the processing content is the same as each step S301 of the contract confirmation process. The explanation that overlaps with S306 will be omitted.

In step S301, the first user selects the URL written in the received message by operating the input device 206 of the first user terminal 20, and specifies the URL using the browser application of the first user terminal 20. You can open the web page that was created. Thereby, the first user terminal 20 transmits a request to the server 10 to execute the contract confirmation process.
The contract confirmation unit 1043 of the server 10 searches the contract ID item in the contract table 1014 and the document table 1015 based on the contract ID included in the received request, and acquires contract information and document information included in the contract information.
The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1016 based on the document ID included in the obtained document information, and obtains the first user information. The contract confirmation unit 1043 of the server 10 searches the document ID item in the input item table 1017 based on the document ID included in the acquired document information, and acquires the input item information associated with the document information.

In step S302, the contract confirmation 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 may be identified based on the identification information for identifying the first user included in the URL. good.

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

In step S303, the contract conditions 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 document information in which the contract conditions included in the contract information are defined. The first user confirms the contract information displayed on the display 2081 of the first user terminal 20.

FIG. 16 is an example screen showing the operation of the contract confirmation process. A screen 80 for confirming contract information displayed on the display 2081 of the first user terminal 20 includes a status 810 indicating the current creation status of contract information, a contract information display area 830, document data 831, and an consent button 840. , an add document button 850, and a document switch button 860 are displayed.
The first user operates the input device 206 of the first user terminal 20 and presses the document switching button 860 to selectively switch the plurality of document information associated with the contract information. It can be displayed on the display 2081 of the terminal 20. For example, the first user can display the document information of the "lease contract" in the contract information display area 830 by selecting "lease contract." The first user can display the document information of the "identity verification document" in the contract information display area 830 by selecting "identity verification document."
In addition, on the screen 80 for confirming the contract information, you, as the confirmer, specify the document information for which the value of True is not stored in the confirmation flag, and set the document information as the default document information on the screen 80. It is also possible to have a configuration in which the information is displayed on the screen. In other words, the first user may present unconfirmed document information to the first user as default document information.
Thereby, the first user can preferentially confirm document information that the first user has not yet confirmed, and can conveniently execute the document confirmation process.

In step S304, the contract confirmation unit 1043 of the server 10 receives input of contract conditions from the first user for the contract conditions presented in step S303.
The contract confirmation unit 1043 of the server 10 receives input for one or more input items of contract information. Further, the contract confirmation unit 1043 of the server 10 can newly receive document information in which contract conditions are defined.

In step S305, the contract confirmation unit 1043 of the server 10 determines that the second contract conditions are defined from the first user with respect to the second document information in which the second contract conditions are defined and presented to the first user in step S303. The first document information in which the first contract conditions are defined and the second document information in which the second contract conditions are defined are approved by the first user in accordance with the input operation for the second document information that has been performed. Store information indicating.
Specifically, the contract confirmation unit 1043 of the server 10 receives an instruction from the first user to agree to conclude the contract in response to a confirmation request requested by the second user.
The first user confirms the contract information and input data displayed on the display 2081 of the first user terminal 20, and if he or she agrees to the contents, operates the input device 206 of the first user terminal 20, etc. By pressing the consent button 840 displayed on the screen 80 for confirming contract information, a request including the document ID, information for identifying the first user, and input data for each input item input in step S304 is sent to the server. 10. The information identifying the first user may be the first user ID 2011.
Specifically, the contract confirmation unit 1043 of the server 10 stores information indicating that the first user has confirmed the contract information based on the received request. The contract confirmation unit 1043 of the server 10 searches the confirmation table 1016 based on the received document ID and information specifying the first user, and stores a value of True in the confirmation flag field of the record. For example, if the information specifying the first user is an email address, the document ID and confirmer email address fields of the confirmation table 1016 are searched, and a value of True is stored in the confirmation flag field of the record. If the information identifying the first user is user identification information, the document ID and confirmation information in the confirmation table 1016 are determined based on the e-mail address of the first user identified by searching the user ID item in the user table 1012. The user's email address field is searched, and a value of True is stored in the confirmation flag field of the record.
For example, in the confirmation table 1016, a value of True is stored in the document ID of the second document information and the confirmation flag item of the record in which the first user is stored as the confirmer email address. As a result, it is stored that the second document information has been confirmed by the first user.
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1017 specified by the input item ID associated with the input data. Thereby, in step S304, the input data input by the first user is stored as input item information in the input item table 1017.

The contract confirmation unit 1043 of the server 10 receives the first document information that defines the first contract conditions received in step S101 of the contract creation process, and the second document information that defines the second contract conditions received in step S304 of the contract confirmation process. The information indicating that the second document information has been approved by the first user and the second user is stored.

<Electronic signature processing>
Step S305 may include electronic signature processing. The contract confirmation unit 1043 of the server 10 adds an electronic signature to the first contract condition and the second contract condition and stores them in response to the first user's input operation for the second contract condition.
Specifically, the contract confirmation unit 1043 of the server 10 attaches an electronic signature to the first document information in which the first contract conditions are defined and the second document information in which the second contract conditions are defined based on the received request. and memorize it. The contract confirmation unit 1043 of the server 10 searches the contract ID item in the contract table 1014 and the document table 1015 based on the contract ID, and obtains contract information and document information included in the contract information.
The contract confirmation unit 1043 of the server 10 adds an electronic signature to the acquired document information and stores it in the contract data item of the document table 1015. The contract confirmation unit 1043 of the server 10 may update (overwrite) the document information to which the electronic signature has been attached, or may store the document information before the electronic signature has been attached in a separate storage device (not shown). .
The contract confirmation unit 1043 of the server 10 includes the document ID, the first user's email address, the second user's email address, approval date and time, confirmation date and time, authentication method of approval date and time, authentication method of confirmation date and time, and input items in the electronic signature. Any information such as the value of input data for each user, consent (approval) of the first user and second user, and a time stamp may be included.
As a result, the first user agrees to an electronic contract that is defined by multiple contract conditions of the first contract conditions and the second contract conditions. 2 contract conditions are stored as an electronic signature in the predetermined first document information and second document information. It is possible to prevent impersonation or falsification of contract terms by a third party.

<Modified example>
In step S304 of the contract confirmation process, the first document information in which the first contract conditions received in step S101 of the contract creation process are specified or the second document information in which the second contract conditions received in step S304 are specified. On the other hand, a configuration may be adopted in which a modification instruction is received from the first user or the second user. The contract confirmation unit 1043 of the server 10 may be configured to add and store an electronic signature to the first contract condition or the second contract condition that is the subject of the modification instruction, according to the received modification instruction.
Specifically, the second user can operate the input device 306 of the second user terminal 30 to modify (edit) the first document information in which the first contract conditions are defined, and store it in the document table 1015. It may also be used as a configuration. At this time, the contract confirmation unit 1043 of the server 10 may be configured to add an electronic signature including information indicating that the second user has modified the first document information and store it in the document table 1015.
Similarly, the first user may be configured to operate the input device 206 of the first user terminal 20, modify the second document information in which the second contract conditions are defined, and store it in the document table 1015. . At this time, the contract confirmation unit 1043 of the server 10 may be configured to add an electronic signature including information indicating that the second document information has been modified by the first user and store it in the document table 1015.
Note that a configuration may be adopted in which the second user can modify the second document information in which the second contract conditions are defined and store it in the document table 1015. Similarly, a configuration may be adopted in which the first user can modify the first document information in which the first contract conditions are defined and store it in the document table 1015.
As a result, the electronic signature is stored in the first contract condition and the second contract condition that have been modified in response to the instruction to modify the contract condition by the first user or the second user. It is possible to prevent impersonation or falsification of contract terms by a third party.

<Basic hardware configuration of the computer>
FIG. 17 is a block diagram showing the basic hardware configuration of the computer 90. The computer 90 includes at least a processor 901, a main storage device 902, an auxiliary storage device 903, and a communication IF 991 (interface). These are electrically connected to each other by a communication bus 921.

The processor 901 is hardware for executing an instruction set written in a program. The processor 901 includes an arithmetic unit, registers, peripheral circuits, and the like.

The main storage device 902 is for temporarily storing programs, data processed by the programs, and the like. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

The auxiliary storage device 903 is a storage device for storing data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, semiconductor memory, and the like.

The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using a wired or wireless communication standard.
The network is composed of various mobile communication systems constructed using the Internet, LAN, wireless base stations, and the like. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), a wireless network (for example, Wi-Fi (registered trademark)) that can be connected to the Internet through a predetermined access point, and the like. When connecting wirelessly, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), and the like. In the case of a wired connection, the network includes a network that is directly connected using a USB (Universal Serial Bus) cable or the like.

Note that the computers 90 can be virtually realized by distributing all or part of each hardware configuration to a plurality of computers 90 and interconnecting them via a network. In this way, the concept of the computer 90 includes not only the computer 90 housed in a single housing or case, but also a virtualized computer system.

<Basic functional configuration of computer 90>
The functional configuration of the computer realized by the basic hardware configuration of the computer 90 (FIG. 17) will be described. The computer includes at least functional units of a control section, a storage section, and a communication section.

Note that the functional units included in the computer 90 can also be implemented by distributing all or part of each functional unit to a plurality of computers 90 interconnected via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

The control unit is realized by the processor 901 reading various programs stored in the auxiliary storage device 903, loading them into the main storage device 902, and executing processing according to the programs. The control unit can implement a functional unit that performs various information processing depending on the type of program. Thereby, the computer is realized as an information processing device that performs information processing.

The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Further, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to the program. Further, the control unit can cause the processor 901 to execute processing for adding, updating, and deleting data stored in the storage unit according to various programs.

A database refers to a relational database, which is used to manage a data set called a master, which is a tabular table whose structure is defined by rows and columns, in relation to each other. In a database, a table is called a table or a master, a table column is called a column, and a table row is called a record. In a relational database, you can set and associate relationships between tables and masters.
Usually, each table and each master is set with a column that serves as a primary key to uniquely identify a record, but it is not essential to set a primary key on a column. The control unit can cause the processor 901 to add, delete, or update records to a specific table or master stored in the storage unit according to various programs.

Note that the database and master in the present disclosure may include any data structure (list, dictionary, associative array, object, etc.) in which information is structurally defined. Data structures include data that can be considered as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

The communication unit is realized by a communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a 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 execute information processing on the received information according to various programs. Further, the communication unit can transmit information output from the control unit to another computer 90.

<Additional notes>
The matters explained in each of the above embodiments are additionally described below.

(Additional note 1)
A program, comprising a processor and a storage unit, for causing a computer to execute electronic contract procedures between a plurality of users, the program receiving input of first contract conditions from a first user to the processor. a first reception step (S101); a first presentation step (S303) of presenting the first contract conditions received in the first reception step to the second user; In contrast, a second reception step (S304) receives input of second contract conditions from the second user, the first contract conditions received in the first reception step, and the second contract conditions received in the second reception step. a storage step (S304) of associating and storing these as contract conditions related to one contract procedure; the first contract conditions received in the first reception step; and the second contract conditions received in the second reception step; A program for executing an approval step (S305) of storing information indicating approval by at least one of the first user and the second user.
As a result, based on the document information that specifies the contract conditions that are the subject of the contract prepared by users related to multiple contract parties, electronic contracts can be created as one contract that is defined by multiple contract conditions. can be concluded.

(Additional note 3)
The program according to supplementary note 2, wherein the first document information and the second document information are document information having different document types related to the contract procedure 1.
Thereby, an electronic contract can be concluded as a single contract based on documents related to a plurality of contracts prepared by users of a plurality of contract parties.

(Additional note 4)
The first reception step is a step of receiving first document information having the first document type assigned to the first user according to the contract type of the contract procedure of 1. The program according to any one of appendices 1 to 3, which is a step of receiving second document information having a second document type assigned to a second user according to a contract type of a contract procedure.
As a result, users of multiple parties to a contract can conclude one electronic contract as a single contract by preparing document types assigned according to the contract type of the contract procedure. The user can appropriately input necessary document information.

(Appendix 6)
The first reception step is a step in which the first document information regarding the real estate or goods lease contract is received when the contract type of the first contract procedure is a real estate or goods lease contract. The program according to any one of Supplementary Notes 1 to 5, which is a step of accepting an identification document to be presented to a first user when the contract type of the contract procedure is a rental contract for real estate or goods.
As a result, when a user with multiple contract parties concludes a rental contract for real estate or goods, the contract conditions that are covered by the contract prepared by each of the multiple contract parties can be specified without complicated communication between the contract parties. Based on the document information provided, an electronic contract can be concluded as one contract defined by multiple contract conditions.

(Appendix 8)
The program causes the processor to execute a second presentation step (S303) of presenting the second contract terms received in the second reception step to the first user, and the approval step includes In response to an input operation from the first user to the second contract terms presented to the second contract terms, it is determined that the first contract terms and the second contract terms have been approved by the first user. 8. The program according to any one of Supplementary Notes 1 to 7, which is a step of storing information shown.
Thereby, the first user can agree to conclude the contract after confirming the second contract conditions input by the second user. It is possible to avoid concluding a contract without the first user confirming the second contract conditions input by the second user.

(Appendix 9)
The program according to appendix 8, wherein the second presentation step is a step of presenting the second contract conditions as default document information to the first user.
Thereby, the first user can preferentially confirm document information that the first user has not yet confirmed, and can conveniently execute the document confirmation process.

(Appendix 10)
The program includes a signing step (S305) in which the processor adds and stores an electronic signature to the first contract condition and the second contract condition in response to the input operation for the second contract condition from the first user in the approval step; The program according to supplementary note 8 or 9, which executes.
As a result, the first user agrees to an electronic contract that is defined by multiple contract conditions of the first contract conditions and the second contract conditions. 2. It will be stored as an electronic signature in the contract terms. It is possible to prevent impersonation or falsification of contract terms by a third party.

(Appendix 11)
A modification step (S304) in which the program causes the processor to receive a modification instruction from the first user or the second user for the first contract condition received in the first reception step or the second contract condition received in the second reception step. and a modification signature step (S305) of adding and storing an electronic signature to the first contract condition or the second contract condition that is the subject of the modification instruction in accordance with the modification instruction received in the modification step. The program according to any one of 10 to 10.
As a result, the first user or the second user can flexibly modify the first contract terms or the second contract terms, and the revised first contract terms and conditions and The electronic signature is stored in the second contract condition. It is possible to prevent impersonation or falsification of contract terms by a third party.

(Appendix 12)
An information processing device comprising a processor and a storage unit, the information processing device causing the processor to execute a program according to any one of Supplementary Notes 1 to 11.
As a result, based on the document information that specifies the contract conditions that are the subject of the contract prepared by users related to multiple contract parties, electronic contracts can be created as one contract that is defined by multiple contract conditions. can be concluded.

(Appendix 13)
An information processing system including an information processing device including a processor and a storage unit, the information processing system causing the processor to execute a program according to any one of appendices 1 to 11.
As a result, based on the document information that specifies the contract conditions that are the subject of the contract prepared by users related to multiple contract parties, electronic contracts can be created as one contract that is defined by multiple contract conditions. can be concluded.

(Appendix 14)
An information processing method executed by a computer including a processor and a storage unit, the information processing method causing the processor to execute a program according to any one of appendices 1 to 11.
As a result, based on the document information that specifies the contract conditions that are the subject of the contract prepared by users related to multiple contract parties, electronic contracts can be created as one contract that is defined by multiple contract conditions. can be concluded.

1 system, 10 server, 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 (14)

A program comprising a processor and a storage unit and causing a computer to execute electronic contract procedures between multiple users,
The program causes the processor to:
a first reception step of receiving input of first contract conditions regarding one contract 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 an input of second contract conditions that define the first contract together with the first contract conditions from a second user in response to the first contract conditions presented in the first presentation step;
a storage step for storing the first contract conditions received in the first reception step and the second contract conditions received in the second reception step in association with each other as contract conditions related to one contract procedure;
The first contract terms and the second contract terms, which are stored in association with each other as contract terms defining the first contract in the storage step, are approved by all parties to the contract, including the first user and the second user . an approval step of adding and memorizing an electronic signature indicating that the
a second presentation step of presenting the second contract terms received in the second reception step to the first user;
run the
The approval step includes:
In response to an input operation from the first user regarding the second contract conditions presented to the first user in the second presentation step,
a step of storing information indicating that the first contract condition and the second contract condition have been approved by the first user and the second user;
program. The first reception step is a step of receiving first document information in which first contract conditions are defined,
The second reception step is a step of receiving second document information in which second contract conditions are defined.
The program according to claim 1. The first document information and the second document information are document information having different document types related to the contract procedure in the above-mentioned 1.
The program according to claim 2. A program comprising a processor and a storage unit and causing a computer to execute electronic contract procedures between multiple users,
The program causes the processor to:
a first reception step of receiving input of first contract conditions 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 for receiving input of second contract conditions from a second user in response to the first contract conditions presented in the first presentation step;
a storage step for storing the first contract conditions received in the first reception step and the second contract conditions received in the second reception step in association with each other as contract conditions related to one contract procedure;
Approval for storing information indicating that the first contract conditions received in the first reception step and the second contract conditions received in the second reception step are approved by at least one of the first user and the second user. step and
run the
The first receiving 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,
The second receiving 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.
program. The program causes the processor to:
a contract type reception step of receiving the contract type of the first contract procedure from the first user;
The program according to claim 4, which causes the program to execute. The first reception step is a step of receiving first document information regarding a lease contract for real estate or goods when the contract type of the first contract procedure is a lease contract for real estate or goods;
The second reception step is a step of accepting an identity verification document to be presented to the first user when the contract type in the first contract procedure is a real estate or goods rental contract.
The program according to any one of claims 1 to 5. The first receiving step is a step of receiving first document information regarding the basic contract when the contract type of the first contract procedure is a contract in which an individual contract for the basic contract is associated with the basic contract,
The second receiving step is a step of receiving second document information regarding the individual contract when the contract type of the first contract procedure is a contract in which an individual contract for the basic contract is associated with the basic contract,
The program according to any one of claims 1 to 5. The program causes the processor to:
a second presentation step of presenting the second contract terms received in the second reception step to the first user;
run the
The approval step includes:
In response to an input operation from the first user regarding the second contract conditions presented to the first user in the second presentation step,
a step of storing information indicating that the first contract condition and the second contract condition have been approved by the first user;
The program according to claim 4 or 5 . The second presentation step is a step of presenting the second contract terms as default document information to the first user.
The program according to claim 1 or 8 . The program causes the processor to:
a signing step of adding and storing an electronic signature to the first contract conditions and the second contract conditions in response to the input operation for the second contract conditions from the first user in the approval step;
The program according to claim 1, 8 or 9, which causes the program to execute. The program causes the processor to:
a modification step of receiving a modification instruction from the first user or the second user with respect to the first contract condition received in the first reception step or the second contract condition received in the second reception step;
a modification signature step of adding and storing an electronic signature to the first contract condition or the second contract condition that is the subject of the modification instruction in accordance with the modification instruction received in the modification step;
The program according to any one of claims 1 to 10, which causes the program to execute. An information processing device comprising a processor and a storage unit,
causing the processor to execute the program according to any one of claims 1 to 11;
Information processing device. An information processing system including an information processing device including a processor and a storage unit,
causing the processor to execute the program according to any one of claims 1 to 11;
Information processing system. An information processing method executed by a computer comprising a processor and a storage unit,
causing the processor to execute the program according to any one of claims 1 to 11;
Information processing method.