JP7249453B1 - Contract management program, information processing device, information processing system, information processing method - Google Patents

Abstract

[Problem] Contract information concluded by a user using an electronic contract service is stored and managed in each electronic contract service. It was necessary to manage it manually, and it was inconvenient for the user. [Solution] A reception step for receiving a request including an endpoint for identifying contract information stored in an external contract conclusion service, and a contract accessed based on the endpoint received in the reception step and identified by the endpoint. A contract management program for executing a contract acquisition step of acquiring information and a contract storage step of storing contract information acquired in the contract acquisition step. [Selection drawing] Fig. 22

Description

The present disclosure relates to a contract management 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 used to be paper media are 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 an information processing system communicably connected to an external system via a network.
Patent Literature 2 discloses a new account opening method and system that can reduce the time and effort required for account opening processing for financial institutions such as banks.
Patent Literature 3 discloses a technology that allows a buyer to collectively manage information on various commercial transactions conducted by the buyer and their settlements.

Japanese Patent Application Laid-Open No. 2022-023409 JP 2003-122922 A Japanese Patent Application Laid-Open No. 2005-317039

Some users may use multiple electronic contract services. In particular, in the electronic contract service, when concluding a contract, it is necessary for both parties to conclude the contract to use the same electronic contract service. Therefore, the contract information concluded by the user using the electronic contract service is stored and managed in each electronic contract service. It was necessary to manage, and the user's convenience was poor.
Accordingly, the present disclosure has been made to solve the above problems, and its purpose is to provide a user with a technique for conveniently using a plurality of electronic contract services.

A contract management program, comprising a processor and a storage unit, for storing electronic contract procedures between users in a computer, wherein the contract management program stores contract information stored in an external contract conclusion service in the processor a receiving step of receiving a request including an endpoint for specifying a contract obtaining step of accessing based on the endpoint received in the receiving step to obtain contract information identified by the endpoint; a contract storage step for storing contract information; and a contract management program for executing a contract storage step.

According to the present disclosure, users can conveniently use multiple electronic contract services.

2 is a block diagram showing the functional configuration of the 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 the functional configuration of an external server 40; FIG. 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 is a diagram showing the data structure of an access authority table 1017; FIG. FIG. 10 shows the data structure of a contract group table 1018. FIG. It is a flowchart which shows the operation|movement of a contract preparation process. 10 is a flowchart showing the operation of contract confirmation processing; It is a flowchart which shows the operation|movement of contract management processing (1st Example). It is a flowchart which shows the operation|movement of contract management processing (2nd Example). It is a flowchart which shows the operation|movement of contract management processing (3rd Example). It is an example of a screen which shows the operation|movement of contract creation processing. 3 is an example of a screen showing a confirmation request message notified to the second user terminal 30. FIG. It is an example of a screen which shows the operation|movement of a contract confirmation process. It is an example of a screen showing a conclusion completion message notified to the second user terminal 30 . It is an example of a screen showing the operation of contract management processing. 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 information processing system 1>
An information processing system 1 according to the present disclosure is an information processing system for realizing a service of storing and managing contract information concluded between a plurality of users.
The information processing system 1 includes a server 10, a first user terminal 20, a second user terminal 30, and an external server 40, which are information processing devices connected via a network N.
FIG. 1 is a block diagram showing the functional 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 external server 40. 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, and the external server 40, descriptions overlapping the basic hardware configuration of the computer and the basic functional configuration of the computer, which will be described later, will be omitted.

<Configuration of Server 10>
The server 10 is an information processing device that provides an electronic contract conclusion service among a plurality of users. The server 10 is an information processing device that provides a service of storing and managing contract information concluded between a plurality of users.
The server 10 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 , access authority table 1017 , and contract group table 1018 .

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. 6 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. Groups are defined by a group table 1013, which will be described later, and a user may belong to a plurality of 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.
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. 7 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, document data, creator ID, and endpoint columns with document ID as a primary key.
FIG. 8 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). Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
This is an item for storing a creator ID and user identification information for identifying a user who is a creator of contract information.
If the contract information is acquired from an external electronic contract service, the endpoint stores the endpoint for identifying the contract information in the external electronic contract service referred to when acquiring the contract information. It is an item to do. Specifically, a character string or the like for specifying a web page for the user to refer to the contract information, such as the URL of the page specifying the contract information, is stored.

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, confirmation person's email address, confirmation flag, language data, access code, and date and time.
FIG. 9 is a diagram showing the data structure of the confirmation table 1015. 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.
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 confirmation of the contract information, information indicating that the confirmation has been completed, such as a True value, is stored in the confirmation flag field.
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. 10 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 access authority table 1017 is a table for storing and managing information on access authority (access authority information).
The access authority table 1017 is a table having columns of user ID, service ID, and access token.
FIG. 11 shows the data structure of the access authority table 1017. As shown in FIG.

User ID is an item that stores user identification information for identifying a user.
Service ID is an item that stores service identification information for identifying a service. Specifically, the service ID stores a character string or the like for identifying the electronic contract service for each external electronic contract service.
An access token is an item that stores access authority information when a user accesses an external electronic contract service specified by a service ID. Specifically, the access token stores a character string issued to the user in the external electronic contract service. By sending an access token when accessing an external electronic contract service, the external electronic contract service identifies the user based on the character string of the access token and provides various information services to the user. . Access tokens may include authentication information, such as user IDs and passwords, that are required when logging in and accessing general web services.

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

Document ID is an item for storing document identification information for identifying contract information.
Cabinet ID stores cabinet identification information for identifying a cabinet. Cabinet ID is classification information for managing and classifying contract information.

<Configuration of Control Unit 104 of Server 10>
The control unit 104 of the server 10 includes a user registration control unit 1041 , a contract creation unit 1042 , a contract confirmation unit 1043 and a contract management unit 1044 . 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 or not 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.

The contract management unit 1044 executes contract management processing (first embodiment), contract management processing (second embodiment), and contract management processing (third embodiment). 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 application program 2012 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 application program 3012 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 External Server 40>
The external server 40 is an information processing device operated by a business entity different from the business entity that operates the electronic contract conclusion service according to the present disclosure. The external server 40 has a storage unit 401 and a control unit 404 . Each component included in the external server 40 is the same as each component included in the server 10, and detailed description thereof will be omitted.

<Configuration of Storage Unit 401 of External Server 40>
Storage unit 401 of external server 40 includes application program 4011 , user table 4012 , group table 4013 , document table 4014 , confirmation table 4015 and input item table 4016 .

<Configuration of Control Unit 404 of External Server 40>
The control unit 404 of the external server 40 includes a user registration control unit 4041 , a contract creation unit 4042 and a contract confirmation unit 4043 . Control unit 404 implements each functional unit by executing application program 4011 stored in storage unit 401 .

<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 flow chart showing the operation of contract management processing (first embodiment).
FIG. 16 is a flow chart showing the operation of contract management processing (second embodiment).
FIG. 17 is a flow chart showing the operation of contract management processing (third embodiment).
FIG. 18 is a screen example showing the operation of the contract creating process.
FIG. 19 is a screen example showing a confirmation request message notified to the second user terminal 30. As shown in FIG.
FIG. 20 is a screen example showing the operation of the contract confirmation process.
FIG. 21 is a screen example showing a conclusion completion message notified to the second user terminal 30 .
FIG. 22 is a screen example showing the operation of contract management processing.

In the present disclosure, contract creation processing and contract confirmation processing in the server 10 will be described below. The external server 40 can also execute similar contract creation processing and contract confirmation processing. The contract creation process and contract confirmation process in the external server 40 are the same as the contract creation process and contract confirmation process in the server 10, respectively, so the description thereof will be omitted.

<Contract creation process>
The contract creation process is a process in which the creator creates electronic contract information and transmits it to the confirmer.

FIG. 18 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 electronic contract information, sets the confirmation person who is the destination of the electronic contract information, sets the input items for the electronic contract information, sets the input rules for the input items, and sets the input rules for the input items. It is a series of processes for receiving input data for input items from and sending electronic contract information to the set confirmer.

<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 creating 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 first user operates the input device 206 or the like of the first user terminal 20 to select and specify a 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 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, the contract creating unit 1042 of the server 10 transmits to the second user a message notifying that the first user has sent a request to confirm the contract information. Specifically, the contract creating unit 1042 of the server 10 searches the confirmation order item of the confirmation table 1015, and the user (first confirmation user) who is the first confirmer with the smallest value stored in the confirmation order item. identify. In the present disclosure, the first confirmed user is assumed to be the second user as an example. The contract creating unit 1042 of the server 10 transmits a message to the second user's mail address by means of contact 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 second 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 second user. For example, if the second user has not registered as a user for the service according to the present disclosure, it is necessary to include information for specifying the second user in the URL.

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

FIG. 19 is a screen example showing a message notified to the second user terminal 30. As shown in FIG. The message screen 60 displayed on the display 3081 of the second user terminal 30 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 electronic contract information received from the creator.

<Outline of contract confirmation process>
The contract confirmation process receives access from the confirmer, presents the confirmation screen that displays the contract information to the confirmer, receives input data for the input items from the confirmer, and receives data related to confirmation of the contract information from the confirmer. It is a series of processing that accepts.

<Details of contract confirmation process>
In step S301, the second user, who is the confirmer, operates the input device 306 or the like of the second user terminal 30 to select the URL described in the received message. A web page specified by the URL can be opened. Thereby, the second user terminal 30 transmits to the server 10 a request for executing the contract confirmation process.

When the second user record in the confirmation table 1015 stores an access code item, the second user is requested to enter the access code, and the entered access code and the second user in the confirmation table 1015 are sent. An authentication process can be performed for the second 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 second user terminal 30 . The second user operates the input device 306 of the second user terminal 30 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 second 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 second user and acquires the approval authority information of the second user. The second user may be identified based on the second user ID 3011 included in the request received from the second user terminal 30, or identified based on the identification information for identifying the second user included in the URL. good. If the second user has not registered for the service according to the present disclosure, it is necessary to identify the second user from the URL. For example, the URL may include the second user's e-mail address, user ID, etc. as information for specifying the second user.

The contract confirmation unit 1043 of the server 10 searches for the item of user ID in the user table 1012 based on the specified user identification information of the second user, and acquires the item of approval authority of the second user. In the present disclosure, the approval authority of the second user is stored in the user table 1012, but the approval authority of the second user may be stored for each group to which the second user belongs, 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 second user for the target contract information.
In addition, if the second user has not registered as a user for the service according to the present disclosure, the process may be executed by regarding the second user as a user without approval authority.

In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, confirmer information (information specifying the second user), input item information, and confirmation authority information of the confirmer. 2 transmit to the user terminal 30;

Specifically, the display 3081 of the second user terminal 30 presents to the second user a confirmation screen for accepting an operation to approve the contract information. The second user confirms and approves the contract information displayed on the display 3081 of the second user terminal 30 .
Note that the confirmation screen presented to the second user is based on the language information stored in the item of language data of the record of the second user in the confirmation table 1015, and is written in the language specified for the confirmation person. It is good also as a structure which is shown to.

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

Specifically, the contract confirmation unit 1043 of the server 10 determines that, when the second user's approval authority information acquired in step S302 contains information that has the authority to approve the conclusion of the contract, the second user accepts It is determined that the user can approve the contract conclusion of the contract information, a confirmation screen is presented to the second user, and the process proceeds to step S304.

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

In step S304, the contract confirmation unit 1043 of the server 10 accepts input for one or more input items of the contract information.
Specifically, the second user operates the input device 306 or the like of the second user terminal 30 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 second user is not assigned to the input item 736, so that the fact that the second user cannot input input data is visually identifiably displayed.

In step S305, the contract confirmation unit 1043 of the server 10 receives from the second user an instruction to agree and approve the contract conclusion of the contract information received from the first user.
The second user confirms the contract information and input data displayed on the display 3081 of the second user terminal 30, and operates the input device 306 or the like of the second user terminal 30 when agreeing or consenting to the content. By pressing the consent button 740 displayed on the confirmation screen 70 for confirming the contract information, a request including the document ID, the information specifying the second user, and the input data for each input item input in step S305 is sent. The process of transmitting to the server 10 is executed. The information specifying the second user may be the second user ID 3011 .
The contract confirmation unit 1043 of the server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract confirmation unit 1043 of the server 10 searches the confirmation table 1015 based on the received document ID and the information specifying the second user, and stores the value of True in the confirmation flag field of the record. For example, if the information specifying the second user is an e-mail address, the items of the document ID and the e-mail address of the confirmer in the confirmation table 1015 are searched, and the value of True is stored in the item of the confirmation flag of the record. If the information that identifies the second user is the 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 second 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 having approval authority. Specifically, the contract confirmation unit 1043 of the server 10, in the confirmation table 1015, if the confirmation flag of the record of the confirmer with approval authority stores a value of True, all the confirmers with approval 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 is executed by all confirmers having approval authority. Similarly, the contract confirmation unit 1043 of the server 10 may transmit a message notifying that the contract confirmation process has been completed to the second user.

Specifically, the contract confirmation unit 1043 of the server 10 transmits a message to the email address of the first user by means of contact means such as email to notify that the confirmation of the contract information has been completed by the second user. 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 message to be notified to the first user may include the information of the URL, which is the endpoint, including the document ID for specifying the contract information.

FIG. 21 is a screen example showing a message notified to the first user terminal 20. As shown in FIG. The message screen 80 displayed on the display 2081 of the first user terminal 20 includes the information of the URL 82 including the document ID for specifying the message 81 and the contract information.

Similarly, the contract confirmation unit 1043 of the server 10 uses a chat service or the like (not shown) to send a message notifying that the second user has completed confirmation of the contract information, including a mention to the first user. You can That is, the first user is notified via the chat service 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 message to be notified to the first user may include the information of the URL, which is the endpoint, including the document ID for specifying the contract information.

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

When a plurality of users are set as confirmers, the contract confirmation unit 1043 of the server 10 notifies the user of the confirmer 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.
Note that the message may be sent via e-mail, chat service, or the like.
As a result, the manager of the group to which the confirming user belongs can be notified of the completion of the contract confirmation process.

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

<Electronic signature processing>
Electronic signature processing may be included in step S305. The contract confirmation unit 1043 of the server 10 indicates in the contract information received from the first user that the contract information has been approved in response to the instruction to approve the contract conclusion received from the second user in step S305. 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 electronic signature to the document ID, the first user's e-mail address, the second 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. Any information such as the value of the input data for each, the consent (approval) of the first user, the second 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 second 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.

Contract management processing (first embodiment), contract management processing (second embodiment), and contract management processing (third embodiment) will be described as follows. In addition, in the present disclosure, the contract management process by the first user is illustrated as an example, but the contract management process can be executed by the second user in the same manner as the first user.

<Contract management processing (first embodiment)>
The contract management process (first embodiment) is a process of acquiring, storing, and managing contract information stored in an external electronic contract service.

<Overview of contract management processing (first embodiment)>
The contract management process (first embodiment) receives an email indicating that a contract has been concluded in an external electronic contract service, accepts an endpoint for specifying contract information based on the email, and identifies a user. , acquires contract information from an external server, specifies a cabinet with which the contract information is associated, associates the cabinet with the contract information, and stores the contract information. In addition to e-mail, mail also includes a message service such as SMS (Short Message Service) that uses a telephone number as a destination.

<Details of contract management processing (first embodiment)>
Details of the contract management process (first embodiment) will be described below.

In step S501, the first user operates the input device 206 or the like of the first user terminal 20 to notify that the contract confirmation process received from the external server 40 in step S305 of the contract confirmation process has been completed. An email including a message is transferred to a predetermined email address for executing contract management processing according to the present disclosure.
It should be noted that the first user sends an email containing a message notifying that the contract confirmation process has been completed, which is sent from the external server 40 in step S305 of the contract confirmation process, in the external server 40. It may be set in advance so as to include a predetermined mail address for executing processing. With this setting, the first user can send a message notifying that the contract confirmation process has been completed to a predetermined e-mail address for executing the contract management process without forwarding the mail. You can send emails containing This can prevent the first user from forgetting to forward the mail.
The contract management unit 1044 of the server 10 receives an e-mail from the first user via a predetermined e-mail address for executing contract management processing. Specifically, the contract management unit 1044 of the server 10 accesses a mail server that manages a predetermined mail address for executing contract management processing, and receives mail.

In addition, the first user receives an email containing a message notifying that the contract confirmation process has been completed, which is received from the external server 40 in step S305 of the contract confirmation process. You may transfer to the mail address of the mail server etc. which do. Specifically, the email may be transferred to an email address having a domain name of the organization, company, etc., which is preset by the organization, company, etc. to which the first user belongs.
As a result, the first user is notified that the contract confirmation process received from the external server 40 has been completed, even if the organization, company, etc. to which the first user belongs imposes restrictions on forwarding mail to outside the company. You can forward mail that contains messages to
In this case, the contract management unit 1044 of the server 10 can access the mail server managed by the organization, company, etc. to which the first user belongs and receive the mail.

In step S502, the contract management unit 1044 of the server 10 executes a receiving step of receiving a request including an endpoint for specifying contract information stored in an external contract conclusion service. The accepting step executes a step of accepting an endpoint for identifying contract information stored in an external contract conclusion service from a user. The accepting step executes a step of accepting a request including the endpoint by receiving an e-mail describing the endpoint from the user.
Specifically, the contract management unit 1044 of the server 10 analyzes the message included in the mail received in step S501, and extracts the URL 82 including the document ID for specifying the predetermined contract information in the external server 40 included in the message. Identify and accept.
The contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc., and uses the message included in the received email as input data to determine the document ID for specifying the contract information. can be obtained and accepted as output data.

Note that the acceptance step is a step of accepting a request including an endpoint by receiving an email containing the endpoint from the user via an email address having the domain name of the organization or company to which the user belongs. may be executed.

In step S503, the contract management unit 1044 of the server 10 executes an authority acquisition step of acquiring access authority information for accessing the endpoint accepted in the acceptance step.

Specifically, the contract management unit 1044 of the server 10 retrieves the mail address item of the user table 1012 based on the mail address of the sender of the mail received in step S501, and acquires the user ID, thereby obtaining the user ID in step S501. to identify the first user who forwarded the mail.
If the endpoint identified in step S502 contains a character string for identifying the first user ID, the contract management unit 1044 of the server 10 forwards the mail in step S501 based on the character string. You may specify the 1st user who performed.
If the mail information such as the subject, text, and header information of the mail received in step S501 contains a character string for specifying the first user ID, the contract management unit 1044 of the server 10 For example, the first user who forwarded the mail in step S501 may be specified.
In addition, the contract management unit 1044 of the server 10, based on the mail information such as the subject, text, and header information of the mail received in step S501, the service identification information of the external electronic contract service provided by the external server 40. Identify the ID.
If the end point specified in step S502 contains a character string for specifying the service ID, the contract management unit 1044 of the server 10, based on the character string, etc., A service ID, which is service identification information of the electronic contract service, may be specified.

The contract management unit 1044 of the server 10 searches the user ID and service ID items of the access authority table 1017 based on the identified first user ID and service ID, and acquires the access token item. As a result, the contract management unit 1044 of the server 10 acquires access authority information for accessing the endpoint accepted in step S502, and proceeds to step S504.

In step S503, the authority obtaining step includes a notifying step of notifying the user or administrator when the access authority information for accessing the endpoint received in the receiving step cannot be obtained.
Specifically, the contract management unit 1044 of the server 10, based on the specified first user ID and service ID of the first user, the contract management unit 1044 of the server 10, the user ID and service ID items of the access authority table 1017 is searched, but if there is no corresponding record, it is determined that the access authority information for accessing the endpoint accepted in step S502 could not be acquired. At this time, the contract management unit 1044 of the server 10 transmits a message to the first user or the administrator of the group to which the first user belongs, notifying that the access authority information could not be acquired. The contract management unit 1044 of the server 10 stops the contract management process (first embodiment) and does not proceed to step S504.

Specifically, the contract management unit 1044 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 first user ID or email address of the first user. do. The contract management unit 1044 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 to notify that access authority information could not be obtained.

In step S503, the authority acquisition step includes a step of acquiring access authority information received after notification from the user or administrator notified in the notification step.
Specifically, the first user or administrator who has received the message notifying that the access authority information could not be acquired accesses a predetermined web page provided by the server 10, and accesses the first user's user ID, the service Access authority information can be transmitted to the server 10 by inputting an ID and an access token. The contract management unit 1044 of the server 10 stores the received user ID, service ID, and access token in the user ID, service ID, and access token items of the access authority table 1017, respectively.
As a result, the contract management unit 1044 of the server 10 can newly store in the access authority table 1017 the access authority information for accessing the endpoint received in step S502.
When the contract management unit 1044 of the server 10 detects that the access authority information for accessing the endpoint accepted in step S502 is stored, it acquires the access authority information, and proceeds to step S504.

In step S504, the contract management unit 1044 of the server 10 accesses based on the endpoint accepted in the acceptance step, and executes a contract acquisition step of acquiring contract information specified by the endpoint. The contract obtaining step accesses the endpoint received in the receiving step based on the access authority information obtained in the authority obtaining step, and executes a step of obtaining contract information.
Specifically, the contract management unit 1044 of the server 10 generates a request including the access token included in the access authority information acquired in step S503, and transmits the request to the endpoint accepted in step S502. Thereby, the contract management unit 1044 of the server 10 transmits the request to the external server 40 .

In step S504, the contract obtaining step detects that the access authority information has been obtained from the user or administrator after the notice is given in the authority obtaining step, and executes the step of obtaining the contract information.
Specifically, if it is determined in step S503 that the access authority information for accessing the endpoint could not be acquired, upon detecting that the access authority information has been stored by the first user or administrator, the server 10 The contract management unit 1044 generates a request including the access token included in the access authority information acquired in step S503, and transmits the request to the endpoint accepted in step S502. Thereby, the contract management unit 1044 of the server 10 transmits the request to the external server 40 .
If it is not detected that the access authority information has been stored by the first user or administrator, the contract management unit 1044 of the server 10 does not send the request.

The contract management unit 1044 of the server 10 receives and acquires contract information from the external server 40 as a response to the request.

Also, in step S504, the contract acquisition step accesses the endpoint accepted in the acceptance step based on the access authority information acquired in the authority acquisition step, and acquires a page written in a markup language such as a web page. The obtaining step, identifying a link associated with the contract information included in the page obtained by the page obtaining step, and accessing the identified endpoint to obtain the contract information may be performed.
Specifically, the external server 40 may transmit HTML (Hypertext Markup Language) such as a web page or XML as a response to a request. In such a case, the contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc., using HTML, XML, etc. received from the external server 40 as input data, A link for downloading the contract information may be obtained as output data, specified, and received and obtained by downloading the contract information from the link. Thereby, the contract management unit 1044 of the server 10 can acquire the contract information from the endpoint.

In step S505, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the e-mail address of the destination of the e-mail received in the reception step.
Specifically, the contract management unit 1044 of the server 10 refers to a table (not shown) or the like based on the destination mail address of the mail received in step S501, and identifies the cabinet ID associated with the mail address.
For example, in step S501, a plurality of e-mail addresses can be set in advance for each cabinet as predetermined e-mail addresses for executing contract management processing. For example, mail address A, mail address B, and mail address C are set in association with cabinet A, cabinet B, and cabinet C, respectively.
In step S501, the contract management unit 1044 of the server 10 identifies cabinet A when receiving mail from the first user via mail address A. Similarly, when contract management unit 1044 of server 10 receives mail from first user via mail address B and mail address C, it identifies cabinet B and cabinet C, respectively. Thereby, the first user can select the cabinet ID to which the contract information is associated by switching the forwarding destination of the mail, and can prevent forgetting to classify the contract information.
In addition, the first user can specify a plurality of e-mail addresses, in which case the contract information may be stored in association with cabinets corresponding to each of the plurality of e-mail addresses.

In step S505, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the e-mail address of the sender of the e-mail received in the reception step.
Specifically, the contract management unit 1044 of the server 10 refers to a table (not shown) based on the email address of the sender of the email received in step S501, and identifies the cabinet ID associated with the email address.
The contract management unit 1044 of the server 10 searches the mail address item of the user table 1012 based on the mail address of the sender of the mail received in step S501, acquires and identifies the user ID, and based on the user ID , a table (not shown) or the like may be referenced to identify the cabinet ID associated with the mail address.
For example, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID according to the department to which the first user belongs. For example, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID according to the position of the first user.
Thereby, it is possible to automatically assign a cabinet ID, which is predetermined classification information, to the information received from the first user and manage the information.

In step S505, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on at least one of the subject, text, or attached file of the e-mail received in the reception step.
Specifically, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID based on the mail information such as the subject, text, header information, and attached file of the mail received in step S501. For example, the contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc., and outputs the cabinet ID with the subject, text, header information, attached file, etc. as input data. It may be acquired as data and specified.

In step S505, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the contract information acquired in the contract acquisition step.
Specifically, the contract management unit 1044 of the server 10 collects the document data included in the contract information acquired in step S504, the type of contract such as non-disclosure agreement, research and development contract, outsourcing contract, etc. A predetermined cabinet ID may be specified based on the name and other incidental attribute information related to the contract information.

Also, in step S505, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the page acquired in the page acquisition step.
Specifically, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID based on page information such as HTML and XML received from the external server 40 in step S504. For example, the contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc. to acquire page information as input data and cabinet IDs as output data, and specify Also good.

Note that the contract management unit 1044 of the server 10 skips step S505 and advances to step S506 when the classification cannot be identified by the classification identification step.

In step S506, the contract management unit 1044 of the server 10 executes a contract storage step of storing the contract information acquired in the contract acquisition step. The contract storage step stores the contract information in association with the endpoint for specifying the contract information.
Specifically, the contract management unit 1044 of the server 10 converts the endpoint received in step S502 and the document data included in the contract information acquired in step S504 into the document data of the new record in the document table 1014, the end Store in the item of points. Note that the first user ID identified in step S503 may be stored in association with the contract information using a table (not shown) or the like.

In step S506, the contract management unit 1044 of the server 10 executes a classification storage step of associating the contract information stored in the storage step with the classification information identified in the classification identification step and storing the information.
Specifically, the contract management unit 1044 of the server 10 converts the document ID of the new record of the document table 1014 and the cabinet ID specified in step S505 into the document ID of the new record of the contract group table 1018, cabinet Stored in the ID item. Thereby, the contract management unit 1044 of the server 10 can store the contract information in association with the classification information.

In step S506, the contract storing step executes a step of storing the contract information attached to the e-mail received in the receiving step.
Specifically, document data in PDF format or the like may be attached to the message received from the external server 40 in step S305 of the contract confirmation process, notifying that the contract confirmation process has been completed. In such a case, the contract management unit 1044 of the server 10 acquires and identifies the attached document data from the mail received in step S501. The contract management unit 1044 of the server 10 stores the acquired document data in the document data item of the new record in the document table 1014 . Note that the first user ID identified in step S503 may be stored in association with the contract information using a table (not shown) or the like.
In this case, the contract management unit 1044 of the server 10 may store the endpoint received in step S502 in association with the document data in the document table 1014. FIG. In this case, the contract information acquisition process in step S504 may be omitted.

<Contract Management Processing (Second Embodiment)>
The contract management process (second embodiment) is a process of acquiring, storing, and managing contract information stored in an external electronic contract service.

<Overview of Contract Management Processing (Second Embodiment)>
The contract management process (second embodiment) receives a message indicating that a contract has been concluded in an external electronic contract service, accepts an endpoint for specifying contract information based on the message, and specifies a user. , acquires contract information from an external server, identifies a cabinet with which the contract information is associated, associates the cabinet with the contract information, and stores the contract information.

<Details of Contract Management Processing (Second Embodiment)>
Details of the contract management process (second embodiment) will be described below.

In step S501, the first user operates the input device 206 or the like of the first user terminal 20 to notify that the contract confirmation process received from the external server 40 in step S305 of the contract confirmation process has been completed. Send the contents of the mail including the message via the chat service. Chat services include Slack, chatwork, Microsoft Teams, LINE WORKS, and the like.
Specifically, the first user operates the input device 206 or the like of the first user terminal 20 to select a predetermined channel for executing the contract management process according to the present disclosure in the chat service, and In the channel, send a message including the subject and text of the email notifying that the contract confirmation process has been completed. A predetermined channel for executing the contract management process is created in advance by an administrator or the like in the group to which the first user belongs, and invites accounts associated with the first user, the server 10, etc. It is assumed that settings are made such that a user can transmit and post a message to a channel, and that the message posted by the first user can be acquired and read by the control unit 104 of the server 10 .
It should be noted that the first user automatically changes the subject and text of the email notifying that the contract confirmation process has been completed, which is sent from the external server 40 in step S305 of the contract confirmation process, to the external server 40. It may be set to automatically post to a predetermined channel for executing contract management processing related to disclosure. It is possible to prevent the first user from forgetting to transfer.
The contract management unit 1044 of the server 10 accesses the chat service, selects a predetermined channel for executing the contract management process according to the present disclosure, and executes the contract management process posted by the first user. Get and read the message of . Accordingly, the contract management unit 1044 of the server 10 receives the message for executing contract management processing.

In step S602, the accepting step executes a step of accepting a request including an endpoint by receiving a message describing the endpoint from the user via the chat service. The contract management unit 1044 of the server 10 executes a receiving step of receiving a request including an endpoint for specifying contract information stored in an external contract conclusion service. The accepting step executes a step of accepting an endpoint for identifying contract information stored in an external contract conclusion service from a user. The accepting step executes a step of accepting a request including an endpoint by receiving a message describing the endpoint from the user via the chat service.
Specifically, the contract management unit 1044 of the server 10 analyzes the message received via the chat service in step S601, and extracts the URL 82 containing the document ID for specifying the predetermined contract information in the external server 40 included in the message. identify and accept
The contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc., with the message as input data, and the URL 82 including the document ID for specifying the contract information as output data. can be obtained and accepted as

In step S603, the contract management unit 1044 of the server 10 executes an authority acquisition step of acquiring access authority information for accessing the endpoint accepted in the acceptance step.

Specifically, the contract management unit 1044 of the server 10 acquires the user ID of the first user associated via a table (not shown) or the like based on the account of the sender of the message received in step S601. The first user who sent the message is identified in step S601.
If the endpoint identified in step S602 contains a character string for identifying the first user ID, the contract management unit 1044 of the server 10 transmits a message in step S601 based on the character string. You may specify the 1st user who did.
If the message information such as the text of the message received in step S601 contains a character string for specifying the first user ID, the contract management unit 1044 of the server 10 performs step The first user who forwarded the mail in S601 may be specified.
Also, the contract management unit 1044 of the server 10 identifies the service ID, which is the service identification information of the external electronic contract service provided by the external server 40, based on the message information such as the text of the message received in step S601.
If the end point identified in step S602 contains a character string for identifying the service ID, the contract management unit 1044 of the server 10 determines the external A service ID, which is service identification information of the electronic contract service, may be specified.

The contract management unit 1044 of the server 10 searches the user ID and service ID items of the access authority table 1017 based on the identified first user ID and service ID, and acquires the access token item. As a result, the contract management unit 1044 of the server 10 acquires access authority information for accessing the endpoint accepted in step S602, and proceeds to step S604.

In step S603, the authority acquisition step includes a notification step of notifying the user or the administrator when the access authority information for accessing the endpoint accepted in the acceptance step cannot be acquired. In the present disclosure, the processing content is the same as that of step S503 of the contract management processing (first embodiment), so the description is omitted.

Since step S604 is the same as step S504 of the contract management process (first embodiment), description thereof is omitted.

In step S605, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the account information mentioned in the message received in the reception step.
Specifically, the contract management unit 1044 of the server 10 refers to a table (not shown) or the like based on the information specifying the destination of the message, which is called the mention included in the message received in step S601, and refers to the mention associated with the mention. Identify the cabinet ID.
For example, in step S601, the server 10 can preset a plurality of accounts for each cabinet as predetermined accounts for executing contract management processing in the chat service. For example, Account A, Account B, and Account C are set in association with Cabinet A, Cabinet B, and Cabinet C, respectively.
In step S601, the contract management unit 1044 of the server 10 identifies cabinet A when receiving a message mentioning account A from the first user. Similarly, when the contract management unit 1044 of the server 10 receives an email mentioning Account B and Account C from the first user, it identifies Cabinet B and Cabinet C, respectively. Thereby, the first user can select the cabinet ID with which the contract information is associated by switching the accounts to be mentioned in the message, thereby preventing forgetting to classify the contract information.
Note that the first user can mention a plurality of accounts, in which case the contract information may be stored in association with cabinets corresponding to each of the plurality of accounts.

In step S605, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the account information of the sender of the message received in the reception step.
Specifically, the contract management unit 1044 of the server 10 refers to a table (not shown) or the like based on the account of the transmission source of the message received in step S601, and identifies the cabinet ID associated with the account.
For example, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID according to the department to which the first user belongs. For example, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID according to the position of the first user.
Thus, the information received from the first user can be automatically assigned a cabinet ID, which is predetermined classification information, and managed.

In step S605, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on at least one of the body of the message received in the reception step and the attached file.
Specifically, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID based on the message information such as the text of the message received in step S601 and the attached file. For example, the contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc., to obtain the text, attached files, etc. as input data and the cabinet ID as output data, You can specify.

In step S605, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the contract information acquired in the contract acquisition step.
Specifically, the contract management unit 1044 of the server 10 collects the document data included in the contract information acquired in step S604, the contract type such as a non-disclosure agreement, research and development contract, outsourcing contract, etc. A predetermined cabinet ID may be specified based on the name and other incidental attribute information related to the contract information.

Also, in step S605, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the page acquired in the page acquisition step.
Specifically, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID based on page information such as HTML or XML received from the external server 40 in step S604. For example, the contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc. to acquire page information as input data and cabinet IDs as output data, and specify Also good.

Note that the contract management unit 1044 of the server 10 skips step S605 and advances to step S606 when the classification cannot be identified by the classification identification step.

Since step S606 is the same as step S506 of the contract management process (first embodiment), description thereof is omitted.

<Contract Management Processing (Third Embodiment)>
The contract management process (second embodiment) is a process of acquiring, storing, and managing contract information stored in an external electronic contract service.

<Overview of Contract Management Processing (Third Embodiment)>
The contract management process (third embodiment) identifies the user, periodically acquires a list of contract information that has been concluded from an external electronic contract service, and selects the contract information that has already been stored from the acquired list of contract information. Excluding the contract information that is stored, specifying the endpoint for acquiring the contract information, accepting the endpoint for specifying the contract information, acquiring the contract information from the external server, and specifying the cabinet with which to associate the contract information , is a series of processes for storing the relevant cabinet and contract information in association with each other.

<Details of contract management processing (third embodiment)>
Details of the contract management process (third embodiment) will be described below.

In step S701, the contract management unit 1044 of the server 10 identifies a user who executes contract management processing (third embodiment).
Specifically, the contract management unit 1044 of the server 10 refers to the access authority table 1017 and acquires access authority information including the user ID, service ID, and access token. In the present disclosure, contract management processing (third embodiment) for one predetermined user ID, service ID, and access token will be described for the sake of simplicity.
Note that the contract management unit 1044 of the server 10 may execute contract management processing (third embodiment) for each acquired user ID, service ID, and access token.

The contract management process (third embodiment) may be configured to be automatically executed at predetermined intervals. The contract management process (third embodiment) may be configured to be executed according to instructions from the user or administrator.

In step S702, the contract management unit 1044 of the server 10 executes a list acquisition step of acquiring a list of one or more endpoints associated with one or more pieces of contract information that can be referenced by the user. The list acquisition step is automatically executed at predetermined intervals. Also, the list obtaining step may be configured to be executed according to an instruction from the user or administrator.
Specifically, based on the service ID acquired in step S701, the contract management unit 1044 of the server 10 refers to a table (not shown) or the like to determine an endpoint (list acquisition endpoint) for acquiring the contract information list. Identify and get. A list acquisition endpoint is a character string such as a URL for specifying a web page for a user to refer to and acquire a list of contract information. Also, the list acquisition endpoint may be acquired by accessing a predetermined API (Application Programming Interface) provided by an external contract conclusion service identified by a service ID.
For example, the list acquisition endpoint is a character string such as a URL such as "https://contract.service/get_all_documents/".

The contract management unit 1044 of the server 10 accesses the list acquisition endpoint based on the access authority information acquired in step S701, and executes a step of acquiring the contract information list.
Specifically, the contract management unit 1044 of the server 10 generates a request including the access token included in the access authority information acquired in step S701, and transmits the request to the list acquisition endpoint. Thereby, the contract management unit 1044 of the server 10 transmits the request to the external server 40 .
Upon receiving the request, the external server 40 identifies the user ID based on the access token. Based on the specified user ID, the external server 40 searches the item of the creator ID in the document table 4014 and acquires the document ID. Similarly, the external server 40 retrieves the user ID item of the user table 4012 of the external server 40 based on the specified user ID, and acquires the mail address. The external server 40 searches the confirmation table 4015 of the external server 40 for the confirmation person email address based on the acquired email address, and acquires the document ID.
The external server 40 generates, specifies, and acquires an endpoint for each document ID based on one or more acquired document IDs. The external server 40 transmits one or more document IDs and an endpoint for each document ID to the server 10 as a response to the request.
The contract management unit 1044 of the server 10 receives and acquires a list of contract information (contract list information) from the external server 40 as a response to the request.

In step S703, the contract management unit 1044 of the server 10 selects one or more exclusion target endpoints corresponding to the contract information already stored in the contract storage step among the one or more endpoints obtained in the list obtaining step. perform an exclusion identification step that identifies the
Specifically, the contract management unit 1044 of the server 10 searches for endpoint items in the document table 1014 based on one or more endpoints acquired in step S702, and finds that the endpoint is already stored in the document table 1014. determine whether or not there is The contract management unit 1044 of the server 10 excludes the endpoints already stored in the endpoint item of the document table 1014 from among the one or more endpoints acquired in step S702. As a result, contract information already stored in the document table 1014 can be excluded from acquisition targets.

In step S704, the contract management unit 1044 of the server 10 executes a contract identification step of identifying at least one predetermined endpoint included in the one or more endpoints obtained in the list obtaining step.

In step S704, the contract identifying step identifies at least one predetermined endpoint from the one or more endpoints obtained in the list obtaining step excluding the exclusion target endpoints identified in the exclusion identifying step. perform the steps to
Specifically, the contract management unit 1044 of the server 10 specifies the contract information by excluding the endpoints already stored in the document table 1014 in step S703 from among the one or more endpoints acquired in step S702. .

In step S705, the accepting step executes a step of accepting a request including the predetermined endpoint specified in the contract specifying step.
Specifically, the contract management unit 1044 of the server 10 accepts one or more endpoints identified in step S703.

In step S706, the contract management unit 1044 of the server 10 accesses based on the one or more endpoints accepted in the acceptance step, and acquires one or more pieces of contract information specified by the one or more endpoints. Execute the step.
The contract obtaining step accesses the endpoint received in the receiving step based on the access authority information obtained in the authority obtaining step, and executes a step of obtaining contract information.
Specifically, the contract management unit 1044 of the server 10 generates a request including the access token included in the access authority information acquired in step S701, and transmits the request to the endpoint accepted in step S705. Thereby, the contract management unit 1044 of the server 10 transmits the request to the external server 40 .
The contract management unit 1044 of the server 10 receives and acquires one or more pieces of contract information from the external server 40 as a response to the request.

Further, in step S706, the contract acquisition step accesses the endpoint accepted in the acceptance step based on the access authority information acquired in the authority acquisition step, and acquires a page written in a markup language such as a web page. The obtaining step, identifying a link associated with the contract information included in the page obtained by the page obtaining step, and accessing the identified endpoint to obtain the contract information may be performed.
Specifically, the external server 40 may transmit HTML (Hypertext Markup Language) such as a web page or XML as a response to a request. In such a case, the contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc., and uses HTML, XML, etc. received from the external server 40 as input data, A link for downloading the contract information may be obtained as output data, specified, and received and obtained by downloading the contract information from the link. Thereby, the contract management unit 1044 of the server 10 can acquire the contract information from the endpoint.

In step S707, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the user ID identified in step S701.
Specifically, the contract management unit 1044 of the server 10 refers to a table (not shown) or the like based on the user ID specified in step S701, and specifies the cabinet ID associated with the user ID.
For example, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID according to the user's department or the like. For example, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID according to the user's position or the like.
Thereby, it is possible to automatically assign a cabinet ID, which is predetermined classification information, to information received from a user and manage the information.

In step S707, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the contract information acquired in the contract acquisition step.
Specifically, the contract management unit 1044 of the server 10 collects the document data included in the contract information acquired in step S706, the type of contract such as non-disclosure agreement, research and development contract, outsourcing contract, etc. included in the document data, A predetermined cabinet ID may be specified based on the name and other incidental attribute information related to the contract information.
In the present disclosure, a configuration may be adopted in which different cabinet IDs are specified for each piece of contract information.

Also, in step S707, the contract management unit 1044 of the server 10 executes a classification identification step of identifying classification information based on the page acquired in the page acquisition step.
Specifically, the contract management unit 1044 of the server 10 may specify a predetermined cabinet ID based on page information such as HTML and XML received from the external server 40 in step S706. For example, the contract management unit 1044 of the server 10 uses pattern matching such as regular expressions, arbitrary machine learning, deep learning models, etc. to acquire page information as input data and cabinet IDs as output data, and specify Also good.
In the present disclosure, a configuration may be adopted in which different cabinet IDs are specified for each piece of contract information.
Note that the contract management unit 1044 of the server 10 skips step S707 and advances to step S708 when the classification cannot be identified by the classification identification step.

In step S708, the contract management unit 1044 of the server 10 executes a contract storage step of storing one or a plurality of pieces of contract information acquired in the contract acquisition step. The contract storing step stores the one or more pieces of contract information in association with endpoints for specifying the one or more pieces of contract information.
Specifically, the contract management unit 1044 of the server 10 converts the one or more endpoints accepted in step S705 and the one or more document data included in the one or more contract information acquired in step S706 into document It is stored in the document data and endpoint items of the new record in the table 1014 . Note that the user ID specified in step S701 may be stored in association with the contract information using a table (not shown) or the like.

In step S708, the contract management unit 1044 of the server 10 stores the one or more pieces of contract information stored in the storage step in association with the one or more pieces of classification information identified in the classification identification step. to run.
Specifically, the contract management unit 1044 of the server 10 stores the one or more document IDs of the new record in the document table 1014 and the one or more cabinet IDs identified for each document ID in step S707 as contract documents. Stored in the document ID and cabinet ID items of the new record in the group table 1018 . Thereby, the contract management unit 1044 of the server 10 can store the contract information in association with the classification information.

In the present disclosure, the user can display the contract information stored in the storage unit 101 of the server 10 by contract management processing by accessing the server 10 using the user terminal. In the present disclosure, the processing by the first user is illustrated as an example, but the second user can also perform the processing in the same way as the first user.
The first user inputs a predetermined URL by operating the input device 206 or the like of the first user terminal 20 in the browser application of the first user terminal 20 . The control unit 204 of the first user terminal 20 transmits to the server 10 a request for listing the contract information. Upon receiving the request, the server 10 acquires one or more pieces of contract information associated with the first user from the document table 1014 and transmits them to the first user terminal 20 . Specifically, the contract information to be transmitted to the first user terminal 20 may include the document ID and the storage date and time of the contract information in the document table 1014 .
The control unit 204 of the first user terminal 20 displays the received one or more pieces of contract information on the display 2081 or the like of the first user terminal 20, and displays the contract information before the conclusion of the contract acquired from the external contract conclusion service as the first contract information. Presented to 1 user.

FIG. 22 is a screen example of a list display screen 84 showing contract information displayed in a list on the first user terminal 20 .
The list display screen 84 includes a table 841 that displays a list of contract information in a list format. In the table 841, contract information 851, 852, . . . are displayed in list form for each row. The table 841 includes, for each piece of contract information 851, drawing objects 8511 such as icons for selecting contract information, document IDs 8512, storage dates 8513, acquisition sources 8515, and other drawing objects.
The first user can confirm the contract information stored in the document table 1014 by operating the input device 206 of the first user terminal 20 or the like to select the drawing object 8511 . For example, when the first user operates the input device 206 of the first user terminal 20 or the like to select the drawing object 8511 , the request including the document ID is transmitted to the server 10 . Based on the received document ID, the contract management unit 1044 of the server 10 retrieves the item of the document ID in the document table 1014 and the confirmation table 1015, acquires the contract information and the confirmer information, generates the confirmation screen, and displays the confirmation screen on the first user terminal. 20.
Specifically, the display 2081 of the first user terminal 20 presents the first user with a confirmation screen for accepting an operation to approve the contract information. The confirmation screen is similar to the confirmation screen 70 of the contract confirmation process shown in FIG. 20, but the consent button 740 is hidden or cannot be selected.
Thereby, the first user can view and check the contract information stored by the contract management process.

<Basic computer hardware configuration>
FIG. 23 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/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. 23) 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 for managing 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 contract management program, comprising a processor and a storage unit, for storing electronic contract procedures between users in a computer, wherein the contract management program stores contract information stored in an external contract conclusion service in the processor and a contract acquisition step ( S504, S604, S706) and a contract storage step (S506, S606, S708) for storing the contract information acquired in the contract acquisition step.
Thereby, it is possible to store and manage contract information concluded in an external contract conclusion service. Specifically, contract information concluded through a plurality of external contract conclusion services can be acquired, stored, and managed.

(Appendix 2)
The contract management program according to supplementary note 1, wherein the receiving step (S502, S602) is a step of receiving from a user an endpoint for specifying contract information stored in an external contract conclusion service.
This makes it possible to acquire, store, and manage contract information concluded in an external contract conclusion service specified by the endpoint received from the user.

(Appendix 3)
The contract management program according to appendix 2, wherein the accepting step (S502) is a step of accepting a request including an endpoint by receiving an e-mail describing the endpoint from a user.
This makes it possible to store and manage contract information concluded in an external contract conclusion service specified by an endpoint received from a user via e-mail. The user can acquire, store, and manage contract information without performing special settings.

(Appendix 4)
The accepting step (S502) is a step of accepting a request including an endpoint by receiving an email containing the endpoint from the user via an email address having the domain name of the organization or company to which the user belongs. The contract management program according to Supplementary Note 3.
This makes it possible to store and manage contract information concluded in an external contract conclusion service specified by an endpoint received from a user via a chat service. The user can acquire, store, and manage contract information without performing special settings.

(Appendix 5)
The contract management program according to appendix 2, wherein the accepting step (S602) is a step of accepting a request including an endpoint by receiving a message describing the endpoint from a user via a chat service.
As a result, the user can acquire, store, and manage contract information concluded in an external contract conclusion service without performing any special operation.

(Appendix 6)
The contract management program instructs the processor to acquire a list of one or more endpoints associated with each of the one or more pieces of contract information that can be referenced by the user (S702); a contract identification step (S704) for identifying at least one predetermined endpoint included in one or more endpoints; 1. The contract management program of Claim 1, wherein the step of accepting a request comprising:
As a result, it is possible to acquire, store, and manage contract information concluded in an external contract conclusion service, excluding already stored contract information.

(Appendix 7)
The contract management program instructs the processor to specify one or more exclusion target endpoints corresponding to the contract information already stored in the contract storage step among the one or more endpoints obtained in the list obtaining step. step (S703), and the contract specifying step (S704) includes one or more endpoints acquired in the list acquisition step, excluding endpoints to be excluded specified in the exclusion specifying step, 7. The contract management program of clause 6, the step of identifying at least one predetermined endpoint.
As a result, the user can periodically acquire, store, and manage contract information concluded in an external contract conclusion service without performing any special operation.

(Appendix 8)
6. The contract management program according to appendix 6, wherein the list obtaining step (S702) is automatically executed at predetermined intervals.
As a result, according to the contents of the contract information, the user can specify the desired e-mail address as the destination and send the message including the endpoint by e-mail. Information can be sorted and stored without special manipulation or the like.

(Appendix 9)
6. The contract management program according to appendix 6, wherein the list obtaining step (S702) is executed according to an instruction from a user or an administrator.
Thereby, according to the user's e-mail address, the contract information concluded in the external contract conclusion service can be classified and stored without performing any special operation.

(Appendix 10)
The contract management program instructs the processor to perform a category specifying step (S505) of specifying category information based on the email address of the destination of the email received in the receiving step; and a classification storage step (S506) of correlating and storing the classification information specified in the contract management program according to appendix 3.
As a result, the contract information concluded by the external contract conclusion service can be classified and stored according to the subject, text, attached file, etc. of the user's e-mail without performing any special operation.

(Appendix 11)
The contract management program instructs the processor to perform a classification identification step (S505) for identifying classification information based on the e-mail address of the sender of the e-mail received in the receiving step; and a classification storage step (S506) of correlating and storing the classification information specified in the contract management program according to appendix 3.
As a result, according to the contents of the contract information, the user mentions the desired account information and sends a message that includes the endpoint using the chat service, so that the contract information concluded in the external contract conclusion service can be treated as a special It can be sorted and stored without any manipulation or the like.

(Appendix 12)
The contract management program provides the processor with a classification identification step (S505) for identifying classification information based on at least one of the subject, text, or attached file of the e-mail received in the reception step, and the contract information stored in the storage step. , a classification storage step (S506) for storing in association with the classification information identified in the classification identification step (S506).
Thereby, the contract information concluded in the external contract conclusion service can be classified and stored according to the user's account information without performing a special operation.

(Appendix 13)
The contract management program provides the processor with a category specifying step (S605) for specifying category information based on the account information mentioned in the message received in the receiving step, and specifying the contract information stored in the storing step in the category specifying step. and a classification storage step (S606) for storing the classified information in association with each other.
This makes it possible to store and manage contract information without accessing the endpoint.

(Appendix 14)
The contract management program instructs the processor to perform a classification identification step (S605) for identifying classification information based on the account information of the sender of the message received in the receiving step, and associate the classification information with the contract information stored in the storing step. The contract management program according to Supplementary Note 5, which executes a classification storing step (S606) for storing.
This allows the contract information to be stored in association with the endpoint. For example, it is possible to prevent double registration of contract information associated with the same endpoint.

(Appendix 15)
3. The contract management program according to appendix 3, wherein the contract storing step (S506) is a step of storing the contract information attached to the e-mail received in the receiving step.
As a result, when receiving a request that includes an endpoint that does not have access authority information for accessing contract information, the user or administrator can set appropriate access authority according to the prescribed notification. can.

(Appendix 16)
The contract management program according to appendix 1, wherein the contract storage step (S506, S606, S708) stores the contract information in association with an endpoint for specifying the contract information.
As a result, when a request including an endpoint that does not have access authority information for accessing contract information is received, an external contract conclusion service can conclude in response to the acceptance of access authority information from the user or administrator. contract information can be stored and managed.

(Appendix 17)
The contract management program causes the processor to execute an authority acquisition step (S503, S603, S701) for acquiring access authority information for accessing the endpoint accepted in the acceptance step, and a contract acquisition step (S504, S604, S701). S706) is a step of accessing the endpoint accepted in the receiving step based on the access authority information acquired in the authority acquiring step and acquiring contract information. 1. The contract management program according to supplementary note 1, comprising a notification step of notifying a user or an administrator when access authority information for accessing the endpoint accepted in 1. cannot be acquired.
Thereby, it is possible to store and manage contract information concluded in an external contract conclusion service. Specifically, contract information concluded through a plurality of external contract conclusion services can be acquired, stored, and managed.

(Appendix 18)
The contract management program instructs the processor that the authority acquisition step (S503, S603, S701) acquires access authority information received after the notification from the user or administrator notified in the notification step. and the contract acquisition step (S504, S604, S706) is a step of acquiring contract information by detecting that access authority information has been acquired from a user or administrator after notification is made in the authority acquisition step. 17. The contract management program according to Supplementary Note 17.
Thereby, it is possible to store and manage contract information concluded in an external contract conclusion service. Specifically, contract information concluded through a plurality of external contract conclusion services can be acquired, stored, and managed.

(Appendix 19)
19. An information processing device comprising a processor and a storage unit, the information processing device causing the processor to execute the contract management program according to any one of Appendices 1 to 18.
Thereby, it is possible to store and manage contract information concluded in an external contract conclusion service. Specifically, contract information concluded through a plurality of external contract conclusion services can be acquired, stored, and managed.

1 information processing system, 10 server, 101 storage unit, 104 control unit, 106 input device, 108 output device, 20 first user terminal, 201 storage unit, 204 control unit, 206 input device, 208 output device, 30 second user terminal, 301 storage unit, 304 control unit, 306 input device, 308 output device

Claims (20)

A contract management program capable of providing a predetermined contract management service relating to electronic contract procedures between users to a computer comprising a processor and a storage unit,
The contract management program causes the processor to:
a receiving step of receiving a request including an endpoint for specifying contract information stored in an external contract conclusion service different from the predetermined contract management service ;
a contract acquisition step of accessing based on the endpoint accepted in the acceptance step and acquiring the contract information specified by the endpoint;
a contract storage step for storing the contract information acquired in the contract acquisition step;
an authority acquisition step of acquiring access authority information for accessing the endpoint accepted in the acceptance step;
and
the contract acquisition step is a step of accessing the endpoint accepted in the acceptance step based on the access authority information acquired in the authority acquisition step to acquire the contract information;
The authority acquisition step includes a notification step of notifying a user or an administrator when the access authority information for accessing the endpoint accepted in the acceptance step cannot be acquired,
Contract management program. The receiving step is a step of receiving, from a user, an endpoint for specifying contract information stored in the external contract conclusion service.
The contract management program according to claim 1. The accepting step is a step of accepting the request including the endpoint by receiving an e-mail describing the endpoint from the user.
The contract management program according to claim 2. In the receiving step, the request including the endpoint is received from the user via an email address having a domain name of the organization or company to which the user belongs, and the email containing the endpoint is received. is a step that accepts
The contract management program according to claim 3. The accepting step is a step of accepting the request including the endpoint by receiving a message describing the endpoint from the user via a chat service.
The contract management program according to claim 2. The contract management program causes the processor to:
a list obtaining step of obtaining a list of one or more endpoints associated with each of the one or more pieces of contract information that can be referenced by a user;
a contract identification step of identifying at least one predetermined endpoint included in the one or more endpoints obtained in the list obtaining step;
and
The accepting step is a step of accepting the request including the predetermined endpoint specified in the contract specifying step,
The contract management program according to claim 1. The contract management program causes the processor to:
an exclusion identification step of identifying one or more exclusion target endpoints corresponding to the contract information already stored in the contract storage step among the one or more endpoints obtained in the list obtaining step;
and
In the contract specifying step, at least one of the predetermined endpoints is selected from the one or more endpoints obtained in the list obtaining step, excluding the exclusion target endpoints identified in the exclusion specifying step. is the step of identifying
The contract management program according to claim 6. The list obtaining step is automatically executed at predetermined intervals,
The contract management program according to claim 6. The list acquisition step is executed in response to an instruction from the user or administrator,
The contract management program according to claim 6. The contract management program causes the processor to:
a classification identifying step of identifying classification information based on the destination email address of the email received in the receiving step;
a classification storage step for storing the contract information stored in the contract storage step in association with the classification information identified in the classification identification step;
to run
The contract management program according to claim 3. The contract management program causes the processor to:
a classification identification step of identifying classification information based on the email address of the sender of the email received in the reception step;
a classification storage step for storing the contract information stored in the contract storage step in association with the classification information identified in the classification identification step;
to run
The contract management program according to claim 3. The contract management program causes the processor to:
a classification identification step of identifying classification information based on at least one of the subject, text or attached file of the e-mail received in the reception step;
a classification storage step for storing the contract information stored in the contract storage step in association with the classification information identified in the classification identification step;
to run
The contract management program according to claim 3. The contract management program causes the processor to:
a classification identifying step of identifying classification information based on the account information mentioned in the message received in the receiving step;
a classification storage step for storing the contract information stored in the contract storage step in association with the classification information identified in the classification identification step;
to run
The contract management program according to claim 5. The contract management program causes the processor to:
a classification identifying step of identifying classification information based on the account information of the sender of the message received in the receiving step;
a classification storage step for storing classification information in association with the contract information stored in the contract storage step;
to run
The contract management program according to claim 5. The contract storage step is a step of storing the contract information attached to the e-mail received in the reception step.
The contract management program according to claim 3. The contract storage step stores the contract information in association with an endpoint for specifying the contract information.
The contract management program according to claim 1. The contract management program causes the processor to:
The authority acquisition step includes a step of acquiring the access authority information received after the notification from the user or administrator notified in the notification step,
The contract acquisition step is a step of acquiring the contract information by detecting that the access authority information has been acquired from the user or administrator after the notification is made in the authority acquisition step.
The contract management program according to claim 1. An information processing device comprising a processor and a storage unit,
causing the processor to execute the contract management program according to any one of claims 1 to 17;
Information processing equipment. An information processing system including an information processing device comprising a processor and a storage unit,
An information processing system that causes the processor to execute the contract management program according to any one of claims 1 to 17. An information processing method executed by a computer comprising a processor and a storage unit,
causing the processor to execute the contract management program according to any one of claims 1 to 17;
Information processing methods.

Images