JP2023179029A - Program, information processing device, information processing system, and information processing method - Google Patents

Abstract

To provide a program for more simply inputting information on a counterpart of contract conclusion in an electronic contract procedure between a plurality of users, an information processing device, a system and a method.SOLUTION: A program of a server for executing an electronic contract procedure between a plurality of users causes a processor to execute a contract reception step in which the processor receives contract information to be an object of a contract conclusion from a first user, a candidate acquisition step for acquiring one or more pieces of candidate information corresponding to one or more recipient candidates for the contract information received in the contract reception step by inquiring an external server, a candidate presentation step for presenting the one or more pieces of candidate information acquired in the candidate acquisition step to the first user, and a recipient reception step for receiving second identification information being the recipient of the contract information received in the contract reception step from the one or more pieces of candidate information presented to the first user in the candidate presentation step on the basis of selection operation of the first user.SELECTED DRAWING: Figure 13

Description

The present disclosure relates to a program, an information processing device, an information processing system, and an information processing method.

With the development and spread of computer technology, documents that were previously paper-based are being digitized. For example, it is being considered that documents such as contracts that require the signatures and seals of the parties involved will be managed using electronic data.
Patent Document 1 discloses an information processing system regarding digital contracts that includes a creator terminal, a confirmer terminal, and a contract management server.

JP2017-10096

In electronic contract procedures between multiple users, there is a problem in that it is complicated to input information about the other party with whom the contract is to be concluded.
Therefore, the present disclosure has been made to solve the above problems, and its purpose is to provide a technology for more easily inputting information on the other party to conclude a contract.

A program, comprising a processor and a storage unit, in which a computer executes electronic contract procedures between a plurality of users, wherein the processor receives contract information as a subject of contract conclusion from a first user; a contract reception step; and a candidate acquisition step that acquires one or more candidate information corresponding to one or more recipient candidates of the contract information received in the contract reception step by querying the external server, and one or more candidate information acquired in the candidate acquisition step. or a candidate presenting step of presenting a plurality of candidate information to the first user; and a contract accepting step from the one or more candidate information presented to the first user in the candidate presenting step based on the first user's selection operation. A program that executes a recipient receiving step of receiving second identification information of a recipient of the received contract information.

According to the present disclosure, in electronic contract procedures between a plurality of users, it is possible to more easily input information on the other party to conclude the contract.

1 is a block diagram showing the functional configuration of system 1. FIG. 1 is a block diagram showing the functional configuration of a server 10. FIG. 2 is a block diagram showing the functional configuration of a first user terminal 20. FIG. 3 is a block diagram showing the functional configuration of a second user terminal 30. FIG. 3 is a block diagram showing the functional configuration of an external server 40. FIG. 3 is a diagram showing a data structure of a user table 1012. FIG. 3 is a diagram showing the data structure of a group table 1013. FIG. 3 is a diagram showing the data structure of a document table 1014. FIG. 3 is a diagram showing a data structure of a confirmation table 1015. FIG. 3 is a diagram showing the data structure of an input item table 1016. FIG. 3 is a diagram showing the data structure of a contract group table 1018. FIG. 5 is a diagram showing the data structure of a user table 5012. FIG. 3 is a flowchart showing the operation of contract creation processing. 3 is a flowchart showing the operation of contract confirmation processing. This is an example screen showing the operation of contract creation processing. This is an example of a candidate information presentation screen in contract creation processing. This is an example of a screen showing a confirmation request message notified to the second user terminal 30. This is an example screen showing the operation of contract confirmation processing. It is an example of a screen showing a conclusion completion message notified to the second user terminal 30. 2 is a block diagram showing the basic hardware configuration of a computer 90. FIG.

Embodiments of the present disclosure will be described below with reference to the drawings. In all the figures explaining the embodiments, common components are given the same reference numerals and repeated explanations will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are essential components of the present disclosure. Furthermore, each figure is a schematic diagram and is not necessarily strictly illustrated.

<System 1 configuration>
A 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 such as a server 10, a first user terminal 20, a second user terminal 30, and an external server 40, which are connected via a network N.
FIG. 1 is a block diagram showing the functional configuration of the system 1. As shown in FIG.
FIG. 2 is a block diagram showing the functional configuration of the server 10.
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.
FIG. 5 is a block diagram showing the functional configuration of the external server 40.

Each information processing device is composed of a computer including an arithmetic unit and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. Regarding each of the server 10, the first user terminal 20, the second user terminal 30, and the external server 40, explanations that overlap with the basic hardware configuration of the computer and the basic functional configuration of the computer, which will be described later, will be omitted.

<Configuration of server 10>
The server 10 is an information processing device that provides electronic contract conclusion services between multiple users. The server 10 is an information processing device that provides a service of storing and managing contract information concluded between a plurality of users.
The server 10 includes a storage section 101 and a control section 104.

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

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

The user table 1012 is a table that stores and manages information about member users (hereinafter referred to as users) who use the service. When a user registers to use a 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 in the present disclosure, users who use services do not necessarily need to be registered in the user table 1012.
The user table 1012 is a table having user ID as a primary key and columns of user ID, user name, email address, group ID, and approval authority.
FIG. 6 is a diagram showing the data structure of the user table 1012.

The user ID is an item that stores user identification information for identifying a user. The user identification information is an item in which a unique value is set for each user.
The user name is an item that stores the user's name. The user name may be any character string such as a nickname instead of a full name.
The email address is an item that stores the user's email address.
Group ID is an item that stores 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 the user's approval conclusion. For a user who has the authority to approve the conclusion of a contract (authorization authority), information such as True that has the authority to approve the conclusion of the contract is stored. On the other hand, for a user who does not have the authority to approve the conclusion of a contract, information such as False, blank, or a null value that does not have the authority to approve the conclusion of the contract is stored.
A configuration may also be adopted in which approval authority can be set according to contract information. For example, a configuration may be adopted in which user A has approval authority for specific contract information A but does not have approval authority for specific contract information B.
It may also be configured such that approval authority can be set according to the type of contract information (contract information type) such as a non-disclosure agreement, joint research contract, or contract. For example, a configuration may be adopted in which user A has the authority to approve non-disclosure agreements, but not authority to approve contract contracts.
In addition, a configuration may be adopted in which authority information of multiple levels (levels, ranks) is stored depending on the department, government office, etc. to which the user belongs. For example, information such as C for temporary employees, B for general employees, A for managers, and S for executives is stored in the approval authority field, and depending on the contract type information, contract amount, etc., (For example, a configuration may be adopted in which only a user who has approval authority such as A or above for a non-disclosure agreement) can approve the conclusion of a contract.

The group table 1013 is a table that stores and manages information regarding groups to which users belong (group information). The group can be defined as any group to which the user belongs, such as a corporation, company, circle, organization, or department within a company.
The group table 1013 is a table having columns of group ID, group name, and administrator ID, with group ID as the primary key.
FIG. 7 is a diagram showing the data structure of the group table 1013.

Group ID is an item that stores group identification information for identifying a group. Group identification information is an item in which a unique value is set for each group.
Group name is an item that stores the name of the group. Any character string can be set for the group name.
The administrator ID is an item that stores 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 predetermined position or authority in a group such as an organization.

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

The document ID is an item that stores document identification information for identifying contract information. The document identification information is an item in which a unique value is set for each contract information.
Document data is an item that stores contract information (binary or text data). Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
This item stores the creator ID and user identification information for identifying the user who is the creator of the contract information.

The confirmation table 1015 is a table for storing and managing information (confirmer information) including the email address of a user who is a confirmer of contract information.
The confirmation table 1015 is a table having columns of document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time.
FIG. 9 is a diagram showing the data structure of the confirmation table 1015.

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

The input item table 1016 is a table that stores and manages information regarding input items (input item information) associated with 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. 10 is a diagram showing the data structure of the input item table 1016.

The input item ID is an item that stores input item identification information for identifying the input item.
The document ID is an item that stores document identification information of electronic contract information with which an input item is associated.
The input person ID is an item that stores the user identification information or email address of the input person who inputs the input data for the input item. Specifically, the input user ID stores the creator ID, the email address of the user specified by the creator ID, the confirmer email address, and the like.
The input data is an item that stores input data input into an input item by an inputter.
The input rule is an item that stores input rule information regarding input rules for input items. Input rules include data types such as date, datetime, text, and integer, as well as any input items such as the number of characters for strings and regular expressions for strings. Input rule information regarding input rules can be stored.
The date and time is an item that stores the date and time when the input data was input into the input item by the inputter.

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

The document ID is an item that stores document identification information for identifying contract information.
The cabinet ID stores cabinet identification information for identifying the cabinet. The cabinet ID is classification information for managing and classifying contract information.

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

The user registration control unit 1041 performs a process of storing information of users who wish to use the service according to the present disclosure in the user table 1012.
Information stored in the user table 1012 is transmitted to the server 10 by a user opening a web page operated by a service provider from any information processing terminal, inputting information into a predetermined input form, and transmitting the information to the server 10 . The user registration control unit 1041 stores the received information in a new record of the user table 1012, and the user registration is completed. This allows the users stored in the user table 1012 to use the service.
Prior to the registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a predetermined examination to restrict whether or not the user can use the service.
The user ID may be any character string or number that can identify the user, and may be any character string or number desired by the user, or may be automatically set by the user registration control unit 1041. .

The contract creation unit 1042 executes contract creation processing. Details will be described later.

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

<Configuration of first user terminal 20>
The first user terminal 20 is an information processing device operated by a user who uses the service. The first user terminal 20 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The first user terminal 20 includes a storage section 201, a control section 204, an input device 206, and an output device 208.

<Configuration of storage unit 201 of 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.

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

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

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

<Configuration of input device 206 of 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.

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

<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 stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smartphone or a tablet. Further, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The second user terminal 30 includes a storage section 301, a control section 304, an input device 306, and an output device 308.

<Configuration of storage unit 301 of 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.

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

The application program 3012 may be stored in advance in the storage unit 301, or may be downloaded from a web server operated by a service provider via a communication IF.
Application programs 3012 include applications such as web browser applications.
Application program 3012 includes an interpreted programming language, such as JavaScript®, executed on a web browser application stored on second user terminal 30.

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

<Configuration of input device 306 of 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.

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

<Configuration of external server 40>
The external server 40 is an information processing device that provides a service of storing and managing other user information associated with the user. For example, the external server 40 is an information processing system or information processing service provided outside the server 10.
The external server 40 includes a business card management system and the like that stores and manages business card information of other users with whom the user has exchanged business cards in the past.
The external server 40 includes a CRM (Customer Relationship Management) system that stores and manages customer information for each customer of the user, information regarding business negotiations, and the like. A CRM system may include a business card management system. Examples of CRM systems include SalesForce and HubSpot.
The external server 40 includes an external mail service, an external chat service, and the like. External email services include Gmail and the like. External chat services include Slack and Slack Connect.
The external server 40 includes a storage section 401 and a control section 404.

<Configuration of storage unit 401 of external server 40>
The storage unit 401 of the external server 40 includes an application program 4011 and a user table 4012.

The application program 4011 is a program for causing the control unit 404 of the server 10 to function as each functional unit.

The user table 4012 is a table having user ID as a primary key and columns of user ID, user name, email address, and user attribute.
FIG. 12 is a diagram showing the data structure of the user table 4012.

The user ID is an item that stores user identification information for identifying a user. The user identification information is an item in which a unique value is set for each user.
The user name is an item that stores the user's name. The user name may be any character string such as a nickname instead of a full name.
The email address is an item that stores the user's email address.
User attributes are attribute information regarding users. The user attributes include organizational information regarding the organization to which the user belongs, position information regarding the user's position, department information regarding the department to which the user belongs, and the like.
The organizational information includes information regarding arbitrary organizations and groups such as companies, corporations, corporate groups, circles, and various organizations. The organizational information may include more detailed information for each subgroup, such as company departments (sales department, general affairs department, customer support department). The user attributes may include attribute information such as the user's date of birth, age, gender, and credit score.

<Configuration of control unit 404 of external server 40>
The control unit 404 of the external server 40 includes a user registration control unit 4041. The control unit 404 realizes each functional unit by executing the application program 4011 stored in the storage unit 401.

The user registration control unit 4041 performs a process of storing information of users who wish to use the service according to the present disclosure in the user table 4012.
Information stored in the user table 4012 is transmitted to the external server 40 by the user opening a web page operated by the external server 40 from any information processing terminal, inputting information into a predetermined input form, and transmitting the information to the external server 40 . The user registration control unit 4041 stores the received information in a new record of the user table 4012, and the user registration is completed. This allows the users stored in the user table 4012 to use the service.

<Operation of system 1>
Each process of the system 1 will be explained below.
FIG. 13 is a flowchart showing the operation of the contract creation process.
FIG. 14 is a flowchart showing the operation of the contract confirmation process.
FIG. 15 is an example of a screen showing the operation of the contract creation process.
FIG. 16 is an example of a candidate information presentation screen in the contract creation process.
FIG. 17 is an example of a screen showing a confirmation request message notified to the second user terminal 30.
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 notified to the second user terminal 30.

<Contract creation process>
The contract creation process is a process in which the creator creates electronic contract information and sends it to the confirmer. In this disclosure, the first user is the creator.

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

<Summary of contract creation process>
In the contract creation process, the creator creates electronic contract information, sets a confirmer to be the recipient of the electronic contract information, sets input items for the electronic contract information, sets input rules for the input items, and then the creator This is a series of processes in which input data for input items is received from , and electronic contract information is sent to the set confirmer.

<Details of contract creation process>
In step S101, the contract creation unit 1042 of the server 10 executes a contract reception step of receiving contract information for contract conclusion from the first user.
Specifically, the first user operates the input device 206 of the first user terminal 20 and creates contract information including document data related to the contract. The contract information can include document data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
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 receives the received first user ID 2011 and document data, and stores them in the creator ID and document data fields 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.

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

In step S102, the contract creation unit 1042 of the server 10 acquires one or more candidate information corresponding to one or more recipient candidates of the contract information received in the contract reception step by inquiring the external server. Execute the acquisition step.
Specifically, the first user transmits a request to display a list of candidate information to the server 10 by operating the input device 206 of the first user terminal 20. The contract creation unit 1042 of the server 10 sends a request to inquire about other users associated with the first user to a predetermined API endpoint of the external server 40 based on the first user ID 2011 included in the received request. Send to URL (Uniform ReSource Locator). The contract creation unit 1042 of the server 10 may refer to a table (not shown) based on the first user ID 2011 and execute a process of converting it into user identification information such as the user ID in the external server 40 of the first user.
Based on the user ID of the first user included in the request received from the server 10, the control unit 404 of the external server 40 refers to the user table 4012, etc., and determines the user ID, user name, and user name of the user associated with the first user. Obtain user information such as email address and user attributes.

For example, if the external server 40 is a business card management system or the like, the control unit 404 of the external server 40 can detect information written on a business card obtained by the first user in the past, and when the first user reads the business card, the control unit 404 of the external server 40 Obtain the user information of the user stored in association with the user. Thereby, as a user associated with the first user, it is possible to acquire user information of a party with whom the first user has exchanged business cards in the past.

For example, if the external server 40 is a CRM system or the like, the control unit 404 of the external server 40 acquires the user's user information included in the first user's customer information, information regarding business negotiations (business negotiation information), and the like. Thereby, as a user associated with the first user, it is possible to acquire user information of the first user's customers and parties with whom business negotiations have been conducted in the past.

For example, when the external server 40 is an external mail service, an external chat service, etc., the control unit 404 of the external server 40 acquires user information of users with whom the first user has exchanged messages and the like in the past. Thereby, as a user associated with the first user, it is possible to acquire user information of a partner with whom the first user has exchanged messages or the like in the past.

The control unit 404 of the external server 40 transmits the acquired one or more pieces of user information to the server 10. The contract creation unit 1042 of the server 10 acquires one or more pieces of user information received from the external server 40 as one or more pieces of candidate information corresponding to one or more recipient candidates of the first user's contract information. Identify.

For example, if the external server 40 is an external mail service or the like, the control unit 404 of the external server 40 acquires user information of users to whom the first user has sent and received mail in the past. For example, the user information may include signature information of users with whom the first user has sent and received emails in the past. Thereby, as a user associated with the first user, it is possible to acquire user information of a party with whom the first user has exchanged business cards in the past.

In step S102, the contract creation unit 1042 of the server 10 executes a candidate presentation step of presenting one or more candidate information acquired in the candidate acquisition step to the first user.
Specifically, the contract creation unit 1042 of the server 10 transmits one or more pieces of user information received from the external server 40 to the first user terminal 20. The control unit 204 of the first user terminal 20 transfers the received one or more pieces of user information to the first user terminal as one or more candidate information corresponding to one or more recipient candidates of the contract information of the first user. It is presented by displaying a list on the display 2081 of No. 20.

In step S102, the contract creation unit 1042 of the server 10 selects the contract information received in the contract acceptance step from the one or more candidate information presented to the first user in the candidate presentation step based on the selection operation of the first user. A recipient reception step of accepting second identification information of the recipient is executed.
Specifically, by operating the input device 206 of the first user terminal 20, the first user selects a second recipient from one or more candidate information listed on the display 2081 of the first user terminal 20. Select a user. This specifies second identification information that specifies the second user who is the recipient of the contract information. The first user may be able to select a plurality of second users.
The control unit 204 of the first user terminal 20 transmits the email address of the second user selected by the first user 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 confirmer email address and document ID fields of the confirmation table 1015, respectively, and stores the contract information and the document ID in the confirmation table 1015. It is stored in association with the second user's email address. Note that the first user may set the second user's language and access code, and store them in association with the second user's email address.
Note that the first user may input an e-mail address and send it to the server 10 by operating the input device 206 of the first user terminal 20. Thereby, a user who is not stored in the external server 40 can be set as a recipient.
At this time, a value of 1 is stored in the confirmation order item of the confirmation table 1015. In step S102, the first user may be able to select and set a plurality of users to be confirmers. In this case, the value of the confirmation order item of the user who is the confirmer is incremented by one and stored in accordance with the selection order. This sets the order of circulation of confirmers in contract confirmation processing, which will be described later. Note that setting the circulation order is not essential.

In step S102, the candidate acquisition step selects candidate information with an older registration date and time in the external server from among the plurality of candidate information related to the same user included in the one or more candidate information acquired from the external server. You may perform a step of excluding the information from the candidate information and acquiring it as one or more candidate information.
Specifically, if one or more pieces of user information received from the external server 40 include duplicate information regarding the same user, the contract creation unit 1042 of the server 10 selects the user information with the latest registration date and time in the external server 40. is set as user information related to the user, excluding older user information, and identified as one or more candidate information corresponding to one or more recipient candidates of the contract information of the first user.
The contract creation unit 1042 of the server 10 transmits the identified one or more pieces of candidate information to the first user terminal 20.

In step S102, the candidate acquisition step may include a step of acquiring user attributes of one or more users specified by one or more candidate information by inquiring an external server. The candidate acquisition step is a step of acquiring, as one or more candidate information, candidate information in which the user attribute of the user specified by the candidate information is included in a predetermined condition, from among the one or more acquired candidate information. . The candidate acquisition step is a step of acquiring candidate information in which the position of the user identified by the candidate information is equal to or higher than a predetermined value, as one or more candidate information.
Specifically, when the external server 40 is a business card management system, an external mail service, an external chat service, etc., the contract creation unit 1042 of the server 10 receives the first user from the external server 40 as a user associated with the first user. User information including user attributes of parties with whom the user has exchanged business cards in the past and with whom the first user has exchanged messages in the past is acquired. The contract creation unit 1042 of the server 10 compares predetermined conditions and user attributes, and selects the user information of the user whose user attributes are included in the predetermined conditions from one or more of the contract information of the first user. The candidate information is identified as one or more candidate information corresponding to the candidate. On the other hand, the contract creation unit 1042 of the server 10 compares predetermined conditions and user attributes, excludes user information of users whose user attributes are not included in the predetermined conditions, and generates one or more candidate information. Specify as.
For example, when the external server 40 is a business card management system, the contract creation unit 1042 of the server 10 stores the user information of a user whose job title included in the user attributes is a predetermined job title (section manager, general manager) or higher, for one or more users. Identify as candidate information. This makes it possible to exclude user information of users who are not expected to have the authority to approve a contract, and to specify the information as one or more candidate information.
The contract creation unit 1042 of the server 10 transmits the identified one or more pieces of candidate information to the first user terminal 20.

In step S102, the candidate acquisition step may include a step of acquiring one or more business negotiation information associated with one or more candidate information by inquiring an external CRM system.
Specifically, when the external server 40 is a CRM system or the like, the contract creation unit 1042 of the server 10 may acquire the first user's customer information and information regarding business negotiations (business negotiation information) from the external server 40. For example, the contract creation unit 1042 of the server 10 receives information regarding one or more users associated with the first user from the external server 40, and customer information and business negotiations associated with each of the one or more users, such as: Information such as affiliated organization, address, position, name, etc. may be acquired.

FIG. 16 is an example of a candidate information presentation screen in the contract creation process. The screen D20 displayed on the display 2081 of the first user terminal 20 includes a list screen D201 for displaying a list of candidate information. The list screen D201 includes displays regarding user names D2011, D2021, D2031, email addresses D2012, D2022, D2032, and check boxes D2013, D2023, and D2033 as candidates for one or more recipients of the contract information received in step S101. . The first user can select the second user who is the recipient of the contract information by selecting check boxes D2013, D2023, and D2033.

In step S103, the first user operates the input device 206 of the first user terminal 20 and sets input items for the contract information.
Specifically, the first user operates the input device 206 of the first user terminal 20 and sets a plurality of input items for the contract information created and stored in step S101. Any input items can be set, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a check box field for selecting check items, and a date field for entering the date. .
The first user operates the input device 206 of the first user terminal 20 and transmits a request to add an input item to the server 10. Upon receiving the request, the contract creation unit 1042 of the server 10 stores the document ID of the contract information in 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. Note that the first user can store a plurality of pieces of input item information in association with the contract information.

In step S103, the contract creation unit 1042 of the server 10 executes a contract editing step of editing the contract information received in the contract reception step, based on the negotiation information associated with the second identification information received in the recipient reception step. It's okay.
In the contract editing step, information regarding at least one of the organization, address, position, and name of the user related to the second identification information, which is included in the business negotiation information associated with the second identification information, is stored in the contract reception step. It includes a step of adding information to the received contract information.
Specifically, when the external server 40 is a CRM system or the like, the contract creation unit 1042 of the server 10 executes the contract creation unit 1042 in step S101 based on the customer information and business negotiation information regarding each of the one or more recipients set in step S102. You may edit the contract information received at .
For example, the contract creation unit 1042 of the server 10 may respond to each of the one or more recipients with respect to a plurality of input items such as affiliated organization, address, position, name, etc. related to the one or more recipients associated with the contract information. You may edit the contract information by entering the organization to which you belong, address, position, name, etc.
For example, the contract creation unit 1042 of the server 10 edits the document data received in step S101, and directly adds the affiliated organization, address, title, name, etc. corresponding to one or more recipients to the document data. You may edit the contract information by

In step S104, the first user sets input rules for each input item to be added. The first user specifies the input rule for each input item information set in step S103 by operating the input device 206 of the first user terminal 20, and transmits the input rule to the server 10. The contract creation unit 1042 of the server 10 stores the received input rule in the input rule field of each input item information record in the input item table 1016. This allows input rules to be set for each input item.

In step S105, the contract creation unit 1042 of the server 10 receives input data for a plurality of input items input by the first user.
Specifically, the first user inputs input data for each input item set in step S104 by operating the input device 206 of the first user terminal 20 or the like. For example, the first user may input input data of a number for managing contract information such as a reference number for a group to which the first user belongs to an input item set with a management number. The first user may input input data of the contract conclusion date of the contract information into the input item in which the contract conclusion date is set. When the first user completes inputting the input data to 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 input by the first user is stored in the input item table 1016.

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 regarding the contract information.
Specifically, the first user transmits the contract information by operating the input device 206 of the first user terminal 20 and pressing the send button 540 displayed on the screen 50 for creating contract information. Send the request to the server 10.

In step S106, the contract creation unit 1042 of the server 10 sends a message to the second user notifying that the first user has sent a request to confirm the contract information. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order item in the confirmation table 1015, and selects the user (first confirmation user) who is the first confirmer with the smallest value stored in the confirmation order item. Identify. In the present disclosure, the first confirmed user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's e-mail address, using communication means such as e-mail, to notify that the first user has sent a request to confirm the contract information.
The message notified to the second user includes URL (Uniform Resource Locator) information including a document ID for specifying 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). good. Further, the URL may include information for identifying the second user. For example, if the second user has not registered for the service according to the present disclosure, it is necessary to include information for identifying the second user in the URL.

That is, in step S106, the contract confirmation unit 1043 of the server 10 requests the second user identified by the second identification information received in the recipient reception step to approve the contract information received in the contract reception step. A notification step is executed to provide a notification.

When the first user sets an access code for the second user, the first user separately conveys the access code to the second user by means such as e-mail. As a result, even if a third party obtains the message to be notified to the second user, the third party cannot execute the contract confirmation process unless the third party obtains the access code.

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

<Modified example>
When the first user selects and sets a plurality of confirmers in step S102, the first user may be configured to be able to independently set different input item information in step S103 for each of the plurality of confirmers. do not have. For example, when the first user sets two users, the second user and the ninth user, as confirmers, the input items for the contract start date and contract end date are set for the second user, and the contract is concluded. The input item for the day may be set for the ninth user. In this case, in the contract confirmation process described later, the second user can enter input data for the input fields of the contract start date and contract end date, but input data for the input field of the contract conclusion date. Can not do it. On the other hand, the ninth user cannot input data to the input items for the contract start date and contract end date, but can input input data for the input item for the contract conclusion date. A configuration may be adopted in which a plurality of confirmers can be selected and set in duplicate for one piece of input item information.

Input items 532, 533, and 534 are drawn as drawing objects on the screen 50 for creating contract information. In the input items 532 and 533, the user identification information "USER-B" of the user who has selected and set input of the input item as the assignment, and the item "Text" as the type of the input item are drawn. In the input item 534 regarding stamping, the user identification information "USER-C" of the user who has selected and set the stamping as the assignment, and "seal" as the input item type are drawn.

<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. In the present disclosure, the second user is the confirmer.

<Summary of contract confirmation process>
The contract confirmation process accepts access from the confirmer, presents the confirmer with a confirmation screen that displays contract information, receives input data for input items from the confirmer, and receives data related to confirming the contract information from the confirmer. This is a series of processes for accepting requests.

<Details of contract confirmation process>
In step S301, the second user who is the confirmer operates the input device 306 of the second user terminal 30 and selects the URL written in the received message, thereby using the browser application of the second user terminal 30. A web page specified by the URL can be opened. Thereby, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process.

If the access code item is stored in the second user's record in the confirmation table 1015, the second user is requested to input the access code, and the entered access code and the second user's record in the confirmation table 1015 are By comparing the access code stored in the user's record, it is possible to perform 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, inputs the access code, and transmits it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the record of the second user in the confirmation table 1015, and if they match, executes contract confirmation processing. continue. On the other hand, if they do not match, the contract confirmation process is canceled. Note that the authentication process using the access code may be omitted.

The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID included in the received request, and acquires contract information. The contract confirmation unit 1043 of the server 10 searches the document ID item in the confirmation table 1015 based on the document ID included in the received request, and obtains 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 obtains input item information associated with the contract information.

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

The contract confirmation unit 1043 of the server 10 searches the user ID item in the user table 1012 based on the user identification information of the specified second user, and acquires the second user's approval authority item. Note that in this disclosure, the second user's approval authority is stored in the user table 1012, but the second user's approval authority may be stored for each group to which the second user belongs, or may be stored for each group to which the second user belongs. It may be stored for each information or for each contract information type. The contract confirmation unit 1043 of the server 10 acquires the second user's approval authority information for the target contract information.
Further, if the second user has not registered as a user in the service according to the present disclosure, the process may be executed by regarding the second user as a user who does not have approval authority.

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 identifying the second user), input item information, and confirmer approval authority information. 2 to the user terminal 30.

Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts an operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30.
Note that the confirmation screen presented to the second user is based on the language information stored in the language data item of the second user's record in the confirmation table 1015, and is displayed in the language specified for the confirmer by the second user. It is also possible to have a configuration in which the information is presented to the user.

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

Specifically, if the second user's approval authority information obtained in step S302 includes information that has the authority to approve the conclusion of the contract, the contract confirmation unit 1043 of the server 10 determines whether the second user has accepted the agreement. It is determined that the user is capable of approving the conclusion of the contract based on the contract information, a confirmation screen is presented to the second user, and the process proceeds to step S304.

On the other hand, if the second user is a user who cannot approve the conclusion of the contract based on the received contract information, the contract confirmation process ends.

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

In step S305, the contract confirmation unit 1043 of the server 10 receives an instruction from the second user to agree to and approve the conclusion of the contract based on the contract information received from the first user.
The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30, and when agreeing or consenting to the contents, operates the input device 306 of the second user terminal 30, etc. By pressing the consent button 740 displayed on the confirmation screen 70 for confirming the contract information, a request including the document ID, information identifying the second user, and input data for each input item input in step S305 is sent. The process of transmitting to the server 10 is executed. 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 specifying the second user, and stores a value of True in the confirmation flag field of the record. For example, if the information specifying the second user is an email address, the document ID and confirmer email address items in the confirmation table 1015 are searched, and a value of True is stored in the confirmation flag item of the record. If the information that identifies the second user is user identification information, the document ID and confirmation information in the confirmation table 1015 are determined based on the email address of the second user identified by searching the user ID item in the user table 1012. The user's email address field is searched, and a value of True is stored 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. Thereby, in step S305, the input data input by the second user is stored as input item information in the input item table 1016.

The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been executed by all confirmers having approval authority. Specifically, if a value of True is stored in the confirmation flag of the record of the confirmer who has approval authority in the confirmation table 1015, the contract confirmation unit 1043 of the server 10 performs the contract check by all confirmers who have approval authority. It is determined that the contract confirmation process has been executed. That is, the determination is made while ignoring the value of the confirmation flag of the record of a confirmer who does not have approval authority.
When the contract confirmation process is executed by all the confirmers having approval authority, the contract confirmation unit 1043 of the server 10 sends a message to the first user notifying that the contract confirmation process is completed. Note that, similarly, the contract confirmation unit 1043 of the server 10 may send a message to the second user notifying that the contract confirmation process has been completed.

Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the first user's email address to notify that the second user has completed confirmation of the contract information, using a communication means such as email. That is, 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 contract has been concluded with the second user.
The message to be notified to the first user may include information on a URL that is an endpoint that includes a document ID for specifying contract information.

FIG. 19 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 a message 81 and information of a URL 82 including a document ID for specifying contract information.

Similarly, the contract confirmation unit 1043 of the server 10 sends a message notifying that the second user has completed confirmation of the contract information, including a mention to the first user, using a chat service (not shown) or the like. You may do so. That is, 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 contract has been concluded with the second user.
The message to be notified to the first user may include information on a URL that is an endpoint that includes a document ID for specifying contract information.

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

If multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 informs the user other than the last user who executed the contract confirmation process that the contract confirmation process has been completed. You may also send a message to notify you. Thereby, the user corresponding to the confirmer can also receive a notification that execution of the contract confirmation process has been completed by all confirmers.
Further, the contract confirmation unit 1043 of the server 10 may send a message notifying that the contract confirmation process has been completed to a user who has authority equivalent to an administrator in a group to which a plurality of confirmers belong.
Note that the message may be sent via email, chat service, or the like.
Thereby, the administrator of the group to which the user who is the confirmer belongs can receive notification that execution of the contract confirmation process has been completed.

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 of the group table 1013 based on the acquired group ID item, acquires the administrator ID item, and, based on the administrator ID, identifies the person who corresponds to the administrator. An authorized user is identified by searching the user ID in the user table 1012, and a message is sent to notify that the contract confirmation process has been completed.

<Electronic signature processing>
Step S305 may include electronic signature processing. In response to the instruction to approve the contract conclusion received from the second user in step S305, the contract confirmation unit 1043 of the server 10 indicates, in the contract information received from the first user, that the contract conclusion of the contract information is approved. Add and store an electronic signature.
Specifically, the contract confirmation unit 1043 of the server 10 adds and stores an electronic signature to the contract information based on the received request. The contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID and acquires contract information.
The contract confirmation unit 1043 of the server 10 adds an electronic signature to the acquired contract information and stores it in the document data item of the document table 1014. Note that the contract confirmation unit 1043 of the server 10 may update (overwrite) items of document data with the contract information to which the electronic signature has been added, or may store the contract information before the electronic signature has been added in a separate storage device (not shown). I don't mind if you do.
The contract confirmation unit 1043 of the server 10 includes the document ID, the first user's email address, the second user's email address, approval date and time, confirmation date and time, authentication method of approval date and time, authentication method of confirmation date and time, and input items in the electronic signature. Any information such as the value of input data for each user, consent (approval) of the first user and second user, and a time stamp may be included.
As a result, the contract confirmation unit 1043 of the server 10 stores the contract information with an electronic signature indicating that the second user has approved the conclusion of the contract information. It is possible to prevent impersonation or falsification of contract information by a third party.

<Basic hardware configuration of the computer>
FIG. 20 is a block diagram showing the basic hardware configuration of the 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.

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

The main storage device 902 is for temporarily storing programs, data processed by the programs, and the like. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

The auxiliary storage device 903 is a storage device for storing data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, semiconductor memory, and the like.

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

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

<Basic functional configuration of computer 90>
The functional configuration of the computer realized by the basic hardware configuration of the computer 90 (FIG. 20) will be described. The computer includes at least functional units of a control section, a storage section, and a communication section.

Note that the functional units included in the computer 90 can also be implemented by distributing all or part of each functional unit to a plurality of computers 90 interconnected via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

The control unit is realized by the processor 901 reading various programs stored in the auxiliary storage device 903, loading them into the main storage device 902, and executing processing according to the programs. The control unit can implement a functional unit that performs various information processing depending on the type of program. Thereby, the computer is realized as an information processing device that performs information processing.

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. Further, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to the program. Further, the control unit can cause the processor 901 to execute processing for adding, updating, and deleting data stored in the storage unit according to various programs.

A database refers to a relational database, which is used to manage a data set called a master, which is a tabular table whose structure is defined by rows and columns, in relation to each other. In a database, a table is called a table or a master, a table column is called a column, and a table row is called a record. In a relational database, you can set and associate relationships between tables and masters.
Usually, each table and each master is set with a column that serves as a primary key to uniquely identify a record, but it is not essential to set a primary key on a column. The control unit can cause the processor 901 to add, delete, or update records to a specific table or master stored in the storage unit according to various programs.

Note that the database and master in the present disclosure may include any data structure (list, dictionary, associative array, object, etc.) in which information is structurally defined. Data structures include data that can be considered as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

The communication unit is realized by a 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 it to the control unit. The control unit can cause the processor 901 to execute information processing on the received information according to various programs. Further, the communication unit can transmit information output from the control unit to another computer 90.

<Additional notes>
The matters explained in each of the above embodiments are additionally described below.

(Additional note 1)
A program, comprising a processor and a storage unit, in which a computer executes electronic contract procedures between a plurality of users, wherein the processor receives contract information as a subject of contract conclusion from a first user; a contract reception step; (S101), a candidate acquisition step (S102) of acquiring one or more candidate information corresponding to one or more recipient candidates of the contract information received in the contract reception step by querying an external server; a candidate presentation step (S102) of presenting one or more candidate information acquired in the acquisition step to the first user; and one or more candidate information presented to the first user in the candidate presentation step based on the first user's selection operation. A program that executes a recipient reception step (S102) for accepting second identification information of a recipient of the contract information received in the contract reception step from candidate information of the contract information.
Thereby, in electronic contract procedures between a plurality of users, it is possible to more easily input information on the other party to conclude the contract.

(Additional note 2)
a notification step (S106) in which the processor notifies the second user identified by the second identification information received in the recipient reception step to request an approval operation for the contract information received in the contract reception step; The program described in Appendix 1 to be executed.
Thereby, in electronic contract procedures between a plurality of users, it is possible to more easily conclude a contract with the other party.

(Appendix 3)
In the candidate acquisition step (S102), among a plurality of candidate information related to the same user included in one or more candidate information acquired from an external server, candidate information with an older registration date and time in the external server is selected as one or more candidates. The program according to supplementary note 1, which is a step of excluding the information from the information and acquiring it as one or more candidate information.
Thereby, even if the candidate information acquired from the external server includes a plurality of candidate information for the same user, candidate information with the latest registration date and time can be acquired preferentially and presented to the user.

(Additional note 4)
The program according to supplementary note 1, wherein the candidate acquisition step (S102) includes a step of acquiring user attributes of one or more users specified by one or more candidate information by inquiring an external server.
Thereby, user attributes stored in an external business card management system can be used in electronic contract procedures between multiple users.

(Appendix 5)
The candidate acquisition step (S102) is a step of acquiring, as one or more candidate information, candidate information in which the user attribute of the user specified by the candidate information is included in a predetermined condition, from among the one or more acquired candidate information. The program according to appendix 4.
Thereby, by using user attributes stored in an external business card management system, it is possible to more safely conclude a contract with a counterparty that meets the conditions.

(Appendix 6)
The external server is a business card management system, and the candidate acquisition step (S102) is a step of acquiring candidate information in which the job title of the user specified by the candidate information is a predetermined number or more as one or more candidate information. Programs listed.
Thereby, by using user attributes stored in an external business card management system, it is possible to more safely conclude a contract with only those with a predetermined position or higher.

(Appendix 7)
The candidate acquisition step (S102) includes a step of acquiring one or more business negotiation information associated with one or more candidate information by inquiring an external CRM system, and the business negotiation information is specified by the candidate information. a contract editing step in which the processor edits the contract information received in the contract reception step, which is information regarding the user's customer or information regarding the business negotiation, and is associated with the second identification information received in the recipient reception step; The program according to supplementary note 1, which executes S103).
Thereby, business negotiation information stored in an external CRM system can be used in electronic contract procedures between a plurality of users.

(Appendix 8)
In the contract editing step (S103), information regarding at least one of the organization, address, position, and name of the user related to the second identification information, which is included in the negotiation information associated with the second identification information, is edited into a contract. The program according to appendix 7, which includes a step of adding information to the contract information received in the reception step.
Thereby, by using business negotiation information stored in an external CRM system, it is possible to conclude a contract more easily.

(Appendix 9)
An information processing device comprising a processor and a storage unit, wherein the processor executes a program according to any one of appendices 1 to 8.
Thereby, in electronic contract procedures between a plurality of users, it is possible to more easily input information on the other party to conclude the contract.

(Appendix 10)
An information processing system including an information processing device including a processor and a storage unit, wherein the processor executes a program according to any one of Supplementary Notes 1 to 8.
Thereby, in electronic contract procedures between a plurality of users, it is possible to more easily input information on the other party to conclude the contract.

(Appendix 11)
An information processing method executed by a computer including a processor and a storage unit, wherein the computer executes a program according to any one of appendices 1 to 8.
Thereby, in electronic contract procedures between a plurality of users, it is possible to more easily input information on the other party to conclude the contract.

1 system, 10 server, 101 storage unit, 104 control unit, 106 input device, 108 output device, 20 first user terminal, 201 storage unit, 204 control unit, 206 input device, 208 output device, 30 second user terminal, 301 storage unit, 304 control unit, 306 input device, 308 output device, 40 external server, 401 storage unit, 404 control unit, 406 input device, 408 output device

Claims (11)

A program, comprising a processor and a storage unit, for a computer to execute electronic contract procedures between multiple users,
The processor,
a contract reception step of receiving contract information subject to contract conclusion from the first user;
a candidate acquisition step of acquiring one or more candidate information corresponding to one or more recipient candidates of the contract information received in the contract reception step by making an inquiry to an external server;
a candidate presenting step of presenting the one or more candidate information acquired in the candidate acquiring step to the first user;
Based on the first user's selection operation, a second identification of the recipient of the contract information received in the contract acceptance step is selected from the one or more candidate information presented to the first user in the candidate presentation step. a receiver reception step for accepting information;
A program to run. The processor,
a notification step of notifying a second user identified by the second identification information received in the recipient reception step to request an approval operation for the contract information received in the contract reception step;
The program according to claim 1, which executes. In the candidate acquisition step, among the plurality of candidate information related to the same user included in the one or more candidate information acquired from the external server, the candidate information having an older registration date and time in the external server is selected as the first candidate information. or excluding it from a plurality of candidate information and acquiring it as the one or more candidate information,
The program according to claim 1. The candidate acquisition step includes a step of acquiring user attributes of one or more users specified by the one or more candidate information by inquiring the external server.
The program according to claim 1. The candidate acquisition step includes selecting, as the one or more candidate information, the candidate information in which the user attribute of the user specified by the candidate information is included in a predetermined condition, from among the one or more acquired candidate information. The step to obtain
The program according to claim 4. The external server is a business card management system,
The candidate acquisition step is a step of acquiring, as the one or more candidate information, the candidate information in which the job title of the user specified by the candidate information is equal to or higher than a predetermined value.
The program according to claim 5. The candidate acquisition step includes a step of acquiring one or more business negotiation information associated with the one or more candidate information by querying an external CRM system,
The business negotiation information is information regarding a customer of the user identified by the candidate information or information regarding a business negotiation,
The processor,
a contract editing step of editing the contract information received in the contract reception step based on the business negotiation information associated with the second identification information received in the recipient reception step;
execute,
The program according to claim 1. The contract editing step includes information regarding at least one of the organization, address, position, and name of the user associated with the second identification information, which is included in the business negotiation information associated with the second identification information. a step of adding information to the contract information received in the contract reception step;
The program according to claim 7. An information processing device comprising a processor and a storage unit,
The processor executes the program according to any one of claims 1 to 8.
Information processing device. An information processing system including an information processing device including a processor and a storage unit,
The processor executes the program according to any one of claims 1 to 8.
Information processing system. An information processing method executed by a computer comprising a processor and a storage unit,
The computer executes the program according to any one of claims 1 to 8.
Information processing method.