JP2024057170A - Contract management program, information processing device, information processing system manufacturing method, and information processing method - Google Patents

Abstract

[Problem] In electronic contract procedures between multiple users, it is common for the contracting parties to negotiate the terms of the contract through communication means such as email, chat, etc., prior to the conclusion of the contract. [Solution] A contract management program for storing an electronic contract document in a computer having a processor and a storage unit, the processor executing a contract storage step for storing a contract document relating to a contract, a document acquisition step for acquiring exchanged document data that is different from the contract document and is exchanged between one party and the other party who carry out the contract procedure when concluding a contract, and an association step for storing the exchanged document data acquired in the document acquisition step in association with the contract document stored in the contract storage step. [Selected Figure] Figure 15

Description

This disclosure relates to a contract management program, an information processing device, an information processing system, and an information processing method.

With the development and spread of computer technology, documents that have been paper-based up until now are being digitized. For example, documents such as contracts that require the signatures and seals of the parties involved are being considered for management as electronic data.
Patent Document 1 discloses an information processing system for digital contracts that includes a creator terminal, a verifying terminal, and a contract management server.

JP 2017-10096 A

In electronic contract procedures between multiple users, it is common for the contracting parties to negotiate the terms of the contract through communication means such as email or chat prior to the contract being concluded.
In cases where a dispute arises regarding the validity of a contract, it may be necessary to confirm the negotiation records and negotiation history at the time of the contract's conclusion. In such cases, there is an issue in which the negotiation records and negotiation history at the time of the contract's conclusion cannot be organized and managed.
Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide a technology for organizing and managing negotiation records, negotiation history, etc. when concluding a contract.

A contract management program for storing electronic contract documents in a computer having a processor and a storage unit, the contract management program executing a contract storage step in which the processor stores contract documents relating to a contract, a document acquisition step in which exchanged document data, which is different from the contract document and is exchanged between one party and another party who carry out contract procedures when concluding a contract, and an association step in which the exchanged document data acquired in the document acquisition step is associated with the contract document stored in the contract storage step and stored.

This disclosure makes it possible to organize and manage negotiation records and negotiation history when concluding a contract.

FIG. 2 is a block diagram showing the functional configuration of the system 1. FIG. 2 is a block diagram showing the functional configuration of the server 10. FIG. 2 is a block diagram showing a functional configuration of a first user terminal 20. FIG. 2 is a block diagram showing a functional configuration of a second user terminal 30. FIG. 2 is a block diagram showing the functional configuration of a mail server 40. FIG. 13 is a diagram showing the data structure of a user table 1012. FIG. 11 is a diagram showing the data structure of a group table 1013. FIG. 10 is a diagram showing the data structure of a document table 1014. FIG. 11 is a diagram showing the data structure of a confirmation table 1015. FIG. 10 is a diagram showing the data structure of an input item table 1016. FIG. 13 is a diagram showing the data structure of a contract group table 1017. FIG. 13 is a diagram showing the data structure of a negotiation record table 1018. FIG. 10 is a diagram showing the data structure of a document table 1019. 13 is a flowchart showing the operation of a contract creation process (first embodiment). 13 is a flowchart showing the operation of a contract confirmation process (second embodiment); 13 is a flowchart showing the operation of a contact process. 13 is a flowchart showing the operation of a contract creation process. 13 is a flowchart showing the operation of a contract confirmation process. 13 is a flowchart showing the operation of a document storage process. 13 is a screen example showing the operation of a contract creation process. 13 is a screen example showing a confirmation request message sent to the second user terminal 30. 13 is a screen example showing the operation of a contract confirmation process. 13 is an example of a screen showing a signing completion message notified to the first user terminal 20. 13 is an example of a screen showing a signing completion message notified to the first user terminal 20. FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90.

Embodiments of the present disclosure will be described below with reference to the drawings. In all figures describing 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 contents of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each figure is a schematic diagram, and is not necessarily a precise illustration.

<Configuration of System 1>
The system 1 in the present disclosure is an information processing system for realizing a service for storing and managing contract information concluded between multiple users.
The system 1 includes information processing devices, namely, a server 10, a first user terminal 20, a second user terminal 30, and a mail server 40, which are connected via a network N.
FIG. 1 is a block diagram showing the functional configuration of the system 1.
FIG. 2 is a block diagram showing the functional configuration of the server 10. As shown in FIG.
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. As shown in FIG.
FIG. 5 is a block diagram showing the functional configuration of the mail server 40. As shown in FIG.

Each information processing device is configured by a computer equipped with 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. For each of the server 10, the first user terminal 20, the second user terminal 30, and the mail server 40, explanations that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

<Configuration of Server 10>
The server 10 is an information processing device that provides an electronic contract conclusion service between a plurality of users. The server 10 is an information processing device that provides a service of storing and managing contract information concluded between a plurality of users.
The server 10 includes a memory unit 101 and a control unit 104 .

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

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

The user table 1012 is a table for storing and managing information on member users (hereinafter, users) who use the service. When a user registers to use the 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 a user who uses a service according to the present disclosure does not necessarily need to be registered in the user table 1012.
The user table 1012 is a table having a user ID as a primary key and columns of a user ID, a user name, an email address, and a group ID.
FIG. 6 is a diagram showing the data structure of the user table 1012. As shown in FIG.

The user ID is an item for storing user identification information for identifying a user. The user identification information is an item for which a unique value is set for each user.
The user name is an item for storing the name of the user. The user name may be set to any character string such as a nickname instead of a name.
The email address is an item for storing the email address of the user.
The group ID is an item for storing group identification information of a group to which a user belongs. Groups are defined by a group table 1013, which will be described later, and a user may belong to multiple groups.

The group table 1013 is a table for storing and managing information (group information) about groups to which a user belongs. The group can define any group to which a user belongs, such as a corporation, a company, a club, an organization, or a department within a company.
The group table 1013 is a table having the group ID as a primary key, and columns of the group ID, group name, and administrator ID.
FIG. 7 is a diagram showing the data structure of the group table 1013. As shown in FIG.

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

The document table 1014 is a table for storing and managing information (contract information) relating to an electronic contract exchanged between a creator and a recipient.
The document table 1014 is a table having a document ID as a primary key and columns of a document ID, an email address, a chat ID, document data, and a creator ID.
FIG. 8 is a diagram showing the data structure of the document table 1014. As shown in FIG.

The document ID is an item for storing document identification information for identifying contract information. The document identification information is an item for which a unique value is set for each contract information.
The email address is an item for storing an email address associated with the contract information.
The chat ID is an item for storing chat identification information associated with the contract information. The chat identification information includes user identification information (user ID) in any chat service.
The document data is an item for storing contract information (binary or text data) of a contract document related to the conclusion of a contract. Specifically, the document data includes data in any data format such as Portable Document Format (PDF), Word, and Extensible Markup Language (XML).
Creator ID is an item for storing user identification information for identifying the user who is the creator of the contract information.

The confirmation table 1015 is a table that stores and manages information (checker information) including the email address of the user who will be the checker of the contract information.
The confirmation table 1015 is a table having columns for 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 1015. As shown in FIG.

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

The input item table 1016 is a table that stores and manages information (input item information) relating to the input items associated with the electronic contract information.
The input item table 1016 is a table having columns of input item ID, document ID, inputter ID, input data, input rule, and date and time.
FIG. 10 is a diagram showing the data structure of the input item table 1016. As shown in FIG.

The input item ID is an item that stores input item identification information for identifying an input item.
The document ID is an item that stores the document identification information of the electronic contract information with which the input item is associated.
The inputter ID is an item for storing the user identification information or email address of the inputter who inputs the input data into the input item. Specifically, the inputter ID stores the creator ID, the email address of the user identified by the creator ID, the verifying person email address, etc.
The input data is an item that stores input data entered into an input item by a user.
The input rule is a field that stores input rule information related to the input rule of an input item. As the input rule, in addition to data types such as date, datetime, text, and integer, input rule information related to the input rule of any input item such as the number of characters in a text string or a regular expression of the text string can be stored.
The date and time is an item for storing the date and time when the input data is input into the input item by the input user.

The contract group table 1017 is a table for storing and managing information related to contract groups (contract group information). Contract information can be stored and managed in association with one or more cabinets (classification information) for managing contract information. Depending on the information processing service, a cabinet may be called a group, a tag, a label, or the like.
The contract group table 1017 is a table having columns for document ID and cabinet ID.
FIG. 11 is a diagram showing the data structure of the contract group table 1017.

The document ID is an item for storing document identification information for identifying contract information.
The cabinet ID stores cabinet identification information for identifying a cabinet, which is classification information for managing and classifying contract information.

The negotiation record table 1018 is a table for storing and managing information relating to negotiation records (negotiation record information).
The negotiation record table 1018 is a table having columns for document ID and negotiation data.
FIG. 12 is a diagram showing the data structure of the negotiation record table 1018.

The document ID is an item for storing document identification information for identifying contract information.
The negotiation data is an item for storing data (negotiation data) such as negotiation records and negotiation history at the time of contract conclusion. The negotiation data includes any binary data such as email files (eml files), text files (txt files), various document creation application files (files that can be edited with Word, Excel, PowerPoint, etc.), PDF, image files (png, jpeg), etc. The negotiation data may be stored in a form in which multiple negotiation records, negotiation history, and other data can be identified by date, etc.

The document table 1019 is a table for storing and managing information (document information) relating to document data other than the contract document.
The document table 1019 is a table having columns for document ID and document data.
FIG. 13 is a diagram showing the data structure of the document table 1019.

The document ID is an item for storing document identification information for identifying contract information.
The document data is an item that stores document data different from the contract document. The document data includes any document data such as an estimate, an invoice, a receipt, a delivery note, an inspection note, a change contract, an individual contract, etc. The document data includes any binary data such as an email file (eml file), a text file (txt file), various document creation application files (files that can be edited with Word, Excel, PowerPoint, etc.), PDF, an image file (png, jpeg), etc.

<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, a contract confirmation unit 1043, and a document storage unit 1044. The control unit 104 executes an application program 1011 stored in the storage unit 101 to realize each functional unit.

The user registration control unit 1041 performs processing to store information about users who wish to use the service according to the present disclosure in the user table 1012 .
The information stored in the user table 1012 is generated when a user opens a web page operated by a service provider from any information processing terminal, inputs information into a specific input form, and transmits the information to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, completing the user registration. This allows the user stored in the user table 1012 to use the service.
Before the user registration control unit 1041 registers user information in the user table 1012, the service provider may carry out a predetermined examination to restrict whether or not the user is permitted to use the service.
The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or an arbitrary character string or number may be automatically set by the user registration control unit 1041.

The contract creation unit 1042 executes the contract creation process (first embodiment). Details will be described later.

The contract confirmation unit 1043 executes the contract confirmation process (second embodiment). 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) or a laptop PC, or may be a mobile terminal such as a smartphone or a tablet. In addition, the first user terminal 20 may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch terminal.
The first user terminal 20 includes a storage unit 201 , a control unit 204 , an input device 206 , and an output device 208 .

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

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 services disclosed herein. The first user ID 2011 includes information such as a session ID that is temporarily assigned by the server 10 when identifying the user using the first user terminal 20.

The application program 2012 may be pre-stored in the storage unit 201, or may be configured to be downloaded from a web server operated by a service provider via a communication IF.
The application programs 2012 include applications such as a web browser application.
The application program 2012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the first user terminal 20 .

<Configuration of the control unit 204 of the 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 executes an application program 2012 stored in the storage unit 201, thereby realizing each functional unit.

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

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

<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) or a laptop PC, or may be a mobile terminal such as a smartphone or a tablet. In addition, the second user terminal 30 may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch terminal.
The second user terminal 30 includes a storage unit 301 , a control unit 304 , an input device 306 , and an output device 308 .

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

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 user with the services disclosed herein. The second user ID 3011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user who is using the second user terminal 30.

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

<Configuration of the control unit 304 of the 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 executes an application program 3012 stored in the storage unit 301, thereby realizing each functional unit.

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

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

<Configuration of mail server 40>
The mail server 40 is a server for sending and receiving e-mails when multiple users communicate via e-mail. The mail server 40 does not have to be a single server, and may be configured with different servers provided for the first user and the second user. The mail server 40 may be an SMTP server (Simple Mail Transfer Protocol), a POP3 server (Post Office Protocol), an IMAP server (Internet Message Access Protocol), or the like.
A user can send email to other users and receive email from other users via a mail server by operating a mail application installed on the user terminal. Examples of mail applications include Gmail, Outlook, Thunderbird, etc.
The mail server 40 includes a storage unit 401 and a control unit 404 .

<Configuration of storage unit 401 of mail server 40>
The storage unit 401 of the mail server 40 includes an application program 4011 .

The application program 4011 is a program that causes the control unit 404 of the mail server 40 to function as each functional unit.

<Configuration of control unit 404 of mail server 40>
The control unit 404 of the mail server 40 includes a mail control unit 4041. The control unit 404 executes an application program 4011 stored in the storage unit 401, thereby realizing each functional unit.

<Operation of System 1>
Each process of the system 1 will be described below.
FIG. 14 is a flowchart showing the operation of the contract creation process (first embodiment).
FIG. 15 is a flowchart showing the operation of the contract confirmation process (second embodiment).
FIG. 16 is a flowchart showing the operation of the contact process.
FIG. 17 is a flowchart showing the operation of the contract creation process (second embodiment).
FIG. 18 is a flowchart showing the operation of the contract confirmation process.
FIG. 19 is a flowchart showing the operation of the document storage process.
FIG. 20 is an example of a screen showing the operation of the contract creation process.
FIG. 21 is an example of a screen showing a confirmation request message sent to the second user terminal 30. As shown in FIG.
FIG. 22 is a screen example showing the operation of the contract confirmation process.
FIG. 23 is an example of a screen showing a signing completion message sent to the first user terminal 20. As shown in FIG.
FIG. 24 is an example of a screen showing a signing completion message sent to the first user terminal 20. As shown in FIG.

In this disclosure, the contract creation process (first embodiment), contract confirmation process (second embodiment), and document storage process on the server 10 are described below.

<Contract Creation Process (First Example)>
The contract creation process (first embodiment) is a process in which the creator creates electronic contract information and transmits it to the confirmer.

Figure 20 is an example screen showing the operation of the contract creation process (first embodiment). A screen 50 for creating contract information, which is displayed on the display 2081 of the first user terminal 20, displays a status 510 indicating the current creation status of the contract information, buttons 521, 522, 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, 534, a send button 540, and an exchange document registration button 550.

<Outline of contract creation process (first embodiment)>
The contract creation process (first embodiment) is a series of processes in which the creator creates electronic contract information, sets a verifying party to whom the electronic contract information will be sent, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, the user associates negotiation data containing negotiation records and negotiation history at the time of contract conclusion with the created electronic contract information, stores the negotiation data, and sends the electronic contract information to the set verifying party.

<Details of contract creation process (first embodiment)>
In step S101, the contract creation unit 1042 of the server 10 executes a generating step of generating a record to be stored in association with the contract document in the contract storage step.
In step S101, the first user who will be the creator operates the input device 206 of the first user terminal 20 to input a URL for executing the contract creation process (first embodiment) in the browser application of the first user terminal 20 to open a web page (contract creation page). The first user logs in to the service by inputting the first user ID 2011, password, etc. As a result, the first user terminal 20 transmits a request to the server 10 to execute the contract creation process (first embodiment).
The first user operates the input device 206 of the first user terminal 20, presses a button on the contract creation page to create a new record that associates and stores the contract document, such as a “New Contract” button, and sends a request to the server 10.
When the contract creation unit 1042 of the server 10 receives the request, it creates and stores a new record in the document table 1014. The document ID is an arbitrary document ID that is incremented and assigned.

In step S101, the contract creation unit 1042 of the server 10 executes a destination storage step to store destination information associated with the record generated in the generation step.

The destination storage step executes a step of storing destination information related to a predetermined email address.
Specifically, the contract creation unit 1042 of the server 10 generates a new email address and stores it in the email address field of the newly created record in the document table 1014. It is preferable that the email address be unique for each document ID.
The domain of the email address may be a domain owned by the operator of the electronic contract service according to the present disclosure, or may be any email address. For example, it may be a domain managed by the organization to which the first user belongs. The user name, account name, and local part of the generated email address may include a newly numbered document ID. This allows the generated email address to be a unique value for each document ID.
In the present disclosure, the generated email address will be described as an example of an email address that can be received on the email server 40 managed by the operator of the electronic contract service according to the present disclosure.

The destination storage step executes a step of storing destination information relating to predetermined identification information.
Specifically, the contract creation unit 1042 of the server 10 generates a new user ID (chat ID) for the chat service, and stores it in the chat ID field of the record newly created in the document table 1014. It is preferable that the chat ID is unique for each document ID.
The generated chat ID may include the newly assigned document ID, so that the generated chat ID can be a unique value for each document ID.

In step S102, the contract preparation unit 1042 of the server 10 executes a contract storage step of storing a contract document relating to the contract accepted from the first user.
Specifically, the first user operates the input device 206 of the first user terminal 20 to create contract information including document data related to the contract. The document data may be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and the contract information may include the document data.
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 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of the record identified by the document ID numbered in step S101 of the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the document table 1014 in association with the destination information generated and stored in step S101.

The screen 50 for creating contract information displays document data 531 stored in the document table 1014.

In step S103, the first user operates the input device 206 of the first user terminal 20 to select and specify a user who will be a confirmer (recipient) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies a second user as the recipient.
The first user operates the input device 206 of the first user terminal 20, inputs the email address of the second user who will be the confirmer, and transmits it to the server 10. The contract creation unit 1042 of the server 10 stores the received email address and the document ID of the contract information created and stored in step S101 in the items of confirmer email address and document ID in the confirmation table 1015, respectively, and associates the contract information with the email address of the second user and stores them. The first user may set the language and access code of the second user, and store them in association with the email address of the second user.
At this time, a value of 1 is stored in the confirmation order field of the confirmation table 1015. In step S103, the first user may be able to select and set multiple users to be the confirmers. In this case, the value of the confirmation order field of the users to be the confirmers is incremented by one and stored according to the selection order. This sets the circulation order of the confirmers in the contract confirmation process (second embodiment) described later. Note that setting the circulation order is not essential.

In step S104, the first user operates the input device 206 of the first user terminal 20 to set input items for the contract information.
Specifically, the first user operates the input device 206 of the first user terminal 20, etc., to set a plurality of input items for the contract information created and stored in step S102. The input items can be any input item, such as a seal field for stamping seal data, an input field for inputting text data such as signature data, a check box field for selecting check items, a date field for inputting a date, etc.
The first user operates the input device 206 of the first user terminal 20 to send a request to add an input item to the server 10. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information as the document ID of a new record in the input item table 1016. As a result, the newly added input item information is stored in association with the contract information. The first user can store multiple pieces of input item information in association with the contract information.

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

In step S106, the contract preparation unit 1042 of the server 10 accepts input data for a plurality of input items input by the first user.
Specifically, the first user operates the input device 206 of the first user terminal 20 to input input data for each input item set in step S105. For example, the first user may input input data of a number for managing contract information, such as a serial number for a group to which the first user belongs, into an input item in which a management number is set. The first user may input input data of the contract conclusion date of the contract information into an input item in which a contract conclusion date is set. After completing input of the input data into 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 1016 specified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

<Acquisition of exchanged document data>
In step S107, the contract creation unit 1042 of the server 10 executes a document acquisition step to acquire from the first user exchange document data that is exchanged between one party and another party carrying out contract procedures when concluding a contract, unlike the contract document.

<Acquisition of Exchange Document Data (First Embodiment)>
In step S107, the document obtaining step executes a step of obtaining exchange document data based on a file including the exchange document data received from the first user.
Specifically, the first user operates the input device 206 of the first user terminal 20 and presses the exchange document registration button 550 displayed on the screen 50 for creating contract information, whereby a file selection dialog for selecting the exchange document data to be sent to the server 10 is displayed on the display 2081 of the first user terminal 20.
The first user operates the input device 206 of the first user terminal 20, and selects, in the file selection dialogue, exchange document data that is exchanged between one party and another party who are performing contract procedures when concluding a contract, unlike a contract document. The control unit 204 of the first user terminal 20 transmits (uploads) the selected exchange document data to the server 10.
The contract preparation unit 1042 of the server 10 receives and accepts the exchanged document data from the first user terminal 20 .

<Acquisition of Exchange Document Data (Second Embodiment)>
In step S107, the document obtaining step may include a step of obtaining exchange document data based on a URL that identifies the exchange document data received from the first user.
Specifically, the first user may operate the input device 206 of the first user terminal 20 and press the exchange document registration button 550 displayed on the screen 50 for creating contract information, whereby a file selection dialog including a URL input field for entering a URL identifying the exchange document data to be sent to the server 10 is displayed on the display 2081 of the first user terminal 20.
The first user operates the input device 206 of the first user terminal 20 to input a URL that specifies exchanged document data that is exchanged between one party and another party performing contract procedures when concluding a contract, unlike a contract document, into the URL input field of the file selection dialogue. The control unit 204 of the first user terminal 20 transmits the input URL to the server 10.
The contract preparation unit 1042 of the server 10 receives the URL from the first user terminal 20, and acquires and accepts the exchanged document data from the URL.

<Exchange document data acquisition (third embodiment)>
Based on the exchange document data acquired by the exchange document data acquisition (first embodiment) or the exchange document data acquisition (second embodiment), a process may be executed to acquire other exchange document data that should be associated with the contract document in the same manner as the exchange document data.
In step S107, the control unit 204 of the first user terminal 20 executes a second document acquisition step of acquiring second exchange document data related to the exchange document data acquired in the document acquisition step, based on the destination information included in the exchange document data acquired in the document acquisition step.
Specifically, when the exchange document data acquired by exchange document data acquisition (first embodiment) or exchange document data acquisition (second embodiment) is a file containing destination information such as an e-mail file, the control unit 204 of the first user terminal 20 searches for other files stored in the memory unit 201 of the first user terminal 20 based on the destination information, and acquires the files included in the search results as exchange document data.

For example, the second document acquisition step includes a step of searching for and acquiring second exchange document data that includes the same destination information as the destination information included in the exchange document data.
Specifically, when the exchange document data acquired by exchange document data acquisition (first embodiment) or exchange document data acquisition (second embodiment) is a file containing destination information such as an e-mail file, the control unit 204 of the first user terminal 20 searches the memory unit 201 of the first user terminal 20 for other files with the same destination information as the destination information, and acquires the files included in the search results as exchange document data.

In step S107, the control unit 204 of the first user terminal 20 executes a second document acquisition step of acquiring second exchanged document data related to the exchanged document data, based on the subject information included in the exchanged document data acquired in the document acquisition step.
Specifically, when the exchanged document data acquired by the exchanged document data acquisition (first embodiment) or exchanged document data acquisition (second embodiment) is a file including subject information such as an e-mail file, the control unit 204 of the first user terminal 20 searches the memory unit 201 of the first user terminal 20 for other files having subject information identical or similar to the subject information, and acquires the files included in the search results as exchanged document data. The determination of whether a subject is identical or similar may be based on a measure such as cosine similarity between texts. Also, whether a subject is identical or similar may be determined by excluding character strings such as "Re:" and "Fw:" that are added when replying or forwarding from the subject.

The contract preparation unit 1042 of the server 10 executes a presenting step of presenting the second exchange document data acquired in the second document acquisition step as a candidate document to the first user in a selectable manner.
Specifically, the control unit 204 of the first user terminal 20 may be configured to display other files acquired during exchange document data acquisition (third embodiment) on the display 2081 of the first user terminal 20 as candidate documents for the exchange document data.

The associating step executes a step of storing the candidate document selected by the first user in association with the contract document stored in the contract storing step.
Specifically, the first user operates the input device 206 of the first user terminal 20 to select and specify exchanged document data to be stored in association with the contract information from the candidate documents displayed on the display 2081 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits the selected exchanged document data to the server 10. The contract creation unit 1042 of the server 10 acquires the received exchanged document data.
This allows only the exchange document data that the first user has confirmed and selected to be stored in association with the contract information, thereby making it possible to avoid storing unnecessary exchange document data in association with the contract information while receiving proposals for exchange document data to be stored in association with the contract information without omission.

In the present disclosure, the control unit 204 of the first user terminal 20 is configured to execute the exchange document data acquisition (third embodiment) process, but this is not limited thereto. For example, the contract creation unit 1042 of the server 10 may be configured to search for email files sent and received by the first user from the mail server by setting access rights to the mail server, etc. used by the first user, and execute the exchange document data acquisition (third embodiment) process. Similarly, the contract creation unit 1042 of the server 10 may be configured to search for chat messages, etc. sent and received by the first user from the chat service by setting access rights to the chat service, etc. used by the first user, and execute the exchange document data acquisition (third embodiment) process.

<Acquisition of Exchange Document Data (Fourth Embodiment)>
In step S107, the contract preparation unit 1042 of the server 10 executes an importance calculation step of calculating the importance indicating the relevance of the candidate document data exchanged between one party and another party performing the contract procedure when concluding the contract, unlike the contract document. The importance calculation step is a step of calculating the importance of the candidate document data based on the files included in the candidate document data.
Specifically, the contract preparation unit 1042 of the server 10 accesses a mail server, chat service, etc. used by the first user, and acquires multiple candidate document data such as mail data sent and received by the first user, chat messages, etc. The contract preparation unit 1042 of the server 10 calculates the importance of each of the acquired multiple candidate document data, and stores the candidate document data in association with the importance.
The contract preparation unit 1042 of the server 10 calculates the importance of candidate document data that includes information highly related to contract procedures as higher among the acquired candidate document data. For example, the contract preparation unit 1042 of the server 10 calculates the importance of candidate document data that includes supporting documents such as contracts, estimates, invoices, and receipts as attachments as higher among the acquired candidate document data. The contract preparation unit 1042 of the server 10 calculates the importance of text information included in the acquired candidate document data that includes specific terms such as amounts and legal terms as higher.
The importance level may be a value indicating the relevance to the contract document stored in the contract storage step. For example, the contract creation unit 1042 of the server 10 calculates the importance level of text information contained in the acquired candidate document data that includes character strings such as the contract name and serial number of the contract document stored in the contract storage step as high.

The control unit 204 of the first user terminal 20 executes a candidate presenting step of presenting one or a plurality of candidate document data to the first user based on the importance calculated in the importance calculating step.
Specifically, the contract creation unit 1042 of the server 10 transmits the stored candidate document data to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received candidate document data on the display 2081 of the first user terminal 20 in order of importance and presents it to the first user. The control unit 204 of the first user terminal 20 may be configured to present candidate document data whose importance is equal to or greater than a predetermined value, or a predetermined number of candidate document data in order of increasing importance. This allows the first user to check only candidate document data with high importance, without checking candidate document data with low importance.

The control unit 204 of the first user terminal 20 executes a candidate selection step of accepting, from the first user, a selection operation of a predetermined candidate document data from one or more candidate document data presented in the candidate presentation step.
Specifically, the first user operates the input device 206 of the first user terminal 20 to select a specific candidate document data from among a plurality of candidate document data displayed on the display 2081 of the first user terminal 20 .

The document acquisition step is a step of acquiring the predetermined candidate document data selected in the candidate selection step as exchange document data.
The control unit 204 of the first user terminal 20 transmits the selected candidate document data to the server 10. The contract preparation unit 1042 of the server 10 acquires the received candidate document data as exchange document data.

In step S107, the contract preparation unit 1042 of the server 10 executes an association step of storing the exchange document data acquired in the document acquisition step in association with the contract document stored in the contract storage step.
Specifically, the contract preparation unit 1042 of the server 10 stores the document ID numbered in step S101 and the acquired exchanged document data in the items of document ID and negotiation data in the negotiation record table 1018. As a result, the acquired exchanged document data is stored in association with the contract document.

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 for the contract information.
Specifically, the first user operates the input device 206 of the first user terminal 20 and presses the send button 540 displayed on the screen 50 for creating contract information, thereby sending a request to send the contract information to the server 10.

In step S108, the contract creation unit 1042 of the server 10 sends a message to the second user notifying that a request to confirm the contract information has been sent from the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order item of the confirmation table 1015, and identifies the user (first confirmation user) who will be the first confirmer and who has the smallest value stored in the confirmation order item. In the present disclosure, the first confirmation user is, as an example, the second user. The contract creation unit 1042 of the server 10 sends a message to the email address of the second user by a communication means such as email notifying that a request to confirm the contract information has been sent from the first user.
The message to be notified to the second user includes information on a uniform resource locator (URL) including a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a character string obtained by arbitrarily encrypting the document ID, or a character string that can identify the document ID by referring to a table not shown. The URL may also include information for identifying the second user. For example, if the second user is not registered as a user in 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 communicates the access code to the second user by means of e-mail or the like. As a result, even if a third party obtains the message notified to the second user, the third party cannot execute the contract confirmation process (second embodiment) unless he or she obtains the access code.

Figure 21 is an example 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 a URL 62 including a document ID for identifying the contract information.

<Modification>
When the first user selects and sets multiple checkers in step S103, the first user may be configured to be able to set different input item information for each of the multiple checkers independently in step S104. For example, when the first user sets two users, the second user and the ninth user, as checkers, the input items of the contract start date and contract end date may be set for the second user, and the input item of the contract conclusion date may be set for the ninth user. In this case, in the contract confirmation process (second embodiment) described later, the second user can input input data for the input items of the contract start date and contract end date, but cannot input input data for the input item of the contract conclusion date. On the other hand, the ninth user cannot input input data for the input items of the contract start date and contract end date, but can input input data for the input item of the contract conclusion date. The first user may be configured to select and set multiple checkers for one input item information in a duplicated manner.

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

<Contract confirmation process (second embodiment)>
The contract confirmation process (second embodiment) is a process in which a confirmer confirms the contents of the electronic contract information received from the creator.

<Outline of contract confirmation process (second embodiment)>
The contract confirmation process (second embodiment) is a series of processes that accepts access from a confirmer, presents a confirmation screen displaying contract information to the confirmer, accepts input data for input fields from the confirmer, and accepts data regarding confirmation of the contract information from the confirmer.

<Details of contract confirmation process (second embodiment)>
In step S301, the second user who is to be the confirmer can select the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, thereby opening the web page specified by the URL with the browser application of the second user terminal 30. As a result, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process (second embodiment).

If an access code item is stored in the record of the second user in confirmation table 1015, the second user is requested to input an access code, and the input access code is compared with the access code stored in the record of the second user in confirmation table 1015, thereby performing authentication processing for the second user.
Specifically, the server 10 transmits an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30, inputs the access code, and transmits it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the record of the second user in the confirmation table 1015, and if they match, continues the contract confirmation process (second embodiment). On the other hand, if they do not match, stops the contract confirmation process (second embodiment). Note that the authentication process using the access code may be omitted.

The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID included in the received request, and obtains the contract information.The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1015 based on the document ID included in the received request, and obtains the confirmer information.The contract confirmation unit 1043 of the server 10 searches the document ID item in the input item table 1016 based on the document ID included in the received request, and obtains the input item information associated with the contract 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 based on identification information for identifying the second user included in the URL. If the second user is not registered with the service disclosed herein, 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.

In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, confirmer information (information identifying the second user), and input item information, and transmits the screen to the second user terminal 30.

Specifically, the display 3081 of the second user terminal 30 presents a confirmation screen for accepting an operation to approve the contract information to the second user. The second user checks and approves the contract information displayed on the display 3081 of the second user terminal 30.
In addition, the confirmation screen presented to the second user may be configured to be presented to the second user in the language notation specified by the confirmer, based on the language information stored in the language data item of the second user's record in confirmation table 1015.

Figure 22 is an example of a confirmation screen showing the operation of the contract confirmation process (second embodiment). The confirmation screen 70 for approving the contract information, which is displayed on the display 3081 of the second user terminal 30, displays a status 710 showing the current creation status of the contract information, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an Agree button 740.

In step S304, the contract confirmation unit 1043 of the server 10 accepts input for one or more input items of the contract information.
Specifically, the second user operates the input device 306 of the second user terminal 30, and inputs input data into the input items 732, 733, 734, and 735 set in the contract information. In the present disclosure, since the second user is not assigned to input data into the input item 736, it is visually displayed that the second user cannot input data into the input item 736.

In step S305, the contract confirmation unit 1043 of the server 10 executes a presentation step of presenting the exchange document data stored in association with the contract document in the related step to the second user before the second user performs an operation to approve the contract document.
Specifically, the second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30, and when checking the negotiation data, operates the input device 306 of the second user terminal 30 or the like, and presses the negotiation data viewing button 750 displayed on the confirmation screen 70 for checking the contract information. The control unit 304 of the second user terminal 30 transmits a request to the server 10 to view the negotiation data including the document ID. The contract confirmation unit 1043 of the server 10 searches the document ID item of the negotiation record table 1018 based on the received document ID, and acquires one or more pieces of negotiation data. The contract confirmation unit 1043 of the server 10 transmits the acquired one or more pieces of negotiation data to the second user terminal 30. The control unit 304 of the second user terminal 30 displays the received one or more pieces of negotiation data on the display 3081 of the second user terminal 30.
This allows the second user to check data on the negotiation process, such as the negotiation record and negotiation history at the time of contract conclusion, before performing an operation of agreeing to and approving the contract conclusion of the contract information received from the first user, which will be described later. For example, if another user attempts to deceive the second user by impersonating (misrepresenting) the first user and concluding a contract, the second user can easily notice the misrepresentation by the other user by checking the negotiation data.

In step S305, the contract confirmation unit 1043 of the server 10 accepts an instruction from the second user to agree to and approve the conclusion of the contract in the contract information accepted from the first user.
The second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30, and if he or she agrees or accepts the contents, he or she operates the input device 306 of the second user terminal 30 or the like to press the Agree button 740 displayed on the confirmation screen 70 for confirming the contract information, thereby executing a process of transmitting a request including the document ID, information identifying the second user, and the input data for each input item entered in step S305 to the server 10. The information identifying the second user may be the second user ID 3011.
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. Specifically, the contract confirmation unit 1043 of the server 10 searches the confirmation table 1015 based on the received document ID and information identifying the second user, and stores a value of True in the confirmation flag field of the record. For example, when the information identifying the second user is an email address, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015, and stores a value of True in the confirmation flag field of the record. When the information identifying the second user is user identification information, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015 based on the email address of the second user identified by searching the user ID field of the user table 1012, and stores a value of True in the confirmation flag field of the record.
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. As a result, in step S305, the input data entered by the second user is stored as input item information in the input item table 1016.

The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process (second embodiment) has been executed by all the checkers. Specifically, the contract confirmation unit 1043 of the server 10 determines that the contract confirmation process (second embodiment) has been executed by all the checkers when a value of True is stored in the confirmation flag of the checker's record in the confirmation table 1015.
When the contract confirmation process (second embodiment) has been executed by all the confirmers, the contract confirmation unit 1043 of the server 10 transmits a message to the first user notifying the completion of the contract confirmation process (second embodiment). Similarly, the contract confirmation unit 1043 of the server 10 may transmit a message to the second user notifying the completion of the contract confirmation process (second embodiment).

Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the email address of the first user by a communication means such as email to notify the first user that the second user has completed confirmation of the contract information. In other words, the first user is notified that the second user has approved the conclusion of the contract. This allows the first user to know that the conclusion of the contract with the second user has been completed.
The message sent to the first user may include information about a URL that is an end point including a document ID for identifying the contract information.

Figure 23 is an example screen showing a message notified to the first user terminal 20. The message screen 80 displayed on the display 2081 of the first user terminal 20 includes information about a message 81 and a URL 82 that includes a document ID for identifying contract information.

Similarly, the contract confirmation unit 1043 of the server 10 may use a chat service (not shown) or the like to send a message notifying the first user that the second user has completed confirmation of the contract information, including a mention to the first user. In other words, the first user is notified via the chat service that the second user has approved the conclusion of the contract. This allows the first user to know that the conclusion of the contract with the second user has been completed.
The message sent to the first user may include information about a URL that is an end point including a document ID for identifying the contract information.

The first user can open the web page specified by the URL included in the received message using the browser application of the first user terminal 20. The first user terminal 20 references the contract information and sends a request to the server 10 to inquire. The contract confirmation unit 1043 of the server 10 generates a web page for reference and inquiry of the contract information and sends it to the first user terminal 20. The first user can obtain the document data included in the contract information by downloading it or the like from the web page screen displayed on the display 2081 of the first user terminal 20.

When multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 may send a message notifying the confirmation users other than the user who last executed the contract confirmation process (second embodiment) that the contract confirmation process (second embodiment) has been completed. This allows the confirmation users to receive a notification that the contract confirmation process (second embodiment) has been completed by all confirmers.
In addition, the contract confirmation unit 1043 of the server 10 may send a message to a user who has authority equivalent to that of an administrator in a group to which multiple confirmers belong, notifying them that the contract confirmation process (second embodiment) has been completed.
The message may be sent via email, chat service, etc.
As a result, the administrator in the group to which the user who performed the check belongs can be notified that execution of the contract check process (second embodiment) has been completed.

Specifically, the contract confirmation unit 1043 of the server 10 searches the user ID or email address item in the user table 1012 based on the user ID or email address to obtain the group ID item. The contract confirmation unit 1043 of the server 10 searches the group ID item in the group table 1013 based on the obtained group ID item, obtains the administrator ID item, identifies a user with authority equivalent to an administrator based on the administrator ID by searching the user ID in the user table 1012, and sends a message notifying that the contract confirmation process (second embodiment) has been completed.

<Electronic signature processing>
An electronic signature process may be included in step S305. In response to the instruction to approve the contract conclusion received from the second user in step S305, the contract confirmation unit 1043 of the server 10 assigns an electronic signature indicating that the contract conclusion of the contract information has been approved to the contract information received from the first user, and stores the contract information.
Specifically, the contract confirmation unit 1043 of the server 10 assigns a digital signature to the contract information based on the received request and stores the digital signature. The contract confirmation unit 1043 of the server 10 searches the document ID item of the document table 1014 based on the document ID, and acquires the contract information.
The contract confirmation unit 1043 of the server 10 affixes a digital signature to the acquired contract information and stores it in the document data item of the document table 1014. Note that the contract confirmation unit 1043 of the server 10 may update (overwrite) the document data item with the contract information to which the digital signature has been affixed, or may store the contract information before the digital signature has been affixed in a separate storage device (not shown).
The contract confirmation unit 1043 of the server 10 may include in the electronic signature any of the following information: document ID, the first user's email address, the second user's email address, approval date and time, confirmation date and time, authentication method for the approval date and time, authentication method for the confirmation date and time, input data values for each input item, consent (approval) of the first user, second user, timestamp, etc.
As a result, the contract confirmation unit 1043 of the server 10 adds a digital signature indicating that the second user has approved the conclusion of the contract in the contract information to the contract information, and stores the digital signature. This makes it possible to prevent a third party from impersonating or tampering with the contract information.

<Contact Processing>
The contact process is a process of contacting the contracting party. Generally, a user communicates with the contracting party, including negotiating the contract terms, prior to the conclusion of a contract. Communication between the contracting parties continues even after the contract is concluded. The communication can be performed using any contact means, such as e-mail, chat services (Slack, Chatwork, LINE WORKS, etc.), and SNS services.
In the present disclosure, the communication between a first user and a second user is described as an example, but is not limited thereto, and the contact process can be applied to communication between any users.

<Outline of contact processing>
The contact process is a series of processes that input the address of the contracting party with which communication will be performed, create and edit the contact content (exchange document data such as a message), send it, and store the received exchange document data. The address includes an email address or identification information associated with a specified document ID.

<Details of contact processing>
The contact process will be described in detail below.

In step S501, the first user operates the input device 206 of the first user terminal 20 to start a mailer application. The first user operates the input device 206 of the first user terminal 20 to create a new e-mail message or to reply to a specific e-mail. At this time, the first user includes the e-mail address generated in step S101 of the contract creation process (first embodiment) in the destination of the e-mail. The e-mail address may be included in either CC (Carbon Copy) or BCC (Back Carbon Copy), but it is preferable to include it in CC because if it is set in BCC, the e-mail address will not be included in the reply from the other party. This makes it possible to store the contents of the created e-mail or the reply e-mail in association with the contract information identified by the e-mail address.

Similarly, the first user may operate the input device 206 of the first user terminal 20 to open a website of a specified chat service using a web browser or the like. The first user operates the input device 206 of the first user terminal 20 to create a new chat message or reply to a specified chat message. At this time, the first user includes the chat ID (identification information) generated in step S101 of the contract creation process (first embodiment) in the destination of the chat message (also called a mention, etc.). This allows the content of the created chat message or the replying chat message to be stored in association with the contract information identified by the chat ID.

In step S502, the first user operates the input device 206 of the first user terminal 20 to edit the email message created in step S501, the chat message of the chat service, etc. Specifically, the first user inputs and edits the message subject and text body, and attaches other files, etc. to the message.

In step S503, the first user operates the input device 206 of the first user terminal 20 to send the email message edited in step S502, a chat message for the chat service, or the like, to the destination specified in step S501.
Specifically, the first user can send an e-mail message by operating the input device 206 of the first user terminal 20 and pressing a "send" button or the like displayed in the mailer application.
The first user can send a chat message by operating the input device 206 of the first user terminal 20 and pressing a "send" button or the like displayed on the chat service screen.

In step S504, the document acquisition step executes a step of acquiring exchange document data including the destination information stored in the destination storage step from a server identified based on the destination information.

The document acquisition step executes a step of acquiring exchange document data including a predetermined email address from a mail server capable of receiving emails from the predetermined email address.
Specifically, the control unit 104 of the server 10 transmits a request to acquire the email file that has arrived at the mail server 40. The mail control unit 4041 of the mail server 40 transmits the email file stored in the storage unit 401 of the mail server 40 to the server 10. Note that the storage unit 401 of the mail server 40 contains the email file transmitted from the first user in step S503.
The email file also includes the email address set by the first user in step S501 as destination information.

The control unit 104 of the server 10 searches the email address field in the document table 1014 based on the email address included in the destination information of the received email file, and obtains the document ID. The control unit 104 of the server 10 searches the document ID field in the negotiation record table 1018 based on the obtained document ID, and stores the email file in the negotiation data field of the identified record. Note that if there is no record for the obtained document ID in the negotiation record table 1018, a new record is created, and the email file is stored in the negotiation data field of the record.

The document acquisition step executes a step of acquiring exchange document data including the predetermined identification information as a destination from a predetermined chat service based on the predetermined identification information.
Specifically, the control unit 104 of the server 10 transmits a request to the chat service to acquire chat messages that have arrived. The chat service transmits the received chat messages to the server 10. The chat service transmits the chat message transmitted from the first user in step S503 to the server 10.
The chat message also includes the chat ID set for the first user in step S501 as destination information.

The control unit 104 of the server 10 searches the chat ID field in the document table 1014 based on the chat ID included in the destination information of the received chat message, and acquires the document ID. The control unit 104 of the server 10 searches the document ID field in the negotiation record table 1018 based on the acquired document ID, and stores the chat message in the negotiation data field of the identified record. Note that if there is no record for the acquired document ID in the negotiation record table 1018, a new record is created, and the chat message is stored in the negotiation data field of that record.

<Acquisition of Exchange Document Data (Modification)>
The electronic contract service according to the present disclosure may acquire document data to be exchanged by the following methods other than step S107 of the contract document creation process and the contact process, and store the data in association with the contract information.

The document acquiring step includes acquiring exchange document data to be classified based on a classification operation performed by the first user on the exchange document data.
Specifically, the first user operates the input device 206 of the first user terminal 20 to launch any mailer application such as Gmail, Outlook, or Thunderbird that is pre-stored in the first user terminal 20. A specific add-on for linking with the electronic contract service according to the present disclosure is pre-installed in the mailer application, and the mailer application is configured to be capable of sending a specific request to an API (Application Programming Interface) provided by the electronic contract service according to the present disclosure.
The first user operates the input device 206 of the first user terminal 20 to classify a predetermined mail document into a predetermined classification folder, classification directory, etc. in the mailer application. The classification folder is set with a label such as a contract document or a business project, and is associated with a predetermined document ID.
Similarly, the first user operates the input device 206 of the first user terminal 20 to assign a predetermined classification tag or the like to a predetermined mail document in a mailer application. The classification tag is set with a label such as a contract document or a business project, and is associated with a predetermined document ID.

The associating step executes a step of storing the exchange document data in association with the contract document identified by the classification operation.
Specifically, the control unit of the first user terminal 20 transmits a request including the classified mail document and a predetermined document ID to the server 10. The contract preparation unit 1042 of the server 10 stores the received document ID and mail document in the document ID and negotiation data items of the negotiation record table 1018, respectively.
The control unit of the first user terminal 20 transmits a request including the mail document to which the classification tag has been added and a specific document ID to the server 10. The contract preparation unit 1042 of the server 10 stores the received document ID and mail document in the document ID and negotiation data items of the negotiation record table 1018, respectively.
In this way, the exchanged document data may be stored in association with the contract information through a classification operation of a mailer or the like.

In step S504, a calculation step is executed to calculate an evaluation index value related to the contract document based on the exchanged document data stored in association with the contract document in the association step.
Specifically, the control unit 104 of the server 10 refers to the negotiation record table 1018 and acquires negotiation data associated with one or more contract documents (document IDs). The control unit 104 of the server 10 analyzes the negotiation data associated with a specific contract document and calculates a contract score (evaluation index value) for the specific contract document.
The contract score may be the number of negotiation data items associated with a given contract document.
The control unit 104 of the server 10 stores the calculated contract score in association with the document ID of a specified contract document in the document table 1014. The control unit 104 of the server 10 may calculate an evaluation index value of the contract document, and present the evaluation index value to the user if the evaluation index value is lower than a specified value or if the evaluation index value is higher than a specified value.

In step S504, a calculation step is executed to calculate evaluation index values related to the contracting parties of the contract document based on the exchanged document data stored in association with the contract document in the association step.
Specifically, the control unit 104 of the server 10 refers to the negotiation record table 1018 and acquires negotiation data associated with one or more contract documents (document IDs). The control unit 104 of the server 10 analyzes the negotiation data associated with a specific contract document and calculates a credit score (evaluation index value) for the contracting parties of the specific contract document.
The credit score may be the number of negotiation data items associated with one or more contract documents in which the contracting parties have been involved in the process.
The control unit 104 of the server 10 stores the calculated credit score in association with the user ID of the contracting party in the user table 1012. The control unit 104 of the server 10 may obtain the credit score of the contracting party from the user table 1012 during contract creation processing, contract confirmation processing, etc., and present it to the user who executes the contract creation processing, contract confirmation processing, etc. For example, it may be presented when the contracting party's credit score has an evaluation index value lower than a predetermined value, or when the evaluation index value is higher than a predetermined value. This allows the user to proceed with the contract procedure while taking into account the contracting party's credit score.

The calculation of the evaluation index value may be performed in step S107 of the contract creation process (first embodiment). The calculation of the evaluation index value may also be configured to be performed at any timing or at predetermined intervals.

In this disclosure, the contract creation process (second embodiment), contract confirmation process (second embodiment), and document storage process on the server 10 are described below.

<Contract Creation Process (Second Example)>
The contract creation process (second embodiment) is a process in which the creator creates electronic contract information and transmits it to the confirmer.

Figure 20 is an example screen showing the operation of the contract creation process (second embodiment). A screen 50 for creating contract information, which is displayed on the display 2081 of the first user terminal 20, displays a status 510 indicating the current creation status of the contract information, 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.

<Outline of contract creation process (second embodiment)>
The contract creation process (second embodiment) is a series of processes in which the creator creates electronic contract information, sets a verifying party to whom the electronic contract information will be sent, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, and sends the electronic contract information to the set verifying party.
As one or more users execute the contract creation process (second embodiment) multiple times, the contract creation unit 1042 of the server 10 executes a contract storage step of storing multiple contract documents related to the contract.

<Details of contract creation process (second embodiment)>
In step S201, the contract preparation unit 1042 of the server 10 receives, from the preparer, contract information to be the subject of a contract to be concluded between the preparer and the verifyer.
Specifically, the first user operates the input device 206 of the first user terminal 20 to create contract information including document data related to the contract. The document data may be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and the contract information may include the document data.
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 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the document table 1014.

The screen 50 for creating contract information displays document data 531 stored in the document table 1014.

In step S202, the first user operates the input device 206 of the first user terminal 20 to select and specify a user who will be a confirmer (recipient) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies a second user as the recipient.
The first user operates the input device 206 of the first user terminal 20, inputs the email address of the second user who will be the confirmer, and transmits it to the server 10. The contract creation unit 1042 of the server 10 stores the received email address and the document ID of the contract information created and stored in step S201 in the items of confirmer email address and document ID in the confirmation table 1015, respectively, and associates the contract information with the email address of the second user and stores them. The first user may set the language and access code of the second user, and store them in association with the email address of the second user.
At this time, a value of 1 is stored in the confirmation order field of the confirmation table 1015. In step S202, the first user may be able to select and set multiple users to be the confirmers. In this case, the value of the confirmation order field of the users to be the confirmers is incremented by one and stored according to the selection order. This sets the circulation order of the confirmers in the contract confirmation process (second embodiment) 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 contract 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 contract information created and stored in step S201. The input items can be any input item, such as a seal field for stamping seal data, an input field for inputting text data such as signature data, a check box field for selecting check items, a date field for inputting a date, etc.
The first user operates the input device 206 of the first user terminal 20 to send a request to add an input item to the server 10. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information as the document ID of a new record in the input item table 1016. As a result, the newly added input item information is stored in association with the contract information. The first user can store multiple pieces of input item information in association with the contract information.

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

In step S205, the contract preparation unit 1042 of the server 10 accepts input data for a plurality of input items input by the first user.
Specifically, the first user operates the input device 206 of the first user terminal 20 to input input data for each input item set in step S204. For example, the first user may input input data of a number for managing contract information, such as a serial number for a group to which the first user belongs, into an input item in which a management number is set. The first user may input input data of the contract conclusion date of the contract information into an input item in which a contract conclusion date is set. After completing input of the input data into 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 1016 specified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

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 for the contract information.
Specifically, the first user operates the input device 206 of the first user terminal 20 and presses the send button 540 displayed on the screen 50 for creating contract information, thereby sending a request to send the contract information to the server 10.

In step S206, the contract creation unit 1042 of the server 10 sends a message to the second user notifying that a request to confirm the contract information has been sent from the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order item of the confirmation table 1015, and identifies the user (first confirmation user) who will be the first confirmer and who has the smallest value stored in the confirmation order item. In the present disclosure, the first confirmation user is, as an example, the second user. The contract creation unit 1042 of the server 10 sends a message to the email address of the second user by a communication means such as email notifying that a request to confirm the contract information has been sent from the first user.
The message to be notified to the second user includes information on a uniform resource locator (URL) including a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a character string obtained by arbitrarily encrypting the document ID, or a character string that can identify the document ID by referring to a table not shown. The URL may also include information for identifying the second user. For example, if the second user is not registered as a user in the service according to the present disclosure, the URL needs to include information for identifying the second user.

When the first user sets an access code for the second user, the first user separately communicates the access code to the second user by means of e-mail or the like. As a result, even if a third party obtains the message notified to the second user, the third party cannot execute the contract confirmation process (second embodiment) unless he or she obtains the access code.

Figure 21 is an example 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 a URL 62 including a document ID for identifying the contract information.

<Modification>
When the first user selects and sets multiple checkers in step S202, the first user may be configured to set different input item information for each of the multiple checkers independently in step S103. For example, when the first user sets two users, the second user and the ninth user, as checkers, the first user may set the input items of the contract start date and contract end date for the second user, and the input item of the contract conclusion date for the ninth user. In this case, in the contract confirmation process (second embodiment) described later, the second user can input input data for the input items of the contract start date and contract end date, but cannot input input data for the input item of the contract conclusion date. On the other hand, the ninth user cannot input input data for the input items of the contract start date and contract end date, but can input input data for the input item of the contract conclusion date. The first user may be configured to select and set multiple checkers for one input item information in a duplicated manner.

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

<Contract confirmation process (second embodiment)>
The contract confirmation process (second embodiment) is a process in which a confirmer confirms the contents of the electronic contract information received from the creator.

<Outline of contract confirmation process (second embodiment)>
The contract confirmation process (second embodiment) is a series of processes that accepts access from a confirmer, presents a confirmation screen displaying contract information to the confirmer, accepts input data for input fields from the confirmer, and accepts data regarding confirmation of the contract information from the confirmer.

<Details of contract confirmation process (second embodiment)>
In step S401, the second user who is to be the confirmer can select the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, thereby opening the web page specified by the URL with the browser application of the second user terminal 30. As a result, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process (second embodiment).

If an access code item is stored in the record of the second user in confirmation table 1015, the second user is requested to input an access code, and the input access code is compared with the access code stored in the record of the second user in confirmation table 1015, thereby performing authentication processing for the second user.
Specifically, the server 10 transmits an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30, inputs the access code, and transmits it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the record of the second user in the confirmation table 1015, and if they match, continues the contract confirmation process (second embodiment). On the other hand, if they do not match, stops the contract confirmation process (second embodiment). Note that the authentication process using the access code may be omitted.

The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID included in the received request, and obtains the contract information.The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1015 based on the document ID included in the received request, and obtains the confirmer information.The contract confirmation unit 1043 of the server 10 searches the document ID item in the input item table 1016 based on the document ID included in the received request, and obtains the input item information associated with the contract information.

In step S402, 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 based on identification information for identifying the second user included in the URL. If the second user is not registered with the service disclosed herein, 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.

In step S403, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, confirmer information (information identifying the second user), and input item information, and transmits the screen to the second user terminal 30.

Specifically, the display 3081 of the second user terminal 30 presents a confirmation screen for accepting an operation to approve the contract information to the second user. The second user checks and approves the contract information displayed on the display 3081 of the second user terminal 30.
In addition, the confirmation screen presented to the second user may be configured to be presented to the second user in the language notation specified by the confirmer, based on the language information stored in the language data item of the second user's record in confirmation table 1015.

Figure 22 is an example of a confirmation screen showing the operation of the contract confirmation process (second embodiment). The confirmation screen 70 for approving the contract information, which is displayed on the display 3081 of the second user terminal 30, displays a status 710 showing the current creation status of the contract information, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an Agree button 740.

In step S404, the contract confirmation unit 1043 of the server 10 accepts input for one or more input items of the contract information.
Specifically, the second user operates the input device 306 of the second user terminal 30, and inputs input data into the input items 732, 733, 734, and 735 set in the contract information. In the present disclosure, since the second user is not assigned to input data into the input item 736, it is visually displayed that the second user cannot input data into the input item 736.

In step S405, the contract confirmation unit 1043 of the server 10 accepts an instruction from the second user to agree to and approve the conclusion of the contract in the contract information accepted from the first user.
The second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30, and if he or she agrees or accepts the contents, he or she operates the input device 306 of the second user terminal 30 or the like to press the Agree button 740 displayed on the confirmation screen 70 for confirming the contract information, thereby executing a process of transmitting a request including the document ID, information identifying the second user, and the input data for each input item entered in step S405 to the server 10. The information identifying the second user may be the second user ID 3011.
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. Specifically, the contract confirmation unit 1043 of the server 10 searches the confirmation table 1015 based on the received document ID and information identifying the second user, and stores a value of True in the confirmation flag field of the record. For example, when the information identifying the second user is an email address, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015, and stores a value of True in the confirmation flag field of the record. When the information identifying the second user is user identification information, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015 based on the email address of the second user identified by searching the user ID field of the user table 1012, and stores a value of True in the confirmation flag field of the record.
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. As a result, the input data entered by the second user in step S405 is stored as input item information in the input item table 1016.

The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process (second embodiment) has been executed by all the checkers. Specifically, the contract confirmation unit 1043 of the server 10 determines that the contract confirmation process (second embodiment) has been executed by all the checkers when a value of True is stored in the confirmation flag of the checker's record in the confirmation table 1015.
When the contract confirmation process (second embodiment) has been executed by all the confirmers, the contract confirmation unit 1043 of the server 10 transmits a message to the first user notifying the completion of the contract confirmation process (second embodiment). Similarly, the contract confirmation unit 1043 of the server 10 may transmit a message to the second user notifying the completion of the contract confirmation process (second embodiment).

Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the email address of the first user by a communication means such as email to notify the first user that the second user has completed confirmation of the contract information. In other words, the first user is notified that the second user has approved the conclusion of the contract. This allows the first user to know that the conclusion of the contract with the second user has been completed.
The message sent to the first user may include information about a URL that is an end point including a document ID for identifying the contract information.

Figure 23 is an example screen showing a message notified to the first user terminal 20. The message screen 80 displayed on the display 2081 of the first user terminal 20 includes information about a message 81 and a URL 82 that includes a document ID for identifying contract information.

Similarly, the contract confirmation unit 1043 of the server 10 may use a chat service (not shown) or the like to send a message notifying the first user that the second user has completed confirmation of the contract information, including a mention to the first user. In other words, the first user is notified via the chat service that the second user has approved the conclusion of the contract. This allows the first user to know that the conclusion of the contract with the second user has been completed.
The message sent to the first user may include information about a URL, which is an end point including a document ID for identifying the contract information.

The first user can open the web page specified by the URL included in the received message using the browser application of the first user terminal 20. The first user terminal 20 references the contract information and sends a request to the server 10 to inquire. The contract confirmation unit 1043 of the server 10 generates a web page for reference and inquiry of the contract information and sends it to the first user terminal 20. The first user can obtain the document data included in the contract information by downloading it or the like from the web page screen displayed on the display 2081 of the first user terminal 20.

When multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 may send a message notifying the confirmation users other than the user who last executed the contract confirmation process (second embodiment) that the contract confirmation process (second embodiment) has been completed. This allows the confirmation users to receive a notification that the contract confirmation process (second embodiment) has been completed by all confirmers.
In addition, the contract confirmation unit 1043 of the server 10 may send a message to a user who has authority equivalent to that of an administrator in a group to which multiple confirmers belong, notifying them that the contract confirmation process (second embodiment) has been completed.
The message may be sent via email, chat service, etc.
As a result, the administrator in the group to which the user who performed the check belongs can be notified that execution of the contract check process (second embodiment) has been completed.

Specifically, the contract confirmation unit 1043 of the server 10 searches the user ID or email address item in the user table 1012 based on the user ID or email address to obtain the group ID item. The contract confirmation unit 1043 of the server 10 searches the group ID item in the group table 1013 based on the obtained group ID item, obtains the administrator ID item, identifies a user with authority equivalent to an administrator based on the administrator ID by searching the user ID in the user table 1012, and sends a message notifying that the contract confirmation process (second embodiment) has been completed.

<Electronic signature processing>
An electronic signature process may be included in step S405. In response to the instruction to approve the contract conclusion received from the second user in step S405, the contract confirmation unit 1043 of the server 10 assigns an electronic signature indicating that the contract conclusion of the contract information has been approved to the contract information received from the first user, and stores the contract information.
Specifically, the contract confirmation unit 1043 of the server 10 assigns a digital signature to the contract information based on the received request and stores the contract information. The contract confirmation unit 1043 of the server 10 searches the document ID item of the document table 1014 based on the document ID, and acquires the contract information.
The contract confirmation unit 1043 of the server 10 affixes a digital signature to the acquired contract information and stores it in the document data item of the document table 1014. Note that the contract confirmation unit 1043 of the server 10 may update (overwrite) the document data item with the contract information to which the digital signature has been affixed, or may store the contract information before the digital signature has been affixed in a separate storage device (not shown).
The contract confirmation unit 1043 of the server 10 may include in the electronic signature any of the following information: document ID, the first user's email address, the second user's email address, approval date and time, confirmation date and time, authentication method for the approval date and time, authentication method for the confirmation date and time, input data values for each input item, consent (approval) of the first user, second user, timestamp, etc.
As a result, the contract confirmation unit 1043 of the server 10 adds a digital signature indicating that the second user has approved the conclusion of the contract in the contract information to the contract information, and stores the contract information. This makes it possible to prevent a third party from impersonating or tampering with the contract information.

<Document storage processing>
The document storage process is a process for storing document data selected by the user in association with contract information.

<Outline of Document Storage Processing>
The document storage process is a series of processes in which a user selects document data to be related to the document storage process, proposes to the user candidate contract documents that are candidates for association with the document data, accepts from the user a selection of one or more contract information from the candidate contract documents to be associated with the document data, and stores the document data in association with the one or more contract information selected by the user.
In the present disclosure, the document storage process is described as being performed by a first user as an example, but is not limited thereto. The document storage process can be performed by any user.

<Details of document storage processing>
The document storage process will be described in detail below.

In step S601, the document storage unit 1044 of the server 10 executes a document reception step to receive document data from the user that is different from the contract document stored in the contract creation process (second embodiment).

Figure 24 is an example screen showing the operation of the document storage process. The document storage screen D10 for storing document data, which is displayed on the display 2081 of the first user terminal 20, includes a document registration button D101 and a contract document selector D102. By selecting icons D1021A, D1021B, D1021C displayed for each contract document D102A, D102B, D102C in the contract document selector D102 using check boxes D1022A, D1022B, D1022C, the contract documents associated with each icon can be displayed on the display 2081 of the first user terminal 20.

Specifically, the first user operates the input device 206 of the first user terminal 20 to input a URL for executing the document storage process in the browser application of the first user terminal 20, and opens a web page (document storage screen). The first user logs in to the service by inputting the first user ID 2011, password, etc. As a result, the first user terminal 20 transmits a request to execute the document storage process to the server 10.

The first user operates the input device 206 of the first user terminal 20 and presses the document registration button D101 displayed on the document storage screen D10, whereby a file selection dialog for selecting document data to be sent to the server 10 is displayed on the display 2081 of the first user terminal 20.
The first user operates the input device 206 of the first user terminal 20, and selects, in the file selection dialog, document data different from the contract document stored in the contract creation process (second embodiment). The document data includes any document data such as an estimate, invoice, receipt, delivery note, inspection note, modified contract, individual contract, etc. The control unit 204 of the first user terminal 20 transmits the selected document data to the server 10.
The document storage unit 1044 of the server 10 receives and accepts the selected document data.

<Candidate Proposal Process (First Example)>
In step S602, the document storage unit 1044 of the server 10 executes a candidate proposal step to propose to the user one or more candidate contract documents selectable from among the multiple contract documents stored in the contract storage step, based on the document data accepted in the document acceptance step.
Specifically, the document storage unit 1044 of the server 10 analyzes the document data received in step S601, searches for document data in the document table 1014 based on the file name of the document data, character strings included in the document data, etc., and acquires a document ID. For example, the document data in the document table 1014 is searched for a serial number identifying the contract document included in the file name of the document data, a serial number identifying the contract document included in the character strings of the document data, a title of the contract document, etc., and acquires a document ID of one or more pieces of contract information. For example, the document storage unit 1044 searches for the name, name, company name, organization name, group name, etc. of the contracting parties of the contract document included in the document data in the document table 1014 based on the name, name, company name, organization name, group name, etc. of the contracting parties included in the character strings of the document data, and acquires a document ID of one or more pieces of contract information.

<Candidate Proposal Process (Second Example)>
In step S602, the document storage unit 1044 of the server 10 executes a candidate suggestion step of suggesting to the user, from among the multiple contract documents stored in the contract storage step, one or more candidate contract documents in which the user has previously been involved in contract procedures, so as to be selectable by the user.
Specifically, the document storage unit 1044 of the server 10 searches the user ID field of the user table 1012 based on the first user ID 2011 received from the first user terminal 20, and obtains the first email address of the first user.
The document storage unit 1044 of the server 10 searches the creator ID field of the document table 1014 based on the first user ID 2011, and obtains a document ID. Similarly, the document storage unit 1044 of the server 10 searches the confirmer email address field of the confirmation table 1015 based on the first email address, and obtains a document ID. In this way, the document IDs of one or more pieces of contract information in which the first user was previously involved as a creator or confirmer in a contract procedure are obtained.

The candidate proposing step may include a step of proposing one or more candidate contract documents in which the user has been involved in contract procedures in the past, arranged in order of contract conclusion date, to the user so that the candidate contract documents can be selected.
Specifically, in the candidate proposal process (second embodiment), the document storage unit 1044 of the server 10 sorts the document IDs of one or more acquired contract information in order of the most recent or oldest contract conclusion date of the contract information identified by the document ID. By sorting the document IDs in order of the most recent, the candidate contract documents can be presented to the first user in the order in which they were most recently concluded by the first user. The candidate contract documents can be conveniently presented to the first user in the order of the contract conclusion date.

<Candidate Proposal Process (Third Example)>
In step S602, the document storage unit 1044 of the server 10 executes a candidate suggestion step of suggesting to the user one or more candidate contract documents selected by comparing the date information contained in the document data accepted in the document acceptance step with the date information contained in the multiple contract documents stored in the contract storage step. The date information contained in the document data is date information specified in the document data, obtained by an input operation by the user or by analyzing character strings contained in the document data. The date information contained in the contract document is date information specified in the contract document, obtained by an input operation by the user or by analyzing character strings contained in the contract document.
Specifically, the document storage unit 1044 of the server 10 analyzes the document data received in step S601, and extracts and acquires information (date information) relating to dates such as the invoice date, receipt date, delivery date, and inspection date contained in character strings and the like included in the document data. The document storage unit 1044 of the server 10 may also extract and acquire attributes (date attribute information) relating to dates such as the invoice date, receipt date, delivery date, and inspection date, in addition to the date information. The date attribute information may be configured to be specified based on the type of document data, such as an invoice, receipt, delivery note, inspection note, change contract, individual contract, etc.
The document storage unit 1044 of the server 10 may be configured to acquire and specify date information and date attribute information based on an input operation by the first user, without relying on analysis of document data. For example, the first user operates the input device 206 of the first user terminal 20, inputs date information and date attribute information for each date information in a predetermined input field, and transmits the input information to the server 10. The document storage unit 1044 of the server 10 receives and acquires the date information and date attribute information from the first user terminal 20.
The document storage unit 1044 of the server 10 searches for contract information by comparing the acquired date information and date attribute information with information (date information) relating to dates such as the billing date, receipt date, delivery date, and inspection date contained in the character strings of the contract document of the document data in the document table 1014. Specifically, when the document data is an invoice and contains date information relating to the delivery date (first date), a contract document that contains the first date as the delivery date is searched for from the document data in the document table 1014, and the document ID of one or more pieces of contract information is acquired.

The date information and date attribute information of the contract document of the document data in the document table 1014 may be information that has been determined in advance by the control unit 104 of the server 10 analyzing character strings of the contract document, etc. Also, the date information and date attribute information of the contract document of the document data in the document table 1014 may be information that has been acquired based on input operations by a user involved in the conclusion of the contract document, a user equivalent to another administrator, etc., without relying on analysis of the document data. The document table 1014 stores document data in association with each date information and date attribute information.

In step S602, the document storage unit 1044 of the server 10 transmits the document ID of the acquired one or more pieces of contract information to the first user terminal 20. The display 2081 of the first user terminal 20 presents the received one or more document IDs as candidate contract documents in the contract document selector D102 so that the first user can select them. The first user can select one or more contract documents D102A, D102B, D102C displayed in the contract document selector D102 by operating the input device 206 of the first user terminal 20 using the check boxes D1022A, D1022B, D1022C.

In step S603, the document storage unit 1044 of the server 10 executes a contract selection step of selecting one or more contract documents from the multiple contract documents stored in the contract storage step, which associates the document data accepted in the document acceptance step. The contract selection step executes a step of the user selecting one or more contract documents from one or more candidate contract documents proposed to the user in the candidate proposal step.
Specifically, the first user operates the input device 206 of the first user terminal 20 to select one or more contract documents D102A, D102B, D102C displayed in the contract document selector D102 by checking the check boxes D1022A, D1022B, D1022C. The first user may be able to select multiple contract documents D102A, D102B, D102C. The control unit 204 of the first user terminal 20 transmits the document ID of the selected one or more pieces of contract information to the server 10.

In step S604, the document storage unit 1044 of the server 10 executes a document association step of storing the document data accepted in the document acceptance step in association with one or more contract documents selected in the contract selection step.
Specifically, the document storage unit 1044 of the server 10 stores the document data received in step S601 in the document data, document ID items of the document table 1019 for each of the one or more document IDs received in step S602. As a result, the document data received in step S601 is stored in association with the one or more document IDs received in step S602.

In step S604, the document storage unit 1044 of the server 10 executes a related party identification step of identifying one or more involved users who were involved in the contract procedures of one or more contract documents stored in association with each other in the document association step.
Specifically, the document storage unit 1044 of the server 10 searches the document ID field in the document table 1014 based on the one or more document IDs received in step S602, and obtains the creator ID. Based on the obtained creator ID, the document storage unit 1044 searches the user ID field in the user table 1012 and obtains the creator email address. Similarly, based on the one or more document IDs, the document storage unit 1044 searches the document ID field in the confirmation table 1015, and obtains the confirmer email address.
This allows obtaining and identifying the email addresses of one or more involved users who have been involved in the creation or confirmation of the contract procedure of the contract document identified by the one or more document IDs received in step S602. The one or more involved users include any user who has been involved in the creation or confirmation of the contract procedure of the contract document, as well as a user designated as a related party by the user who created or confirmed the content, etc.

In step S604, the document storage unit 1044 of the server 10 executes a related party notification step to notify one or more involved users identified in the related party identification step that the document data has been stored in association with one or more contract documents in the document association step.
Specifically, the document storage unit 1044 of the server 10 sends an e-mail to the e-mail address of the acquired participating user, including a message indicating that the document data has been stored in association with the contract information in which the participating user was previously involved in concluding a contract, to notify the user.

In step S604, the document storage unit 1044 of the server 10 executes an authority setting step of setting the viewing authority for the document data stored in the document-related step based on the viewing authority for one or more associated and stored contract documents.
Specifically, the document storage unit 1044 of the server 10 acquires the viewing authority for the one or more document IDs received in step S602 from a column or the like for storing viewing authorities (not shown) in the document table 1014. The document storage unit 1044 of the server 10 sets the viewing authority for the document ID as the viewing authority for the document data stored in association with the one or more document IDs in the document table 1019. When multiple pieces of contract information are associated with one piece of document data, multiple viewing authorities corresponding to each of the multiple pieces of contract information may be set as the viewing authority for the document data, or the strictest viewing authority or the loosest viewing authority among the multiple viewing authorities corresponding to each of the multiple pieces of contract information may be set.

The document data stored in association with the contract information in the document storage process can be referenced when a user of the electronic contract service according to the present disclosure checks the contract document included in the contract information. For example, the first user operates the input device 206 of the first user terminal 20 to send a request to the server 10 to refer to the contract information. The control unit 104 of the server 10 acquires document data related to the contract document from the document table 1014, and also searches the document ID item of the document table 1019 based on the document ID of the acquired document data, and acquires the document data associated with the document ID. The control unit 104 of the server 10 transmits the acquired document data and document data to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the acquired document data and document data on the display 2081 of the first user terminal 20 in an associated manner. For example, the first user can download the document data by selecting the document data displayed on the display 2081 of the first user terminal 20.

In step S604, a calculation step is executed to calculate an evaluation index value related to one or more contract documents based on the document data stored in association with the one or more contract documents in the document-related step.
Specifically, the document storage unit 1044 of the server 10 refers to the document table 1019 and acquires document data associated with one or more contract documents (document IDs). The document storage unit 1044 of the server 10 analyzes the document data associated with a specific contract document and calculates a contract score (evaluation index value) for the specific contract document.
The contract score may be the number of document data items associated with a specific contract document.
The contract score may be calculated by determining points in advance according to the document type, such as quotation, invoice, receipt, delivery note, inspection note, change contract, individual contract, etc., and calculating the sum of a predetermined number of points for each document data associated with a specified contract document.
The contract score may be an evaluation index value calculated based on the amount stated in an estimate, invoice, receipt, delivery note, etc. For example, the evaluation index value may be increased as the amount of document data associated with a specific contract document increases.
The document storage unit 1044 of the server 10 stores the calculated contract score in association with the document ID of a specified contract document in the document table 1014. The control unit 104 of the server 10 may calculate an evaluation index value of the contract document, and present the evaluation index value to the user if the evaluation index value is lower than a specified value or if the evaluation index value is higher than a specified value.

In step S604, a calculation step is executed to calculate evaluation index values related to the contracting parties of one or more contract documents based on the document data stored in association with the one or more contract documents in the document-related step.
Specifically, the document storage unit 1044 of the server 10 refers to the document table 1019 and acquires document data associated with one or more contract documents (document IDs). The document storage unit 1044 of the server 10 analyzes the document data associated with a specific contract document and calculates a credit score (evaluation index value) for the contracting parties of the specific contract document.
The credit score may be the number of document data items associated with one or more contract documents in which the contracting parties were involved in the process.
The credit score may be calculated by determining points in advance according to the document type, such as an estimate, invoice, receipt, delivery note, inspection note, amendment contract, individual contract, etc., and calculating the sum of a predetermined number of points for each document data item associated with one or more contract documents in which the contracting parties were involved in the procedure.
The credit score may be an evaluation index value calculated based on the amount stated in an estimate, invoice, receipt, delivery note, etc. For example, the evaluation index value may be increased as the amount of document data associated with one or more contract documents in which the contracting parties are involved in the procedure increases.
The document storage unit 1044 of the server 10 stores the calculated credit score in association with the user ID of the contracting party in the user table 1012. The control unit 104 of the server 10 may obtain the credit score of the contracting party from the user table 1012 during contract creation processing, contract confirmation processing, etc., and present it to the user who executes the contract creation processing, contract confirmation processing, etc. For example, it may be presented when the contracting party's credit score has an evaluation index value lower than a predetermined value, or when the evaluation index value is higher than a predetermined value. This allows the user to proceed with the contract procedure while taking into account the contracting party's credit score.

The calculation of the evaluation index value may be configured to be performed at any timing or at a predetermined interval.

<Basic computer hardware configuration>
25 is a block diagram showing the basic hardware configuration of a 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 a set of instructions written in a program. The processor 901 is composed of an arithmetic unit, registers, peripheral circuits, etc.

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

The auxiliary storage device 903 is a storage device for saving data and programs. For example, it is a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, etc.

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 the Internet, a LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, 5G mobile communication systems, LTE (Long Term Evolution), wireless networks that can connect to the Internet through a predetermined access point (e.g., Wi-Fi (registered trademark)), etc. In the case of wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), Bluetooth (registered trademark), etc. In the case of wired connection, the network also includes a network directly connected by a USB (Universal Serial Bus) cable, etc.

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

<Basic Functional Configuration of Computer 90>
A description will now be given of the functional configuration of a computer realized by the basic hardware configuration (FIG. 25) of a computer 90. The computer includes at least the functional units of a control unit, a storage unit, and a communication unit.

The functional units of the computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 connected to each other via a network. The concept of computer 90 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, expanding them in the main storage device 902, and executing processing according to the programs. The control unit can realize functional units that perform various information processing depending on the type of program. In this way, 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. The processor 901 can also secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with a program. The control unit can also cause the processor 901 to execute processing for adding, updating, and deleting data stored in the storage unit in accordance with the various programs.
Furthermore, by storing data, various programs, and various databases in the storage unit, it can be considered that the information processing device and information processing system according to the present disclosure have been manufactured.

The term database refers to a relational database, which is used to manage sets of data called masters and tables in a tabular format structurally defined by rows and columns, by associating them with each other. In a database, a table is called a table or master, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables and masters can be set and associated.
Usually, a column that serves as a primary key for uniquely identifying a record is set in each table and each master, but setting a primary key to a column is not essential. The control unit can cause the processor 901 to add, delete, or update records in a specific table or master stored in the storage unit according to various programs.

In addition, the databases and masters in this disclosure may include any data structure (such as a list, dictionary, associative array, or object) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc. written in any programming language.

The communication unit is realized by the communication IF 991. The communication unit realizes the 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. In addition, the communication unit can transmit information output from the control unit to other computers 90.

<Additional Notes>
The matters described in the above embodiments will be supplemented below.

(Appendix 1)
A contract management program for storing an electronic contract document in a computer having a processor and a memory unit, the processor executing a contract storage step (S102) for storing a contract document relating to a contract, a document acquisition step (S107, S504) for acquiring exchanged document data that is different from the contract document and is exchanged between one party and another party carrying out contract procedures when concluding a contract, and an association step (S107, S504) for storing the exchanged document data acquired in the document acquisition step in association with the contract document stored in the contract storage step.
This makes it possible to organize and manage the negotiation records and negotiation history at the time of contract conclusion in association with the contract documents.

(Appendix 2)
A contract management program as described in Appendix 1, wherein the contract storage step (S102) is a step of storing the contract document accepted from the first user, and the document acquisition step (S107) is a step of acquiring exchange document data when accepting the contract document from the first user in the contract storage step.
As a result, when the user stores the contract document, the specific user can organize and manage the negotiation records and negotiation history at the time of contract conclusion in association with the contract document.

(Appendix 3)
The contract management program according to claim 2, wherein the document acquisition step (S107) is a step of acquiring the exchange document data based on a URL that identifies the exchange document data received from the first user.
This allows a specific user to obtain the negotiation records and negotiation history at the time of contract conclusion from a specific URL, and organize and manage them in association with the contract document.

(Appendix 4)
3. The contract management program according to claim 2, wherein the document acquisition step (S107) is a step of acquiring the exchange document data based on a file including the exchange document data received from the first user.
This allows a specific user to store a contract document by uploading a file containing the negotiation records and negotiation history at the time of contract conclusion, and organize and manage the file in association with the contract document.

(Appendix 5)
A contract management program as described in Appendix 1, in which a processor executes an importance calculation step (S107) of calculating the importance indicating the relevance of candidate document data exchanged between one party and another party carrying out contract procedures when concluding a contract, unlike a contract document.
This makes it possible to calculate the importance of the negotiation records and negotiation history at the time of contract conclusion.

(Appendix 6)
6. The contract management program according to claim 5, wherein the importance calculation step (S107) is a step of calculating the importance of the candidate document data based on a file included in the candidate document data.
This makes it possible to calculate the importance of candidate document data such as e-mail based on the type and content of attached supporting documents such as contracts, estimates, and invoices.

(Appendix 7)
6. The contract management program according to claim 5, wherein the document acquisition step (S107) is a step of acquiring, as exchange document data, candidate document data whose importance calculated in the importance calculation step is equal to or greater than a predetermined value.
This allows candidate document data whose importance is equal to or greater than a predetermined value to be stored as exchanged document data in association with the contract document, and candidate document data whose importance is less than the predetermined value to be stored without being associated with the contract document. Only exchanged document data with a higher importance can be associated with the contract document.

(Appendix 8)
A contract management program as described in Appendix 7, wherein a processor executes a candidate presentation step (S107) of presenting one or more candidate document data to a first user based on the importance calculated in the importance calculation step, and a candidate selection step (S107) of accepting a selection operation of a specific candidate document data from the one or more candidate document data presented in the candidate presentation step from the first user, and a document acquisition step (S107) is a step of acquiring the specific candidate document data selected in the candidate selection step as exchange document data.
This allows the first user to be presented with candidate document data whose importance is above a predetermined value, or a predetermined number of candidate document data in order of increasing importance, and by selecting the presented candidate document data, the first user can easily associate the candidate document data with high importance with the contract document and store it.

(Appendix 9)
A contract management program as described in Appendix 1, wherein the document acquisition step is a step of acquiring exchange document data to be subjected to a classification operation based on a classification operation on the exchange document data by the first user, and the association step is a step of storing the exchange document data in association with the contract document identified by the classification operation.
This allows a specific user to perform classification operations such as folder classification and tagging on exchanged document data such as e-mails, and thereby store the exchanged document data in association with a contract document specified based on the folder, tag, etc. selected by the classification operation. Negotiation records and negotiation details at the time of contract conclusion can be organized and managed in association with the contract document.

(Appendix 10)
A contract management program as described in Appendix 1, in which a processor executes a second document acquisition step (S107) in which second exchange document data related to the exchange document data acquired in the document acquisition step is acquired based on destination information contained in the exchange document data acquired in the document acquisition step, and the association step (S107) is a step in which the second exchange document data acquired in the second document acquisition step is stored in association with the contract document stored in the contract storage step.
This makes it possible to obtain second exchanged document data that is highly related to the first exchanged document data and has the same or similar destination as the first exchanged document data, based on the first exchanged document data. This makes it possible to organize and manage the negotiation records and negotiation history at the time of contract conclusion in a manner that is linked to the contract documents without omission.

(Appendix 11)
11. The contract management program according to claim 10, wherein the second document acquisition step (S107) is a step of searching for and acquiring second exchange document data including the same destination information as the destination information included in the exchange document data.
This makes it possible to organize and manage all negotiation records and negotiation history at the time of contract conclusion by linking them to the contract documents.

(Appendix 12)
A contract management program as described in Appendix 1, in which a processor executes a second document acquisition step (S107) in which second exchanged document data related to the exchanged document data based on subject information contained in the exchanged document data acquired in the document acquisition step, and the association step (S107) is a step in which the second exchanged document data acquired in the second document acquisition step is stored in association with the contract document stored in the contract storage step.
This makes it possible to obtain second exchanged document data that has the same or similar subject matter as, and is highly related to, the first exchanged document data, based on the first exchanged document data. This makes it possible to organize and manage the negotiation records and negotiation history at the time of contract conclusion in a manner that is linked to the contract documents without omission.

(Appendix 13)
A contract management program described in any of Appendices 10 to 12, wherein a processor executes a presentation step (S107) of presenting the second exchange document data acquired in the second document acquisition step as a candidate document to the first user so that the first user can select it, and an association step (S107) is a step of storing the candidate document selected by the first user in association with the contract document stored in the contract storage step.
In this way, only the selection candidates selected by the user from among the highly relevant second exchanged document data can be stored in association with the contract document. Unnecessary exchanged document data from the negotiation records and negotiation history at the time of contract conclusion can be stored without being associated with the contract document.

(Appendix 14)
A contract management program as described in Appendix 1, in which a processor executes a generation step (S101) of generating a record to be stored in association with a contract document in a contract storage step, and a destination storage step (S101) of storing destination information associated with the record generated in the generation step, and a document acquisition step (S304) of acquiring exchange document data including the destination information stored in the destination storage step from a server identified based on the destination information.
This makes it possible to contact the contracting party using specified destination information issued prior to contract procedures such as contract negotiations, and easily transmit the content of the communication with the contracting party (exchanged document data) to a server specified by the destination information.
The received exchange document data is stored in association with the contract document specified by the destination information, so that the negotiation records and negotiation history at the time of contract conclusion can be easily organized and managed in association with the contract document.

(Appendix 15)
A contract management program as described in Appendix 14, wherein the destination storage step (S101) is a step of storing destination information relating to a specified email address, and the document acquisition step (S504) is a step of acquiring exchange document data including the specified email address from a mail server capable of receiving emails from the specified email address.
This allows communication with the contracting party via email using a specific email address issued prior to contract procedures such as contract negotiations, and makes it easy to send the content of communication with the contracting party (exchanged document data) to the mail server specified by that email address.
By storing the received exchange document data in association with the contract document identified by a specified email address, negotiation records and negotiation history at the time of contract conclusion can be easily organized and managed in association with the contract document.

(Appendix 16)
A contract management program as described in Appendix 14, wherein the destination storage step (S101) is a step of storing destination information relating to specified identification information, and the document acquisition step (S504) is a step of acquiring exchange document data including the specified identification information as a destination from a specified chat service based on the specified identification information.
This allows a user to mention a specific identification information issued prior to contract procedures such as contract negotiations, and contact the contracting party via a chat service, etc., and then send the content of the communication with the contracting party (exchanged document data) to the chat service.
The received exchange document data is stored in association with the contract document specified by the identification information, so that the negotiation records and negotiation history at the time of contract conclusion can be easily organized and managed in association with the contract document.

(Appendix 17)
A contract management program as described in Appendix 1, in which a processor executes a confirmer receiving step (S102) of receiving from a first user second user identification information identifying a second user who will approve the contract document received in the contract storage step, and a presentation step (S305) of presenting to the second user exchange document data stored in association with the contract document in the association step before the second user performs an operation to approve the contract document, wherein the contract storage step (S102) is a step of storing the contract document received from the first user.
This allows the second user to check data on the negotiation process, such as the negotiation record and negotiation history at the time of contract conclusion, before performing an operation of agreeing to and approving the contract conclusion of the contract information received from the first user, which will be described later. For example, if another user attempts to deceive the second user by impersonating (misrepresenting) the first user and concluding a contract, the second user can easily notice the misrepresentation by the other user by checking the negotiation data.

(Appendix 18)
A contract management program according to claim 1, wherein the processor executes a calculation step (S107, S504) of calculating an evaluation index value relating to the contract document based on the exchange document data stored in association with the contract document in the related step.
This makes it possible to calculate an evaluation index value for the contract document based on the negotiation data stored in association with the contract document, and to score the contract document.

(Appendix 19)
A contract management program as described in Appendix 1, in which a processor executes a calculation step (S107, S504) of calculating an evaluation index value for the contracting parties of the contract document based on the exchange document data stored in association with the contract document in the related step.
This makes it possible to calculate an evaluation index value for the contracting parties of the contract document based on the negotiation data stored in association with the contract document, and to score the creditworthiness of the contracting parties.

(Appendix 20)
An information processing device comprising a processor and a memory unit, wherein the processor executes a contract management program according to any one of appendices 1 to 12 and 14 to 19.
This makes it possible to organize and manage the negotiation records and negotiation history at the time of contract conclusion in association with the contract documents.

(Appendix 21)
A method for manufacturing an information processing system including an information processing device having a processor and a memory unit, the method comprising providing a contract management program described in any one of Appendices 1 to 12 and 14 to 19 to the information processing device.
This makes it possible to organize and manage the negotiation records and negotiation history at the time of contract conclusion in association with the contract documents.

(Appendix 22)
An information processing method executed by a computer having a processor and a memory unit, wherein the computer executes a contract management program described in any one of Appendices 1 to 12 and 14 to 19.
This makes it possible to organize and manage the negotiation records and negotiation history at the time of contract conclusion in association with the contract documents.

1 System, 10 Server, 101 Memory unit, 104 Control unit, 106 Input device, 108 Output device, 20 First user terminal, 201 Memory unit, 204 Control unit, 206 Input device, 208 Output device, 30 Second user terminal, 301 Memory unit, 304 Control unit, 306 Input device, 308 Output device, 40 Mail server, 401 Memory unit, 404 Control unit, 406 Input device, 408 Output device

Claims (22)

A contract management program for storing an electronic contract document in a computer having a processor and a storage unit,
The processor,
a contract storage step of storing a contract document relating to the contract;
A document acquisition step of acquiring exchange document data exchanged between one party and another party performing a contract procedure when concluding a contract, which is different from a contract document;
an association step of storing the exchange document data acquired in the document acquisition step in association with the contract document stored in the contract storage step;
Execute
Contract Management Program. the contract storage step is a step of storing the contract document received from the first user,
the document acquisition step is a step of acquiring the exchange document data when the contract document is accepted from the first user in the contract storage step;
The contract management program according to claim 1. the document acquisition step is a step of acquiring the exchange document data based on a URL that identifies the exchange document data received from the first user;
The contract management program according to claim 2. the document acquisition step is a step of acquiring the exchange document data based on a file including the exchange document data received from the first user;
3. The contract management program according to claim 2. The processor,
An importance calculation step of calculating the importance indicating the relevance of candidate document data exchanged between one party and another party performing contract procedures when concluding a contract, unlike the contract document, to the contract procedures;
Execute
The contract management program according to claim 1. the importance calculation step is a step of calculating an importance of the candidate document data based on a file included in the candidate document data;
6. The contract management program according to claim 5. the document acquisition step is a step of acquiring, as the exchange document data, the candidate document data whose importance calculated in the importance calculation step is equal to or greater than a predetermined value;
6. The contract management program according to claim 5. The processor,
a candidate presenting step of presenting one or more candidate document data to a first user based on the importance calculated by the importance calculating step;
a candidate selection step of accepting, from the first user, a selection operation of a predetermined candidate document data from the one or more candidate document data presented in the candidate presentation step;
Run
the document acquisition step is a step of acquiring the predetermined candidate document data selected in the candidate selection step as the exchange document data;
The contract management program according to claim 7. the document acquisition step is a step of acquiring the exchange document data to be classified based on a classification operation performed by a first user on the exchange document data,
The associating step is a step of storing the exchange document data in association with the contract document identified by the classification operation.
The contract management program according to claim 1. The processor,
a second document acquisition step of acquiring second exchange document data related to the exchange document data acquired in the document acquisition step based on destination information included in the exchange document data;
Run
the associating step is a step of storing the second exchange document data acquired in the second document acquiring step in association with the contract document stored in the contract storing step;
The contract management program according to claim 1. the second document acquisition step is a step of searching for and acquiring the second exchange document data including the same destination information as the destination information included in the exchange document data;
The contract management program according to claim 10. The processor,
a second document acquisition step of acquiring second exchange document data related to the exchange document data acquired in the document acquisition step based on subject information included in the exchange document data;
Run
the associating step is a step of storing the second exchange document data acquired in the second document acquiring step in association with the contract document stored in the contract storing step;
The contract management program according to claim 1. The processor,
a presenting step of presenting the second exchange document data acquired in the second document acquisition step as a candidate document to a first user in a selectable manner;
Run
The associating step is a step of storing the candidate document selected by the first user in association with the contract document stored in the contract storing step.
13. The contract management program according to claim 10. The processor,
a generation step of generating a record for storing the contract document in association with the contract document in the contract storage step;
a destination storage step of storing destination information associated with the record generated in the generating step;
Run
the document acquisition step is a step of acquiring the exchange document data including the destination information stored in the destination storage step from a server specified based on the destination information;
The contract management program according to claim 1. The destination storage step is a step of storing the destination information related to a predetermined email address,
the document acquisition step is a step of acquiring the exchange document data including the predetermined email address from a mail server capable of receiving the predetermined email address;
The contract management program according to claim 14. The destination storage step is a step of storing the destination information related to predetermined identification information,
the document acquisition step is a step of acquiring the exchange document data including the predetermined identification information as a destination from a predetermined chat service based on the predetermined identification information;
The contract management program according to claim 14. The processor,
a confirmer receiving step of receiving, from a first user, second user identification information that identifies a second user who approves the contract document received in the contract storage step;
a presentation step of presenting the exchange document data stored in association with the contract document in the association step to the second user before an operation of approving the contract document by the second user;
Run
The contract storage step is a step of storing the contract document received from the first user.
The contract management program according to claim 1. The processor,
a calculation step of calculating an evaluation index value related to the contract document based on the exchange document data stored in association with the contract document in the association step;
Execute
The contract management program according to claim 1. The processor,
a calculation step of calculating an evaluation index value related to the contracting parties of the contract document based on the exchanged document data stored in association with the contract document in the association step;
Execute
The contract management program according to claim 1. An information processing device including a processor and a storage unit,
The processor executes a contract management program according to any one of claims 1 to 12 and 14 to 19.
Information processing device. A method for manufacturing an information processing system including an information processing device having a processor and a storage unit,
providing the information processing device with a contract management program according to any one of claims 1 to 12 and 14 to 19;
A method for manufacturing an information processing system. An information processing method executed by a computer including a processor and a storage unit,
The computer executes a contract management program according to any one of claims 1 to 12 and 14 to 19.
Information processing methods.