Contract signing program, information processing device, information processing system, information processing method

Abstract

To provide users with a contract signing program, information processing device, information processing system, and information processing method that allow them to conveniently use multiple electronic contract services. [Solution] In an information processing system including an information processing device comprising a processor and a memory unit, the contract conclusion program causes the processor to execute a contract acquisition step of acquiring pre-contract information from an external contract conclusion service, a contract storage step of storing the pre-contract information acquired from the external contract conclusion service in the contract acquisition step, and a list presentation step of presenting the pre-contract information acquired from the external contract conclusion service and stored in the contract storage step to the user in a manner that can be distinguished from other contract information.

Description

[Technical Field]

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

[0002] With the development and popularization of computer technology, documents for which paper media have conventionally been used are being digitized. For example, it has been considered that documents such as contracts that require the signatures and seals of the parties are also managed as electronic data. Patent Document 1 discloses a technology for constructing a new service by linking with existing operations and a public WWW server while maintaining the linkage of the screen that the user is viewing. Patent Document 2 discloses a technology for checking the validity of an input value on a transition source screen in a linking source Web application before transitioning to a linking destination Web application without making the user aware, and smoothly and safely linking processing to the linking destination Web application. Patent Document 3 discloses a member registration support server, method, and system in which a third-party server holds user information and saves the user the trouble of authentication. [Prior Art Documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2001-060187 [Patent Document 2] Japanese Unexamined Patent Application Publication No. 2008-077511 [Patent Document 3] Japanese Unexamined Patent Application Publication No. 2011-070390 [Summary of the Invention] [Problem to be Solved by the Invention]

[0004] Some users utilize multiple electronic contract services. In particular, with electronic contract services, both parties to a contract must use the same service. Therefore, users have to selectively switch between multiple electronic contract services depending on the other party, which is inconvenient for them. Therefore, this disclosure has been made to solve the above-mentioned problems, and its purpose is to provide users with technology that allows them to conveniently use multiple electronic contract services. [Means for solving the problem]

[0005] A contract signing program comprising a processor and a memory unit, for causing a computer to execute electronic contract procedures between users, wherein the contract signing program causes the processor to execute a contract acquisition step of acquiring pre-contract information from an external contract signing service; a contract storage step of storing the pre-contract information acquired from the external contract signing service in the contract acquisition step; and a list presentation step of presenting the pre-contract information acquired from the external contract signing service stored in the contract storage step to the user in a manner that distinguishes it from other contract information. [Effects of the Invention]

[0006] According to this disclosure, users can conveniently utilize multiple electronic contract services. [Brief explanation of the drawing]

[0007] [Figure 1] This is a block diagram showing the functional configuration of Information Processing System 1. [Figure 2] This block diagram shows the functional configuration of Server 10. [Figure 3] This is a block diagram showing the functional configuration of the first user terminal 20. [Figure 4] This is a block diagram showing the functional configuration of the second user terminal 30. [Figure 5]It is a block diagram showing the functional configuration of the external server 40. [Figure 6] It is a diagram showing the data structure of the user table 1012. [Figure 7] It is a diagram showing the data structure of the group table 1013. [Figure 8] It is a diagram showing the data structure of the document table 1014. [Figure 9] It is a diagram showing the data structure of the confirmation table 1015. [Figure 10] It is a diagram showing the data structure of the input item table 1016. [Figure 11] It is a diagram showing the data structure of the access authority table 1017. [Figure 12] It is a diagram showing the data structure of the contract document group table 1018. [Figure 13] It is a flowchart showing the operation of contract document creation processing. [Figure 14] It is a flowchart showing the operation of contract document confirmation processing. [Figure 15] It is a flowchart showing the operation of external storage processing. [Figure 16] It is a flowchart showing the operation of external confirmation processing. [Figure 17] It is a screen example showing the operation of contract document creation processing. [Figure 18] It is a screen example showing a message notified to the second user terminal 30. [Figure 19] It is a screen example showing the operation of contract document confirmation processing. [Figure 20] It is a screen example showing contract information presented as a list on the second user terminal 30. [Figure 21] It is a block diagram showing the basic hardware configuration of the computer 90. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference signs, and repeated descriptions are omitted. It should be noted that the following embodiments do not unduly limit the content of the present disclosure described in the claims. In addition, not all of the components shown in the embodiments are essential components of the present disclosure. Furthermore, each drawing is a schematic diagram and is not necessarily strictly illustrated.

[0009] <Configuration of Information Processing System 1> The information processing system 1 according to the present disclosure is an information processing system for implementing a service of storing and managing contract information concluded between a plurality of users. The information processing system 1 includes information processing devices, i.e., a server 10, a first user terminal 20, a second user terminal 30, and an external server 40, which are connected via a network N. FIG. 1 is a block diagram showing a functional configuration of the information processing system 1. FIG. 2 is a block diagram showing a functional configuration of the server 10. FIG. 3 is a block diagram showing a functional configuration of the first user terminal 20. FIG. 4 is a block diagram showing a functional configuration of the second user terminal 30. FIG. 5 is a block diagram showing a functional configuration of the external server 40.

[0010] Each of the information processing devices is constituted by a computer including an arithmetic device and a storage device. The basic hardware configuration of a computer and the basic functional configuration of a computer implemented by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, the second user terminal 30, and the external server 40, descriptions overlapping with the basic hardware configuration and the basic functional configuration of the computer described later are omitted.

[0011] <Configuration of Server 10> Server 10 is an information processing device that provides electronic contract conclusion services between multiple users. Server 10 is an information processing device that provides services for storing and managing contract information concluded between multiple users. 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, an access permission table 1017, and a contract group table 1018.

[0013] The application program 1011 is a program that causes the control unit 104 of the server 10 to function as individual functional units.

[0014] User table 1012 is a table that stores and manages information about member users (hereinafter referred to as "users") who use the service. When a user registers to use the service, their information is stored in a new record in user table 1012. This will enable users to utilize the services provided in this disclosure. Note that users utilizing the services under this disclosure do not necessarily need to be registered in user table 1012. User table 1012 is a table with User ID as the primary key and contains columns for User ID, Username, Email Address, Group ID, and Approval Authority. Figure 6 shows the data structure of user table 1012.

[0015] The User ID is an item that stores user identification information to identify a user. User identification information is an item that is set to a unique value for each user. The username field is used to store the user's real name. However, the username can also be a nickname or any other string of characters. The email address field is used to store the user's email address. The Group ID is an item that stores the group identification information of the group to which the user belongs. Groups are defined by the Group Table 1013 described later, and a user may belong to multiple groups. Approval authority is an item that stores user authorization information regarding contract signing. Users who have the authority to approve contract signing (approval authority) will have information such as True stored in their records. On the other hand, users who do not have the authority to approve contract signing will have information such as False, blank, or null stored in their records. It is also possible to configure the system so that approval permissions can be set according to the contract information. For example, user A may have approval permissions for a specific contract information A, but not for a specific contract information B. The system can be configured to allow approval authority to be set according to the type of contract information (contract information type), such as confidentiality agreements, joint research agreements, and contract work agreements. For example, User A may have approval authority for confidentiality agreements but not for contract work agreements. Alternatively, the system could be configured to store multiple levels (ranks) of permission information depending on the user's department, government office, etc. For example, temporary staff could be assigned rank C, regular employees rank B, managers rank A, and executives rank S in the approval authority field. Based on the contract information, such as contract type and contract amount, only users with approval authority of a predetermined rank or higher (for example, A or higher for non-disclosure agreements) could approve the conclusion of contracts.

[0016] Group table 1013 is a table that stores and manages information about the groups to which a user belongs (group information). A group can be defined as any group to which a user belongs, such as a corporation, company, club, organization, or department within a company. Group table 1013 is a table with Group ID as the primary key and containing columns for Group ID, Group Name, and Administrator ID. Figure 7 shows the data structure of group table 1013.

[0017] The Group ID is an item that stores group identification information used to identify a group. This group identification information is an item with a unique value assigned to each group. The group name is an item that stores the name of the group. The group name can be set to any string. The Administrator ID is an item that stores the user identification information of users who have administrator privileges within a group. Users with administrator privileges can arbitrarily define and set administrator IDs for users who have a certain level of status or authority or higher within a group such as an organization.

[0018] Document table 1014 is a table for storing and managing information (contract information) related to electronic contracts exchanged between the creator and the recipient. Document table 1014 is a table with Document ID as the primary key and containing columns for Document ID, Document Data, Creator ID, and Endpoint. Figure 8 shows the data structure of document table 1014.

[0019] The Document ID is an item that stores document identification information used to identify contract information. The document identification information is an item with a unique value assigned to each piece of contract information. Document data is an item that stores contract information (binary or text data). Specifically, document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). The Creator ID is a field that stores user identification information to identify the user who created the contract information. The endpoint is an item that stores the endpoint used to identify the contract information in the external electronic contract service that was referenced when the contract information was obtained from that external electronic contract service. Specifically, it stores strings that identify the web page on which the user accesses the contract information, such as the URL of the page that identifies the contract information.

[0020] Confirmation table 1015 is a table that stores and manages information (confirmer information) including the email address of the user who will be confirming the contract information. Confirmation table 1015 is a table that has columns for document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time. Figure 9 shows the data structure of confirmation table 1015.

[0021] The document ID is an item that stores the document identification information of the contract information to be reviewed by the verifier. The "Verification Order" field stores information about the order in which contract information is reviewed by the reviewers. The contract information stored by the creator is circulated to the reviewers in the order of the verification order, and verification is performed accordingly. The verifier email address field stores the email address of the person who verifies the contract information. The verifier email address does not need to be registered beforehand to use the services related to this disclosure. In other words, the verifier email address does not need to be included in user table 1012. The confirmation flag is an item that stores confirmation identification information to determine whether the confirmation procedure for contract information has been completed by the verifier. When the confirmation of contract information is completed by the verifier, information indicating that the confirmation has been completed, such as a value of True, is stored in the confirmation flag item. Language data is an item that stores information about the verifier's language (language information). The access code is an item that stores the access code set for the verifier. The date and time field stores the date and time when the verifier performed the contract information verification procedure. Specifically, it stores the date and time when the verification identification information was stored in the verification flag field.

[0022] The input item table 1016 is a table that stores and manages information about input items associated with electronic contract information (input item information). Input item table 1016 is a table that has columns for input item ID, document ID, inputter ID, input data, input rules, and date and time. Figure 10 shows the data structure of the input item table 1016.

[0023] The input field ID is an item that stores input field identification information used to identify an input field. The document ID is an item that stores the document identification information of the electronic contract information to which the input field is associated. The Inputter ID is a field that stores the user identification information or email address of the person who entered the data into the input field. Specifically, the Inputter ID stores the Creator ID, the email address of the user identified by the Creator ID, and the Confirmer's email address. Input data is an item that stores the input data entered by the user into the input fields. An input rule field is an item that stores information about the input rules for an input item. Input rules can store information about data types such as date, datetime, text, and integer, as well as, for strings, the number of characters, regular expressions for strings, and other arbitrary input rules for any input item. The date and time field stores the date and time when the user entered data into the input field.

[0024] Access permission table 1017 is a table for storing and managing information related to access permissions (access permission information). Access permission table 1017 is a table that has columns for User ID, Service ID, and Access Token. Figure 11 shows the data structure of the access permission table 1017.

[0025] The User ID is an item that stores user identification information used to identify a user. The Service ID is an item that stores service identification information to identify a service. Specifically, for each external electronic contract service, the Service ID stores a string of characters or other information that identifies that electronic contract service. An access token is an item that stores access permission information when a user accesses an external electronic contract service identified by a service ID. Specifically, the access token stores a string issued to the user by the external electronic contract service. When accessing the external electronic contract service, the user sends the access token, and the external electronic contract service identifies the user based on the string of the access token and provides various information services to that user. The access token may also include authentication information such as a user ID and password, which are commonly required when logging into and accessing web services.

[0026] The contract group table 1018 is a table for storing and managing information about 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, cabinets may be called groups, tags, labels, etc. The contract group table 1018 is a table that has columns for document ID and cabinet ID. Figure 12 shows the data structure of the contract group table 1018.

[0027] The document ID is an item that stores document identification information used to identify contract information. The cabinet ID stores cabinet identification information to identify a cabinet. The cabinet ID is classification information used to manage and classify contract information.

[0028] <Configuration of the control unit 104 of server 10> The control unit 104 of the server 10 includes a user registration control unit 1041, a contract creation unit 1042, a contract confirmation unit 1043, an external storage unit 1045, and an external confirmation unit 1046. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0029] The user registration control unit 1041 processes information of users who wish to use the services related to this disclosure and stores it in the user table 1012. Information stored in the user table 1012 is obtained when a user opens a web page operated by the service provider from any information processing terminal, enters information into a designated input form, and sends it to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, and user registration is completed. As a result, users 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 prescribed review and restrict whether or not the user can use the service. The user ID can be any string or number that can identify the user, and may be any string or number desired by the user, or the user registration control unit 1041 may automatically set any string or number.

[0030] The contract creation unit 1042 executes the contract creation process. Details will be described later.

[0031] The contract verification unit 1043 executes the contract verification process. Details will be described later.

[0032] The external storage unit 1045 performs external storage processing. Details will be described later.

[0033] The external verification unit 1046 executes the external verification process. Details will be described later.

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

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

[0036] 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 services related to this disclosure to the user. The first user ID 2011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the first user terminal 20.

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

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

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

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

[0041] <Configuration of the second user terminal 30> The second user terminal 30 is an information processing device operated by a user of the service. The second user terminal 30 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile device such as a smartphone or tablet. It may also be a wearable device such as an HMD (Head Mount Display) or a smartwatch. The second user terminal 30 includes a storage unit 301, a control unit 304, an input device 306, and an output device 308.

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

[0043] 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 services related to this disclosure to the user. The second user ID 3011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the second user terminal 30.

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

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

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

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

[0048] <Operation of Information Processing System 1> The following describes each process of Information Processing System 1. Figure 13 is a flowchart showing the operation of the contract creation process. Figure 14 is a flowchart showing the operation of the contract verification process. Figure 15 is a flowchart showing the operation of the external storage processing. Figure 16 is a flowchart showing the operation of the external verification process. Figure 17 shows an example screen illustrating the operation of the contract creation process. Figure 18 shows an example screen displaying a message notified to the second user terminal 30. Figure 19 shows an example screen illustrating the operation of the contract verification process. Figure 20 is an example screen showing the contract information displayed in a list on the second user terminal 30. Figure 21 is a block diagram showing the basic hardware configuration of computer 90.

[0049] In this disclosure, the contract creation process and contract verification process on server 10 are described below. The external server 40 can also perform the same contract creation process and contract verification process. The contract creation process and contract verification process on the external server 40 are the same as those on server 10, respectively, so their description is omitted.

[0050] <Contract creation process> The contract creation process involves the creator generating electronic contract information and sending it to the verifier.

[0051] Figure 18 shows an example screen illustrating the operation of the contract creation process. The screen 50 displayed on the display 2081 of the first user terminal 20, which is used to create contract information, displays a status 510 indicating the current status of contract information creation, buttons 521, 522, and 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, and 534, and a send button 540.

[0052] <Overview of the contract creation process> The contract creation process is a series of steps in which the creator creates electronic contract information, sets the recipient (the verifier) ​​of the electronic contract information, sets the input fields for the electronic contract information, sets input rules for the input fields, receives input data for the input fields from the creator, and sends the electronic contract information to the designated verifier.

[0053] <Details of the contract creation process> In step S101, the contract creation unit 1042 of the server 10 receives contract information from the creator that is to be concluded between the creator and the verifier. 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 can be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and can be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and sends the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 receives the first user ID 2011 and the document data and stores them in the creator ID and document data fields of the 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.

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

[0055] In step S102, the first user operates the input device 206 of the first user terminal 20 to select and identify the user who will be the verifier (recipient) of the contract information. In this disclosure, the first user selects and identifies the second user as the recipient. The first user operates the input device 206 of the first user terminal 20 to enter the email address of the second user, who will act as the verifier, 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 contract information created and stored in step S101 in the verifier email address and document ID fields of the verification table 1015, respectively, and stores the contract information in association with the second user's email address. The first user may also set the language and access code of the second user and store them in association with the second user's email address. At this time, the value 1 is stored in the "Confirmation Order" field of the confirmation table 1015. In step S102, the first user may select and set multiple users to be confirmers. In this case, the value in the "Confirmation Order" field of the users to be confirmers is incremented by one according to the selection order and stored. This sets the circulation order of the confirmers in the contract confirmation process described later. Note that setting the circulation order is not mandatory.

[0056] In step S103, the first user operates the input device 206 of the first user terminal 20 to set the input items for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 to set multiple input fields for the contract information created and stored in step S101. The input fields can be any fields, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a checkbox field for selecting check items, and a date field for entering the date. The first user operates the input device 206 on the first user terminal 20 and sends a request to the server 10 to add an input item. 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 the new record in the input item table 1016. In this way, the newly added input item information is stored in association with the contract information. The first user can store multiple input item information in association with the contract information.

[0057] In step S104, the first user sets input rules for each input item to be added. The first user specifies the input rules for each input item information set in step S103 by operating the input device 206 of the first user terminal 20 and sends 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 input item information in the input item table 1016. This allows input rules to be set for each input item.

[0058] In step S105, the contract creation unit 1042 of the server 10 receives input data for multiple input items entered by the first user. Specifically, the first user inputs input data for each input item set in step S104 by operating the input device 206 of the first user terminal 20. For example, the first user may input data for a number used to manage contract information, such as a reference number within the group to which they belong, into the input item where a management number is set. The first user may also input data for the date of the contract signing of the contract information into the input item where a contract signing date is set. Once the first user has finished inputting data into the input items, they send the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of server 10 stores the received input data in the input data field of the input item information in the input item table 1016, which is identified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

[0059] The contract creation unit 1042 of server 10 receives an instruction from the first user to request the second user to conclude a contract regarding the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 and sends a request to the server 10 to send contract information by pressing the send button 540 displayed on the screen 50 for creating contract information.

[0060] In step S106, the contract creation unit 1042 of the server 10 sends a message to the second user notifying them that a request for confirmation of contract information has been sent by the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order column in the confirmation table 1015 and identifies the user who will be the first confirmer (first confirming user) with the smallest value stored in the confirmation order column. In this disclosure, the first confirming user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's email address notifying them that a request for confirmation of contract information has been sent by the first user, via email or other means of communication. The message sent to the second user will include information about a URL (Uniform Resource Locator) containing a document ID to identify the contract information. The URL may directly contain the document ID, or it may contain information such as an encrypted string of the document ID, or a string that can identify the document ID by referring to an unillustrated table. The URL may also contain information to identify the second user. For example, if the second user has not registered for the service related to this disclosure, the URL must contain information to identify the second user.

[0061] If the first user sets an access code for the second user, the first user will communicate the access code to the second user via email or other means. This ensures that even if the message sent to the second user is intercepted by a third party, the third party cannot perform the contract verification process unless they obtain the access code.

[0062] Figure 19 shows an example screen displaying a message notified to the second user terminal 30. The message screen 60 displayed on the display 3081 of the second user terminal 30 includes a message 61 and information about a URL 62 containing a document ID for identifying contract information.

[0063] <Variation> If the first user selects and sets multiple verifiers in step S102, the system may be configured to allow different input field information to be set independently for each of the multiple verifiers in step S103. For example, if the first user sets two users, the second user and the ninth user, as verifiers, the input fields for the contract start date and contract end date may be set for the second user, and the input field for the contract signing date may be set for the ninth user. In this case, in the contract confirmation process described later, the second user can input data for the contract start date and contract end date, but not for the contract signing date. On the other hand, the ninth user cannot input data for the contract start date and contract end date, but can input data for the contract signing date. The system may also be configured to allow multiple verifiers to be selected and set for a single input field.

[0064] On screen 50 for creating contract information, input fields 532, 533, and 534 are drawn as drawing objects. For input fields 532 and 533, the user identification information "USER-B" of the user who has been selected and set to input the input field is drawn as the assignment, and the input field type is drawn as "Text". For input field 534 related to stamping, the user identification information "USER-C" of the user who has been selected and set to stamp is drawn as the assignment, and the input field type is drawn as "Stamp".

[0065] <Contract Verification Process> The contract verification process is the process by which a verifier confirms the contents of the electronic contract information received from the creator.

[0066] <Overview of contract verification process> The contract verification process is a series of operations that involves receiving access from the verifier, presenting the verifier with a verification screen displaying the contract information, receiving input data from the verifier for the input fields, and receiving data from the verifier regarding the verification of the contract information.

[0067] <Details of contract verification process> In step S301, the second user, who will act as the verifier, can open the webpage specified by the URL by operating the input device 306 or the like on the second user terminal 30 and selecting the URL contained in the received message. This allows the browser application on the second user terminal 30 to open the webpage specified by the URL. As a result, the second user terminal 30 sends a request to the server 10 to execute the contract verification process.

[0068] If the second user's record in the verification table 1015 contains an access code field, the system can request the second user to enter an access code and then compare the entered access code with the access code stored in the second user's record in the verification table 1015 to perform authentication for the second user. Specifically, server 10 sends an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 on the second user terminal 30, enters the access code, and sends it to server 10. The contract verification unit 1043 of server 10 determines whether the received access code matches the access code stored in the second user's record in the verification table 1015. If they match, the contract verification process continues. If they do not match, the contract verification process is terminated. Note that the authentication process using the access code may be omitted.

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

[0070] In step S302, the contract verification unit 1043 of the server 10 identifies the second user and obtains the second user's approval authority information. The second user may be identified based on the second user ID 3011 included in the request received from the second user terminal 30, or based on identification information for identifying the second user included in the URL. If the second user has not registered for the service related to this disclosure, it is necessary to identify the second user from the URL. For example, the URL may include information for identifying the second user, such as the second user's email address or user ID.

[0071] The contract verification unit 1043 of server 10 searches the user ID field in user table 1012 based on the user identification information of the identified second user and retrieves the approval authority field for the second user. In this disclosure, the approval authority for the second user is stored in user table 1012, but the approval authority for the second user may also be stored for each group to which the second user belongs, or for each contract information or contract information type. The contract verification unit 1043 of server 10 retrieves the approval authority information for the second user for the target contract information. Furthermore, if the second user has not registered for the service related to this disclosure, the processing may be carried out by treating the second user as a user without approval authority.

[0072] In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, verifier information (information identifying the second user), input item information, and verifier approval authority information, and sends it to the second user terminal 30.

[0073] Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts an operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30. Furthermore, the confirmation screen presented to the second user may be configured to display the screen in the language specified to the verifier, based on the language information stored in the language data field of the second user's record in confirmation table 1015.

[0074] Figure 20 shows an example of a confirmation screen illustrating the operation of the contract confirmation process. The confirmation screen 70 for approving contract information, displayed on the display 3081 of the second user terminal 30, shows the status 710 indicating the current status of contract information creation, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an agreement button 740.

[0075] Specifically, if the approval authority information of the second user obtained in step S302 contains information indicating that the second user has the authority to approve the conclusion of the contract, the contract confirmation unit 1043 of the server 10 determines that the second user is a user who can approve the conclusion of the contract information received by the second user, presents a confirmation screen to the second user, and proceeds to step S304.

[0076] On the other hand, if the second user is a user who cannot approve the conclusion of the contract based on the received contract information, the contract verification process will be terminated.

[0077] In step S304, the contract confirmation unit 1043 of the server 10 receives input for one or more input fields of contract information. Specifically, the second user operates the input device 306 of the second user terminal 30 to input data to input items 732, 733, 734, and 735 set in the contract information. In this disclosure, input item 736 is not assigned to input by the second user, so it is visually indicated that the second user cannot input data for that item.

[0078] 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 based on the contract information received from the first user. The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30. If the second user agrees to or accepts the contents, they operate the input device 306 of the second user terminal 30 and press the consent button 740 displayed on the confirmation screen 70 for confirming the contract information. This causes the server 10 to execute a request that includes the document ID, information identifying the second user, and the input data for each input item entered in step S305. The information identifying the second user may also be the second user ID 3011. The contract verification unit 1043 of server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract verification unit 1043 of server 10 searches the verification table 1015 based on the received document ID and information identifying the second user, and stores the value of True in the verification flag field of the record. For example, if the information identifying the second user is an email address, it searches the document ID and verifier email address fields in the verification table 1015 and stores the value of True in the verification flag field of the record. If the information identifying the second user is user identification information, it searches the document ID and verifier email address fields in the verification table 1015 based on the email address of the second user identified by searching the user ID field in user table 1012, and stores the value of True in the verification flag field of the record. The contract confirmation unit 1043 of server 10 stores the received input data in the input data item of input item table 1016, which is identified by the input item ID associated with the input data. As a result, in step S305, the input data entered by the second user is stored as input item information in input item table 1016.

[0079] The contract verification unit 1043 of server 10 determines that the contract verification process has been performed by all verifiers with approval authority. Specifically, the contract verification unit 1043 of server 10 determines that the contract verification process has been performed by all verifiers with approval authority if the verification flag in the verification table 1015 of the verifiers with approval authority has a value of True. In other words, the value of the verification flag in the records of verifiers who do not have approval authority is ignored when making this determination. When the contract verification unit 1043 of server 10 has completed the contract verification process by all authorized verifiers, it sends a message to the first user notifying them that the contract verification process is complete. Similarly, the contract verification unit 1043 of server 10 may also send a message to the second user notifying them that the contract verification process is complete.

[0080] Specifically, the contract confirmation unit 1043 of server 10 sends a message to the first user's email address via email or other means of communication notifying them that the second user has completed the confirmation of the contract information. In other words, it notifies the first user that the second user has approved the conclusion of the contract. As a result, the first user can know that the conclusion of the contract with the second user has been completed. The message sent to the first user may include information about a URL that is an endpoint containing a document ID to identify the contract information.

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

[0082] Similarly, the contract confirmation unit 1043 of server 10 may use a chat service (not shown) or the like to send a message notifying the second user that they have completed the 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 endpoint containing a document ID to identify the contract information.

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

[0084] If multiple users are set as verifiers, the contract verification unit 1043 of server 10 may send a message to all verifiers except the user who last performed the contract verification process, notifying them that the contract verification process is complete. This allows all verifiers to receive notification that the contract verification process has been completed by all verifiers. Furthermore, the contract verification unit 1043 of the server 10 may send a message to a user with administrator-level privileges in a group to which multiple verifiers belong, notifying them that the contract verification process has been completed. Messages can also be sent via email, chat services, etc. This allows the administrator of the group to which the user responsible for verification belongs to receive notification that the contract verification process has been completed.

[0085] Specifically, the contract verification unit 1043 of server 10 retrieves the group ID item by searching the user ID or email address item in user table 1012 based on the user ID or email address. Based on the retrieved group ID item, the contract verification unit 1043 of server 10 retrieves the group ID item in group table 1013, retrieves the administrator ID item, identifies a user with administrator-level privileges by searching the user ID in user table 1012 based on the administrator ID, and sends a message notifying that the contract verification process is complete.

[0086] <Electronic signature processing> Step S305 may include an electronic signature process. In response to the instruction to approve the conclusion of the contract received from the second user in step S305, the contract confirmation unit 1043 of the server 10 stores the contract information received from the first user with an electronic signature indicating that the conclusion of the contract information has been approved. Specifically, the contract verification unit 1043 of server 10 attaches an electronic signature to the contract information and stores it based on the received request. Based on the document ID, the contract verification unit 1043 of server 10 searches the document ID field in the document table 1014 and retrieves the contract information. The contract verification unit 1043 of server 10 affixes an electronic signature to the acquired contract information and stores it in the document data item of the document table 1014. The contract verification unit 1043 of server 10 may update (overwrite) the document data item with the electronically signed contract information, or it may store the contract information before the electronic signature was added in a separate storage device (not shown). The contract verification unit 1043 of server 10 may include any of the following information in the electronic signature: document ID, email address of the first user, email address of the second user, approval date and time, confirmation date and time, authentication method for the approval date and time, authentication method for the confirmation date and time, input data values ​​for each input item, consent (approval) of the first user and the second user, and a timestamp. As a result, the contract verification unit 1043 of the server 10 stores the contract information with an electronic signature indicating that the second user has approved the conclusion of the contract. This prevents impersonation or tampering of the contract information by a third party.

[0087] <External storage processing> External storage processing is the process of acquiring and storing contract information created in an external electronic contract service within the electronic contract service relating to this disclosure.

[0088] <Overview of External Storage Processing> External storage processing is a series of processes that involves identifying a user, obtaining a list of contract information stored on an external server where the user is the verifier, excluding already concluded contract information from the obtained list, identifying an endpoint for obtaining contract information, obtaining the contract information from the external server, and storing the contract information.

[0089] <Details of external storage processing> The details of the external storage processing are described below.

[0090] In step S801, the external storage unit 1045 of the server 10 identifies the user who will perform the external storage processing. Specifically, the external storage unit 1045 of the server 10 refers to the access authority table 1017 and obtains access authority information including the user ID, service ID, and access token. For simplicity, this disclosure describes the external storage process targeting a predetermined user ID, service ID, and access token. The external storage unit 1045 of server 10 may perform external storage processing for each acquired user ID, service ID, and access token.

[0091] External storage processing may be configured to be performed automatically at predetermined intervals. External storage processing may also be configured to be performed in response to instructions from the user or administrator.

[0092] In step S802, the external storage unit 1045 of the server 10 performs a list acquisition step to obtain a list of one or more endpoints associated with each of the one or more pre-contract information records that can be accessed by the user. The list acquisition step is performed automatically at predetermined intervals. Specifically, the external storage unit 1045 of the server 10 identifies and retrieves an endpoint (list retrieval endpoint) for obtaining a list of contract information by referring to a table (not shown) or the like, based on the service ID obtained in step S801. The list retrieval endpoint is a string such as a URL that identifies a web page for the user to view and retrieve a list of contract information. Alternatively, the list retrieval endpoint may be obtained by accessing a predetermined API (Application Programming Interface) provided by an external contract conclusion service identified by the service ID. For example, the endpoint for retrieving a list of documents is a string such as a URL, like "https: / / contract.service / get_all_documents / ".

[0093] The external storage unit 1045 of server 10 accesses the list acquisition endpoint based on the access permission information acquired in step S801 and executes the step of acquiring a list of contract information. Specifically, the external storage unit 1045 of server 10 generates a request containing the access token included in the access permission information obtained in step S801 and sends it to the list acquisition endpoint. As a result, the external storage unit 1045 of server 10 sends the request to the external server 40. When the external server 40 receives a request, it identifies the user ID based on the access token. Based on the identified user ID, the external server 40 searches the creator ID field in the document table 4014 and retrieves the document ID. Similarly, based on the identified user ID, the external server 40 searches the user ID field in the user table 4012 of the external server 40 and retrieves the email address. Based on the retrieved email address, the external server 40 searches the confirmer email address field in the confirmation table 4015 of the external server 40 and retrieves the document ID and confirmation flag records. The external server 40 stores a value of False in the confirmation flag of the retrieved records and identifies and retrieves only records for which the contract information has not been confirmed by the user who is the verifier. In other words, the external server 40 identifies the document ID by excluding records for which the contract information has been confirmed by the user and which have a value of True in the confirmation flag of the retrieved records. Furthermore, the external server 40 may include in the document IDs used to identify contract information that has been reviewed by a user, but has not been reviewed by other reviewers, and has not been reviewed by any reviewer with full approval authority. The external server 40 generates, identifies, and retrieves an endpoint for each document ID based on the identified document IDs. The external server 40 sends the document IDs and the endpoint for each document ID to the server 10 as a response to the request. The external storage unit 1045 of server 10 receives and acquires a list of contract information (contract list information) from the external server 40 as a response to the request.

[0094] In step S803, the external storage unit 1045 of the server 10 performs an exclusion identification step to identify one or more endpoints to be excluded from the one or more endpoints acquired in the list acquisition step that correspond to contract information already stored in the contract storage step. Specifically, the external storage unit 1045 of the server 10 searches the endpoint entries in the document table 1014 based on one or more endpoints acquired in step S802, and determines whether the endpoint is already stored in the document table 1014. The external storage unit 1045 of the server 10 excludes the endpoints that are already stored in the endpoint entries of the document table 1014 from among the one or more endpoints acquired in step S802. This makes it possible to exclude contract information that is already stored in the document table 1014 from the acquisition target.

[0095] In step S804, the external storage unit 1045 of the server 10 performs a contract identification step to identify at least one predetermined endpoint that is included in the one or more endpoints acquired in the list acquisition step. Specifically, the external storage unit 1045 of the server 10 identifies contract information by excluding, in step S803, one or more endpoints acquired in step S802 that are already stored in the document table 1014.

[0096] In step S804, the reception step performs a step of receiving a request that includes a predetermined endpoint identified in the contract identification step. Specifically, the external storage unit 1045 of the server 10 accepts one or more identified endpoints.

[0097] In step S805, the external storage unit 1045 of the server 10 executes a contract acquisition step to acquire pre-contract information from an external contract signing service. The contract acquisition step includes the step of acquiring an endpoint from an external contract signing service to identify pre-contract information, and the step of acquiring the pre-contract information identified by the endpoint by accessing the endpoint. The contract acquisition step executes the step of acquiring the pre-contract information identified by the endpoint by accessing a predetermined endpoint. Specifically, the external storage unit 1045 of server 10 generates a request containing the access token included in the access permission information acquired in step S801, and sends it to the endpoint received in step S804. As a result, the external storage unit 1045 of server 10 sends the request to the external server 40. The external storage unit 1045 of server 10 receives and acquires one or more contract information from the external server 40 as a response to a request.

[0098] Furthermore, in step S805, the contract acquisition step may also perform the following steps: access the endpoint received in the acceptance step based on the access permission information obtained in the authorization acquisition step and acquire a page written in a markup language such as a web page; identify a link associated with the contract information contained in the page acquired in the page acquisition step; and access the identified endpoint and acquire the contract information. Specifically, the external server 40 may send HTML (Hypertext Markup Language) or XML, such as web pages, as a response to a request. In such cases, the external storage unit 1045 of the server 10 may use pattern matching such as regular expressions, arbitrary machine learning, or deep learning models to take the HTML or XML received from the external server 40 as input data, identify a link to download the contract information as output data, and receive and obtain the contract information by downloading it from that link. This allows the external storage unit 1045 of the server 10 to obtain the contract information from the endpoint.

[0099] The external server 40 may include status information, which includes information regarding the conclusion status of each contract, in the response it sends to the server 10. In this case, the external storage unit 1045 of the server 10 receives and acquires one or more contract information and status information for each of the multiple contract information from the external server 40 as a response to the request. Status information may include cases such as: one designated user in step S801 has not performed the contract verification process on the external server 40 (the user has not agreed, the contract has not been concluded); one designated user in step S801 has performed the contract verification process on the external server 40, but users related to other verifiers have not performed the contract verification process (the user has agreed, the contract has not been concluded); or the contract has been rejected by a user related to any of the verifiers (rejected, the contract has not been concluded). Furthermore, the external server 40 may include, in the response sent to the server 10, status information such as confirmation flags associated with the contract information in the confirmation table 4015 of the external server 40, for each piece of contract information.

[0100] In step S806, the external storage unit 1045 of the server 10 performs a contract storage step in which it stores pre-contract information obtained from an external contract signing service during the contract acquisition step. The contract storage step performs the step of storing the pre-contract information in association with an endpoint for identifying the contract information. Specifically, the external storage unit 1045 of the server 10 stores the one or more endpoints received in step S705 and the one or more document data included in the one or more contract information acquired in step S706 in the document table 1014, in the new record's document data and endpoint fields, respectively. The user ID identified in step S701 may also be stored in association with the contract information using a table or the like (not shown).

[0101] <External Verification Process> External verification is the process by which a verifier reviews, agrees to, and approves the content of electronic contract information received from the creator through an external electronic contract service. The external verification process is described below. While this disclosure illustrates the external verification process performed by a second user as an example, the first user can also perform the external verification process in the same way as the second user.

[0102] <Overview of External Verification Process> The external confirmation process is a series of operations that involves obtaining a list of contract information in which the user is stored as a verifier on an external server, excluding contract information that has already been concluded from the obtained list, identifying an endpoint for obtaining contract information, obtaining the contract information from the external server, storing the contract information, presenting the stored list of contract information to the user, accepting the user's selection of contract information obtained from the external server, presenting the user with a confirmation screen displaying the contract information, receiving data related to the contract information from the user, accepting instructions for consent and approval regarding the contract information, sending these instructions to the external server, and presenting the user with an approval notification received after consent and approval of the contract information on the external server.

[0103] In step S901, the external verification unit 1046 of the server 10 executes a list presentation step in which it presents to the user the pre-contract information acquired from an external contract signing service, which was stored in the contract storage step, in a manner that allows it to be distinguished from other contract information. The list presentation step presents to the user the pre-contract information acquired from an external contract signing service, which was stored in the contract storage step, in a manner that allows it to be distinguished from other contract information that was not acquired from an external contract signing service. Specifically, if the predetermined user in step S801 is the second user, the second user enters a predetermined URL in the browser application of the second user terminal 30 by operating the input device 306 of the second user terminal 30. The control unit 304 of the second user terminal 30 sends a request to the server 10 to display a list of contract information. Upon receiving the request, the server 10 retrieves one or more contract information associated with the second user from the document table 1014 and sends it to the second user terminal 30. Specifically, the contract information sent to the second user terminal 30 may include the document ID and status information obtained from the external server 40. The control unit 304 of the second user terminal 30 displays one or more received contract information on the display 3081 of the second user terminal 30, and presents the pre-contract information obtained from an external contract signing service to the second user.

[0104] Figure 20 is an example of a screen display 84 showing a list of contract information presented on the second user terminal 30. The list display screen 84 includes a table 841 that displays a list of contract information in list format. Table 841 displays contract information 851, 852, etc. in list format for each row. For each piece of contract information 851, Table 841 includes drawing objects such as an icon 8511 for selecting the contract information, a document ID 8512, status information 8513, an icon 8514 indicating the status information, and a source 8515.

[0105] If the contract information is obtained from the external server 40, the control unit 304 of the second user terminal 30 displays information indicating that it was obtained from the external server 40, the service ID associated with the external server 40, and other information such as the name of the contract signing service provided by the external server 40 on the display 3081 of the second user terminal 30. In other words, the display 3081 of the second user terminal 30 presents to the user the pre-contract information obtained from the external contract signing service in a way that makes it distinguishable from other contract information. The control unit 304 of the second user terminal 30 may present the contract information created by the contract creation process on the server 10 to the user in a manner that distinguishes it from other contract information. The control unit 304 of the second user terminal 30 may also present the contract information to the user in a manner that distinguishes it for each contract-concluding service that created the contract information. This allows the second user to easily verify whether the contract documents, prior to the contract signing, were created by the contract creation process on server 10 or by the contract creation process on another external server, such as server 40.

[0106] In step S901, the list presentation step performs the step of presenting to the user the pre-contract information obtained from an external contract conclusion service, which was stored in the contract storage step, in a formatted manner so that it can be identified from other contract information. Specifically, if the contract information is contract information obtained from the external server 40, the control unit 304 of the second user terminal 30 displays the document ID, status information, and other characters of the contract information in table 841 using bold, italics, and underlines on the display 3081 of the second user terminal 30. In addition, the control unit 304 of the second user terminal 30 includes drawing objects such as icons indicating the source of acquisition in the acquisition source 8515 and displays them on the display 3081 of the second user terminal 30.

[0107] In step S902, the second user selects contract information by operating the input device 306, etc., of the second user terminal 30. Specifically, the second user operates the input device 306, etc., of the second user terminal 30 to select a drawing object 8511, such as an icon, for selecting contract information, which is associated with the desired contract information, from among the contract information included in the table 841 displayed on the display 3081, etc., of the second user terminal 30. In this way, the second user selects the contract information to be subject to external verification processing. In this disclosure, the second user shall select contract information that "they have not agreed to and have not concluded" from the contract information obtained from the external server 40 during external storage processing. Furthermore, if a second user selects contract information created during the contract creation process on server 10, the system may be configured to execute steps S303 to S305 of the contract verification process related to that contract information.

[0108] In step S903, the external verification unit 1046 of the server 10 executes an approval step in which it receives instructions from the user to approve pre-contract information obtained from an external contract signing service. Specifically, in step S902, when the second user selects contract information obtained from the external server 40, the control unit 304 of the second user terminal 30 sends the document ID of the selected contract information to the server 10. The external verification unit 1046 of the server 10 searches the document ID item in the document table 1014 based on the received document ID and obtains the contract information. The external verification unit 1046 of server 10 generates a confirmation screen based on the acquired contract information and sends it to the second user terminal 30. Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts the operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30. The confirmation screen may be the same as the confirmation screen 70 in Figure 20 that is presented to the second user during the contract confirmation process.

[0109] In this disclosure, unlike the contract confirmation process, the contract information obtained from the external server 40 is configured not to acquire input item information, verifier's approval authority information, etc. However, in the external storage process, the input item information, verifier's approval authority information, etc. from the external server 40 may be obtained from the external server 40 and stored in the corresponding items of the input item table 1016 and confirmation table 1015, respectively. In this case, similar to the contract confirmation process on server 10, the second user can be configured to input data into the input items.

[0110] In addition, in step S903 of this disclosure, the second user may be configured to perform the same processing as steps S303 and S304 of the contract verification process on server 10. Since the processing in that case is the same as steps S303 and S304 of the contract verification process, the explanation is omitted.

[0111] In step S903, the external verification unit 1046 of the server 10 executes a transmission step in which it sends a request to an external contract signing service to approve the pre-contract signing contract information, in response to the instruction to approve the pre-contract signing contract information received in the approval step. Specifically, the second user checks the contract information displayed on the display 3081 of the second user terminal 30. If the second user agrees to or accepts the contents, they operate the input device 306 of the second user terminal 30 and press the consent button 740 displayed on the confirmation screen 70 for checking the contract information, thereby executing a process to send a request including the document ID and second user ID 3011 to the server 10.

[0112] In step S902, if the second user selects a contract information other than "I have not agreed to this, and the contract has not been concluded" from the contract information obtained from the external server 40 during the external storage processing, the display 3081 of the second user terminal 30 will present the second user with a confirmation screen 70, but the consent button 740 will be hidden or unavailable for selection. As a result, the second user will be able to confirm the contents of the contract information obtained from the external server 40 that they selected in step S902, but will not be able to consent or approve it. In this case, the external confirmation process will end, and the process will not proceed to step S904.

[0113] Furthermore, if the second user is a user who does not have the authority to consent to or approve the contract information, the display 3081 of the second user terminal 30 will present the second user with a confirmation screen 70, but the consent button 740 will be hidden or unavailable for selection. Specifically, the external verification unit 1046 of server 10 searches the user ID field in user table 1012 based on the second user ID 3011 and obtains approval authority. Based on the approval authority, the external verification unit 1046 of server 10 determines whether the second user is a user who has the authority to approve the contract information received in step S902. If the external verification unit 1046 of server 10 determines that the second user does not have the authority to approve the contract information received in step S902, it presents the confirmation screen 70 to the second user, but hides or disables the consent button 740. As a result, the second user can confirm the contents of the contract information obtained from the external server 40 selected in step S902, but cannot perform the consent or approval process. In this case, the external verification process ends, and the process does not proceed to step S904. In this way, the consent and approval of contract information by a second user can be restricted according to the approval authority in the user table 1012 of server 10. In other words, in this disclosure, the contract conclusions of a second user on the external server 40 can be stored and managed collectively in server 10 according to the approval authority stored therein. This prevents users without appropriate approval authority from concluding contracts in external contract conclusion services.

[0114] In step S903, the transmission step performs the step of sending a request to the endpoint to approve the contract information prior to contract conclusion. Specifically, the external verification unit 1046 of server 10 searches the document ID field in document table 1014 based on the document ID included in the received request and obtains the endpoint. Based on the service ID of the external electronic contract service identified based on the second user ID 3011, the endpoint, etc., the external verification unit 1046 of server 10 searches the user ID and service ID fields in access permission table 1017 and obtains the access token. The external verification unit 1046 of server 10 sends a request to the acquired endpoint to approve the contract information identified by the document ID, including the access token. As a result, the external verification unit 1046 of server 10 sends a request to the external server 40 to approve the contract information identified by the document ID.

[0115] The control unit 404 of the external server 40 identifies the second user ID 3011 based on the received access token. Based on the second user ID 3011, the control unit 404 of the external server 40 searches the user ID field in the user table 1012 and obtains the email address. Based on the received document ID and the identified second user's email address, the control unit 404 of the external server 40 searches the document ID and verifier email address fields in the confirmation table 1015 and stores the value True in the confirmation flag field of the record. As a result, the external server 40 stores information that the contract information selected by the second user in step S902 has been approved by the second user.

[0116] The external server 40 may send HTML or XML, such as a web page, as a response to a request. In such cases, the external verification unit 1046 of the server 10 may use pattern matching such as regular expressions, arbitrary machine learning, or deep learning models to take the HTML or XML received from the external server 40 as input data, obtain and identify operation objects such as buttons or links for approving the contract information as output data, and approve the contract information by virtually operating those operation objects. This allows the external verification unit 1046 of the server 10 to approve the contract information via the endpoint.

[0117] In step S904, the external verification unit 1046 of the server 10 executes a receiving step in which it receives a response indicating that the approval of the pre-contract information has been completed in response to the request to approve the pre-contract information that was sent in the transmission step. Specifically, the external verification unit 1046 of server 10 receives a response from the external server 40 to the request to approve the contract information in step S903. The response may be an HTTP response such as JSON sent from the endpoint, or it may be a web page of approval completion displayed by the external server 40 indicating that the approval of the contract information has been completed.

[0118] In step S904, the external verification unit 1046 of the server 10 executes an approval presentation step in which it informs the user that the approval of the contract information prior to contract conclusion has been completed, in accordance with the response received in the receiving step. Specifically, the external verification unit 1046 of the server 10 transmits information to the second user terminal 30 indicating that the approval of the contract information has been completed. The control unit 304 of the second user terminal 30 displays a screen on the display 3081 or the like of the second user terminal 30 indicating that the approval of the contract information selected in step S902 has been completed, and presents it to the second user.

[0119] In step S904, the external verification unit 1046 of the server 10 executes an approval storage step in which, in response to the response received in the receiving step, it associates information indicating that the pre-contract information has been approved with the pre-contract information obtained from the external contract signing service stored in the storage step, and stores it. Specifically, the external verification unit 1046 of the server 10 stores information in the document table 1014 that indicates that the contract information has been approved, associated with the record identified by the document ID of the contract information selected in step S902.

[0120] In step S904, the external verification unit 1046 of the server 10 executes an approval storage step in which, in response to the response received in the receiving step, it associates status information regarding the approval and conclusion status of the pre-contract information with the pre-contract information obtained from the external contract conclusion service stored in the storage step, and stores it. Specifically, in step S805 of the external storage processing, the external verification unit 1046 of the server 10 overwrites one or more contract information obtained from the external server 40 and the status information associated with each contract information with status information (approved) indicating that the contract information has been approved by the external verification process. Furthermore, if the response from the external server 40 to the request to approve the contract information in step S903 includes status information for the contract information, the external verification unit 1046 of the server 10 may overwrite the status information of the contract information with the status information included in the response. The status information may include "I have agreed, but the contract has not been concluded," "The contract has been concluded," etc. This allows the system to associate and store information regarding the approval of contract information on the external server 40 with the pre-contract signing contract information acquired from the external server 40 via external storage processing and stored in the document table 1014. Furthermore, when presenting the list of contract information in step S901, the drawing object 8514, such as an icon indicating the status information of the target contract information, is displayed according to the overwritten status information and presented to the second user. As a result, the display 3081 of the second user terminal 30 presents the contract information approved by the external verification process to the user in a way that allows it to be distinguished from other contract information.

[0121] <Basic Computer Hardware Configuration> Figure 21 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 comprises at least a processor 901, main memory 902, auxiliary memory 903, and a communication interface IF991. These are electrically connected to each other by a communication bus 921.

[0122] The processor 901 is hardware for executing the instruction set written in a program. The processor 901 consists of an arithmetic unit, registers, peripheral circuits, etc.

[0123] Main memory 902 is used to temporarily store programs and data processed by programs, etc. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0124] Auxiliary storage device 903 refers to a storage device for saving data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

[0125] The IF991 communication interface is an interface for inputting and outputting signals for communication with other computers via a network using wired or wireless communication standards. A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0126] Furthermore, by distributing all or part of each hardware configuration across multiple computers 90 and connecting them to each other via a network, a computer 90 can be virtually realized. Thus, the concept of computer 90 includes not only a computer 90 housed in a single enclosure or case, but also a virtualized computer system.

[0127] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 (Figure 21) will be explained. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.

[0128] Furthermore, the functional units of computer 90 can also be realized by distributing all or part of each functional unit across multiple computers 90 interconnected via a network. The concept of computer 90 includes not only a single computer 90 but also a virtualized computer system.

[0129] The control unit is realized when the processor 901 reads various programs stored in the auxiliary storage device 903, loads them into the main memory device 902, and executes processing according to those programs. The control unit can realize various functional units that perform information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0130] The memory unit is implemented by the main memory 902 and the auxiliary memory 903. The memory unit stores data, various programs, and various databases. The processor 901 can also reserve memory areas corresponding to the memory unit in the main memory 902 or the auxiliary memory 903 according to the program. The control unit can also cause the processor 901 to perform operations such as adding, updating, and deleting data stored in the memory unit according to the various programs.

[0131] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters. Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.

[0132] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.

[0133] The communication unit is implemented by the communication IF991. The communication unit provides the functionality to communicate with other computers 90 via the 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 perform information processing on the received information according to various programs. The communication unit can also transmit information output from the control unit to other computers 90.

[0134] <Note> The details described in each of the above embodiments are noted below.

[0135] (Note 1) A contract signing program comprising a processor and a memory unit, for causing a computer to execute electronic contract procedures between users, wherein the contract signing program causes the processor to execute a contract acquisition step (S805) for acquiring pre-contract information from an external contract signing service, a contract storage step (S806) for storing the pre-contract information acquired from the external contract signing service in the contract acquisition step, and a list presentation step (S901) for presenting the pre-contract information acquired from the external contract signing service and stored in the contract storage step to the user in a manner that can be distinguished from other contract information. This allows users to avoid mistakenly entering into contracts based on pre-contract information obtained from external contract execution services.

[0136] (Note 2) The contract signing program is the contract signing program described in Appendix 1, which causes the processor to execute an approval step (S903) in which it receives an instruction from the user to approve pre-contract information obtained from an external contract signing service, and a transmission step (S903) in which it sends a request to the external contract signing service to approve the pre-contract information in response to the instruction to approve the pre-contract information received in the approval step. This allows users to approve pre-contract information on external contract execution services without having to access those services themselves.

[0137] (Note 3) The contract signing program is the contract signing program described in Appendix 2, which causes the processor to execute a receiving step (S904) in which it receives a response indicating that the approval of the pre-contract information has been completed in response to a request to approve the pre-contract information sent in the transmission step, and an approval presentation step (S904) in which it presents to the user that the approval of the pre-contract information has been completed in accordance with the response received in the receiving step. This allows users to confirm, based on the information provided, that a contract has been concluded in an external contract signing service, without having to access the external contract signing service itself.

[0138] (Note 4) A contract conclusion program as described in Appendix 3, which, in response to a response received in the receiving step, causes the program to execute an approval storage step (S904) which stores information indicating that the pre-contract information has been approved in association with the pre-contract information obtained from an external contract conclusion service stored in the storage step. This allows users to see at a glance the contract information of completed contracts in external contract signing services.

[0139] (Note 5) The contract conclusion program described in Appendix 4 includes a step of presenting a list (S904) which includes presenting to the user, in a manner that distinguishes the contract information stored in association with information indicating that it was approved in the approval storage step from other contract information. This allows users to see at a glance the contract information of completed contracts in external contract signing services.

[0140] (Note 6) A contract conclusion program as described in Appendix 3, which, in response to a response received in the receiving step, causes the program to execute an approval storage step (S904) which stores, in association with the pre-contract information obtained from an external contract conclusion service stored in the storage step, status information regarding the approval and conclusion status of the pre-contract information. This allows users to see at a glance the contract information of completed contracts in external contract signing services.

[0141] (Note 7) The contract conclusion program described in Appendix 6 includes a step of presenting a list (S904) which presents to the user contract information stored in association with status information in a manner that allows it to be distinguished from other contract information according to the status information. This allows users to see at a glance the contract information of completed contracts in external contract signing services.

[0142] (Note 8) The contract acquisition step (S805) is a contract signing program as described in Appendix 2, which includes the step of obtaining an endpoint from an external contract signing service to identify pre-contract signing contract information, and the step of obtaining the pre-contract signing contract information identified by the endpoint by accessing the endpoint. This allows users to accurately obtain pre-contract information from external contract execution services.

[0143] (Note 9) The contract signing program as described in Appendix 8, wherein the contract storage step (S806) is a step of storing contract information prior to contract signing in association with an endpoint for identifying the contract information, and the transmission step (S903) is a step of sending a request to the endpoint to approve the contract information prior to contract signing. This allows contract information to be stored in association with endpoints. For example, it prevents duplicate registration of contract information associated with the same endpoint.

[0144] (Note 10) The contract signing program, as described in Appendix 1, causes the processor to perform a list acquisition step (S802) to acquire a list of one or more endpoints associated with each of the one or more pre-contract information items that can be referenced by the user, and a contract identification step (S804) to identify at least one predetermined endpoint included in the one or more endpoints acquired in the list acquisition step, and the contract acquisition step (S805) is a step of acquiring pre-contract information identified by the endpoint by accessing the predetermined endpoint. This allows users to retrieve, store, and manage pre-contract information stored in external contract execution services without performing any special operations.

[0145] (Note 11) The contract conclusion program described in Appendix 1 includes a list presentation step (S901) which presents to the user, in a manner that distinguishes pre-contract information obtained from an external contract conclusion service, which was stored in the contract storage step, from other contract information not obtained from the external contract conclusion service. This allows users to avoid mistakenly entering into contracts based on pre-contract information obtained from external contract execution services.

[0146] (Note 12) The contract conclusion program described in Appendix 1 is a step in which the list presentation step (S901) presents to the user the pre-contract information obtained from an external contract conclusion service, which was stored in the contract storage step, in a decorated manner, so that it can be distinguished from other contract information. This allows users to avoid mistakenly entering into contracts based on pre-contract information obtained from external contract execution services.

[0147] (Note 13) An information processing device comprising a processor and a memory unit, wherein the processor is configured to execute a contract conclusion program described in any of the appendices 1 to 12. This allows users to avoid mistakenly entering into contracts based on pre-contract information obtained from external contract execution services.

[0148] (Note 14) An information processing system including an information processing device comprising a processor and a memory unit, wherein the system causes the processor to execute a contract conclusion program described in any of the appendices 1 to 12. This allows users to avoid mistakenly entering into contracts based on pre-contract information obtained from external contract execution services.

[0149] (Note 15) An information processing method performed by a computer comprising a processor and a memory unit, wherein the processor is made to execute a contract conclusion program described in any of the appendices 1 to 12. This allows users to avoid mistakenly entering into contracts based on pre-contract information obtained from external contract execution services. [Explanation of Symbols]

[0150] 1 Information processing 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 contract-concluding program comprising a processor and a memory unit, which causes a computer to execute electronic contract procedures between users, The contract signing program provides the processor with The contract acquisition step involves obtaining pre-contract information from an external contract signing service, and In the contract acquisition step, there is a contract storage step that stores the pre-contract information obtained from the external contract signing service, A list presentation step in which the contract information obtained from the external contract conclusion service, which was stored in the contract storage step, is presented to the user in a manner that allows it to be distinguished from other contract information, A contract signing program that enables the execution of a contract.

2. The contract signing program provides the processor with An approval step in which the user gives instructions to approve the pre-contract information obtained from the external contract signing service, A transmission step in which, in response to an instruction to approve the pre-contract information received in the approval step, a request is sent to the external contract signing service to approve the pre-contract information. To execute The contract conclusion program according to claim 1.

3. The contract signing program provides the processor with A receiving step in which a response indicating that the approval of the pre-contract information has been completed has been received in response to the request to approve the pre-contract information sent in the transmission step, In response to the response received in the receiving step, an approval notification step is performed to inform the user that the approval of the contract information prior to the conclusion of the contract has been completed. To execute The contract conclusion program according to claim 2.

4. In response to the response received in the receiving step, an approval storage step is performed to associate and store information indicating that the pre-contract information has been approved with the pre-contract information obtained from the external contract conclusion service stored in the storage step, To execute The contract conclusion program described in claim 3.

5. The aforementioned list presentation step includes presenting to the user the contract information stored in association with information indicating that it was approved by the approval storage step, in a manner that allows it to be distinguished from other contract information. The contract conclusion program described in claim 4.

6. In response to the response received in the receiving step, an approval storage step stores the pre-contract information obtained from the external contract conclusion service stored in the storage step, associating it with status information regarding the approval and conclusion status of the pre-contract information. To execute The contract conclusion program described in claim 3.

7. The aforementioned list presentation step includes presenting the contract information stored in association with the status information to the user in a manner that allows it to be distinguished from other contract information according to the status information. The contract conclusion program according to claim 6.

8. The aforementioned contract acquisition step is, The steps include obtaining an endpoint from the aforementioned external contract signing service to identify the contract information prior to the signing of the contract, The steps include: accessing the endpoint to obtain the pre-contractual contract information identified by the endpoint; The contract conclusion program according to claim 2.

9. The contract storage step is a step of storing contract information prior to the conclusion of the contract, in association with an endpoint for identifying the contract information, The transmission step is a step of sending a request to the endpoint to approve the contract information prior to the conclusion of the contract. The contract conclusion program according to claim 8.

10. The contract signing program provides the processor with A list acquisition step that obtains a list of one or more endpoints associated with each of the one or more pre-contract information items that can be referenced by the user, A contract identification step that identifies at least one predetermined endpoint included in the one or more endpoints obtained in the list acquisition step, Make it run, The contract acquisition step is a step of acquiring pre-contract information identified by the endpoint by accessing the predetermined endpoint. The contract conclusion program according to claim 1.

11. The aforementioned list presentation step presents to the user the pre-contract information obtained from the external contract conclusion service, which was stored in the contract storage step, in a manner that allows it to be distinguished from other contract information not obtained from the external contract conclusion service. The contract conclusion program according to claim 1.

12. The aforementioned list presentation step is a step of presenting to the user the pre-contract information obtained from the external contract conclusion service, which was stored in the contract storage step, in a decorated manner, so that it can be identified from the other contract information. The contract conclusion program according to claim 1.

13. An information processing device comprising a processor and a memory unit, The processor is made to execute the contract signing program described in any one of claims 1 to 12. Information processing device.

14. An information processing system including an information processing device comprising a processor and a memory unit, The processor is made to execute the contract signing program described in any one of claims 1 to 12. Information processing system.

15. An information processing method performed by a computer comprising a processor and a memory unit, The processor is made to execute the contract signing program described in any one of claims 1 to 12. Information processing methods.

Images