Program, method, information processing apparatus, and system

Abstract

To provide a program, a method, an information processing apparatus, and a system capable of comparing a contract document with contract conditions and other information of past contract documents.SOLUTION: A program includes a processor and a storage unit. The program offers, to the computer, a service related to a contract document to be agreed between parties. The processor executes processing including: a contract information receiving step of receiving, from a first user, a first contract document related to a contract; a concluded electronic contract information retrieval step of acquiring a second contract document that has already been concluded; and a comparison result presentation step of presenting, to the first user, a comparison result between the first contract document and the second contract document.SELECTED DRAWING: Figure 11

Description

[Technical Field]

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

[0002] With the development and spread of computer technology, documents that were previously stored on paper 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 relating to digital contracts that includes a creator terminal, a verifier terminal, and a contract management server. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2017-10096 Summary of the Invention [Problem to be solved by the invention]

[0004] In electronic contract procedures between multiple users, there is a problem in that it is not possible to compare the contract document with the contract terms and conditions of past contract documents. Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide a technology for comparing a contract document with the contract terms and conditions of past contract documents. [Means for solving the problem]

[0005] A program comprising a processor and a storage unit, for providing a computer with services relating to a contract document to be agreed upon between the parties, wherein the processor executes a contract acceptance step of accepting a first contract document relating to the contract from a first user, a contract acquisition step of acquiring an already concluded second contract document, and a contract presentation step of presenting to the first user the results of comparing the first contract document with the second contract document. [Effects of the Invention]

[0006] According to the present disclosure, a contract document can be compared with the contract terms and conditions of past contract documents. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 2 is a block diagram showing the functional configuration of the system 1. [Figure 2] FIG. 2 is a block diagram showing the functional configuration of the server 10. [Figure 3] 2 is a block diagram showing the functional configuration of a first user terminal 20. FIG. [Figure 4] 3 is a block diagram showing the functional configuration of a second user terminal 30. FIG. [Figure 5] FIG. 10 is a diagram showing the data structure of a user table 1012. [Figure 6] FIG. 10 is a diagram showing the data structure of a group table 1013. [Figure 7] FIG. 10 is a diagram showing the data structure of a document table 1014. [Figure 8] FIG. 10 is a diagram showing the data structure of a confirmation table 1015. [Figure 9] FIG. 10 is a diagram showing the data structure of an input item table 1016. [Figure 10] FIG. 10 is a diagram showing the data structure of a contract group table 1017. [Figure 11] 10 is a flowchart showing the operation of a contract creation process. [Figure 12] 10 is a flowchart showing the operation of a contract confirmation process. [Figure 13]10 is a screen example showing the operation of a contract creation process. [Figure 14] 10 is an example of a screen showing a confirmation request message sent to the second user terminal 30. [Figure 15] 10 is a screen example showing the operation of a contract confirmation process. [Figure 16] 10 is an example of a screen showing a conclusion completion message notified to the first user terminal 20. [Figure 17] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all drawings describing the embodiments, common components are designated by the same reference numerals, and repeated description will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each drawing is a schematic diagram and is not necessarily a precise illustration.

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

[0010] 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, and the second user terminal 30, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer will be omitted.

[0011] <Server 10 configuration> The server 10 includes an information processing device that provides an electronic contract conclusion service between multiple users. The server 10 includes an information processing device that provides a service for storing and managing contract information concluded between multiple users. In addition, the server 10 includes any information processing service that stores and manages contract information. The server 10 includes a storage unit 101 and a control unit 104 .

[0012] <Configuration of the storage unit 101 of the server 10> The storage 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 , and a contract group table 1017 .

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

[0014] The user table 1012 is a table that stores and manages information about member users (hereinafter referred to as users) who use the service. When a user registers to use 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 the user who uses the 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 user ID, user name, email address, group ID, and approval authority. FIG. 5 is a diagram showing the data structure of the user table 1012. As shown in FIG.

[0015] The user ID is an item that stores user identification information for identifying a user. The user identification information is an item that is set with a unique value 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 the group to which the user belongs. Groups are defined by a group table 1013, which will be described later, and a user may belong to multiple groups. The approval authority is an item that stores authority information regarding the user's approval of the conclusion of a contract. For a user who has the authority to approve the conclusion of a contract (approval authority), information indicating that the user has the authority to approve the conclusion of a contract, such as True, is stored. On the other hand, for a user who does not have the authority to approve the conclusion of a contract, information indicating that the user does not have the authority to approve the conclusion of a contract, such as False, blank, or null value, is stored. The system may be configured so that approval authority can be set according to the contract information. For example, a system may be configured so that user A has approval authority for specific contract information A but does not have approval authority for specific contract information B. The system may be configured so that approval authority can be set according to the type of contract information (contract information type), such as a confidentiality agreement, a joint research agreement, a contract for work, etc. For example, the system may be configured so that user A has approval authority for a confidentiality agreement but does not have approval authority for a contract for work. Alternatively, the system may be configured to store multiple levels (levels, ranks) of authority information depending on the user's department, government office, etc. For example, information such as C for temporary staff, B for regular employees, A for managers, and S for executives may be stored in the approval authority field, and only users with approval authority of a predetermined rank or higher (for example, A or higher for a confidentiality agreement) may be able to approve the conclusion of a contract depending on the contract type information, contract amount, etc. of the contract information.

[0016] The group table 1013 is a table that stores and manages 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 group ID, group name, and administrator ID. FIG. 6 is a diagram showing the data structure of the group table 1013. As shown in FIG.

[0017] 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 that stores the user identification information of a user who has administrator privileges in a group. A user with administrator privileges can arbitrarily define and set a user who has a certain level of status or authority in a group such as an organization.

[0018] 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 the document ID as a primary key and columns of document ID, document data, and creator ID. FIG. 7 is a diagram showing the data structure of the document table 1014. As shown in FIG.

[0019] 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 document data is an item that stores contract information (binary or text data) of the contract document related to the conclusion of the contract. Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). Creator ID is an item for storing user identification information for identifying the user who created the contract information.

[0020] The confirmation table 1015 is a table that stores and manages information (checker information) including the email addresses of users who will be checkers of 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. 8 is a diagram showing the data structure of the confirmation table 1015.

[0021] The document ID is an item for storing document identification information of the contract information to be checked by the checker. The confirmation order is an item for storing information regarding the confirmation order when the contract information is confirmed by the confirmer. The contract information stored by the creator is circulated to the confirmers in the confirmation order and confirmed. The checker email address is an item that stores 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 to use the service disclosed herein. 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 that stores confirmation identification information for identifying whether or not the checker has completed the procedure for checking the contract information. When the checker has completed checking the contract information, information indicating that the check 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 verifyer. 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 checker performed the procedure for checking the contract information. Specifically, the date and time when the check identification information was stored in the check flag item is stored.

[0022] The input item table 1016 is a table that stores and manages information (input item information) related to input items associated with electronic contract information. The input item table 1016 is a table having columns for input item ID, document ID, inputter ID, input data, input rule, and date and time. FIG. 9 is a diagram showing the data structure of the input item table 1016.

[0023] 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 that stores the user identification information or email address of the inputter who entered 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 email address of the verifying person, 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 rules for input fields. The input rules can be data types such as date, datetime, text, and integer, as well as the number of characters in the case of text, regular expressions for text, and other input rule information related to any input field. 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 inputter.

[0024] 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, tag, label, etc. The contract group table 1017 is a table having columns for document ID and cabinet ID. FIG. 10 is a diagram showing the data structure of the contract group table 1017.

[0025] 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. The cabinet ID is classification information for managing and classifying contract information.

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

[0027] 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, enters information into a predetermined 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 the user information in the user table 1012, the service provider may conduct 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 may be automatically set by the user registration control unit 1041.

[0028] The contract preparation unit 1042 executes the contract preparation process, the details of which will be described later.

[0029] The contract confirmation unit 1043 executes a contract confirmation process, the details of which will be described later.

[0030] <Configuration of First User Terminal 20> The first user terminal 20 is an information processing device operated by a user who uses a service. The first user terminal 20 may be, for example, a desktop personal computer (PC) or a laptop PC, or may be a mobile terminal such as a smartphone or a tablet. It may also 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 .

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

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

[0033] The application program 2012 may be stored in advance in the storage unit 201, or may be configured to be downloaded from a web server or the like 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.

[0034] <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.

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

[0036] <Configuration of 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 .

[0037] <Configuration of second user terminal 30> The second user terminal 30 is an information processing device operated by a user who uses a service. The second user terminal 30 may be, for example, a desktop personal computer (PC) or laptop PC, or may be a mobile terminal such as a smartphone or tablet. It may also 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 .

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

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

[0040] The application program 3012 may be stored in advance in the storage unit 301, or may be configured to be downloaded from a web server or the like 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 in the second user terminal 30.

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

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

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

[0044] <System 1 Operation> Each process of the system 1 will be explained below. FIG. 11 is a flowchart showing the operation of the contract creation process. FIG. 12 is a flowchart showing the operation of the contract confirmation process. FIG. 13 is an example of a screen showing the operation of the contract creation process. FIG. 14 is an example of a screen showing a confirmation request message sent to the second user terminal 30. In FIG. FIG. 15 is an example of a screen showing the operation of the contract confirmation process. FIG. 16 is an example of a screen showing a conclusion completion message sent to the first user terminal 20.

[0045] In the present disclosure, the contract creation process and contract confirmation process in the server 10 will be described below.

[0046] <Contract Creation Process> The contract creation process is a process in which the creator creates electronic contract information and sends it to the confirmer.

[0047] 13 is an example of a screen showing the operation of the contract creation process. 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, and 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, and 534, a send button 540, comparison results 550, 551, and 552, correction suggestions 561 and 562, correction reflection buttons 5611 and 5621, and advice 571 and 572.

[0048] <Outline of contract creation process> The contract creation process 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, searches for electronic contract information that has already been concluded in the past, presents the results of a comparison with the previously concluded electronic contract information, 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.

[0049] <Details of contract creation process> The contract creation process will be described in detail below.

[0050] In step S101, the contract creation unit 1042 of the server 10 executes a contract acceptance step of accepting a first contract document relating to a contract from a first user. Specifically, the contract creation unit 1042 of the server 10 receives, from the creator, first contract information that is the subject of a contract to be concluded between the creator and the verifying party. Specifically, the first user operates the input device 206 of the first user terminal 20 to create first contract information including first document data related to the contract. The first document data can be in any data format such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language) and can be included in the first contract information. The first user operates the input device 206 of the first user terminal 20 and transmits the created first 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 first document data, and stores them in the creator ID and first 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 first contract information in the document table 1014.

[0051] Document data 531 stored in document table 1014 is displayed on screen 50 for creating contract information.

[0052] In step S102, the first user operates the input device 206 of the first user terminal 20 to select and identify a user who will be the checker (recipient) of the first contract information. In the present disclosure, it is assumed that the first user selects and identifies 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 checker, and sends it to the server 10. The contract creation unit 1042 of the server 10 stores the received email address and the document ID of the first contract information created and stored in step S101 in the checker email address and document ID items in the confirmation table 1015, respectively, and associates the first contract information with the email address of the second user and stores them. The first user may also 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 S102, the first user may be able to select and set multiple users to be the checkers. In this case, the value of the confirmation order field for the users to be the checkers is incremented by one and stored according to the selection order. This sets the circulation order of the checkers in the contract confirmation process, which will be described later. Note that setting the circulation order is not essential.

[0053] <Processing for obtaining concluded contract information> In step S103, the contract preparation unit 1042 of the server 10 executes a contract acquisition step of acquiring the concluded secondary contract document. Specifically, the contract creation unit 1042 of the server 10 searches for contract information by referring to the document table 1014, based on the first contract information received in step S101 and the information of the confirmer received in step S102. Based on the search results, contract information (second contract information) to be compared in the comparison result presentation process described below is identified. In the present disclosure, an example will be described in which the contract creation unit 1042 of the server 10 searches for contract information for which a contract has been concluded (contract confirmation processing has been executed by all checkers) from among the contract information stored in the document table 1014. Specifically, the contract creation unit 1042 of the server 10 searches for contract information for which a value of True is stored in the confirmation flag field of the checker information associated with the contract information and stored in the confirmation table 1015 from among the contract information stored in the document table 1014. The contract creation unit 1042 of the server 10 may search for contract information for which the conclusion of a contract has not been completed among the contract information stored in the document table 1014. Specifically, the contract creation unit 1042 of the server 10 may search for contract information among the contract information stored in the document table 1014, regardless of the value of the confirmation flag item of the confirmer information associated with the contract information and stored in the confirmation table 1015. For example, all contract information stored in the document table 1014 may be acquired as the search result.

[0054] In step S103, the contract acquisition step executes a step of acquiring a second contract document similar to the first contract document. Specifically, the contract creation unit 1042 of the server 10 searches the document data (search document data) item in the document table 1014 based on the first document data (target document data) included in the first contract information received in step S101, and obtains the record of the second contract information that includes similar document data. For example, the contract creation unit 1042 of the server 10 applies processing such as morphological analysis to the sentences of the contract content included in the target document data to extract keywords. The keywords may be weighted based on the frequency of appearance, etc. The contract creation unit 1042 of the server 10 searches for document data items in the document table 1014 based on the keywords, applies similar processing such as morphological analysis to the retrieved document data, and calculates indices of similarity, such as the degree of agreement or difference between terms between the target document data and one or more retrieved document data. Note that the similarity may be calculated using any machine learning model, deep learning model, artificial intelligence model, etc. The contract creation unit 1042 of the server 10 acquires and identifies, as a search result, the second contract information related to the searched document data whose similarity is equal to or greater than a predetermined value.

[0055] In step S103, the contract acquisition step executes a step of acquiring a second contract document of a contract type that is the same as or similar to the contract type of the first contract document. Specifically, the contract creation unit 1042 of the server 10 identifies the contract type (target contract type) of the target document data based on the first document data (target document data) included in the first contract information received in step S101. The contract type is information that identifies the type or category of contract that the contract information targets, such as a confidentiality agreement, lease agreement, or purchase contract. For example, the contract type is identified based on the title (heading) of the target document data. Note that the contract type may be identified in response to an input operation by any user other than the first user, and may be stored in association with the contract information related to the target document data. The contract creation unit 1042 of the server 10 searches for the document data (searched document data) item in the document table 1014 based on the target contract type, and acquires a record of the second contract information including document data of the same or similar contract type. Specifically, the contract creation unit 1042 of the server 10 identifies the contract type (searched contract type) based on the searched document data in the same way as the target document data, and compares the target contract type with the searched contract type to acquire a record of the second contract information including document data of the searched contract type that is the same as or similar to the target contract type. For example, if the character strings of the target contract type and the searched contract type are an exact match, the contract types may be determined to be the same. Also, if the similarity (an index representing similarity such as the Levenshtein distance) between the character strings of the target contract type and the searched contract type is equal to or greater than a predetermined value, the target contract type and the searched contract type may be determined to be similar. Additionally, predetermined contract types may be considered to be similar contract types. For example, a contract type related to a "confidentiality agreement" and a contract type related to a "joint research agreement" may be considered to be similar contract types. The contract types being the same or similar may be determined according to a predetermined rule, or may be managed using a table (not shown) or the like.

[0056] In step S103, a contract acquisition step executes a step of acquiring a second contract document previously concluded between the first user and the second user. Specifically, the contract creation unit 1042 of the server 10 searches for the creator ID in the document table 1014 and the checker's email address in the confirmation table 1015 based on the first user ID 2011 and the email address of the second user identified in step S102 (the checker's email address stored in the confirmation table 1015). This allows the contract creation unit 1042 of the server 10 to search for contract information previously concluded between the first user and the second user, and acquire it as second contract information. In the present disclosure, a configuration in which contract information in which a first user is involved as a creator and a second user as a checker is searched for and acquired is described as an example, but this is not limited to this. For example, a configuration in which contract information in which a first user or a second user is involved as a creator, checker, or other related party is searched for and acquired as second contract information is also acceptable.

[0057] In step S103, the contract acquisition step executes a step of acquiring a second contract document previously concluded between the first user and another user who belongs to the same or similar business type as the second user. Specifically, the contract creation unit 1042 of the server 10 searches the creator ID in the document table 1014 based on the first user ID 2011, and acquires and specifies the second contract information. Next, the contract creation unit 1042 of the server 10 identifies the industry to which the second user belongs (target industry) by referring to a table or the like that stores email addresses or domain names (not shown) associated with industries, based on the email address of the second user identified in step S102 (the confirming person's email address in the confirmation table 1015). Note that the identified industry may include industries similar to the identified industry. For example, the industry of legal affairs may include the industry of patent affairs as a similar industry. The contract creation unit 1042 of the server 10 searches for the document ID in the confirmation table 1015 based on the document ID of the acquired contract information, and acquires the checker email address field. The contract creation unit 1042 of the server 10 refers to a table (not shown) and, based on the checker email address, identifies the industry to which the user associated with the checker email address belongs (search industry). For each contract information, the contract creation unit 1042 of the server 10 identifies second contract information in which the search industry is included in the target industry. This allows the contract creation unit 1042 of the server 10 to obtain contract information that the creator has previously concluded with other users who belong to the same or similar industry as the user related to the verifying user, and identify it as second contract information.

[0058] In step S103, a contract acquisition step executes a step of acquiring a second contract document concluded within a predetermined period. Specifically, the contract creation unit 1042 of the server 10 searches for and identifies records of verifyer information whose confirmation table date and time field is included in a predetermined period from the current date and time, such as within the last six months or one year. Note that, when there are multiple verifyer information records with the same document ID, the contract creation unit 1042 of the server 10 may be configured to search only for records of verifyer information with the most recent date and time (the date and time when the last verifyer completed the contract confirmation process for one contract information, i.e., the date when all verifyers agreed to and concluded the contract for one contract information). The contract creation unit 1042 of the server 10 searches the document ID item of the document table 1014 based on the document ID included in the retrieved checker information, acquires the contract information, and identifies it as the second contract information. As a result, the contract creation unit 1042 of the server 10 can acquire contract information included in a predetermined period, such as within the last six months or one year from the current date and time, and identify it as the second contract information.

[0059] In step S103, the contract acquisition step executes a step of acquiring a second contract document, which is the previous contract document of the first contract document, when the first contract document is a renewal contract. Specifically, the contract creation unit 1042 of the server 10 acquires and identifies the document ID of the contract information related to the first contract information received in step S101 by referring to a column (not shown) that specifies the relationship between contracts, such as parent-child relationships, for contracts such as renewal contracts and amendment contracts in the document table 1014. Alternatively, the contract creation unit 1042 of the server 10 may be configured to acquire and identify the document ID of the contract information related to the first contract information by searching the document data items in the document table 1014 based on the description of the original contract, basic contract, etc. mentioned in the first document data included in the first contract document. In the present disclosure, as an example, when the first contract information received in step S101 is a renewal contract, the document ID of the previous contract information is acquired and identified. Note that the previous contract information does not necessarily have to be the most recent contract information, and in the case of a renewal contract spanning multiple generations, it includes contract information of any parent generation. The contract creation unit 1042 of the server 10 searches the document ID item in the document table 1014 based on the identified document ID, acquires the contract information, and identifies it as the second contract information. As a result, the contract information that is the basis of the contract information that is the renewed contract accepted in step S101 can be acquired and identified as the second contract information.

[0060] Alternatively, the concluded contract information acquisition process may be configured to search for, acquire, and identify the secondary contract document by combining one or more of the search conditions already mentioned.

[0061] <Comparison result presentation process> In step S104, the contract preparation unit 1042 of the server 10 executes a contract presentation step of presenting the comparison result between the first contract document and the second contract document to the first user. Specifically, the contract creation unit 1042 of the server 10 compares the first contract information received in step S101 with one or more pieces of second contract information identified in step S103. Specifically, the contract creation unit 1042 of the server 10 compares the first document data included in the first contract information with the second document data included in the second contract information, and extracts differences (differences). The contract creation unit 1042 of the server 10 displays the differences in the comparison result 550 on the screen 50. Note that the comparison result 550 may include, for example, information summarizing the similarities and differences in the contract information as a whole (summary information) rather than information on the parts related to the multiple differences. For example, the summary information can be generated based on the information on the parts related to the multiple differences by using artificial intelligence technology such as any rule-based model, machine learning model, deep learning model, or large-scale language model (LLM).

[0062] In step S104, the contract presentation step executes a step of presenting to the first user information indicating whether the first contract document is advantageous or disadvantageous relative to the second contract document. The contract presentation step executes a step of presenting to the first user information indicating whether each clause or provision of the first contract document is advantageous or disadvantageous relative to the second contract document. Specifically, the contract creation unit 1042 of the server 10 calculates information indicating whether the first contract information is advantageous or disadvantageous compared to the second contract information for each difference based on the extracted differences. For example, if the upper limit of the compensation provision for damages included in the second document data is 5 million yen, and the upper limit of the compensation provision for damages included in the first document data is 10 million yen, the first contract information is calculated to be more advantageous than the second contract information. For example, if the upper limit of the compensation provision for damages included in the second document data is 5 million yen, and the upper limit of the compensation provision for damages included in the first document data is 3 million yen, the first contract information is calculated to be at a disadvantage compared to the second contract information. In addition, information indicating whether something is advantageous or disadvantageous can be output based on the extracted differences by using artificial intelligence techniques such as any rule-based model, machine learning model, deep learning model, large-scale language model (LLM), etc. Information regarding the comparison results, including information indicating whether the information is advantageous or disadvantageous, can be output as follows: for the entire contract information, for each clause or article that makes up the contract information, or for each section or part that makes up the contract information. · The entire contract information (whether the entire first contract information is advantageous or disadvantageous compared to the entire second contract information) Each clause or provision that makes up the contract information (whether clause ●●, clause ●● of the first contract information is more or less favorable than clause ●●, clause ●● of the second contract information) Each part or section that makes up the contract information (whether the "···" on page ●●, line ●● of the first contract information is advantageous or disadvantageous compared to the "···" on page ●●, line ●● of the second contract information) In addition, information indicating whether the contract information as a whole is advantageous or disadvantageous can be output based on the multiple extracted differences by utilizing artificial intelligence technologies such as any rule-based model, machine learning model, deep learning model, large-scale language model (LLM), etc. The contract creation unit 1042 of the server 10 displays information about the comparison results, including information indicating whether the comparison is advantageous or disadvantageous, on the comparison results 551 and 552 on the screen 50.

[0063] <Proposed correction process> In step S104, the contract preparation unit 1042 of the server 10 executes a correction suggestion step of suggesting correction candidates for the first contract document based on the comparison result with the second contract document. Specifically, the contract creation unit 1042 of the server 10 calculates correction candidates for the first contract information based on information indicating the calculated comparison results by utilizing artificial intelligence technologies such as any rule-based model, machine learning model, deep learning model, large-scale language model (LLM), etc. For example, the contract creation unit 1042 of the server 10 calculates correction candidates for the first contract information based on the extracted differences and on information indicating whether the first contract information is advantageous or disadvantageous compared to the second contract information for each difference, by utilizing artificial intelligence technology such as any rule-based model, machine learning model, deep learning model, large-scale language model (LLM), etc. For example, if the upper limit amount of the compensation provision for damages included in the second document data is 5 million yen, and the upper limit amount of the compensation provision for damages included in the first document data is 3 million yen, correction suggestions 561 and 562 indicating that the upper limit amount of the compensation provision for damages in the first contract information should be corrected to 5 million yen are displayed on screen 50. Correction suggestions can be output as follows: for the entire contract information, for each clause or article that makes up the contract information, or for each section or part that makes up the contract information. - Proposal of corrections for the entire contract information (perhaps ●● in the first contract information should be corrected to ●●) - Proposals for amendments to each clause or clause that makes up the contract information (Clause ●●, clause ●● in the first contract information could be amended to clause ●●, clause ●●) - Proposal of corrections for each part of the contract information (perhaps correcting the "···" in line ●● on page ●● of the first contract information to "···") Each correction candidate can be output by utilizing artificial intelligence technology such as any rule-based model, machine learning model, deep learning model, large-scale language model (LLM), etc., based on information regarding the comparison results, including information indicating whether the entire contract information, each clause or article that makes up the contract information, and each section or part that makes up the contract information are advantageous or disadvantageous.

[0064] In step S104, a correction suggestion step is executed to suggest correction candidates including a correction group including a plurality of correction portions for the first contract document. Specifically, the contract creation unit 1042 of the server 10 proposes a modification candidate that, for example, modifies contract condition A to favorably become contract condition A1 at the first modification point of the first contract information, and modifies contract condition B to unfavorably become contract condition B1 at the second modification point of the first contract information. For example, if the upper limit of the compensation provision for damages included in the second document data is 5 million yen, and the upper limit of the compensation provision for damages included in the first document data is 3 million yen, a revision candidate (favorable revision candidate) can be proposed indicating that the upper limit of the compensation provision for damages in the first contract information should be changed to 5 million yen, and a revision candidate (unfavorable revision candidate) can be proposed indicating that the conditions under which damages will be incurred should be limited. This allows for proposal of amendments that are easy to agree on and do not unilaterally put one party at an advantage or disadvantage.

[0065] In step S104, the contract preparation unit 1042 of the server 10 executes a correction receiving step of receiving corrections to the first contract document from the first user. Specifically, the first user selects correction reflection buttons 5611, 5621 by operating the input device 206 of the first user terminal 20. As a result, a request to reflect the proposed correction content related to correction candidates 561, 562 in the first contract information is sent to the server 10. Upon receiving the request, the contract preparation unit 1042 of the server 10 corrects the content of the first document data included in the first contract information based on the correction candidates. Specifically, the contract preparation unit 1042 of the server 10 reflects the correction content in the first document data. For example, if correction suggestion 561 is proposed indicating that the upper limit amount of the compensation provision regarding damages in the first contract information should be revised to 5 million yen, selecting the Reflect Correction button 5611 will correct the upper limit amount of the compensation provision regarding damages included in the first document data of the first contract information to 5 million yen. The contract creation unit 1042 of the server 10 stores the corrected first document data in the document data item of the target record in the document table 1014. As a result, the correction content is reflected in the content of the first document data of the first contract information accepted in step S101 and stored.

[0066] <Advice processing> In step S104, the contract creation unit 1042 of the server 10 executes an advice proposal step in which, based on the amendments received in the amendment reception step, the first user is proposed advice information indicating key points to consider when negotiating to communicate the amendments to the contracting party. Specifically, the contract creation unit 1042 of the server 10 generates advice information for conveying the details of the corrections to the contracting party (second user) in accordance with the selected correction candidates 561, 562, and transmits the advice information to the first user terminal 20. Upon receiving the advice information, the control unit 204 of the first user terminal 20 displays and presents the advices 571, 572 on the display 2081 of the first user terminal 20. For example, when the upper limit amount of the compensation provision regarding damages in the first contract information is amended from 3 million yen to 5 million yen and the conditions under which damages will occur are also amended, advice 571 and 672 are displayed and presented to the second user, the other party to the contract, to convey, for example, "Since the transaction amount this time is larger than the previous time, it is not appropriate that the upper limit amount of the compensation provision regarding damages is less favorable than the previous time." This allows the first user to receive suggested advice information that can be used as a reference when negotiating with the other party when amending the contract document, allowing the first user to smoothly negotiate the contract with the second user.

[0067] Note that, in the present disclosure, as an example, a case has been disclosed in which various processes such as a process for acquiring already-concluded contract information, a process for presenting comparison results, a process for proposing amendments, and a process for giving advice are provided to a first user in the contract creation process, but the present invention is not limited to this. For example, when contract information such as step S303 of the contract confirmation process is presented to a second user, various processes such as a process for acquiring already-concluded contract information, a process for presenting comparison results, a process for proposing amendments, and a process for giving advice may be provided to the second user instead of the first user.

[0068] In step S105, 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 to set multiple input items for the contract information created and stored in step S101. The input items can be any input item, such as a seal field for stamping seal data, an input field for entering text data such as signature data, a check box field for selecting check items, and a date field for entering a date. The first user operates the input device 206 of the first user terminal 20 or the like to send a request to add an input item to the server 10. Upon receiving the request, the contract creation unit 1042 of the server 10 stores the document ID of the 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.

[0069] In step S106, the first user sets input rules for each input item to be added. The first user operates the input device 206 of the first user terminal 20 or the like to specify input rules for each piece of input item information set in step S103 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 piece of input item information in the input item table 1016. This makes it possible to set input rules for each input item.

[0070] In step S107, the contract creation 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 S106. For example, the first user may input input data for a number used to manage 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 for the contract conclusion date of the contract information into an input item in which a contract conclusion date is set. After completing input of 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 in the input item table 1016 identified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

[0071] 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.

[0072] 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 field in the confirmation table 1015 and identifies the user (first confirmation user) who will be the first checker and has the smallest value stored in the confirmation order field. In the present disclosure, the first confirmation user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's email address 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 sent to the second user includes a URL (Uniform Resource Locator) containing a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a string obtained by arbitrarily encrypting the document ID, or a string that can identify the document ID by referencing a table (not shown). The URL may also include information for identifying the second user. For example, if the second user is not registered with the service disclosed herein, the URL must include information for identifying the second user.

[0073] If the first user sets an access code for the second user, the first user will separately communicate the access code to the second user by means of email, etc. This means that even if a third party obtains the message notified to the second user, the third party will not be able to execute the contract confirmation process unless they obtain the access code.

[0074] 14 is an example of a screen showing a message notified to the second user terminal 30. The message screen 60 displayed on the display 3081 of the second user terminal 30 includes a message 61 and information about a URL 62 including a document ID for identifying contract information.

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

[0076] 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 allocation, 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 allocation, and the item "stamp" is drawn as the input item type.

[0077] Additionally, although the present disclosure has disclosed as an example a configuration in which the contract information and various input information are stored in various tables of the server 10 in each step, the present disclosure is not limited to this. For example, in the transmission step of step S108, the contract information and various input information input by the creator may be stored together in various tables of the server 10.

[0078] <Contract confirmation process> The contract confirmation process is a process in which the confirmer confirms the contents of the electronic contract information received from the creator.

[0079] <Outline of contract confirmation process> The contract confirmation process is a series of processes that accepts access from the confirmer, presents the confirmer with a confirmation screen that displays the contract information, accepts input data for input fields from the confirmer, and accepts data related to confirmation of the contract information from the confirmer.

[0080] <Details of contract confirmation process> The details of the contract confirmation process are explained below.

[0081] In step S301, the second user who will 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 using 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.

[0082] 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 to input the access code and transmit 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 second user's record in the confirmation table 1015, and if they match, continues the contract confirmation process. On the other hand, if they do not match, stops the contract confirmation process. Note that the authentication process using the access code may be omitted.

[0083] 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 acquires 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 acquires 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 acquires input item information associated with the contract information.

[0084] 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 according to the present disclosure, the second user must be identified from the URL. For example, the URL may include the second user's email address, user ID, or the like as information for identifying the second user.

[0085] In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, checker information (information that identifies the second user), and input item information, and transmits the generated confirmation screen to the second user terminal 30.

[0086] 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 the contract information displayed on the display 3081 of the second user terminal 30 and approves it. In addition, the confirmation screen presented to the second user may be configured to be presented to the second user in the language specified for the confirmer, based on the language information stored in the language data item of the second user's record in confirmation table 1015.

[0087] 15 is an example of a confirmation screen showing the operation of the contract confirmation process. 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 indicating 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.

[0088] 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 or the like to input data into the input items 732, 733, 734, and 735 set in the contract information. In the present disclosure, input by the second user into the input item 736 is not assigned, and therefore, it is visually displayed that the second user cannot input input data into the input item 736.

[0089] In step S305, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to and approve the conclusion of the contract in the contract information received 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 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 relevant record. For example, if 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 relevant record. If 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 relevant 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 identified 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.

[0090] The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all the checkers. Specifically, the contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed 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 has been performed by all the confirmers, the contract confirmation unit 1043 of the server 10 transmits a message to the first user notifying that the contract confirmation process has been completed. Similarly, the contract confirmation unit 1043 of the server 10 may transmit a message to the second user notifying that the contract confirmation process has been completed.

[0091] Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the first user's email address by a communication means such as email notifying the first user that the second user has completed confirmation of the contract information. In other words, the message notifies the first user 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 endpoint including a document ID for identifying the contract information.

[0092] 16 is an example of a 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 such as a message 81 and a URL 82 including a document ID for identifying contract information.

[0093] 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 of 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 endpoint including a document ID for identifying the contract information.

[0094] 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 for inquiry to the server 10. The contract confirmation unit 1043 of the server 10 references the contract information, generates a web page for inquiry, 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.

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

[0096] Specifically, the contract confirmation unit 1043 of the server 10 acquires the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 then searches the group ID item in the group table 1013 based on the acquired group ID item, acquires the administrator ID item, identifies a user with authority equivalent to that of 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 has been completed.

[0097] <Electronic signature processing> An electronic signature process may be included in step S305. In response to the instruction to approve the conclusion of the contract received from the second user in step S305, the contract confirmation unit 1043 of the server 10 affixes an electronic signature indicating that the conclusion of the contract of the contract information has been approved to the contract information received from the first user, and stores the resulting digital signature. Specifically, the contract confirmation unit 1043 of the server 10 adds a digital signature to the contract information based on the received request and stores it. The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID, and acquires the contract information. The contract confirmation unit 1043 of the server 10 affixes an electronic signature to the acquired contract information and stores it in the document data item of the document table 1014. The contract confirmation unit 1043 of the server 10 may update (overwrite) the document data item with the contract information affixed with the electronic signature, or may store the contract information before affixing the electronic signature in a separate storage device (not shown). The contract confirmation unit 1043 of the server 10 may include any of the following information in the electronic signature: document ID, email address of the first user, email address of the second user, approval date and time, confirmation date and time, authentication method for approval date and time, authentication method for confirmation date and time, input data value 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 to the contract information indicating that the second user has approved the conclusion of the contract of the contract information, and stores the digital signature. This makes it possible to prevent spoofing or tampering of the contract information by a third party.

[0098] <Basic computer hardware configuration> 17 is a block diagram showing the basic hardware configuration of a computer 90. The computer 90 includes at least a processor 901, a main memory device 902, an auxiliary memory device 903, and a communication IF 991 (interface), which are electrically connected to one another by a communication bus 921.

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

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

[0101] The auxiliary storage device 903 is a storage device for saving data and programs, such as a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, or a semiconductor memory.

[0102] The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using wired or wireless communication standards. 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, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks (e.g., Wi-Fi (registered trademark)) that can connect to the Internet via a predetermined access point. In the case of a wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), and Bluetooth (registered trademark). In the case of a wired connection, the network also includes a direct connection using a USB (Universal Serial Bus) cable, etc.

[0103] It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration across multiple computers 90 and interconnecting them via a network. In this way, the computer 90 is a concept that includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

[0104] <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. 17) of the computer 90. The computer comprises at least the functional units of a control unit, a storage unit, and a communication unit.

[0105] The functional units of the computer 90 can also be realized by distributing all or part of the functional units among multiple computers 90 interconnected via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

[0106] The control unit is realized by the processor 901 reading out various programs stored in the auxiliary storage device 903, expanding them in the main storage device 902, and executing processing in accordance with the programs. The control unit can realize functional units that perform various types of information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0107] 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. Furthermore, the processor 901 can allocate a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with the programs. Furthermore, the control unit can cause the processor 901 to execute processes for adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

[0108] A database refers to a relational database, which manages data sets called masters and tables in a tabular format structurally defined by rows and columns, by relating them to each other. In a database, a table is called a table, a 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. Typically, each table and each master has a column set as a primary key to uniquely identify a record, 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 specific tables and masters stored in the storage unit according to 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.

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

[0110] The communication unit is realized by the communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input the information to the control unit. The control unit can cause the processor 901 to execute information processing on the received information in accordance with various programs. In addition, the communication unit can transmit information output from the control unit to other computers 90.

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

[0112] (Appendix 1) A program comprising a processor and a storage unit, for providing a computer with services relating to a contract document to be agreed upon between the parties, wherein the processor executes a contract acceptance step (S101) for accepting a first contract document relating to a contract from a first user, a contract acquisition step (S103) for acquiring an already concluded second contract document, and a contract presentation step (S104) for presenting to the first user the results of a comparison between the first contract document and the second contract document. This allows the first user to refer to the past contract history of the second contract document, such as the contract conditions, for the first contract document that the first user is about to enter into with the second user.

[0113] (Appendix 2) The program according to Appendix 1, wherein the contract presentation step (S104) is a step of presenting to the first user information indicating whether the first contract document is advantageous or disadvantageous compared to the second contract document. This allows the first user to check whether the first contract document that he is about to enter into with the second user is more advantageous or less advantageous than the contract terms and conditions of past second contracts and the like.

[0114] (Appendix 3) The program described in Appendix 1, wherein the contract presentation step (S104) is a step of presenting to the first user information indicating whether each clause or provision of the first contract document is advantageous or disadvantageous compared to the second contract document. This allows the first user to check whether each clause or provision of the first contract document that the second user is about to enter into with the second user is more favorable or less favorable than the contract terms of past second contracts, etc.

[0115] (Appendix 4) The program according to appendix 1, wherein the contract acquisition step (S103) is a step of acquiring a second contract document similar to the first contract document. This allows the first user to refer to the contract history of the second contract document of a similar contract type, such as the contract conditions, for the first contract document. A second contract document that is more similar to the first contract document can be used as reference information when concluding the contract.

[0116] (Appendix 5) The program according to appendix 1, wherein the contract acquisition step (S103) is a step of acquiring a second contract document of a contract type that is the same as or similar to the contract type of the first contract document. This allows the first user to refer to the contract history of the second contract document, such as the contract conditions, of the same or similar contract type, for the first contract document. The second contract document, which is concluded under conditions more similar to the first contract document, can be used as reference information when concluding the contract.

[0117] (Appendix 6) The program is used for business related to a contract document concluded between a first user and a second user, and the contract acquisition step (S103) is a step of acquiring a second contract document previously concluded between the first user and the second user, the program described in Appendix 1. This allows the first user to refer to the contract history of the second contract document, such as the contract conditions of the second contract document that was previously concluded with the second user, for the first contract document. The second contract document, which is concluded under conditions more similar to the first contract document, can be used as reference information when concluding the contract.

[0118] (Appendix 7) The program is used for work related to a contract document concluded between a first user and a second user, and the contract acquisition step (S103) is a step of acquiring a second contract document that the first user has previously concluded with another user who belongs to the same or similar industry as the second user, as described in Appendix 1. This allows the first user to refer to the contract history of the second contract document, such as the contract terms and conditions, that have been concluded in the past with other users in the same or similar industry as the second user, when it comes to the first contract document. The second contract document, which is concluded under conditions more similar to the first contract document, can be used as reference information when concluding the contract.

[0119] (Appendix 8) The program according to appendix 1, wherein the contract acquisition step (S103) is a step of acquiring a second contract document concluded within a predetermined period. This allows the first user to refer to the contract record of the second contract document, such as the contract conditions, concluded within a predetermined period, for the first contract document. For example, you can use secondary contract documents concluded within the last six months or one year as the comparison subject. Older contract documents can be excluded from the comparison subject.

[0120] (Appendix 9) The program according to Appendix 1, wherein the contract acquisition step (S103) is a step of acquiring a second contract document, which is the previous contract document of the first contract document, when the first contract document is a renewal contract. This allows the first user to refer to the contract history, such as the contract conditions of the previous contract, of the renewal contract, for the first contract document that the first user is about to enter into with the second user.

[0121] (Appendix 10) The program according to Appendix 1, wherein the processor executes a correction suggestion step (S104) of suggesting correction candidates for the first contract document based on the comparison result with the second contract document. This allows the first user to receive suggested revision candidates by referring to the contract conditions and the like of past second contract documents.

[0122] (Appendix 11) The program according to Appendix 10, wherein the correction suggestion step (S104) is a step of proposing correction candidates including a correction group including multiple correction locations for the first contract document. This allows the first user to receive suggestions for amendments that are easy to agree on so that neither party is unilaterally put at a disadvantage or advantage, for example, amending contract condition A to be favorable to contract condition A1 at the first amendment point, and amending contract condition B to be unfavorable to contract condition B1 at the second amendment point.

[0123] (Appendix 12) A program described in Appendix 1, in which a processor executes an amendment receiving step (S104) in which amendments to a first contract document are received from a first user, and an advice proposing step (S104) in which, based on the amendments received in the amendment receiving step, the processor proposes advice information to the first user indicating key points to consider when negotiating to convey the amendments to the contracting party. This allows the first user to receive suggested advice information that can be used as a reference when negotiating with the other party when amending the contract document, allowing the first user to smoothly negotiate the contract with the second user.

[0124] (Appendix 13) A computer-implemented method comprising a processor and a memory, wherein the processor performs all of the steps performed in the invention according to any one of appendices 1 to 12. This allows the first user to refer to the past contract history of the second contract document, such as the contract conditions, for the first contract document that the first user is about to enter into with the second user.

[0125] (Appendix 14) An information processing device comprising a control unit and a storage unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 12. This allows the first user to refer to the past contract history of the second contract document, such as the contract conditions, for the first contract document that the first user is about to enter into with the second user.

[0126] (Appendix 15) A system comprising means for performing all steps performed in any of the inventions according to any one of appendixes 1 to 12. This allows the first user to refer to the past contract history of the second contract document, such as the contract conditions, for the first contract document that the first user is about to enter into with the second user. [Explanation of symbols]

[0127] 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

Claims

1. A program comprising a processor and a storage unit, the program providing a service related to a contract document to be agreed upon between parties to a computer, the processor: a contract acceptance step of accepting a first contract document relating to the contract from the first user; a contract acquisition step of acquiring an already concluded second contract document; a contract presentation step of presenting to the first user a comparison result between the first contract document and the second contract document; A program that executes.

2. the contract presentation step is a step of presenting to the first user information indicating whether the first contract document is advantageous or disadvantageous relative to the second contract document; The program according to claim 1.

3. the contract presentation step is a step of presenting to the first user information indicating whether each clause or provision of the first contract document is advantageous or disadvantageous relative to the second contract document; The program according to claim 1.

4. the contract acquisition step is a step of acquiring the second contract document similar to the first contract document; The program according to claim 1.

5. the contract acquisition step is a step of acquiring the second contract document having a contract type that is the same as or similar to the contract type of the first contract document; The program according to claim 1.

6. the program is used for business related to a contract document concluded between the first user and the second user, the contract acquisition step is a step of acquiring the second contract document previously concluded between the first user and the second user; The program according to claim 1.

7. the program is used for business related to a contract document concluded between the first user and the second user, the contract acquisition step is a step of acquiring the second contract document previously concluded by the first user with another user belonging to the same or similar industry as the second user; The program according to claim 1.

8. the contract acquisition step is a step of acquiring the second contract document concluded within a predetermined period of time; The program according to claim 1.

9. The contract acquisition step is a step of acquiring the second contract document, which is the previous contract document of the first contract document, when the first contract document is a renewal contract. The program according to claim 1.

10. the processor: a modification suggestion step of proposing a modification candidate for the first contract document based on the comparison result with the second contract document; To execute The program according to claim 1.

11. The modification suggestion step includes: a step of proposing the modification candidates including a modification group including a plurality of modification portions with respect to the first contract document; The program according to claim 10.

12. the processor: an amendment receiving step of receiving amendments to the first contract document from the first user; an advice proposing step of proposing advice information to the first user, based on the content of the modification accepted in the modification accepting step, which advice information indicates points to be considered in negotiations when conveying the content of the modification to a contracting party; To execute The program according to claim 1.

13. A method implemented on a computer having a processor and a memory, wherein the processor performs all of the steps performed in the invention according to any one of claims 1 to 12.

14. 13. An information processing device comprising a control unit and a storage unit, wherein the control unit executes all of the steps executed in the invention according to any one of claims 1 to 12.

15. A system comprising means for executing all steps performed in any one of the inventions according to claims 1 to 12.

Images