JP7174870B1 - Program, information processing device, information processing system, information processing method - Google Patents

Abstract

[Problem] In an electronic contract system, when information (contract information) related to an electronic contract is received from a sender, a specific person in charge of executing a contract in the recipient organization is not determined, or the recipient organization Recipients themselves are not authorized to enter into (sign) contracts, and may require separate approval by a specific department or official with authority, in which case the sender It was necessary to ask the customer to specify the recipient of the contract information, which was a complicated task.
A contract reception step for receiving contract information to conclude a contract from a first user, and a receiver reception for receiving second identification information as a receiver of the contract information received in the contract reception step from the first user. and a forwarding step of forwarding the contract information accepted in the contract accepting step to one or more third users based on the second identification information accepted in the recipient accepting step.
[Selection drawing] Fig. 14

Description

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

2. Description of the Related Art With the development and spread of computer technology, documents that have been used as paper media are now being digitized. For example, documents such as contracts that require the signatures and seals of parties are also being managed as electronic data.
Patent Literature 1 discloses a data storage destination limiting device capable of limiting data storage destinations for each user group within a company.
Patent Literature 2 discloses an information processing system relating to a digital contract, which consists of a creator terminal, a confirmation company terminal, and a contract management server.

Japanese Patent Application Laid-Open No. 2021-51345 JP 2017-10096

In the electronic contract system, when receiving information on electronic contracts (contract information) from the sender, there is no specific person in charge to conclude the contract for the recipient organization, or the recipient organization is not authorized to enter into (sign) contracts, and may require separate approval by a specific department or a specific officer with authority, and in such cases, the contract information will be sent to the sender. It was necessary to request the designation of the recipient of the email, which was a cumbersome task.
Therefore, the present disclosure has been made to solve the above problems, and its purpose is to provide an electronic contract system for executing electronic contract procedures, in which the contract information transmitted from the sender is sent to the sender in a complicated manner. To provide a technique for transferring to a predetermined contact person in charge without requiring a request for a receiver setting work.

A program, comprising 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 be subject to contract conclusion from a first user a contract receiving step of receiving contract information; a receiver receiving step of receiving second identification information from the first user as a receiver of the contract information received in the contract receiving step; and a transferring step of transferring the contract information received in the contract receiving step to one or more third users.

According to the present disclosure, the contract information sent for the second identification information can be forwarded to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

1 is a diagram showing an overall configuration of an information processing system 1; FIG. 3 is a block diagram showing the functional configuration of the server 10; FIG. 2 is a block diagram showing the functional configuration of the first user terminal 20; FIG. 3 is a block diagram showing a functional configuration of a second user terminal 30; FIG. 3 is a block diagram showing a functional configuration of a third user terminal 40; FIG. FIG. 11 is a block diagram showing the functional configuration of a fourth user terminal 41; FIG. 10 is a diagram showing the data structure of a user table 1012; FIG. FIG. 10 is a diagram showing the data structure of a group table 1013; FIG. FIG. 10 is a diagram showing the data structure of a document table 1014; FIG. FIG. 10 is a diagram showing the data structure of a confirmation table 1015; FIG. FIG. 10 is a diagram showing the data structure of an input item table 1016. FIG. FIG. 10 illustrates the data structure of a transfer management table 1017; It is a flowchart which shows the operation|movement of a contract creation process. 10 is a flowchart showing the operation of contract confirmation processing; It is an example of a screen which shows the operation|movement of contract creation processing. It is an example of a screen showing a message notified to the second user terminal 30 . It is a screen example of the 1st screen which shows the operation|movement of a contract confirmation process. It is a screen example of the 2nd screen (1st Example) which shows the operation|movement of a contract confirmation process. It is a screen example of the 2nd screen (2nd Example) which shows the operation|movement of a contract confirmation process. It is a screen example of the 3rd screen which shows the operation|movement of a contract confirmation process. 2 is a block diagram showing the basic hardware configuration of computer 90. FIG.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings for explaining the embodiments, common constituent elements are given the same reference numerals, and repeated explanations are omitted. It should be noted that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Also, not all the components shown in the embodiments are essential components of the present disclosure. Each figure is a schematic diagram and is not necessarily strictly illustrated.

<Configuration of System 1>
A system 1 according to the present disclosure is an information processing system for realizing an electronic contract conclusion service among a plurality of users.
The system 1 includes information processing devices such as a server 10, a first user terminal 20, a second user terminal 30, a third user terminal 40, and a fourth user terminal 41, which are connected via a network N. FIG.
FIG. 1 is a diagram showing the overall configuration of an information processing system 1. As shown in FIG.
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 third user terminal 40. As shown in FIG.
FIG. 6 is a block diagram showing the functional configuration of the fourth user terminal 41. As shown in FIG.

Each information processing device is composed of a computer having an arithmetic device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, the second user terminal 30, the third user terminal 40, and the fourth user terminal 41, descriptions overlapping the basic hardware configuration of the computer and the basic functional configuration of the computer, which will be described later, are omitted. do.

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

<Configuration of Storage Unit 101 of Server 10>
Storage unit 101 of server 10 includes application program 1011 , user table 1012 , group table 1013 , document table 1014 , confirmation table 1015 , input item table 1016 , and transfer management table 1017 .

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

The user table 1012 is a table that stores and manages information on member users (hereinafter referred to as users) who use the service. By registering to use the service, the user's information is stored in a new record in the user table 1012 .
This enables the user to use the service according to the present disclosure. Note that users who use services in the present disclosure do not necessarily need to be registered in the user table 1012 .
The user table 1012 is a table having columns of user ID, user name, mail address, group ID, and approval authority, with user ID as a primary key.
FIG. 7 is a diagram showing the data structure of the user table 1012. As shown in FIG.

User ID is an item that stores user identification information for identifying a user. User identification information is an item in which a unique value is set for each user.
The user name is an item that stores the name of the user. Any character string such as a nickname may be set as the user name instead of the full name.
The mail address is an item for storing the user's mail address.
Group ID is an item that stores group identification information of a group to which the user belongs. A user may belong to multiple groups.
Approval authority is an item that stores authority information related to conclusion of approval by the user. For a user who has the authority to approve the conclusion of a contract (approval authority), information such as True, which has the authority to approve the conclusion of a contract, is stored. On the other hand, for a user who does not have the authority to approve the conclusion of a contract, information such as False, blank, or null value, which does not have the authority to approve the conclusion of a contract, is stored.
In addition, it is also possible to store information (window role information) indicating that the user has the role of window clerk within the group. As a result, it is possible to determine that the user whose approval authority has contact role information is the contact person.
A configuration in which approval authority can be set according to contract information may be employed. For example, user A may have approval authority for specific contract information A, but may not have approval authority for specific contract information B. FIG.
Approval authority may be set according to the type of contract information (type of contract information) such as non-disclosure agreement, joint research agreement, and contract. For example, the user A may be configured to have approval authority for non-disclosure agreements, but not to have approval authority for contract contracts.
In addition, it is also possible to store authority information in multiple levels (levels and ranks) according to the department to which the user belongs, government office, and the like. For example, information such as C for temporary employees, B for general employees, A for managers, and S for executives is stored in the approval authority item, and depending on the contract type information, contract amount, etc. in the contract information, a predetermined rank or higher (For example, a non-disclosure agreement is A or higher.) Only a user who has approval authority may approve the conclusion of a contract.

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

Group ID is an item that stores group identification information for identifying a group. Group identification information is an item in which a unique value is set for each group.
The group name is an item that stores the name of the group. Any character string can be set for the group name.
The administrator ID is an item that stores user identification information of a user who has administrator authority in the group. A user having administrative authority can arbitrarily determine and set a user having a predetermined or higher position or authority in a group such as an organization.

Document table 1014 is a table for storing and managing information (contract information) relating to electronic contracts exchanged between creators and recipients.
The document table 1014 is a table having document ID as a primary key and columns of document ID, document data, and creator ID.
FIG. 9 is a diagram showing the data structure of the document table 1014. As shown in FIG.

Document ID is an item for storing document identification information for identifying contract information. Document identification information is an item in which a unique value is set for each piece of contract information.
Document data is an item that stores contract information (binary or text data).
This is an item for storing a creator ID and user identification information for identifying a user who is a creator of contract information.

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

The document ID is an item for storing the document identification information of the contract information to be confirmed by the confirmer.
The confirmation order is an item that stores information about the confirmation order when the contract information is confirmed by the confirmer. The contract information stored by the creator is circulated to the confirmers in order of confirmation order, and confirmation is performed.
Designator data is an item that stores information for identifying a user who designates a confirmation person of contract information. Specifically, the designator data includes information that identifies the user, such as an email address or user identification information.
The confirmer e-mail address is an item for storing the e-mail address of the person who confirmed the contract information. The e-mail address of the confirmer does not need to be registered as a user in advance to use the service according to the present disclosure. In other words, the confirmer's email address need not be included in the user table 1012 .
The confirmation flag is an item for storing confirmation identification information for identifying whether or not confirmation procedures for contract information have been completed by a confirmation person. When the confirmer completes the confirmation of the contract information, information indicating that the confirmation has been completed, such as a value of True, is stored in the item of the confirmation flag.
Language data is an item that stores information (language information) on the language of the confirmer.
The access code is an item that stores the access code set for the confirmer.
The date and time is an item for storing the date and time when the confirmation procedure of the contract information was performed by the confirmation person. Specifically, the date and time when the confirmation identification information is stored in the item of the confirmation flag 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, input person ID, input data, input rule, and date and time.
FIG. 11 is a diagram showing the data structure of the input item table 1016. As shown in FIG.

The input item ID is an item that stores input item identification information for identifying an input item.
The document ID is an item that stores the document identification information of the electronic contract information associated with the input item.
The input person ID is an item that stores the user identification information or the e-mail address of the input person who has input the input data for the input item. Specifically, the input person ID stores the creator ID, the email address of the user identified by the creator ID, the email address of the confirmer, and the like.
The input data is an item that stores the input data input to the input item by the input person.
The input rule is an item that stores input rule information regarding input rules for input items. As input rules, in addition to data types such as date (date), date and time (datetime), character strings (text), and numeric values (integer), for character strings, the number of characters, regular expressions for character strings, etc. Validation rule information can be stored for validation rules.
The date and time is an item that stores the date and time when the input data was input to the input item by the input person.

The transfer management table 1017 is a table that stores and manages information on transfer conditions (transfer condition information).
The transfer management table 1017 is a table having columns of a transfer condition and a transfer destination user ID.
FIG. 12 shows the data structure of the transfer management table 1017. As shown in FIG.

The forwarding condition is an item that stores conditions for forwarding to the user specified by the forwarding destination user ID.
For example, the forwarding conditions can store predetermined user identification information and e-mail address. That is, it is possible to specify specific user identification information and contract information with a mail address as a transmission destination, and transfer the information to a user having a specific forwarding destination user ID.
For example, the forwarding conditions can store predetermined group identification information. In other words, it is possible to specify contract information whose transmission destination is a user associated with specific group identification information, and transfer it to a user having a specific transfer destination user ID.
For example, the transfer conditions can store predetermined contract type information. That is, contract information having specific contract type information can be specified and transferred to a user having a specific transfer destination user ID.
For example, the transfer conditions can store contract amount information (contract amount information). That is, it is possible to specify contract information whose contract amount is less than or equal to or greater than a predetermined amount, and transfer the information to a user having a specific transfer destination user ID.
For example, the transfer conditions can store creator information (creator information). In other words, the user who is the creator (sender) can identify the creator information, such as a predetermined user or a user belonging to a predetermined group, and transfer it to a user having a specific forwarding destination user ID. can. A predetermined user ID can be set as the forwarding destination according to the company, organization, etc. to which the creator belongs.
Transfer conditions may include a combination of conditions for user identification information, group identification information, contract type information, contract amount information, creator information, and the like.
The forwarding conditions can be stored in association with the forwarding destination user ID by operating the administrator terminal by a user having administrative authority. A user having administrator authority may store only users belonging to the group ID associated with his/her own user ID in the group table 1013 as the forwarding destination user ID. In other words, a configuration may be adopted in which a user having administrator authority can store other users who belong to a group to be managed as forwarding destination user IDs. As a result, it is possible to prevent a user having administrator authority from transferring contract information to a user who is not subject to management.
The forwarding destination user ID is an item for storing the user identification information of the forwarding destination user. Instead of the user identification information, the mail address of the forwarding destination user may be stored.

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

The user registration control unit 1041 performs processing for storing information of 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 transmitted to the server 10 by the user opening a web page or the like operated by the service provider from any information processing terminal, entering information in a predetermined input form, and transmitting the information to the server 10 . The user registration control unit 1041 stores the received information in a new record of the user table 1012, and user registration is completed. As a result, the users stored in the user table 1012 can use the service.
Prior to registration of user information in the user table 1012 by the user registration control unit 1041, the service provider may perform a predetermined examination to limit whether the user can 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 any character string or number automatically set by the user registration control unit 1041. .

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

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

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

<Configuration of Storage Unit 201 of First User Terminal 20>
The storage unit 201 of the first user terminal 20 has a first user ID 2011 and an application program 2012 .

The first user ID 2011 is the user's account ID. The user transmits the first user ID 2011 from the first user terminal 20 to the server 10 . The server 10 identifies the user based on the first user ID 2011 and provides the user with the service according to the present disclosure. 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 stored in the storage unit 201 in advance, or may be downloaded from a web server or the like operated by the service provider via the communication IF.
Application programs 2012 include applications such as web browser applications.
The application program 2012 includes an interpreted programming language such as JavaScript (registered trademark) that runs 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 has an input control unit 2041 and an output control unit 2042 . Control unit 204 implements each functional unit by executing first user ID 2011 stored in storage unit 201 .

<Configuration of Input Device 206 of First User Terminal 20>
The input device 206 of the first user terminal 20 has a camera 2061 , a microphone 2062 , a position information sensor 2063 , a motion sensor 2064 and a touch device 2065 .

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

<Configuration of Second User Terminal 30>
The second user terminal 30 is an information processing device operated by a user who uses the service. The second user terminal 30 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smart phone or a tablet. Moreover, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The second user terminal 30 includes a storage section 301 , a control section 304 , an input device 306 and an output device 308 .

<Configuration of Storage Unit 301 of Second User Terminal 30>
The storage unit 301 of the second user terminal 30 has 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 service according to the present disclosure. The second user ID 3011 includes information such as a session ID temporarily assigned by the server 10 for identifying the user using the second user terminal 30 .

The application program 3012 may be stored in advance in the storage unit 301, or may be downloaded from a web server or the like operated by the service provider via the communication IF.
Application programs 3012 include applications such as web browser applications.
The application program 3012 includes an interpreted programming language such as JavaScript (registered trademark) executed on a web browser application stored in 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 has an input control unit 3041 and an output control unit 3042 . Control unit 304 implements each functional unit by executing second user ID 3011 stored in storage unit 301 .

<Configuration of Input Device 306 of Second User Terminal 30>
The input device 306 of the second user terminal 30 has a camera 3061 , a microphone 3062 , a position information sensor 3063 , a motion sensor 3064 and a keyboard 3065 .

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

<Configuration of Third User Terminal 40>
The third user terminal 40 is an information processing device operated by a user who uses the service. The third user terminal 40 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smart phone or a tablet. Moreover, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The third user terminal 40 includes a storage section 401 , a control section 404 , an input device 406 and an output device 408 .

<Configuration of Storage Unit 401 of Third User Terminal 40>
The storage unit 401 of the third user terminal 40 has a third user ID 4011 and an application program 4012 .

The third user ID 4011 is the user's account ID. The user transmits the third user ID 4011 from the third user terminal 40 to the server 10 . The server 10 identifies the user based on the third user ID 4011 and provides the user with the service according to the present disclosure. The third user ID 4011 includes information such as a session ID temporarily assigned by the server 10 for identifying the user using the third user terminal 40 .

The application program 4012 may be stored in the storage unit 401 in advance, or may be downloaded from a web server or the like operated by the service provider via the communication IF.
Application programs 4012 include applications such as web browser applications.
The application program 4012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored in the third user terminal 40 .

<Configuration of the control unit 404 of the third user terminal 40>
The control unit 404 of the third user terminal 40 has an input control unit 4041 and an output control unit 4042 . Control unit 404 implements each functional unit by executing third user ID 4011 stored in storage unit 401 .

<Configuration of Input Device 406 of Third User Terminal 40>
The input device 406 of the third user terminal 40 has a camera 4061 , a microphone 4062 , a position information sensor 4063 , a motion sensor 4064 and a keyboard 4065 .

<Configuration of output device 408 of third user terminal 40>
The output device 408 of the third user terminal 40 has a display 4081 and a speaker 4082 .

<Configuration of fourth user terminal 41>
The fourth user terminal 41 is an information processing device operated by a user who uses the service. The fourth user terminal 41 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile terminal such as a smart phone or a tablet. Moreover, it may be a wearable terminal such as an HMD (Head Mount Display) or a wristwatch type terminal.
The fourth user terminal 41 has a storage unit 411 , a control unit 414 , an input device 416 and an output device 418 .

<Configuration of Storage Unit 411 of Fourth User Terminal 41>
The storage unit 411 of the fourth user terminal 41 has a fourth user ID 4111 and an application program 4112 .

The fourth user ID 4111 is the user's account ID. The user transmits the fourth user ID 4111 from the fourth user terminal 41 to the server 10 . The server 10 identifies the user based on the fourth user ID 4111 and provides the user with the service according to the present disclosure. The fourth user ID 4111 includes information such as a session ID temporarily assigned by the server 10 for identifying the user using the fourth user terminal 41 .

The application program 4112 may be stored in the storage unit 411 in advance, or may be downloaded from a web server or the like operated by the service provider via the communication IF.
Application programs 4112 include applications such as web browser applications.
The application program 4112 includes an interpreted programming language such as JavaScript (registered trademark) executed on a web browser application stored in the fourth user terminal 41 .

<Configuration of the control unit 414 of the fourth user terminal 41>
The controller 414 of the fourth user terminal 41 has an input controller 4141 and an output controller 4142 . Control unit 414 implements each functional unit by executing fourth user ID 4111 stored in storage unit 411 .

<Configuration of Input Device 416 of Fourth User Terminal 41>
The input device 416 of the fourth user terminal 41 has a camera 4161 , a microphone 4162 , a position information sensor 4163 , a motion sensor 4164 and a keyboard 4165 .

<Configuration of Output Device 418 of Fourth User Terminal 41>
The output device 418 of the fourth user terminal 41 has a display 4181 and a speaker 4182 .

<Operation of information processing system 1>
Each process of the information processing system 1 will be described below.
FIG. 13 is a flow chart showing the operation of the contract creating process.
FIG. 14 is a flow chart showing the operation of contract confirmation processing.
FIG. 15 is a screen example showing the operation of the contract creating process.
FIG. 16 is a screen example showing a message notified to the second user terminal 30. As shown in FIG.
FIG. 17 is a screen example of the first screen showing the operation of the contract confirmation process.
FIG. 18 is a screen example of the second screen (first embodiment) showing the operation of the contract confirmation process.
FIG. 19 is a screen example of the second screen (second embodiment) showing the operation of the contract confirmation process.
FIG. 20 is a screen example of the third screen showing the operation of the contract confirmation process.

<Contract creation process>
Contract creation processing is processing in which a creator creates contract information and transmits it to a confirmer. In the present disclosure, it is assumed that the first user is the creator of the contract information, and the second, third, and fourth users are the confirmers of the contract information. It should be noted that it is possible to set a plurality of users as confirmers when creating the contract information.
In the present disclosure, the first user is a user belonging to a group such as an organization or company different from the second user, and the second user, the third user, and the fourth user are users belonging to the same group such as an organization or company. is.

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

<Overview of contract creation process>
In the contract creation process, the creator creates contract information, sets the confirmation person who is the addressee of the contract information, sets the input items for the contract information, sets the input rules for the input items, and sets the input items from the creator. It is a series of processes of accepting input data for the client, determining transfer conditions, and sending contract information to the set confirmer or transfer destination.

<Details of contract creation process>
In step S101, the contract creating unit 1042 of the server 10 receives contract information to be concluded between the creator and the confirmer.
Specifically, the first user operates the input device 206 or the like of the first user terminal 20 to create contract information including document data related to the contract. The contract information can include document data in any data format, such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
The first user operates the input device 206 or the like of the first user terminal 20 to transmit 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 items of creator ID and document data of a new record in the document table 1014, respectively. As a result, the contract creating unit 1042 of the server 10 stores the new contract information in the document table 1014. FIG.

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

In step S102, the second identification information is received from the first user as the recipient of the contract information received in step S101. For example, the second identification information is information for specifying the second user. The second identification information may include the second user's email address or a second user ID. In the present disclosure, a case of an e-mail address will be described as an example of the second identification information. Note that the second identification information does not have to be information that identifies a specific user, and includes identification information that identifies a specific group such as a company, an organization, an organization, or a department. Specifically, the first user can designate, as the second identification information, a specific department of a specific company as the recipient of the contract information instead of the user.
Specifically, the first user operates the input device 206 or the like of the first user terminal 20 to select and specify the user who will be the confirmer (recipient) of the contract information. For purposes of this disclosure, the first user shall select and identify the second user as the recipient.
The first user operates the input device 206 or the like of the first user terminal 20 to input the e-mail address of the second user who will be the confirmer, and transmits the e-mail address to the server 10 . The contract creating unit 1042 of the server 10 stores the received e-mail address and the document ID of the contract information created and stored in step S101 in the items of the confirmer e-mail address and the document ID of the confirmation table 1015, respectively. Stored in association with the email address of the second user. Note that the first user may set the language and access code of the second user and store them in association with the second user's email address.
At this time, a value of 1 is stored in the confirmation order item of the confirmation table 1015 . In step S102, the first user may select and set a plurality of confirmers. In this case, according to the selection order, the value of the check order item of the user who is the checker is incremented one by one and stored. As a result, the circulation order of confirmers in the contract confirmation process, which will be described later, is set. Note that the setting of the circulation order is not essential.

In step S103, the first user operates the input device 206 or the like of the first user terminal 20 to set input items for the contract information.
Specifically, the first user operates the input device 206 or the like of the first user terminal 20 to set a plurality of input items for the contract information created and stored in step S101. Input items can be any input items such as a seal field for stamping seal data, an input field for entering text data such as signature data, a check box field for selecting check items, and a date field for entering dates. .
The first user operates the input device 206 or the like of the first user terminal 20 to transmit a request to add an input item to the server 10 . Upon receiving the request, the contract creation unit 1042 of the server 10 stores the document ID of the contract information in the document ID of the new record in the input item table 1016 . As a result, the newly added input item information is stored in association with the contract information. Note that the first user can store a plurality of pieces of input item information in association with the contract information.

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

In step S105, the contract creation unit 1042 of the server 10 receives input data for a plurality of input items input by the first user.
Specifically, the first user inputs input data for each input item set in step S104 by operating the input device 206 of the first user terminal 20 or the like. For example, the first user may enter number input data for managing contract information, such as reference number in the group to which the first user belongs, in the input item in which the management number is set. The first user may input the input data of the contract execution date of the contract information in the input item in which the contract execution date is set. After completing the input of the input data to the input items, the first user transmits the input item ID for each input item and the input data to the server 10 .
The contract creating unit 1042 of the server 10 receives and accepts the input item ID and input data for each input item. The contract creating unit 1042 of the server 10 stores the received input data in the input data item of the input item information of the input item table 1016 specified by the received input item ID. Thereby, the input data input by the first user is stored in the input item table 1016 .

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

In step S106, upon receiving the request, the contract creation unit 1042 of the server 10 transfers the contract information received in step S101 to one or more third users based on the second identification information received in step S102.

Specifically, the contract creating unit 1042 of the server 10 acquires the confirmer email address stored in the confirmation table 1015 in step S102. The contract creation unit 1042 of the server 10 searches the mail address item of the user table 1012 based on the obtained confirmer's email address, and obtains the confirmer's user ID.
The contract creating unit 1042 of the server 10 searches the transfer condition items in the transfer management table 1017 based on the acquired user ID of the confirmation person, and acquires the transfer destination user ID. Specifically, when there is a transfer condition in which the acquired confirmer user ID is set as the user ID of the confirmer in the transfer condition, the transfer destination user ID associated with the transfer condition is acquired.
Note that the contract creating unit 1042 of the server 10 searches for transfer condition items in the transfer management table 1017 based on the user ID of the confirmer, contract type information, contract amount specified in the contract information, creator information, and the like. A forwarding destination user ID may be obtained. The contract creating unit 1042 of the server 10 may be configured to identify and acquire a plurality of forwarding destination user IDs. In the present disclosure, the forwarding destination user ID includes, for example, the third user ID.

The contract creating unit 1042 of the server 10 searches the user ID item of the user table 1012 based on the acquired forwarding destination user ID, and acquires the mail address of the forwarding destination user. The contract creating unit 1042 of the server 10 acquires the items of the document ID, confirmation order, designator data, language data, and access code associated with the second user from the confirmation table 1015, and associates them with the forwarding destination user's email address. , are respectively stored in the items of document ID, confirmation order, designator data, language data, access code, and confirmer email address of a new record in the confirmation table 1015 .
When a plurality of forwarding destination users are specified, the contract creating unit 1042 of the server 10 adds a value obtained by incrementing the value of the second user's confirmation order item by one to each forwarding destination user's record. It may be configured to be stored in the confirmation order item. At this time, the contract creation unit 1042 of the server 10 adds the predetermined forwarding destination user to the record of the confirmation table 1015, so that the confirmation order value of the record of the confirmation person in the latter stage (higher confirmation order) in the confirmation order may be moved down and stored (updated). As a result, when a plurality of confirmers are designated, it is possible to replace the transfer source user with the transfer destination user while maintaining the confirmation order.
In addition, the contract creation unit 1042 of the server 10 stores information indicating that the confirmation work was skipped due to the transfer in the confirmation flag item of the record of the second user stored in the confirmation table 1015 . Note that the contract creating unit 1042 of the server 10 may be configured to delete the second user's record in the confirmation table 1015 . As a result, the contract confirmation process by the second user is skipped.

In step S107, the contract creating unit 1042 of the server 10 transmits a message notifying that the confirmation request of the contract information has been transmitted from the first user to the second user or the confirmer such as the forwarding destination user. . Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order item of the confirmation table 1015, and finds the user (first confirmation user) who is the first confirmer with the smallest value stored in the confirmation order item. identify. In the present disclosure, as an example, the first confirmed user is the third user. The contract creating unit 1042 of the server 10 transmits a message to the mail address of the first confirming user by communication means such as mail, notifying that the first user has sent a request to confirm the contract information.
The message to be notified to the first confirmation user includes URL (Uniform Resource Locator) information including the document ID for specifying the contract information. The URL may directly contain the document ID, or may contain information such as a character string obtained by optionally encrypting the document ID, or a character string that can identify the document ID by referring to a table (not shown). good. Also, the URL may include information for specifying the first confirmed user. For example, if the first confirmed user has not registered as a user for the service according to the present disclosure, it is necessary to include information for identifying the first confirmed user in the URL.

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

The contract creating unit 1042 of the server 10 may notify the second user accepted in step S102 that the contract information accepted in step S101 has been transferred to one or more third users. Specifically, the contract creation unit 1042 of the server 10 searches for a record in which information indicating that the confirmation work has been skipped is stored in the confirmation flag item of the confirmation table 1015, and checks the confirmer email address of the record. to send a message notifying that the contract information has been transferred to the first confirmed user.

FIG. 16 is a screen example showing a message notified to the third user terminal 40, which is the user terminal of the first confirmed user. The message screen 60 displayed on the display 4081 of the third user terminal 40 includes the information of the URL 62 including the document ID for specifying the message 61 and the contract information.

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

Input items 532, 533, and 534 are drawn as drawing objects on the screen 50 for creating contract information. In the input items 532 and 533, the user identification information "USER-B" of the user selected and set to input the input item and the item "text" as the input item type are drawn as allocation. In the input item 534 related to sealing, the user identification information “USER-C” of the user for whom sealing is selected and set as the assignment, and the item “mark” as the input item type are drawn.

<Contract confirmation process>
The contract confirmation process is a process in which a confirmation person 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 first screen for displaying contract information to the confirmer, receives input data for input items from the confirmer, and receives confirmation of contract information from the confirmer. This is a series of processes for receiving data.
In the contract confirmation process, if the confirmer does not have approval authority for the contract information, or if he/she is the person in charge of contact, the confirmer is presented with a second screen for selecting and designating an approver. 1, a series of processes for accepting designation of an approver of contract information from the confirmer, accepting input data for input items from the confirmer, and sending contract information to the set approver.
The details of the contract confirmation process for the third user and the fourth user who are the confirmers in the present disclosure are respectively the details of the contract confirmation process (third user) and the details of the contract confirmation process (fourth user). user).

<Details of contract confirmation processing (third user)>
In step S301, the third user, who is the first confirmed user, operates the input device 406 of the third user terminal 40 to select the URL described in the received message. The application can open the web page specified by the URL. Accordingly, the third user terminal 40 transmits to the server 10 a request for executing the contract verification process.

When the access code item is stored in the record of the third user in the confirmation table 1015, the input of the access code is requested to the third user, and the entered access code and the third user in the confirmation table 1015 are entered. An authentication process can be performed for a third user by matching it with the access code stored in the user's record.
Specifically, the server 10 transmits an input screen for authenticating the access code to the third user terminal 40 . The third user operates the input device 406 of the third user terminal 40 to enter the access code and transmit it to the server 10 . The contract confirmation unit 1043 of the server 10 determines whether or not the received access code matches the access code stored in the record of the third user in the confirmation table 1015. If they match, contract confirmation processing is performed. continue. On the other hand, if they do not match, the contract confirmation process is aborted. Note that the authentication process using the access code may be omitted.

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

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

The contract confirmation unit 1043 of the server 10 searches the user ID item of the user table 1012 based on the specified user identification information of the third user, and acquires the approval authority item of the third user. In the present disclosure, the approval authority of the third user is stored in the user table 1012, but the approval authority of the third user may be stored for each group to which the third user belongs, or It may be stored for each information or for each contract information type. The contract confirmation unit 1043 of the server 10 acquires the approval authority information of the third user for the target contract information.
In addition, when the third user has not registered as a user for the service according to the present disclosure, the process may be executed by regarding the third user as a user without approval authority.

In step S303, the contract confirmation unit 1043 of the server 10 checks the second screen or the first A screen is generated and transmitted to the third user terminal 40 .

Specifically, the contract confirmation unit 1043 of the server 10, if the third user's approval authority information acquired in step S302 stores information having the authority to approve the conclusion of a contract, the third user The first screen is presented, and the process proceeds to step S304.

On the other hand, when the third user is a user who cannot approve the contract conclusion of the received contract information, the second screen is presented to the third user, and the process proceeds to step S307. Specifically, if the third user's approval authority information acquired in step S302 contains information that does not have the authority to approve the conclusion of a contract, the contract confirmation unit 1043 of the server 10 asks the third user to to present the second screen, and the process proceeds to step S307.

Note that if the third user is a user who has contact role information, the second screen may be presented to the third user and the process proceeds to step S307. In this case, if the third user is a user who cannot approve the conclusion of the contract of the received contract information, the execution of the contract confirmation process may be terminated.
As a result, the approver can be set only when the third user is the contact person, and other users who cannot approve the conclusion of the contract cannot set the approver. .

In step S304, the display 4081 of the third user terminal 40 presents the third user with the first screen for accepting the operation of approving the contract information. The third user confirms and approves the contract information displayed on the display 4081 of the third user terminal 40 .
Note that the first screen presented to the third user is based on the language information stored in the language data item of the record of the third user in the confirmation table 1015, and is written in the language specified for the confirmer. It may be configured to be presented to the user.

FIG. 17 is a screen example of the first screen showing the operation of the contract confirmation process. On the first screen 70A for approving the contract information displayed on the display 4081 of the third user terminal 40, 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 and an agree button 740 are displayed.

In step S305, the contract confirmation unit 1043 of the server 10 accepts input for one or more input items of the contract information.
Specifically, the third user operates the input device 406 or the like of the third user terminal 40 to input input data to input items 732, 733, 734, and 735 set in the contract information. Note that, in the present disclosure, input by the third user is not assigned to the input item 736, so that the fact that the third user cannot input input data is visually identifiably displayed.

In step S306, the contract confirmation unit 1043 of the server 10 receives from the third user an instruction to agree and approve the contract conclusion of the contract information received from the first user.
The third user confirms the contract information and input data displayed on the display 4081 of the third user terminal 40, and operates the input device 406 or the like of the third user terminal 40 when agreeing or consenting to the content. By pressing the consent button 740 displayed on the screen 70 for confirming the contract information, the request including the document ID, the information specifying the third user, and the input data for each input item input in step S305 is sent to the server. 10 is executed. Information specifying the third user may be the third user ID 4011 .
The contract confirmation unit 1043 of the server 10 stores information indicating that the third 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 the information specifying the third user, and stores the value of True in the confirmation flag field of the record. For example, if the information specifying the third user is an e-mail address, the items of the document ID and the confirmer's e-mail address in the confirmation table 1015 are searched, and the value of True is stored in the confirmation flag item of the record. When the information specifying the third user is user identification information, the document ID, confirmation The item of the person's mail address is searched, and the value of True is stored in the item of the confirmation flag of the record.
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. As a result, the input data input by the third user is stored as input item information in the input item table 1016 in step S305.

The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all confirmers with approval authority. Specifically, the contract confirmation unit 1043 of the server 10 confirms that, in the confirmation table 1015, when a value of True is stored in the confirmation flag of the record of the confirmer with approval authority, all confirmers with authorization authority It is determined that the contract confirmation process has been executed. In other words, the determination is made while ignoring the value of the confirmation flag of the record of the confirmer who does not have approval authority.
The contract confirmation unit 1043 of the server 10 transmits a message notifying that the contract confirmation process has been completed to the first user when the contract confirmation process has been executed by all confirmers having approval authority.
Specifically, the contract creating unit 1042 of the server 10 transmits a message to the first user's mail address by means of contact means such as mail, notifying that the second user has completed checking the contract information. That is, the first user is notified that the contract conclusion has been approved by the second user. This allows the first user to know that the contract has been concluded with the second user. The second user can complete an appropriate contract conclusion procedure without the first user knowing that the contract conclusion has been approved by the third user in the organization to which the second user belongs. Note that the message may include content to notify that the third user has completed confirmation of the contract information.
The message to be notified to the first user may include URL information including the document ID for specifying the contract information.
When a plurality of users are set as confirmers, the contract confirmation unit 1043 of the server 10 notifies the user of the confirmation person other than the user who last executed the contract confirmation process that the contract confirmation process has been completed. You may send a message notifying As a result, the user who is the confirmer can also be notified that the contract confirmation process has been completed by all the confirmers.
Further, the contract confirmation unit 1043 of the server 10 may transmit a message notifying that the contract confirmation process has been completed to a user having authority corresponding to an administrator in a group to which a plurality of confirmers belong. As a result, the administrator of the group to which the confirming user belongs can be notified of the completion of the contract confirmation process. The contract confirmation unit 1043 of the server 10 acquires the group ID item by searching the user table 1012 for the user ID or email address based on the user ID or email address. The contract confirmation unit 1043 of the server 10 searches the group ID item of the group table 1013 based on the acquired group ID item, acquires the administrator ID item, and corresponds to the administrator based on the administrator ID. An authorized user is identified by searching for the user ID in the user table 1012, and a message is sent notifying that the contract verification process has been completed.

<Second screen presentation processing (first embodiment)>
In step S307, the display 4081 of the third user terminal 40 presents the third user with the second screen (first embodiment) for accepting an operation to specify one or more approvers.
For example, if the third user has not registered as a user for the service according to the present disclosure, the second screen presentation process (first embodiment) may be executed.
Note that the second screen presented to the third user is based on the language information stored in the language data item of the record of the third user in the confirmation table 1015, and is written in the language specified for the confirmer. It may be configured to be presented to the user.

FIG. 18 is a screen example (first embodiment) of the second screen showing the operation of the contract confirmation process. The second screen 80 for accepting an operation to specify a user of one or more approvers, displayed on the display 4081 of the third user terminal 40, includes the approver's email address 801, name 802, company name 803, language 804, an entry field for entering an access code 805, a cancel button 821, and an add button 822 are displayed.

In step S308, information identifying one or more fourth users as approvers is received from the third user.
Specifically, the third user operates the input device 406 or the like of the third user terminal 40 to input the approver's email address, name, company name, language used by the approver, and access code to the second screen. Enter the mail address 801, name 802, company name 803, language 804, and access code 805 displayed in 80. Note that the third user may omit the input of the company name, language, and access code.

<Second screen presentation process (second embodiment)>
In step S307, the display 4081 of the third user terminal 40 presents the third user with a second screen (second embodiment) for accepting an operation to specify one or more approvers.
For example, when a third user has registered as a user for the service according to the present disclosure, the second screen presentation process (second embodiment) may be executed.

FIG. 19 is a screen example (second embodiment) of the second screen showing the operation of the contract confirmation process. The second screen 80 for accepting an operation to specify a user of one or more approvers, displayed on the display 4081 of the third user terminal 40, includes the approver's email address 801, name 802, company name 803, language 804, an input field for entering the access code 805, a cancel button 821, an add button 822, a user candidate presentation area 841 for presenting a plurality of users as user candidates, and a switch button 861 for switching the type of user candidates. Is displayed.
By operating the input device 406 of the third user terminal 40 or the like, the third user presses the switch button 861 displayed on the second screen 80 to select "group", "history", and "group history". , and “Others”, and a plurality of user candidates can be presented in the user candidate presentation area 841 .
If the third user does not belong to a predetermined group and is not associated with the group identification information, or if the third user cannot use the functions related to the group, the switch button 861 is set to "group", A configuration in which the items "group history" and "others" cannot be pressed may be adopted. In other words, a configuration may be adopted in which only user candidates based on the "history" can be presented to the third user. In addition, a configuration may be included in which a predetermined manager such as a section manager or department manager is presented as a user candidate.

In step S308, information identifying one or more fourth users as approvers is received from the third user.
Specifically, the third user operates the input device 406 of the third user terminal 40, etc., in the same manner as in the second screen presentation process (first embodiment), and uses the approver's email address, name, company name, approval The language and access code used by the user can be entered in the mail address 801, name 802, company name 803, language 804, and access code 805 displayed on the second screen 80, respectively. Note that the third user may omit the input of the company name, language, and access code.

In the second screen presentation process (second embodiment), the contract confirmation unit 1043 of the server 10 accepts an operation of specifying one or more approvers from among the user candidates presented in the user candidate presentation area 841. can be done.
Specifically, the third user selects and specifies one or more user candidates presented in the user candidate presentation area 841 by operating the input device 406 or the like of the third user terminal 40 . The control unit 404 of the third user terminal inputs the information of the selected user candidate into input fields such as the mail address 801, name 802, company name 803, language 804, and the like.
As a result, the third user can select the third user who will be the approver from among the plurality of presented user candidates, thereby reducing the input burden on the third user.

<Presentation of User Candidates Based on Group>
The contract confirmation unit 1043 of the server 10 selects one or more users who can approve the contract information among the plurality of users associated with the second group for the third user associated with the second group. Submit as a candidate. At this time, one or a plurality of users who cannot approve the contract information among the plurality of users associated with the second group may not be presented as user candidates.
Specifically, the third user operates the input device 406 or the like of the third user terminal 40, presses the "group" button from the switching button 861 displayed on the second screen 80, and presents user candidates based on the group. Send the request to the server 10 .
Upon receiving the request, the contract confirmation unit 1043 of the server 10 searches the user table 1012 for the e-mail address or user ID based on the third user's e-mail address or user ID, which is the information identifying the third user, Acquire the group ID item (second group ID). The contract confirmation unit 1043 of the server 10 searches the group ID item of the user table 1012 based on the acquired second group ID, and acquires the user ID, user name, email address, and approval authority items.
The contract confirmation unit 1043 of the server 10 transmits to the third user terminal 40 the user ID, user name, and email address of the user who has approval authority. The display 4081 of the third user terminal 40 displays a list of user candidate information including the user name, mail address, etc. received in the user candidate presentation area 841 .

<Presentation of User Candidates Based on History (First Embodiment)>
The contract confirmation unit 1043 of the server 10 presents, as user candidates, one or more fourth users identified in the past by the third user, based on the history information of the third user. At this time, one or more users whose contract information cannot be approved may not be presented as user candidates.
Specifically, the third user operates the input device 406 or the like of the third user terminal 40, presses the "history" button from the switching button 861 displayed on the second screen 80, and presents user candidates based on the history. Send the request to the server 10 . Upon receiving the request, the contract confirmation unit 1043 of the server 10 searches the designated person data item in the confirmation table 1015 based on the information identifying the third user, and Get the confirmer email address. The contract confirmation unit 1043 of the server 10 searches the mail address item of the user table 1012 based on the acquired mail address, and acquires the user ID, user name, mail address, and approval authority items.
The contract confirmation unit 1043 of the server 10 transmits to the third user terminal 40 the user ID, user name, and email address of the user who has approval authority. The display 4081 of the third user terminal 40 displays a list of user candidate information including the user name, mail address, etc. received in the user candidate presentation area 841 .

<Presentation of User Candidates Based on History (Second Embodiment)>
Based on the history information of the second group with which the third user is associated, the contract confirmation unit 1043 of the server 10 identifies one or more users in the past including the third user associated with the second group. A fourth user is presented as a candidate user. At this time, one or more users whose contract information cannot be approved may not be presented as user candidates.
Specifically, the third user operates the input device 406 or the like of the third user terminal 40, presses the "group history" button from the switching button 861 displayed on the second screen 80, and selects user candidates based on the group history. to the server 10.
Upon receiving the request, the contract confirmation unit 1043 of the server 10 searches the user table 1012 for the e-mail address or user ID based on the third user's e-mail address or user ID, which is information identifying the third user, Acquire the group ID item (second group ID). The contract confirmation unit 1043 of the server 10 searches the group ID item of the user table 1012 based on the acquired second group ID, and acquires the user ID and mail address items. Thereby, a plurality of users associated with the second group can be acquired.
The contract confirmation unit 1043 of the server 10 searches the designated person data items in the confirmation table 1015 based on the obtained user IDs and email addresses of the users associated with the second group, and Get the confirmer email address of a user who has been identified as an approver by multiple users in the past. The contract confirmation unit 1043 of the server 10 searches the mail address item of the user table 1012 based on the acquired mail address, and acquires the user ID, user name, mail address, and approval authority items.
The contract confirmation unit 1043 of the server 10 transmits to the third user terminal 40 the user ID, user name, and email address of the user who has approval authority. The display 4081 of the third user terminal 40 displays a list of user candidate information including the user name, mail address, etc. received in the user candidate presentation area 841 .

<Presentation of User Candidates Based on Other Information>
The contract confirmation unit 1043 of the server 10 presents a plurality of users as user candidates based on at least one of the contract information, the first user associated with the first group, and the first group. At this time, one or more users whose contract information cannot be approved may not be presented as user candidates.
Specifically, the third user operates the input device 406 of the third user terminal 40 or the like, presses the "other" button from the switching button 861 displayed on the second screen 80, and selects user candidates based on other information. to the server 10. Upon receiving the request, the contract confirmation unit 1043 of the server 10 receives the contract information concluded in the past with the first user, the contract information in the past with other users associated with the first group to which the first user belongs. , searches the document ID item of the confirmation table 1015 based on the document ID included in the contract information, and confirms the email of the user identified as the approver in the past in the contract information Get the address item. At this time, the user table 1012 and the group table 1013 may be referenced, and only the checker e-mail address of the user associated with the second group to which the third user belongs may be obtained. The contract confirmation unit 1043 of the server 10 searches the mail address item of the user table 1012 based on the obtained mail address, and obtains the user ID, user name, mail address, and approval authority items.
Based on the information specifying the third user, the item of the designated person data in the confirmation table 1015 is searched, and the confirmation person email address of the user identified as the approver in the past by the third user is acquired. The contract confirmation unit 1043 of the server 10 searches the mail address item of the user table 1012 based on the obtained mail address, and obtains the user ID, user name, mail address, and approval authority items.
The contract confirmation unit 1043 of the server 10 transmits to the third user terminal 40 the user ID, user name, and email address of the user who has approval authority. The display 4081 of the third user terminal 40 displays a list of user candidate information including the user name, mail address, etc. received in the user candidate presentation area 841 .

<Modification 1>
In presenting user candidates based on groups, presenting user candidates based on history (first embodiment), presenting user candidates based on history (second embodiment), and presenting user candidates based on other information, contract One or more users who can approve the information may be presented as candidate users in preference to one or more users who cannot approve the contract information.
Specifically, the contract confirmation unit 1043 of the server 10 may be configured to transmit to the third user terminal 40 the user IDs, user names, and email addresses of users without approval authority in addition to users with approval authority. good. In this case, the display 4081 of the third user terminal 40 presents the user candidate information with approval authority at a higher position in the list than the user candidate information without approval authority, thereby displaying the user candidate information with approval authority. You may present so that a 3rd user may select easily. In addition, when user candidate information is displayed by carousel or page turning, user candidate information having approval authority may be displayed on the first page.

<Modification 2>
The contract confirmation unit 1043 of the server 10 presents the user candidates based on the history (first embodiment) and presents the user candidates based on the history (second embodiment). It is also possible to preferentially present the fourth user who has been the fourth user the most frequently as a user candidate.
Specifically, the contract confirmation unit 1043 of the server 10 confirms the acquired user candidate information in the presentation of the user candidate based on the history (first embodiment) and the presentation of the user candidate based on the history (second embodiment). By counting the number (number of times) of duplicate user candidate information for each candidate user ID or e-mail address, and presenting the user candidate information with higher priority in order of priority based on the count, the third user or The user candidate information of users that have been selected and specified more frequently by a plurality of users belonging to the second group in the past may be presented so that the third user can easily select it. In addition, when user candidate information is displayed by carousel or page turning, it is conceivable to display user candidate information with a higher priority on the first page.

<Modification 3>
1 by combining presentation of user candidates based on groups, presentation of user candidates based on history (first embodiment), presentation of user candidates based on history (second embodiment), and presentation of user candidates based on other information A configuration may be adopted in which the user candidates are presented to the third user.

<Approver setting process>
The third user operates the input device 406 or the like of the third user terminal 40 and presses the add button 822 displayed on the second screen. A process of transmitting a request including the information entered in the access code 805 to the server 10 is executed.
The contract confirmation unit 1043 of the server 10 stores the e-mail address and the document ID included in the received request in the items of the confirmer e-mail address and the document ID of the new record in the confirmation table 1015, respectively. stored in association with the e-mail address of Note that the user ID or mail address of the third user may be stored in the designated person data item of the confirmation table 1015 . Thereby, the third user can receive the presentation of user candidates based on the history.
At this time, in the confirmation order field of the confirmation table 1015, the value of the confirmation order field of the user who is the confirmer is incremented by one and stored. As a result, the circulation order of confirmers in the contract confirmation process is set. Note that the setting of the circulation order is not essential.
The third user can specify and set one or more approvers by repeatedly executing the processes of steps S307 and S308. After completing the approver setting, the third user operates the input device 406 or the like of the third user terminal 40 and presses the cancel button 821 to end the approver setting process.

At this time, the contract confirmation unit 1043 of the server 10 may be configured to assign the input items assigned to the third user by the first user to the fourth user. In other words, the input item information assigned to the third user may be handed over to the approver designated by the third user.
Specifically, the contract confirmation unit 1043 of the server 10 searches the input person ID item of the input item table 1016 based on the third user ID, and adds the fourth user ID to the input person ID item of the specified record. Remember. The contract confirmation unit 1043 of the server 10 may be configured to delete the third user ID from the input person ID item of the specified record, store the fourth user ID, and overwrite the fourth user ID as the input person ID. good. The contract confirmation unit 1043 of the server 10 stores the fourth user ID without deleting the third user ID from the input person ID item of the specified record, and adds the fourth user ID as the input person ID. It is good as

In addition, when the third user specifies a plurality of fourth users as approvers, the third user requests a plurality of different fourth users for each of the plurality of input item information assigned to the third user by the first user. It is good also as a structure which allocates a user respectively.
Specifically, the third user operates the input device 406 or the like of the third user terminal 40, and enters the input person ID of the input item information record in which the third user ID is stored in the input person ID of the input item table 1016. The user IDs of each of a plurality of different fourth users are selectively added to the item and stored.

In step S309, the display 4081 of the third user terminal 40 presents the third screen to the third user for accepting an operation to confirm the contract information. The third user confirms the contract information displayed on the display 4081 of the third user terminal 40 .
Note that if there is no input item information assigned to the third user, step S309 may be omitted.

FIG. 20 is a screen example of the third screen showing the operation of the contract confirmation process. The third screen 70B for confirming the contract information displayed on the display 4081 of the third user terminal 40 differs from the first screen 70A in that the consent button 740 is not displayed and the save button 750 is displayed. Since the configuration is the same except that it is different, the description is omitted. In other words, a third user who does not have approval authority cannot consent to and approve the contract information.

In step S309, the contract confirmation unit 1043 of the server 10 accepts input for one or more input items of the contract information.
Specifically, the third user operates the input device 406 or the like of the third user terminal 40 to input input data to input items 732, 733, 734, and 735 set in the contract information. Note that, in the present disclosure, input by the third user is not assigned to the input item 736, so that the fact that the third user cannot input input data is visually identifiably displayed.

The third user operates the input device 406 or the like of the third user terminal 40 and presses the save button 750 to store the document ID, the information specifying the third user, and the input data for each input item input in step S309. to the server 10. Information specifying the third user may be the third user ID 4011 .
The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. As a result, the input data input by the third user is stored as input item information in the input item table 1016 in step S305.
At this time, since the third user does not have approval authority, the value of True is not stored in the confirmation flag field of the record of the third user in the confirmation table 1015 .

In step S310, the contract confirmation unit 1043 of the server 10 receives an instruction from the third user to request the fourth user to conclude a contract for the contract information.
Specifically, the contract creation unit 1042 of the server 10 transmits to the fourth user a message notifying that the third user has transmitted a request for approval of the contract information. For example, the contract confirmation unit 1043 of the server 10 transmits a message to the mail address of the fourth user by means of contact means such as mail, notifying that the third user has sent a request for approval of the contract information.
The message to be notified to the fourth user includes URL (Uniform Resource Locator) information including the document ID for specifying the contract information. The URL may directly contain the document ID, or may contain information such as a character string obtained by optionally encrypting the document ID, or a character string that can identify the document ID by referring to a table (not shown). good. Also, the URL may include information for specifying the fourth user. For example, if the fourth user has not registered as a user for the service according to the present disclosure, the URL needs to include information for specifying the fourth user.
Since the message notified to the fourth user terminal 41 is the same as in FIG. 16, the description is omitted.

When the third user sets the access code for the fourth user, the third user notifies the fourth user of the access code separately by means such as e-mail. As a result, even if a third party obtains the message to be notified to the fourth user, the third party cannot execute the contract verification process unless the third party obtains the access code.

<Details of contract confirmation processing (fourth user)>
In step S301, the fourth user who is the first confirmation user operates the input device 416 or the like of the fourth user terminal 41 to select the URL described in the received message, thereby opening the browser of the fourth user terminal 41. The application can open the web page specified by the URL. Accordingly, the fourth user terminal 41 transmits to the server 10 a request for executing the contract confirmation process.
The contract confirmation process for the fourth user is the same as the contract confirmation process for the third user, so the explanation is omitted. A fourth user who has approval authority can approve the contract information by executing the processes of steps S304, S305, and S306 of the contract confirmation process.

For example, in step S306, the contract confirmation unit 1043 of the server 10 can receive an instruction from one or more fourth users to approve the contract conclusion of the contract information received from the first user.
Then, the contract creation unit 1042 of the server 10 transmits a message to the first user's mail address by means of contact means such as mail, notifying that the second user has completed checking the contract information. That is, the first user is notified that the contract conclusion has been approved by the second user. Thereby, the first user can know that the contract conclusion has been completed with the second user. The second user can complete an appropriate contract conclusion procedure without the first user knowing that the contract conclusion has been approved by the fourth user via the third user in the organization to which the second user belongs. can. Note that the message may include the content of notifying that the fourth user has completed checking the contract information. Also, the message may include the content of notifying that the fourth user has completed the confirmation of the contract information via the third user.

In step S306, the contract confirmation unit 1043 of the server 10 may perform processing for notifying the second user that an instruction to approve conclusion of the contract has been received from the fourth user. Specifically, the contract confirmation unit 1043 of the server 10 transmits a message to the email address of the second user by communication means such as email to notify that the confirmation of the contract information has been completed by the fourth user.
Thereby, the second user can confirm by the notification that the contract information received for the second user as a target of contract conclusion has been approved by the fourth user.

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

Similarly, the contract confirmation unit 1043 of the server 10, in response to the instruction to approve the contract conclusion received from the fourth user in step S306, confirms that the contract information received from the first user has been approved for contract conclusion. An electronic signature indicating that is attached and stored.
The contract confirmation unit 1043 of the server 10 adds the electronic signature to the document ID, the email address of the first user, the email address of the fourth user, the date and time of approval, the date and time of confirmation, the authentication method of the date and time of approval, the authentication method of the date and time of confirmation, and the input items. Any information such as the value of the input data for each, the consent (approval) of the first user, the fourth user, a time stamp, etc. may be included.
As a result, the contract confirmation unit 1043 of the server 10 adds an electronic signature to the contract information indicating that the fourth user has approved the contract conclusion of the contract information, and stores the contract information. It is possible to prevent spoofing and falsification of contract information by a third party.

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

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

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

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

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

It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration to a plurality of computers 90 and connecting them to each other via a network. Thus, the computer 90 is a concept that includes not only the computer 90 housed in a single housing or case, but also a virtualized computer system.

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

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

The control unit is implemented by the processor 901 reading out various programs stored in the auxiliary storage device 903, developing them in the main storage device 902, and executing processing according to the programs. The control unit can implement functional units that perform various information processing according to the type of program. Thereby, the computer is implemented as an information processing device that performs information processing.

A storage unit is realized by the main storage device 902 and the auxiliary storage device 903 . The storage unit stores data, various programs, and various databases. Also, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to a program. In addition, the control unit can cause the processor 901 to execute addition, update, and deletion processing of data stored in the storage unit according to various programs.

A database refers to a relational database, and is used to manage tabular tables structurally defined by rows and columns, and data sets called masters in association with each other. In a database, a table is called a table, a master is called a column, and a row is called a record. In a relational database, relationships between tables and masters can be set and associated.
Normally, each table and each master has a primary key column for uniquely identifying a record, but setting a primary key to a column is not essential. The control unit can cause the processor 901 to add, delete, and update records in specific tables and masters stored in the storage unit according to various programs.

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

A communication unit is implemented by the communication IF 991 . The communication unit implements a function of communicating with another computer 90 via a network. The communication section can receive information transmitted from another computer 90 and input it to the control section. The control unit can cause the processor 901 to execute information processing on the received information according to various programs. Also, the communication section can transmit information output from the control section to another computer 90 .

<Appendix>
The items described in the above embodiments will be added below.

(Appendix 1)
A program, comprising 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 a contract from a first user. a contract receiving step (S101) for receiving contract information; a receiver receiving step (S102) for receiving second identification information as a receiver of the contract information received from the first user in the contract receiving step; and a transferring step (S106) of transferring the contract information received in the contract receiving step to one or more third users based on the second identification information.
Thereby, the contract information transmitted with respect to the second identification information can be transferred to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

(Appendix 2)
The second identification information is information for identifying the second user, and the recipient receiving step (S102) identifies the second user as the recipient of the contract information received from the first user in the contract receiving step. This is a step of receiving information, and the transfer step (S106) transfers the contract information received in the contract receiving step to one or more third users based on the information for specifying the second user received in the recipient receiving step. 1. The program of Appendix 1, which transfers.
Thereby, the contract information transmitted to the second user can be transferred to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

(Appendix 3)
The program according to appendix 2, wherein the first user belongs to a group different from that of the second user, and the second user and the third user belong to the same group.
Thereby, the contract information transmitted to the second user can be transferred to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

(Appendix 4)
Transfer notification step (S107) for notifying the processor that the contract information received in the contract receiving step has been transferred to one or more third users, to the second user received in the recipient receiving step. and the program according to appendix 2 or 3.
Thereby, the second user can confirm by the notification that the contract information accepted for the second user as a target of contract conclusion has been transferred to the third user.

(Appendix 5)
The program provides the processor with an approver receiving step (S308) for receiving, from the third user, information specifying one or more fourth users as approvers of the contract information received in the contract receiving step; and an approval step (S306) for receiving an instruction to approve the contract conclusion of the contract information received in the contract reception step from the 4 user, and the third user approves the contract conclusion of the contract information received in the contract reception step. 5. The program according to any one of appendices 2 to 4, wherein the user (S303) cannot
As a result, when the third user is a user who cannot approve the conclusion of a contract, it is possible to avoid approval of the conclusion of the contract by the third user, and the third user, who is the person in charge of the contact, can confirm the contents of the contract information. The contract information can be forwarded to a fourth user who is the appropriate approver based on.

(Appendix 6)
The program executes an approval notification step (S306) for notifying the second user accepted in the recipient acceptance step that an instruction to approve the conclusion of the contract has been accepted from the fourth user in the approval step to the processor. The program according to Supplementary Note 5 that causes the
Thereby, the second user can confirm by the notification that the contract information received for the second user to conclude a contract has been approved by the fourth user.

(Appendix 7)
The program causes the processor to add an electronic signature to the contract information received in the contract reception step indicating that the contract information has been approved in response to the instruction to approve the conclusion of the contract received from the fourth user in the approval step. Supplementary note 5 or 6 for executing a signature step (S306) of giving and storing, and a completion notification step (S306) of notifying the first user that the second user has approved the conclusion of the contract program.
Thereby, the first user can know that the contract conclusion has been completed with the second user. The second user can complete an appropriate contract conclusion procedure without the first user knowing that the contract conclusion has been approved by the fourth user via the third user in the organization to which the second user belongs. can.

(Appendix 8)
The program according to appendix 7, wherein the signature step (S306) is a step of adding an electronic signature to the contract information indicating that the fourth user has approved the contract conclusion of the contract information, and storing the electronic signature.
As a result, it is stored in the contract information that the fourth user who is the actual approval authority has approved the contract information.

(Appendix 9)
4. The program according to any one of appendices 1 to 3, wherein the program causes the processor to execute an approval step (S306) for receiving, from a third user, an instruction to approve the conclusion of the contract in the contract information received in the contract receiving step.
Thereby, the contract information transmitted to the second user can be transferred to the third user who is the predetermined contact person. The third user who is the contact person can forward the contract information to the appropriate approver based on the content of the contract information.

(Appendix 10)
The program causes the processor to add an electronic signature to the contract information received in the contract reception step indicating that the contract information has been approved in response to the instruction to approve the conclusion of the contract received from the third user in the approval step. The program according to Supplementary Note 9 for executing the signature step (S306) of adding and storing, and the completion notification step (S306) of notifying the first user that the second user has approved the conclusion of the contract. .
This allows the first user to know that the contract has been concluded with the second user. The second user can complete an appropriate contract conclusion procedure without the first user knowing that the contract conclusion has been approved by the third user in the organization to which the second user belongs.

(Appendix 11)
11. The program according to supplementary note 10, wherein the signature step (S306) is a step of adding an electronic signature to the contract information indicating that the third user has approved the contract conclusion of the contract information, and storing the electronic signature.
As a result, it is stored in the contract information that the third user who is the actual approval authority has approved the contract information.

(Appendix 12)
The forwarding step (S106) is a step of forwarding the contract information accepted in the contract accepting step to one or more third users identified based on predetermined conditions, based on the second user accepted in the recipient accepting step. 12. The program according to any one of Appendixes 2 to 11.
Thereby, the contract information transmitted to the second user can be transferred to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

(Appendix 13)
An information processing device comprising a processor and a storage unit, the information processing device causing the processor to execute the program according to any one of appendices 1 to 9.
Thereby, the contract information transmitted with respect to the second identification information can be transferred to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

(Appendix 14)
An information processing system including an information processing device comprising a processor and a storage unit, the information processing system causing the processor to execute the program according to any one of appendices 1 to 9.
Thereby, the contract information transmitted with respect to the second identification information can be transferred to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

(Appendix 15)
An information processing method executed by a computer comprising a processor and a storage unit, the information processing method comprising causing the processor to execute the program according to any one of Appendices 1 to 9.
Thereby, the contract information transmitted with respect to the second identification information can be transferred to the third user who is the predetermined contact person. The third user, who is the contact person, can approve the contract information himself or forward the contract information to an appropriate approver.

1 system, 10 server, 101 storage unit, 104 control unit, 106 input device, 108 output device, 20 first user terminal, 201 storage unit, 204 control unit, 206 input device, 208 output device, 30 second user terminal, 301 storage unit, 304 control unit, 306 input device, 308 output device, 40 third user terminal, 401 storage unit, 404 control unit, 406 input device, 408 output device, 41 fourth user terminal, 411 storage unit, 414 control part, 416 input device, 418 output device

Claims (14)

A program, comprising a processor and a storage unit, for causing a computer to execute electronic contract procedures between users belonging to different organizations,
The program causes the processor to:
a contract receiving step of receiving, from the first user, contract information for contract conclusion;
a receiver receiving step of receiving from the first user information for specifying a second user who is a receiver of the contract information received in the contract receiving step;
acquiring information for identifying one or more third users pre-associated with the information for identifying the second user based on the information for identifying the second user received in the recipient receiving step ; a transferring step of transferring the contract information received in the contract receiving step to one or more third users ;
program to run. The first user is a user belonging to a group different from the second user,
The second user and the third user are users belonging to the same group,
A program according to claim 1 . The program causes the processor to:
a transfer notification step of notifying the second user accepted in the recipient acceptance step that the contract information accepted in the contract acceptance step has been transferred to one or more third users;
3. The program according to claim 1 or 2, causing the execution of The program causes the processor to:
an approver receiving step of receiving from a third user information specifying one or more fourth users as approvers of the contract information received in the contract receiving step;
an approval step of receiving, from the one or more fourth users, an instruction to approve conclusion of a contract in the contract information received in the contract reception step;
and
the third user is a user who cannot approve the conclusion of the contract in the contract information received in the contract receiving step;
4. The program according to any one of claims 1 to 3 . The program causes the processor to:
an approval notification step of notifying the second user accepted in the recipient acceptance step that an instruction to approve the conclusion of the contract has been accepted from the fourth user in the approval step;
5. The program according to claim 4 , causing the execution of The program causes the processor to:
In response to the instruction to approve the conclusion of the contract received from the fourth user in the approval step, the contract information received in the contract reception step is given an electronic signature indicating that the conclusion of the contract in the contract information has been approved. a signature step stored as
a completion notification step of notifying the first user that the contract conclusion has been approved by the second user;
6. The program according to claim 4 or 5, causing the execution of The signing step is a step of adding an electronic signature to the contract information indicating that the fourth user has approved the conclusion of the contract of the contract information, and storing the electronic signature.
7. The program according to claim 6 . The program causes the processor to:
an approval step of receiving, from a third user, an instruction to approve conclusion of a contract in the contract information received in the contract reception step;
3. The program according to any one of claims 1 and 2, which executes The program causes the processor to:
In response to the instruction to approve the conclusion of the contract received from the third user in the approval step, the contract information received in the contract reception step is given an electronic signature indicating that the conclusion of the contract in the contract information has been approved. a signature step stored as
a completion notification step of notifying the first user that the contract conclusion has been approved by the second user;
9. The program according to claim 8 , causing the execution of The signing step is a step of adding an electronic signature to the contract information indicating that a third user has approved the conclusion of the contract of the contract information, and storing the electronic signature.
10. A program according to claim 9 . The forwarding step is associated with the predetermined condition when the information for identifying the second user accepted in the recipient accepting step and the contract information accepted in the contract accepting step match a specified condition. a step of acquiring information for specifying one or more third users, and transferring the contract information received in the contract receiving step to one or more third users;
A program according to any one of claims 1 to 10 . An information processing device comprising a processor and a storage unit,
Cause the processor to execute the program according to any one of claims 1 to 11 ,
Information processing equipment. An information processing system including an information processing device comprising a processor and a storage unit,
Cause the processor to execute the program according to any one of claims 1 to 11 ,
Information processing system that executes An information processing method executed by a computer comprising a processor and a storage unit,
Cause the processor to execute the program according to any one of claims 1 to 11 ,
Information processing methods.

Images