Contract management programs, information processing devices, information processing systems, information processing methods

Abstract

To provide a contract management program that organizes and manages contract information concluded for each contractor, an information processing apparatus, an information processing system, and an information processing method.SOLUTION: A contract management program executes: a contract information acquisition step which acquires contract information in operation, concluded by a first organization as a contractor; an opposite party specifying step which specifies one or more opposite parties of the contract information acquired in the contract information acquisition step; an opposite party credit information acquisition step which acquires one or more pieces of credit information of each of the one or more opposite parties specified in the opposite party specifying step; a validity determination step which determines whether the one or more pieces of credit information acquired in the opposite party credit information acquisition step fall under a specific contract clause included in the contract information acquired in the contract information acquisition step; and an information notification step which outputs notification information when determination is made in the validity determination step that the one or more pieces of credit information fall under the specific contract clause.SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] The present disclosure relates to a contract management program, an information processing apparatus, an information processing system, and an information processing method.

Background Art

[0002] With the development and popularization of computer technology, documents that have conventionally used paper media are being digitized. For example, it has been considered that documents such as contracts that require the signatures and seals of the parties are also managed as electronic data. Patent Document 1 discloses a technology for guaranteeing the conclusion and cancellation of a contract and storing an electronic contract.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problem to be Solved by the Invention

[0004] In electronic contract procedures between a plurality of users, there is a problem that what kind of contract information is concluded for each contracting party cannot be organized and managed. Therefore, the present disclosure has been made to solve the above problem, and an object of the present disclosure is to provide a technology for organizing and managing what kind of contract information is concluded for each contracting party.

Means for Solving the Problem

[0005] A contract management program comprising a processor and a memory unit, for causing a computer to store electronic contract procedures between users, wherein the processor executes: a contract acquisition step of acquiring contract information concluded by a first organization as a party and in the course of the contract; a counterparty identification step of identifying one or more counterparties to the contract information acquired in the contract acquisition step; a credit acquisition step of acquiring one or more credit information for each of the one or more counterparties identified in the counterparty identification step; a determination step of determining whether the one or more credit information acquired in the credit acquisition step corresponds to a specific contract clause included in the contract information acquired in the contract acquisition step; and a notification output step of outputting notification information if, in the determination step, it is determined that the one or more credit information corresponds to a specific contract clause. [Effects of the Invention]

[0006] According to this disclosure, it is possible to organize and manage what kind of contract information each contracting party has entered into. [Brief explanation of the drawing]

[0007] [Figure 1] This is a block diagram showing the functional configuration of System 1. [Figure 2] This block diagram shows the functional configuration of Server 10. [Figure 3] This is a block diagram showing the functional configuration of the first user terminal 20. [Figure 4] This is a block diagram showing the functional configuration of the second user terminal 30. [Figure 5] This diagram shows the data structure of user table 1012. [Figure 6] This diagram shows the data structure of group table 1013. [Figure 7] This diagram shows the data structure of document table 1014. [Figure 8] This diagram shows the data structure of confirmation table 1015. [Figure 9]It is a diagram showing the data structure of the input item table 1016. [Figure 10] It is a diagram showing the data structure of the contract group table 1017. [Figure 11] It is a flowchart showing the operation of contract creation processing. [Figure 12] It is a flowchart showing the operation of contract confirmation processing. [Figure 13] It is a flowchart showing the operation of contract cancellation processing. [Figure 14] It is a flowchart showing the operation of external cooperation processing. [Figure 15] It is a screen example showing the operation of contract creation processing. [Figure 16] It is a screen example showing a confirmation request message notified to the second user terminal 30. [Figure 17] It is a screen example showing the operation of contract confirmation processing. [Figure 18] It is a screen example showing a conclusion completion message notified to the first user terminal 20. [Figure 19] It is a screen example showing the operation of contract cancellation processing. [Figure 20] It is a block diagram showing the basic hardware configuration of a computer 90.

Mode for Carrying Out the Invention

[0008] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference numerals, and repeated descriptions are omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. In addition, not all of the components shown in the embodiments are essential components of the present disclosure. Furthermore, each drawing is a schematic diagram and is not necessarily strictly illustrated.

[0009] <Configuration of System 1> System 1 of the present disclosure is an information processing system for implementing a service that stores and manages contract information concluded between a plurality of users. System 1 includes information processing devices connected via a network N, specifically a server 10, a first user terminal 20, a second user terminal 30, and an institution server 40. FIG. 1 is a block diagram showing the functional configuration of System 1. 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. FIG. 4 is a block diagram showing the functional configuration of the second user terminal 30.

[0010] Each of the information processing devices is constituted by a computer including an arithmetic device and a storage device. The basic hardware configuration of a computer and the basic functional configuration of a computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, the second user terminal 30, and the institution server 40, descriptions overlapping with the basic hardware configuration and basic functional configuration of a computer described later are omitted.

[0011] <Configuration of Server 10> The server 10 is an information processing device that provides an electronic contract conclusion service between a plurality of users. The server 10 is an information processing device that provides a service for storing and managing contract information concluded between a plurality of users. The server 10 includes a storage unit 101 and a control unit 104.

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

[0013] The application program 1011 is a program that causes the control unit 104 of the server 10 to function as individual functional units.

[0014] 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 the service, their information is stored in a new record in user table 1012. This will enable users to utilize the services provided in this disclosure. Note that users utilizing the services under this disclosure do not necessarily need to be registered in user table 1012. User table 1012 is a table with User ID as the primary key and contains columns for User ID, Username, Email Address, Group ID, and Approval Authority. Figure 5 shows the data structure of user table 1012.

[0015] The User ID is an item that stores user identification information to identify a user. User identification information is an item that is set to a unique value for each user. The username field is used to store the user's real name. However, the username can also be a nickname or any other string of characters. The email address field is used to store the user's email address. The Group ID is an item that stores the group identification information of the group to which the user belongs. Groups are defined by the Group Table 1013 described later, and a user may belong to multiple groups. Approval authority is an item that stores user authorization information regarding contract signing. Users who have the authority to approve contract signing (approval authority) will have information such as True stored in their records. On the other hand, users who do not have the authority to approve contract signing will have information such as False, blank, or null stored in their records. It is also possible to configure the system so that approval permissions can be set according to the contract information. For example, user A may have approval permissions for a specific contract information A, but not for a specific contract information B. The system can be configured to allow approval authority to be set according to the type of contract information (contract information type), such as confidentiality agreements, joint research agreements, and contract work agreements. For example, User A may have approval authority for confidentiality agreements but not for contract work agreements. Alternatively, the system could be configured to store multiple levels (ranks) of permission information depending on the user's department, government office, etc. For example, temporary staff could be assigned rank C, regular employees rank B, managers rank A, and executives rank S in the approval authority field. Then, based on the contract information, such as the contract type and contract amount, only users with approval authority of a predetermined rank or higher (for example, A or higher for non-disclosure agreements) could approve the conclusion of the contract.

[0016] Group table 1013 is a table that stores and manages information about the groups to which a user belongs (group information). A group can be defined as any group to which a user belongs, such as a corporation, company, club, organization, or department within a company. Group table 1013 is a table with Group ID as the primary key and containing columns for Group ID, Group Name, and Administrator ID. Figure 6 shows the data structure of group table 1013.

[0017] The Group ID is an item that stores group identification information used to identify a group. This group identification information is an item with a unique value assigned to each group. The group name is an item that stores the name of the group. The group name can be set to any string. The Administrator ID is an item that stores the user identification information of users who have administrator privileges within a group. Users with administrator privileges can arbitrarily define and set administrator IDs for users who have a certain level of status or authority or higher within a group such as an organization.

[0018] Document table 1014 is a table for storing and managing information (contract information) related to electronic contracts exchanged between the creator and the recipient. Document table 1014 is a table with Document ID as the primary key and containing columns for Document ID, Document Data, Creator ID, Party Data, and Release Flag. Figure 7 shows the data structure of document table 1014.

[0019] The Document ID is an item that stores document identification information used to identify contract information. The document identification information is an item with a unique value assigned to each piece of contract information. Document data is an item that stores contract information (binary or text data). Specifically, document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). The Creator ID is a field that stores user identification information to identify the user who created the contract information. Party data is an item that stores information such as the names, company names, and organization names of the contracting parties related to the contract information. Specifically, party data stores the names, company names, and organization names of the contracting parties who are the counterparties to the contract information, or strings of characters that identify those parties. The termination flag is an item that stores information indicating that a contract has been terminated. The termination flag includes termination grounds for multiple contracting parties. Termination grounds can include "insufficient equity ratio," "insolvency," "classified as a specific corporate organization," "insufficient credit score," "arrest record of officers, directors, etc.," and any other termination grounds can be stored as text information. In addition to arbitrary text information, termination grounds can also be selected and assigned in a format such as a predetermined tag or label.

[0020] Confirmation table 1015 is a table that stores and manages information (confirmer information) including the email address of the user who will be confirming the contract information. Confirmation table 1015 is a table that has columns for document ID, confirmation order, confirmer email address, confirmation flag, language data, access code, and date and time. Figure 8 shows the data structure of confirmation table 1015.

[0021] The document ID is an item that stores the document identification information of the contract information to be reviewed by the verifier. The "Verification Order" field stores information about the order in which contract information is reviewed by the reviewers. The contract information stored by the creator is circulated to the reviewers in the order of the verification order, and verification is performed accordingly. The verifier email address field stores the email address of the person who verifies the contract information. The verifier email address does not need to be registered in advance to use the services related to this disclosure. In other words, the verifier email address does not need to be included in user table 1012. The confirmation flag is an item that stores confirmation identification information to determine whether the confirmation procedure for contract information has been completed by the verifier. When the confirmation of contract information is completed by the verifier, information indicating that the confirmation has been completed, such as a value of True, is stored in the confirmation flag item. Language data is an item that stores information about the verifier's language (language information). The access code is an item that stores the access code set for the verifier. The date and time field stores the date and time when the verifier performed the contract information verification procedure. Specifically, it stores the date and time when the verification identification information was stored in the verification flag field.

[0022] The input item table 1016 is a table that stores and manages information about input items associated with electronic contract information (input item information). Input item table 1016 is a table that has columns for input item ID, document ID, inputter ID, input data, input rules, and date and time. Figure 9 shows the data structure of input item table 1016.

[0023] The input field ID is an item that stores input field identification information used to identify an input field. The document ID is an item that stores the document identification information of the electronic contract information to which the input field is associated. The Inputter ID is a field that stores the user identification information or email address of the person who entered the data into the input field. Specifically, the Inputter ID stores the Creator ID, the email address of the user identified by the Creator ID, and the Confirmer's email address. Input data is an item that stores the input data entered by the user into the input fields. An input rule field is an item that stores information about the input rules for an input item. Input rules can store information about data types such as date, datetime, text, and integer, as well as, for strings, the number of characters, regular expressions for strings, and other arbitrary input rules for any input item. The date and time field stores the date and time when the user entered data into the input field.

[0024] The contract group table 1017 is a table for storing and managing information about contract groups (contract group information). Contract information can be stored and managed in association with one or more cabinets (classification information) for managing contract information. Depending on the information processing service, cabinets may be called groups, tags, labels, etc. The contract group table 1017 is a table that has columns for document ID and cabinet ID. Figure 10 shows the data structure of the contract group table 1017.

[0025] The document ID is an item that stores document identification information used to identify contract information. The cabinet ID stores cabinet identification information to identify a cabinet. The cabinet ID is classification information used to manage and classify contract information.

[0026] <Configuration of the 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, a contract cancellation unit 1044, and an external linkage unit 1045. The control unit 104 realizes each functional unit by executing the application program 1011 stored in the storage unit 101.

[0027] The user registration control unit 1041 processes information of users who wish to use the services related to this disclosure and stores it in the user table 1012. Information stored in the user table 1012 is obtained when a user opens a web page operated by the service provider from any information processing terminal, enters information into a designated input form, and sends it to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, and user registration is completed. As a result, users stored in the user table 1012 can 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 prescribed review and restrict whether or not the user can use the service. The user ID can be any string or number that can identify the user, and may be any string or number desired by the user, or the user registration control unit 1041 may automatically set any string or number.

[0028] The contract creation unit 1042 executes the contract creation process. Details will be described later.

[0029] The contract verification unit 1043 executes the contract verification process. Details will be described later.

[0030] The contract termination unit 1044 executes the contract termination process. Details will be described later.

[0031] The external integration unit 1045 executes external integration processing. Details will be described later.

[0032] <Configuration of the first user terminal 20> The first user terminal 20 is an information processing device operated by a user of the service. The first user terminal 20 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile device such as a smartphone or tablet. It may also be a wearable device such as an HMD (Head Mount Display) or a smartwatch. The first user terminal 20 includes a storage unit 201, a control unit 204, an input device 206, and an output device 208.

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

[0034] 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 services related to this disclosure to the user. The first user ID 2011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the first user terminal 20.

[0035] The application program 2012 may be pre-stored in the memory unit 201, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. Application Program 2012 includes applications such as web browser applications. Application program 2012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the first user terminal 20.

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

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

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

[0039] <Configuration of the second user terminal 30> The second user terminal 30 is an information processing device operated by a user of the service. The second user terminal 30 may be, for example, a stationary PC (Personal Computer), a laptop PC, or a mobile device such as a smartphone or tablet. It may also be a wearable device such as an HMD (Head Mount Display) or a smartwatch. The second user terminal 30 includes a storage unit 301, a control unit 304, an input device 306, and an output device 308.

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

[0041] 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 services related to this disclosure to the user. The second user ID 3011 includes information such as a session ID that is temporarily assigned by the server 10 to identify the user using the second user terminal 30.

[0042] The application program 3012 may be pre-stored in the memory unit 301, or it may be configured to be downloaded from a web server operated by the service provider via a communication interface. Application program 3012 includes applications such as web browser applications. The application program 3012 includes an interpreted programming language such as JavaScript (registered trademark) that is executed on a web browser application stored on the second user terminal 30.

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

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

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

[0046] <Configuration of the institutional server 40> The institutional server 40 is an information processing device that provides credit information services managed and operated by an external credit information research agency, providing credit information about individuals or organizations. Credit information services include corporate databases such as Teikoku Databank and Nikkei Telecom, and databases providing credit information provided by credit card companies, etc. In this disclosure, the institutional server 40 is mainly described as a credit information service that provides credit information, credit information, etc. for each organization, but it may also be described as providing credit information, credit information, etc. for individuals rather than organizations. The institutional server 40 includes a storage unit 401 and a control unit 404.

[0047] <Configuration of the storage unit 401 of the institutional server 40> The storage unit 401 of the institutional server 40 includes an application program 4011 and a credit table 4012.

[0048] Application program 4011 is a program that causes the control unit 404 of the institutional server 40 to function as a functional unit.

[0049] Credit table 4012 is a table for managing and storing credit information of an organization or an individual. Credit table 4012 is a table with Organization ID as the primary key, and contains columns for Organization ID, Organization Name, and Credit Data.

[0050] The Organization ID is an item that stores organizational identification information to identify an organization or individual. Organizational identification information is an item with a unique value assigned to each organization or individual. The organization name is an item used to remember the name of an organization or an individual. Credit data is an item that stores credit information of an organization or individual. The credit information stores strings representing credit status, such as S, A, B, C, D, etc., in order of increasing creditworthiness, according to the degree of creditworthiness of the organization or individual. This represents the credit status of the organization or individual. The credit status of an organization or individual may also be stored as a numerical value between 0 and 100, rather than a string. In addition, labels, tags for classifying organizations or individuals, and text describing the credit information of the organization or individual may also be included. For example, credit data may include information indicating that it is inappropriate for an organization or individual to continue entering into contracts. Credit data may include information about the financial status of an organization or individual. For example, credit data may include information such as an organization's equity ratio, whether the organization or individual is insolvent, and whether the organization or individual has a history of bankruptcy, civil rehabilitation, etc. Credit data may also include information on whether the organization or individual belongs to an organization that is socially undesirable, and whether there is any transaction history with such an organization. Credit data may also include information such as arrest records of officers, etc., within an organization, and arrest records, etc., in the case of an individual.

[0051] <Configuration of the control unit 404 of the institutional server 40> The control unit 404 of the institutional server 40 includes an organization registration control unit 4041. The control unit 404 realizes each functional unit by executing an application program 4011 stored in the storage unit 401.

[0052] <System 1 operation> The following describes each process in System 1. Figure 11 is a flowchart showing the operation of the contract creation process. Figure 12 is a flowchart showing the operation of the contract verification process. Figure 13 is a flowchart showing the operation of the contract termination process. Figure 14 is a flowchart showing the operation of the external integration process. Figure 15 shows an example screen illustrating the operation of the contract creation process. Figure 16 shows an example screen displaying a confirmation request message sent to the second user terminal 30. Figure 17 shows an example screen illustrating the operation of the contract verification process. Figure 18 is an example screen showing the completion message notified to the first user terminal 20. Figure 19 shows an example screen illustrating the operation of the contract termination process.

[0053] In this disclosure, the contract creation process and contract verification process on server 10 are described below.

[0054] <Contract creation process> The contract creation process involves the creator generating electronic contract information and sending it to the verifier.

[0055] Figure 15 shows an example screen illustrating the operation of the contract creation process. The screen 50 displayed on the display 2081 of the first user terminal 20, which is used to create contract information, displays a status 510 indicating the current status of contract information creation, buttons 521, 522, and 523 for specifying input items, a contract information display area 530, document data 531, input items 532, 533, and 534, and a send button 540.

[0056] <Overview of the contract creation process> The contract creation process is a series of steps in which the creator creates electronic contract information, sets the recipient (the verifier) ​​of the electronic contract information, sets the input fields for the electronic contract information, sets input rules for the input fields, receives input data for the input fields from the creator, and sends the electronic contract information to the designated verifier.

[0057] <Details of the contract creation process> In step S101, the contract creation unit 1042 of the server 10 receives contract information from the creator that is to be concluded between the creator and the verifier. Specifically, the first user operates the input device 206 of the first user terminal 20 to create contract information, including document data related to the contract. The document data can be in any data format, such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language), and can be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and sends the created document data and the first user ID 2011 to the server 10. The first user operates the input device 206 of the first user terminal 20 and inputs party data such as the names of the contracting parties, company names, and organization names related to the contract information, and sends it to the server 10. The contract creation unit 1042 of the server 10 receives the first user ID 2011, document data, and party data and stores them in the creator ID, document data, and party data fields of the new record in the document table 1014, respectively. As a result, the contract creation unit 1042 of the server 10 stores the new contract information in the document table 1014.

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

[0059] In step S102, the first user operates the input device 206 of the first user terminal 20 to select and identify the user who will be the verifier (recipient) of the contract information. In this disclosure, the first user selects and identifies the second user as the recipient. The first user operates the input device 206 of the first user terminal 20 to enter the email address of the second user, who will act as the verifier, and sends it 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 verifier email address and document ID fields of the verification table 1015, respectively, and stores the contract information in association with the second user's email address. The first user may also set the language and access code of the second user and store them in association with the second user's email address. At this time, the value 1 is stored in the "Confirmation Order" field of the confirmation table 1015. In step S102, the first user may select and set multiple users to be confirmers. In this case, the value in the "Confirmation Order" field of the users to be confirmers is incremented by one according to the selection order and stored. This sets the circulation order of the confirmers in the contract confirmation process described later. Note that setting the circulation order is not mandatory.

[0060] In step S103, the first user operates the input device 206 of the first user terminal 20 to set the input items for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 to set multiple input fields for the contract information created and stored in step S101. The input fields can be any fields, such as a stamp field for stamping seal data, an input field for entering text data such as signature data, a checkbox field for selecting check items, and a date field for entering the date. The first user operates the input device 206 on the first user terminal 20 and sends a request to the server 10 to add an input item. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information in the document ID of the new record in the input item table 1016. In this way, the newly added input item information is stored in association with the contract information. The first user can store multiple input item information in association with the contract information.

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

[0062] In step S105, the contract creation unit 1042 of the server 10 receives input data for multiple input items entered 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. For example, the first user may input data for a number used to manage contract information, such as a reference number within the group to which they belong, into the input item where a management number is set. The first user may also input data for the date of the contract signing of the contract information into the input item where a contract signing date is set. Once the first user has finished inputting data into the input items, they send the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of server 10 stores the received input data in the input data field of the input item information in the input item table 1016, which is identified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

[0063] The contract creation unit 1042 of 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 operates the input device 206 of the first user terminal 20 and sends a request to the server 10 to send contract information by pressing the send button 540 displayed on the screen 50 for creating contract information.

[0064] In step S106, the contract creation unit 1042 of the server 10 sends a message to the second user notifying them that a request for confirmation of contract information has been sent by the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order column in the confirmation table 1015 and identifies the user who will be the first confirmer (first confirming user) with the smallest value stored in the confirmation order column. In this disclosure, the first confirming user is, for example, the second user. The contract creation unit 1042 of the server 10 sends a message to the second user's email address notifying them that a request for confirmation of contract information has been sent by the first user, via email or other means of communication. The message sent to the second user will include information about a URL (Uniform Resource Locator) containing a document ID to identify the contract information. The URL may directly contain the document ID, or it may contain information such as an encrypted string of the document ID, or a string that can identify the document ID by referring to an unillustrated table. The URL may also contain information to identify the second user. For example, if the second user has not registered for the service related to this disclosure, the URL must contain information to identify the second user.

[0065] If the first user sets an access code for the second user, the first user will communicate the access code to the second user via email or other means. This ensures that even if the message sent to the second user is intercepted by a third party, the third party cannot perform the contract verification process unless they obtain the access code.

[0066] Figure 16 shows an example screen displaying 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 about a URL 62 containing a document ID for identifying contract information.

[0067] <Variation> If the first user selects and sets multiple verifiers in step S102, the system may be configured to allow different input field information to be set independently for each of the multiple verifiers in step S103. For example, if the first user sets two users, the second user and the ninth user, as verifiers, the input fields for the contract start date and contract end date may be set for the second user, and the input field for the contract signing date may be set for the ninth user. In this case, in the contract confirmation process described later, the second user can input data for the contract start date and contract end date, but not for the contract signing date. On the other hand, the ninth user cannot input data for the contract start date and contract end date, but can input data for the contract signing date. The system may also be configured to allow multiple verifiers to be selected and set for a single input field.

[0068] On screen 50 for creating contract information, input fields 532, 533, and 534 are drawn as drawing objects. For input fields 532 and 533, the user identification information "USER-B" of the user who has been selected and set to input the input field is drawn as the assignment, and the input field type is drawn as "Text". For input field 534 related to stamping, the user identification information "USER-C" of the user who has been selected and set to stamp is drawn as the assignment, and the input field type is drawn as "Stamp".

[0069] <Contract Verification Process> The contract verification process is the process by which a verifier confirms the contents of the electronic contract information received from the creator.

[0070] <Overview of contract verification process> The contract verification process is a series of operations that involves receiving access from the verifier, presenting the verifier with a verification screen displaying the contract information, receiving input data from the verifier for the input fields, and receiving data from the verifier regarding the verification of the contract information.

[0071] <Details of contract verification process> In step S301, the second user, who will act as the verifier, can open the webpage specified by the URL by operating the input device 306 or the like on the second user terminal 30 and selecting the URL contained in the received message. This allows the browser application on the second user terminal 30 to open the webpage specified by the URL. As a result, the second user terminal 30 sends a request to the server 10 to execute the contract verification process.

[0072] If the second user's record in the verification table 1015 contains an access code field, the system can request the second user to enter an access code and then compare the entered access code with the access code stored in the second user's record in the verification table 1015 to perform authentication for the second user. Specifically, server 10 sends an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 on the second user terminal 30, enters the access code, and sends it to server 10. The contract verification unit 1043 of server 10 determines whether the received access code matches the access code stored in the second user's record in the verification table 1015. If they match, the contract verification process continues. If they do not match, the contract verification process is terminated. Note that the authentication process using the access code may be omitted.

[0073] The contract verification unit 1043 of server 10 searches the document ID field in document table 1014 based on the document ID included in the received request and obtains contract information. The contract verification unit 1043 of server 10 searches the document ID field in verification table 1015 based on the document ID included in the received request and obtains verifier information. The contract verification unit 1043 of server 10 searches the document ID field in input item table 1016 based on the document ID included in the received request and obtains input item information associated with the contract information.

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

[0075] The contract verification unit 1043 of server 10 searches the user ID field in user table 1012 based on the user identification information of the identified second user and retrieves the approval authority field for the second user. In this disclosure, the approval authority for the second user is stored in user table 1012, but the approval authority for the second user may also be stored for each group to which the second user belongs, or for each contract information or contract information type. The contract verification unit 1043 of server 10 retrieves the approval authority information for the second user for the target contract information. Furthermore, if the second user has not registered for the service related to this disclosure, the processing may be carried out by treating the second user as a user without approval authority.

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

[0077] 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. Furthermore, the confirmation screen presented to the second user may be configured to display the screen in the language specified to the verifier, based on the language information stored in the language data field of the second user's record in confirmation table 1015.

[0078] Figure 17 shows an example of a confirmation screen illustrating the operation of the contract confirmation process. The confirmation screen 70 for approving contract information, displayed on the display 3081 of the second user terminal 30, shows the status 710 indicating the current status of contract information creation, the contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an agreement button 740.

[0079] Specifically, if the approval authority information of the second user obtained in step S302 contains information indicating that the second user has the authority to approve the conclusion of the contract, the contract confirmation unit 1043 of the server 10 determines that the second user is a user who can approve the conclusion of the contract information received by the second user, presents a confirmation screen to the second user, and proceeds to step S304.

[0080] 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 verification process will be terminated.

[0081] In step S304, the contract confirmation unit 1043 of the server 10 receives input for one or more input fields of contract information. Specifically, the second user operates the input device 306 of the second user terminal 30 to input data to input items 732, 733, 734, and 735 set in the contract information. In this disclosure, input item 736 is not assigned to input by the second user, so it is visually indicated that the second user cannot input data for that item.

[0082] 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. If the second user agrees to or accepts the contents, they operate the input device 306 of the second user terminal 30 and press the consent button 740 displayed on the confirmation screen 70 for confirming the contract information. This causes the server 10 to execute a request that includes the document ID, information identifying the second user, and the input data for each input item entered in step S305. The information identifying the second user may also be the second user ID 3011. The contract verification unit 1043 of server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract verification unit 1043 of server 10 searches the verification table 1015 based on the received document ID and information identifying the second user, and stores the value of True in the verification flag field of the record. For example, if the information identifying the second user is an email address, it searches the document ID and verifier email address fields in the verification table 1015 and stores the value of True in the verification flag field of the record. If the information identifying the second user is user identification information, it searches the document ID and verifier email address fields in the verification table 1015 based on the email address of the second user identified by searching the user ID field in user table 1012, and stores the value of True in the verification flag field of the record. The contract confirmation unit 1043 of server 10 stores the received input data in the input data item of input item table 1016, which is identified by the input item ID associated with the input data. As a result, in step S305, the input data entered by the second user is stored as input item information in input item table 1016.

[0083] The contract verification unit 1043 of server 10 determines that the contract verification process has been performed by all verifiers with approval authority. Specifically, the contract verification unit 1043 of server 10 determines that the contract verification process has been performed by all verifiers with approval authority if the verification flag in the verification table 1015 of the verifiers with approval authority has a value of True. In other words, the value of the verification flag in the records of verifiers who do not have approval authority is ignored when making this determination. When the contract verification unit 1043 of server 10 has completed the contract verification process by all authorized verifiers, it sends a message to the first user notifying them that the contract verification process is complete. Similarly, the contract verification unit 1043 of server 10 may also send a message to the second user notifying them that the contract verification process is complete.

[0084] Specifically, the contract confirmation unit 1043 of server 10 sends a message to the first user's email address via email or other means of communication notifying them that the second user has completed the confirmation of the contract information. In other words, it notifies the first user that the second user has approved the conclusion of the contract. As a result, the first user can know that the conclusion of the contract with the second user has been completed. The message sent to the first user may include information about a URL that is an endpoint containing a document ID to identify the contract information.

[0085] Figure 18 shows an example screen displaying 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 about a URL 82 containing a document ID for identifying contract information.

[0086] Similarly, the contract confirmation unit 1043 of server 10 may use a chat service (not shown) or the like to send a message notifying the second user that they have completed the confirmation of the contract information, including a mention to the first user. In other words, 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 conclusion of the contract with the second user has been completed. The message sent to the first user may include information about a URL that is an endpoint containing a document ID to identify the contract information.

[0087] The first user can open the web page specified by the URL included in the received message using the browser application on the first user terminal 20. The first user terminal 20 sends a request to the server 10 to refer to and inquire about the contract information. 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 from the web page screen displayed on the display 2081 of the first user terminal 20 by downloading or other means.

[0088] If multiple users are set as verifiers, the contract verification unit 1043 of server 10 may send a message to all verifiers except the user who last performed the contract verification process, notifying them that the contract verification process is complete. This allows all verifiers to receive notification that the contract verification process has been completed by all verifiers. Furthermore, the contract verification unit 1043 of the server 10 may send a message to a user with administrator-level privileges in a group to which multiple verifiers belong, notifying them that the contract verification process has been completed. Messages can also be sent via email, chat services, etc. This allows the administrator of the group to which the user responsible for verification belongs to receive notification that the contract verification process has been completed.

[0089] Specifically, the contract verification unit 1043 of server 10 retrieves the group ID item by searching the user ID or email address item in user table 1012 based on the user ID or email address. Based on the retrieved group ID item, the contract verification unit 1043 of server 10 retrieves the group ID item in group table 1013, retrieves the administrator ID item, identifies a user with administrator-level privileges by searching the user ID in user table 1012 based on the administrator ID, and sends a message notifying that the contract verification process is complete.

[0090] <Electronic signature processing> Step S305 may include an electronic signature process. In response to the instruction to approve the conclusion of the contract received from the second user in step S305, the contract confirmation unit 1043 of the server 10 stores the contract information received from the first user with an electronic signature indicating that the conclusion of the contract information has been approved. Specifically, the contract verification unit 1043 of server 10 attaches an electronic signature to the contract information and stores it based on the received request. Based on the document ID, the contract verification unit 1043 of server 10 searches the document ID field in the document table 1014 and retrieves the contract information. The contract verification unit 1043 of server 10 affixes an electronic signature to the acquired contract information and stores it in the document data item of the document table 1014. The contract verification unit 1043 of server 10 may update (overwrite) the document data item with the electronically signed contract information, or it may store the contract information before the electronic signature was added in a separate storage device (not shown). The contract verification unit 1043 of server 10 may include any of the following information in the electronic signature: document ID, email address of the first user, email address of the second user, approval date and time, confirmation date and time, authentication method for the approval date and time, authentication method for the confirmation date and time, input data values ​​for each input item, consent (approval) of the first user and the second user, and a timestamp. As a result, the contract verification 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. This prevents impersonation or tampering of the contract information by a third party.

[0091] <Variation> In the contract creation process and contract confirmation process, if the other party to the contract has had their contract terminated due to a contract termination clause in other contract information, the process of suspending or refusing to conclude the contract may be executed. In step S101, the contract creation unit 1042 of the server 10 executes a contract acceptance step to receive second contract information from the second user. The contract creation unit 1042 of the server 10 executes a second counterparty identification step to identify one or more counterparties to the second contract information received in the contract acceptance step. Specifically, when the contract creation unit 1042 of server 10 receives party data, it identifies the other party to the contract, such as the name of the contracting party, company name, or organization name, based on the received party data. The contract creation unit 1042 of server 10 may also identify the user who will be the verifier (recipient) set in step S102 as the other party to the contract, using the contracting party information.

[0092] The contract creation unit 1042 of the server 10 executes a second credit acquisition step, which acquires one or more second credit information records for each of the one or more counterparties identified in the second counterparty identification step. Specifically, the contract termination unit 1044 of server 10 obtains one or more credit information for each of the other parties based on the party information of one or more other parties identified in step S101. Note that the process for obtaining credit information is the same as in step S503 of the contract termination process described later, so the explanation is omitted.

[0093] The contract creation unit 1042 of the server 10 executes a second determination step to determine whether one or more second credit information obtained in the second credit acquisition step corresponds to a second contract termination clause included in the second contract information obtained in the contract acceptance step. The second determination step performs a step of determining whether the contract falls under the second contract termination clause included in the second contract information received in the contract acceptance step, based on the party information and grounds for termination of multiple contract information of the first user associated with the information indicating termination. Specifically, the contract termination unit 1044 of the server 10 determines, based on the one or more credit information for each of the one or more counterparty party information identified in step S101 and the contract information received in step S101, whether each of the one or more counterparty party information corresponds to a specific contract clause (contract termination clause) included in the contract information. The process for determining whether or not a specific contract clause applies is the same as step S504 of the contract termination process described later, so the explanation will be omitted.

[0094] If the contract creation unit 1042 of the server 10 determines in the second determination step that one or more second credit information items fall under the second contract termination clause, it executes a second notification output step to output second notification information to the second user. Specifically, if the party information of one or more counterparties identified in step S101 is determined to fall under a specific contract clause (contract termination clause), the user of the creator will be notified of information indicating that the counterparty to the contract falls under a specific contract clause.

[0095] In step S106, if the contract creation unit 1042 of the server 10 determines in the second determination step that the contract termination clause applies, it executes a rejection step in which it rejects the second user from entering into a contract with one or more parties that fall under the contract termination clause. Specifically, if the party information of one or more counterparties identified in step S101 is determined to be a contract termination clause, the system may take steps to prohibit, refuse, or suspend the user of the document creator from entering into a contract with the counterparty. Specifically, if it is determined to be a contract termination clause, the system may control the execution of steps S102 and later of the contract creation process so that they cannot be carried out.

[0096] <Contract Termination Process> The contract termination process involves presenting the user with contract information that the user has previously been involved in as a creator or verifier, and which is determined to fall under specific contract clauses based on the credit information of the contracting parties, etc. Upon receiving instructions from the user to terminate the contract, the process also stores the relevant contract information in association with information indicating that the contract has been terminated.

[0097] <Overview of contract termination process> The contract termination process involves retrieving contract information in which the user has previously been involved as a creator or verifier, identifying the counterparty to the contract information, obtaining the counterparty's credit information, determining whether each contract item falls under a specific contract clause, presenting the user with a notice containing the contract information that falls under the specific contract clause, and receiving instructions from the user to terminate the contract.

[0098] <Details of contract termination process> The details of the contract termination process are explained below.

[0099] In step S501, the contract termination unit 1044 of the server 10 executes a contract acquisition step to acquire contract information that has been concluded by the first organization as a party and is still in effect. The first user launches a browser application stored in the memory unit 201 of the first user terminal 20, enters a URL to execute the contract cancellation process on the server 10, and opens the contract cancellation process page. The control unit 204 of the first user terminal 20 sends a request to the server 10 to execute the contract cancellation process. The contract termination unit 1044 of server 10 receives the first user ID 2011 included in the received request. Based on the received first user ID 2011, the contract termination unit 1044 of server 10 searches the user ID column in user table 1012 and obtains the email address of the first user. The contract termination unit 1044 of server 10 searches the creator ID field in document table 1014 based on the first user ID 2011, and obtains and identifies the document ID. The contract termination unit 1044 of server 10 searches the confirmer email address field in confirmation table 1015 based on the first user's email address, and obtains and identifies the document ID. Based on the obtained document ID, the contract termination unit 1044 of server 10 searches the document ID field in document table 1014 and obtains multiple contract information, including document data and party data, as contract information that will be candidates for contract termination in the contract termination process. As a result, the contract termination unit 1044 of server 10 obtains and identifies multiple contract information in which the first user was involved in the conclusion of the contract as a creator or confirmer, as contract information that will be candidates for contract termination in the contract termination process. The contract termination unit 1044 of server 10 may, when acquiring contract information, exclude contract information that is no longer in effect due to termination, suspension, cancellation, etc., and acquire and identify only contract information that is still in effect. For example, the contract termination unit 1044 of server 10 may determine whether the contract information is still in effect based on information such as document data, termination flags, and contract termination dates associated with the contract information in the document table 1014, and acquire and identify only the contract information that is determined to be still in effect. In this disclosure, the system is configured to acquire contract information in which the first user was involved as a creator or verifier. However, it is also acceptable to configure the system to acquire and identify contract information that includes the first organization, which is identified by a group ID associated with the first user, in the party data. Alternatively, it is also acceptable to configure the system to acquire and identify contract information that includes any group (first organization) specified by the first user via the input device 206 of the first user terminal 20, in the party data.

[0100] In step S501, the contract acquisition step executes the step of acquiring contract information that is still in effect when the contract is renewed or the contract is amended. Specifically, the contract termination unit 1044 of server 10 periodically retrieves each of the contract information stored in the document table 1014, and if the current date and time fall within a predetermined period before the contract renewal date of the retrieved contract information, it sends a notification via email or other means to the user who created or confirmed the contract information, including a message indicating that the contract renewal date is approaching. The message contains a URL for executing the contract termination process, and the user who receives the notification opens the contract termination page by operating their user terminal and selecting the URL contained in the message. Similarly, when a user of the electronic contract signing service related to this disclosure modifies contract information in which they were involved as a creator or verifier, the system may be configured to open a contract termination processing page. For example, on a page that displays a list of contract information in which the user was involved as a creator or verifier, the contract termination processing may be included in a series of processes (contract modification processing) performed when the user selects the contract information to be modified from the list of displayed contract information. A contract modification refers to a new contract that involves changes to the terms and conditions stipulated in the original contract. This includes, for example, expanding or reducing the rights and obligations agreed upon between the parties, as well as changes to pricing plans and upgrades to service content.

[0101] Typically, in step S501, multiple contract information items in which the first user has previously been involved as a creator or verifier are retrieved and identified. However, for simplicity, the explanation from step S502 onward will mainly focus on the processing of a predetermined single contract information item. In reality, the processing from step S502 onward is performed for each of the multiple contract information items retrieved and identified in step S501.

[0102] In step S502, the contract termination unit 1044 of the server 10 performs a counterparty identification step to identify one or more counterparties of the contract information acquired in the contract acquisition step. Specifically, the contract termination unit 1044 of the server 10 retrieves information (such as strings) to identify the contracting parties, such as the names of the contracting parties, company names, and organization names, which are included in the party data of the contract information obtained in step S501. This identifies one or more counterparties to the contract information obtained in step S501.

[0103] In step S503, the contract termination unit 1044 of the server 10 executes a credit acquisition step in which it acquires one or more credit information for each of the one or more counterparties identified in the counterparty identification step. Specifically, the contract termination unit 1044 of server 10 includes information for identifying one or more contracting parties obtained in step S502 and sends a request to the institutional server 40 to inquire about the credit information of each of the one or more contracting parties. When the control unit 404 of the institutional server 40 receives a request, it searches the credit table 4012 for the organization ID or organization name based on information to identify one or more contracting parties, and retrieves the credit data corresponding to one or more contracting parties. The control unit 404 of the institutional server 40 sends credit data associated with each of the one or more contracting parties as a response to the received request to the server 10. The contract termination unit 1044 of the server 10 obtains credit data for each of the one or more counterparties associated with the contract information obtained in step S501 from the institutional server 40.

[0104] In step S504, the contract termination unit 1044 of the server 10 executes a determination step to determine whether one or more credit information obtained in the credit acquisition step corresponds to a specific contract clause included in the contract information obtained in the contract acquisition step. The determination step involves determining whether one or more pieces of credit information included in the contract information constitute a contract termination clause that would render the contract information as if it never existed from the beginning. Specifically, the contract termination unit 1044 of the server 10 refers to the document data included in the contract information acquired in step S501 and determines whether the credit information of one or more parties associated with the contract information falls under any of the specified contract clauses, such as contract termination clauses, included in the document data. For example, the contract termination unit 1044 of server 10 takes each clause or provision contained in the document data and the credit data of the parties as input data, and outputs information indicating whether the credit data of the parties corresponds to the clause or provision, and makes a determination for any machine learning model, deep learning model, artificial intelligence model (AI model), etc. Alternatively, using arbitrary pattern matching, syntactic analysis techniques, etc., information indicating whether the credit data of a party corresponds to a clause or provision may be obtained and determined, using each clause or provision contained in the document data and the credit data of the party as input data.

[0105] For example, consider a case where a contract between Company A and Company B includes a contract termination clause in the document data within the contract information stating that "the contract will be terminated if the company becomes insolvent." In this case, if the credit data of Company B obtained in step S503 contains information indicating that "Company B is insolvent," the contract termination unit 1044 of the server 10 determines that the contract information falls under a specific contract clause (contract termination clause). On the other hand, if the credit data of Company B does not contain information indicating that "Company B is insolvent," the contract termination unit 1044 of the server 10 determines that the contract information does not fall under a specific contract clause (contract termination clause).

[0106] For example, consider a case where a contract between Company A and Company B includes a contract termination clause in the document data within the contract information stating that "the contract will be terminated if the company is an organization that is socially undesirable, or if it has a history of doing business with such an organization." In this case, if the credit data of Company B obtained in step S503 contains information indicating that "the company is an organization that is socially undesirable, or has a history of doing business with such an organization," the contract termination unit 1044 of the server 10 determines that the contract information falls under a specific contract clause (contract termination clause). On the other hand, if the credit data of Company B does not contain information indicating that "the company is an organization that is socially undesirable, or has a history of doing business with such an organization," the contract termination unit 1044 of the server 10 determines that the contract information does not fall under a specific contract clause (contract termination clause).

[0107] In this disclosure, a contract termination clause has been explained as an example, but the structure may also be such that the contracting parties determine whether or not it falls under any other clause. For example, specific contract clauses include contract termination clauses, contract cancellation clauses, contract modification clauses, etc.

[0108] In step S505, the contract termination unit 1044 of the server 10 executes a notification output step in which it outputs notification information if it is determined in the determination step that one or more credit information items fall under a specific contract clause. In step S505, the notification output step executes the step of outputting notification information if, in the determination step, it is determined that one or more pieces of credit information fall under the contract termination clause. In step S505, the notification output step performs the step of outputting notification information that includes one or more credit information and specific contract clauses that are determined to be applicable in the contract information. Specifically, in step S504, if it is determined that the credit information of each party associated with the contract information falls under a predetermined specific contract clause, such as a contract termination clause, among the clauses included in the document data, the contract termination unit 1044 of the server 10 generates a contract termination processing page containing notification information indicating that the contract information falls under a specific contract clause and sends it to the first user terminal 20. On the other hand, if the contract termination unit 1044 of the server 10 determines that the credit information of each party associated with the contract information does not fall under any of the specified contract clauses, such as contract termination clauses, among the clauses included in the document data, the contract termination unit 1044 of the server 10 generates a contract termination processing page that includes notification information indicating that the contract information does not fall under any of the specified contract clauses, and sends it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received contract cancellation processing page on the display 2081 of the first user terminal 20, and displays and presents the contract information to the first user. Furthermore, the control unit 204 of the first user terminal 20 may, on the contract termination processing page, present to the first user, as a candidate for contract termination, contract information that has been determined to fall under a specific contract clause, in a manner that allows it to be identified from contract information that has been determined not to fall under a specific contract clause. For example, if multiple contract information items in which the first user was involved as creator or verifier are identified in step S501, the display 2081 of the first user terminal 20 displays and presents the multiple contract information items to the first user in a manner that allows identification of contract information items that are candidates for contract termination and contract information items that are not candidates for contract termination.

[0109] Furthermore, the control unit 204 of the first user terminal 20 displays a contract termination processing page containing the relevant specific contract clauses for the contract information related to the contract termination candidate on the display 2081 of the first user terminal 20. This allows the first user to easily confirm which specific contract clauses apply to the contract information related to the contract termination candidate.

[0110] Figure 19 is an example screen showing the operation of the contract termination process. The contract termination process page D10 displayed on the display 2081 of the first user terminal 20 includes contract termination candidates D101A, D101B, D101C, specific contract clauses D111A, D111B, D111C for each contract termination candidate, contracting parties D121A, D121B, D121C, D121D determined to be subject to the specific contract clauses for each contract termination candidate, contract termination buttons D131A, D131B, D131C, and contract information that is not a contract termination candidate D151A, D151B, D151C, D151D. Note that the contract information that is not a contract termination candidate D151A, D151B, D151C, D151D may be configured not to be displayed on the contract termination process page D10.

[0111] Furthermore, information indicating the relevant grounds for each of the specific contract clauses D111A, D111B, and D111C (or, if the specific contract clause is a termination clause, the grounds for termination) may be associated with each of these clauses and displayed on the contract termination processing page D10. For example, when a user operates the input device 206 of the first user terminal 20 and selects a pointer or the like for specific contract clauses D111A, D111B, and D111C, the relevant grounds associated with each specific contract clause may be displayed as a pop-up on the screen. This allows users to see at a glance which specific contract clauses and applicable circumstances apply to each piece of contract information.

[0112] In step S505, the notification output step includes outputting notification information to the first user belonging to the first organization, indicating that the contract information obtained in the contract acquisition step falls under a contract termination clause. In this disclosure, the first user may be defined as a user belonging to a predetermined organization (the first organization) as defined in the group table 1013 via the group ID in the user table 1012. In other words, the contract termination processing page D10 may be configured to be output and presented to the first user belonging to the first organization.

[0113] In step S505, the determination step performs a step of determining whether or not the contract is subject to a contract termination clause included in the contract information obtained in the contract acquisition step, based on the party information and grounds for termination of multiple contract information of other users different from the first user, which are associated with the information indicating that the contract has been terminated. Specifically, the contract termination unit 1044 of the server 10 retrieves contract information stored in the document table 1014, based on the information of one or more contracting parties for the contract information identified in step S502, in which the termination flag contains information indicating that the contract has been terminated for that one or more contracting parties. The contract termination unit 1044 of server 10 searches the party data items in document table 1014 based on the information of one or more contracting parties identified in step S502, and retrieves a record of contract information that includes a termination flag and in which the contracting party is included in the party data. At this time, it is also possible to retrieve only records in which the termination flag contains "information indicating that the contract information has been terminated" for any of the one or more contracting parties, and to exclude records in which "information indicating that the contract information has been terminated" is not stored. The contract termination unit 1044 of server 10 retrieves information on the reason for termination for each contracting party, which is included in the termination flag of the acquired contract information. The contract termination unit 1044 of the server 10 determines that the contract information obtained and identified in step S501 corresponds to a specific contract clause (contract termination clause) if one or more contracting parties to the contract information identified in step S502 have terminated the contract due to a ground for contract termination in other contract information stored in the document table 1014. The contract termination unit 1044 of the server 10 determines that the contract information obtained and identified in step S501 does not fall under a specific contract clause (contract termination clause) if one or more contracting parties to the contract information identified in step S502 have not terminated the contract due to a ground for contract termination in other contract information stored in the document table 1014.

[0114] In other words, in step S505, the contract termination unit 1044 of the server 10 determines that if the contracting party is a person whose contract has been terminated in the past in the contract information stored in the storage unit 101 of the server 10, then the contract information falls under a specific contract clause (contract termination clause). The contract termination unit 1044 of server 10 determines that if the contracting party is not a person whose contract has been terminated in the past in the contract information stored in the storage unit 101 of server 10, then the contract information does not fall under a specific contract clause (contract termination clause).

[0115] Furthermore, when determining whether or not a contract falls under a specific contract clause (contract termination clause), the contract termination unit 1044 of the server 10 may, for each clause or article included in the contract information obtained and identified in step S501, consider the "grounds for termination" included in the termination flag in other contract information stored in the document table 1014 to determine whether or not it falls under a specific contract clause (contract termination clause).

[0116] For example, if the contract information concluded between Company A and Company B includes a contract termination clause stating that "the contract will be terminated if the company is insolvent," and there is a record in other contract information stored in document table 1014 indicating that Company B terminated the contract due to "insolvency," then the contract termination unit 1044 of server 10 determines that the contract information obtained and identified in step S501 corresponds to a specific contract clause (contract termination clause). On the other hand, if there is no record in other contract information stored in document table 1014 indicating that Company B terminated the contract due to "insolvency," then the contract termination unit 1044 of server 10 determines that the contract information obtained and identified in step S501 does not correspond to a specific contract clause (contract termination clause).

[0117] For example, in contract information concluded between Company A and Company B, if the document data included in the contract information contains a contract termination clause stating that "the contract will be terminated if the organization is socially undesirable or has a history of doing business with such an organization," and if there is a record in other contract information stored in document table 1014 indicating that Company B's contract was terminated for the reason of "being socially undesirable or having a history of doing business with such an organization," then the contract termination unit 1044 of server 10 determines that the contract information obtained and identified in step S501 falls under the specific contract clause (contract termination clause). On the other hand, if there is no record in other contract information stored in document table 1014 indicating that Company B's contract was terminated for the reason of "being socially undesirable or having a history of doing business with such an organization," then the contract termination unit 1044 of server 10 determines that the contract information obtained and identified in step S501 does not fall under the specific contract clause (contract termination clause).

[0118] In this disclosure, the first user may determine whether the contract information obtained in step S501 falls under a specific contract clause based solely on contract information in which the first user has previously been involved as a creator or verifier. In this disclosure, the first user may determine whether the contract information obtained in step S501 falls under a specific contract clause, based on contract information in which other users in the group to which the first user belongs have previously been involved as creators or verifiers. In this disclosure, the first user may determine whether the contract information obtained in step S501 falls under a specific contract clause, based on contract information that includes the group to which the first user belongs in the party data. In this disclosure, the first user may determine whether the contract information obtained in step S501 falls under a specific contract clause, based not only on contract information in which the first user has previously been involved as a creator or verifier, but also on contract information previously created by other users. This allows the first user to determine whether a specific contract clause applies to their own contract information based on information regarding the contract information of other users. In other words, decisions such as contract termination can be made more accurately based on various credit information about the other party to the contract.

[0119] In step S506, the contract cancellation unit 1044 of the server 10 executes a cancellation acceptance step in which it receives input from the first user to cancel the contract information acquired in the contract acquisition step. Specifically, the first user selects and presses the contract cancellation button D131A for the contract information to be canceled from among the multiple contract cancellation candidates D101A, D101B, and D101C displayed on the display 2081 of the first user terminal 20 by operating the input device 206 of the first user terminal 20. The control unit 204 of the first user terminal 20 transmits the document ID of the selected contract information to the server 10. The contract cancellation unit 1044 of the server 10 receives and accepts the document ID of the contract information relating to the contract cancellation candidate selected by the first user.

[0120] In step S506, the contract termination unit 1044 of the server 10 executes a contract termination step in which, based on the input operation received in the termination acceptance step, it associates information indicating that the contract information has been terminated with the contract information obtained in the contract acquisition step and stores it. In step S506, the contract termination step performs a step of associating and storing a termination reason indicating that the contract information has been terminated with the contract information obtained in the contract acquisition step, based on the input operation. Specifically, the contract termination unit 1044 of server 10 searches for the document ID in document table 1014 based on the document ID received from the first user terminal 20, and stores information indicating that the contract information has been terminated in the termination flag field of the identified record. As a result, information indicating that the contract information has been terminated is associated with and stored for the contract information relating to contract termination candidate D101A selected by the first user. Furthermore, the contract termination unit 1044 of server 10 may include information regarding the reason for termination in the termination flag. For example, the contract termination unit 1044 of server 10 stores the reason for termination, which is specified by the specific contract clause D111A, in the termination flag. As a result, the reason for termination is associated with and stored in the contract information relating to the contract termination candidate D101A selected by the first user. For example, the external communication unit 1045 of server 10 stores termination grounds such as "contract termination due to insolvency" or "the organization is socially undesirable, or there is a history of transactions with such an organization" in association with contract information.

[0121] <External Integration Processing> External linkage processing is a process that outputs credit information to an external server operated by an external business, which is different from the business that provides the electronic contract signing service related to this disclosure, based on the party data accumulated through the contract termination processing related to this disclosure, in response to inquiries about customer information, etc., from the said external server. In this disclosure, external integration processing by the first user terminal 20 will be explained as an example. However, external integration processing may also be performed from the second user terminal 30 or any other user terminal.

[0122] Services operated by external vendors include CRM (Customer Relationship Management) services provided through CRM systems. Examples of CRM services include Salesforce, Zoho CRM, kintone, and HubSpot.

[0123] <Overview of External Integration Processing> External integration processing is a series of processes that receive customer information queries from external servers (external services), retrieve customer credit information related to those customers, and output customer credit information to the external server.

[0124] <Details of external integration processing> The details of the external integration process are explained below.

[0125] In step S701, the external integration unit 1045 of the server 10 executes a customer inquiry step in which it receives inquiries for one or more customer information relating to one or more customers from a CRM system operated by an external CRM service provider. Specifically, the first user accesses a website or other service provided by the CRM system by operating the input device 206 of the first user terminal 20. The external CRM system reads multiple customer information records of the first user's customers, which are stored in association with the first user within the CRM system, from its storage unit and transmits them to the first user terminal. The control unit 204 of the first user terminal 20 displays the received customer information in a list on the display 2081 of the first user terminal 20. The first user selects a specific customer information from a list of customer information displayed on the display 2081 of the first user terminal 20, and presses an "inquiry button" or the like to query the server 10 for customer information. The customer information includes a string indicating the customer's name, company name, organization name, etc., or an identification code to identify the customer's name, company name, organization name, etc. The control unit 204 of the first user terminal 20 sends an inquiry request containing the selected customer information to the CRM system. When the control unit of the CRM system receives the inquiry request containing the customer information, it sends a request containing the customer information to the server 10. The external integration unit 1045 of server 10 receives and accepts inquiry requests containing customer information from the CRM system. For example, the control unit of the CRM system sends the string "Company B" as customer information to the server 10. The external communication unit 1045 of the server 10 receives and accepts the string "Company B" received from the CRM system.

[0126] In step S702, the external communication unit 1045 of the server 10 performs a third credit acquisition step in which it acquires one or more third credit information for each of the one or more customers identified by one or more customer information. Specifically, the external communication unit 1045 of the server 10 acquires contract information based on the received customer information, which includes the received customer information as a contracting party and stores information indicating that the contract information has been terminated in the termination flag. The external integration unit 1045 of server 10 searches the party data fields in document table 1014 based on the received customer information and obtains contract information including document data, party data, and a termination flag. From the obtained contract information, the external integration unit 1045 of server 10 excludes contract information for which the termination flag does not contain information indicating that the contract information has been terminated, and obtains and identifies contract information for which the termination flag contains information indicating that the contract information has been terminated. In particular, the external communication unit 1045 of the server 10 may use a cancellation flag to retrieve only contract information that was canceled due to the customer related to the received customer information, excluding other contract information. This makes it possible to retrieve and identify contract information that was previously canceled based on customer credit information, etc., related to the customer information received from the CRM system.

[0127] In step S703, the external communication unit 1045 of the server 10 executes a third notification output step, which outputs third notification information, including one or more third credit information acquired in the third credit acquisition step, to the CRM system. In step S703, the third notification output step performs the step of outputting third notification information, which includes party information of multiple contract information of the first user and one or more third credit information based on the grounds for termination, associated with information indicating that the contract has been terminated. Specifically, the external communication unit 1045 of server 10 sends information including the reason for termination, which is included in the termination flag of the identified contract information, to the CRM system as customer credit information relating to the received customer information as a response.

[0128] For example, if the termination flag item in the specified contract information contains the termination reason "Contract terminated due to insolvency" for the contracting party "Company B," then the string of characters indicating "Contract terminated due to insolvency" will be sent to the CRM system as credit information for Company B. For example, if the termination flag item in the specified contract information contains the termination reason "An organization that is socially undesirable, or has a history of doing business with such an organization" for the contracting party "Company B," then the string of characters or other information indicating "An organization that is socially undesirable, or has a history of doing business with such an organization" will be sent to the CRM system as credit information for Company B.

[0129] The control unit of the CRM system transmits the customer credit information received from the server 10 to the first user terminal 20 as a response to the inquiry request in step S701. The control unit 204 of the first user terminal 20 displays the customer credit information on the display 2081 of the first user terminal 20, in association with predetermined customer information selected in step S701, and presents it to the first user.

[0130] The CRM system may, based on the received credit information of the customer, control actions such as preventing approval of transactions with that customer. For example, it may execute a process to suspend approval of transactions with that customer. It may also restrict communication with that customer based on their credit information. This allows businesses to restrict transactions with customers who have insufficient credit information, enabling users to focus on building secure customer relationships and avoid continuing transactions with unsuitable customers.

[0131] <Basic Computer Hardware Configuration> Figure 20 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 comprises at least a processor 901, main memory 902, auxiliary memory 903, and a communication interface 991. These are electrically connected to each other by a communication bus 921.

[0132] The processor 901 is hardware for executing the instruction set written in a program. The processor 901 consists of an arithmetic unit, registers, peripheral circuits, etc.

[0133] Main memory 902 is used to temporarily store programs and data processed by programs, etc. For example, it is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0134] Auxiliary storage device 903 refers to a storage device for saving data and programs. Examples include flash memory, HDD (Hard Disc Drive), magneto-optical disk, CD-ROM, DVD-ROM, and semiconductor memory.

[0135] The IF991 communication interface is an interface for inputting and outputting signals for communication with other computers via a network using wired or wireless communication standards. A network consists of various mobile communication systems built on the internet, LANs, wireless base stations, etc. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0136] Furthermore, by distributing all or part of each hardware configuration across multiple computers 90 and connecting them to each other via a network, a computer 90 can be virtually realized. Thus, the concept of computer 90 includes not only a computer 90 housed in a single enclosure or case, but also a virtualized computer system.

[0137] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 (Figure 20) will be explained. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.

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

[0139] The control unit is realized when the processor 901 reads various programs stored in the auxiliary storage device 903, loads them into the main memory device 902, and executes processing according to those programs. The control unit can realize various functional units that perform information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0140] The memory unit is implemented by the main memory 902 and the auxiliary memory 903. The memory unit stores data, various programs, and various databases. The processor 901 can also reserve memory areas corresponding to the memory unit in the main memory 902 or the auxiliary memory 903 according to the program. The control unit can also cause the processor 901 to perform operations such as adding, updating, and deleting data stored in the memory unit according to the various programs.

[0141] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters. Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.

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

[0143] The communication unit is implemented by the communication IF991. The communication unit provides the functionality to communicate with other computers 90 via the 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 perform information processing on the received information according to various programs. The communication unit can also transmit information output from the control unit to other computers 90.

[0144] <Note> The details described in each of the above embodiments are noted below.

[0145] (Note 1) A contract management program comprising a processor and a memory unit, for causing a computer to store electronic contract procedures between users, wherein the processor executes: a contract acquisition step (S501) for acquiring contract information concluded by a first organization as a party and in the course of the contract; a counterparty identification step (S502) for identifying one or more counterparties to the contract information acquired in the contract acquisition step; a credit acquisition step (S503) for acquiring one or more credit information for each of the one or more counterparties identified in the counterparty identification step; a determination step (S504) for determining whether the one or more credit information acquired in the credit acquisition step corresponds to a specific contract clause included in the contract information acquired in the contract acquisition step; and a notification output step (S505) for outputting notification information if, in the determination step, it is determined that the one or more credit information corresponds to a specific contract clause. This allows users to receive notifications regarding past and ongoing contracts if specific clauses are violated, based on the credit information of the other party to the contract. Users can also identify and address compliance issues that may arise regarding ongoing contracts while the contract is still in effect.

[0146] (Note 2) The contract management program as described in Appendix 1, wherein the determination step (S504) is a step to determine whether one or more credit information items included in the contract information fall under a contract termination clause that would render the contract information invalid from the beginning, and the notification output step (S505) is a step to output notification information if, in the determination step, one or more credit information items are determined to fall under a contract termination clause. This allows users to receive notification, based on the credit information of the other party, if the information regarding an ongoing contract falls under a contract termination clause. Even if grounds for contract termination are discovered retrospectively regarding an ongoing contract, users can take appropriate action, such as disclosing the contract, without delay. This minimizes potential compliance issues arising from ongoing contracts.

[0147] (Note 3) The contract management program described in Appendix 2 is a contract management program in which the notification output step (S505) outputs notification information indicating that the contract information obtained in the contract acquisition step falls under a contract termination clause to the first user belonging to the first organization. This allows users to receive notifications indicating that contract information while the contract is still in effect has been subject to a contract termination clause.

[0148] (Note 4) A contract management program as described in Appendix 3, which executes a cancellation acceptance step (S506) that accepts an input operation from a first user to cancel contract information acquired in the contract acquisition step, and a contract cancellation step (S506) that, based on the input operation accepted in the cancellation acceptance step, associates and stores information indicating that the contract information has been canceled with the contract information acquired in the contract acquisition step. This allows users to associate and store information indicating that a contract has been terminated with contract information that falls under the contract termination clause, thereby enabling them to properly manage their contract information.

[0149] (Note 5) The contract management program described in Appendix 4 is a contract management program in which the determination step (S505) determines whether or not a contract termination clause included in the contract information obtained in the contract acquisition step is applicable, based on the party information of multiple contract information of other users different from the first user, which is associated with information indicating that the contract has been terminated. This makes it possible to retrospectively determine whether contract information that is still in effect has been subject to contract termination based on contract termination by other users.

[0150] (Note 6) The contract termination step (S506) is a step in the contract management program described in Appendix 4, in which, based on an input operation, the program associates and stores with the termination reason indicating that the contract information obtained in the contract acquisition step has been terminated. This allows the system to associate and store the reason for termination with the contract information that is to be terminated.

[0151] (Note 7) The contract management program described in Appendix 5 is a contract management program in which the determination step (S505) determines whether or not a contract is included in the contract termination clauses obtained in the contract acquisition step, based on the party information and termination grounds of multiple contract information of other users different from the first user, associated with information indicating that a contract has been terminated. This makes it possible to retrospectively determine whether contract information that is still in effect has been subject to contract termination based on the grounds for contract termination in other users' contracts.

[0152] (Note 8) The processor performs the following steps: a contract acceptance step (S101) in which it receives second contract information from a second user; a second counterparty identification step (S101) in which it identifies one or more counterparties to the second contract information received in the contract acceptance step; a second credit acquisition step (S101) in which it acquires one or more second credit information for each of the one or more counterparties identified in the second counterparty identification step; and a determination of whether the one or more second credit information acquired in the second credit acquisition step corresponds to a second contract termination clause included in the second contract information acquired in the contract acceptance step. The contract management program described in Appendix 7, which performs a second determination step (S101) and a second notification output step (S101) which outputs second notification information to the second user if, in the second determination step, it is determined that one or more second credit information items fall under the second contract termination clause, wherein the second determination step (S101) is a step in which it determines whether or not the second contract termination clause included in the second contract information received in the contract acceptance step falls under the second contract termination clause, based on the party information and grounds for termination of multiple contract information of the first user associated with information indicating termination. As a result, when a second user enters into a new contract with one or more counterparties, they can receive notification before entering into a contract with those counterparties based on the fact that a contract has been terminated by the first user or other users. The second user may, prior to entering into a contract, be notified that the other party is a person who has terminated a contract with another user of the Services relating to this Disclosure, and may be able to confirm in advance any compliance issues that may arise in the future.

[0153] (Note 10) The contract management program described in Appendix 7 includes a processor that performs a customer inquiry step (S701) which receives an inquiry for one or more customer information relating to one or more customers from a CRM system operated by an external CRM service provider; a third credit acquisition step (S702) which acquires one or more third credit information for each of the one or more customers identified by the one or more customer information; and a third notification output step (S703) which outputs third notification information including the one or more third credit information acquired in the third credit acquisition step to the CRM system, wherein the third notification output step (S703) is a step of outputting third notification information including party information and one or more third credit information based on the grounds for termination of multiple contract information of the first user associated with information indicating termination. This allows the CRM service provider, which is a different business from the contract signing service provider in this disclosure, to output customer credit information based on the customer's contract termination history, etc., to the CRM system in response to customer inquiries from the CRM system operated by the CRM service provider. This allows users of the CRM system to check a customer's credit information during negotiations and other stages prior to contract signing, and to use this information as reference for negotiations. For example, they can decline a deal.

[0154] (Note 11) The contract management program as described in Appendix 1 is a contract management program that outputs notification information including one or more credit information items and specific contract clauses determined to be applicable in the contract information, with the notification output step (S505) being a step of outputting notification information including one or more credit information items and specific contract clauses determined to be applicable in the contract information items. This allows users to check the credit information of the other party to the contract and to see which contract clauses apply.

[0155] (Note 12) The contract acquisition step (S501) is a step in the contract management program described in Appendix 1, in which contract information that is still in effect is acquired when the contract is renewed or amended. This allows users to receive notification when a contract is renewed or amended that a specific clause has been met regarding contract information that was previously entered into and is still in effect.

[0156] (Note 13) An information processing apparatus comprising a processor and a memory unit, wherein the processor executes a program described in any of the appendices 1 to 12. This allows users to receive notifications regarding past and ongoing contracts if specific clauses are violated, based on the credit information of the other party to the contract. Users can also identify and address compliance issues that may arise regarding ongoing contracts while the contract is still in effect.

[0157] (Note 14) An information processing system including an information processing device comprising a processor and a memory unit, wherein the processor executes a program described in any of the appendices 1 to 12. This allows users to receive notifications regarding past and ongoing contracts if specific clauses are violated, based on the credit information of the other party to the contract. Users can also identify and address compliance issues that may arise regarding ongoing contracts while the contract is still in effect.

[0158] (Note 15) An information processing method performed by a computer comprising a processor and a memory unit, wherein the computer executes a program described in any of the appendices 1 to 12. This allows users to receive notifications regarding past and ongoing contracts if specific clauses are violated, based on the credit information of the other party to the contract. Users can also identify and address compliance issues that may arise regarding ongoing contracts while the contract is still in effect. [Explanation of Symbols]

[0159] 1 System, 10 Servers, 101 Storage Unit, 104 Control Unit, 106 Input Device, 108 Output Device, 20 First User Terminal, 201 Storage Unit, 204 Control Unit, 206 Input Device, 208 Output Device, 30 Second User Terminal, 301 Storage Unit, 304 Control Unit, 306 Input Device, 308 Output Device, 40 Organization Server, 401 Storage Unit, 404 Control Unit, 406 Input Device, 408 Output Device

Claims

1. A contract management program comprising a processor and a memory unit, for causing a computer to store electronic contract procedures between users, The aforementioned processor, The contract acquisition step involves the first organization, as a party to the agreement, entering into a contract and obtaining contract information while the contract is still in effect, A counterparty identification step which identifies one or more counterparties to the contract information obtained in the contract acquisition step, A credit acquisition step in which the credit information of each of the one or more credit information A determination step to determine whether the one or more credit information pieces obtained in the credit acquisition step correspond to specific contract clauses included in the contract information obtained in the contract acquisition step, In the determination step, if it is determined that the one or more credit information pieces fall under the specified contract clause, a notification output step outputs notification information indicating that it has been determined to fall under the specified contract clause; A contract management program that executes this process.

2. The determination step is to determine whether the one or more credit information items included in the contract information constitute a contract termination clause that would render the contract information invalid from the beginning. The notification output step is a step in which, in the determination step, it is determined that the one or more credit information items fall under the contract termination clause, and the notification information is output. The contract management program according to claim 1.

3. The notification output step is a step of outputting the notification information indicating that the contract information obtained in the contract acquisition step falls under the contract termination clause to the first user terminal of the first user belonging to the first organization. The contract management program according to claim 2.

4. A cancellation acceptance step that accepts input operations from the first user to cancel the contract information acquired in the contract acquisition step, A contract termination step which stores information indicating that the contract information has been terminated in association with the contract information obtained in the contract acquisition step, based on the input operation received in the termination acceptance step, Execute The contract management program according to claim 3.

5. The determination step is a step of determining whether or not the contract termination clause included in the contract information obtained in the contract acquisition step applies, based on the party information of multiple contract information of other users different from the first user, which is associated with information indicating that the contract has been terminated. The contract management program according to claim 4.

6. The contract termination step is a step of associating and storing with the contract information obtained in the contract acquisition step a reason for termination indicating that the contract information has been terminated, based on the input operation. The contract management program according to claim 4.

7. The determination step is a step of determining whether or not the contract falls under the contract termination clause included in the contract information obtained in the contract acquisition step, based on the party information and termination grounds of multiple contract information of other users different from the first user, which are associated with information indicating that the contract has been terminated. The contract management program according to claim 5.

8. The aforementioned processor, A contract acceptance step that receives second contract information from the second user, A second counterparty identification step for identifying one or more counterparties of the second contract information received in the contract acceptance step, A second credit acquisition step involves acquiring the one or more second credit information of each of the one or more counterparties identified in the second counterparty identification step, A second determination step to determine whether the one or more second credit information obtained in the second credit acquisition step corresponds to a second contract termination clause included in the second contract information obtained in the contract acceptance step, In the second determination step, if it is determined that the one or more second credit information items fall under the second contract termination clause, a second notification output step outputs second notification information to the second user, Execute, The second determination step is a step of determining whether the contract falls under the second contract termination clause included in the second contract information received in the contract acceptance step, based on the party information and grounds for termination of the first user's multiple contract information associated with the information indicating termination. The contract management program according to claim 7.

9. If it is determined in the second determination step that the second contract termination clause applies, the second user refuses to enter into a contract with the one or more parties that fall under the said second contract termination clause, A contract management program according to claim 8, which performs the following:

10. The aforementioned processor, A customer inquiry step that receives inquiries about one or more customer information per customer from a CRM system operated by an external CRM service provider, A third credit acquisition step of acquiring the one or more third credit information for each of the one or more customers identified by the one or more customer information, A third notification output step which outputs third notification information including the one or more third credit information obtained in the third credit acquisition step to the CRM system, Execute, The third notification output step is a step of outputting the third notification information, which includes the party information of the first user's multiple contract information and the one or more third credit information based on the grounds for termination, associated with information indicating that the contract has been terminated. The contract management program according to claim 7.

11. The notification output step is a step of outputting notification information that includes the one or more credit information and the specific contract clause that is determined to apply in the contract information. The contract management program according to claim 1.

12. The aforementioned contract acquisition step is a step in which the contract information that is still in effect is acquired when the contract is renewed or amended. The contract management program according to claim 1.

13. An information processing device comprising a processor and a memory unit, The processor executes the program according to any one of claims 1 to 12. Information processing device.

14. An information processing system including an information processing device comprising a processor and a memory unit, The processor executes the program according to any one of claims 1 to 12. Information processing system.

15. An information processing method performed by a computer comprising a processor and a memory unit, The computer executes the program according to any one of claims 1 to 12. Information processing methods.

Images