Program, method, information processor, and system

Abstract

To solve the issue that in the process of electronic contract execution among multiple users, a supplementary message requesting a counterparty to review a contract document suitable for the counterparty has not been sent.SOLUTION: A program includes a processor and a storage unit and causes a computer to execute an electric contract procedure among multiple users. The processor executes: a contract reception step for receiving a contract document related to a contract from a first user; a generation step of generating a message for making a request from the first user to a second user to confirm the contract document according to an input operation by the first user; and a sending step of sending the message generated in the generation step to the second user.SELECTED DRAWING: Figure 14

Description

[Technical field]

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

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

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

[0004] In electronic contract procedures between multiple users, there is a problem in that it is not possible to send an additional message to request confirmation of a contract document that is suitable for the other party to the contract. Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide a technology for sending an additional message to request confirmation of a contract document that is suitable for the other party to the contract. [Means for solving the problem]

[0005] A program having a processor and a memory unit, for causing a computer to execute electronic contract procedures between multiple users, wherein the processor executes a contract acceptance step of accepting a contract document relating to a contract from a first user, a creation step of creating a message from the first user to a second user requesting confirmation of the contract document in response to an input operation by the first user, and a transmission step of sending the message created in the creation step to the second user. Effect of the Invention

[0006] According to the present disclosure, it is possible to organize and manage what contract information has been concluded for each contracting party. [Brief description of the drawings]

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

[0008] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In all the drawings explaining the embodiment, the same reference numerals are given to common components, and repeated explanations are omitted. Note that the following embodiment does not unduly limit the contents of the present disclosure described in the claims. In addition, not all of the components shown in the embodiment are essential components of the present disclosure. In addition, each figure is a schematic diagram and is not necessarily illustrated strictly.

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

[0010] Each information processing device is configured by a computer equipped with a calculation device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, and the second user terminal 30, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

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

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

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

[0014] The user table 1012 is a table for storing and managing information on member users (hereinafter, users) who use the service. When a user registers to use the service, the user's information is stored in a new record in the user table 1012. This allows the user to use the service according to the present disclosure. Note that a user who uses a service according to the present disclosure does not necessarily need to be registered in the user table 1012. The user table 1012 is a table having a user ID as a primary key, and columns of user ID, user name, email address, group ID, and approval authority. FIG. 5 is a diagram showing the data structure of the user table 1012. As shown in FIG.

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

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

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

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

[0019] The document ID is an item for storing document identification information for identifying contract information. The document identification information is an item for which a unique value is set for each contract information. The document data is an item that stores contract information (binary or text data) of a contract document related to the conclusion of a contract. Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). Creator ID is an item for storing user identification information for identifying the user who created the contract information.

[0020] The confirmation table 1015 is a table for storing and managing information (checker information) including the email address of the user who will be the checker of the contract information. The confirmation table 1015 is a table having columns for document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time. FIG. 8 is a diagram showing the data structure of the confirmation table 1015. As shown in FIG.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0037] <Configuration of second user terminal 30> The second user terminal 30 is an information processing device operated by a user who uses the service. The second user terminal 30 may be, for example, a desktop PC (Personal Computer) or a laptop PC, or may be a mobile terminal such as a smartphone or a tablet. It may also be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch terminal. The 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 a user's account ID. The user transmits the second user ID 3011 from the second user terminal 30 to the server 10. The server 10 identifies the user based on the second user ID 3011 and provides the user with the service according to the present disclosure. The second user ID 3011 includes information such as a session ID temporarily assigned by the server 10 to identify the user using the second user terminal 30.

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

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

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

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

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

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

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

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

[0048] <Outline of contract creation process> The contract creation process is a series of processes in which the creator creates electronic contract information, sets a reviewer to whom the electronic contract information is to be sent, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, creates an accompanying message to request the reviewer to confirm the electronic contract information, presents the accompanying message, accepts input operations from the creator to confirm the accompanying message, and sends the electronic contract information together with the accompanying message to the set reviewer.

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

[0050] In step S101, the contract preparation unit 1042 of the server 10 executes a contract reception step of receiving a contract document related to a contract from a first user. The contract preparation unit 1042 of the server 10 receives contract information to be a subject of a contract between a preparer and a verifyer from the preparer. Specifically, the first user operates the input device 206 of the first user terminal 20 to create contract information including document data related to the contract. The document data may be in any data format such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language) and may be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and transmits the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the document table 1014.

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

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

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

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

[0055] In step S105, the contract preparation unit 1042 of the server 10 accepts input data for a plurality of input items input by the first user. Specifically, the first user operates the input device 206 of the first user terminal 20 to input input data for each input item set in step S104. For example, the first user may input input data of a number for managing contract information, such as a serial number for a group to which the first user belongs, into an input item in which a management number is set. The first user may input input data of the contract conclusion date of the contract information into an input item in which a contract conclusion date is set. After completing input of the input data into the input items, the first user transmits the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of the server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of the server 10 stores the received input data in the input data item of the input item information of the input item table 1016 specified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

[0056] <Additional message creation process> In step S106, the contract preparation unit 1042 of the server 10 executes a preparation step of preparing a message from the first user to the second user requesting confirmation of the contract document in response to an input operation by the first user. Specifically, the first user operates the input device 206 of the first user terminal 20 to press the associated message creation button 541 displayed on the screen 50 for creating contract information. The control unit 204 of the first user terminal 20 displays the associated message screen D1 for displaying the associated message on the display 2081 of the first user terminal 20. 14 is a screen example showing the operation of the additional message presentation process. The additional message screen D1 includes a message generation button D11, an additional message input field D12, a second user's proficiency level D13, and a confirmation button D14.

[0057] The first user presses the message generation button D11 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits a request to create an accompanying message to the server 10. The contract creation unit 1042 of the server 10 creates the accompanying message using any AI technology such as machine learning, deep learning, or a large-scale language model represented by ChatGPT. Upon receiving the request, the contract creation unit 1042 of the server 10 creates the accompanying message by referring to a template document of the accompanying message stored in the storage unit 101 of the server 10.

[0058] The creating step executes a step of creating a message indicating the procedure for electronic contract procedures in the electronic contract system. Specifically, the accompanying message created by the contract creation unit 1042 of the server 10 includes, when the second user executes electronic contract procedures in the electronic contract system of the present disclosure, an explanation of the operating procedures, the contents of the screen, and a detailed explanation of the legal effects of the electronic contract. This allows the second user to browse the accompanying message indicating the procedure for the electronic contract procedure and to comfortably carry out the electronic contract procedure.

[0059] The message created in the creation step is an additional message set by the first user, which is different from a standard message that requests the second user to confirm the contract document. Specifically, the generated additional message is not a standard message, but is a message generated by the first user based on the information and contract information of the second user.

[0060] <Additional Message Creation Process (First Embodiment)> The creating step includes a step of creating a message according to the second user.

[0061] The creating step executes a step of creating a message according to the second user's familiarity with electronic contract procedures. The creating step executes a step of creating a message according to the familiarity calculated based on the number of electronic contract procedures concluded in the electronic contract system of the second user. Specifically, the contract creation unit 1042 of the server 10 can include polite support text in the accompanying message when the second user has a low level of proficiency, and can include concise support text in the accompanying message when the second user has a high level of proficiency. The contract creation unit 1042 of the server 10 can include in the accompanying message a detailed support sentence that specifies the work procedures for electronic contract procedures in detail when the second user has a low level of proficiency, and can include in the accompanying message a support sentence that concisely describes the work procedures for electronic contract procedures when the second user has a high level of proficiency. The accompanying message can be generated based on a manual that specifies the work procedures for electronic contract procedures and the proficiency of the second user, using any AI technology such as machine learning, deep learning, and a large-scale language model represented by ChatGPT. For example, the manual and the proficiency of the second user are used as input data, and a prompt including an instruction to output information indicating the work procedures for electronic contract procedures according to the proficiency of the second user is input to the large-scale language model, whereby information indicating the work procedures for electronic contract procedures according to the proficiency of the second user can be generated.

[0062] The proficiency of the second user is an index (score) showing the proficiency of the second user regarding electronic contract procedures, calculated based on the number of electronic contract procedures concluded, the cumulative operation time in the electronic contract system etc. disclosed herein, the number of logins, the number of operations, the number of times contract information is created in the electronic contract system etc. disclosed herein, the number of times contract information is confirmed in the electronic contract system etc. disclosed herein, etc. The proficiency may be calculated using any AI technology, such as machine learning, deep learning, or a large-scale language model represented by ChatGPT. It is assumed that highly proficient users are familiar with electronic contract procedures, while less proficient users are not familiar with electronic contract procedures. It is assumed that less proficient users are unable to properly input data during the contract confirmation process described below, and are therefore unable to execute the contract confirmation process, or have difficulty in inputting data.

[0063] <Additional Message Creation Process (Second Embodiment)> The creation step executes a step of creating a message according to the contract type, contract contents, and clauses or provisions contained in the contract document accepted in the contract acceptance step. Specifically, the contract creation unit 1042 of the server 10 includes information regarding the content and significance of the contract type, contract content, and clauses or provisions contained in the contract document in the accompanying message based on the contract type, contract content, and clauses or provisions contained in the contract document of the contract document related to the contract creation process. For example, information explaining what type of transaction the contract type of the contract document is used for, and information indicating points that should be particularly checked when checking the contract document, etc., are included in the accompanying message. For example, the accompanying message may include information explaining what rights or obligations the contract contents, clauses or provisions prescribe, and information indicating points that should be particularly checked when reviewing the contract contents, clauses or provisions. Information on the contents and meanings of clauses, points to be particularly checked when checking, etc. can be configured to be generated from the contents of the contract document using any AI technology such as machine learning, deep learning, large-scale language models represented by ChatGPT, etc. For example, by inputting a contract document as input data and inputting a prompt including an instruction to output information explaining what rights or obligations the contract contents, clauses or clauses prescribe, and information indicating points to be particularly checked when checking the contract contents, clauses or clauses, into a large-scale language model, it is possible to generate information explaining what rights or obligations the contract contents, clauses or clauses prescribe, and information indicating points to be particularly checked when checking the contract contents, clauses or clauses. <Additional Message Creation Process (Third Embodiment)> The creating step extracts important points based on the contract document accepted in the contract accepting step, and creates a message including the important points. Specifically, the contract preparation unit 1042 of the server 10 extracts information such as important clauses, specific obligations and rights, high amounts, short deadlines, etc. based on the contents of the contract document related to the contract preparation process, and includes it in the accompanying message. The extraction of attention points can be configured to be generated from the contents of the contract document using any AI technology such as machine learning, deep learning, large-scale language models represented by ChatGPT, etc. For example, attention points based on the contract document can be extracted by inputting a prompt including an instruction to extract attention points into a large-scale language model using the contract document as input data. <Additional Message Creation Process (Fourth Embodiment)>

[0064] The creating step executes a step of extracting important points regarding a deadline or amount based on the contract document accepted in the contract accepting step, and creating a message including the important points. Specifically, the contract creation unit 1042 of the server 10 can identify and extract important points regarding deadlines and amounts based on the contents of the contract document related to the contract creation process, and generate advice and warnings based on this information as additional messages. The term includes the term related to the rights or obligations under the contract, such as the due date for conclusion, the due date for payment, etc. The amount includes the amount related to the rights or obligations under the contract, such as the payment amount, the amount received, etc. For example, based on information such as the payment deadline and penalty amount contained in the contract document, a message emphasizing the importance of the deadline to the second user and a warning regarding the amount that must be paid in case of delay can be included. In addition, when the amount included in the contract document is higher than the amount normally specified in the contract type to which the contract document belongs, or when the deadline included in the contract document is shorter than the amount normally specified in the contract type to which the contract document belongs, points to which the user should pay particular attention are automatically extracted, and a message corresponding to the points is included in the accompanying message. The important points regarding the deadline or amount can be configured to be generated from the contents of the contract document using any AI technology such as machine learning, deep learning, large-scale language models represented by ChatGPT, etc. For example, by using the contract document as input data and inputting a prompt including an instruction to extract important points regarding the deadline or amount into a large-scale language model, it is possible to extract important points regarding the deadline or amount based on the contract document.

[0065] <Additional message display processing> In step S107, the contract creation unit 1042 of the server 10 executes a presentation step of presenting the message created in the creation step to the first user. The presentation step executes a step of presenting a message input field that presents the message created in the creation step in an editable manner, together with information on the second user's proficiency level and a confirmation input field that can accept an input operation for confirmation in the previous confirmation step. Specifically, the contract creation unit 1042 of the server 10 transmits the created associated message to the first user terminal 20. The control unit 204 of the first user terminal 20 inputs the received associated message into the input field D12, and presents the content of the associated message to the first user in an editable form. The contract creation unit 1042 of the server 10 calculates the proficiency of the second user and transmits it to the first user terminal 20. The proficiency of the second user is similar to the proficiency explained in the accompanying message creation process (first embodiment). The control unit 204 of the first user terminal 20 displays the received proficiency in the proficiency D13 of the accompanying message screen D1. Note that the proficiency of the second user does not necessarily need to be presented as the proficiency D13, and may be indicated by direct or indirect description in the input field D12 or the like. The contract creation unit 1042 of the server 10 displays and presents the message generation button D11, the auxiliary message input field D12, the second user's proficiency level D13, and the confirmation button D14 on the auxiliary message screen D1.

[0066] In step S107, the contract preparation unit 1042 of the server 10 executes a confirmation step of accepting an input operation for confirming the message presented in the presentation step from the first user. Specifically, the first user checks the content of the associated message entered in the input field D12, and adds or modifies it if necessary. After checking that there is no problem with the content of the associated message, the first user operates the input device 206 of the first user terminal 20 to press the confirm button D14. The control unit 204 of the first user terminal 20 transmits a request to transmit the contract information to the server 10. The accompanying message screen D1 may be configured to close when the first user presses the Confirm button D14. In this case, the first user can transmit a request to transmit the contract information to the server 10 by operating the input device 206 of the first user terminal 20 and pressing the Send button 540.

[0067] The accompanying message created by the first user may be stored in the document table 1014 or the like in association with the contract information.

[0068] In step S108, the contract creation unit 1042 of the server 10 transmits a message to the second user notifying the second user that a request to confirm the contract information has been sent from the first user. The contract creation unit 1042 of the server 10 executes a transmission step of transmitting the message created in the creation step to the second user. The message transmitted to the second user includes the accompanying message created by the first user in steps S106 and S107.

[0069] The sending step executes a step of sending the message to the second user in response to receiving an input operation for confirming the message in the confirmation step. Specifically, a request to send the contract information together with the accompanying message may be sent to the server 10 in response to the first user pressing the Confirm button D14 or the Send button 540. As a result, in response to the first user pressing the Confirm button D14, a message notifying the second user that a confirmation request for the contract information has been sent from the first user including the accompanying message is sent to the second user's email address by a communication means such as email. The second user can quickly and comfortably perform the input operation for the contract confirmation process according to the contents of the message and the accompanying message.

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

[0071] When the first user sets an access code for the second user, the first user separately communicates the access code to the second user by means of e-mail, etc. In this way, even if the message notified to the second user is obtained by a third party, the third party cannot execute the contract confirmation process unless he or she obtains the access code.

[0072] 15 is an example of a screen showing a message notified to the second user terminal 30. The message screen 60 displayed on the display 3081 of the second user terminal 30 includes information on a message 61, a URL 62 including a document ID for identifying contract information, and an associated message 63. The associated message 63 is an associated message created by the first user in step S106 of the contract creation process.

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

[0074] On screen 50 for creating contract information, input items 532, 533, and 534 are drawn as drawing objects. In input items 532 and 533, user identification information "USER-B" of a user who has selected and set to input the input item is drawn as an assignment, and an item called "text" is drawn as an input item type. In input item 534 related to stamping, user identification information "USER-C" of a user who has selected and set to stamp is drawn as an assignment, and an item called "stamp" is drawn as an input item type.

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

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

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

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

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

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

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

[0082] 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 identification information for identifying the second user included in the URL. If the second user is not registered as a user in 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.

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

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

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

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

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

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

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

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

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

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

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

[0094] Specifically, the contract confirmation unit 1043 of the server 10 acquires the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 searches the group ID item in the group table 1013 based on the acquired group ID item, acquires the administrator ID item, identifies a user having authority equivalent to that of an administrator by searching the user ID in the user table 1012 based on the administrator ID, and transmits a message notifying that the contract confirmation process has been completed.

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

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

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

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

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

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

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

[0102] <Basic functional configuration of computer 90> A description will now be given of the functional configuration of a computer realized by the basic hardware configuration (FIG. 18) of a computer 90. The computer comprises at least the functional units of a control unit, a storage unit, and a communication unit.

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

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

[0105] The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Furthermore, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with a program. Furthermore, the control unit can cause the processor 901 to execute processes of adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

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

[0107] In addition, the database and master in this disclosure may include any data structure (such as a list, a dictionary, an associative array, or an object) in which information is structurally defined. The data structure also includes data that can be considered as a data structure by combining data with a function, class, method, or the like written in any programming language.

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

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

[0110] (Appendix 1) A program having a processor and a memory unit, for causing a computer to execute electronic contract procedures between multiple users, wherein the processor executes a contract acceptance step (S101) of accepting a contract document relating to a contract from a first user, a creation step (S106) of creating a message from the first user to a second user requesting confirmation of the contract document in response to an input operation by the first user, and a transmission step (S108) of sending the message created in the creation step to the second user. This makes it possible to create an additional message for requesting the second user to confirm the contract document in response to an input operation by the first user, and to transmit the message to the second user.

[0111] (Appendix 2) The program according to claim 1, wherein the creating step (S106) is a step of creating a message according to the second user. This makes it possible to create an additional message including text for assisting the second user in completing an electronic contract procedure in accordance with the second user, and to transmit the message to the second user.

[0112] (Appendix 3) The program according to claim 2, wherein the creating step (S106) is a step of creating a message according to the second user's level of familiarity with electronic contract procedures. This allows an additional message including text to assist the second user (assistance text) to be created according to the second user's level of familiarity with electronic contract procedures, and to be sent to the second user. The second user can receive an additional message including an appropriate support text according to his / her own level of familiarity.

[0113] (Appendix 4) The program described in Appendix 3, wherein the creation step (S106) is a step of creating a message according to the level of proficiency calculated based on the number of electronic contract procedures concluded in the second user's electronic contract system. This allows a supplementary message including a sentence to assist the second user to be created according to the second user's level of proficiency based on the number of electronic contract procedures concluded to date, and to be sent to the second user. The second user can receive a supplementary message including a sentence to assist the second user according to his or her level of proficiency.

[0114] (Appendix 5) The program according to appendix 1, wherein the creating step (S106) is a step of creating a message according to the contract type of the contract document accepted in the contract accepting step. This makes it possible to create an additional message including text to assist the second user in electronically completing the contract procedure in accordance with the contract type of the contract document, and to transmit the additional message to the second user. For example, the accompanying message may include a support sentence that briefly describes the procedure for electronic contract procedures according to the contract type.

[0115] (Appendix 6) The program according to appended claim 1, wherein the creating step (S106) is a step of creating a message according to the contract contents of the contract document accepted in the contract accepting step. This makes it possible to create an additional message including text to assist the second user in completing the electronic contract procedure in accordance with the contract contents of the contract document, and to transmit the additional message to the second user. For example, the accompanying message may include a support sentence that briefly describes the procedure for electronic contract procedures according to the contents of the contract.

[0116] (Appendix 7) The program according to appendix 6, wherein the creating step (S106) is a step of creating a message according to a clause or provision included in the contract document accepted in the contract accepting step. This makes it possible to create and transmit to the second user an additional message including text to assist the second user in completing the electronic contract procedure in accordance with the clause or provisions contained in the contract of the contract document. For example, the accompanying message may include a supporting document that briefly describes the procedure for electronic contract procedures according to the clauses or provisions contained in the contract.

[0117] (Appendix 8) The program according to appendix 6, wherein the creation step (S106) is a step of extracting points of caution based on the contract document accepted in the contract acceptance step, and creating a message including the points of caution. This makes it possible to create an accompanying message including points (attention points) that the second user should check with particular care according to the contract contents of the contract document, and to transmit the accompanying message to the second user. The second user can refer to the important points included in the accompanying message and proceed with the electronic contract procedure more comfortably.

[0118] (Appendix 9) The program according to appendix 1, wherein the creation step (S106) is a step of extracting important points regarding a deadline or amount based on the contract document accepted in the contract acceptance step, and creating a message including the important points. This makes it possible to create an additional message including the part (important point) related to the deadline or amount included in the contract contents of the contract document, and transmit it to the second user. The second user can refer to important points contained in the accompanying message and proceed with the electronic contract procedure more comfortably.

[0119] (Appendix 10) The program described in Appendix 1, wherein the creation step (S106) is a step of creating a message indicating the work procedure of electronic contract procedures in the electronic contract system. This allows the second user to carry out the electronic contract procedure by referring to the accompanying message indicating the procedure for the electronic contract procedure.

[0120] (Appendix 11) 2. The program according to claim 1, wherein the message created in the creating step (S106) is an additional message set by the first user, different from a standard message requesting the second user to confirm the contract document. This allows the second user to receive an additional message for requesting the second user to confirm the contract document, separate from the standard message for requesting the second user to confirm the contract document.

[0121] (Appendix 12) A program as described in Appendix 1, in which a processor executes a presentation step (S107) of presenting the message created in the creation step to a first user, and a confirmation step (S107) of accepting an input operation from the first user to confirm the message presented in the presentation step, and a transmission step (S108) is a step of transmitting the message to a second user in response to accepting the input operation to confirm the message in the confirmation step. This allows the first user to receive the created accompanying message, and also allows the first user to transmit the accompanying message to the second user by performing a confirmation operation on the presented message.

[0122] (Appendix 13) The presentation step (S107) is a step of presenting a message input field that presents the message created in the creation step in an editable manner, and a confirmation input field that can accept information about the second user's proficiency and an input operation for confirmation in the previous confirmation step, the program described in Appendix 12. This allows the first user to be presented with both the accompanying message and the second user's proficiency. The first user can edit the content of the accompanying message taking into consideration the second user's proficiency, etc. The first user can perform an input operation to confirm the accompanying message on the presentation screen, and can send the accompanying message to the second user.

[0123] (Appendix 14) The program described in Appendix 1, wherein the creation step is a step of creating a message requesting confirmation of the contract document using the generation AI. This makes it possible to create an accompanying message that the second user can comfortably check when checking the contract document.

[0124] (Appendix 15) A method implemented on a computer having a processor and a memory, the processor performing all the steps performed in the invention according to any one of claims 1 to 14. This makes it possible to create an additional message for requesting the second user to confirm the contract document in response to an input operation by the first user, and to transmit the message to the second user.

[0125] (Appendix 16) An information processing device comprising a control unit and a memory unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 14. This makes it possible to create an additional message for requesting the second user to confirm the contract document in response to an input operation by the first user, and to transmit the message to the second user.

[0126] (Appendix 17) A system comprising means for performing all the steps performed in any one of claims 1 to 14. This makes it possible to create an additional message for requesting the second user to confirm the contract document in response to an input operation by the first user, and to transmit the message to the second user. [Explanation of symbols]

[0127] 1 System, 10 Server, 101 Memory unit, 104 Control unit, 106 Input device, 108 Output device, 20 First user terminal, 201 Memory unit, 204 Control unit, 206 Input device, 208 Output device, 30 Second user terminal, 301 Memory unit, 304 Control unit, 306 Input device, 308 Output device

Claims

1. A program for causing a computer to execute an electronic contract procedure between a plurality of users, the program comprising: a processor; and a storage unit, The processor, a contract receiving step of receiving a contract document relating to a contract from a first user; a creating step of creating a message from the first user to a second user requesting confirmation of the contract document in response to an input operation by the first user; a sending step of sending the message created in the creating step to the second user; A program that executes.

2. The creating step is a step of creating the message according to the second user. The program according to claim 1.

3. The creating step is a step of creating the message according to the second user's proficiency level in electronic contract procedures. The program according to claim 2.

4. The creation step is a step of creating the message according to a proficiency level calculated based on the number of electronic contract procedures concluded in the electronic contract system of the second user, The program according to claim 3.

5. the creating step is a step of creating the message according to the contract type of the contract document accepted in the contract accepting step; The program according to claim 1.

6. the creating step is a step of creating the message according to the contract content of the contract document accepted in the contract accepting step; The program according to claim 1.

7. the creating step is a step of creating the message in accordance with a clause or a provision included in the contract document accepted in the contract accepting step; The program according to claim 6.

8. The creation step is a step of extracting attention points based on the contract document accepted in the contract acceptance step, and creating the message including the attention points. The program according to claim 6.

9. The creating step is a step of extracting important points related to a deadline or an amount based on the contract document accepted in the contract accepting step, and creating the message including the important points. The program according to claim 1.

10. The creating step is a step of creating the message indicating the procedure of an electronic contract procedure in an electronic contract system. The program according to claim 1.

11. The message created in the creating step is an additional message set by the first user, which is different from a standard message requesting the second user to confirm the contract document. The program according to claim 1.

12. The processor, a presentation step of presenting the message created in the creation step to the first user; a confirmation step of accepting an input operation from the first user for confirming the message presented in the presentation step; Run The sending step is a step of sending the message to the second user in response to receiving an input operation for confirming the message in the confirming step. The program according to claim 1.

13. The presenting step includes: a message input field that presents the message created in the creating step in an editable manner; Information regarding the proficiency level of the second user; and a confirmation input field capable of receiving an input operation for the confirmation in the confirmation step; The step of presenting both The program according to claim 12.

14. The creation step is a step of creating a message requesting confirmation of the contract document using a generation AI. The program according to claim 1.

15. A method implemented on a computer having a processor and a memory, the processor performing all of the steps performed in any one of the inventions according to claims 1 to 14.

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

17. A system comprising means for performing all the steps performed in any one of claims 1 to 14.

Images