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

Description

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

With the development and spread of computer technology, documents that were previously written on paper 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.
Japanese Patent Laid-Open No. 2003-144222 discloses a data storage destination restriction device that can restrict data storage destinations for each user group within a company.
Patent Document 2 discloses an information processing system relating to digital contracts that includes a creator terminal, a verification company terminal, and a contract management server.

JP 2021-51345 A JP 2017-10096 A

In electronic contract systems that execute electronic contract procedures between the creator (sender) of information related to an electronic contract (contract information) and the verifier (receiver) of the contract information, it is often difficult to determine whether the other party user who is a party to the contract conclusion is a user with appropriate approval authority within the other party organization.
In addition, it was difficult to confirm whether the other party to the contract was trustworthy or whether they were involved in anti-social forces, crimes, scandals, etc.

A program having a processor and a storage unit for causing a computer to execute electronic contract procedures between users belonging to different organizations, the program causing the processor to execute the following steps: a contract acceptance step for accepting contract information to be the subject of a contract from a first user; a recipient acceptance step for accepting from the first user a second user as the recipient of the contract information accepted in the contract acceptance step; an approval step for accepting from the second user an instruction to approve the conclusion of the contract information from the second user accepted in the recipient acceptance step; an information acquisition step for acquiring, from at least one of the first user or the second user, user information about the other user from an external social networking service; and an information presentation step for presenting the other user information acquired in the information acquisition step to at least one of the users.

According to this disclosure, when executing electronic contract procedures, the parties to a contract can safely execute the contract procedures by taking into account the credit information of the other user.

1 is a diagram showing the overall configuration of an information processing system 1. FIG. 2 is a block diagram showing the functional configuration of the server 10. FIG. 2 is a block diagram showing the functional configuration of a first user terminal 20. FIG. 2 is a block diagram showing the functional configuration of a second user terminal 30. FIG. 2 is a block diagram showing the functional configuration of an SNS server 40. FIG. 10 is a diagram showing the data structure of a user table 1012. FIG. 10 is a diagram showing the data structure of a group table 1013. FIG. 10 is a diagram showing the data structure of a document table 1014. FIG. 10 is a diagram showing the data structure of a confirmation table 1015. FIG. 10 is a diagram showing the data structure of an input item table 1016. FIG. 10 is a diagram showing the data structure of an approval authority master 1017. FIG. 4 is a diagram showing the data structure of an SNS user table 4012. FIG. 4 is a diagram showing the data structure of an SNS group table 4013. 10 is a flowchart showing the operation of a contract creation process. 10 is a flowchart showing the operation of a contract confirmation process. 10 is a screen example showing the operation of a contract creation process. 10 is a screen example showing the operation of a contract creation process. 10 is a screen example showing the operation of a contract creation process. 10 is a screen example showing a message sent to the second user terminal 30. 10 is a screen example showing the operation of a contract confirmation process. 10 is a screen example showing the operation of a contract confirmation process. FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90.

Embodiments of the present disclosure will be described below with reference to the drawings. In all figures describing the embodiments, common components will be designated by 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 as described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each figure is a schematic diagram and is not necessarily a precise illustration.

<Configuration of System 1>
The system 1 in the present disclosure is an information processing system for realizing an electronic contract conclusion service between multiple users.
The system 1 includes information processing devices, namely, a server 10, a first user terminal 20, a second user terminal 30, and an SNS server 40, which are connected via a network N.
FIG. 1 is a diagram showing the overall configuration of an information processing 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.
FIG. 5 is a block diagram showing the functional configuration of the SNS server 40. As shown in FIG.

Each information processing device is composed of a computer equipped with an arithmetic unit and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by this hardware configuration will be described later. For each of the server 10, first user terminal 20, second user terminal 30, and SNS server 40, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer described below will be omitted.

<Configuration of Server 10>
The server 10 is an information processing device that provides an electronic contract conclusion service between multiple users.
The server 10 includes a storage unit 101 and a control unit 104 .

<Configuration of the storage unit 101 of the 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 an approval authority master 1017 .

User table 1012 is a table that stores and manages information about 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 user table 1012. This allows the user to use the service according to the present disclosure.
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, approval authority, and SNS user data.
FIG. 6 is a diagram showing the data structure of the user table 1012.

The user ID is an item for storing user identification information for identifying a user, and a unique value is set for each user in the user identification information.
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. A user may belong to multiple groups.
The approval authority is an item that stores authority information regarding the approval of a user. For a user who has the authority to approve the conclusion of a contract (approval authority), information indicating that the user has 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 indicating that the user does not have the authority to approve the conclusion of a contract, such as False, blank, or null value, is stored.
The system may be configured so that approval authority can be set depending on the contract information. For example, a system may be configured so that user A has approval authority for specific contract information A but does not have 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 for work, 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 for work.
Alternatively, the system may be configured to store multiple levels (levels, ranks) of authority information depending on the user's department, position, etc. For example, information such as C for temporary staff, B for regular 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 a confidentiality agreement) may be able to approve the conclusion of a contract depending on the contract type information, contract amount, etc. of the contract information.
The SNS user data is an item that stores information (SNS user information) about a user in a social networking service (SNS service) that uses the service according to the present disclosure.
The SNS user information includes the user's name, affiliation information, job title, work history, etc., which are stored in an SNS user table 5012 and an SNS group table 5013 described below for users who use the service according to the present disclosure.
The SNS user information may include information on the SNS service of the user who uses the service according to the present disclosure, as well as information such as the job titles and work histories of other users with whom the user is connected on the SNS service.
The SNS user information includes credit information, which is information indicating the user's trustworthiness in a transaction, including the user's affiliation information, job title, work history, etc. The credit information includes the job title, work history, and the job titles and work histories of other users connected to the user via the social networking service, as well as a credit score calculated based on the credit information of the other users.

The group table 1013 is a table that stores and manages 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 group ID, group name, and administrator ID.
FIG. 7 is a diagram showing the data structure of the group table 1013.

The group ID is an item for storing group identification information for identifying a group, and 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.

The document table 1014 is a table for storing and managing information (electronic contract information) relating to an electronic contract exchanged between a creator and a recipient.
The document table 1014 is a table having a 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. As shown in FIG.

The document ID is an item for storing document identification information for identifying electronic contract information. The document identification information is an item for which a unique value is set for each piece of electronic contract information.
The document data is an item that stores electronic contract information (binary or text data).
Creator ID: This is an item for storing user identification information for identifying the user who created the electronic contract information.

The confirmation table 1015 is a table that stores and manages information (checker information) including the email addresses of users who will be checkers of electronic contract information.
The confirmation table 1015 is a table having columns for document ID, confirmation order, confirmer email address, confirmation flag, date and time, 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 for storing document identification information of the electronic contract information to be verified by the verifying person.
The confirmation order is an item for storing information regarding the confirmation order when the electronic contract information is confirmed by the confirmer. The electronic contract information stored by the creator is circulated to the confirmers in the confirmation order and confirmed.
The checker email address is an item that stores the email address of the checker of the electronic contract information. The checker's email address does not need to be registered in advance as a user in order to use the services disclosed herein. In other words, the checker's email address does not need to be included in the user table 1012.
The confirmation flag is an item that stores confirmation identification information for identifying whether or not the confirming procedure for the electronic contract information has been completed by the confirming person. When the confirming person has completed the confirmation of the electronic contract information, information indicating that the confirmation has been completed, such as a value of True, is stored in the confirmation flag item.
The date and time is an item for storing the date and time when the verifying procedure for the electronic contract information was carried out by the verifying person. Specifically, the date and time when the verification identification information was stored in the verification flag item is stored.
The language data is an item for storing information (language information) related to the language of the verifyer.
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 checker performed the procedure for checking the contract information. Specifically, the date and time when the check identification information was stored in the check flag item is stored.

The input item table 1016 is a table that stores and manages information (input item information) related to input items 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 an input item.
The document ID is an item that stores 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 entered the 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 email address of the verifying person, 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 input items. The input rule can store input rule information related to the input rules of any input item, such as data types such as date, datetime, text, and integer, as well as the number of characters in the case of text, regular expressions for text, etc.
The date and time is an item for storing the date and time when the inputter inputs the input data into the input item.

The approval authority master 1017 is a table that stores rule information on approval authority for approving contract information in a group to which a user belongs.
The approval authority master 1017 is a table having columns for group ID, approval authority, and score threshold.
FIG. 11 is a diagram showing the data structure of the approval authority master 1017.

The group ID is an item for storing group identification information for identifying a group.
The approval authority is an item for storing authority information regarding the approval conclusion of a user. Authority information of multiple levels (levels, ranks) is stored according to the user's department, position, etc.
The score threshold is an item that stores the credit score threshold (score threshold) of a trading partner for which a contract can be approved for each user's approval authority. A user can proceed with the contract procedure with a trading partner only if the trading partner's credit score is higher than the score threshold specified by the user's approval authority.

<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 determination unit 1044. The control unit 104 executes an application program 1011 stored in the storage unit 101, thereby realizing each functional unit.

The user registration control unit 1041 performs processing to store information about users who wish to use the service according to the present disclosure in the user table 1012 .
The information stored in the user table 1012 is entered when a user opens a web page operated by a service provider from any information processing terminal, enters information into a predetermined input form, and sends 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 the user information in the user table 1012, the service provider may conduct 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 may be automatically set by the user registration control unit 1041.

<Configuration of First User Terminal 20>
The first user terminal 20 is an information processing device operated by a first user who uses a service. The first user terminal 20 may be, for example, a desktop personal computer (PC) 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 .

<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 .

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 services disclosed herein. The first user ID 2011 includes information such as a session ID temporarily assigned by the server 10 to identify the user using the first user terminal 20.

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

<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 the first user ID 2011 stored in the storage unit 201, thereby realizing each functional unit.

<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 keyboard 2065 .

<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 .

<Configuration of second user terminal 30>
The second user terminal 30 is an information processing device operated by a second user who uses the service. The second user terminal 30 may be, for example, a desktop personal computer (PC) 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 .

<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 .

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 user with the services disclosed herein. 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.

The application program 3012 may be pre-stored in the storage unit 301, or may be configured to be downloaded from a web server operated by the service provider via the communication IF. The application program 3012 includes an interpreter-type programming language such as JavaScript (registered trademark) that is executed on a web browser application stored on the second user terminal 30.

<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 the second user ID 3011 stored in the storage unit 301, thereby realizing each functional unit.

<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 .

<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 .

<Configuration of SNS Server 40>
The SNS server 40 is an information processing device that provides an SNS service.
The SNS service according to the present disclosure is preferably a business SNS, which stores and manages information such as the user's organization, position within the organization, work history, educational background, etc. A business SNS provides an SNS service that builds a social network between users who share mutual contact information, work history, educational background, etc., and enables mutual business communication.
The SNS service disclosed herein allows users to register their business cards on the SNS server 40, thereby enabling them to store and manage information such as their affiliated organization, position within the organization, work history, contact information, etc. on the SNS server 40 without the need for complicated registration procedures.
The SNS server 40 includes a storage unit 401 and a control unit 404 .

<Configuration of the storage unit 401 of the SNS server 40>
The storage unit 401 of the SNS server 40 includes an application program 4011 , an SNS user table 4012 , and an SNS group table 4013 .

The SNS user table 4012 is a table that stores and manages information about member users (hereinafter, "users") who use the SNS service. When a user registers to use the service, the user's information is stored in a new record in the SNS user table 4012. This allows the user to use the SNS service according to the present disclosure. In the SNS service according to the present disclosure, a user can read their own business card with an optical reading device such as a scanner, and store information such as the name and affiliation information written on the business card as user information.
The SNS user table 4012 is a table having the SNS user ID as a primary key and columns of SNS user ID, SNS user name, SNS email address, SNS group ID, work history data, and educational history data.
FIG. 12 is a diagram showing the data structure of the SNS user table 4012.

The SNS user ID is an item for storing user identification information for identifying a user who uses the SNS service. The user identification information is an item for which a unique value is set for each user.
The SNS user name is an item for storing the name of a user who uses the SNS service. The user name may be set to any character string such as a nickname instead of a name.
The SNS email address is an item for storing the email address of a user who uses an SNS service.
The SNS group ID is an item for storing group identification information of a group to which a user who uses an SNS service belongs. A user may belong to multiple groups.
The work history data is an item that stores information (work history information) about the current job and past work history of a user who uses an SNS service. The work history data stores information about the user's past work history, such as the organization to which the user belongs (corporation, company, club, organization, department within a company), the user's position, length of employment, and awards received.
The educational background data is an item that stores information (educational background information) about the current employment and past educational background of a user who uses an SNS service. The educational background data stores information about the user's past employment history, such as the school the user attended, the school they graduated from, their period of attendance, and any awards they have received.

The SNS group table 4013 is a table that stores and manages information (group information) about groups to which users of the SNS service belong. 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 SNS group table 4013 is a table having the SNS group ID as a primary key and columns of the SNS group ID, the SNS group name, and the SNS administrator ID.
FIG. 13 is a diagram showing the data structure of the SNS group table 4013.

The SNS group ID is an item for storing group identification information for identifying a group that uses the SNS service. The group identification information is an item for storing a unique value for each group.
The SNS group name is an item for storing the name of a group that uses the SNS service. Any character string can be set as the group name.
The SNS administrator ID is an item that stores user identification information of a user with administrator privileges in a group that uses the SNS service. A user with administrator privileges can arbitrarily define and set users who have a certain level of status or authority or higher in a group such as an organization.

<Configuration of the control unit 404 of the SNS server 40>
The control unit 404 of the SNS server 40 includes an SNS user registration control unit 4041. The control unit 404 executes an application program 4011 stored in the storage unit 401, thereby realizing each functional unit.

The SNS user registration control unit 4041 performs processing to store information about users who wish to use the SNS service according to the present disclosure in the SNS user table 4012 .
The information stored in SNS user table 4012 is generated when a user using an SNS service opens a webpage operated by the service provider from any information processing terminal, enters information into a predetermined input form, and transmits the information to SNS server 40. SNS user registration control unit 4041 stores the received information in a new record in SNS user table 4012, completing user registration. This allows the user stored in SNS user table 4012 to use the service.
Before the SNS user registration control unit 4041 registers user information in the SNS user table 4012, the SNS service provider may conduct a predetermined examination and restrict whether or not the user is permitted to use the SNS service.
The SNS 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 SNS user registration control unit 4041.

<Operation of Information Processing System 1>
Each process of the information processing system 1 will be described below.
FIG. 14 is a flowchart showing the operation of the contract creation process.
FIG. 15 is a flowchart showing the operation of the contract confirmation process.
FIG. 16 is an example of a screen showing the operation of the contract creation process.
FIG. 17 shows an example of a screen showing the operation of the contract creation process.
FIG. 18 is an example of a screen showing the operation of the contract creation process.
FIG. 19 is an example of a screen showing a message sent to the second user terminal 30. In FIG.
FIG. 20 is an example of a screen showing the operation of the contract confirmation process.
FIG. 21 is an example of a screen showing the operation of the contract confirmation process.

<Contract creation process>
The contract creation process is a process in which a creator creates contract information and sends it to a verifyer. In the present disclosure, a first user is a user who creates the contract information, and a second user is a user who checks the contract information. Note that when creating contract information, multiple users can be set as checkers.
In the present disclosure, a first user is a user who belongs to a group, such as an organization or company, that is different from that of a second user.

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

<Outline of contract creation process>
The contract creation process involves the creator creating contract information, setting a verifying party to whom the contract information will be sent, obtaining the SNS user information of the verified party in the social networking service and presenting it to the creator, and determining whether the contract procedure can be completed based on the SNS user information. If it is determined that the contract procedure cannot be completed, a first announcement message is displayed. If it is determined that the contract procedure can be completed, this is a series of processes that sets input fields for the contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, and sends the contract information to the verifying party.

<Details of contract creation process>
In step S101, the contract creation unit 1042 of the server 10 executes a contract acceptance step of accepting contract information to be the subject of a contract conclusion from the first user.
Specifically, the first user operates the input device 206 of the first user terminal 20 to create contract information including document data related to the contract. The document data can be in any data format, such as Portable Document Format (PDF), Word, or Extensible Markup Language (XML), and the contract information can include such document data.
The first user operates the input device 206 of the first user terminal 20 to send 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 fields of a new record in the document table 1014. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the document table 1014.

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

In step S102, the contract creation unit 1042 of the server 10 executes a receiver reception step of receiving from the first user the second user as a confirmer (receiver) of the contract information received in the contract reception step. In the present disclosure, it is assumed that the first user selects and specifies the second user as the receiver.
Specifically, the first user operates the input device 206 of the first user terminal 20 to input the email address and user name of the second user who will be the checker, and transmits them to the server 10 .

In step S102, the contract creation unit 1042 of the server 10 may execute a candidate acquisition step of acquiring user candidates from a social networking service. In a recipient acceptance step, a step of accepting a second user as a recipient of the contract information from the user candidates acquired in the candidate acquisition step is executed.
Specifically, the first user operates the input device 206 of the first user terminal 20 to send a request to inquire about user candidates to the server 10. The request sent to the server 10 may include information about the organization to which the contract information is concluded.

When the contract creation unit 1042 of the server 10 receives the request, it sends a request to the SNS server 40 to inquire about user candidates. When the control unit 406 of the SNS server 40 receives the request, it searches the SNS user table 4012, the SNS group table 4013, etc., and sends a response including the user candidate's SNS user ID, SNS username, and SNS email address to the server 10. For example, the control unit 406 of the SNS server 40 may determine as user candidates users who are connected to the first user. The control unit 406 of the SNS server 40 may determine as user candidates users who are connected to the first user and who belong to the organization to which the contracting party belongs. The control unit 406 of the SNS server 40 may determine as user candidates users who are connected to the first user and who belong to the organization to which the contracting party belongs and who have the authority to approve the conclusion of the contract for the target contract information. The control unit 406 of the SNS server 40 may select as user candidates users who are connected to the first user, belong to the organization to which the contracting party belongs, and hold a predetermined position or higher.

The contract creation unit 1042 of the server 10 identifies and acquires the user name and email address of the user candidate from the user table 1012 based on the SNS user ID, SNS user name, and SNS email address included in the received response. Note that the contract creation unit 1042 of the server 10 may search the email address field in the user table 1012 based on the SNS email address to acquire the user ID and username. Alternatively, the contract creation unit 1042 of the server 10 may identify a user ID corresponding to the SNS user ID, taking into consideration information such as the organization to which the user belongs and their job title, and identify and acquire the email address and username of the user candidate from the user table 1012.
The contract creation unit 1042 of the server 10 transmits the acquired user names and email addresses of the candidate users to the first user terminal 20. The display 2081 of the first user terminal 20 presents the received user names and email addresses of the user candidates to the first user. The first user operates the input device 206 of the first user terminal 20 or the like to select a second user who will be the confirmer from the presented multiple user candidates, and transmits the second user's username, email address, etc. to the server 10.

This allows the first user, when designating a second user as a reviewer, to select a second user with appropriate approval authority as the reviewer based on user candidates obtained from the social networking service.

In step S102, the contract creation unit 1042 of the server 10 may execute a candidate acquisition step of acquiring, from the social networking service, user candidates who have approval authority for the contract information in a group to which the second user belongs, based on the second user. A recipient acceptance step executes a step of accepting a third user as a recipient of the contract information from the user candidates acquired in the candidate acquisition step.
Specifically, the first user operates the input device 206 of the first user terminal 20 to send a request to the server 10 to inquire about user candidates. The request sent to the server 10 includes information about the second user, such as the user identification information and email address of the second user with whom the contract information is concluded. In other words, it is assumed that at this time, the first user has already added the second user as a checker.

When the contract creation unit 1042 of the server 10 receives the request, it sends a request to the SNS server 40 to inquire about user candidates. When the control unit 406 of the SNS server 40 receives the request, it searches the SNS user table 4012, SNS group table 4013, etc. based on the information about the second user, and sends a response to the server 10 including the user candidate's SNS user ID, SNS username, and SNS email address. For example, the control unit 406 of the SNS server 40 may determine as user candidates users who belong to the same organization as the second user. The control unit 406 of the SNS server 40 may determine as user candidates users who belong to the same organization as the second user and have the authority to approve the conclusion of a contract for the target contract information. For example, the control unit 406 of the SNS server 40 may refer to the work history data in the SNS user table 4012 and other data from users who belong to the same organization as the second user and hold a predetermined position or higher and determine these users as user candidates.

The contract creation unit 1042 of the server 10 identifies and acquires the user name and email address of the user candidate from the user table 1012 based on the SNS user ID, SNS user name, and SNS email address included in the received response. Note that the contract creation unit 1042 of the server 10 may also search the email address field in the user table 1012 based on the SNS email address to acquire the user ID and username. Alternatively, the contract creation unit 1042 of the server 10 may identify a user ID corresponding to the SNS user ID, taking into consideration information such as the organization to which the user belongs and their job title, and identify and acquire the email address and username of the user candidate from the user table 1012.
The contract creation unit 1042 of the server 10 transmits the acquired user names and email addresses of the candidate users to the first user terminal 20. The display 2081 of the first user terminal 20 presents the received user names and email addresses of the user candidates to the first user. The first user operates the input device 206 of the first user terminal 20 or the like to select a third user who will be the confirmer from the presented multiple user candidates, and transmits the third user's username, email address, etc. to the server 10.

This allows the first user to include a third user with appropriate approval authority as a confirmer of the contract information in the circulation destinations based on the second user who has already been accepted and the potential users who have approval authority for the contract information in the group to which the second user belongs from the social networking service.

In step S103, the contract creation unit 1042 of the server 10 executes an information acquisition step of acquiring user information of the second user from an external social networking service for the first user. The same applies to the third user.
Specifically, the information acquisition step executes a step of acquiring the second user's credit information from an external social networking service. Upon receiving the second user's email address and username, the contract creation unit 1042 of the server 10 transmits a request to the SNS server 40 to inquire about the second user's SNS user information, including the second user's email address and username. The request may also include information such as the organization to which the second user belongs.
Based on the email address, username, etc. included in the received request, the SNS server 40 searches the SNS user table 4012 for items such as the SNS email address and SNS username, and acquires the SNS user information of the second user, including profile information such as the second user's name, organization, and job title. The SNS user information of the second user may also include information such as the second user's credit information and credit score. The control unit 406 of the SNS server 40 transmits the acquired SNS user information to the server 10.
The contract creation unit 1042 of the server 10 stores the received SNS user information in the SNS user data field of the record of the second user in the user table 1012. As a result, the SNS user information regarding the second user is stored in the user table 1012 of the server 10 in association with the user identification information of the second user.

The contract creation unit 1042 of the server 10 sends the SNS user information of the second user to the first user terminal 20. The display 2081 of the first user terminal 20 presents the received SNS user information to the first user.

17 is an example of an addition screen 55 for adding a verifying person (recipient) of contract information in the contract creation process. The addition screen 55 for adding a verifying person, which is displayed on the display 2081 of the first user terminal 20, displays an input field for the verifying person's email address 551, name 552, organization name 553, and access code 554. The SNS information display area 561 displays SNS user information of the user designated as the verifying person. The SNS user information displays the organization to which the user designated as the verifying person belongs in the SNS service, a credit score 5612, credit information 5613, a cancel button 571, and an add button 572.
Specifically, the contract creation unit 1042 of the server 10 displays the received SNS email address, SNS username, and SNS user information in the email address 551, name 552, and SNS information display area 561 items on the addition screen 55, respectively.

The information obtaining step includes a step in which the second user obtains user information including information regarding the frequency of updates to the user's name and affiliation information by reading the user's business card in the social networking service.
Specifically, the SNS information may include information regarding the frequency of updates to the second user's SNS user information, such as the second user's name, organization, and job title, by the second user scanning the second user's business card on a social networking service.
This allows the parties to a contract to carry out electronic contract procedures more safely by taking into account the credit information of the other user based on the other user's activity status on the social networking service.
Then, the contract creation unit 1042 of the server 10 may present the acquired information regarding the update frequency of the SNS user information of the second user to the first user.

In step S104, the contract determination unit 1044 of the server 10 executes a determination step of determining whether or not to proceed with the contract with the second user based on the credit information of the second user acquired in the information acquisition step. The determination step executes a step of determining whether or not to proceed with the contract with the second user based on the approval authority information of the first user and the credit information of the second user.
The determination step is a step of determining whether or not to proceed with the contract procedure with the second user by comparing a score threshold according to the approval authority information of the first user with the credit score of the second user. The same applies to the third user.

Specifically, the determination step executes a step of determining whether or not to proceed with the contract procedure with the second user based on the second user's credit information acquired in the information acquisition step.

Specifically, the contract determination unit 1044 of the server 10 determines that the contract procedure cannot be carried out if the second user's work history, etc., included in the second user's SNS user information, shows that the second user has worked for inappropriate companies, etc. In addition, the contract determination unit 1044 of the server 10 may determine whether or not to carry out the contract procedure with the second user based on any information included in the SNS user information, including user information of other users who are connected to the second user on the social networking service.

Specifically, the contract determination unit 1044 of the server 10 searches the approval authority item in the approval authority master 1017 and acquires the score threshold based on the approval authority information of the first user stored in the user table 1012. The contract determination unit 1044 of the server 10 compares the credit score of the second user with the acquired score threshold, and determines that the contract procedure with the second user can be carried out if the credit score of the second user is greater than the score threshold, and determines that the contract procedure with the second user cannot be carried out if the credit score of the second user is equal to or less than the score threshold.
In the present disclosure, a user with approval authority rank S has a score threshold of 0, and therefore can enter into contract procedures with all users regardless of the credit score of the second user.

Then, in the receiver accepting step, if it is determined in the determining step that the contract procedure cannot be carried out with the second user, the second user is not accepted as a receiver of the contract information.
Specifically, if the contract determination unit 1044 of the server 10 determines that the contract procedure cannot be carried out with the second user, the first user cannot add the second user as a checker, and the process proceeds to step S109. In other words, the contract creation unit 1042 of the server 10 does not store the second user as a checker in the confirmation table 1015.

On the other hand, if the contract determination unit 1044 of the server 10 determines that the contract procedure with the second user can be carried out, the process proceeds to step S105, where the contract procedure can be carried out. Specifically, the contract creation unit 1042 of the server 10 stores the email address received in step S102 and the document ID of the contract information created and stored in step S101 in the checker email address and document ID fields of the confirmation table 1015, respectively, and associates the contract information with the email address of the second user and stores them. 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 the confirmation table 1015. In steps S102 to S104, 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 for 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 below. Note that setting the circulation order is not essential.

In step S109, if it is determined in the determination step that the contract procedure cannot be completed with the second user, the contract determination unit 1044 of the server 10 executes a first presentation step in which it presents a first guidance message to the first user to complete the contract procedure with the second user.

18 shows an example of an addition screen 55 for adding a confirmer (receiver) of the contract information when it is determined that the contract procedure cannot be carried out with the second user during the contract creation process. Explanation of the configuration that overlaps with that of FIG. 17 will be omitted.
The addition screen 55 for adding a reviewer, which is displayed on the display 2081 of the first user terminal 20, displays a type-1 guide notification 5614. The type-1 guide notification 5614 includes information indicating that the first user's approval authority does not allow the second user to proceed with the contract conclusion as a reviewer. The type-1 guide notification 5614 may also include a display informing users of other users who are able to proceed with the contract conclusion with the second user as a reviewer, or users who belong to other groups, such as other departments. This allows the first user to request the contract creation process from other users who are able to proceed with the contract conclusion with the second user as a reviewer.
Furthermore, the Add button 572 is presented to the first user in an unselectable state on the addition screen 55. In other words, the first user cannot add the second user as a checker.
The type-1 guide notification 5614 may simply be presented to the first user as a warning or alert on the addition screen 55, and the Add button 572 may remain selectable. In this case, the first user can add the second user as a checker, taking into consideration the content of the type-1 guide notification 5614 warning or alert.

In step S105, 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 to set multiple input items for the contract information created and stored in step S101. The input items can be any input items 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.

In step S106, 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, etc., to specify input rules for each input item information set in step S105 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 for each input item information in the input item table 1016. This makes it possible to set input rules for each input item.

In step S107, the contract creation 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 S106. For example, the first user may input input data for a number used to manage contract information, such as a serial number for the group to which the first user belongs, into an input item for which a management number is set. The first user may input input data for the contract conclusion date of the contract information into an input item for which a contract conclusion date is set. After completing input of 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 in the input item table 1016 identified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

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 based on 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 creation screen 50 for creating contract information, thereby sending a request to send the contract information to the server 10.

In step S108, the contract creation unit 1042 of the server 10 sends 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 in the confirmation table 1015 and identifies the 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, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the email address of the first confirmation user via a communication means such as email notifying that a request to confirm the contract information has been sent from the first user.
The message sent to the first confirmation user includes a URL (Uniform Resource Locator) containing a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a string obtained by optionally encrypting the document ID, or a string that can identify the document ID by referencing a table (not shown). The URL may also include information for identifying the first confirmation user. For example, if the first confirmation user is not registered as a user with the service disclosed herein, the URL must include information for identifying the first confirmation user.

If the first user sets an access code for the second user, the first user will separately communicate the access code to the first confirmation user by email or other means. This means that even if a third party obtains the message notified to the first confirmation user, the third party will not be able to perform the contract confirmation process unless they obtain the access code.

Figure 19 is an example screen showing a message sent 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 a URL 62 containing a document ID for identifying the contract information.

<Modification>
The first user can select and set multiple checkers by performing steps S102 to S104 for each of the multiple checkers. When selecting and setting multiple checkers, different input field information may be set independently for each of the multiple checkers in step S105. For example, if the first user sets two users, a second user and a ninth user, as checkers, the first user may set the input fields for the contract start date and contract end date for the second user and the input field for the contract conclusion date for the ninth user. In this case, in the contract confirmation process described below, the second user can enter input data for the contract start date and contract end date input fields, but cannot enter input data for the contract conclusion date input field. On the other hand, the ninth user cannot enter input data for the contract start date and contract end date input fields, but can enter input data for the contract conclusion date input field. Multiple checkers may be selected and set for the same input field information.

Input fields 532, 533, and 534 are drawn as drawing objects on the creation screen 50 for creating contract information. Input fields 532 and 533 are drawn with the user identification information "USER-B" of the user who has selected and set up input for the input field as the assignment, and the item "Text" as the input field type. Input field 534 for stamping is drawn with the user identification information "USER-C" of the user who has selected and set up input for the seal as the assignment, and the item "Stamp" as the input field type.

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

<Outline of contract confirmation process>
The contract confirmation process accepts access from the confirmer, presents the confirmer with a confirmation screen displaying the contract information, acquires and presents SNS user information on the social networking service of the creator of the contract information, and determines whether the contract procedure can be completed based on the SNS user information. If it is determined that the contract procedure cannot be completed, a type-2 guide message is presented. If it is determined that the contract procedure can be completed, input data for the input fields is accepted from the confirmer, and data related to confirmation of the contract information is accepted from the confirmer.

<Details of contract confirmation process>
In step S301, the second user who will be the confirmer operates the input device 306 of the second user terminal 30 to select the URL described in the received message, 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 a request to the server 10 to execute the contract confirmation process.

If an access code item is stored in the second user's record 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 second user's record in confirmation table 1015, thereby performing authentication processing for the second user.
Specifically, the server 10 sends an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30 to input the access code and send 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 second user's record 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.

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 obtains 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 obtains the verifying party 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 the 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 obtains the second user's approval authority information. The second user may be identified based on the second user ID 3011 included in the request received from the second user terminal 30, or based on identification information for identifying the second user included in the URL. If the second user is not registered with the service disclosed herein, the second user must be identified 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 field in the user table 1012 based on the user identification information of the identified second user, and acquires the approval authority field of the second user. Note that in the present disclosure, the approval authority of the second user is configured to be stored in the user table 1012, but the approval authority of the second user may be stored for each group to which the second user belongs, or for each contract information or for each contract information type. The contract confirmation unit 1043 of the server 10 acquires the approval authority information of the second user for the target contract information.
Furthermore, if the second user is not registered as a user for the service according to the present disclosure, the second user may be regarded as a user without approval authority and processing may be executed.

In step S303, 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 the 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.

In step S304, the contract creation unit 1042 of the server 10 executes an information acquisition step of acquiring user information of the first user from an external social networking service for the second user.
Specifically, the information obtaining step includes a step of obtaining the first user's credit information from an external social networking service.
Note that the information acquisition step is the same process as the information acquisition step in step S103 of the contract creation process, except that the user from which information is acquired is the first user rather than the second user, so duplicate explanations will be omitted.

Figure 20 is an example of a confirmation screen showing the operation of the contract confirmation process. The 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 indicating the current creation status of the contract information, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, an agree button 740, and an SNS information display area 761. The SNS information display area 761 displays the creator's SNS user information. The SNS user information displays the creator's affiliation in the SNS service, credit score 7612, and credit information 7613.

In step S305, the contract confirmation unit 1043 of the server 10 executes a determination step of determining whether or not to proceed with the contract with the first user based on the credit information of the second user acquired in the information acquisition step. The determination step executes a step of determining whether or not to proceed with the contract with the first user based on the approval authority information of the second user and the credit information of the first user.
Note that the determination step is the same process as the determination step in step S104 of the contract creation process, except that the user from which information is obtained is the first user instead of the second user, and the approval authority information of the second user is used instead of the approval authority information of the first user, so duplicate explanations will be omitted.

Specifically, the contract determination unit 1044 of the server 10 searches the approval authority item in the approval authority master 1017 based on the approval authority information of the second user stored in the user table 1012, and obtains the score threshold. The contract determination unit 1044 of the server 10 compares the credit score of the first user with the obtained score threshold, and determines that the contract procedure with the first user can be carried out if the credit score of the first user is greater than the score threshold, and determines that the contract procedure with the first user cannot be carried out if the credit score is equal to or less than the score threshold.

Then, in the approval step, if it is determined in the determination step that the contract procedure cannot be carried out with the first user, an instruction to approve the conclusion of the contract in the contract information is not accepted.
Specifically, if the contract determination unit 1044 of the server 10 determines that the contract procedure cannot be carried out with the first user, the second user cannot approve the contract information, and the process proceeds to step S308.

In step S308, if it is determined in the determination step that the contract procedure cannot be completed with the first user, the contract confirmation unit 1043 of the server 10 executes a second presentation step in which a second guidance message is presented to the second user to enable the second user to complete the contract procedure with the first user.

21 shows an example of a confirmation screen 70 that accepts an operation to approve the contract information when it is determined in the contract confirmation process that the contract procedure cannot be carried out with the first user. Explanation of the configuration that overlaps with that of FIG. 20 will be omitted.
The confirmation screen 70, which is displayed on the display 3081 of the second user terminal 30 and accepts an operation to approve the contract information, displays a type-2 guide message 7614. The type-2 guide message 7614 includes information indicating that the second user's approval authority does not allow them to approve the contract information created by the first user. The type-2 guide message 7614 may also include a display informing other users who can approve the contract conclusion with the first user as the creator, or users who belong to a group such as another department. This allows the second user to request the contract procedure from other users who can proceed with the contract conclusion with the first user as the creator. For example, the second user may be configured to transfer the contract information to a fourth user who belongs to the same group or organization and who can proceed with the contract conclusion with the first user as the creator. In this case, the fourth user who receives the transferred contract information can approve the contract information created by the first user.
Furthermore, the confirmation screen 70 is presented to the second user with the Agree button 740 in a non-selectable state, meaning that the second user cannot approve the conclusion of the contract with the first user as the creator.
Alternatively, the type-2 guide notification 7614 may simply be presented to the second user as a warning or alert on the confirmation screen 70, with the consent button 740 remaining selectable. In this case, the second user can approve the conclusion of the contract with the first user as the creator, taking into consideration the content of the type-2 guide notification 7614 warning or alert.

In step S306, 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 or the like to input data into the input items 732, 733, 734, and 735 set in the contract information. In the present disclosure, input by the second user into the input item 736 is not assigned, and therefore, it is visually displayed that the second user cannot input input data into the input item 736.

In step S307, the contract confirmation unit 1043 of the server 10 executes an approval step of accepting an instruction to agree to and approve the conclusion of the contract of the contract information from the second user accepted in the recipient acceptance step.
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 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 S306 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 corresponding 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 corresponding 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 corresponding 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 identified by the input item ID associated with the input data. As a result, in step S306, the input data entered 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 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 the 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 executed by all the confirmers, the contract confirmation unit 1043 of the server 10 sends a message to the first user notifying that the contract confirmation process has been completed.
Specifically, the contract creation unit 1042 of the server 10 sends a message to the first user's email address by a communication means such as email notifying the first user that the second user has completed confirmation of the contract information. In other words, the message notifies the first user 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 including a document ID for identifying the contract information.
When multiple users are set as checkers, the contract confirmation unit 1043 of the server 10 may send a message notifying the checkers other than the user who last executed the contract confirmation process that the contract confirmation process has been completed. This allows the checkers to receive notification that the contract confirmation process has been completed by all checkers.
The contract confirmation unit 1043 of the server 10 may also send a message notifying a user with authority equivalent to that of an administrator in a group to which multiple confirmers belong that the contract confirmation process has been completed. This allows the administrator in the group to which the confirmer belongs to be notified that the contract confirmation process has been completed. The contract confirmation unit 1043 of the server 10 acquires the group ID field by searching the user ID or email address field in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 then searches the group ID field in the group table 1013 based on the acquired group ID field, acquires the administrator ID field, and identifies a user with authority equivalent to that of an administrator by searching the user ID in the user table 1012 based on the administrator ID, and sends a message notifying that the contract confirmation process has been completed.

<Electronic signature processing>
An electronic signature process may be included in step S307. In response to the instruction to approve the conclusion of the contract received from the second user in step S307, the contract confirmation unit 1043 of the server 10 affixes an electronic signature to the contract information received from the first user, indicating that the conclusion of the contract information has been approved, and stores the contract information.
Specifically, the contract confirmation unit 1043 of the server 10 adds 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 in the document table 1014 based on the document ID, and acquires the contract information.
The contract confirmation unit 1043 of the server 10 affixes 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) the document data item with the contract information affixed with the electronic signature, or may store the contract information before affixing the electronic signature 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 for the approval date and time, authentication method for the confirmation date and time, input data value 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 adds a digital signature to the contract information indicating that the second user has approved the conclusion of 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.

<Basic computer hardware configuration>
22 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), which are electrically connected to one another by a communication bus 921.

The processor 901 is hardware that executes a set of instructions written in a program. The processor 901 is composed of an arithmetic unit, registers, peripheral circuits, etc.

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

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

The communication IF 991 is an interface for inputting and outputting signals for communicating with other computers via a network using wired or wireless communication standards.
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, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks (e.g., Wi-Fi (registered trademark)) that can connect to the Internet via a predetermined access point. In the case of a wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), and Bluetooth (registered trademark). In the case of a wired connection, the network also includes a network that is directly connected using a USB (Universal Serial Bus) cable, etc.

In addition, computers 90 can be virtually realized by distributing all or part of each hardware configuration across multiple computers 90 and connecting them via a network. In this way, the concept of computer 90 includes not only computers 90 housed in a single housing or case, but also virtualized computer systems.

<Basic Functional Configuration of Computer 90>
The following describes the functional configuration of a computer realized by the basic hardware configuration (FIG. 22) of the computer 90. The computer includes at least the functional units of a control unit, a storage unit, and a communication unit.

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

The control unit is realized when the processor 901 reads various programs stored in the auxiliary storage device 903, expands them into the main storage device 902, and executes processing in accordance with the programs. The control unit can realize functional units that perform various types of information processing depending on the type of program. In this way, 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. The processor 901 can also allocate a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with the programs. The control unit can also cause the processor 901 to add, update, and delete data stored in the storage unit in accordance with the various programs.

A database refers to a relational database, which manages data sets called masters and tables in a tabular format structurally defined by rows and columns, by relating them to each other. In a database, a table is called a table, a 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.
Typically, 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 specific tables and masters stored in the storage unit according to various programs.

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

The communication unit is realized by the communication IF 991. The communication unit realizes the function of communicating with other computers 90 via a network. The communication unit can receive information sent 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 in accordance with various programs. The communication unit can also transmit information output from the control unit to other computers 90.

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

(Appendix 1)
A program having a processor and a memory unit, for causing a computer to execute electronic contract procedures between users belonging to different organizations, the program causing the processor to execute the following steps: a contract acceptance step (S101) of accepting contract information to be the subject of a contract from a first user; a recipient acceptance step (S102) of accepting from the first user a second user as a recipient of the contract information accepted in the contract acceptance step; an approval step (S307) of accepting an instruction from the second user accepted in the recipient acceptance step to approve the conclusion of the contract for the contract information; information acquisition steps (S103, S304) of acquiring, from at least one of the first user or the second user, user information of the other user from an external social networking service; and an information presentation step (S103, S304) of presenting the other user information acquired in the information acquisition step to at least one of the users.
This allows the parties to a contract to take into consideration the information of the other user when carrying out electronic contract procedures and carry out the contract procedures with peace of mind.

(Appendix 3)
The program according to claim 1 or 2, wherein the information acquisition step (S103, S304) is a step of acquiring user information including the credit information of the other user.
This allows the parties to conclude a contract to safely carry out the contract procedures by taking into consideration the credit information of the other user when carrying out electronic contract procedures.

(Appendix 4)
The program according to any one of appendices 1 to 3, wherein the information acquisition step (S103, S304) is a step of acquiring user information including the credit score of the other user.
This allows the parties to a contract to safely carry out the contract procedures by taking into account the credit score of the other user when carrying out electronic contract procedures.

(Appendix 5)
The information acquisition step (S103, S304) is a step of acquiring user information including the other user's job title, work history, and the job titles and work history of other users connected to the other user via a social networking service, as well as the other user's credit score calculated based on the other user's credit information, a program described in any of Appendices 1 to 4.
This allows the parties to a contract to safely carry out the contract procedures by taking into account the credit score of the other user when carrying out electronic contract procedures.

(Appendix 6)
A program described in any of Appendices 1 to 5, wherein the social networking service is a service that builds a social network among multiple users based on the user's name and affiliation information written on the business card by reading the user's business card, and the information acquisition step (S103, S304) is a step of acquiring user information including the other user's name and affiliation information.
This allows the parties to conclude a contract to carry out the contract procedures more safely by taking into consideration the highly reliable credit information based on the business card information of the other user when carrying out electronic contract procedures.

(Appendix 7)
The program described in Appendix 6, wherein the information acquisition steps (S103, S304) are steps in which the other user acquires user information including information regarding the frequency of updates to the user's name and affiliation information by reading the user's business card in a social networking service.
This allows the parties to a contract to carry out electronic contract procedures more safely by taking into account the credit information of the other user based on the other user's activity status on the social networking service.

(Appendix 8)
A program described in any of Appendices 1 to 7, wherein the program causes a processor to execute a candidate acquisition step (S102) of acquiring user candidates from a social networking service, and a recipient acceptance step (S102) of accepting a second user as a recipient of contract information from the user candidates acquired in the candidate acquisition step.
This allows the first user, when designating the second user as the reviewer, to select the second user as the reviewer who has appropriate approval authority based on user candidates obtained from the social networking service.

(Appendix 9)
The program causes a processor to execute a candidate acquisition step (S102) of acquiring user candidates who have approval authority for contract information in a group to which the second user belongs from a social networking service based on the second user, and a recipient acceptance step (S102) of accepting a third user as a recipient of the contract information from the user candidates acquired in the candidate acquisition step, a program described in any of Appendices 1 to 8.
This allows the first user to include a third user with appropriate approval authority as a confirmer of the contract information in the circulation list based on the second user who has already been accepted and based on potential users who have approval authority for the contract information in the group to which the second user belongs from the social networking service.

(Appendix 10)
A program described in any of Appendices 1 to 9, which causes a processor to execute a judgment step (S104, S305) of determining whether or not to proceed with the contract with the other user based on the other user's credit information acquired in the information acquisition step.
This allows the parties to a contract to suspend the contract procedure based on the credit information of the other user when executing an electronic contract procedure, allowing users to avoid entering into a contract with a less secure party.

(Appendix 11)
The program according to appendix 10, wherein the determination step (S104) is a step of determining whether or not to proceed with the contract with the other user based on the approval authority information of one user and the credit information of the other user.
This allows a party to suspend the contract procedure based on the credit information of the other party according to the party's approval authority when executing the electronic contract procedure, thereby enabling the user to avoid entering into a contract with a less secure party.

(Appendix 12)
The program described in Appendix 11, wherein the judgment step (S104) is a step of determining whether or not to proceed with the contract with the other user by comparing a score threshold corresponding to the approval authority information of one user with the credit score of the other user.
This allows the parties to suspend the contract procedure based on the credit score of the other party according to their approval authority when executing the electronic contract procedure, thereby enabling users to avoid entering into a contract with a less secure party.

(Appendix 13)
A program as described in Appendix 11 or 12, wherein the information acquisition step (S103) is a step of acquiring the second user's credit information from an external social networking service, the judgment step (S104) is a step of judging whether or not a contract procedure can be carried out with the second user based on the second user's credit information acquired in the information acquisition step, and the recipient acceptance step (S102) does not accept the second user as a recipient of the contract information if it is determined in the judgment step that the contract procedure cannot be carried out with the second user.
This allows the first user to stop setting the second user as a recipient of contract information based on the second user's credit information, thereby allowing the first user to avoid entering into a contract with a less secure party.

(Appendix 14)
The program described in Appendix 13 causes the processor to execute a first presentation step (S109) of presenting the first guidance message to the first user to complete the contract procedure with the second user if it is determined in the determination step that the contract procedure with the second user cannot be completed.
This allows the first user to stop setting the second user as a recipient of contract information based on the second user's credit score, thereby allowing the first user to avoid entering into a contract with a less secure counterparty.

(Appendix 15)
A program described in any of Appendices 10 to 14, wherein the information acquisition step (S304) is a step of acquiring the first user's credit information from an external social networking service, the judgment step (S305) is a step of determining whether or not contract procedures with the first user can be carried out based on the first user's credit information acquired in the information acquisition step, and the approval step (S307) does not accept an instruction to approve the conclusion of a contract based on the contract information if it is determined in the judgment step that contract procedures cannot be carried out with the first user.
This allows the second user to suspend approval of the contract information received from the first user based on the credit information of the first user, thereby enabling the second user to avoid entering into a contract with a less secure counterparty.

(Appendix 16)
The program described in Appendix 15 causes the processor to execute a second presentation step (S308) of presenting a second guidance message to the second user to complete the contract procedure with the first user if it is determined in the determination step that the contract procedure with the first user cannot be completed.
This allows the second user to suspend approval of the contract information received from the first user based on the credit score of the first user, thereby allowing the second user to avoid entering into a contract with a less secure counterparty.

(Appendix 17)
An information processing device comprising a processor and a storage unit, the information processing device causing the processor to execute a program according to any one of appendices 1 to 16.
This allows the parties to a contract to take into consideration the information of the other user when carrying out electronic contract procedures and carry out the contract procedures with peace of mind.

(Appendix 18)
An information processing method executed by a computer having a processor and a storage unit, the information processing method causing the processor to execute a program according to any one of Supplementary Notes 1 to 16.
This allows the parties to a contract to take into consideration the information of the other user when carrying out electronic contract procedures and carry out the contract procedures with peace of mind.

(Appendix 19)
An information processing system including a computer having a processor and a memory unit, the information processing system causing the processor to execute a program according to any one of appendices 1 to 16.
This allows the parties to a contract to take into consideration the information of the other user when carrying out electronic contract procedures and carry out the contract procedures with peace of mind.

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, 40 SNS server, 401 Memory unit, 404 Control unit, 406 Input device, 408 Output device

Claims (5)

A program for causing a computer having a processor and a storage unit to execute an electronic contract procedure between different users ,
The program causes the processor to:
a contract acceptance step of accepting contract information to be the subject of a contract conclusion from the first user;
a recipient receiving step of receiving, from the first user, a designation of a second user as a recipient of the contract information received in the contract receiving step;
a contract presentation step of returning the contract information received from the first user to the first user and presenting the contract information to the second user in response to a designation of a second user from the first user and reception of the contract information, without requiring an operation for confirmation by the first user;
an approval step of accepting an instruction to approve the conclusion of the contract information from the second user accepted in the recipient acceptance step;
an information acquisition step of acquiring, for at least one of the first user and the second user, user information of the other user from a service that enables mutual business communication between users ;
an information presenting step of presenting the other user information acquired in the information acquiring step to the at least one user;
A program that executes. 2. The program according to claim 1, wherein in the information presenting step, the other user information including at least a user name in the service is presented to the at least one user. The program of claim 2, wherein the contract information is presented to the second user on a screen in the contract presentation step, and the contract information, an operation member for accepting an operation to agree to the contract information, and the user information including at least the username of the first user for the service are displayed together. A method for causing a computer having a processor and a storage unit to execute an electronic contract procedure between different users, comprising:
The method further comprises the processor:
a contract acceptance step of accepting contract information to be the subject of a contract conclusion from the first user;
a recipient receiving step of receiving, from the first user, a designation of a second user as a recipient of the contract information received in the contract receiving step;
a contract presentation step of returning the contract information received from the first user to the first user and presenting the contract information to the second user in response to a designation of a second user from the first user and reception of the contract information, without requiring an operation for confirmation by the first user;
an approval step of accepting an instruction to approve the conclusion of the contract information from the second user accepted in the recipient acceptance step;
an information acquisition step of acquiring, for at least one of the first user and the second user, user information of the other user from a service that enables mutual business communication between users;
an information presenting step of presenting the other user information acquired in the information acquiring step to the at least one user;
How to perform. An information processing device that executes electronic contract procedures between different users,
a control unit of the information processing device,
a contract acceptance step of accepting contract information to be the subject of a contract conclusion from the first user;
a recipient receiving step of receiving, from the first user, a designation of a second user as a recipient of the contract information received in the contract receiving step;
a contract presentation step of returning the contract information received from the first user to the first user and presenting the contract information to the second user in response to a designation of a second user from the first user and reception of the contract information, without requiring an operation for confirmation by the first user;
an approval step of accepting an instruction to approve the conclusion of the contract information from the second user accepted in the recipient acceptance step;
an information acquisition step of acquiring, for at least one of the first user and the second user, user information of the other user from a service that enables mutual business communication between users;
an information presenting step of presenting the other user information acquired in the information acquiring step to the at least one user;
An information processing device that executes the above.