Program, method, information processing apparatus, and system

Abstract

To provide a program, a method, an information processing apparatus, and a system configured to omit the confirmation from an opposite party as to whether an electronic contract using an electronic contract service can be concluded.SOLUTION: In a computer equipped with a processor and a storage unit, a program that provides a service related to a contract document which is to be concluded between parties concerned causes the processor to execute: an opposite-party receiving step of receiving, from a first user, information specifying an opposite party that is to agree with the content of a contract; a determination step of determining a status of use of a service for executing an electronic contract procedure, on the basis of the information specifying the opposite party received in the opposite-party receiving step; and a determination presentation step of presenting, to the first user, a result determined in the determination step.SELECTED DRAWING: Figure 20

Description

[Technical field]

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

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

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

[0004] When entering into a contract or other agreement with a trading partner, there is a need to confirm whether it is possible to enter into a contract with that partner using an electronic contract service. Therefore, the present disclosure provides a technology that eliminates the need to confirm with the other party whether or not an electronic contract can be concluded using an electronic contract service. [Means for solving the problem]

[0005] A program having a processor and a memory unit, which provides a computer with a service related to a contract document to be agreed upon between the parties, wherein the processor executes a counterparty receiving step in which it receives information identifying the counterparty with which the contract contents are agreed from a first user, a determination step in which it determines the usage status of a service for executing electronic contract procedures based on the information identifying the counterparty received in the counterparty receiving step, and a determination presentation step in which it presents the determination result determined in the determination step to the first user. Effect of the Invention

[0006] According to the present disclosure, it is possible to omit confirmation from the other party as to whether or not an electronic contract can be concluded using an electronic contract service. [Brief description of the drawings]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0030] The contract processing unit 1051 executes inquiry processing, paper contract conclusion processing, and intermediation conclusion processing, which will be described in detail later.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0046] <Inquiry processing> The inquiry process is a process of inquiring and determining whether the other party of a transaction is a user of the information processing service according to the present disclosure, and executing various services related to electronic contracts according to the result of the determination. In the present disclosure, the execution of the inquiry process by the first user will be described as an example. Note that the inquiry process can be executed by any user other than the first user.

[0047] <Inquiry process overview> The inquiry process is a series of processes that, upon receiving input of information about the other party to a transaction from the creator, inquires as to whether the other party is a user of the information processing disclosed herein, presents the creator with the determination result as to whether or not the other party is a user, and provides various services related to electronic contracts, such as contract creation processing, invitations to the electronic contract service disclosed herein, paper contract conclusion processing, and intermediary conclusion processing, depending on the determination result.

[0048] <Details of inquiry process> The inquiry process will be described in detail below.

[0049] In step S701, the contract processing unit 1051 of the server 10 executes a counterparty receiving step of receiving, from the first user, information identifying a counterparty with which the contract contents are agreed upon. Specifically, the first user operates the input device 206 of the first user terminal 20 to execute a browser application or the like, and opens the query page D1 by inputting the URL of a web page (query page) for executing a query process, etc. The control unit 204 of the first user terminal 20 transmits a request including the first user ID 2011 for opening the query page to the server 10.

[0050] When the server 10 receives the request, it generates a query page and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the query page on the display 2081 of the first user terminal 20 for presentation. 20 is an example of a query screen in query processing. Query page D1 is displayed on the display 2081 of the first user terminal 20. Query page D1 includes an input field D11, a send button D12, a determination result D13, and a contract selection field D14. The contract selection field D14 includes an invitation button D141, a paper contract button D142, and an intermediation button D143.

[0051] The first user operates the input device 206 of the first user terminal 20 to input an email address (second email address) which is information identifying the other party (second user) with whom a contract is to be concluded, into the input field D11. The first user presses the send button D12 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits the second email address entered in the input field D11 to the server 10. The contract processing unit 1051 of the server 10 receives and accepts the second email address, which is information identifying the other party with whom a contract is to be concluded.

[0052] In step S702, the contract processing unit 1051 of the server 10 executes a determination step of determining the usage status of a service for executing an electronic contract procedure, based on the information identifying the other party accepted in the other party acceptance step. Specifically, the contract processing unit 1051 of the server 10 searches the email address field in the user table 1012 based on the received second email address, and determines whether or not the second email address is stored in the user table 1012. If the second user has registered as a user with the electronic contract service according to the present disclosure, the user table 1012 includes a record that stores the second email address. If the second user has not registered as a user with the electronic contract service according to the present disclosure, the user table 1012 does not include a record that stores the second email address. If the second email address is stored in the user table 1012, the contract processing unit 1051 of the server 10 determines that the second user is using the electronic contract service disclosed herein; if not, it determines that the second user is not using the electronic contract service disclosed herein.

[0053] In step S703, the contract processing unit 1051 of the server 10 executes a determination presentation step of presenting the determination result determined in the determination step to the first user. Specifically, the contract processing unit 1051 of the server 10 transmits the determination result determined in step S702 to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received determination result D13 on the display 2081 of the first user terminal 20 for presentation. The presentation of the determination result may be performed when the other party determines in the determination step that the service for executing the electronic contract procedure is available, or may be performed when the other party does not determine in the determination step that the service for executing the electronic contract procedure is available. The presentation of the determination result may be performed in either case, or in only one of the cases.

[0054] If the contract processing unit 1051 of the server 10 does not determine in the judgment step that a service for the other party to execute electronic contract procedures is available, it executes a selection and presentation step of notifying the first user of a message inviting the other party to a service for executing electronic contract procedures, and presenting at least one of the following procedures as a selectable option: concluding a contract with the other party through a paper contract, and concluding an electronic contract through another service used by the other party. Specifically, when the control unit 204 of the first user terminal 20 determines in step S702 that the second user is not using the electronic contract service according to the present disclosure, it displays and presents the invitation button D141, the paper contract button D142, and the intermediation button D143 in the contract selection field D14. The first user may be able to select any one of the invitation button D141, the paper contract button D142, and the intermediation button D143, or any combination of one or more of them. When the first user operates the input device 206 of the first user terminal 20 to press the Invite button D141, the process proceeds to step S706. When the first user operates the input device 206 of the first user terminal 20 to press the paper contract button D142, the process proceeds to step S501 of the paper contract conclusion process. When the first user operates the input device 206 of the first user terminal 20 to press the intermediation button D143, the process proceeds to step S601 of the intermediation conclusion process.

[0055] In step S704, if the contract processing unit 1051 of the server 10 determines in the judgment step that a service for the other party to execute electronic contract procedures is available, it executes a template presentation step of presenting one or more templates including agreements regarding the electronic contract to the first user. Specifically, when the contract processing unit 1051 of the server 10 determines in step S702 that the second user is using the electronic contract service according to the present disclosure, it refers to a template table (not shown) or the like to obtain template data relating to a contract document template based on an electronic contract. In addition, a contract document template based on electronic contracts refers to a contract document template that includes wording such as "electronic processing" and "electromagnetic record" and contains provisions regarding electronic contracts (articles, clauses, etc.). For example, it includes a template of a contract document that includes the following clauses, provisions, etc. Article ●● (Contract Formation) It is established when the seller delivers to the buyer the individual contract (regardless of the form, such as an order confirmation or receipt) that has been signed and sealed or has been subjected to an electronic processing equivalent thereto. ... Article ●● (Consultation) In addition, when consultations are held, if requested by the other party, an agreement to hold consultations will be made in writing or by means of an electromagnetic record. ... Final Sentence As evidence of the formation of this Agreement, an electromagnetic record of this document will be created, and after both parties have agreed, they will affix their electronic signatures and each party will keep a copy of the electromagnetic record.

[0056] The contract processing unit 1051 of the server 10 transmits the acquired one or more templates to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received one or more templates in a list on the display 2081 of the first user terminal 20.

[0057] The first user operates the input device 206 of the first user terminal 20 to select a predetermined template from the templates displayed in a list. Note that the first user does not necessarily have to select a template. The first user may create a contract document using word processing software or the like installed in the first information processing terminal without using a template.

[0058] In step S705, the first user executes the contract creation process. If the first user selected a template in step S704, the first user creates a contract document according to the contents of the planned contract by editing the template, such as by adding or modifying it. Note that the first user may send the created contract document to the second user by email or the like before proceeding to the contract creation process, so that the second user can check the contents in advance. The first user operates the input device 206 of the first user terminal 20 to press the send button, thereby transmitting the contract document created based on the selected template to the server 10. The contract creation unit 1042 of the server 10 receives and accepts the contract document. Details of the contract creation process will be described later. In addition, when executing the contract creation process, it is not necessarily required to execute the template presentation process in step S704, and the contract creation process may be executed based on a contract document created by the first user himself / herself.

[0059] In step S706, if the contract processing unit 1051 of the server 10 does not determine in the determination step that the other party can use the service for executing the electronic contract procedure, it executes an invitation step of notifying the other party of a message for inviting the other party to the service for executing the electronic contract procedure. The invitation step executes a step of notifying a message including information that helps the other party execute the electronic contract procedure or information indicating the contact information for the support desk of the service for executing the electronic contract procedure. Specifically, the first user presses the invite button D141 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits a request to the server 10 to invite the second user to the electronic contract service according to the present disclosure. The contract processing unit 1051 of the server 10 transmits a message to the second email address to invite the other party (second user) with whom a contract is planned to be concluded to the electronic contract service according to the present disclosure. The message includes URL (Uniform Resource Locator) information for registering an account with the electronic contract service according to the present disclosure. The URL may include information for identifying the second user. The message may include information to assist the second user in carrying out electronic contract procedures, such as information indicating the procedures for the second user to start using the electronic contract service, and information indicating the procedures for concluding an electronic contract using the electronic contract service. The message may include information such as a URL or telephone number indicating the contact point for inquiries or support for the electronic contract service according to the present disclosure. By inquiring at the URL or telephone number, a user can receive information on the procedure for starting to use the electronic contract service, the procedure for concluding an electronic contract using the electronic contract service, etc. This makes it possible to motivate the other party to use electronic contract services even if the other party is not familiar with such services.

[0060] In step S707, the contract processing unit 1051 of the server 10 executes a new registration step of accepting account registration for a service for executing electronic contract procedures from the other party in response to the message notified in the invitation step. Specifically, the second user can select the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, thereby opening the web page specified by the URL using the browser application of the second user terminal 30. As a result, the second user terminal 30 transmits to the server 10 a request for a page for registering an account with the electronic contract service according to the present disclosure (account registration page). The contract processing unit 1051 of the server 10 generates an account registration page and transmits it to the second user terminal 30. The account registration page includes input fields for inputting the email address of the second user, etc. The account registration page may also include input fields for a user ID, a user name, a group ID, approval authority, etc. The second user operates the input device 306 of the second user terminal 30 to input and send user information including the second email address, second user ID, second user name, group ID, and approval authority in the input fields. The contract processing unit 1051 of the server 10 stores the received second email address, second user ID, and second user name in the email address, user ID, user name, group ID, and approval authority items in the user table 1012, respectively. As a result, the second user is registered as a user of the electronic contract service according to the present disclosure. It is preferable that the group ID, approval authority, etc. are set not by the second user but by the administrator of the group to which the second user belongs (specified by the administrator ID in the group table 1013).

[0061] In step S708, the contract processing unit 1051 of the server 10 executes a registration notification step of notifying the first user of a message in response to the acceptance of the account registration from the other party in the new registration step. Specifically, the contract processing unit 1051 of the server 10 sends a message to the email address (first email address) of the first user notifying that the second user has registered an account. The message includes URL information for the first user to start the contract creation process. The URL may include information for identifying the first user and the second user. The first user can start the contract creation process, which will be described later, by operating the input device 206 of the first user terminal 20 to select the URL described in the message.

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

[0063] <Contract Creation Process> The contract creation process is a process in which the creator creates electronic contract information and transmits it to the confirmer. The contract creation process can be executed following steps S705 and S708 of the inquiry process already explained. Note that the contract creation process can also be executed independently without the inquiry process.

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

[0065] <Outline of contract creation process> The contract creation process is a series of processes in which the creator creates electronic contract information, sets the verifying party to whom the electronic contract information will be sent, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, and sends the electronic contract information to the set verifying party.

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

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

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

[0069] A case will be described where the contract creation process is executed following step S705 of the inquiry process. In step S101, the contract preparation unit 1042 of the server 10 executes a contract reception step of receiving, from the first user, a contract document prepared based on the template presented in the template presentation step. Specifically, when the first user creates a contract document from the listed template in steps S704 and S705 of the inquiry process, the server 10 receives and accepts the contract document created based on the template from the first user terminal 20.

[0070] A case will be described where the contract creation process is executed following step S708 of the inquiry process. In step S101, the contract preparation unit 1042 of the server 10 executes a contract acceptance step of accepting a contract document in response to the message notified in the registration notification step. Specifically, when the second user registers an account in step S707 of the inquiry process, the first user receives the message sent in step S708. The first user may select a URL or the like described in the received message, whereby a screen for creating contract information is displayed on the display 2081 of the first user terminal 20. The first user can execute the contract creation process.

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

[0072] A case will be described where the contract creation process is executed following steps S705 and S708 of the inquiry process. In step S102, the contract preparation unit 1042 of the server 10 executes a verifyer addition step of adding information (counterparty) that identifies the other party to the verifyers of the contract document accepted in the contract acceptance step. Specifically, the contract preparation unit 1042 of the server 10 automatically includes the email address (second email address), which is information identifying the other party (second user) with whom the contract is to be concluded, received in step S701, in the confirmer. This allows the other party who agrees to the contract contents to be automatically included as a reviewer (approver) when creating a new contract document. The first user can include the other party in the contract document circulation and approval flow without specifying the other party.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0089] In step S302, the contract confirmation unit 1043 of the server 10 identifies the second user. The second user may be identified based on the second user ID 3011 included in the request received from the second user terminal 30, or may be identified based on identification information for identifying the second user included in the URL. If the second user is not registered as a user in the service according to the present disclosure, it is necessary to identify the second user from the URL. For example, the URL may include the email address, user ID, etc. of the second user as information for identifying the second user.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0103] <Paper contract signing process> The paper contract conclusion process is a process in which the creator concludes a contract via a paper contract with a confirmer who is not using an electronic contract service.

[0104] <Outline of paper contract signing process> The paper contract conclusion process is a series of processes in which the creator creates electronic contract information, sets a verifying party to whom the electronic contract information will be sent, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, mails a paper contract printed based on the electronic contract information to the set verifying party, the verifying party fills in the input fields and stamps the received paper contract, returns it to the electronic contract service disclosed herein, and digitizes the returned paper contract using a scanner or the like and stores it.

[0105] <Details of paper contract signing process> The paper contract signing process will be described in detail below.

[0106] In step S501, if the contract processing unit 1051 of the server 10 does not determine in the judgment step that the other party has access to a service for executing electronic contract procedures, it executes a contract acceptance step of accepting a contract document from the first user. Specifically, the first user presses the paper contract button D142 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits to the server 10 a request to execute the paper contract conclusion process. When the contract processing unit 1051 of the server 10 receives the request, it generates a paper contract conclusion page and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the paper contract conclusion page on the display 2081 of the first user terminal 20 for presentation. 21 is an example of a paper contract conclusion screen in the paper contract conclusion process. A paper contract conclusion page D2 is displayed on the display 2081 of the first user terminal 20. The paper contract conclusion page D2 includes buttons D221, D222, and D223 for specifying input items, a contract information display area D230, document data D231, input items D232, D233, and D234, and a send button D240.

[0107] The first user operates the input device 206 of the first user terminal 20 to create contract information including document data related to the contract. The document data may be in any data format such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language) and may be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and transmits the created document data and the first user ID 2011 to the server 10. The contract processing unit 1051 of the server 10 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores new contract information in the document table 1014. Note that the contract information may include information indicating that the contract information is subject to paper contract conclusion processing. This makes it possible to distinguish whether the contract information stored in the document table 1014 is contract information related to contract creation processing or paper contract conclusion processing. The creation of the contract information may include a process similar to step S101 of the contract creation process.

[0108] In step S502, the first user operates the input device 206 of the first user terminal 20 to input information (destination information) for identifying the second user, such as the second user's name, group (name of company, name of organization, etc.), address, telephone number, email address, etc. In the paper contract conclusion process, the second user's address and other information must be input in order to mail the printed paper contract. The contract processing unit 1051 of the server 10 stores the input destination information of the second user in the confirmation table 1015 of the server 10. Note that multiple pieces of destination information can be stored for one piece of contract information. The setting of the checker may include the same process as step S102 of the contract creation process.

[0109] In step S503, the first user can operate the input device 206 of the first user terminal 20 or the like to set input items for the contract information. The details are the same as those in step S103 of the contract creation process, so a detailed explanation will be omitted.

[0110] In step S504, the first user sets input rules for each input item to be added. The details are the same as those in step S104 of the contract creation process, so a detailed explanation will be omitted.

[0111] In step S505, the contract preparation unit 1042 of the server 10 accepts input data for a plurality of input items input by the first user. The details are similar to step S105 of the contract creation process, so a detailed explanation will be omitted.

[0112] In step S506, the contract processing unit 1051 of the server 10 receives an instruction from the first user to request the second user to conclude a contract for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 to press the send button D240 displayed on the paper contract conclusion page D2, thereby sending a request to send the contract information to the server 10. The contract processing unit 1051 of the server 10 receives and accepts the request.

[0113] In step S507, the contract processing unit 1051 of the server 10 executes a paper contract sending step, which executes processing to send the paper contract, which is the contract document accepted in the contract acceptance step, to the other party without the first user having to perform the sending operation. Specifically, the contract processing unit 1051 of the server 10 searches the document ID item in the document table 1014 based on the document ID included in the received request, and acquires the contract information. The contract processing unit 1051 of the server 10 may search the document ID item in the input item table 1016 based on the document ID, and acquire the input item information. The contract processing unit 1051 of the server 10 also searches the document ID item in the confirmation table 1015 based on the document ID, and acquires the destination information of the second user. The contract processing unit 1051 of the server 10 creates a contract document for printing based on the document data included in the contract information, the input data included in the input item information, etc. Specifically, when input item information is not set in the document data, the document data becomes the contract document for printing as is. On the other hand, if input item information is set in the document data, a contract document for printing is created with the input item information arranged in the document data. The contract document for printing is provided with fields for the user related to the confirmer who received the contract document to fill in by hand, fields for stamping, etc. If input rules are set, annotation information indicating the input rules (for example, for the date of birth, enter the Gregorian calendar instead of the Japanese calendar) may be provided near the fields. The contract processing unit 1051 of the server 10 sends a request including the contract document to be printed and the destination information of the second user to an information processing service regarding printing and mailing of paper documents (not shown in the figure) (for example, there is a service called Web Mail provided by Japan Post). The information processing service provider that has received the request outputs the contract document for printing on paper using a printer, printing machine, etc. The contract document output on paper is then mailed to the name, group, address, etc. included in the destination information of the second user. Note that the information processing service provider according to the present disclosure may output the contract document on paper using a printer, printing machine, or the like, and have the operator mail the output paper contract to the address of the second user. Specifically, the contract processing unit 1051 of the server 10 outputs the contract document on paper by sending the contract document for printing to a printer, printing machine, or the like (not shown). Furthermore, the contract processing unit 1051 of the server 10 transmits the destination information of the second user to an information processing terminal of an operator in the organization that operates the electronic contract service according to the present disclosure. Based on the destination information, the operator mails the paper contract to the name, group, and address specified in the destination information. For example, the operator writes or prints the second user's name, group, address, etc. on an envelope, encloses the paper contract in the envelope, and drops it in a postbox.

[0114] If multiple pieces of destination information are stored in the confirmation table 1015, steps S507 to S508 may be executed for each checker in the order of confirmation. In other words, each time a checker completes stamping and returning (step S508), a process of printing and mailing (step S507) to the next checker in the order may be executed. Furthermore, if the confirmation order is not set, printing and mailing (step S507) may be performed simultaneously for each confirmer. In this case, the electronic storage process (step S509) is performed according to the seal and return from the second user (step S508), so the time until the paper contract conclusion process is completed can be shortened.

[0115] In step S508, the second user receives the paper contract by mail. The second user checks the contents of the paper contract. If the paper contract has fields for writing, stamping, etc., the second user writes the necessary information in the fields and affixes his / her signature and seal to the fields for stamping, etc. After the second user checks the contents of the paper contract, the second user returns the paper contract to the address of the information processing service according to the present disclosure. It is preferable to enclose a return envelope when mailing the paper contract to the second user in step S507.

[0116] In step S509, the contract processing unit 1051 of the server 10 executes a process for accepting the return of the paper contract sent to the other party in the paper contract sending step without requiring the first user to perform the receiving operation, and executes a contract digitization step for digitizing the returned paper contract. The contract processing unit 1051 of the server 10 executes a contract storage step for adding an electronic signature to the paper contract digitized in the contract digitization step and storing it. Specifically, when an operator at an organization that operates the electronic contract service according to the present disclosure receives the paper contract returned from the second user, the operator reads the paper contract using a scanner or the like and creates a file that digitizes the paper contract. Specifically, the digitized file is in a data format such as PDF. The operator also identifies the document ID based on the contents of the returned paper contract. Note that identification information (such as a number) for identifying the document ID is written on the paper contract, and the document ID may be identified based on that identification information. The operator stores the digitized file in the document table 1014 of the server 10 in the field of digitized data of the record specified based on the document ID. The contract processing unit 1051 of the server 10 may add a digital signature to the digitized file and store it in the item of digitized data in the document table 1014 . The contract processing unit 1051 of the server 10 may include any of the following information in the electronic signature: the document ID, the email address of the first user, the destination information of the second user, the receipt date and time, the value of the input data for each input item, a timestamp, and the like. The contract processing unit 1051 of the server 10 adds a digital signature indicating that the second user has approved the conclusion of the contract in the contract information to the contract information, and stores the digital signature. This makes it possible to prevent a third party from impersonating or tampering with the contract information.

[0117] In step S509, the contract processing unit 1051 of the server 10 executes a completion notification step of notifying the first user and the other party of a message indicating that the paper contract has been stored in the contract storage step. Specifically, the contract processing unit 1051 of the server 10 generates a URL for a web page for at least one of the first user and the second user to refer to the digitized data. The URL includes information for identifying the contract information. The URL may directly include the document ID, or may include information such as a character string obtained by arbitrarily encrypting the document ID, or other character strings that can identify the document ID by referring to a table (not shown). The URL may also include information for identifying the first user and the second user. The contract processing unit 1051 of the server 10 transmits a message including the URL of a web page for referencing the digitized data to at least one of the email address of the first user and the email address of the second user. The first user operates the input device 206 of the first user terminal 20 to open the URL in a web browser or the like, thereby transmitting a request to the server 10 to refer to the digitized data. The contract processing unit 1051 of the server 10 searches for the document ID item in the document table 1014 based on the document ID included in the request, and acquires the digitized data item. The control unit 204 of the first user terminal 20 displays and presents the received digitized data on the display 2081 of the first user terminal 20. The second user can also receive the digitized data by operating the input device 306 of the second user terminal 30 in a similar manner.

[0118] In step S509, the contract processing unit 1051 of the server 10 executes a new registration step of registering the other party as an account in a service for executing electronic contract procedures. The completion notification step executes a step of notifying the other party of a message including information indicating that the other party has registered an account for the service in the new registration step. Specifically, the contract processing unit 1051 of the server 10 stores the destination information (such as name) and the second email address of the second user in the items of user name and email address of a new record in the user table 1012. The user ID may be assigned any character string including the second email address, etc. As a result, the contract processing unit 1051 of the server 10 automatically registers the second user as a user in the electronic contract service according to the present disclosure. The contract processing unit 1051 of the server 10 sends a message to at least one of the email addresses of the first user and the second user notifying them that the second user has registered an account. The message includes the URL of the web page for referencing the digitized data, as already described. As a result, the other party will also register an account for the electronic contract service. The other party can conveniently check the contents of the concluded paper contract by referring to the electronic contract service according to the present disclosure.

[0119] <Intermediary conclusion process> The intermediary conclusion process is a process in which, when the creator and verifier are using different electronic contract services, the electronic contract service disclosed herein mediates the conclusion of an electronic contract between the creator and verifier in the different electronic contract services, thereby establishing the electronic contract between them.

[0120] <Outline of the mediation process> The intermediary conclusion process is a series of processes in which the creator creates electronic contract information, sets a verifying party to whom the electronic contract information is addressed, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, the electronic contract service disclosed herein executes a contract creation process in an external electronic contract service, the verifying party executes a contract confirmation process in the external electronic contract service, and the electronic contract service disclosed herein obtains and stores contract information related to the conclusion result from the external electronic contract service.

[0121] <Details of the mediation process> The details of the intermediation conclusion process will be described below.

[0122] In step S601, if the contract processing unit 1051 of the server 10 does not determine in the judgment step that the other party is able to use a service for executing electronic contract procedures, or if it determines that the other party is able to use a service other than the service, it executes a contract acceptance step of accepting a contract document from the first user. Specifically, the first user presses the intermediation button D143 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits to the server 10 a request for executing the intermediation conclusion process. When the contract processing unit 1051 of the server 10 receives the request, it generates an intermediation conclusion page and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the intermediation conclusion page on the display 2081 of the first user terminal 20 for presentation. 22 is an example of a mediation conclusion screen in the mediation conclusion process. A mediation conclusion page D3 is displayed on the display 2081 of the first user terminal 20. The mediation conclusion page D3 includes buttons D321, D322, and D323 for specifying input items, a contract information display area D330, document data D331, input items D332, D333, and D334, and a send button D340.

[0123] The first user operates the input device 206 of the first user terminal 20 to create contract information including document data related to the contract. The document data may be in any data format such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language) and may be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and transmits the created document data and the first user ID 2011 to the server 10. The contract processing unit 1051 of the server 10 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores new contract information in the document table 1014. Note that the contract information may include information indicating that the contract information is the subject of an intermediation conclusion process. This makes it possible to distinguish whether the contract information stored in the document table 1014 is contract information related to a contract creation process or contract information related to an intermediation conclusion process. The creation of the contract information may include a process similar to step S101 of the contract creation process.

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

[0125] In step S603, the first user can operate the input device 206 of the first user terminal 20 or the like to set input items for the contract information. The details are the same as those in step S103 of the contract creation process, so a detailed explanation will be omitted.

[0126] In step S604, the first user sets input rules for each input item to be added. The details are the same as those in step S104 of the contract creation process, so a detailed explanation will be omitted.

[0127] In step S605, the contract preparation unit 1042 of the server 10 accepts input data for a plurality of input items input by the first user. The details are similar to step S105 of the contract creation process, so a detailed explanation will be omitted.

[0128] In step S606, the contract processing unit 1051 of the server 10 receives an instruction from the first user to request the second user to conclude a contract for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 to press the send button D340 displayed on the intermediation conclusion page D3, thereby transmitting a request to transmit contract information to the server 10. The contract processing unit 1051 of the server 10 receives and accepts the request.

[0129] In step S607, the contract processing unit 1051 of the server 10 creates contract information for an external electronic contract service based on the contract information, input item information, and the like accepted in the contract acceptance step. Specifically, the contract processing unit 1051 of the server 10 refers to the confirmation table 1015, and obtains the verifyer email address (assumed to be the second email address) and external service ID of the verifyer (assumed to be the second user) who is the earliest in the verification order among the verifyer information whose verification flag stores information indicating that the contract information verification procedure has not been completed. The contract processing unit 1051 of the server 10 logs in to an external electronic contract service (external contract service) identified based on the external service ID by using predetermined account information. It is preferable to access via an API (Application Programming Interface) or the like provided by the external contract service. In the present disclosure, a configuration is disclosed as an example in which information processing in the external contract service is controlled by sending a request to an API end point provided by the external contract service, but this is not limited thereto. For example, information processing in the external contract service may be controlled via scraping such as Selenium, a robot, an RPA tool, or the like. In addition, the specified account information may be account information issued to the electronic contract service according to the present disclosure, or multiple pieces of account information may be created in an external contract service for each user related to the creator, such as the first user. The contract processing unit 1051 of the server 10 creates contract information (external contract information) in the external contract service based on the document data included in the contract information, the input data included in the input item information, etc. Specifically, the contract processing unit 1051 of the server 10 executes the processes related to steps S101 to S105 of the contract creation process in the present disclosure in the external contract service on behalf of the first user. This allows the contract processing unit 1051 of the server 10 to create contract information in the external contract service on behalf of the first user without the first user creating an account in the external contract service. Note that the confirmer in the external contract service may include only the second email address, and may exclude the email addresses of the other confirmers selected in step S602. This is because the other confirmers may not necessarily be able to use the external contract service.

[0130] The contract processing unit 1051 of the server 10 transmits an instruction to the external contract service to request the second user to conclude a contract for the contract information. Specifically, the contract processing unit 1051 of the server 10 transmits a request to transmit the created external contract information to the second email address of the second user as the confirmer, to an API endpoint provided by the external contract service.

[0131] In step S608, the contract processing unit 1051 of the server 10 executes a contract notification step of notifying the other party of the contract document accepted in the contract acceptance step via another service. Specifically, the external contract service sends a message to the second user notifying the second user that a request to confirm the contract information has been sent. The message sent to the second user includes a URL including a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a character string that is an arbitrary encryption of the document ID, or a character string that can identify the document ID by referring to a table (not shown). Note that the processing in the external contract service in step S608 is similar to step S106 in the contract creation processing of the present disclosure, except that the execution entity is the external contract service rather than the electronic contract service of the present disclosure, and therefore a description thereof will be omitted.

[0132] The second user who will be the confirmer in the external contract service can select the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, and thereby open the web page specified by the URL using the browser application of the second user terminal 30. As a result, the second user terminal 30 transmits a request to the server 10 to execute a contract confirmation process in the external contract service. The second user executes the contract confirmation process in the external contract service. The contract confirmation process in the external contract service by the second user is the same as steps S301 to S305 of the contract confirmation process in the electronic contract service according to the present disclosure, except that the execution subject is the external contract service rather than the electronic contract service according to the present disclosure, and therefore a description thereof will be omitted. The second user can check the contents of the contract information received in the external contract service and approve (agree) to the contents of the contract information.

[0133] In step S609, the contract processing unit 1051 of the server 10 executes a confirmation acquisition step of acquiring that the other party has confirmed the contract document notified in the contract notification step in another service. In response to acquiring in the confirmation acquisition step that the other party has confirmed the contract document in another service, the contract processing unit 1051 of the server 10 executes a contract storage step of adding a digital signature to the contract document accepted in the contract acceptance step and storing it. Specifically, the contract processing unit 1051 of the server 10 periodically accesses an API endpoint for checking the processing status of the contract confirmation process in the external contract service, thereby checking whether the target contract information has been confirmed (approved) by the second user. Note that the contract processing unit 1051 of the server 10 may access the API endpoint in response to a message notified in response to the second user confirming (approving) the contract information in the external contract service (the contract confirmation process in the external contract service has been completed). The contract processing unit 1051 of the server 10 transmits a request to the API endpoint of the external contract service to confirm whether the target contract information has been confirmed (approved) by the second user. When the information included in the response received from the API endpoint includes information indicating that the second user has confirmed (approved) the contract information in the external contract service, the contract processing unit 1051 of the server 10 determines that the target contract information has been confirmed (approved) by the second user. When the contract processing unit 1051 of the server 10 determines that the target contract information has been confirmed (approved) by the second user, it transmits a request to an API endpoint for acquiring contract information in the external contract service. The contract processing unit 1051 of the server 10 acquires, from the API endpoint, the contract information stored with an electronic signature indicating that the contract conclusion has been approved in the external contract service. The contract processing unit 1051 of the server 10 stores the contract information acquired from the external contract service in the field of digitized data in the document table 1014. The contract processing unit 1051 of the server 10 may further add an electronic signature to the contract information received from the external contract service and store it. As a result, the contract information (document data) in the electronic contract service of the present disclosure and the contract information (digitized data) in the external contract service are stored in association with each other.

[0134] In step S609, the contract processing unit 1051 of the server 10 executes a contract acquisition step of reaching an agreement on a contract document with the other party on behalf of the first user in the other service, and acquiring the contract document to which a digital signature has been affixed in the other service. Specifically, since the contract processing unit 1051 of the server 10 executes the contract creation process on behalf of the first user in the external contract service, the contract information concluded in the external contract service is the contract information agreed upon between the account issued to the electronic contract service according to the present disclosure and the second user and to which an electronic signature has been attached. The contract processing unit 1051 of the server 10 acquires the contract information to which an electronic signature has been attached from the external contract service. As a result, even if the first user and the other party use different electronic contract services, the information processing service disclosed herein can mediate the conclusion of an electronic contract in the other service used by the other party on behalf of the first user. In this case, two electronic contracts are created in the information processing service disclosed herein and in the other service used by the other party, and the evidentiary force of the electronic contracts can be guaranteed by comparing the electronic signatures attached to each.

[0135] The contract processing unit 1051 of the server 10 searches the checker email address field of the confirmation table 1015 based on the second email address, and stores information indicating that the confirmation has been completed (True) in the confirmation flag field of the relevant record. This is regarded as having resulted in the second user executing the contract confirmation process in the electronic contract service according to the present disclosure.

[0136] The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all the checkers. Specifically, the contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all the checkers when a value of True is stored in the confirmation flag of the checker's record in the confirmation table 1015.

[0137] Furthermore, the contract processing unit 1051 of the server 10 assigns an electronic signature to the document data in the document table 1014 and stores the same. Note that this is the same process as the electronic signature process in step S305 of the contract confirmation process, and therefore a description thereof will be omitted.

[0138] When the contract confirmation process has been performed by all the confirmers, the contract confirmation unit 1043 of the server 10 transmits a message to the first user notifying the completion of the contract confirmation process. Similarly, the contract confirmation unit 1043 of the server 10 may transmit a message to the second user notifying the completion of the contract confirmation process.

[0139] Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the email address of the first user by a communication means such as email to notify the first user that the second user has completed confirmation of the contract information. In other words, the first user is notified that the second user has approved the conclusion of the contract. This allows the first user to know that the conclusion of the contract with the second user has been completed. The message to be sent to the first user may include information about a URL, which is an end point including a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a character string that is an arbitrary encryption of the document ID, or other information such as a character string that can identify the document ID by referring to a table (not shown).

[0140] At this time, two electronic contracts are created, one in the information processing service disclosed herein and one in another service used by the other party, and by comparing the electronic signatures affixed to each, the evidentiary value of the electronic contracts can be guaranteed.

[0141] In step S609, the contract processing unit 1051 of the server 10 executes an invitation step of notifying the other party of a message inviting the other party to a service for executing electronic contract procedures. Specifically, the contract processing unit 1051 of the server 10 may include a message inviting the second user to the electronic contract service according to the present disclosure in the message sent to the second user. The message includes URL information for registering an account with the electronic contract service according to the present disclosure. The URL may include information for identifying the second user. The message may include information to assist the second user in carrying out electronic contract procedures, such as information indicating the procedures for the second user to start using the electronic contract service, and information indicating the procedures for concluding an electronic contract using the electronic contract service. The message may include information such as a URL or telephone number indicating the contact point for inquiries or support for the electronic contract service according to the present disclosure. By inquiring at the URL or telephone number, a user can receive information on the procedure for starting to use the electronic contract service, the procedure for concluding an electronic contract using the electronic contract service, etc. This makes it possible to motivate the other party to use electronic contract services even if the other party is not familiar with such services.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0156] (Appendix 1) A program having a processor and a memory unit, which provides a computer with a service related to a contract document to be agreed upon between the parties, wherein the processor executes a other party receiving step (S701) in which information identifying the other party with which the contract contents will be agreed upon from a first user, a determination step (S702) in which the processor determines the usage status of a service for executing electronic contract procedures based on the information identifying the other party received in the other party receiving step, and a determination presentation step (S703) in which the processor presents the determination result determined in the determination step to the first user. This allows users to confirm the results of a judgment as to whether or not a contract can be concluded with a trading partner using the electronic contract service when concluding a contract with the trading partner, eliminating the need to inquire in advance with the trading partner whether or not an electronic contract can be concluded using the electronic contract service.

[0157] (Appendix 2) A program as described in Appendix 1, in which the processor executes a template presentation step (S704) of presenting one or more templates including an agreement regarding the electronic contract to the first user if the processor determines in the determination step that a service is available for the other party to execute electronic contract procedures. If the other party is able to use the electronic contract service to conclude a contract, the first user can be presented with a template of a contract document that is based on an electronic contract. A template of a contract document that is based on an electronic contract is a template of a contract document that includes the terms "electronic processing" and "electronic record" and includes provisions related to electronic contracts (articles, clauses, etc.). For example, it includes a template of a contract document that includes the following clauses, provisions, etc. Article ●● (Contract Formation) It is established when the seller delivers to the buyer the individual contract (regardless of the form, such as an order confirmation or receipt) that has been signed and sealed or has been subjected to an electronic processing equivalent thereto. ... Article ●● (Consultation) In addition, when consultations are held, if requested by the other party, an agreement to hold consultations will be made in writing or by means of an electromagnetic record. ... Final Sentence As evidence of the formation of this Agreement, an electromagnetic record of this document will be created, and after both parties have agreed, they will affix their electronic signatures and each party will keep a copy of the electromagnetic record.

[0158] (Appendix 3) A program described in Appendix 2, in which a processor executes a contract acceptance step (S101) in which a contract document created based on the template presented in the template presentation step is accepted from a first user, and a confirmer addition step (S102) in which information identifying the other party is added to the confirmer of the contract document accepted in the contract acceptance step. This allows the other party who agrees to the contract contents to be automatically included as a reviewer (approver) when creating a new contract document. The first user can include the other party in the contract document circulation and approval flow without specifying the other party.

[0159] (Appendix 4) A program as described in Appendix 1, which executes an invitation step (S706) of notifying the other party of a message inviting the other party to a service for executing electronic contract procedures if the processor does not determine in the determination step that a service for executing electronic contract procedures is available to the other party. This makes it possible to motivate the other party to use electronic contract services even if the other party does not use electronic contract services.

[0160] (Appendix 5) The program described in Appendix 4, wherein the invitation step (S706) is a step of notifying the other party of a message including information to assist the other party in executing the electronic contract procedure, or information indicating the contact information for the support desk of the service for executing the electronic contract procedure. This makes it possible to motivate the other party to use electronic contract services even if the other party is not familiar with such services.

[0161] (Appendix 6) The program described in Appendix 4, in which the processor executes a new registration step (S707) of accepting an account registration for a service for executing electronic contract procedures from the other party in response to the message notified in the invitation step, a registration notification step (S708) of notifying the first user of a message in response to the acceptance of the account registration from the other party in the new registration step, a contract acceptance step (S101) of accepting a contract document in response to the message notified in the registration notification step, and a verifyer addition step (S102) of including the other party as a verifyer of the contract document accepted in the contract acceptance step. As a result, when the other party registers an account with the electronic contract service, the first user is notified that the other party has registered an account with the electronic contract service. When the first user uploads the contract document in response to the notification, the other party who agrees to the contract contents can be automatically included as a reviewer (approver). The first user can include the other party in the circulation and approval flow of the contract document without specifying the other party.

[0162] (Appendix 7) A program as described in Appendix 1, which executes, when the processor does not determine in the determination step that a service for the other party to execute electronic contract procedures is available, a contract acceptance step (S501) of accepting a contract document from a first user, a paper contract sending step (S507) of executing a process for sending to the other party a paper contract obtained by printing out the contract document accepted in the contract acceptance step on paper, without the first user having to perform the work of sending, a contract digitization step (S509) of executing a process for accepting the return of the paper contract sent to the other party in the paper contract sending step, without the first user having to perform the work of receiving, and digitizing the returned paper contract, and a contract storage step (S509) of adding an electronic signature to the paper contract digitized in the contract digitization step and storing it. As a result, even if the other party does not use the electronic contract service, the contract document uploaded using the electronic contract service can be sent to the other party as a paper contract by mail, etc. Also, the paper contract returned by the other party with its signature and seal can be digitized by scanning, etc., and an electronic signature can be added to store and manage it. The first user can carry out appropriate contract procedures with the other party without carrying out cumbersome tasks such as creating a paper contract.

[0163] (Appendix 8) The program described in Appendix 7, wherein the processor executes a completion notification step (S509) of notifying the first user and the other party of a message indicating that the paper contract has been stored in the contract storage step. This allows the first user and the other party to confirm through the message that the contract has been concluded. The completion of the contract can be confirmed without notifying each other. In addition, the first user and the other party can confirm the contents of the concluded paper contract by referring to a file or the like that has been stored with an electronic signature.

[0164] (Appendix 9) A program as described in Appendix 8, in which a processor executes a new registration step (S509) of registering the other party as an account with a service for executing electronic contract procedures, and a completion notification step (S509) of notifying the other party of a message including information indicating that the other party has registered an account with the service in the new registration step. As a result, the other party will also register an account for the electronic contract service. The other party can conveniently check the contents of the concluded paper contract by referring to the electronic contract service according to the present disclosure.

[0165] (Appendix 10) A program as described in Appendix 1, which executes, when the processor does not determine in the judgment step that a service for the other party to execute electronic contract procedures is available, or when the processor determines that the other party can use a service other than the service, a contract acceptance step (S601) of accepting a contract document from the first user, a contract notification step (S608) of notifying the other party via the other service of the contract document accepted in the contract acceptance step, a confirmation acquisition step (S609) of acquiring, in the other service, that the other party has confirmed the contract document notified in the contract notification step, and a contract storage step (S609) of applying an electronic signature to the contract document accepted in the contract acceptance step and storing it in response to acquiring, in the confirmation acquisition step, that the other party has confirmed the contract document in the other service. This means that if the other party is not using the electronic contract service but is using another electronic contract service, the other party can approve (confirm) the contract document via that other electronic contract service.

[0166] (Appendix 11) The program described in Appendix 10, in which the processor executes a contract acquisition step (S609) of agreeing on a contract document with the other party on behalf of the first user in another service, and acquiring the contract document to which an electronic signature has been affixed in the other service. As a result, even if the first user and the other party use different electronic contract services, the information processing service disclosed herein can mediate the conclusion of an electronic contract in another service used by the other party on behalf of the first user. At this time, two electronic contracts are created, one in the information processing service disclosed herein and one in another service used by the other party, and by comparing the electronic signatures affixed to each, the evidentiary value of the electronic contracts can be guaranteed.

[0167] (Appendix 12) The program described in Appendix 10, in which a processor executes an invitation step (S609) of notifying the other party of a message inviting them to a service for executing electronic contract procedures. This makes it possible to motivate the other party to use electronic contract services even if the other party does not use electronic contract services.

[0168] (Appendix 13) A program as described in Appendix 1, which executes a selection presentation step (S703) that, if it is not determined in the determination step that a service for executing electronic contract procedures is available to the other party, notifies the first user of a message inviting the first user to a service for executing electronic contract procedures with the other party, and presents at least one of the following procedures as a selectable option: concluding a contract with the other party through a paper contract, and concluding an electronic contract through another service used by the other party. As a result, even if the other party does not use the electronic contract service disclosed herein, the first user can select and execute one of the following procedures for concluding a contract: registering an account with the electronic contract service disclosed herein, concluding a contract using a paper contract, or concluding a contract electronically via another service used by the other party.

[0169] (Appendix 14) A method implemented on a computer having a processor and a memory, the processor performing all the steps performed in the invention according to any one of claims 1 to 13. This allows users to confirm the results of a judgment as to whether or not a contract can be concluded with a trading partner using the electronic contract service when concluding a contract with the trading partner, eliminating the need to inquire in advance with the trading partner whether or not an electronic contract can be concluded using the electronic contract service.

[0170] (Appendix 15) An information processing device comprising a control unit and a memory unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 13. This allows users to confirm the results of a judgment as to whether or not a contract can be concluded with a trading partner using the electronic contract service when concluding a contract with the trading partner, eliminating the need to inquire in advance with the trading partner whether or not an electronic contract can be concluded using the electronic contract service.

[0171] (Appendix 16) A system comprising means for performing all the steps performed in any of the inventions according to appendix 1 to appendix 13. This allows users to confirm the results of a judgment as to whether or not a contract can be concluded with a trading partner using the electronic contract service when concluding a contract with the trading partner, eliminating the need to inquire in advance with the trading partner whether or not an electronic contract can be concluded using the electronic contract service. [Explanation of symbols]

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

Claims

1. A program comprising a processor and a storage unit, the program providing a service related to a contract document to be agreed upon between parties to a computer, The processor, a counterparty receiving step of receiving information identifying a counterparty with which the contract contents are agreed from the first user; a determination step of determining a usage status of the service for executing an electronic contract procedure based on information identifying the other party received in the other party receiving step; a determination presentation step of presenting a result of the determination made in the determination step to the first user; A program that executes.

2. The processor, a template presentation step of presenting one or more templates including an agreement regarding an electronic contract to the first user when the other party determines in the determination step that the service for executing an electronic contract procedure is available; Execute The program according to claim 1.

3. The processor, a contract receiving step of receiving, from the first user, a contract document created based on the template presented in the template presentation step; a verifying person adding step of adding information identifying the other party to the verifying person of the contract document accepted in the contract accepting step; Execute The program according to claim 2.

4. The processor, an invitation step of notifying the other party of a message inviting the other party to the service for executing an electronic contract procedure when the other party does not determine in the determination step that the service for executing an electronic contract procedure is available; Execute The program according to claim 1.

5. The invitation step is a step of notifying the other party of the message including information for assisting the other party in executing an electronic contract procedure or information indicating a contact point for a support desk of the service for executing an electronic contract procedure. The program according to claim 4.

6. The processor, a new registration step of accepting an account registration for the service from the other party in response to the message notified in the invitation step in order to execute an electronic contract procedure; a registration notification step of notifying the first user of the message in response to the acceptance of the account registration from the other party in the new registration step; a contract acceptance step of accepting a contract document in response to the message notified in the registration notification step; a verifying person adding step of including the other party as a verifying person of the contract document accepted in the contract accepting step; Execute The program according to claim 4.

7. The processor, a contract acceptance step of accepting a contract document from the first user when the other party does not determine in the determination step that the service for executing an electronic contract procedure is available; a paper contract sending step of executing a process for sending a paper contract, which is a paper copy of the contract document accepted in the contract acceptance step, to the other party without requiring the first user to perform a sending operation; a contract digitization step of executing a process for accepting the return of the paper contract sent to the other party in the paper contract sending step without requiring the first user to perform a receiving operation, and digitizing the returned paper contract; a contract storage step of adding an electronic signature to the paper contract digitized in the contract digitization step and storing the electronic signature; Execute The program according to claim 1.

8. The processor, a completion notification step of notifying the first user and the other party of a message indicating that the paper contract has been stored in the contract storage step; Execute The program according to claim 7.

9. The processor, a new registration step of registering the other party as an account in the service for executing an electronic contract procedure; Run the completion notification step is a step of notifying the other party of the message including information indicating that the other party has registered an account for the service in the new registration step; The program according to claim 8.

10. The processor, a contract acceptance step of accepting a contract document from the first user when the other party has not determined in the determination step that the service for executing an electronic contract procedure is available and when the other party has determined that a service other than the service is available; a contract notification step of notifying the other party of the contract document accepted in the contract acceptance step via the other service; a confirmation acquisition step of acquiring, in the other service, that the other party has confirmed the contract document notified in the contract notification step; a contract storage step of adding an electronic signature to the contract document accepted in the contract acceptance step and storing the contract document in response to acquiring in the confirmation acquisition step that the other party has confirmed the contract document in the other service; Execute The program according to claim 1.

11. The processor, a contract acquisition step of reaching an agreement on the contract document with the other party on behalf of the first user in the other service and acquiring the contract document to which a digital signature has been affixed in the other service; Execute The program according to claim 10.

12. The processor, an invitation step of notifying the other party of a message inviting the other party to the service for executing an electronic contract procedure; Execute The program according to claim 10.

13. When the other party does not determine in the determining step that the service for executing an electronic contract procedure is available, Sending a message to the other party inviting them to use the service to execute an electronic contract procedure; Concluding a contract with the other party through a paper contract; Electronic contract conclusion through other services used by the other party; a selection and presentation step of selectively presenting at least one of the procedures; Execute The program according to claim 1.

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

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

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

Images