Contract management program, information processing device, information processing system, information processing method
The contract management program addresses the issue of notifying parties when a person in charge becomes unavailable by deactivating their account and informing relevant parties, ensuring service continuity.
Patent Information
- Application Number
- JP2022116723
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-07-21
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2042-07-21
AI Technical Summary
When a person in charge who previously performed contract procedures becomes unable to use the service due to retirement or personnel transfer, the parties related to the contract information are not notified that the person can no longer use the service.
A contract management program that includes a processor to identify the first user, deactivate their account, identify associated contract information, and notify involved parties that the user account is unusable.
Ensures that parties involved in past contract information are informed when the person in charge can no longer use the service, maintaining continuity and awareness of account status.
Smart Images

Figure 0007948786000001 
Figure 0007948786000002 
Figure 0007948786000003
Abstract
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 signatures and seals of the parties are also managed as electronic data. Patent Document 1 discloses an information processing system related to digital contracts, which is composed of a creator terminal, a confirmer terminal, and a contract management server.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] There is a problem that when a person in charge (first user) who previously performed procedures for contract information becomes unable to use the service due to retirement, personnel transfer, or the like, the parties related to the contract information for which the person in charge previously performed procedures cannot know that the person in charge can no longer use the service. Accordingly, the present disclosure has been made to solve the above problem, and an object thereof is to provide a technology that enables parties related to contract information for which a person in charge previously performed procedures to know that the person in charge can no longer use the service.
Means for Solving the Problems
[0005] A contract management program comprising a processor and a memory unit, for causing a computer to store electronic contract procedures between first users, wherein the processor performs an identification reception step of receiving first user identification information that identifies a first user; a deactivation step of making the user account of the first user identified by the first user identification information received in the identification reception step unusable; a contract identification step of identifying one or more contract information associated with the first user identification information received in the identification reception step; a party identification step of identifying one or more parties involved in the contract procedures of the one or more contract information identified in the contract identification step; and a notification step of notifying one or more parties identified in the party identification step that the user account of the first user is unusable. [Effects of the Invention]
[0006] According to this disclosure, parties involved in contract information handled by the person in charge in the past can learn that the person in charge is no longer able to use the service. [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] This is a diagram showing the data structure of the input item table 1016. [Figure 10] This is a diagram showing the data structure of the contract document group table 1017. [Figure 11] This is a flowchart showing the operation of the contract document creation process. [Figure 12] This is a flowchart showing the operation of the contract document confirmation process. [Figure 13] This is a flowchart showing the operation of the account deactivation process. [Figure 14] This is a screen example showing the operation of the contract document creation process. [Figure 15] This is a screen example showing a confirmation request message notified to the second user terminal 30. [Figure 16] This is a screen example showing the operation of the contract document confirmation process. [Figure 17] This is a screen example showing a conclusion completion message notified to the first user terminal 20. [Figure 18] This is a screen example showing the operation of the account deactivation process. [Figure 19] This is a block diagram showing the basic hardware configuration of the 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 describing the embodiments, common constituent elements 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 the constituent elements shown in the embodiments are necessarily essential constituent elements of the present disclosure. Each drawing is a schematic diagram and is not necessarily strictly illustrated.
[0009] <Configuration of System 1> The system 1 in the present disclosure is an information processing system for realizing a service that stores and manages contract information concluded between a plurality of users. System 1 includes information processing apparatuses, namely a server 10, a first user terminal 20, and a second user terminal 30, which are connected via a network N. Figure 1 is a block diagram showing the functional configuration of System 1. Figure 2 is a block diagram showing the functional configuration of the server 10. Figure 3 is a block diagram showing the functional configuration of the first user terminal 20. Figure 4 is a block diagram showing the functional configuration of the second user terminal 30.
[0010] Each information processing apparatus is configured by a computer including an arithmetic device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. Descriptions overlapping with the later-described basic hardware configuration of the computer and the basic functional configuration of the computer for each of the server 10, the first user terminal 20, and the second user terminal 30 will be omitted.
[0011] <Configuration of Server 10> The server 10 is an information processing apparatus that provides an electronic contract conclusion service between a plurality of users. The server 10 is an information processing apparatus 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 document group table 1017.
[0013] The application program 1011 is a program for causing the control unit 104 of the server 10 to function as each functional unit.
[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 containing columns for User ID, Username, Email Address, Group ID, Approval Authority, and Enabled Flag. 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 where the user's email address is stored. 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. Based on the contract information, such as 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 contracts. The valid flag is an item in the service that stores information about the validity of a user's account. Specifically, if a user is unable to use the service due to reasons such as leaving their organization, information indicating that the user's account, identified by the user's identification information, is invalid is stored in association with the user information. In addition to retirement, if a user is unable to use the service due to a change in their organizational structure, such as a transfer, promotion, demotion, leave of absence, temporary suspension of work, or death, information indicating that the service is unavailable may be stored in association with the user's information. The valid flag can be edited by the administrator of the service related to this disclosure via a designated website or the like provided by server 10. The enabled flag can be edited by a user with administrator privileges, identified based on the administrator ID associated with the group ID of the group to which the user belongs, by referring to the group table 1013. The enabled flag can be edited by other users belonging to the same or similar group as the group identified based on the group ID of the user's group.
[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 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 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, and Successor ID. 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 an item that stores user identification information to identify the user who created the contract information. The successor ID is a field that stores user identification information to identify a successor user when the user who was involved in the contract information as the creator, verifier, etc., becomes unable to use the service. The contracting party can identify the successor user by referring to the successor ID and contact them regarding contract renewal. Alternatively, a message such as an email may be automatically sent to the successor user upon contract expiration or renewal, guiding them through the contract renewal procedure.
[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 beforehand 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, and a invalidation unit 1044. 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 invalidation unit 1044 executes the account invalidation process. Details will be described later.
[0031] <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.
[0032] <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.
[0033] 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.
[0034] 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.
[0035] <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.
[0036] <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.
[0037] <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.
[0038] <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.
[0039] <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.
[0040] 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.
[0041] 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.
[0042] <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.
[0043] <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.
[0044] <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.
[0045] <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 account deactivation process. Figure 14 shows an example screen illustrating the operation of the contract creation process. Figure 15 shows an example screen displaying a confirmation request message sent to the second user terminal 30. Figure 16 shows an example screen illustrating the operation of the contract verification process. Figure 17 is an example screen showing the completion message notified to the first user terminal 20. Figure 18 shows an example screen illustrating the operation of the account deactivation process.
[0046] In this disclosure, the contract creation process and contract verification process on server 10 are described below. The external server 40 can also perform the same contract creation process and contract verification process. The contract creation process and contract verification process on the external server 40 are the same as those on server 10, respectively, so their description is omitted.
[0047] <Contract creation process> The contract creation process involves the creator generating electronic contract information and sending it to the verifier.
[0048] Figure 14 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.
[0049] <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.
[0050] <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 contract creation unit 1042 of the server 10 receives the first user ID 2011 and the document data and stores them in the creator ID and document 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.
[0051] Screen 50, used for creating contract information, displays the document data 531 stored in document table 1014.
[0052] 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.
[0053] 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.
[0054] 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.
[0055] 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.
[0056] 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.
[0057] 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.
[0058] 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.
[0059] Figure 15 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.
[0060] <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.
[0061] 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".
[0062] <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.
[0063] <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.
[0064] <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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] Specifically, the display 3081 of the second user terminal 30 presents the second user with a confirmation screen that accepts the 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.
[0071] Figure 16 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, a contract information display area 730, document data 731, input items 732, 733, 734, 735, 736, and an agreement button 740.
[0072] 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.
[0073] 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.
[0074] In step S304, the contract confirmation unit 1043 of the server 10 accepts 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.
[0075] 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.
[0076] 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.
[0077] 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.
[0078] Figure 17 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] <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.
[0084] <Account Deactivation Process> The account deactivation process deactivates the user account of a user who is a creator or verifier of the services related to this disclosure, and also performs prescribed processing on contract information for which the user has previously entered into contract procedures.
[0085] <Overview of Account Deactivation Process> The account deactivation process is a series of operations that involves checking the validity of the email addresses of users who use the services related to this disclosure, notifying the administrators of users whose email addresses are determined to be invalid, having the administrators select the users, deactivating the user accounts of the selected users, extracting contract information in which the selected users were involved, identifying the parties involved in the extracted contract information, and notifying those parties.
[0086] <Details of the account deactivation process> The details of the account deactivation process are explained below.
[0087] In step S501, the invalidation unit 1044 of the server 10 performs a determination step to determine whether the first email address or digital certificate of the first user is valid. In the determination step, the invalidation unit 1044 of the server 10 determines that the first user is a user who cannot use the service. Specifically, the invalidation unit 1044 of server 10 refers to the user table 1012 and obtains the email addresses of registered users of the service related to this disclosure. The invalidation unit 1044 of server 10 determines and checks the validity of the acquired email addresses. The invalidation unit 1044 of server 10 extracts and identifies email addresses that have been determined to be invalid from among the acquired email addresses. For example, the invalidation unit 1044 of server 10 may send an email to the acquired email address to check whether or not email is still valid, and if an error email (an email containing information indicating that the email could not be properly delivered to the recipient email address) is returned in response to that email, it may determine that the email address is invalid. Alternatively, the validity of acquired email addresses can be checked by querying external servers that manage the validity of email addresses. The invalidation unit 1044 of server 10 may determine whether a registered user has become a user who cannot use the service, based on whether the electronic certificate has been revoked and its expiration date. Specifically, the invalidation unit 1044 of server 10 may retrieve the digital certificates of registered users (digital certificates associated with the first user) that are pre-stored in the storage unit 101 of server 10, check whether the retrieved digital certificates have expired and their expiration dates, and determine and check the validity of the users. The invalidation unit 1044 of server 10 extracts and identifies the email addresses of users whose retrieved digital certificates are determined to be invalid. An electronic certificate is one of the pieces of information attached to and stored with contract information as proof of identity for registered users of the services related to this disclosure when creating and verifying contract information. By associating and storing information about the electronic certificate with the contract information, it is proven that the registered user associated with that electronic certificate has formally verified and approved the contract information. By verifying the validity of the electronic certificate, it is possible to determine and identify a user who is ineligible to use the services related to this disclosure.
[0088] In step S502, if the invalidation unit 1044 of the server 10 determines that the first email address or digital certificate is not valid, it executes an administrator identification step to identify the administrator associated with the first user. Specifically, the invalidation unit 1044 of server 10 determines that it is invalid in step S501, searches the email address field in user table 1012 based on the extracted email address, and obtains the group ID. Based on the obtained group ID, the invalidation unit 1044 of server 10 searches the group ID field in group table 1013, identifies the administrator ID, and obtains it.
[0089] In step S502, the invalidation unit 1044 of the server 10 performs a second notification step in which it notifies the administrator identified in the administrator identification step of information indicating that the first email address or digital certificate is invalid. Specifically, the invalidation unit 1044 of server 10 searches the user ID field in user table 1012 based on the administrator ID and obtains the email address (administrator email address). The invalidation unit 1044 of server 10 sends an email to the administrator email address containing a message indicating that the first email address or digital certificate of the first user belonging to the group to which the administrator is assigned is invalid. In this disclosure, the notification to the administrator is configured to be sent via email, but notification may also be sent via other publicly known chat services, SMS, telephone, etc. The message sent to the administrator includes a URL to open a page for disabling the account of the first user.
[0090] In step S502, the second notification step obtains contract information in which the first user was involved in the contract procedure, calculates the degree of impact on the first user's contract information based on the obtained contract information, and performs the step of notifying the user. The second notification step involves notifying the first user of at least one of the following: the number of contract information items in which the contract procedure was carried out, or the contract amount.
[0091] Specifically, the invalidation unit 1044 of server 10 determines that the email address is invalid in step S501 and searches the email address field in user table 1012 based on the extracted email address to obtain the user ID. Based on the obtained user ID, the invalidation unit 1044 of server 10 searches the creator ID in document table 1014 to obtain and identify the document ID previously created by the user with the invalid email address. Similarly, based on the extracted email address, the invalidation unit 1044 of server 10 searches the confirmer email address field in confirmation table 1015 to obtain and identify the document ID previously confirmed by the user with the invalid email address. Based on the obtained document ID, it searches the document ID in document table 1014 to obtain contract information. This allows the system to obtain and identify contract information in which the user associated with the extracted email address, which was determined to be invalid, was previously involved.
[0092] The invalidation unit 1044 of server 10 aggregates the number of contract entries and the contract amount for each extracted email address based on the acquired contract information. The invalidation unit 1044 of server 10 notifies the administrator of a message that includes a list of contract entries, the number of contract entries, the contract amount, and the degree of impact on the user's contract information for each user belonging to the group to which the administrator is assigned. This allows the administrator who receives the message to check the past contract information of users belonging to the group they manage whose email address they determined to be invalid, and to see the extent of their influence regarding that contract information.
[0093] In step S503, the invalidation unit 1044 of the server 10 executes an identification reception step in which it receives first user identification information that identifies the first user in response to an input operation by the administrator. Specifically, the administrator user launches a browser application stored in the memory of their administrator terminal, enters a URL to execute the account deactivation process on server 10, and opens the account deactivation page. Alternatively, the administrator may open the account deactivation page by selecting a URL included in the message notified in step S502 and opening it with the browser application. The control unit of the administrator terminal sends a request to the server 10. When the invalidation unit 1044 of the server 10 receives the request, it generates a page for executing the account invalidation process and sends it to the administrator terminal. The control unit of the administrator terminal displays the received page for executing the account invalidation process on the administrator terminal's display. The page for executing the account invalidation process displays a list of one or more users who belong to the group managed by the administrator and who were determined to be invalid in step S501 and extracted, and are available for selection.
[0094] In step S503, the identification reception step involves the administrator performing an input operation to select the first user based on the information notified in the second notification step, and receiving first user identification information that identifies the first user in response to the input operation by the first user.
[0095] Figure 18 shows an example screen illustrating the operation of the account deactivation process. Screen D10, the page for executing the account deactivation process displayed on the administrator terminal's display, includes a checkbox D101, user ID D102, username D103, contract information D104, and a successor input field D105.
[0096] On screen D10, one or more users subject to the deactivation process are displayed in a list, each with a user ID D102 and username D103, which can be selected using the checkbox D101. The administrator operates the input device on the administrator terminal to select one or more user checkboxes D101 for users whose accounts to be disabled from the list of users identified by the user ID D102 and username D102, and sends the user IDs of the selected users to the server 10. The disable unit 1044 of the server 10 receives and accepts the one or more user IDs selected by the administrator.
[0097] In step S503, the invalidation unit 1044 of the server 10 executes an input presentation step in which it presents an input screen for entering one or more successor identification information for each of the one or more contract information identified in the contract identification step. Specifically, screen D10 of the page displayed on the administrator terminal's screen for executing the account deactivation process includes a successor input field D105 for specifying one or more other users (users who will take over or succeed the contract information) for each of the one or more contract information D104 associated with the user ID D102 and username D103 of the one or more users that were determined to be deactivated and extracted in step S501.
[0098] In step S503, the invalidation unit 1044 of the server 10 executes a successor reception step, which receives one or more successor identification information entered on the input screen presented in the input presentation step for each of the one or more contract information identified in the contract identification step. Specifically, by entering the user ID of the successor in the successor input field D105, the administrator can disable the account of the user selected by checkbox D101 and assign a user to take over or succeed each of the one or more contract information D104 that the user was involved with. The administrator, by operating the input device on the administrator terminal, sends the user ID of the successor, which is entered in the successor input field D105 in association with the document ID that identifies the contract information D104, to the server 10. The invalidation unit 1044 of the server 10 receives and accepts the document ID and the user ID of the successor associated with the document ID. This indicates that a user has been assigned to the document ID as a successor.
[0099] In step S504, the invalidation unit 1044 of the server 10 performs an invalidation step that disables the user account of the first user identified by the first user identification information received in the identification reception step. Specifically, the invalidation unit 1044 of server 10 searches the user ID field in user table 1012 based on the user ID of the user selected by the received checkbox D101, and stores "information indicating that it is not valid" in the valid flag field of the found record. As a result, in step S503, the user ID of the user selected by the administrator by checkbox D101 is stored in association with information indicating that it is not valid, and the user account of that user becomes invalid and unusable.
[0100] In step S504, the invalidation unit 1044 of the server 10 executes a successor association step, which associates one or more successor identification pieces of information received in the successor acceptance step with each of the one or more contract information pieces of information. Specifically, when the invalidation unit 1044 of server 10 receives a document ID and the user ID of the successor user associated with the document ID from the administrator terminal, it searches the document ID field in the document table 1014 based on the received document ID and stores the user ID of the successor user in the successor ID field of the identified record. In this way, the invalidation unit 1044 of server 10 associates the document ID with the user ID of the successor user and stores it in the document table 1014.
[0101] In step S505, the invalidation unit 1044 of the server 10 performs a contract identification step to identify one or more contract information associated with the first user identification information received in the identification reception step. In particular, the contract identification step performs a step to identify one or more contract information in which the first user was involved in the contract procedure. Specifically, the invalidation unit 1044 of server 10 searches the user ID field in user table 1012 based on the user ID of the user whose account was invalidated in step S504, and obtains the email address. Based on the received user ID, the invalidation unit 1044 of server 10 searches the creator ID in document table 1014, and obtains and identifies the document ID previously created by the user whose account was invalidated in step S504. Similarly, based on the obtained email address, the invalidation unit 1044 of server 10 searches the confirmer email address field in confirmation table 1015, and obtains and identifies the document ID previously confirmed by the user whose account was invalidated in step S504. This extracts contract information in which the user whose account was invalidated in step S504 was previously involved as a creator or confirmer. This allows the system to identify and retrieve contract information related to contract creation and contract verification processes in which the user whose account was disabled in step S504 was previously involved.
[0102] In step S506, the invalidation unit 1044 of the server 10 performs a party identification step to identify one or more parties involved in the contract procedures of one or more contract information identified in the contract identification step. In particular, the party identification step performs a step to identify one or more parties who are parties to one or more contract information. Specifically, the invalidation unit 1044 of server 10 searches for the document ID in the document table 1014 based on the document ID obtained in step S505, and obtains the creator ID and successor ID. The invalidation unit 1044 of server 10 searches the user ID column in user table 1012 based on the acquired creator ID and obtains the email address of the creator. The invalidation unit 1044 of server 10 searches the user ID column in user table 1012 based on the acquired successor ID and obtains the email address of the successor. Similarly, the invalidation unit 1044 of server 10 searches for the document ID in the confirmation table 1015 based on the document ID obtained in step S505 and obtains the confirmer's email address. This allows us to obtain and identify the email addresses (related party email addresses) of the creator, successor, and verifier, who are the parties associated with the contract information extracted in step S505. Note that email addresses determined to be invalid in step S501, and the email addresses of users newly assigned as successors in step S504, may be excluded from the creator, successor, and verifier email addresses. This is because it is not necessary to notify these users that their accounts have been deactivated.
[0103] In step S507, the invalidation unit 1044 of the server 10 performs a notification step in which it notifies one or more stakeholders identified in the stakeholders identification step that the user account of the first user is unavailable. Specifically, the invalidation unit 1044 of server 10 sends an email to the acquired email address of the person concerned, notifying them that the account of the first user who was involved as a creator or person concerned in the contract information has been invalidated. This allows the person concerned to know that the accounts of other persons concerned in the contract information in which they were involved have been invalidated. The message sent to the email address of the person concerned may also include information about the successor related to the contract information. This allows the person concerned who receives the message to confirm the user who will succeed the invalidated account and to contact that user when the contract expires, terminates, or is renewed.
[0104] <Variation> In this disclosure, step S502 is configured to send an email to the administrator's email address containing a message indicating that the first email address of the first user belonging to the group to which the administrator is assigned is invalid. However, it is also possible to configure the system so that, in step S501, it is determined to be invalid, and a message is sent to the first user associated with the extracted first email address and to other parties involved in the conclusion of specific contract information (creator, verifier). In this case, the user who receives the message notification can learn from the message that the first email address of the first user relating to the contracting party, the creator or verifier, is invalid. The user who receives the message notification can contact another person in charge at the contracting party (such as an administrator) by email or telephone. The administrator who receives the email or telephone contact may then perform the process of disabling the account from step S504 onwards. In this case as well, if the person in charge who previously handled the contract information procedures becomes unavailable due to retirement, transfer, etc., the relevant parties involved in the contract information for which that person previously acted as creator or verifier can be notified that the person in charge is no longer available to use the service, and the relevant parties can be informed that the person in charge is no longer available to use the service.
[0105] <Basic Computer Hardware Configuration> Figure 19 is a block diagram showing the basic hardware configuration of computer 90. Computer 90 includes at least a processor 901, main memory 902, auxiliary memory 903, and a communication interface IF991. These are electrically connected to each other by a communication bus 921.
[0106] 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.
[0107] 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).
[0108] 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.
[0109] 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, such as the internet, LANs, and wireless base stations. 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.
[0110] 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.
[0111] <Basic Functional Configuration of Computer 90> The functional configuration of the computer realized by the basic hardware configuration of computer 90 (Figure 19) is described below. The computer comprises at least one functional unit: a control unit, a memory unit, and a communication unit.
[0112] 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.
[0113] 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.
[0114] 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.
[0115] 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.
[0116] 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.
[0117] 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.
[0118] <Note> The details described in each of the above embodiments are noted below.
[0119] (Note 1) A contract management program comprising a processor and a memory unit, for causing a computer to store electronic contract procedures between first users, wherein the processor performs an identification reception step (S503) of receiving first user identification information that identifies the first user; a deactivation step (S504) of making the user account of the first user identified by the first user identification information received in the identification reception step unusable; a contract identification step (S505) of identifying one or more contract information associated with the first user identification information received in the identification reception step; a party identification step (S506) of identifying one or more parties involved in the contract procedures of the one or more contract information identified in the contract identification step; and a notification step (S507) of notifying one or more parties identified in the party identification step that the user account of the first user is unusable. This allows the system to notify relevant parties involved in the contract information process that the person who previously handled the contract information (the first user) can no longer use the service due to resignation, transfer, etc., and the relevant parties can then be informed that the person is no longer able to use the service.
[0120] (Note 2) The contract identification step (S505) is a step in the contract management program described in Appendix 1 that identifies one or more contract information in which the first user, identified by the first user identification information received in the identification acceptance step, was involved in the contract procedure. This allows, when an employee becomes unable to use the service, to notify those involved in contract information that the employee has previously been involved with, and those involved will be aware that the employee is no longer able to use the service.
[0121] (Note 3) The contract management program as described in Appendix 1, wherein the related party identification step (S506) is a step that identifies one or more related parties who are parties to one or more contract information identified in the contract identification step. This allows, when an employee becomes unable to use the service, to notify the parties involved in the contract information for which the employee previously handled the transaction, and the parties to that contract information to be aware that the employee is no longer able to use the service.
[0122] (Note 4) The processor is a contract management program as described in Appendix 1, which performs a successor reception step (S503) that receives one or more successor identification information for each of the one or more contract information identified in the contract identification step, and a successor association step (S504) that associates the one or more successor identification information received in the successor reception step with each of the one or more contract information. This allows the person in charge to transfer contract information for services they can no longer use to the appropriate successor.
[0123] (Note 5) The contract management program as described in Appendix 4, wherein the processor performs an input presentation step (S503) which presents an input screen for entering one or more successor identification information for each of the one or more contract information identified in the contract identification step, and the successor acceptance step (S503) is a step in which the processor accepts the one or more successor identification information entered on the input screen presented in the input presentation step. This allows the system to receive successor identification information, which designates a successor for contract information that the original user can no longer use, and to transfer the contract information to the appropriate successor.
[0124] (Note 6) The contract management program described in Appendix 1 is a contract management program in which the identification acceptance step (S503) accepts first user identification information that identifies the first user in response to an input operation by the administrator. This allows administrators to select the user who is no longer able to use the service, disable service access for that user, and notify relevant parties that the user is no longer able to use the service.
[0125] (Note 7) The contract management program described in Appendix 6 includes a processor that performs a determination step (S501) to determine whether the first email address or digital certificate of the first user is valid, an administrator identification step (S502) to identify the administrator associated with the first user if it is determined that the first email address or digital certificate is not valid, and a second notification step (S502) to notify the administrator identified in the administrator identification step of information indicating that the first email address or digital certificate is not valid; and an identification reception step (S503) to receive first user identification information that identifies the first user in response to the information notified in the second notification step, which is an input operation performed by the administrator to select the first user based on the information notified in the second notification step. This allows us to prompt the administrator of a client's contact person to disable their user account if their email address becomes invalid due to resignation, transfer, etc.
[0126] (Note 8) The second notification step (S502) is a step in the contract management program described in Appendix 7, in which the first user acquires contract information in which the first user was involved in the contract procedure, calculates the degree of impact on the first user's contract information based on the acquired contract information, and notifies the user. This allows managers of client representatives to visually see what contract information their representatives are involved with and the degree of their influence. This enables them to intuitively understand the extent of the client representatives' influence on contracts.
[0127] (Note 9) The contract management program as described in Appendix 8, wherein the second notification step (S502) is a step in which the first user notifies the number of contract information items in which the contract procedure was carried out or the contract amount of at least one of these. This allows the manager of a client's representative to intuitively see the number of contracts or the contract amount that the representative was involved in.
[0128] (Note 10) The contract management program described in Appendix 1 is a contract management program in which the identification reception step (S503) is a step that receives first user identification information that identifies the first user in response to an input operation by the first user. This allows the person in charge to disable their own service access through an input operation, and also notify relevant parties that the person in charge can no longer use the service.
[0129] (Note 11) An information processing device comprising a processor and a memory unit, wherein the processor executes a contract management program described in any of the appendices 1 to 10. This allows the system to notify relevant parties involved in the contract information process that the person who previously handled the contract information (the first user) can no longer use the service due to resignation, transfer, etc., and the relevant parties can then be informed that the person is no longer able to use the service.
[0130] (Note 12) An information processing system including an information processing device comprising a processor and a memory unit, wherein the processor executes a contract management program described in any of the appendices 1 to 10. This allows the system to notify relevant parties involved in the contract information process that the person who previously handled the contract information (the first user) can no longer use the service due to resignation, transfer, etc., and the relevant parties can then be informed that the person is no longer able to use the service.
[0131] (Note 13) An information processing method performed by a computer comprising a processor and a memory unit, wherein the computer executes a contract management program described in any of the appendices 1 to 10. This allows the system to notify relevant parties involved in the contract information process that the person who previously handled the contract information (the first user) can no longer use the service due to resignation, transfer, etc., and the relevant parties can then be informed that the person is no longer able to use the service. [Explanation of symbols]
[0132] 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
Claims
1. A contract management program for causing a computer, which comprises a processor and a memory unit, to store electronic contract procedures between multiple users, The aforementioned processor, An identification reception step that receives first user identification information to identify the first user, A disabling step which disables the user account of the first user identified by the first user identification information received in the identification acceptance step, A contract identification step that identifies one or more contract information associated with the first user identification information received in the identification reception step, A related party identification step to identify one or more parties involved in the contract procedures of the one or more contract information identified in the contract identification step, A notification step in which information is notified to the one or more parties identified in the aforementioned party identification step that the user account of the first user is unavailable, A contract management program that executes the contract.
2. The contract identification step is a step of identifying one or more contracts in which the first user, identified by the first user identification information received in the identification acceptance step, was involved in the contract procedure. The contract management program according to claim 1.
3. The aforementioned step of identifying parties is a step of identifying the one or more parties who are parties to the one or more contract information identified in the aforementioned step of identifying contracts. The contract management program according to claim 1.
4. The aforementioned processor, A successor reception step that receives one or more successor identification information for each of the one or more contract information identified in the contract identification step, A successor association step is performed to associate the one or more successor identification pieces received in the successor registration step with each of the one or more contract pieces, To execute The contract management program according to claim 1.
5. The aforementioned processor, An input presentation step is provided for each of the one or more contract information items identified in the contract identification step, by presenting an input screen for entering one or more successor identification information. Make it run, The successor registration step is a step of receiving the one or more successor identification information entered on the input screen presented in the input presentation step. The contract management program according to claim 4.
6. The aforementioned identification reception step is a step of receiving first user identification information that identifies the first user in response to an input operation by an administrator. The contract management program according to claim 1.
7. The aforementioned processor, A determination step to determine whether the first email address or digital certificate of the first user is valid, If it is determined that the first email address or digital certificate is not valid, the administrator identification step identifies the administrator associated with the first user, A second notification step involves notifying the administrator identified in the administrator identification step of information indicating that the first email address or digital certificate is invalid, Make it run, The identification reception step is a step in which the administrator performs an input operation to select the first user based on the information notified in the second notification step, and receives first user identification information that identifies the first user in accordance with the input operation. The contract management program according to claim 6.
8. The second notification step involves obtaining contract information in which the first user was involved in the contract procedure, calculating the degree of influence on the first user's contract information based on the obtained contract information, and notifying the first user. The contract management program according to claim 7.
9. The second notification step is to notify the first user of at least one of the number of contract information items or the contract amount in which the first user was involved in the contract procedure. The contract management program according to claim 8.
10. The identification reception step is a step of receiving first user identification information that identifies the first user in response to an input operation by the first user. The contract management program according to claim 1.
11. An information processing device comprising a processor and a memory unit, The processor executes the contract management program according to any one of claims 1 to 10. Information processing device.
12. An information processing system including an information processing device comprising a processor and a memory unit, The processor executes the contract management program according to any one of claims 1 to 10. Information processing system.
13. An information processing method performed by a computer comprising a processor and a memory unit, The computer executes the contract management program according to any one of claims 1 to 10. Information processing methods.
Citation Information
Patent Citations
Computer system and program for providing home delivery service
JP2004126879A
Contract management system, its software, its recording medium, and contract management method
JP2005267052A
Orderer liability support system
JP2006268528A
Electronic data management server
JP2012118702A
Information processing system
JP2017010096A
