JP2024002663A - Contract management program, information processing apparatus, information processing system, information processing method, and information processing terminal - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a contract management program for organizing and managing contract information made for each policyholder, in electronic contract procedures between multiple users, an information processing apparatus, an information processing system, an information processing method, and an information processing terminal.

SOLUTION: In a system comprising a server 10 and a plurality of user terminals 20, a contract management program for causing the server to store electronic contract procedures between users causes a processor to execute: a contract storage step of storing contract information related to a contract; a policyholder storage step of specifying one or more pieces of policyholder information on policyholders of the contract and storing the specified one or more pieces of policyholder information in association with the contract information; and a list presentation step of presenting a list of the one or more pieces of policyholder information stored in the policyholder storage step, in association with the associated one or more pieces of contract information.

SELECTED DRAWING: Figure 1

COPYRIGHT: (C)2024,JPO&INPIT

Description

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

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

JP2017-10096 JP2020-190905

In electronic contract procedures between multiple users, there is a problem in that it is not possible to organize and manage what kind of contract information is concluded for each contracting party.
Therefore, the present disclosure has been made to solve the above problems, and its purpose is to provide a technology for organizing and managing what kind of contract information is concluded for each contracting party.

A contract management program for storing electronic contract procedures between users in a computer, comprising a processor and a storage unit, the processor comprising: a contract storage step for storing contract information regarding the contract; A party storage step in which one or more party information is identified and the identified one or more party information is stored in association with contract information, and each of the one or more party information stored in the party storage step is associated with A contract management program that executes a list presentation step of linking one or more contract information and presenting a list.

According to the present disclosure, it is possible to organize and manage what kind of contract information is concluded for each contracting party.

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

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

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

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

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

<Configuration of storage unit 101 of server 10>
The storage unit 101 of the server 10 includes an application program 1011, a user table 1012, a group table 1013, a document table 1014, a confirmation table 1015, an input item table 1016, a contract group table 1017, and a clause 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 about member users (hereinafter referred to as users) who use the service. When a user registers to use a service, the user's information is stored in a new record in the user table 1012.
This allows the user to use the service according to the present disclosure. Note that in the present disclosure, users who use services do not necessarily need to be registered in the user table 1012.
The user table 1012 is a table having user ID as a primary key and columns of user ID, user name, email address, group ID, and approval authority.
FIG. 5 is a diagram showing the data structure of the user table 1012.

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

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

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

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

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

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

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

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

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

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

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

The clause table 1018 is a table for storing and managing information regarding clauses (clause information) extracted from document data included in contract information. In the present disclosure, clauses are extracted on a clause-by-clause basis from contract information that defines a contract included in document data and stored in the clause table 1018.
The clause table 1018 is a table having columns of document ID, clause ID, clause heading, clause type, and clause data, with clause ID as the primary key.
FIG. 11 is a diagram showing the data structure of the clause table 1018.

The document ID is an item that stores document identification information from which clause information is extracted.
The clause ID is an item that stores clause identification information for identifying a clause. The clause identification information is an item in which a unique value is set for each clause information.
The article heading is an item that stores information regarding the article heading of the article (article heading information). For example, character strings such as confidentiality, compensation for damages, cancellation of contract, and restoration to original condition are stored as article headings.
The clause type is an item that stores information regarding the type of clause (clause type information). For example, the clause type includes information regarding the content imposed on the parties to the contract by the clause, such as rights and obligations. Specifically, it includes information regarding the rights and obligations imposed on each party based on party data regarding the contract parties.
The types of clauses may include contents regarding specific rights and obligations held by the parties to the contract, such as confidentiality obligations, damages compensation obligations, contract cancellation obligations, and restoration obligations. Alternatively, clause type identification information such as clause type ID defined for each clause type may be stored in a table (not shown). Clause information extracted from contract information is classified, stored, and managed by clause type.
By referring to the clause types, it is possible to confirm what rights and obligations are imposed on each clause and each contract party.
The clause data is an item in which information regarding clauses extracted from document data included in contract information is stored. Specifically, the clause data stores character strings included in clauses included in 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 list presentation unit 1044. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

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

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

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

The list presentation unit 1044 executes list presentation processing. Details will be described later.

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

<Configuration of storage unit 201 of first user terminal 20>
The storage unit 201 of the first user terminal 20 includes a first user ID 2011 and an application program 2012.

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

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

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

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

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

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

<Configuration of storage unit 301 of second user terminal 30>
The storage unit 301 of the second user terminal 30 includes a second user ID 3011 and an application program 3012.

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

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

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

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

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

<Operation of system 1>
Each process of the system 1 will be explained below.
FIG. 12 is a flowchart showing the operation of the contract creation process.
FIG. 13 is a flowchart showing the operation of the contract confirmation process.
FIG. 14 is a flowchart showing the operation of list presentation processing.
FIG. 15 is an example of a screen showing the operation of the contract creation process.
FIG. 16 is an example of a screen showing a confirmation request message notified to the second user terminal 30.
FIG. 17 is a screen example showing the operation of the contract confirmation process.
FIG. 18 is an example of a screen showing a conclusion completion message notified to the first user terminal 20.
FIG. 19 is a diagram illustrating the rights and obligation information and clause extraction process in the contract confirmation process.
FIG. 20 is an example of a screen showing the operation of the list presentation process.
FIG. 21 is an example of a screen showing the operation of the list presentation process.

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 the contract confirmation process in the external server 40 are the same as the contract creation process and the contract confirmation process in the server 10, respectively, so a description thereof will be omitted.

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

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

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

<Details of contract creation process>
In step S101, the contract creation unit 1042 of the server 10 receives contract information from a creator to be the subject of a contract conclusion with a confirmer. The contract creation unit 1042 executes a contract storage step of storing contract information regarding the contract.
Specifically, the first user operates the input device 206 of the first user terminal 20 and creates contract information including document data related to the contract. The contract information can include document data in any data format such as PDF (Portable Document Format), Word, and XML (ExtenSible Markup Language).
The first user operates the input device 206 of the first user terminal 20 and transmits the created document data and the first user ID 2011 to the server 10 . The contract creation unit 1042 of the server 10 receives the received first user ID 2011 and document data, and stores them in the creator ID and document data fields of a new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores new contract information in the document table 1014.

The contract storage step executes a step of storing the contract information in association with persistence information regarding the persistence state of the contract information.
Specifically, the contract creation unit 1042 of the server 10 associates and stores the new contract information stored in the document table 1014 with a date and time (survival information) indicating the expiration date or expiration date of the contract information specified in the document data. do. As a result, the new contract information stored in the document table 1014 is stored in association with the survival information regarding the state of existence of the contract information. In addition, in the case of premature termination, cancellation, or expiration of a contract, the survival information regarding the continued status may be stored in association with the contract information such as the end date and the cancellation date.

The contract creation unit 1042 of the server 10 executes a step of storing contract information in association with persistence information regarding the persistence state of the contract information.

In step S102, the first user operates the input device 206 of the first user terminal 20, etc. to select and specify a user who will be the confirmer (receiver) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies the second user as the recipient.
The first user operates the input device 206 of the first user terminal 20 and inputs 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 creation unit 1042 of the server 10 stores the received email address and the document ID of the contract information created and stored in step S101 in the confirmer email address and document ID fields of the confirmation table 1015, respectively, and stores the contract information and the document ID in the confirmation table 1015. It is stored in association with the second user's email address. Note that the first user may set the second user's language and access code, and store them in association with the second user's email address.
At this time, a value of 1 is stored in the confirmation order item of the confirmation table 1015. In step S102, the first user may be able to select and set a plurality of users to be confirmers. In this case, the value of the confirmation order item of the user who is the confirmer is incremented by one and stored in accordance with the selection order. This sets the order of circulation of confirmers in contract confirmation processing, which will be described later. Note that setting the circulation order is not essential.

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

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

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

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

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

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

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

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

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

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

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

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

If the access code item is stored in the second user's record in the confirmation table 1015, the second user is requested to input the access code, and the entered access code and the second user's record in the confirmation table 1015 are stored. By comparing the access code stored in the user's record, it is possible to perform authentication processing for the second user.
Specifically, the server 10 transmits an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30, inputs the access code, and transmits it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the second user's record in the confirmation table 1015, and if they match, executes contract confirmation processing. continue. On the other hand, if they do not match, the contract confirmation process is canceled. Note that the authentication process using the access code may be omitted.

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

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

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

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

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

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

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

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

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

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

The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been executed by all confirmers having approval authority. Specifically, if a value of True is stored in the confirmation flag of the record of the confirmer who has approval authority in the confirmation table 1015, the contract confirmation unit 1043 of the server 10 performs the contract check by all confirmers who have approval authority. It is determined that the contract confirmation process has been executed. That is, the determination is made while ignoring the value of the confirmation flag of the record of a confirmer who does not have approval authority.
The contract confirmation unit 1043 of the server 10 proceeds to step S306 when the contract confirmation process is executed by all the confirmers who have approval authority.

FIG. 19 is a diagram illustrating the process of extracting rights and obligation information and clauses.
In the present disclosure, document data D20 is document data related to contract information in which contract conditions related to a non-disclosure agreement are predetermined. The document data D20 includes contract parties D21 and D22, a plurality of clauses D201 and D202, clause headings D2011 and D2021, and clauses D2012 and D2022.

In step S306, the contract confirmation unit 1043 of the server 10 executes a party storage step of specifying one or more pieces of party information regarding the parties to the contract and storing the specified one or more pieces of party information in association with the contract information.
Specifically, the contract confirmation unit 1043 of the server 10 searches the document ID item in the document table 1014 based on the document ID received in step S301, and obtains the document data and creator ID. The contract confirmation unit 1043 of the server 10 searches the document ID in the confirmation table 1015 based on the document ID received in step S301, and obtains the confirmer email address item.
The contract confirmation unit 1043 of the server 10 specifies the information of the parties to the contract regarding the contract information based on the obtained document data, creator ID, and confirmer email address. Specifically, the contract confirmation unit 1043 of the server 10 analyzes the document data and recognizes character strings such as individual names, company names, and organization names written in parties D21 and D22 of the contract included in the document data. Identify as party information. Character string recognition can use known pattern matching, machine learning, deep learning, and artificial intelligence models.
The contract confirmation unit 1043 of the server 10 may identify the parties to the contract based on information that identifies the creator and confirmer of the contract information, such as the creator ID and the confirmer's email address. For example, based on the domain name of the email address of the creator and confirmer, refer to a table (not shown), etc., and enter character strings such as company name, organization name, etc. to which the creator and confirmer belong to the party information. It may be specified as

In step S306, the contract confirmation unit 1043 executes an extraction step of extracting one or more rights and obligations information regarding rights or obligations included in the contract from the contract information stored in the contract storage step. The extraction step is a step of extracting one or more clauses included in the contract from the contract information.
Specifically, the contract confirmation unit 1043 of the server 10 extracts a plurality of clauses D201 and D202 and clause headings D2011 and D2021 included in the document data, based on the acquired document data. Note that the contract confirmation unit 1043 of the server 10 does not need to extract each clause, but extracts a plurality of clauses in units of rights or obligations (rights and obligations information) from the contract information that defines the contract included in the document data. Alternatively, a configuration may be adopted in which a part of clause 1 is extracted. Further, the clauses may be extracted in arbitrary classification units such as articles, sections, and subheadings.
The contract confirmation unit 1043 of the server 10 identifies the clause types of clauses D201 and D202 based on clauses D201 and D202, clause headings D2011 and D2021, and the like. For example, the types of clauses are specified, such as "definition clause" as the clause type of clause D201 and "confidentiality obligation" as the clause type of clause D202.

In step S306, the party storage step executes a step of storing each of the one or more rights and obligation information extracted in the extraction step in association with the identified one or more party information. The party storage step executes a step of storing each of the one or more clauses extracted in the extraction step in association with the identified one or more party information.
Specifically, the contract confirmation unit 1043 of the server 10 converts the document ID, extracted clause headings D2011, D2021, clause types, clauses D201, D202 received in step S301 into the document ID, clause headings, and clauses of the clause table 1018, respectively. Stored in the clause type and clause data items. Note that the clause ID is automatically incremented and numbered.
Note that the contract confirmation unit 1043 of the server 10 may be configured to store arbitrary rights and obligation information in the clause table 1018 instead of clauses.
As a result, one or more extracted clauses and rights and obligations information are stored in association with party data in the document table 1014 via the document ID.

When the contract confirmation process is executed by all the confirmers having approval authority, the contract confirmation unit 1043 of the server 10 sends a message to the first user notifying that the contract confirmation process is completed. Note that, similarly, the contract confirmation unit 1043 of the server 10 may send a message to the second user notifying that the contract confirmation process has been completed.

Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the first user's email address to notify that the second user has completed confirmation of the contract information, using a communication means such as email. That is, the first user is notified that the second user has approved the conclusion of the contract. This allows the first user to know that the contract has been concluded with the second user.
The message to be notified to the first user may include information on a URL that is an endpoint that includes a document ID for specifying contract information.

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

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

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

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

Specifically, the contract confirmation unit 1043 of the server 10 acquires the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 searches the group ID item of the group table 1013 based on the acquired group ID item, acquires the administrator ID item, and, based on the administrator ID, identifies the person who corresponds to the administrator. An authorized user is identified by searching the user ID in the user table 1012, and a message is sent to notify that the contract confirmation process has been completed.

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

<List presentation process>
The list presentation process is a process of presenting one or more pieces of contract information associated with each piece of party information regarding parties to a contract.

<Overview of list presentation process>
The list presentation process receives an inquiry request including rights and obligations information from a user, acquires one or more rights and obligations information that is equivalent or similar to the received rights and obligations information, and presents a list of the obtained rights and obligations information to the user. This is a series of processes.

<Details of list presentation process>
The details of the list presentation process will be explained below. In the present disclosure, evidence storage processing using the first user terminal 20 will be described as an example, but the evidence storage processing may be configured to be executed from any information processing terminal other than the second user terminal 30. Further, a configuration may be adopted in which any user other than the first user and the second user can execute the process.

FIG. 20 is an example of a screen showing the operation of the list presentation process. A screen D30 displayed on the display 2081 of the first user terminal 20 includes an input field D301 for inputting predetermined rights and obligation information, article headings, etc., a radio button D302 for specifying either rights or obligations, and a send button D303. , one or more different party information D311, D312, one or more different party information associated with each one or more rights and obligations information that is equivalent or similar to the predetermined rights and obligations information, a contract concluded between one or more different party information Information D321 and D322 are included.
The radio button D302 indicates whether the first user is in a position of "rights" or "obligations" or "neither" with respect to the rights and obligation information and article headings input in the input field D301. This is a user interface for selecting the "even" case.
For example, if the first user enters "confidentiality" in the input field D301 and selects "obligation" in the radio button D302, the first user can determine the "obligation" regarding "confidentiality" and what kind of party information D311, D312 It is possible to display whether the Similarly, if the first user enters "confidentiality" in the input field D301 and selects "rights" in the radio button D302, the first user can specify the "rights" related to "confidentiality" and what kind of party information D311, D312 You can display whether you have it. If "Both" is selected, it is possible to display which parties have rights and obligations related to "confidentiality" regardless of "rights" or "duties."
The party information D311, D312 is the name of the party, company name, organization name, etc., and the number of contract information concluded with the party is displayed in parentheses.
The contract information D321 and D322 includes information on the document ID, contract start date, and contract end date for each contract information. Note that the contract information D321 and D322 may also include the name of the contract and, if there is another party to the contract, information on the other party to the contract.

FIG. 21 is an example of a screen showing the operation of the list presentation process. A screen D40 displayed on the display 2081 of the first user terminal 20 includes an input field D401 for inputting predetermined party information, a send button D403, and one or more rights and obligations held with the predetermined party. Labels D411 and D412 indicating information or clause headings, and contract information D421 and D422 including one or more pieces of rights and obligation information are included.
In the parentheses of labels D411 and D412 indicating rights and obligations information or article headings, the number of pieces of contract information held with a predetermined party is displayed for each right and obligation information or article heading.

In step S501, the list presentation unit 1044 of the server 10 executes an inquiry step of receiving an inquiry request including predetermined rights and obligations information regarding rights or obligations from a user. The inquiry step is a step of receiving an inquiry request including a predetermined clause heading as predetermined rights and obligation information from a user.
Specifically, the first user starts the browser application stored in the storage unit 201 of the first user terminal 20, inputs the URL for executing the list presentation process of the server 10, and opens the list presentation page. The control unit 204 of the first user terminal 20 transmits a request to the server 10 to execute list presentation processing.

Note that the list presentation page on which the screen D30 for inputting predetermined rights and obligation information and predetermined clause headings is displayed is different from the list presentation page on which the screen D40 for inputting predetermined party information is displayed. A configuration may also be adopted in which a URL is assigned and the first user inputs a different URL to selectively switch between screen D30 and screen D40 to execute a desired list presentation process.

The server 10 generates an input screen including an input field for inputting rights and obligation information or article headings to be subjected to list presentation processing, and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received input screen as a screen D30 on the display 2081 of the first user terminal 20, and presents it to the first user. The first user inputs the specified rights and obligations information or article heading into the input field D301 for entering the rights and obligation information or article heading displayed on the screen D30, and presses the send button D303. A request (inquiry request) including mandatory information or article headings is sent to the server 10.
If the first user wants to specify whether he or she has either "rights" or "obligations" for the rights and obligations information or article heading entered in the input field D301, the first user selects the "rights and obligations" in the radio button D302. ” or “Obligation.”

The predetermined rights and obligations information is a collection of a plurality of clauses in units of rights or obligations (rights and obligations information) in the contract information, or an extracted part of one clause. Further, the predetermined rights and obligations information may be a predetermined clause included in the contract information. For example, the rights and obligation information may be clauses D201 and D202. Note that the clause may be input as an arbitrary division unit such as article, section, or item.
Further, the predetermined rights and obligations information includes information corresponding to the clause type in the clause table 1018. For example, it is a character string indicating the specific rights and obligations held by the parties to the contract, such as confidentiality obligations, damages compensation obligations, contract cancellation obligations, and restoration obligations, and may also be clause type identification information such as clause type ID. .
The predetermined article heading is a character string related to the article heading in the contract information. For example, the article headings are character strings such as "confidential information" and "handling of confidential information" in article headings D2011 and D2021. The article heading may be a character string such as "Confidentiality,""Compensation for Damages,""Cancellation of Contract," or "Restoration to Original Condition."

Further, in step S501, the list presenting unit 1044 of the server 10 may perform a party inquiry step of accepting an inquiry request including predetermined party information regarding parties to the contract from the user.
In this case, the screen D40, which is the input screen, includes an input field D401 for inputting a character string indicating the name, company name, organization name, etc. of the party who is the target of the list presentation process. The first user enters party information such as a predetermined name, company, organization name, etc. in the input field D401 displayed on the input screen and presses the send button D403. A request including information (inquiry request) is sent to the server 10.

The input field D401 may be an input field such as a text field in which the first user can input any character string, or a selection type input field (in which the first user can select and input any character string from a plurality of predetermined character strings). It doesn't matter if it's an input field (pulldown, radio button, checkbox).

The list presentation unit 1044 of the server 10 receives and accepts rights and obligations information, article headings, party information, etc. included in the inquiry request.

In step S502, the list presentation unit 1044 of the server 10 executes an acquisition step of acquiring one or more rights and obligations information that is equivalent to or similar to the predetermined rights and obligations information received in the inquiry step.
Specifically, upon receiving predetermined rights and obligations information included in the inquiry request, the list presentation unit 1044 of the server 10 searches the clause data and clause type items in the clause table 1018 based on the predetermined rights and obligations information, and Among the clause data and clause types stored in the table 1018, one or more clause data and clause types that are equivalent or similar to the predetermined rights and obligation information are acquired.

The list presentation unit 1044 of the server 10 compares the clause data and clause types stored in the clause table 1018 with the received predetermined rights and obligation information to determine whether they are equivalent or similar.
Equivalence refers to a text that defines rights and obligations equivalent to the text included in the predetermined rights and obligations information. Equivalence refers to the text contained in a given clause and the equivalent clause stipulated.
Determination as to whether equivalent rights, obligations, and provisions are stipulated may be determined using known syntax analysis and text analysis techniques, as well as machine learning, deep learning, artificial intelligence models, and the like.
When the predetermined rights and obligations information is a clause type, clause information having the same clause type is said to be equivalent to the predetermined rights and obligations information.

Similarity refers to a text included in the predetermined rights and obligations information and a text in which similar rights and obligations are defined. Similarity refers to sentences contained in a given provision and those in which similar provisions are prescribed.
Determination as to whether similar rights, obligations, and provisions are stipulated may be determined using known syntax analysis and text analysis techniques, as well as machine learning, deep learning, artificial intelligence models, and the like.
Similarity refers to a sentence whose degree of similarity is greater than or equal to a predetermined value in a calculation method that calculates the degree of similarity between a sentence included in predetermined rights and obligation information and character strings such as Levenshtein distance. Similarity refers to a sentence whose similarity is equal to or greater than a predetermined value in a calculation method that calculates the similarity between text included in a predetermined clause and character strings.
If the predetermined rights and obligations information is a clause type, similar clause types may be linked and defined in advance in a table (not shown), etc., and the linked clause types may be defined as similar clause types. . In addition, in addition to known syntax analysis and text analysis techniques, machine learning, deep learning, artificial intelligence models, etc. may be used to determine the similarity between clause types.

In step S502, the acquisition step executes the step of acquiring one or more articles having article headings that are equivalent to or similar to the predetermined article heading received in the inquiry step.
Specifically, when the list presentation unit 1044 of the server 10 receives a predetermined article heading included in the inquiry request, it searches for the article heading item in the article table 1018 based on the predetermined article heading, and searches the articles stored in the article table 1018. One or more clause information that is equivalent to or similar to a predetermined clause heading is acquired from among the clause headings.
The list presentation unit 1044 of the server 10 compares the clause headings stored in the clause table 1018 with the received predetermined clause headings to determine whether they are equivalent or similar.

Equivalent means that a sentence included in a predetermined article heading is defined as an equivalent article heading. The determination as to whether or not equivalent article headings are defined may be made using known syntax analysis and text analysis techniques, as well as machine learning, deep learning, artificial intelligence models, and the like.
Similarity refers to a sentence included in a predetermined article heading and a provision for a similar article heading. The determination as to whether similar article headings are defined may be made using known syntax analysis and text analysis techniques, as well as machine learning, deep learning, artificial intelligence models, and the like.
Similarity refers to article headings for which the degree of similarity is greater than or equal to a predetermined value in a calculation method that calculates the degree of similarity between text included in a predetermined article heading and character strings such as Levenshtein distance.

The list presentation unit 1044 of the server 10 searches the document ID in the document table 1014 based on the document ID included in the acquired one or more clause information, and acquires party data. The list presentation unit 1044 of the server 10 transmits the document ID included in the acquired one or more clause information and the acquired party data to the first user terminal 20. Note that the list presentation unit 1044 of the server 10 may transmit the contract information specified by the document ID to the first user terminal 20.

In step S503, the control unit 204 of the first user terminal 20 displays the party data, contract information, rights and obligations information, clause information, etc. received from the server 10 on the display 2081 of the first user terminal 20. The control unit 204 of the first user terminal 20 executes a list presentation step of presenting a list of one or more pieces of party information stored in the party storage step in association with one or more associated contract information.
The control unit 204 of the first user terminal 20 transmits the predetermined rights and obligations information received in the inquiry step to one or more different rights and obligations information associated with each of the one or more equal or similar rights and obligations information obtained in the acquisition step. A party presentation step is performed in which the party is presented to the user in association with the party information.
The control unit 204 of the first user terminal 20 combines the predetermined article heading received in the inquiry step with one or more different party information associated with each of the one or more equal or similar articles acquired in the acquisition step. Execute the step of presenting the parties in a linked manner to the user.

Specifically, the screen D30 displays information that is associated with one or more rights and obligations information that is equivalent or similar to the predetermined rights and obligations information input in the input field D301 and the condition selected in the radio button D302. One or more pieces of different party information D311 and D312 are linked and presented to the first user. Similarly, by entering a predetermined article heading into the input field D301 and sending an inquiry request, a screen D30 will display information that is associated with each of one or more articles that are equivalent or similar to the predetermined article heading. One or more different party information D311 and D312 associated with one or more different party information are linked and presented to the first user.

In step S503, the list presentation unit 1044 of the server 10 executes a selection reception step in which the user selects predetermined contract information from the one or more pieces of contract information presented in the list presentation step.
Specifically, the first user inputs one or more predetermined pieces of contract information D421 and D422 displayed on the display 2081 of the first user terminal 20 by operating the input device 206 of the first user terminal 20. Select by pressing the document ID label of the contract information. The control unit 204 of the first user terminal 20 receives a selection operation for predetermined contract information, and transmits to the server 10 the document ID of the predetermined contract information for which the selection operation has been accepted. The list presentation unit 1044 of the server 10 receives and accepts the document ID.

In step S503, the list presenting unit 1044 of the server 10 executes a voucher issuing step of issuing voucher information regarding vouchers including destination information based on the predetermined contract information selected in the selection receiving step.
Specifically, the list presentation unit 1044 of the server 10 searches the document ID in the document table 1014 based on the received document ID, and specifies the contract information. The list presentation unit 1044 of the server 10 generates a screen for selecting evidence information such as a bill, receipt, estimate, report, etc. regarding the contract information, and transmits it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received one or more pieces of evidence information on the display 2081 of the first user terminal 20 in a manner that can accept a selection operation from the user. The first user selects desired evidence information from the displayed one or more pieces of evidence information by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 displays on the display 2081 of the first user terminal 20 an input screen including an input field for inputting the destination of the selected evidence information.
The first user enters a character string such as a name, company name, department name, organization name, etc. related to the destination of the voucher information in the input field, and issues the voucher information. Thereby, the first user can easily create evidence such as a bill with an input address based on the selected predetermined contract information.

In step S503, the list presentation unit 1044 of the server 10 warns the user if the destination information included in the evidence information does not include the party information stored in association with the predetermined contract information in the party storage step. Execute a warning presentation step that presents information.
Specifically, the first user terminal 20 performs the processing when the character string such as the name, company name, department name, organization name, etc. related to the destination entered in the input field is not included in the party information of the contract information that serves as the basis. displays information pointing out the possibility that there is an error in the destination information on the display 2081 of the first user terminal 20, and presents it to the first user.
As a result, since the destination information of the voucher usually includes the party information of the contract information, it is possible to prevent misdirection of the voucher information.

In step S503, the list presenting step executes a step of presenting a list of one or more pieces of contract information associated with the predetermined party information, based on the predetermined party information received in the party inquiry step.
Specifically, on the screen D40, one or more pieces of contract information D421 and D422 associated with a predetermined party are presented to the first user in response to the predetermined party information input in the input field D401. .

In step S503, the list presentation step presents a list of labels D411 and D412 indicating one or more rights and obligations information held with the predetermined party information based on the predetermined party information received in the party inquiry step. Execute the steps to
For example, specific character strings such as "obligation to maintain confidentiality,""obligation to compensate for damages,""obligation to cancel contract," and "obligation to restore original condition" that you have with a given party indicate rights and obligations. They are presented as a list as labels D411 and D412.

In step S503, the list presentation step includes displaying one or more rights and obligations information held with a predetermined party based on the predetermined party information received in the party inquiry step, with labels D411 and D412 indicating article headings. Execute the steps that list the.
For example, specific character strings such as "confidentiality,""compensation for damages,""cancellation of contract," and "restoration to original condition" that are held with a predetermined party are displayed in labels D411 and D412 that indicate clause headings. It is presented as a list. Note that either "rights" or "obligations" between the first user and company A may be distinguished and presented in a list. For example, for the same "Confidentiality" heading, cases where the first user has "rights" and cases where the first user has "obligations" may be distinguished and presented as a list. Similarly, for the same heading of "Confidentiality", cases where Company A has "rights" and cases where Company A has "obligations" may be distinguished and presented as a list.

<Modified example>
The list presentation step may include a step of excluding one or more contract information for which information indicating that the contract information continues to exist is not stored among the one or more contract information and presenting the contract information in a list. .
Specifically, the list presentation unit 1044 of the server 10 compares the current date and time with the date and time indicating the expiration date, expiration date, end date, and cancellation date of the contract information, and selects contracts for which it is determined that the contract information does not exist. Even if only the rights and obligations information, clause information, article headings, and party information are obtained from the information, and the rights and obligations information, clause information, article headings, and party information are excluded from the contract information that is determined to be continuing. good.
By excluding the party information of the contract that no longer exists, the first user can confirm the rights and obligations that the first user currently has, while excluding the rights and obligations that the first user does not currently have. The first user can conveniently manage contract information.

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

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

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

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

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

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

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

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

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

The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Further, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 according to the program. Further, the control unit can cause the processor 901 to execute processing for adding, updating, and deleting data stored in the storage unit according to various programs.

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

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

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

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

(Additional note 1)
A contract management program for storing electronic contract procedures between users in a computer, comprising a processor and a storage unit, the processor includes a contract storage step (S101) for storing contract information regarding the contract; A party storage step (S306) in which one or more party information regarding the party is specified and the identified one or more party information is stored in association with the contract information, and the one or more party information stored in the party storage step is A contract management program that executes a list presentation step (S503) of presenting a list in association with one or more associated contract information.
This makes it possible to organize and manage what kind of contract information is concluded for each contracting party.
The user can conveniently manage contract information.

(Additional note 2)
Execute an extraction step (S306) of extracting one or more rights and obligations information regarding rights or obligations included in the contract from the contract information stored in the contract storage step, and the party storage step (S306) The contract management program according to appendix 1, which is a step of storing each of the extracted one or more rights and obligation information in association with the identified one or more party information.
This makes it possible to organize and manage what rights and obligations each contract party has.

(Additional note 3)
The extraction step (S306) is a step of extracting one or more clauses included in the contract from the contract information, and the party storage step (S306) specifies each of the one or more clauses extracted in the extraction step. The contract management program according to appendix 2, which is a step of storing information in association with one or more party information that has been obtained.
This makes it possible to organize and manage what kind of clauses are entered into for each contracting party.

(Additional note 4)
The processor includes an inquiry step (S501) in which an inquiry request including predetermined rights and obligations information regarding rights or obligations is received from a user, and one or more rights and obligations information that is equivalent or similar to the predetermined rights and obligations information received in the inquiry step. The contract management program according to supplementary note 2, which executes the acquisition step (S502) of acquiring .
Thereby, it is possible to receive an inquiry request regarding rights and obligations from a user, and to confirm the rights and obligations of contract information in past contracts that are equivalent to or similar to the rights and obligations included in the request.

(Appendix 5)
The processor associates the predetermined rights and obligations information received in the inquiry step with one or more different party information associated with each of the one or more equivalent or similar rights and obligations information obtained in the acquisition step and provides the user with the information. The contract management program according to supplementary note 4, which executes the step of presenting a party (S503).
Thereby, the user can check which contract parties the user has rights and obligations with for each right and obligation information.

(Appendix 6)
The inquiry step (S501) is a step of receiving an inquiry request including a predetermined article heading as predetermined rights and obligation information from the user, and the acquisition step (S502) is a step of receiving an inquiry request containing a predetermined article heading as the predetermined rights and obligation information, and the acquisition step (S502) is a step of receiving an inquiry request that includes a predetermined article heading that is equivalent to or similar to the predetermined article heading received in the inquiry step. The contract management program according to supplementary note 4, which is a step of acquiring one or more clauses having a clause heading.
Thereby, it is possible to receive an inquiry request regarding article headings from a user, and to check the articles of contract information of past contracts that are equivalent to or similar to the article headings included in the request.

(Appendix 7)
The processor associates the predetermined clause heading received in the inquiry step with one or more different party information associated with each of the one or more equivalent or similar clauses obtained in the acquisition step and presents the same to the user. The contract management program according to appendix 6, which executes the presenting step (S503).
This allows the user to confirm, for each contract clause, what kind of contract parties the contract clause is with.

(Appendix 8)
The processor performs a selection reception step (S503) in which the processor accepts an operation for selecting predetermined contract information from one or more pieces of contract information presented in the list presentation step from the user, and selects a destination based on the predetermined contract information selected in the selection reception step. In the voucher issuing step (S503) of issuing voucher information regarding the voucher containing the information, and in the case where the destination information included in the voucher information does not include the party information stored in association with the predetermined contract information in the party storing step, The contract management program according to supplementary note 1, which executes a warning presentation step (S503) of presenting warning information to the user.
As a result, when a user issues evidence such as an estimate, invoice, or receipt based on contract information, the destination information of the evidence does not include the party information of the contract information that is the basis of the evidence. You can receive a warning if Since the destination information of the voucher usually includes the party information of the contract information, it is possible to prevent the wrong address of the voucher information.

(Appendix 9)
The contract storage step (S101) is a step of storing contract information in association with the survival information regarding the state of existence of the contract information, and the list presentation step (S502) is a step of storing the contract information in association with the survival information regarding the existence state of the contract information. The contract management program according to supplementary note 1, which is a step of excluding one or more pieces of contract information for which information indicating that the contract information is not stored and presenting a list.
This makes it possible to organize and manage what kind of ongoing contract information is concluded for each contracting party. By excluding party information of contracts that no longer exist, the user can exclude rights and obligations that the user does not currently have and confirm the rights and obligations that the user currently has. The user can conveniently manage contract information.

(Appendix 10)
The processor executes a party inquiry step (S501) in which an inquiry request including predetermined party information regarding parties to a contract is received from a user, and a list presentation step (S503) includes the predetermined party information received in the party inquiry step. The contract management program according to supplementary note 1, which is a step of presenting a list of one or more contract information associated with predetermined party information based on.
Thereby, the user can inquire about the parties concerned and see what kind of contract information has been concluded with the parties concerned.

(Appendix 11)
The processor executes a party inquiry step (S501) in which an inquiry request including predetermined party information regarding parties to a contract is received from a user, and a list presentation step (S503) includes the predetermined party information received in the party inquiry step. The contract management program according to appendix 2, which is a step of presenting a list of one or more rights and obligations information held with predetermined party information based on.
As a result, when a user has concluded multiple contracts with parties to the contract, it is possible to check at a glance what kind of rights and obligations the user has with the parties.

(Appendix 12)
The list presentation step (S503) is a step of presenting a list of one or more rights and obligations information held with the predetermined party information for each clause heading based on the predetermined party information received in the party inquiry step. The contract management program described in Supplementary Note 11.
As a result, when a user has concluded multiple contracts with the parties to the contract, it is possible to check the rights and obligations that the user has with the parties by viewing the article headings. can.

(Appendix 13)
An information processing device comprising a processor and a storage unit, wherein the processor executes a contract management program according to any one of Supplementary Notes 1 to 12.
Thereby, contract information can be stored in association with party information, and it is possible to organize and manage what kind of contract information has been concluded for each contract party.

(Appendix 14)
An information processing system including an information processing device including a processor and a storage unit, wherein the processor executes a contract management program according to any one of Supplementary Notes 1 to 12.
Thereby, contract information can be stored in association with party information, and it is possible to organize and manage what kind of contract information has been concluded for each contract party.

(Appendix 15)
An information processing method executed by a computer including a processor and a storage unit, the computer executing a contract management program according to any one of appendices 1 to 12.
Thereby, contract information can be stored in association with party information, and it is possible to organize and manage what kind of contract information has been concluded for each contract party.

(Appendix 16)
An information processing terminal comprising a processor, a storage unit, and a display device, wherein the processor executes the list presentation step in the contract management program according to any one of Supplementary Notes 1 to 12.
This makes it possible to organize and manage what kind of contract information is concluded for each contracting party.
The user can conveniently manage contract information.

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

Claims (16)

A contract management program for storing electronic contract procedures between users in a computer, comprising a processor and a storage unit,
The processor includes:
a contract storage step for storing contract information regarding the contract;
a party storage step of identifying one or more party information regarding the parties to the contract and storing the identified one or more party information in association with the contract information;
a list presentation step of presenting a list of one or more of the party information stored in the party storage step in association with one or more of the associated contract information;
A contract management program that runs an extraction step of extracting one or more rights and obligations information regarding rights or obligations included in the contract from the contract information stored in the contract storage step;
Run
The party storage step is a step of storing each of the one or more rights and obligation information extracted in the extraction step in association with the one or more identified party information.
The contract management program according to claim 1. The extraction step is a step of extracting one or more clauses included in the contract from the contract information,
The party storing step is a step of storing each of the one or more clauses extracted in the extracting step in association with the identified one or more party information,
The contract management program according to claim 2. The processor includes:
an inquiry step of receiving an inquiry request including predetermined rights and obligations information regarding rights or obligations from the user;
an acquisition step of acquiring one or more rights and obligations information that is equivalent or similar to the predetermined rights and obligations information received in the inquiry step;
execute,
The contract management program according to claim 2. The processor includes:
The predetermined rights and obligations information received in the inquiry step is linked with one or more different party information associated with each of the one or more equal or similar rights and obligations information obtained in the acquisition step. a step of presenting a party to the user;
5. The contract management program according to claim 4. The inquiry step is a step of receiving an inquiry request including a predetermined article heading as the predetermined rights and obligation information from the user,
The acquisition step is a step of acquiring one or more articles having article headings that are equivalent to or similar to the predetermined article heading received in the inquiry step.
The contract management program according to claim 4. The processor includes:
The predetermined article heading received in the inquiry step is presented to the user in association with one or more different party information associated with each of the one or more equal or similar articles acquired in the acquisition step. a step of presenting a party to
7. The contract management program according to claim 6. The processor includes:
a selection reception step of receiving a user's operation to select predetermined contract information from the one or more contract information presented in the list presentation step;
a voucher issuing step of issuing voucher information regarding the voucher including destination information based on the predetermined contract information selected in the selection receiving step;
If the destination information included in the evidence information does not include the party information stored in association with the predetermined contract information in the party storage step, a warning presentation step of presenting warning information to the user. and,
execute,
The contract management program according to claim 1. The contract storage step is a step of storing the contract information in association with survival information regarding the state of existence of the contract information,
The step of presenting a list is a step of presenting a list of one or more pieces of contract information, excluding one or more pieces of contract information for which information indicating that it continues in the surviving information is not stored, from among the one or more pieces of contract information. be,
The contract management program according to claim 1. The processor includes:
a party inquiry step of receiving an inquiry request including predetermined party information regarding the parties to the contract from the user;
Run
The list presenting step is a step of presenting a list of one or more of the contract information associated with the predetermined party information, based on the predetermined party information received in the party inquiry step.
The contract management program according to claim 1. The processor includes:
a party inquiry step of receiving an inquiry request including predetermined party information regarding the parties to the contract from the user;
Run
The list presenting step is a step of presenting a list of the one or more rights and obligations information held with the predetermined party information based on the predetermined party information received in the party inquiry step.
The contract management program according to claim 2. The list presentation step is based on the predetermined party information received in the party inquiry step, and presents a list of the one or more rights and obligations information held with the predetermined party information for each article heading. The step is to
The contract management program according to claim 11. An information processing device comprising a processor and a storage unit,
The processor executes the contract management program according to any one of claims 1 to 12.
Information processing device. An information processing system including an information processing device including a processor and a storage unit,
The processor executes the contract management program according to any one of claims 1 to 12.
Information processing system. An information processing method executed by a computer comprising a processor and a storage unit,
The computer executes the contract management program according to any one of claims 1 to 12.
Information processing method. An information processing terminal comprising a processor, a storage unit, and a display device,
The processor executes the list presenting step in the contract management program according to any one of claims 1 to 12.
Information processing terminal.