Program, method, information processing apparatus, system

Abstract

To solve that problem that a contact document cannot be compared with a contact condition or the like of past contact documents in an electronic contact procedure between a plurality of users.SOLUTION: A program includes a processor and a storage part, and provides a computer with a service about a contract document to be an object to be agreed between parties. The program causes the processor to execute a contract reception step for receiving a first contract document related to a contract from a first user, a contract acquisition step for acquiring a second concluded contract document, and a contract presentation step for presenting a comparison result with the second contract document to a first user about the first contract document.SELECTED DRAWING: Figure 13

Description

Technical Field

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

Background Art

[0002] With the development and popularization of computer technology, documents that were previously in paper form are being digitized. For example, it is considered possible to manage documents such as contract documents that require the signatures and seals of the parties involved in electronic data. Patent Document 1 discloses an information processing system for digital contracts including a creator terminal, a checker terminal, and a contract document management server.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In an electronic contract procedure among multiple users, there is a problem that the contract conditions of the contract document cannot be compared with those of past contract documents. Therefore, the present disclosure has been made to solve the above problems, and its object is to provide a technique for comparing the contract conditions of a contract document with those of past contract documents.

Means for Solving the Problems

[0005] A program that includes a processor and a memory unit and provides services related to contract documents agreed upon among parties on a computer. The processor executes a contract reception step of receiving a first contract document related to a contract from a first user, a contract acquisition step of acquiring a second contract document that has been concluded, and a contract presentation step of presenting a comparison result with the second contract document to the first user with respect to the first contract document.

Advantages of the Invention

[0006] According to the present disclosure, it is possible to compare contract documents with contract conditions and the like of past contract documents.

Brief Description of the Drawings

[0007]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Embodiments for Carrying Out the Invention

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

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

[0010] Each information processing device is configured by a computer including an arithmetic unit and a storage unit. 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 overlapping with the basic hardware configuration of the computer and the basic functional configuration of the computer described later are omitted.

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

[0012] <Configuration of the Storage Unit 101 of Server 10> The storage unit 101 of the server 10 includes an application program 1011, a user table 1012, a group table 1013, a document table 1014, a confirmation table 1015, an input item table 1016, and a contract document 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 for storing and managing information of member users (hereinafter referred to as users) who use the service. By registering for use of the service, the information of the user is stored in a new record of the user table 1012. Thereby, the user can use the service according to the present disclosure. Note that a user who uses the service in the present disclosure does not necessarily have to be registered in the user table 1012. The user table 1012 is a table that has columns for user ID, user name, email address, group ID, and approval authority, with the user ID as the primary key. Figure 5 is a diagram showing the data structure of the user table 1012.

[0015] The user ID is an item that stores user identification information for identifying a user. The user identification information is an item for which a unique value is set for each user. The user name is an item that stores the user's name. The user name may be set to any string such as a nickname instead of the real name. The email address is an item that stores the user's email address. The group ID is an item that stores group identification information of the group to which the user belongs. The group is defined by the group table 1013 described later, and a user may belong to multiple groups. The approval authority is an item that stores authority information regarding the approval of user contracts. Information indicating the authority to approve contract conclusion (approval authority), such as True, is stored for users who have the authority to approve contract conclusion. On the other hand, information indicating no authority to approve contract conclusion, such as False, blank, or null value, is stored for users who do not have the authority to approve contract conclusion. It may also be configured such that the approval authority can be set according to the contract information. For example, it may be configured such that user A has the approval authority for specific contract information A but does not have the approval authority for specific contract information B. It may also be configured such that the approval authority can be set according to the type of contract information (contract information type), such as a confidentiality contract, a joint research contract, or a subcontract. For example, it may be configured such that user A has the approval authority for a confidentiality contract but does not have the approval authority for a subcontract. In addition, it may be configured to store authority information at multiple levels (levels, ranks) according to the user's department, government agency, etc. For example, dispatched employees, etc. store information such as C, regular employees as B, managerial positions as A, and officers as S in the approval authority item, and according to the contract type information, contract amount, etc. of the contract information, only users with approval authority above a certain rank (for example, confidentiality agreements are above A, etc.) can approve the conclusion of the contract.

[0016] The group table 1013 is a table that stores and manages information (group information) regarding the group to which the user belongs. The group can define any group to which the user belongs, such as a corporation, company, circle, organization, or department within a company. The group table 1013 is a table having columns for group ID, group name, and administrator ID, with the group ID as the primary key. Figure 6 is a diagram showing the data structure of the group table 1013.

[0017] The group ID is an item that stores group identification information for identifying the group. The group identification information is an item for which a unique value is set for each group. The group name is an item that stores the name of the group. Any string can be set as the group name. The administrator ID is an item that stores the user identification information of the user having administrator authority in the group. The user having administrator authority can be arbitrarily defined and set as a user having a certain status or authority or higher in a group such as an organization.

[0018] The document table 1014 is a table for storing and managing information (contract information) regarding an electronic contract exchanged between the creator and the recipient. The document table 1014 is a table having columns for document ID, document data, and creator ID, with the document ID as the primary key. Figure 7 is a diagram showing the data structure of the document table 1014.

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

[0020] The confirmation table 1015 is a table that stores and manages information (verifier information) including the email address of the user who is the verifier of the contract information. The confirmation table 1015 is a table having columns of document ID, confirmation order, verifier 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 that stores the document identification information of the contract information to be verified by the verifier. The confirmation order is an item that stores information regarding the confirmation order when the contract information is verified by the verifier. The contract information stored by the creator is circulated to the verifier in the order of the confirmation order for verification. The verifier email address is an item that stores the email address of the verifier of the contract information. It is not necessary to perform user registration in advance when using the service according to the present disclosure. That is, the verifier 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 the confirmation procedure of the contract information by the verifier is completed. When the verification of the contract information by the verifier is completed, information indicating that the verification is completed, such as a True value, is stored in the item of the confirmation flag. The language data is an item that stores information about the language of the verifier (language information). The access code is an item that stores the access code set for the verifier. The date and time is an item that stores the date and time when the verification procedure of the contract information was performed by the verifier. Specifically, the date and time when the verification identification information was stored in the item of the verification flag is stored.

[0022] The input item table 1016 is a table that stores and manages information about input items (input item information) associated with the electronic contract information. The input item table 1016 is a table having columns of input item ID, document ID, inputter ID, input data, input rule, and date and time. FIG. 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 the input item. The document ID is an item that stores the document identification information of the electronic contract information to 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 input the input data for the input item. Specifically, the inputter ID stores the creator ID, the email address of the user specified by the creator ID, the verifier email address, etc. The input data is an item that stores the input data input to the input item by the inputter. The input rule is an item that stores input rule information regarding the input rule of the input item. As the input rule, in addition to data types such as date, datetime, text, and integer, input rule information regarding the input rule of any input item such as the number of characters and the regular expression of the character string can be stored if it is a character string. The date and time is an item that stores the date and time when the input data was input to the input item by the inputter.

[0024] The contract group table 1017 is a table for storing and managing information about contract groups (contract group information). The contract information is stored and managed in association with one or more cabinets (classification information) for managing the contract information. Depending on the information processing service, the 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. Figure 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 the 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 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0027] The user registration control unit 1041 performs a process of storing information of a user who wishes to use the service according to the present disclosure in the user table 1012. The information stored in the user table 1012 is that the user opens a web page or the like operated by the service provider from an arbitrary information processing terminal, inputs information into a predetermined input form, and transmits it to the server 10. The user registration control unit 1041 stores the received information in a new record of the user table 1012, and the user registration is completed. As a result, the user stored in the user table 1012 can use the service. Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a predetermined review to restrict the user's access to the service. The user ID may be any string or number that can identify the user, such as any string or number desired by the user, or any string or number automatically set by the user registration control unit 1041.

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

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

[0030] <Configuration of the First User Terminal 20> The first user terminal 20 is an information processing device operated by a user who uses the service. The first user terminal 20 may be, for example, a desktop PC (Personal Computer), a laptop PC, a mobile terminal such as a smartphone or a tablet, or a wearable terminal such as an HMD (Head Mount Display) or a wristwatch-type 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 service according to the present disclosure to the user. Note that the first user ID 2011 includes information such as a session ID temporarily assigned by the server 10 for identifying the user using the first user terminal 20.

[0033] The application program 2012 may be pre-stored 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 program 2012 includes applications such as a web browser application. The application program 2012 includes an interpreter-type programming language such as JavaScript (registered trademark) that is executed on a web browser application stored in the first user terminal 20.

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

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

[0036] <Configuration of 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 the second user terminal 30> The second user terminal 30 is an information processing device operated by a user who uses the service. The second user terminal 30 may be, for example, a stationary PC (Personal Computer), a laptop PC, a mobile terminal such as a smartphone or a tablet, or a wearable terminal such as an HMD (Head Mount Display) or a wristwatch-type 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 service according to the present disclosure to the user. Note that the second user ID 3011 includes information such as a session ID temporarily assigned by the server 10 for identifying the user using the second user terminal 30.

[0040] The application program 3012 may be pre-stored 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. The application program 3012 includes applications such as a web browser application. The application program 3012 includes an interpreter-type programming language such as JavaScript (registered trademark) that is executed on the web browser application stored in the second user terminal 30.

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

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

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

[0044] <Operation of the system 1> Hereinafter, each process of the system 1 will be described. 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 screen showing the operation of the contract creation process. FIG. 14 is an example screen showing a confirmation request message notified to the second user terminal 30. FIG. 15 is an example screen showing the operation of the contract confirmation process. FIG. 16 is an example screen showing a conclusion completion message notified to the first user terminal 20.

[0045] In the present disclosure, the contract creation process and the 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 transmits it to the confirmator.

[0047] FIG. 13 is an example screen showing the operation of the contract creation process. On the screen 50 for creating contract information displayed on the display 2081 of the first user terminal 20, a status 510 indicating the current creation status of the contract information, buttons 521, 522, 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, 534, a transmission button 540, comparison results 550, 551, 552, correction candidates 561, 562, correction reflection buttons 5611, 5621, and advice 571, 572 are displayed.

[0048] <Overview of Contract Document Creation Process> The contract document creation process is a series of processes in which the creator creates electronic contract information, sets the confirmers who are the destinations of the electronic contract information, searches for previously concluded and executed electronic contract information, presents the comparison results with the previously concluded and executed electronic contract information, sets input items for the electronic contract information, sets input rules for the input items, accepts input data for the input items from the creator, and sends the electronic contract information to the set confirmers.

[0049] <Details of Contract Document Creation Process> The details of the contract document creation process are described below.

[0050] In step S101, the contract creation unit 1042 of the server 10 executes a contract reception step of receiving a first contract document related to the contract from the first user. Specifically, the contract creation unit 1042 of the server 10 receives first contract information that is the subject of contract conclusion between the creator and the confirmer. Specifically, the first user operates an input device 206 of the first user terminal 20 or the like to create first contract information including first document data related to the contract document. The first document data can include first document data in any data format such as PDF (Portable Document Format), Word, XML (Extensible Markup Language) in the first contract information. The first user operates an input device 206 of the first user terminal 20 or the like to send the created first document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 receives the received first user ID 2011 and first document data, and stores them in the creator ID of a new record in the document table 1014 and the items of the first document data, respectively. Thereby, the contract creation unit 1042 of the server 10 stores new first contract information in the document table 1014.

[0051] On the screen 50 for creating contract information, the document data 531 stored in the document table 1014 is displayed.

[0052] In step S102, the first user operates an input device 206 of the first user terminal 20 or the like 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 the second user as the recipient. The first user operates an input device 206 of the first user terminal 20 or the like to input 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 items of the checker email address and the document ID of the confirmation table 1015, respectively, and stores the first contract information in association with the email address of the second user. Note that the first user may set the language and access code of the second user and store them in association with the email address of the second user. At this time, a value of 1 is stored in the item of the confirmation order in the confirmation table 1015. In step S102, it is also possible that the first user can select and set a plurality of users who will be checkers. In this case, according to the selection order, the values of the items of the confirmation order of the users who will be checkers are incremented and stored one by one. Thereby, the viewing order of the checkers in the contract document confirmation process described later is set. Note that the setting of the viewing order is not essential.

[0053] <Process for obtaining signed contract information> In step S103, the contract creation unit 1042 of the server 10 executes a contract acquisition step of acquiring the signed second contract document. Specifically, the contract creation unit 1042 of the server 10 refers to the document table 1014 to search for contract information based on the first contract information received in step S101 and the information of the checker received in step S102. Based on the search result, the contract information (second contract information) to be compared in the comparison result presentation process described later is identified. In the present disclosure, as an example, the contract creation unit 1042 of the server 10 searches for contract information that has been concluded (contract document confirmation processing by all confirmers has been executed) among the contract information stored in the document table 1014. Specifically, the contract creation unit 1042 of the server 10 searches for contract information among the contract information stored in the document table 1014, in which the value of True is stored in the confirmation flag item of the confirmers' information stored in the confirmation table 1015 and associated with the contract information. Note that the contract creation unit 1042 of the server 10 may search for contract information whose contract conclusion is not 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 regardless of the value of the confirmation flag item of the confirmers' information stored in the confirmation table 1015 and associated with the contract information among the contract information stored in the document table 1014. For example, all the contract information stored in the document table 1014 may be obtained as search results.

[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 item of the document data (search document data) 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 acquires a record of the second contract information including similar document data. For example, the contract creation unit 1042 of the server 10 applies processing such as morphological analysis to the text of the contract content included in the target document data to extract keywords. The keywords may be weighted based on the frequency of occurrence or the like. The contract creation unit 1042 of the server 10 searches for items of the document data in the document table 1014 based on the keywords, applies the same processing such as morphological analysis to the retrieved document data, and calculates an index related to the similarity such as the degree of match and difference between the terms of the target document data for each of the one or more retrieved document data. Note that the similarity may be calculated using any machine learning model, deep learning model, artificial intelligence model, or the like. The contract creation unit 1042 of the server 10 acquires and specifies, as a search result, second contract information related to the retrieved document data having a similarity 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 having a contract type identical to or similar to the contract type of the first contract document. Specifically, the contract creation unit 1042 of the server 10 specifies 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 specifies the type and category of the contract targeted by contract information such as a confidentiality contract, a lease contract, a purchase contract, etc. For example, the contract type is specified based on the title (heading) of the target document data. Note that the contract type may be specified in response to an input operation by any user other than the first user and may be configured to 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 items of the document data (retrieved document data) in the document table 1014 based on the target contract type, and acquires a record of second contract information including document data of the same or similar contract type. Specifically, the contract creation unit 1042 of the server 10 specifies the contract type (retrieved contract type) in the same manner as the target document data based on the retrieved document data, and acquires a record of second contract information including document data of a retrieved contract type identical to or similar to the target contract type by comparing the target contract type and the retrieved contract type. For example, when the character strings of the target contract type and the search contract type exactly match, it may be determined that the contract types are the same. Also, when the similarity degree of the character strings of the target contract type and the search contract type (an index representing the similarity degree such as the Levenshtein distance) is equal to or greater than a predetermined value, it may be determined that the target contract type and the search contract type are similar. Additionally, contract types determined in advance to be similar to each other may be used. For example, the contract type related to a "confidentiality agreement" and the contract type related to a "joint research agreement" may be regarded as similar contract types. Whether the contract types are the same or similar may be determined according to a predetermined rule, or may be managed by a table (not shown) or the like.

[0056] In step S103, the contract acquisition step executes a step of acquiring a second contract document concluded in the past 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 verifier email address in the verification table 1015 based on the first user ID 2011 and the email address of the second user specified in step S102 (the verifier email address stored in the verification table 1015). Thereby, the contract creation unit 1042 of the server 10 can search for contract information concluded in the past between the first user and the second user and acquire it as the second contract information. In the present disclosure, a configuration in which contract information in which the first user is the creator and the second user is the verifier is searched for and acquired has been described as an example, but it is not limited thereto. For example, a configuration in which the first user or the second user searches for contract information in which they are involved as the creator, the verifier, or other related parties and acquires it as the second contract information may also be acceptable.

[0057] In step S103, the contract acquisition step executes a step of acquiring a second contract document concluded in the past between the first user and another user belonging to the same or a similar industry as the second user. Specifically, the contract creation unit 1042 of the server 10 searches for the creator ID in the document table 1014 based on the first user ID 2011, and acquires and identifies the second contract information. Next, based on the email address of the second user (the verifier email address in the verification table 1015) identified in step S102, the contract creation unit 1042 of the server 10 refers to a table or the like in which an email address or domain name (not shown) is associated with the industry type and the like, and identifies the industry type (target industry type) to which the second user belongs. Note that the identified industry type may include industry types similar to the said industry type. For example, the industry type of patent affairs may be included as a similar industry type in the industry type of legal affairs. Based on the document ID of the acquired contract information, the contract creation unit 1042 of the server 10 searches for the document ID in the verification table 1015 and acquires the item of the verifier email address. The contract creation unit 1042 of the server 10 refers to a table or the like (not shown), and based on the verifier email address, identifies the industry type (searched industry type) to which the user related to the verifier email address belongs. The contract creation unit 1042 of the server 10 identifies the second contract information in which the searched industry type is included in the target industry type for each contract information. Thereby, the contract creation unit 1042 of the server 10 can acquire the contract information concluded by the creator with other users belonging to the same or similar industry types as the users related to the verifiers in the past, and identify it as the second contract information.

[0058] In step S103, the contract acquisition step executes a step of acquiring the second contract documents concluded during a predetermined period. Specifically, the contract creation unit 1042 of the server 10 searches for and identifies the records of the verifier information in which the item of the verification table date and time is included in a predetermined period such as within the most recent 6 months or within 1 year from the current date and time. Note that when there is a plurality of verifier information having the same document ID, the contract creation unit 1042 of the server 10 may be configured to search only for the record of the verifier information having the latest date and time (the date and time when the last verifier completed the contract document verification process for one contract information, that is, the date when all the verifiers agreed and concluded the contract for one contract information). The contract creation unit 1042 of the server 10 searches the document ID item in the document table 1014 based on the document ID included in the retrieved approver information, obtains the contract information, and specifies it as the second contract information. As a result, the contract creation unit 1042 of the server 10 can obtain the contract information included in a predetermined period such as within the most recent 6 months or within 1 year from the current date and time, and specify it as the second contract information.

[0059] In step S103, when the first contract document is an updated contract, the contract acquisition step executes a step of acquiring the second contract document which is the previous contract document of the first contract document. Specifically, the contract creation unit 1042 of the server 10 refers to a column (not shown) that defines the relationship between contracts such as the parent-child relationship regarding contracts such as updated contracts and changed contracts in the document table 1014, and obtains and specifies the document ID of the contract information related to the first contract information received in step S101. In addition, the contract creation unit 1042 of the server 10 may be configured to obtain and specify the document ID of the contract information related to the first contract information by searching the document data item in the document table 1014 based on the description content such as the original contract and the basic contract 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 an updated contract, the document ID of the previous contract information is obtained and specified. Note that the previous contract information does not necessarily have to be the earliest contract information, and in the case of an updated contract spanning multiple generations, it includes the 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 specified document ID, obtains the contract information, and specifies it as the second contract information. As a result, the contract information that is the basis of the contract information which is the updated contract received in step S101 can be obtained and specified as the second contract information.

[0060] Alternatively, the processed contract information acquisition may also be configured to search, acquire, and identify the second contract document by combining any one or more of the one or more search conditions described above.

[0061] <Comparison result presentation process> In step S104, the contract creation 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 the 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 the differences. The contract creation unit 1042 of the server 10 displays the differences on the comparison result 550 of the screen 50. Note that the comparison result 550 may include information summarizing the points of agreement and differences as a whole for the contract information, rather than information on the parts related to multiple differences. For example, the summary information can be generated by using artificial intelligence technologies such as any rule-based model, machine learning model, deep learning model, large language model (LLM), etc., based on the information on the parts related to multiple differences.

[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 with respect to the second contract document. The contract presentation step executes a step of presenting to the first user information indicating whether each clause or article of the first contract document is advantageous or disadvantageous with respect 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 with respect to the second contract information for each difference based on the extracted differences. For example, when the upper limit amount of the compensation regulations regarding damages included in the second document data is 5 million yen, and when the upper limit amount of the compensation regulations regarding damages included in the first document data is 10 million yen, the first contract information is calculated to be advantageous over the second contract information. For example, when the upper limit amount of the compensation regulations regarding damages included in the second document data is 5 million yen, and when the upper limit amount of the compensation regulations regarding damages included in the first document data is 3 million yen, the first contract information is calculated to be disadvantageous over the second contract information. Note that the information indicating whether it is advantageous or disadvantageous can be output by using artificial intelligence technologies such as any rule-based model, machine learning model, deep learning model, large language model (LLM), etc. based on the extracted differences. The information regarding the comparison result including the information indicating whether it is advantageous or disadvantageous can be output for the entire contract information, for each clause or article constituting the contract information, and for each location or part constituting the contract information as follows. · For the entire contract information (whether the entire first contract information is advantageous or disadvantageous over the entire second contract information) · For each clause or article constituting the contract information (whether clause ●●, article ●● of the first contract information is advantageous or disadvantageous over clause ●●, article ●● of the second contract information) · For each location or part constituting the contract information (whether the description "···" at page ●●, line ●● of the first contract information is advantageous or disadvantageous over the description "···" at page ●●, line ●● of the second contract information) Note that the information indicating whether it is advantageous or disadvantageous for the entire contract information can be output by using artificial intelligence technologies such as any rule-based model, machine learning model, deep learning model, large language model (LLM), etc. based on the extracted multiple differences. The contract creation unit 1042 of the server 10 displays the information regarding the comparison result including the information indicating whether it is advantageous or disadvantageous on the comparison results 551, 552 of the screen 50.

[0063] <Amendment Proposal Processing> In step S104, the contract creation unit 1042 of the server 10 executes a modification proposal step of proposing modification 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 modification candidates for the first contract information by using artificial intelligence technologies such as an arbitrary rule-based model, a machine learning model, a deep learning model, and a large language model (LLM) based on the information indicating the calculated comparison result. For example, the contract creation unit 1042 of the server 10 calculates modification candidates for the first contract information by using artificial intelligence technologies such as an arbitrary rule-based model, a machine learning model, a deep learning model, and a large language model (LLM) based on the information indicating whether the first contract information is advantageous or disadvantageous to the second contract information for each difference point based on the extracted difference points. For example, when the upper limit amount of the compensation regulation regarding damages included in the second document data is 5 million yen, and the upper limit amount of the compensation regulation regarding damages included in the first document data is 3 million yen, modification candidates 561 and 562 indicating that the upper limit amount of the compensation regulation regarding damages in the first contract information is modified to 5 million yen are displayed on the screen 50. The modification candidates can be output for the entire contract information, for each article or clause constituting the contract information, for each location or part constituting the contract information, as follows. · Proposal of modification candidates for the entire contract information (It is considered to modify ●● of the first contract information to ●●) · Proposal of modification candidates for each article or clause constituting the contract information (It is considered to modify article ●●, clause ●● of the first contract information to article ●●, clause ●●) · Proposal of modification candidates for each location or part constituting the contract information (It is considered to modify the description "···" in line ●● on page ●● of the first contract information to "···") Each amendment candidate can be output by using artificial intelligence technologies such as any rule-based model, machine learning model, deep learning model, large language model (LLM), etc., based on information regarding the comparison result that indicates whether it is advantageous or disadvantageous for the entire contract information, each clause or article constituting the contract information, or each location or part constituting the contract information.

[0064] In step S104, the amendment proposal step executes a step of proposing amendment candidates including an amendment group including a plurality of amendment locations for the first contract document. Specifically, the contract creation unit 1042 of the server 10 proposes amendment candidates that advantageously amend contract condition A to contract condition A1 at the first amendment location of the first contract information and disadvantageously amend contract condition B to contract condition B1 at the second amendment location of the first contract information. For example, when the upper limit amount of the compensation regulation regarding damages included in the second document data is 5 million yen and the upper limit amount of the compensation regulation regarding damages included in the first document data is 3 million yen, an amendment candidate (advantageous amendment candidate) indicating that the upper limit amount of the compensation regulation regarding damages in the first contract information is amended to 5 million yen can be proposed, and an amendment candidate (disadvantageous amendment candidate) indicating that the conditions under which damages occur are limited can be proposed. Thereby, it is possible to propose amendment candidates that are easy to agree on so that neither party of the parties is unilaterally advantaged or disadvantaged.

[0065] In step S104, the contract creation unit 1042 of the server 10 executes an amendment reception step of receiving the amendment content for the first contract document from the first user. Specifically, the first user operates the input device 206 of the first user terminal 20 to select the modification reflection buttons 5611 and 5621. As a result, a request to reflect the proposed modification content for the modification candidates 561 and 562 in the first contract information is sent to the server 10. When the contract creation unit 1042 of the server 10 receives the request, it modifies the content of the first document data included in the first contract information based on the modification candidates. Specifically, the contract creation unit 1042 of the server 10 reflects the modification content in the first document data. For example, when a modification candidate 561 is proposed to modify the upper limit amount of the compensation provision regarding damages in the first contract information to 5 million yen, if the modification reflection button 5611 is selected, the upper limit amount of the compensation provision regarding damages included in the first document data of the first contract information is modified to 5 million yen. The contract creation unit 1042 of the server 10 stores the modified first document data in the document data item of the target record in the document table 1014. As a result, the modification content is reflected in and stored in the content of the first document data of the first contract information received in step S101.

[0066] <Advice processing> In step S104, the contract creation unit 1042 of the server 10 executes an advice proposal step of proposing advice information indicating points during negotiation when communicating the modification content to the counterparty of the contract to the first user based on the modification content received in the modification reception step. Specifically, the contract creation unit 1042 of the server 10 generates advice information when communicating the modification content to the counterparty of the contract (the second user) according to the selected modification candidates 561 and 562, and sends it to the first user terminal 20. When the control unit 204 of the first user terminal 20 receives the advice information, it displays and presents it in the advices 571 and 572 on the display 2081 of the first user terminal 20. For example, when modifying the upper limit amount of the compensation regulations regarding the damages of the first contract information from 3 million yen to 5 million yen and limiting the conditions for damages to occur, advice 571 and 672 such as "Since the amount of this transaction is larger than the previous one, it is not appropriate for the upper limit amount of the compensation regulations regarding damages to be less favorable than the previous one" are displayed and presented to the second user, the counterparty of the contract. As a result, when modifying the contract document, the first user can receive a proposal of advice information that can be used as a reference when negotiating with the counterparty. The first user can smoothly conduct contract negotiations with the second user.

[0067] In addition, in this disclosure, as an example, a case of providing various processes such as a concluded contract information acquisition process, a comparison result presentation process, a modification proposal process, and an advice process to the first user in the contract document creation process is disclosed, but it is not limited to this. For example, when presenting contract information such as step S303 of the contract document confirmation process to the second user, various processes such as a concluded contract information acquisition process, a comparison result presentation process, a modification proposal process, and an advice process may be provided to the second user instead of the first user.

[0068] In step S105, the first user operates an input device 206 of the first user terminal 20 or the like to set input items for the contract information. Specifically, the first user operates an input device 206 of the first user terminal 20 or the like to set a plurality of input items for the contract information created and stored in step S101. The input items can be arbitrarily set, such as a stamping field for stamping seal data, an input field for inputting text data such as signature data, a checkbox field where check items can be selected, and a date field for inputting a date. The first user operates an input device 206 of the first user terminal 20 or the like, and sends a request to add an input item to the server 10. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information in the document ID of a new record in the input item table 1016. Thereby, the newly added input item information is stored in association with the contract information. Note that the first user can store a plurality of input item information in association with the contract information.

[0069] In step S106, the first user sets an input rule for each input item to be added. The first user operates an input device 206 of the first user terminal 20 or the like to specify the input rule for each input item information set in step S103, and sends it to the server 10. The contract creation unit 1042 of the server 10 stores the received input rule in the input rule item of the record of each input item information in the input item table 1016. Thereby, an input rule can be set for each input item.

[0070] In step S107, the contract creation unit 1042 of the server 10 receives input data for a plurality of input items input by the first user. Specifically, the first user inputs input data for each input item set in step S106 by operating an input device 206 of the first user terminal 20 or the like. For example, the first user may input input data of a number for managing contract information, such as an arrangement number in the group to which the user belongs, to an input item with a management number set. The first user may input input data of the date of the contract conclusion date of the contract information to an input item with the contract conclusion date set. When the input of the input data to the input item is completed, the first user sends the input item ID and the 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 item of the input data of the input item information in the input item table 1016 specified by the received input item ID. Thereby, the input data input 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 the 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 notifying the second user that a contract information confirmation request has been sent from the first user. Specifically, the contract creation unit 1042 of the server 10 searches the item of the confirmation order in the confirmation table 1015 and identifies the user (the first confirmation user) who is the first confirmator with the smallest value stored in the item of the confirmation order. In the present disclosure, as an example, the first confirmation user is the second user. The contract creation unit 1042 of the server 10 sends a message notifying that a contract information confirmation request has been sent from the first user to the email address of the second user by means of communication such as email. The message notified to the second user includes information of a URL (Uniform ReSource Locator) including a document ID for specifying the contract information. The URL may directly include the document ID, or may include information such as a character string obtained by performing arbitrary encryption on the document ID, or a character string capable of specifying the document ID by referring to a table (not shown). Further, the URL may include information for specifying the second user. For example, when the second user is not registered as a user in the service according to the present disclosure, it is necessary to include information for specifying the second user in the URL.

[0073] When the first user sets an access code for the second user, the access code is separately communicated to the second user by means such as email. This ensures that even if a message notified to the second user is obtained by a third party, the third party cannot execute the contract document confirmation process unless they obtain the access code.

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

[0075] <Modification Example> When the first user selects and sets a plurality of approvers in step S102, it may be configured such that different input item information can be independently set for each of the plurality of approvers in step S103. For example, when the first user sets two users, the second user and the ninth user, as approvers, the input items of the contract start date and the contract end date may be set for the second user, and the input item of the contract conclusion date may be set for the ninth user. In this case, in the contract document confirmation process described later, the second user can input input data for the input items of the contract start date and the contract end date, but cannot input input data for the input item of the contract conclusion date. On the other hand, the ninth user cannot input input data for the input items of the contract start date and the contract end date, but can input input data for the input item of the contract conclusion date. It may also be configured such that a plurality of approvers can be selected and set repeatedly for one input item information.

[0076] On the screen 50 for creating contract information, input items 532, 533, and 534 are drawn as drawing objects. In input items 532 and 533, as an assignment, the user identification information "USER-B" of the user who has selected and set to input the input item and the item of "text" as the type of the input item are drawn. In the input item 534 regarding the seal, as an assignment, the user identification information "USER-C" of the user who has selected and set to affix the seal and the item of "seal" as the type of the input item are drawn.

[0077] In addition, in the present disclosure, although a configuration in which contract information and various input information are stored in various tables of the server 10 at each step is disclosed as an example, it is not limited thereto. For example, in the transmission step of step S108, a configuration in which contract information and various input information input by the creator are collectively stored in various tables of the server 10 may be adopted.

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

[0079] <Outline of the contract document confirmation process> The contract document confirmation process is a series of processes that accepts access from the confirmor, presents a confirmation screen for displaying contract information to the confirmor, accepts input data for the input item from the confirmor, and accepts data regarding the confirmation of the contract information from the confirmor.

[0080] <Details of the contract document confirmation process> The details of the contract document confirmation process will be described below.

[0081] In step S301, the second user who is the confirmor can open the web page specified by the URL by selecting the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, using the browser application of the second user terminal 30. Thereby, the second user terminal 30 transmits a request for executing the contract document confirmation process to the server 10.

[0082] When the access code item is stored in the record of the second user in the confirmation table 1015, the second user is requested to input the access code, and the authentication process for the second user can be executed by collating the input access code with the access code stored in the record of the second user in the confirmation table 1015. Specifically, the server 10 transmits an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30, inputs the access code, and transmits it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the record of the second user in the confirmation table 1015. If they match, the contract document confirmation process continues. On the other hand, if they do not match, the contract document confirmation process is aborted. Note that the authentication process using the access code may be omitted.

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

[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 may be identified based on the identification information for identifying the second user included in the URL. When the second user has not registered for the service according to the present disclosure, it is necessary to identify the second user from the URL. For example, the URL may include the email address, user ID, etc. of the second user 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, confirmation person information (information for identifying the second user), and input item information, and transmits it to the second user terminal 30.

[0086] Specifically, the display 3081 of the second user terminal 30 presents a confirmation screen for receiving an operation for approving the contract information to the second user. The second user checks and approves the contract information displayed on the display 3081 of the second user terminal 30. Note that the confirmation screen presented to the second user may be configured to be presented to the second user in the language notation specified for the confirmor based on the language information stored in the item of the language data of the record of the second user in the confirmation table 1015.

[0087] FIG. 15 is an example screen of a confirmation screen showing the operation of the contract document confirmation process. On the confirmation screen 70 for approving the contract information, which is displayed on the display 3081 of the second user terminal 30, a status 710 indicating the creation status of the current contract information, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an approval button 740 are displayed.

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

[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 information received from the first user. When the second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30 and agrees or approves the content, the second user operates an input device 306 of the second user terminal 30 or the like, and presses an approval button 740 displayed on a confirmation screen 70 for checking the contract information, thereby executing a process of transmitting a request including a document ID, information for identifying the second user, and input data for each input item input in step S305 to the server 10. The information for 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 checked 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 the information for identifying the second user, and stores a True value in the confirmation flag item of the record. For example, when the information for identifying the second user is an email address, the document ID and the confirmor email address items of the confirmation table 1015 are searched, and a True value is stored in the confirmation flag item of the record. When the information for identifying the second user is user identification information, based on the email address of the second user identified by searching the user ID item of the user table 1012, the document ID and the confirmor email address items of the confirmation table 1015 are searched, and a True value is stored in the confirmation flag item of the record. The contract confirmation unit 1043 of the server 10 stores the received input data in the item of the input data of the input item table 1016 specified by the input item ID associated with the input data. Thereby, in step S305, the input data input by the second user is stored as the input item information in the input item table 1016.

[0090] The contract confirmation unit 1043 of the server 10 determines that the contract document confirmation process by all confirmers has been executed. Specifically, the contract confirmation unit 1043 of the server 10 determines that the contract document confirmation process by all confirmers has been executed when the value of True is stored in the confirmation flag of the record of the confirmers in the confirmation table 1015. When the contract document confirmation process by all confirmers has been executed, the contract confirmation unit 1043 of the server 10 sends a message notifying that the contract document confirmation process has been completed to the first user. Similarly, the contract confirmation unit 1043 of the server 10 may send a message notifying that the contract document confirmation process has been completed to the second user.

[0091] Specifically, the contract confirmation unit 1043 of the server 10 sends, by means of communication such as email, a message notifying the first user's email address that the second user has completed the confirmation of the contract information. That is, the first user is notified that the second user has approved the conclusion of the contract. Thereby, the first user can know that the conclusion of the contract with the second user has been completed. The message notified to the first user may include information on the URL, which is an endpoint including the document ID for specifying the contract information.

[0092] FIG. 16 is an example of a screen showing the message notified to the first user terminal 20. The message screen 80 displayed on the display 2081 of the first user terminal 20 includes the message 81 and the information on the URL 82 including the document ID for specifying the contract information.

[0093] Similarly, the contract confirmation unit 1043 of the server 10 may also send a message notifying that the second user has completed the confirmation of the contract information, including a mention to the first user, using a chat service or the like (not shown). That is, the first user is notified via the chat service that the second user has approved the conclusion of the contract. Thereby, the first user can know that the conclusion of the contract with the second user has been completed. The message to be notified to the first user may include information on a URL, which is an endpoint including a document ID for specifying the contract information.

[0094] The first user can open the web page specified by the URL included in the received message by means of the browser application of the first user terminal 20. The first user terminal 20 refers to the contract information and sends a request for inquiry to the server 10. The contract confirmation unit 1043 of the server 10 refers to the contract information and 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 from the web page screen displayed on the display 2081 of the first user terminal 20 by means of downloading or the like.

[0095] When a plurality of users are set as confirmers, the contract confirmation unit 1043 of the server 10 may also send a message notifying that the contract document confirmation process has been completed to the users related to the confirmers other than the user who last executed the contract document confirmation process. Thereby, the users related to the confirmers can also receive a notification that the execution of the contract document confirmation process by all the confirmers has been completed. In addition, the contract confirmation unit 1043 of the server 10 may also send a message notifying that the contract document confirmation process has been completed to the user having the authority corresponding to the administrator in the group to which a plurality of confirmers belong. Note that the message may be sent via email, a chat service, or the like. Thereby, the administrator in the group to which the users related to the confirmers belong can receive a notification that the execution of the contract document confirmation process has been completed.

[0096] Specifically, the contract confirmation unit 1043 of the server 10 retrieves the item of the group ID in the user table 1012 by searching for the item of the user ID or email address in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 searches for the item of the group ID in the group table 1013 based on the retrieved item of the group ID, retrieves the item of the administrator ID, and based on the administrator ID, identifies the user having the authority corresponding to the administrator by searching for the user ID in the user table 1012, and sends a message notifying that the contract document confirmation process has been completed.

[0097] <Electronic signature process> In step S305, an electronic signature process may be included. In response to an instruction to approve the contract conclusion received from the second user in step S305, the contract confirmation unit 1043 of the server 10 attaches and stores an electronic signature indicating that the contract conclusion of the contract information has been approved to the contract information received from the first user. Specifically, the contract confirmation unit 1043 of the server 10 attaches and stores an electronic signature to the contract information based on the received request. The contract confirmation unit 1043 of the server 10 searches for the item of the document ID in the document table 1014 based on the document ID and retrieves the contract information. The contract confirmation unit 1043 of the server 10 attaches an electronic signature to the retrieved contract information and stores it in the item of the document data in the document table 1014. Note that the contract confirmation unit 1043 of the server 10 may update (overwrite) the item of the document data with the contract information with the attached electronic signature, or may separately store the contract information before the attachment of the electronic signature in a storage device (not shown). The contract confirmation unit 1043 of the server 10 may include any information such as the document ID, the email address of the first user, the email address of the second user, the approval date and time, the confirmation date and time, the authentication method of the approval date and time, the authentication method of the confirmation date and time, the value of the input data for each input item, the consent (approval) of the first user and the second user, and the timestamp in the electronic signature. As a result, the contract confirmation unit 1043 of the server 10 attaches and stores an electronic signature indicating that the second user has approved the conclusion of the contract in the contract information. This can prevent forgery and alteration of the contract information by a third party.

[0098] <Basic Hardware Configuration of a Computer> FIG. 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 storage device 903, and a communication IF 991 (Interface). These are electrically connected to each other by a communication bus 921.

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

[0100] The main memory device 902 is for temporarily storing a program and data processed by the program and the like. 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 storing data and programs. For example, it is a flash memory, an HDD (Hard Disc Drive), a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like.

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

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

[0104] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration (Figure 17) of the computer 90 will be described. The computer includes at least functional units of a control unit, a storage unit, and a communication unit.

[0105] Note that the functional units included in the computer 90 can also be realized by distributing all or part of each functional unit to a plurality of computers 90 interconnected by 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 and expanding them in the main storage device 902, and executing processing according to the programs. The control unit can realize functional units that perform various information processes according to the types of programs. As a result, the computer is realized as an information processing device that performs information processing.

[0107] The storage unit is realized by the main storage device 902 and the auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Also, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to the program. Further, the control unit can cause the processor 901 to execute addition, update, and deletion processing of the data stored in the storage unit according to various programs.

[0108] The database refers to a relational database and is for managing a table format table defined structurally by rows and columns and a data set called a master in association with each other. In a database, a table is called a table, a master, a column of a table is called a column, and a row of a table is called a record. In a relational database, the relationship between tables and masters can be set and associated. Normally, a column serving as a primary key for uniquely identifying a record is set for each table and each master, but setting a primary key for a column is not essential. The control unit can cause the processor 901 to add, delete, and update records in a specific table and master stored in the storage unit according to various programs. Also, by storing data, various programs, and various databases in the storage unit, the information processing device and information processing system according to the present disclosure can be regarded as being manufactured.

[0109] Note that the database and master in the present disclosure may include any data structure (such as a list, dictionary, associative array, object, etc.) in which information is structurally defined. The data structure shall also include data that can be regarded as a data structure by combining data with functions, classes, methods, etc. described in any programming language.

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

[0111] <Supplementary Note> The matters described in each of the above embodiments are appended below.

[0112] (Supplementary Note 1) A program that includes a processor and a storage unit and provides services related to contract documents that are the subject of agreement among parties on a computer, wherein the processor executes a contract reception step (S101) of receiving a first contract document related to a contract from a first user, a contract acquisition step (S103) of acquiring a second contract document that has been concluded, and a contract presentation step (S104) of presenting the comparison result between the first contract document and the second contract document to the first user. Thereby, regarding the first contract document that the first user intends to contract with the second user, the contract performance such as the contract conditions of the past second contract document can be referred to.

[0113] (Supplementary Note 2) The contract presentation step (S104) is the program described in Supplementary Note 1, which is a step of presenting to the first user information indicating whether the first contract document is advantageous or disadvantageous with respect to the second contract document. As a result, it is possible to confirm whether the first contract document that the first user is trying to contract with the second user is advantageous or disadvantageous compared to the contract conditions of past second contracts and the like.

[0114] (Appendix 3) The contract presentation step (S104) is the program described in Appendix 1, which is a step of presenting the first user with information indicating whether each clause or article of the first contract document is advantageous or disadvantageous with respect to the second contract document. As a result, it is possible to confirm whether each clause or article of the first contract document that the first user is trying to contract with the second user is advantageous or disadvantageous compared to the contract conditions of past second contracts and the like.

[0115] (Appendix 4) The contract acquisition step (S103) is the program described in Appendix 1, which is a step of acquiring a second contract document similar to the first contract document. As a result, the first user can refer to the contract performance such as the contract conditions of the second contract document of a similar contract type with respect to the first contract document. A second contract document more similar to the first contract document can be used as reference information at the time of contract conclusion.

[0116] (Appendix 5) The contract acquisition step (S103) is the program described in Appendix 1, which is a step of acquiring a second contract document having the same or a similar contract type as the contract type of the first contract document. As a result, the first user can refer to the contract performance such as the contract conditions of the second contract document of the same or a similar contract type with respect to the first contract document. A second contract document concluded under conditions more similar to the first contract document can be used as reference information at the time of contract conclusion.

[0117] (Appendix 6) The program is used for operations related to the contract documents concluded between the first user and the second user. The contract acquisition step (S103) is the step of acquiring the second contract document concluded between the first user and the second user in the past. The program described in Supplementary Note 1. Thereby, for the first contract document, the first user can refer to the contract performance such as the contract terms of the second contract document concluded with the second user in the past. The second contract document concluded under conditions more similar to the first contract document can be used as reference information at the time of contract conclusion.

[0118] (Supplementary Note 7) The program is used for operations related to the contract documents concluded between the first user and the second user. The contract acquisition step (S103) is the step of acquiring the second contract document concluded between the first user and another user belonging to the same or a similar industry type as the second user in the past. The program described in Supplementary Note 1. Thereby, for the first contract document, the first user can refer to the contract performance such as the contract terms of the second contract document concluded with another user in the same or a similar industry type as the second user in the past. The second contract document concluded under conditions more similar to the first contract document can be used as reference information at the time of contract conclusion.

[0119] (Supplementary Note 8) The contract acquisition step (S103) is the step of acquiring the second contract document concluded within a predetermined period. The program described in Supplementary Note 1. Thereby, for the first contract document, the first user can refer to the contract performance such as the contract terms of the second contract document concluded within the predetermined period. For example, the second contract documents concluded in the most recent 6 months or 1 year can be used as comparison targets. Old contract documents can be excluded from the comparison targets.

[0120] (Supplementary Note 9) The contract acquisition step (S103) is the step of acquiring a second contract document that is the previous contract document of the first contract document when the first contract document is a renewal contract, as described in Appendix 1 of the program. Thereby, regarding the first contract document that the first user is trying to contract with the second user, the contract performance such as the contract conditions of the previous contract of the renewal contract can be referred to.

[0121] (Appendix 10) The processor executes a correction proposal step (S104) of proposing a correction candidate based on the comparison result with the second contract document regarding the first contract document, as described in Appendix 1 of the program. Thereby, the first user can receive a proposal of a correction candidate with reference to the contract conditions of the past second contract document.

[0122] (Appendix 11) The correction proposal step (S104) is a step of proposing a correction candidate including a correction group including a plurality of correction points regarding the first contract document, as described in Appendix 10 of the program. Thereby, the first user can receive a proposal of a correction candidate that is easy to agree on such that, for example, the contract condition A is favorably corrected to the contract condition A1 at the first correction point and the contract condition B is unfavorably corrected to the contract condition B1 at the second correction point, without one party of the parties becoming favorable or unfavorable.

[0123] (Appendix 12) The processor executes a correction reception step (S104) of receiving correction contents for the first contract document from the first user, and an advice proposal step (S104) of proposing advice information indicating negotiation points when transmitting the correction contents to the contract partner for the first user based on the correction contents received in the correction reception step, as described in Appendix 1 of the program. Thereby, the first user can receive a proposal of advice information that can be referred to when negotiating with the other party when correcting the contract document. The first user can smoothly conduct contract negotiations with the second user.

[0124] (Appendix 13) A method to be executed on a computer comprising a processor and a memory, wherein the processor executes all the steps executed in the invention according to any one of Appendices 1 to 12. Thereby, regarding the first contract document that the first user is trying to contract with the second user, the contract performance such as the contract conditions of the past second contract document can be referred to.

[0125] (Appendix 14) An information processing apparatus comprising a control unit and a storage unit, wherein the control unit executes all the steps executed in the invention according to any one of Appendices 1 to 12. Thereby, regarding the first contract document that the first user is trying to contract with the second user, the contract performance such as the contract conditions of the past second contract document can be referred to.

[0126] (Appendix 15) A system comprising means for executing all the steps executed in the invention according to any one of Appendices 1 to 12. Thereby, regarding the first contract document that the first user is trying to contract with the second user, the contract performance such as the contract conditions of the past second contract document can be referred to.

Explanation of Reference Signs

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

Claims

1. A program that includes a processor and a memory unit, and provides services related to contract documents that are the subject of agreement between parties on a computer, wherein in the memory unit, information on contract documents for which contracts have been concluded is configured to be stored in association with information on the parties to the contract, the program causes the processor to receive from a first user a first contract document regarding pre - conclusion contract conditions that is the subject of contract conclusion between the first user and a second user, present to the first user an operation screen for displaying information on the pre - conclusion first contract document received in the step of receiving the first contract document, the program further causes the processor to execute a step of searching for the contract documents for which contracts have been concluded and stored in the memory unit based on information on the parties to the contract, In the step of presenting, on the operation screen, display information on the contract conditions of the second contract document for which the contract has been concluded, which is retrieved in the step of searching and is a comparison target with the contract conditions of the first contract document regarding pre - conclusion. A program.

2. The program according to claim 1, wherein in the step of searching, the second contract document for which the contract has been concluded and the parties of which are the same as those of the first contract document is searched based on information on the parties to the contract.

3. The program according to claim 1, wherein in the step of searching, the second contract document for which the contract has been concluded and has the same or similar contract type as the contract type of the first contract document is searched according to the contract type.

4. In the step of searching, extracting keywords for searching for the second contract document for which the contract has been concluded by analyzing the first contract document, and searching for the second contract document for which the contract has been concluded using the extracted keywords. The program according to claim 1.

5. The program according to claim 1, wherein in the step of presenting, on the operation screen, for each clause or article of the contract conditions, the contract conditions of the second contract document for which the contract has been concluded are presented as candidates for reflection on the first contract document.

6. In the step of prompting, on the operation screen, for each clause or article of the contract terms, the contract terms of the executed second contract document are compared with the contract terms of the first contract document, and are prompted as candidates to be reflected in the first contract document according to whether they are advantageous or disadvantageous. The program according to claim 5.

7. In the step of prompting, on the operation screen, a process of receiving a user operation on a candidate to be reflected in the first contract document presented, and a process of updating the first contract document based on the content of the candidate to be reflected in the first contract document in response to receiving the user operation of reflecting. The program according to claim 5.

8. In the step of prompting, on the operation screen, receiving from the user an operation of giving an instruction to request the conclusion of a contract with the second user for the first contract document, and sending a confirmation request for the first contract document to the second user in response to the instruction of requesting. The program according to claim 1.

9. The step of prompting is a step of prompting the first user with information indicating whether the first contract document is advantageous or disadvantageous to the second contract document. The program according to claim 1.

10. The step of prompting is a step of prompting the first user with information indicating whether each clause or article of the first contract document is advantageous or disadvantageous to the second contract document. The program according to claim 1.

11. In the step of searching, searching for the second contract documents concluded within a predetermined period as search targets, or when the first contract document is a renewal contract, searching for the second contract document which is the previous contract document of the first contract document as a search target. The program according to claim 1.

12. The processor executes a modification reception step of receiving modification content for the first contract document from the first user, and an advice proposal step of proposing advice information indicating points during negotiation when communicating the modification content to the counterparty of the contract to the first user based on the modification content received in the modification reception step. The program according to claim 1.

13. A method to be executed on a computer comprising a processor and a memory, the method wherein the processor executes all the steps executed in the invention according to any one of claims 1 to 12.

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

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

Images