Program, method, information processing apparatus, and system

Abstract

To provide a program, a method, an information processing apparatus, and a system for specifying a contract document (electronic data) related to a revision of law or the change in interpretation of the law.SOLUTION: In a system 1, a program causes a server, which serves as an information processing apparatus, the server being a computer equipped with a processor and a storage unit, to manage electronic data agreed between a plurality of users. The program causes the processor to execute: a storage step of storing a plurality of electronic data agreed between the plurality of users; a law revision acquisition step of acquiring law revision information related to a revision of law or a change in interpretation of the law; and a law revision specifying step of specifying predetermined electronic data relating to the law revision information acquired in the law revision acquisition step, out of the plurality of electronic data stored in the storage step.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a program, a method, an information processing device, and a system. [Background technology]

[0002] With the development and spread of computer technology, documents that were previously paper-based are being digitized. For example, documents such as contracts that require the signatures and seals of the parties involved are being considered for management as electronic data. Patent Document 1 discloses an information processing system for digital contracts that includes a creator terminal, a verifying terminal, and a contract management server. Patent Document 2 discloses an information processing system that presents the contract status of an organization based on the contents of a contract. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2017-10096 [Patent Document 2] Patent Publication No. 2020-190905 Summary of the Invention [Problem to be solved by the invention]

[0004] There is an issue with not being able to identify contracts (electronic data) that are related to legal amendments or changes in the interpretation of the law. Therefore, the present disclosure has been made to solve the above problem, and its purpose is to provide a technology for identifying a contract (electronic data) related to a legal amendment or a change in the interpretation of the law. [Means for solving the problem]

[0005] A program having a processor and a memory unit, for managing electronic data agreed upon between multiple users on a computer, wherein the processor executes a storage step of storing multiple electronic data agreed upon between multiple users, an amendment acquisition step of acquiring amendment information relating to legal amendments or changes in the interpretation of law, and an amendment identification step of identifying, from the multiple electronic data stored in the storage step, specific electronic data related to the amendment information acquired in the amendment acquisition step. Effect of the Invention

[0006] According to the present disclosure, it is possible to identify contracts (electronic data) related to legal amendments or changes in the interpretation of the law. [Brief description of the drawings]

[0007] [Figure 1] FIG. 2 is a block diagram showing the functional configuration of the system 1. [Diagram 2] FIG. 2 is a block diagram showing the functional configuration of the server 10. [Diagram 3] 2 is a block diagram showing a functional configuration of a first user terminal 20. FIG. [Figure 4] 2 is a block diagram showing a functional configuration of a second user terminal 30. FIG. [Diagram 5] FIG. 13 is a diagram showing the data structure of a user table 1012. [Figure 6] 13 is a diagram showing the data structure of a group table 1013. FIG. [Figure 7] FIG. 13 shows the data structure of a document table 1014. [Figure 8] FIG. 13 is a diagram showing the data structure of a confirmation table 1015. [Figure 9] 13 is a diagram showing the data structure of an input item table 1016. FIG. [Figure 10] FIG. 13 is a diagram showing the data structure of a contract group table 1017. [Figure 11] FIG. 10 is a diagram showing the data structure of a revision master 1021. [Figure 12]13 is a flowchart showing the operation of a contract creation process. [Figure 13] 13 is a flowchart showing the operation of a contract confirmation process. [Figure 14] 13 is a flowchart showing the operation of a revision specification process. [Figure 15] 13 is a screen example showing the operation of a contract creation process. [Figure 16] 13 is a screen example showing a confirmation request message sent to the second user terminal 30. [Figure 17] 13 is a screen example showing the operation of a contract confirmation process. [Figure 18] 13 is a screen example showing a conclusion completion message notified to the first user terminal 20. [Figure 19] 13 is a screen example showing the operation of the revision specification process. [Figure 20] FIG. 2 is a block diagram showing the basic hardware configuration of a computer 90. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of the present disclosure will be described with reference to the drawings. In all the drawings explaining the embodiment, the same reference numerals are given to common components, and repeated explanations are omitted. Note that the following embodiment does not unduly limit the contents of the present disclosure described in the claims. In addition, not all of the components shown in the embodiment are essential components of the present disclosure. In addition, each figure is a schematic diagram and is not necessarily illustrated strictly.

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

[0010] Each information processing device is configured by a computer equipped with a calculation device and a storage device. The basic hardware configuration of the computer and the basic functional configuration of the computer realized by the hardware configuration will be described later. For each of the server 10, the first user terminal 20, and the second user terminal 30, descriptions that overlap with the basic hardware configuration and basic functional configuration of the computer described later will be omitted.

[0011] <Server 10 Configuration> The server 10 is an information processing device that provides an electronic contract conclusion service between a plurality of users. The server 10 is an information processing device that provides a service of 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 the storage unit 101 of the server 10> The memory unit 101 of the server 10 includes an application program 1011 , a user table 1012 , a group table 1013 , a document table 1014 , a confirmation table 1015 , an input item table 1016 , a contract group table 1017 , and an amendment master 1021 .

[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] The user table 1012 is a table for storing and managing information on member users (hereinafter, users) who use the service. When a user registers to use the service, the user's information is stored in a new record in the user table 1012. This allows the user to use the service according to the present disclosure. Note that a user who uses a service according to the present disclosure does not necessarily need to be registered in the user table 1012. The user table 1012 is a table having a user ID as a primary key, and columns of user ID, user name, email address, group ID, and approval authority. FIG. 5 is a diagram showing the data structure of the user table 1012. As shown in FIG.

[0015] The user ID is an item for storing user identification information for identifying a user. The user identification information is an item for which a unique value is set for each user. The user name is an item for storing the name of the user. The user name may be set to any character string such as a nickname instead of a name. The email address is an item for storing the email address of the user. The group ID is an item for storing group identification information of a group to which a user belongs. Groups are defined by a group table 1013, which will be described later, and a user may belong to multiple groups. The approval authority is an item that stores authority information regarding approval of a user. For a user who has the authority to approve the conclusion of a contract (approval authority), information that indicates the authority to approve the conclusion of a contract, such as True, is stored. On the other hand, for a user who does not have the authority to approve the conclusion of a contract, information that indicates the lack of authority to approve the conclusion of a contract, such as False, blank, or null value, is stored. The approval authority may be set according to the contract information. For example, a user A may have approval authority for specific contract information A, but not approval authority for specific contract information B. The system may be configured so that approval authority can be set according to the type of contract information (contract information type) such as a confidentiality agreement, a joint research agreement, a contract agreement, etc. For example, the system may be configured so that user A has approval authority for a confidentiality agreement but does not have approval authority for a contract agreement. Alternatively, the system may be configured to store multiple levels (levels, ranks) of authority information depending on the user's department, government office, etc. For example, information such as C for temporary staff, B for general employees, A for managers, and S for executives may be stored in the approval authority field, and only users with approval authority of a predetermined rank or higher (e.g., A or higher for non-disclosure agreements) may be able to approve the conclusion of a contract depending on the contract type information, contract amount, etc. of the contract information.

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

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

[0018] The document table 1014 is a table for storing and managing information (contract information) relating to an electronic contract exchanged between a creator and a recipient. The document table 1014 is a table having the document ID as a primary key, and columns of the document ID, document data, creator ID, revision flag, action data, and memo data. FIG. 7 is a diagram showing the data structure of the document table 1014. As shown in FIG.

[0019] The document ID is an item for storing document identification information for identifying contract information. The document identification information is an item for which a unique value is set for each contract information. The document data is an item that stores contract information (binary or text data) of a contract related to the conclusion of the contract. Specifically, the document data includes data in any data format such as PDF (Portable Document Format), Word, and XML (Extensible Markup Language). Creator ID is an item for storing user identification information for identifying the user who created the contract information. The revision flag is an item for storing information indicating whether or not there is an effect based on the revision information. Specifically, it includes the revision ID of the revision information described below, the relevant rule information, etc. The policy data is an item for storing policy information related to countermeasures taken in response to revision information. The policy information will be described in detail in relation to the revision master 1021, which will be described later. The memo data is an item for storing character string information such as memos input by the user for the revision information. Specifically, the user stores a response policy for the revision information by adding a memo.

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

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

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

[0023] The input item ID is an item that stores input item identification information for identifying an input item. The document ID is an item that stores the document identification information of the electronic contract information with which the input item is associated. The inputter ID is an item that stores the user identification information or email address of the inputter who inputs input data into the input item. Specifically, the inputter ID stores the creator ID, the email address of the user identified by the creator ID, the verifying person's email address, etc. The input data is an item that stores input data entered into an input item by a user. The input rule is a field that stores input rule information related to the input rules of the input fields. As input rules, in addition to data types such as date, datetime, text, and integer, it is possible to store input rule information related to any input field, such as the number of characters in a text string or the regular expression of the text string. The date and time is an item for storing the date and time when the input data is input into the input item by the inputter.

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

[0025] The document ID is an item for storing document identification information for identifying contract information. The cabinet ID stores cabinet identification information for identifying a cabinet. The cabinet ID is classification information for managing and classifying contract information.

[0026] The amendment master 1021 is a table for storing and managing information (amendment information) relating to amendments to laws or changes in the interpretation of laws. The revision master 1021 is a table having the revision ID as a primary key and columns of the revision ID, title, revision content, rule data, and policy data. FIG. 11 is a diagram showing the data structure of the revision master 1021.

[0027] The revision ID is an item for storing revision identification information for identifying revision information. The revision identification information is an item in which a unique value is set for each revision information. The title is an item for storing the title, name, etc. of the revision information. The revision content is an item for storing the content of the revision information. Specifically, in the case of a legal amendment, the amendment includes the legal provisions and clauses before the amendment and the legal provisions and clauses after the amendment. It may also include sentences explaining the interpretations of the legal provisions and clauses before the amendment and the legal provisions and clauses after the amendment. In addition, in the case of a change in the interpretation of the law, it includes sentences explaining the legal interpretation before the change and the legal interpretation after the change. Changes in the interpretation of the law include sentences explaining the legal interpretation before the change and the legal interpretation after the change. Changes in the interpretation of the law include, for example, cases in which the range of interest that was previously interpreted as lawful in an interest contract with a money lender is now interpreted as illegitimate due to a judicial decision, etc. The rule data is an item for storing rule information related to conditions. The revision information may include multiple pieces of rule information. The rule information includes information about conditions that specify the contract type of the contract information that is affected based on the revision information. For example, the contract type includes the following: Business and Commercial Contracts ·Purchase contracts, sales contracts, sales consignment contracts, franchise contracts Real estate / Property contract Rental contracts, employment and labor contracts, labor contracts, consulting contracts, and consignment contracts Intellectual Property & License Agreements Non-disclosure agreements (NDAs), license agreements, software development agreements Service provision agreement ·Joint research agreements, marketing agreements, cloud service agreements The rule information may include information regarding conditions that specify the clauses or provisions of the contract information that are affected based on the revision information. For example, the rule information may include information that specifies specific clauses or provisions such as "joint guarantor," "damage compensation clause," and "late interest." The rule information may include information on conditions related to the contents of clauses and articles of the contract information that are affected based on the amendment information. For example, it may include information on the specific contents contained in the clauses and articles, such as "the guarantor's liability limit is not specified in the guarantor clause" or "the late interest is XX% or more." The conditions related to the contents of the clauses and articles may include information on conditions related to the clauses and articles of the contract information that include specific keywords such as "pseudonym information." The policy data is an item for storing policy information related to measures taken in response to amendment information and rule information. Specifically, the policy information includes information related to the contents of the contract information to be amended in accordance with the amendment contents. For example, the policy information includes information such as "the liability limit of the guarantor in the guarantor clause must be kept at approximately ●●", "late interest must be set at ●●% or less", "the creditor principle must be abolished in the case of house purchases, etc., and the transfer of risk for which the right to refuse performance of the counter-performance obligation is given as the effect of risk bearing must be set at the time of delivery". The policy information may store information related to measures taken for each amendment information, or may store information related to measures taken for each of a plurality of rule information included in the amendment information. The policy data may include information regarding deadlines according to the amendment information, such as "Action must be taken at the next contract renewal," "Contract changes are required," "Templates need to be revised," and "Contracts need to be re-signed by the effective date."

[0028] <Configuration of the control unit 104 of the 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 revision unit 1044. The control unit 104 executes an application program 1011 stored in the storage unit 101 to realize each functional unit.

[0029] The user registration control unit 1041 performs processing to store, in the user table 1012, information on users who wish to use the service according to the present disclosure. The information stored in the user table 1012 is generated when a user opens a web page operated by a service provider from any information processing terminal, enters information into a specific input form, and transmits the information to the server 10. The user registration control unit 1041 stores the received information in a new record in the user table 1012, completing the user registration. This allows the user stored in the user table 1012 to use the service. Before the user registration control unit 1041 registers user information in the user table 1012, the service provider may carry out a predetermined examination to restrict whether or not the user is permitted to use the service. The user ID may be any character string or number that can identify the user, any character string or number desired by the user, or an arbitrary character string or number may be automatically set by the user registration control unit 1041.

[0030] The contract preparation unit 1042 executes a contract preparation process, the details of which will be described later.

[0031] The contract confirmation unit 1043 executes a contract confirmation process, the details of which will be described later.

[0032] The revision unit 1044 executes a revision specification process, the details of which will be described later.

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

[0034] <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 .

[0035] The first user ID 2011 is an account ID of the user. The user transmits the first user ID 2011 from the first user terminal 20 to the server 10. The server 10 identifies the user based on the first user ID 2011 and provides the user with the service according to the present disclosure. The first user ID 2011 includes information such as a session ID temporarily assigned by the server 10 when identifying the user using the first user terminal 20.

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

[0037] <Configuration of the control unit 204 of the first user terminal 20> The control unit 204 of the first user terminal 20 includes an input control unit 2041 and an output control unit 2042. The control unit 204 executes an application program 2012 stored in the storage unit 201, thereby realizing each functional unit.

[0038] <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 .

[0039] <Configuration of the 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 .

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

[0041] <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 .

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

[0043] The application program 3012 may be stored in advance in the storage unit 301, or may be configured to be downloaded from a web server operated by a service provider via a communication IF. Application programs 3012 include applications such as a web browser application. The application program 3012 includes an interpreted programming language such as JavaScript (registered trademark) that runs on a web browser application stored on the second user terminal 30.

[0044] <Configuration of the control unit 304 of the second user terminal 30> The control unit 304 of the second user terminal 30 includes an input control unit 3041 and an output control unit 3042. The control unit 304 executes an application program 3012 stored in the storage unit 301, thereby realizing each functional unit.

[0045] <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 .

[0046] <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 .

[0047] <System 1 Operation> Each process of the system 1 will be described below. FIG. 12 is a flowchart showing the operation of the contract creation process. FIG. 13 is a flowchart showing the operation of the contract confirmation process. FIG. 14 is a flowchart showing the operation of the revision specification process. FIG. 15 is a screen example showing the operation of the contract creation process. FIG. 16 is an example of a screen showing a confirmation request message sent to the second user terminal 30. In FIG. FIG. 17 is a screen example showing the operation of the contract confirmation process. FIG. 18 is an example of a screen showing a conclusion completion message sent to the first user terminal 20. In FIG. FIG. 19 is a screen example showing the operation of the revision specification process.

[0048] In this disclosure, the contract creation process, contract confirmation process, and amendment specification process in the server 10 will be described below.

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

[0050] 15 is an example of a screen showing the operation of the contract creation process. A screen 50 for creating contract information, which is displayed on the display 2081 of the first user terminal 20, displays a status 510 showing the current creation status of the contract information, 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.

[0051] <Outline of contract creation process> The contract creation process is a series of processes in which the creator creates electronic contract information, sets the verifying party to whom the electronic contract information will be sent, sets input fields for the electronic contract information, sets input rules for the input fields, accepts input data for the input fields from the creator, and sends the electronic contract information to the set verifying party.

[0052] <Details of contract creation process> The contract creation process will be described in detail below.

[0053] In step S101, the contract preparation unit 1042 of the server 10 receives, from the preparer, contract information to be the subject of a contract to be concluded between the preparer and the verifyer. 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 may be in any data format such as PDF (Portable Document Format), Word, or XML (Extensible Markup Language) and may be included in the contract information. The first user operates the input device 206 of the first user terminal 20 and transmits the created document data and the first user ID 2011 to the server 10. The contract creation unit 1042 of the server 10 accepts the received first user ID 2011 and document data, and stores them in the creator ID and document data items of a 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.

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

[0055] In step S102, the first user operates the input device 206 of the first user terminal 20 to select and specify a user who will be a confirmer (recipient) of the contract information. In the present disclosure, it is assumed that the first user selects and specifies a second user as the recipient. The first user operates the input device 206 of the first user terminal 20, inputs the email address of the second user who will be the checker, and transmits 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 checker email address and document ID items of the confirmation table 1015, respectively, and stores the contract information in association with the email address of the second user. The first user may set the language and access code of the second user, and store them in association with the email address of the second user. At this time, a value of 1 is stored in the confirmation order field of confirmation table 1015. In step S102, the first user may be able to select and set multiple users to be the confirmers. In this case, the value of the confirmation order field of the users to be the confirmers is incremented by one and stored according to the selection order. This sets the circulation order of the confirmers in the contract confirmation process described later. Note that setting the circulation order is not essential.

[0056] In step S103, the first user operates the input device 206 of the first user terminal 20 to set input items for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 and sets multiple input items for the contract information created and stored in step S101. The input items can be any input item, such as a seal field for stamping seal data, an input field for inputting text data such as signature data, a check box field for selecting check items, a date field for inputting a date, etc. The first user operates the input device 206 of the first user terminal 20 to send a request to add an input item to the server 10. When the contract creation unit 1042 of the server 10 receives the request, it stores the document ID of the contract information as the document ID of a new record in the input item table 1016. As a result, the newly added input item information is stored in association with the contract information. The first user can store multiple pieces of input item information in association with the contract information.

[0057] In step S104, the first user sets input rules for each input item to be added. The first user operates the input device 206 of the first user terminal 20 or the like to specify input rules for each piece of input item information set in step S103, and transmits 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 piece of input item information in the input item table 1016. This makes it possible to set input rules for each input item.

[0058] In step S105, the contract preparation unit 1042 of the server 10 accepts input data for a plurality of input items input by the first user. Specifically, the first user operates the input device 206 of the first user terminal 20 to input input data for each input item set in step S104. For example, the first user may input input data of a number for managing contract information, such as a serial number for a group to which the first user belongs, into an input item in which a management number is set. The first user may input input data of the contract conclusion date of the contract information into an input item in which a contract conclusion date is set. After completing input of the input data into the input items, the first user transmits the input item ID and input data for each input item to the server 10. The contract creation unit 1042 of the server 10 receives and accepts the input item ID and input data for each input item. The contract creation unit 1042 of the server 10 stores the received input data in the input data item of the input item information of the input item table 1016 specified by the received input item ID. As a result, the input data entered by the first user is stored in the input item table 1016.

[0059] The contract creation unit 1042 of the server 10 receives an instruction from the first user to request the second user to conclude a contract for the contract information. Specifically, the first user operates the input device 206 of the first user terminal 20 and presses the send button 540 displayed on the screen 50 for creating contract information, thereby sending a request to send the contract information to the server 10.

[0060] In step S106, the contract creation unit 1042 of the server 10 transmits a message to the second user notifying that a request to confirm the contract information has been sent from the first user. Specifically, the contract creation unit 1042 of the server 10 searches the confirmation order field of the confirmation table 1015, and identifies a user (first confirmation user) who will be the first confirmer and who has the smallest value stored in the confirmation order field. In the present disclosure, the first confirmation user is, as an example, the second user. The contract creation unit 1042 of the server 10 transmits a message to the email address of the second user by a communication means such as email notifying that a request to confirm the contract information has been sent from the first user. The message to be notified to the second user includes URL (Uniform Resource Locator) information including a document ID for identifying the contract information. The URL may directly include the document ID, or may include information such as a character string obtained by arbitrarily encrypting the document ID, or a character string that can identify the document ID by referring to a table (not shown). The URL may also include information for identifying the second user. For example, if the second user is not registered as a user with the service according to the present disclosure, the URL needs to include information for identifying the second user.

[0061] When the first user sets an access code for the second user, the first user separately communicates the access code to the second user by means of e-mail, etc. In this way, even if the message notified to the second user is obtained by a third party, the third party cannot execute the contract confirmation process unless he or she obtains the access code.

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

[0063] <Modification> When the first user selects and sets multiple checkers in step S102, the first user may be configured to set different input item information for each of the multiple checkers independently in step S103. For example, when the first user sets two users, the second user and the ninth user, as checkers, the first user may set the input items of the contract start date and contract end date for the second user, and the input item of the contract conclusion date for the ninth user. In this case, in the contract confirmation process described later, the second user can input input data for the input items of the contract start date and contract end date, but cannot input input data for the input item of the contract conclusion date. On the other hand, the ninth user cannot input input data for the input items of the contract start date and contract end date, but can input input data for the input item of the contract conclusion date. The first user may be configured to select and set multiple checkers for one input item information in a duplicated manner.

[0064] On screen 50 for creating contract information, input items 532, 533, and 534 are drawn as drawing objects. In input items 532 and 533, user identification information "USER-B" of a user who has selected and set to input the input item is drawn as an assignment, and an item called "text" is drawn as an input item type. In input item 534 related to stamping, user identification information "USER-C" of a user who has selected and set to stamp is drawn as an assignment, and an item called "stamp" is drawn as an input item type.

[0065] In addition, in the present disclosure, a configuration in which the contract information and various input information are stored in various tables of the server 10 in each step has been disclosed as an example, but is not limited thereto. For example, in the transmission step of step S106, the contract information and various input information input by the creator may be collectively stored in various tables of the server 10.

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

[0067] <Outline of contract confirmation process> The contract confirmation process is a series of processes that accepts access from a confirmer, presents a confirmation screen displaying contract information to the confirmer, accepts input data for input fields from the confirmer, and accepts data regarding confirmation of the contract information from the confirmer.

[0068] <Details of contract confirmation process> The contract confirmation process will be described in detail below.

[0069] In step S301, the second user who is to be the confirmer can select the URL described in the received message by operating the input device 306 of the second user terminal 30 or the like, thereby opening the web page specified by the URL with the browser application of the second user terminal 30. As a result, the second user terminal 30 transmits a request to the server 10 to execute the contract confirmation process.

[0070] If an access code item is stored in the record of the second user in confirmation table 1015, the second user is requested to input an access code, and the input access code is compared with the access code stored in the record of the second user in confirmation table 1015, thereby performing authentication processing for the second user. Specifically, the server 10 transmits an input screen for authenticating the access code to the second user terminal 30. The second user operates the input device 306 of the second user terminal 30 to input the access code and transmit it to the server 10. The contract confirmation unit 1043 of the server 10 determines whether the received access code matches the access code stored in the record of the second user in the confirmation table 1015, and if they match, continues the contract confirmation process. On the other hand, if they do not match, stops the contract confirmation process. Note that the authentication process using the access code may be omitted.

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

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

[0073] In step S303, the contract confirmation unit 1043 of the server 10 generates a confirmation screen based on the acquired contract information, confirmer information (information for identifying the second user), and input item information, and transmits the generated confirmation screen to the second user terminal 30.

[0074] Specifically, the display 3081 of the second user terminal 30 presents a confirmation screen for accepting an operation to approve the contract information to the second user. The second user checks and approves the contract information displayed on the display 3081 of the second user terminal 30. In addition, the confirmation screen presented to the second user may be configured to be presented to the second user in a language specified for the confirmer, based on the language information stored in the language data item of the second user's record in confirmation table 1015.

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

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

[0077] 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 in the contract information received from the first user. The second user checks the contract information and input data displayed on the display 3081 of the second user terminal 30, and if he or she agrees or accepts the contents, he or she operates the input device 306 of the second user terminal 30 or the like to press the Agree button 740 displayed on the confirmation screen 70 for confirming the contract information, thereby executing a process of transmitting a request including the document ID, information identifying the second user, and the input data for each input item entered in step S305 to the server 10. The information identifying the second user may be the second user ID 3011. The contract confirmation unit 1043 of the server 10 stores information indicating that the second user has confirmed the contract information based on the received request. Specifically, the contract confirmation unit 1043 of the server 10 searches the confirmation table 1015 based on the received document ID and information identifying the second user, and stores a value of True in the confirmation flag field of the record. For example, if the information identifying the second user is an email address, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015, and stores a value of True in the confirmation flag field of the record. If the information identifying the second user is user identification information, the contract confirmation unit 1043 searches the document ID and confirmer email address fields of the confirmation table 1015 based on the email address of the second user identified by searching the user ID field of the user table 1012, and stores a value of True in the confirmation flag field of the record. The contract confirmation unit 1043 of the server 10 stores the received input data in the input data item of the input item table 1016 specified by the input item ID associated with the input data. As a result, in step S305, the input data entered by the second user is stored as input item information in the input item table 1016.

[0078] The contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all the checkers. Specifically, the contract confirmation unit 1043 of the server 10 determines that the contract confirmation process has been performed by all the checkers when a value of True is stored in the confirmation flag of the checker's record in the confirmation table 1015. When the contract confirmation process has been performed by all the confirmers, the contract confirmation unit 1043 of the server 10 transmits a message to the first user notifying the completion of the contract confirmation process. Similarly, the contract confirmation unit 1043 of the server 10 may transmit a message to the second user notifying the completion of the contract confirmation process.

[0079] Specifically, the contract confirmation unit 1043 of the server 10 sends a message to the email address of the first user by a communication means such as email to notify the first user that the second user has completed confirmation of the contract information. In other words, the first user is notified that the second user has approved the conclusion of the contract. This allows the first user to know that the 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 end point including a document ID for identifying the contract information.

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

[0081] Similarly, the contract confirmation unit 1043 of the server 10 may use a chat service (not shown) or the like to send a message notifying the first user that the second user has completed 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 end point including a document ID for identifying the contract information.

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

[0083] When multiple users are set as confirmers, the contract confirmation unit 1043 of the server 10 may send a message to confirmers other than the user who last executed the contract confirmation process to notify them that the contract confirmation process has been completed. This allows the confirmers to receive a notification that the contract confirmation process has been completed by all confirmers. Furthermore, the contract confirmation unit 1043 of the server 10 may transmit a message notifying a user having authority equivalent to that of an administrator in a group to which a plurality of confirmers belong that the contract confirmation process has been completed. The message may be sent via email, chat service, etc. This allows the administrator in the group to which the user who performed the check belongs to to be notified that the contract check process has been completed.

[0084] Specifically, the contract confirmation unit 1043 of the server 10 acquires the group ID item by searching the user ID or email address item in the user table 1012 based on the user ID or email address. The contract confirmation unit 1043 of the server 10 searches the group ID item in the group table 1013 based on the acquired group ID item, acquires the administrator ID item, identifies a user having authority equivalent to that of an administrator by searching the user ID in the user table 1012 based on the administrator ID, and transmits a message notifying that the contract confirmation process has been completed.

[0085] <Electronic signature processing> An electronic signature process may be included in step S305. In response to an 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 adds an electronic signature indicating that the conclusion of the contract of the contract information has been approved to the contract information received from the first user, and stores the same. Specifically, the contract confirmation unit 1043 of the server 10 assigns a digital signature to the contract information based on the received request and stores it. The contract confirmation unit 1043 of the server 10 searches the document ID item of the document table 1014 based on the document ID, and acquires the contract information. The contract confirmation unit 1043 of the server 10 affixes a digital signature to the acquired contract information and stores it in the document data item of the document table 1014. The contract confirmation unit 1043 of the server 10 may update (overwrite) the document data item with the contract information to which the digital signature has been affixed, or may store the contract information before the digital signature has been affixed in a separate storage device (not shown). The contract confirmation unit 1043 of the server 10 may include in the electronic signature any of the following information: document ID, email address of the first user, email address of the second user, approval date and time, confirmation date and time, authentication method of the approval date and time, authentication method of the confirmation date and time, value of input data for each input item, consent (approval) of the first user, second user, timestamp, etc. As a result, the contract confirmation unit 1043 of the server 10 attaches a digital signature indicating that the second user has approved the conclusion of the contract in the contract information to the contract information, and stores the contract information. This makes it possible to prevent a third party from impersonating or tampering with the contract information.

[0086] <Revised specific processing> The amendment identification process is a process of collecting amendment information related to amendments to laws or changes in the interpretation of laws, storing it in the amendment master 1021, and identifying and presenting contract information related to the amendment information.

[0087] <Outline of revised specific processing> The amendment identification process is a series of processes that collect amendment information regarding legal amendments or changes in the interpretation of law, store it in amendment master 1021, obtain contract information, calculate information regarding the impact of the amendment information on the contract information based on the amendment information and the contract information, store the information regarding the impact in association with the contract information, and present the information regarding the impact in association with the contract information. In addition, measures to be taken in response to the revised information may be suggested to the user in association with the contract information, and comments such as memos regarding the revised information may be accepted from the user.

[0088] <Details of the revised specific processing> The details of the amendment specific processing are explained below.

[0089] In step S501, the revision unit 1044 of the server 10 executes a revision acquisition step of acquiring revision information related to legal revisions or changes in the interpretation of laws. Specifically, the revision unit 1044 of the server 10 stores revision information including the title, revision content, rule data, and policy data in the revision master 1021 in response to legal revisions or changes in legal interpretation. Specifically, an administrator of an information processing service or the like according to the present disclosure inputs information regarding the title, revision content, rule data, and policy data via his / her own information processing terminal, and transmits the information to the server 10. The revision unit 1044 of the server 10 stores the received title, revision content, rule data, and policy data in the title, revision content, rule data, and policy data items of a new record in the revision master 1021, respectively. In addition, the revision unit 1044 of the server 10 may collect (scrape) information regarding legal revisions from websites etc. provided by the government, competent ministries and agencies, and use any natural language processing technology based on a large-scale language model (LLM), deep learning technology, machine learning technology, artificial intelligence technology, etc. to generate title, revision content, rule data, and policy data from the collected information, and store the generated data in the title, revision content, rule data, and policy data fields of a new record in the revision master 1021, respectively. That is, the amendment information stored in the amendment master 1021 may be stored by being manually input and edited by a user or the like, or may be automatically edited and stored by the amendment unit 1044 of the server 10. Note that the storage process in the amendment master 1021 does not necessarily have to be executed in the amendment specification process, and may be configured to be executed at any timing such as legal amendment, or periodically.

[0090] The amendment acquisition step executes a step of acquiring amendment information including conditions related to the contract type of the electronic data, conditions related to the clauses or provisions included in the electronic data, and conditions related to the contents of the agreement included in the electronic data. The amendment acquisition step executes a step of acquiring amendment information including conditions related to the contents of the agreement contained in the electronic data and information regarding countermeasures associated with the conditions. Specifically, the revision unit 1044 of the server 10 refers to the revision master 1021 and acquires revision information including revision contents, rule data, and policy data. At this time, the revision unit 1044 of the server 10 acquires policy data associated with each of the rule data.

[0091] In step S502, the revision unit 1044 of the server 10 acquires and identifies the contract information. Specifically, the revision unit 1044 of the server 10 refers to the document table 1014 and acquires one or more pieces of contract information. The contract information to be acquired may be all the contract information stored in the document table 1014, or, for example, only the contract information related to the revision information acquired in step S501 may be acquired. For example, when the rule data included in the amendment information acquired in step S501 includes conditions related to a predetermined contract type, the amendment unit 1044 of the server 10 may be configured to acquire only the contract information included in the contract type, etc. Similarly, when the rule data included in the amendment information includes conditions related to a predetermined contract clause, contract article, or content of an agreement, the amendment unit 1044 of the server 10 may be configured to acquire only the contract information including the predetermined contract clause, contract article, or content of an agreement.

[0092] In step S503, the revision unit 1044 of the server 10 executes a revision identification step of identifying predetermined electronic data related to the revision information acquired in the revision acquisition step from among the plurality of electronic data stored in the storage step. Specifically, the revision unit 1044 of the server 10 calculates whether the contract information acquired in step S502 may be affected by the amendment of the law or a change in the interpretation of the law, based on the amendment contents and rule data contained in the amendment information.

[0093] <Influence Calculation Process (First Embodiment)> The revision identification step executes a step of identifying one or more predetermined electronic data that are affected based on the revision information from among the plurality of electronic data. The revision identification step includes an impact calculation step of calculating an impact level based on the revision information for the plurality of electronic data, and an identification step of identifying the predetermined electronic data according to the impact level calculated in the impact calculation step. Specifically, the revision unit 1044 of the server 10 can calculate whether or not a given contract information may be affected by a legal amendment or a change in the interpretation of the law by using any natural language processing technology based on a large-scale language model (LLM), deep learning technology, machine learning technology, artificial intelligence technology, etc. For example, the impact on a combination of contract information and amendment information can be calculated based on document data, amendment contents, and rule data included in the contract information. In addition, this allows one or more pieces of contract information that may be affected by a legal amendment or a change in the interpretation of the law to be acquired and identified from the multiple pieces of contract information acquired in step S502. In addition, an index (score) of the degree of impact, etc., may be calculated for each contract information according to the degree of impact due to legal amendments or changes in the interpretation of the law. Such an impact can be calculated by inputting document data, amendment contents, and rule data into a large-scale language model. Specifically, based on the amendment contents and rule data, the impact is calculated according to the degree of relevance of the document data to the contract type, contract clauses, articles, and other specific agreement contents. The revision unit 1044 of the server 10 acquires and identifies contract information whose impact level is equal to or greater than a predetermined value as one or more pieces of contract information that may be affected by legal revisions or changes in the interpretation of the law.

[0094] <Influence Calculation Process (Second Embodiment)> The revision identification step includes a step of determining whether each of the plurality of electronic data satisfies a condition included in the revision information, and a step of identifying predetermined electronic data that satisfies the condition. Specifically, the revision unit 1044 of the server 10 may acquire and identify one or more pieces of contract information that may be affected by legal amendments or changes in the interpretation of law, based on whether the document data included in the contract information matches the conditions included in the rule data. For example, in a case where the rule information includes conditions related to a predetermined contract type, the revising unit 1044 of the server 10 may be configured to acquire and specify only the contract information included in the contract type, etc. Similarly, in a case where the rule data included in the revision information includes conditions related to the contents of a predetermined contract clause, contract article, or agreement, the revising unit 1044 of the server 10 may be configured to acquire and specify only the contract information including the contents of the predetermined contract clause, contract article, or agreement. It should be noted that if only the contract information that satisfies the conditions included in the rule data has already been acquired in step S502, this step may be omitted.

[0095] In step S503, the revision identification step includes a notification step of notifying the predetermined electronic data identified in the identification step according to the degree of impact calculated in the impact calculation step. Specifically, the revision unit 1044 of the server 10 may acquire one or more pieces of contract information that may be affected according to the amendment of the law or the change in the interpretation of the law in step S503, and when it identifies the contract information, may notify the user of the contract information. For example, the configuration may be such that notification is given to any user involved in the procedure such as the creator or verifier of the contract information, a manager or other user with authority such as an administrator in the organization to which the contracting party of the contract information belongs, or any other user. For example, the revision unit 1044 of the server 10 notifies the user via email, chat service, etc., of text or summaries that associate the document data contained in the contract information, the title, revision content, rule data, and policy data contained in the revision information.

[0096] In step S504, the revision unit 1044 of the server 10 stores information on the impact of the revision information on the contract information based on the revision information and contract information calculated in step S503 in the revision flag item of the record of the contract information in the document table 1014. Note that the revision flag item may include basic information for calculating the impact in accordance with legal revisions or changes in the interpretation of the law, such as the revision ID, title, revision content, and rule data of the revision information. In addition, the revision unit 1044 of the server 10 stores the policy data stored in association with the rule data in the revision master 1021 in the policy data item of the document table 1014. This makes it possible to store, in association with each of one or more pieces of contract information that may be affected by legal amendments or changes in the interpretation of the law, the related amendment information (amendment content) and policy information regarding the amendment content. This makes it possible to quickly identify contracts that need to be reviewed in response to legal changes, etc., and also to identify response measures that should be taken, such as amending contracts, re-contracting, and retroactive contracts.

[0097] In step S505, the revision unit 1044 of the server 10 executes a presentation step of presenting the predetermined electronic data identified in the revision identification step.

[0098] The first user operates the input device 206 of the first user terminal 20 to input the URL of a page for executing the revision presentation processing (revised presentation processing page) into a web browser or the like, and opens the revision presentation processing page. The control unit 204 of the first user terminal 20 sends a request to the server 10 to open the revision presentation processing page. The control unit 104 of the server 10 generates a revision presentation processing page based on the received request, and sends it to the first user terminal 20. The control unit 204 of the first user terminal 20 displays the received revision presentation processing page on the display 2081 of the first user terminal 20. The revision presentation process may be configured to be executable by any user, such as a manager or administrator in the organization or group to which the first user belongs, in addition to the second user.

[0099] 19 is an example of an amendment presentation screen in the amendment presentation process. An amendment presentation page D1 is displayed on the display 2081 of the first user terminal 20. The amendment presentation page D1 includes contract information D11, D12, D13.... The contract information D11, D12, D13... includes counterparty information D111, D121, D131... that identifies the contract counterparty identified based on the creator or confirmer, impact degree 112, D122, D132..., amendment contents D113, D123, D133..., rule data D114, D124, D134..., and policy data D115, D125, D135....

[0100] The presentation step includes a step of presenting predetermined electronic data in association with a countermeasure associated with the electronic data. Specifically, each of the contract information D11, D12, D13, etc. is presented in association with the policy data D115, D125, D135, etc. This makes it possible to quickly identify contracts that need to be checked in response to legal changes, etc., and also to identify the measures that should be taken, such as changing the contract (amended contract), re-contracting, and retroactive contracting.

[0101] Users who receive contract information through the amendment specification processing according to the present disclosure will take contract procedures such as amended contracts, re-contracts, retroactive contracts, and contract termination with the other party, referring to the contents of the response measures, etc. This will save a huge amount of work time that was previously required to inventory, organize, and consider the degree of impact of all past contract documents concluded by the company in response to legal amendments or changes in legal interpretation. Users of the information processing service according to the present disclosure can quickly identify affected contracts in response to amendment information and take appropriate legal action.

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

[0103] The processor 901 is hardware for executing an instruction set described in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0104] The main memory device 902 is for temporarily storing programs, data to be processed by the programs, etc. For example, it is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0105] The auxiliary storage device 903 is a storage device for saving data and programs, such as a flash memory, a hard disk drive (HDD), a magneto-optical disk, a CD-ROM, a DVD-ROM, or a semiconductor memory.

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

[0107] It should be noted that the computer 90 can be virtually realized by distributing all or part of each hardware configuration among multiple computers 90 and connecting them together via a network. In this way, the computer 90 is a concept that includes not only a computer 90 housed in a single housing or case, but also a virtualized computer system.

[0108] <Basic functional configuration of computer 90> A description will now be given of the functional configuration of a computer realized by the basic hardware configuration (FIG. 20) of a computer 90. The computer comprises at least the functional units of a control unit, a storage unit, and a communication unit.

[0109] The functional units of the computer 90 can also be realized by distributing all or part of the functional units among multiple computers 90 connected to each other via a network. The computer 90 is a concept that includes not only a single computer 90 but also a virtualized computer system.

[0110] The control unit is realized by the processor 901 reading out various programs stored in the auxiliary storage device 903, expanding the programs in the main storage device 902, and executing processes according to the programs. The control unit can realize functional units that perform various information processing depending on the type of program. In this way, the computer is realized as an information processing device that performs information processing.

[0111] The storage unit is realized by a main storage device 902 and an auxiliary storage device 903. The storage unit stores data, various programs, and various databases. Furthermore, the processor 901 can secure a storage area corresponding to the storage unit in the main storage device 902 or the auxiliary storage device 903 in accordance with a program. Furthermore, the control unit can cause the processor 901 to execute processes of adding, updating, and deleting data stored in the storage unit in accordance with the various programs.

[0112] The term database refers to a relational database, which is used to manage sets of data called masters and tables in a tabular format structurally defined by rows and columns, by associating them with each other. In a database, a table is called a table or master, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables and masters can be set and associated. Usually, a column that serves as a primary key for uniquely identifying a record is set in each table and each master, but setting a primary key in a column is not essential. The control unit can cause the processor 901 to add, delete, or update records in a specific table or master stored in the storage unit according to various programs. Furthermore, by storing data, various programs, and various databases in the storage unit, it can be considered that the information processing device and information processing system according to the present disclosure have been manufactured.

[0113] In addition, the database and master in this disclosure may include any data structure (such as a list, a dictionary, an associative array, or an object) in which information is structurally defined. The data structure also includes data that can be considered as a data structure by combining data with a function, class, method, or the like written in any programming language.

[0114] The communication unit is realized by the communication IF 991. The communication unit realizes a function of communicating with other computers 90 via a network. The communication unit can receive information transmitted from other computers 90 and input the information to the control unit. The control unit can cause the processor 901 to execute information processing on the received information in accordance with various programs. In addition, the communication unit can transmit information output from the control unit to other computers 90.

[0115] <Additional Notes> The matters described in the above embodiments will be supplemented below.

[0116] (Appendix 1) A program having a processor and a memory unit, for managing electronic data agreed upon between multiple users on a computer, wherein the processor executes a storage step (S101) for storing multiple electronic data agreed upon between multiple users, an amendment acquisition step (S501) for acquiring amendment information relating to legal amendments or changes in the interpretation of law, and an amendment identification step (S503) for identifying, from the multiple electronic data stored in the storage step, specific electronic data related to the amendment information acquired in the amendment acquisition step. This makes it possible to identify contracts (electronic data) related to legal amendments or changes in legal interpretation. Contracts that need to be reviewed in response to legal amendments, etc. can be quickly identified.

[0117] (Appendix 2) The program according to claim 1, wherein the revision identification step (S503) is a step of identifying one or more predetermined electronic data items that are affected based on the revision information, among the plurality of electronic data items. This makes it possible to identify one or more contracts (electronic data) that are affected based on legal amendments or changes in legal interpretation. It is possible to identify contracts that are affected according to amendment information.

[0118] (Appendix 3) The program described in Appendix 2, wherein the revision identification step (S503) includes an impact calculation step of calculating the impact level for multiple electronic data based on revision information, and an identification step of identifying specific electronic data based on the impact level calculated in the impact calculation step. This allows contracts to be identified according to the degree of impact calculated based on legal amendments or changes in legal interpretation, and allows contracts with no or little impact to be excluded, allowing contracts with a large or large impact to be identified.

[0119] (Appendix 4) The program according to appendix 3, wherein the revision identification step (S503) includes a notification step of notifying the specified electronic data identified in the identification step according to the degree of impact calculated in the impact calculation step. This allows the user to be notified of contracts that have an impact or are significant based on changes in the law or changes in the interpretation of the law, and allows the user to take prompt action based on changes in the law or changes in the interpretation of the law.

[0120] (Appendix 5) A program described in Appendix 1, wherein the amendment acquisition step (S501) is a step of acquiring amendment information including conditions related to electronic data, and the amendment identification step (S503) includes a step of determining whether each of the multiple electronic data satisfies the conditions included in the amendment information, and a step of identifying specific electronic data that satisfies the conditions. This allows the contract to be identified according to the conditions included in the amendment information. Specifically, the contract is identified according to the contents of the contract and the conditions included in the amendment information.

[0121] (Appendix 6) The program according to appendix 5, wherein the amendment acquisition step (S501) is a step of acquiring amendment information including conditions related to clauses or provisions contained in electronic data. This allows users to identify contracts that contain clauses or provisions that are affected by the amendment information from among the multiple contracts they manage. This makes it possible to quickly identify contracts that need to be checked in response to legal amendments, etc.

[0122] (Appendix 7) The program according to appendix 5, wherein the amendment acquisition step (S501) is a step of acquiring amendment information including conditions related to the contract type of electronic data. This allows users to identify contracts that are affected by the amendment information from among the multiple contracts they manage, and quickly identify contracts that need to be checked in response to legal amendments, etc.

[0123] (Appendix 8) The program described in Appendix 5, wherein the amendment acquisition step (S501) is a step of acquiring amendment information including conditions regarding the contents of the agreement contained in the electronic data and information regarding response measures associated with the conditions. This makes it possible to quickly identify contracts that need to be reviewed in response to legal changes, etc., and also to identify response measures that should be taken, such as amending contracts, re-contracting, and retroactive contracts.

[0124] (Appendix 9) A program as described in Appendix 1, in which a processor executes a presentation step (S505) of presenting the specified electronic data identified in the amendment identification step, the presentation step (S505) being a step of presenting the specified electronic data in association with the response measures associated with the electronic data. This makes it possible to quickly identify contracts that need to be reviewed in response to legal changes, etc., and also to confirm the response measures that should be taken, such as amending contracts, re-contracting, and retroactive contracts.

[0125] (Appendix 10) A method implemented on a computer having a processor and a memory, the processor performing all of the steps performed in an invention according to any one of appendices 1 to 9. This makes it possible to identify contracts (electronic data) related to legal amendments or changes in legal interpretation. Contracts that need to be reviewed in response to legal amendments, etc. can be quickly identified.

[0126] (Appendix 11) An information processing device comprising a control unit and a memory unit, wherein the control unit executes all of the steps executed in the invention according to any one of Supplementary Note 1 to Supplementary Note 9. This makes it possible to identify contracts (electronic data) related to legal amendments or changes in legal interpretation. Contracts that need to be reviewed in response to legal amendments, etc. can be quickly identified.

[0127] (Appendix 12) A system comprising means for performing all the steps performed in any one of the inventions according to appendix 1 to appendix 9. This makes it possible to identify contracts (electronic data) related to legal amendments or changes in legal interpretation. Contracts that need to be reviewed in response to legal amendments, etc. can be quickly identified. [Explanation of symbols]

[0128] 1 System, 10 Server, 101 Memory unit, 104 Control unit, 106 Input device, 108 Output device, 20 First user terminal, 201 Memory unit, 204 Control unit, 206 Input device, 208 Output device, 30 Second user terminal, 301 Memory unit, 304 Control unit, 306 Input device, 308 Output device

Claims

1. A program for managing electronic data agreed upon among a plurality of users in a computer, the program comprising: a processor; and a storage unit; the processor: a storage step of storing a plurality of electronic data items agreed upon among a plurality of users; an amendment acquisition step of acquiring amendment information regarding amendments to laws or changes in the interpretation of laws; an amendment specifying step of specifying predetermined electronic data related to the amendment information acquired in the amendment acquiring step from the plurality of electronic data stored in the storing step; A program that executes.

2. The revision identification step is a step of identifying one or more of the predetermined electronic data that are affected based on the revision information among the plurality of electronic data. The program according to claim 1.

3. The amendment identification step is a step of identifying predetermined electronic data related to the amendment information based on information output by inputting the electronic data and the amendment information into a large-scale language model. The program according to claim 1.

4. The amendment specifying step includes: an impact calculation step of calculating an impact level based on the revision information on the plurality of electronic data; an identifying step of identifying the predetermined electronic data in accordance with the degree of impact calculated in the impact calculation step; Including, The program according to claim 2.

5. The impact calculation step is a step of calculating the impact by inputting the electronic data and the revision information into a large-scale language model. The program according to claim 4.

6. The amendment specifying step includes: a notification step of notifying the predetermined electronic data identified in the identification step in accordance with the degree of impact calculated in the impact calculation step; Including, The program according to claim 4.

7. The notification step is a step of notifying the user of information related to the specified electronic data identified in the identification step via email or a chat service. The program according to claim 6.

8. the amendment acquisition step is a step of acquiring the amendment information including conditions related to electronic data, The amendment specifying step includes: determining whether each of the plurality of electronic data satisfies the condition included in the revision information; identifying the predetermined electronic data that satisfies the condition; Including, The program according to claim 1.

9. the amendment acquisition step is a step of acquiring the amendment information including the conditions related to the clauses or provisions included in the electronic data; The program according to claim 8.

10. the amendment acquisition step is a step of acquiring the amendment information including the conditions related to the contract type of the electronic data; The program according to claim 8.

11. The amendment acquisition step is a step of acquiring the amendment information including the conditions related to the content of the agreement included in the electronic data and information related to the response measures associated with the conditions. The program according to claim 8.

12. The amendment acquisition step is a step of collecting information on legal amendments by scraping from a website provided by the government or a competent ministry, and acquiring the amendment information generated by applying natural language processing technology including a large-scale language model to the collected information. The program according to claim 1.

13. the processor: a presentation step of presenting the predetermined electronic data identified in the revision identification step; Run the presenting step is a step of presenting the predetermined electronic data in association with the countermeasure associated with the electronic data. The program according to claim 11.

14. A method implemented on a computer having a processor and a memory, wherein the processor performs all of the steps performed in the invention according to any one of claims 1 to 13.

15. 14. An information processing device comprising a control unit and a storage unit, wherein the control unit executes all of the steps executed in the invention according to any one of claims 1 to 13.

16. A system comprising means for executing all steps performed in an invention according to any one of claims 1 to 13.

Images