Contract processing device, contract processing method, and program

Abstract

To address the conventional difficulty of appropriately managing or using a contract.SOLUTION: A contract processing document device 1 comprises: a clue phrase storage unit 111 that stores one or more clue phrases providing clues for acquiring a contract attribute value which is an attribute value of a contract; a contract reception unit 121 that receives contract information; an attribute value acquisition unit 131 that acquires a contract document from the contract information, and acquires two or more contract attribute values relating to contract type information, contract opposite information, contract conclusion date information, contract efficacy start date information, contract efficacy end date information, contract automatic update information, contract cancellation notification period information, and contract fee information from the contract document using the one or more clue phrases; and an accumulation assistance unit 132 that performs an accumulation assistance process for accumulating the two or more contract attribute values. Thus, appropriate management or use of the contract can be facilitated.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a contract processing device that processes contract information. [Background technology]

[0002] Conventionally, there have been contract management systems for supporting the creation of contracts (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-185096 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the prior art, it was not easy to properly manage or use contracts. [Means for solving the problem]

[0005] The contract processing device of the first invention is a contract processing device that includes a clue phrase storage unit that stores one or more clue phrases that serve as clues for obtaining contract attribute values, which are attribute values ​​of a contract; a contract reception unit that receives contract information; an attribute value acquisition unit that acquires contract text from the contract information and uses one or more clue phrases to acquire from the contract text two or more contract attribute values ​​from the contract text: contract type information, contract counterparty information, contract conclusion date information, contract effectiveness start date information, contract effectiveness end date information, contract automatic renewal information, contract cancellation notice deadline information, and contract amount information; and an accumulation support unit that performs accumulation support processing to accumulate two or more contract attribute values.

[0006] This configuration facilitates proper management of contracts.

[0007] Furthermore, in the contract processing device of the second invention, in comparison with the first invention, the storage support unit stores two or more contract attribute values ​​in association with contract information.

[0008] This configuration facilitates proper management of contracts.

[0009] In addition, the contract processing device of the third invention is a contract processing device that, compared to the second invention, further comprises a contract information storage unit in which one or more contract information having contract information associated with two or more contract attribute values ​​obtained from the contract information is stored, a search information receiving unit that receives search information using one or more contract attribute values, a search unit that determines contract information that matches the search information, and a contract information output unit that outputs the contract information contained in the contract information determined by the search unit.

[0010] This configuration facilitates proper management of contracts.

[0011] In addition, the contract processing device of the fourth invention is a contract processing device that further comprises a post-processing unit that performs post-processing using one or more contract attribute values ​​out of two or more contract attribute values ​​for any one of the first to third inventions.

[0012] This configuration facilitates the proper use of the contract.

[0013] Furthermore, in the contract processing device of the fifth invention, compared to the fourth invention, the post-processing unit is a contract processing device equipped with a notification means for issuing a notification regarding contract renewal or contract termination when it is determined that the date indicated by the end date information or the date indicated by the cancellation notice deadline information is approaching so quickly that it satisfies predetermined conditions.

[0014] With this configuration, contract renewal can be notified.

[0015] In addition, the contract processing device of the sixth invention is a contract processing device that, compared to any one of the first to fifth inventions, further comprises a classification unit that analyzes one or more inspection units of the contract text and obtains a class indicating whether the contract is disadvantageous or not, a related information acquisition unit that uses the class obtained by the classification unit to obtain related information regarding the class, and a related information output unit that outputs the related information.

[0016] This configuration makes it possible to classify the contract contents.

[0017] Furthermore, the contract processing device of the seventh invention differs from the sixth invention in that the classification unit acquires a class for each of one or more inspection units of the contract text of one piece of contract information, the related information acquisition unit is equipped with a single score acquisition means that acquires a single score, which is the score of one piece of contract information, using the one or more classes acquired by the classification unit, and the related information output unit is a contract processing device that outputs the single score.

[0018] This configuration makes it possible to score the contract contents.

[0019] Furthermore, the contract processing device of the eighth invention is a contract processing device in which, compared to the seventh invention, the related information acquisition unit includes a recommendation acquisition means for acquiring recommendation information based on an inspection unit corresponding to a class when the class satisfies predetermined conditions, and the related information output unit outputs the recommendation information.

[0020] With this configuration, it is possible to present information that will result in an appropriate contract.

[0021] Furthermore, the contract processing device of the ninth invention differs from the sixth invention in that the classification unit acquires a class for each of one or more inspection units of the contract text of each of two or more pieces of contract information, the related information acquisition unit is equipped with a comprehensive score acquisition means that uses the two or more classes acquired by the classification unit to acquire a comprehensive score, which is the score of the two or more pieces of contract information, and the related information output unit is a contract processing device that outputs the comprehensive score.

[0022] This configuration makes it possible to score the contract contents.

[0023] Furthermore, the contract processing device of the tenth invention, compared to the eighth or ninth invention, further comprises a score storage unit in which individual scores or overall scores for contract information at a first point in time are stored, the related information acquisition unit further comprises a contribution information acquisition means for acquiring contribution information regarding the difference between the individual scores or overall scores acquired from contract information at a second point in time after the first point in time and the individual scores or overall scores in the score storage unit, and the related information output unit is a contract processing device that outputs the contribution information.

[0024] With this configuration, the degree of contribution can be presented using the change in the score for the contract. [Effects of the Invention]

[0025] The contract processing device according to the present invention facilitates the appropriate management and use of contracts. [Brief explanation of the drawings]

[0026] [Figure 1] FIG. 1 is a conceptual diagram of an information system A according to a first embodiment. [Figure 2] Block diagram of Information System A [Figure 3] Block diagram of the contract processing device 1 [Figure 4] A flowchart illustrating an example of the operation of the contract processing device 1 [Figure 5] Flowchart illustrating an example of attribute value acquisition processing [Figure 6] Flowchart illustrating an example of same-type acquisition processing [Figure 7] Flowchart illustrating an example of the partner acquisition process [Figure 8] A flowchart illustrating an example of the execution date acquisition process [Figure 9] Flowchart explaining an example of the process for obtaining start and end dates [Figure 10]A flowchart illustrating an example of the automatic update acquisition process. [Figure 11] A flowchart illustrating an example of the cancellation notice deadline acquisition process. [Figure 12] A flowchart illustrating an example of the transaction amount acquisition process [Figure 13] A flowchart illustrating an example of the related information acquisition process [Figure 14] Flowchart illustrating an example of class acquisition processing [Figure 15] A flowchart illustrating an example of the examination unit class determination process [Figure 16] A flowchart illustrating an example of the notification process [Figure 17] A flowchart illustrating an example of the update process [Figure 18] A flowchart illustrating an example of the overall score acquisition process [Figure 19] A flowchart illustrating an example of the contribution information acquisition process [Figure 20] A diagram showing the contract information management table [Figure 21] Figure showing the overall score management table [Figure 22] Overview of the computer system [Figure 23] Block diagram of the computer system DETAILED DESCRIPTION OF THE INVENTION

[0027] Hereinafter, embodiments of a contract processing device and the like will be described with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore repeated description may be omitted.

[0028] (Embodiment 1) In this embodiment, an information system will be described that includes a contract processing device that receives contract information, acquires two or more predetermined contract attribute values ​​from the contract information, and outputs the values.

[0029] In this embodiment, an information system including a contract processing device that stores two or more contract attribute values ​​in association with contract information will be described.

[0030] In this embodiment, an information system equipped with a contract processing device that can search for contract information using contract attribute values ​​will be described.

[0031] In this embodiment, an information system including a contract processing device that performs post-processing using one or more contract attribute values ​​will be described. The post-processing is, for example, a process of notifying a contract renewal using expiration information.

[0032] In addition, in this embodiment, an information system will be described that is equipped with a contract processing device that inspects the inspection unit of a contract, determines a class such as whether it is disadvantageous or not, and outputs the class.

[0033] In addition, in this embodiment, an information system including a contract processing device that acquires a score for a contract using the class determination result will be described.

[0034] In this embodiment, an information system including a contract processing device that uses the class classification results to make recommendations for the next contract will be described.

[0035] Furthermore, in this embodiment, an information system equipped with a contract processing device that uses time-series scores to obtain and output the degree of contribution to legal work and business contribution will be described.

[0036] FIG. 1 is a conceptual diagram of an information system A in this embodiment. The information system A comprises a contract processing device 1 and one or more terminal devices 2. The contract processing device 1 is what is called a server device here. The contract processing device 1 is, for example, a cloud server or an ASP server, but the type and location of the device do not matter. The terminal device 2 is a mobile terminal such as a smartphone, tablet device, or mobile phone, or a so-called personal computer, and the type does not matter.

[0037] Fig. 2 is a block diagram of the information system A in this embodiment, and Fig. 3 is a block diagram of the contract processing device 1.

[0038] The contract processing device 1 includes a storage unit 11, a receiving unit 12, a processing unit 13, and a transmitting unit 14.

[0039] The storage unit 11 includes a cue phrase storage unit 111 , a learning information storage unit 112 , a contract information storage unit 113 , and a score storage unit 114 .

[0040] The receiving unit 12 includes a contract receiving unit 121 and a search information receiving unit 122 .

[0041] The processing unit 13 includes an attribute value acquisition unit 131 , a storage support unit 132 , a search unit 133 , a post-processing unit 134 , a classification unit 135 , and a related information acquisition unit 136 .

[0042] The post-processing unit 134 includes a notification unit 1341 , an update unit 1342 , and an indication unit 1343 .

[0043] The related information acquisition unit 136 includes a single score acquisition unit 1361 , a total score acquisition unit 1362 , a contribution information acquisition unit 1363 , and a recommendation acquisition unit 1364 .

[0044] The transmission unit 14 includes a related information output unit 141 and a contract information output unit 142 .

[0045] The terminal device 2 includes a terminal storage unit 21, a terminal reception unit 22, a terminal processing unit 23, a terminal transmission unit 24, a terminal reception unit 25, and a terminal output unit 26.

[0046] Various types of information are stored in the storage unit 11 that constitutes the contract processing device 1. The various types of information include, for example, cue phrases (described later), learning information (described later), contract information (described later), and scores (described later).

[0047] The cue phrase storage unit 111 stores one or more cue phrases. A cue phrase is one or more terms that serve as a clue for acquiring a contract attribute value from a contract document, which will be described later. A cue phrase may be one term, two or more terms, a sentence pattern, or the like. A cue phrase may also be called cue information.

[0048] The contract attribute value is an attribute value of the contract. Examples of the contract attribute value include type information, name information, date information, automatic renewal information, and amount information. The type information is information indicating the type of contract. Examples of the type information include "content certification," "debt waiver," "payment agreement," "payment of indemnity," "assignment agreement," "confidentiality obligation," "basic transaction agreement," "personal information protection agreement," and "service outsourcing agreement." The name information is information about the names of the parties to the contract. The name information includes, for example, counterparty information and self information. The counterparty information is the name of the other party to the contract, such as an organization name such as a company name or organization name, or a person's name. The self information is the name of the party to the contract (the person using the contract processing device 1), such as an organization name or a person's name. The date information is information that identifies a specific date, such as conclusion date information that identifies the conclusion date of the contract, start date information that identifies the start date of the contract, end date information that identifies the end date of the contract, and cancellation notice deadline information that identifies the cancellation notice deadline for the contract. The cancellation notice deadline information is preferably date information, but may also be information specifying the period before the date indicated by the end date information (for example, N months or N days in advance). Automatic renewal information is information specifying whether automatic renewal will occur. Amount information is information specifying the amount related to the contract. Amount information is usually information specifying the transaction amount.

[0049] Further, clue phrases include, for example, type information, party terms which are terms for identifying the parties to the contract, period patterns for obtaining period information, period terms for obtaining period information, effect terms regarding the onset of contract effectiveness, termination terms regarding the end of contract effectiveness, automatic renewal patterns which are character string patterns for determining whether the contract is automatically renewed, deadline prediction terms which are terms for detecting the existence of a contract expiration date, deadline terms which are terms for obtaining the deadline, transaction amount terms which are terms for obtaining the transaction amount, and class determination patterns for determining the class of the inspection unit described below.

[0050] Examples of party terms are "Party A," "Party B," and "Party C." Examples of period patterns are "Y year M month D day to y year M month D day," "Y year M month D day to y year M month D day," and "(Note that Y, M, D, y, m, and d are numbers). Examples of period terms are "period." Examples of effect terms are "effective," "become effective," and "effect." Examples of termination terms are "end upon" and "end." Examples of automatic renewal patterns are "the same shall apply thereafter," "follow this example," "automatically ~ renewed," and "automatically ~ extended" (Note that ~ is an arbitrary character string). Examples of deadline expectation terms are "the same shall apply thereafter" and "the same thereafter." Examples of due date terms are "X months in advance," "X months in advance," and "X days in advance" (Note that X is a number). Examples of transaction amount terms are "price" and "consideration."

[0051] Class determination patterns are, for example, "If Party A or Party B violates the provisions of this Agreement by disclosing the other party's confidential information," corresponding to class "neutral," "If Party A violates the provisions of this Agreement by disclosing the other party's confidential information," corresponding to class "adverse" against party "Party A," "If Party B violates the provisions of this Agreement by disclosing the other party's confidential information," corresponding to class "favorable" against party "Party A," "If Party B violates the provisions of this Agreement by disclosing the other party's confidential information," corresponding to class "adverse" against party "Party A" "If Party A violates the provisions of this Agreement by disclosing the other party's confidential information, Party A will compensate Party A if it violates the provisions of this Agreement by disclosing the other party's confidential information, but this does not apply to Party B."

[0052] The learning information storage unit 112 stores one or more pieces of learning information. The learning information is, for example, information used to acquire a class of the contract content. Note that classes will be described later. The learning information may also be a learning device, which will be described later. The learning device is, for example, information used when acquiring a class using a machine learning algorithm. A learning device for acquiring a class is called a class learning device. Note that a learning device may also be called a learning model, a classifier, or a classification model.

[0053] The learning information may be information used to determine whether a term is an organization name. The learning information may also be information used to determine whether a term is a person's name. The learning information may also be information used to determine whether a term is an organization name or a person's name. In such cases, the learning information is a learner that determines whether a received term is an organization name or a person's name, and is referred to as a name learner. The name learner is, for example, data configured by the processing unit 13, which will be described later, through machine learning learning processing.

[0054] The contract information storage unit 113 stores one or more pieces of contract information. The contract information has two or more contract attribute values. It is preferable that the two or more contract attribute values ​​correspond to the contract information. The contract information has, for example, two or more contract attribute values ​​associated with the contract information. It is preferable that the contract information corresponds to an organization identifier that identifies the organization to which the user who transmitted the contract information belongs. The organization identifier is usually information that identifies the subject of the contract. The organization identifier is, for example, a company name, a company ID, a department name, a department ID, a workplace name, a workplace ID, or a person's name. It is also preferable that the two or more contract attribute values ​​are information acquired by the attribute value acquisition unit 131, which will be described later.

[0055] The score storage unit 114 stores one or more scores. The score is information that indicates the degree of disadvantage or advantage of a contract. The score is, for example, an individual score or an overall score. The individual score is the score of one piece of contract information. The overall score is usually the overall score of two or more pieces of contract information. The overall score is, for example, the overall score of one or more pieces of contract information of an organization. The overall score is, for example, the overall score of one or more pieces of contract information of an organization for a specific period. It is preferable that the score is information acquired by the related information acquisition unit 136, which will be described later.

[0056] The score storage unit 114 stores scores of 1 or more in association with time information that specifies a time. The time information may be information that specifies a single point in time (June 30, 2020) or information that specifies a certain period of time (for example, fiscal year 2020, the first half of 2019, etc.). A certain period of time may also be referred to as a point in time.

[0057] The receiving unit 12 receives various types of information and instructions. The receiving unit 12 normally receives various types of information and instructions from the terminal device 2. The various types of information and instructions are, for example, contract information and search information.

[0058] The contract receiving unit 121 receives contract information. The contract information is information about a contract. For example, the contract information is a PDF, a text file, or an image (JPEG, GIF, etc.). The contract information is usually a file. However, the data structure and data type of the contract information are not important.

[0059] It is preferable that the contract receiving unit 121 receives contract information associated with an organization identifier. The organization identifier here is the identifier of the organization to which the user who inputs the contract information belongs.

[0060] Here, acceptance usually means receiving from the terminal device 2, but it may also be a concept that includes acceptance of information input from an input device such as a keyboard, mouse, or touch panel, or acceptance of information read from a recording medium such as an optical disk, magnetic disk, or semiconductor memory.

[0061] The search information receiving unit 122 receives search information using one or more contract attribute values ​​from the terminal device 2. The search information may be called a query. The structure of the search information is not important. The search information may be, for example, a query for searching contract information or a query for searching a character string in the contract information.

[0062] The processing unit 13 performs various types of processing, such as processing performed by an attribute value acquisition unit 131, a storage support unit 132, a search unit 133, a post-processing unit 134, a classification unit 135, and a related information acquisition unit 136.

[0063] The processing unit 13 acquires, for example, two or more sets of training data, each set consisting of a sentence constituting a contract and a class of the sentence, from the storage unit 11, and performs a learning process on the two or more sets of training data using a machine learning algorithm to configure a class learning device that performs multi-value classification. In this machine learning, algorithms such as deep learning, decision trees, and random forests can be used. Furthermore, multiple regression analysis, neural networks, and the like can also be used in the machine learning. In other words, any machine learning algorithm can be used. Furthermore, any machine learning module can be used, for example, fasttext, TensorFlow functions, MicrosoftML functions, and the like.

[0064] The processing unit 13 acquires, for example, two or more pieces of training data for each class, each of which has one or more positive examples that are sentences belonging to the class and one or more negative examples that are sentences that do not belong to the class, from the storage unit 11, and performs a learning process on the two or more pieces of training data using a machine learning algorithm to configure a class learner that performs binary classification. In this machine learning, algorithms such as deep learning, decision trees, random forests, and SVMs can be used. Furthermore, multiple regression analysis, neural networks, and the like can also be used in the machine learning. In other words, any machine learning algorithm can be used. Furthermore, any machine learning module can be used, for example, fasttext, Tiny_svm, TensorFlow functions, MicrosoftML functions, and the like.

[0065] The processing unit 13 performs a learning process using a machine learning algorithm on training data having one or more positive examples, each of which is, for example, one or more organization names or one or more personal names, and one or more negative examples that are neither organization names nor personal names, to configure a name learner. In machine learning, algorithms such as deep learning, decision trees, random forests, SVR, and SVM can be used. Furthermore, multiple regression analysis, neural networks, and the like can also be used in machine learning. In other words, any machine learning algorithm can be used. Furthermore, any machine learning module can be used, for example, Tiny_SVM, TensorFlow functions, MicrosoftML functions, and the like.

[0066] The attribute value acquisition unit 131 acquires two or more contract attribute values ​​from the accepted contract information. Specifically, the attribute value acquisition unit 131 acquires a contract sentence, which is a sentence consisting of a set of character strings, from the contract information. Next, the attribute value acquisition unit 131 acquires one or more contract attribute values ​​from the acquired contract sentence using one or more cue phrases in the cue phrase storage unit 111. An example of a method for acquiring each contract attribute value will be described below. (1) How to obtain contract type information

[0067] The attribute value acquisition unit 131 acquires, from the contract text, a character string that matches a character string indicated by one or more pieces of type information stored in the cue phrase storage unit 111, or a character string that is so close as to satisfy a predetermined condition. The predetermined condition is, for example, "match," "type information with the highest similarity equal to or greater than a threshold," or "type information with the highest similarity equal to or greater than a threshold."

[0068] The attribute value acquisition unit 131 acquires, for example, from a predetermined first range of character strings in the contract text, a character string that matches a character string indicated by one or more pieces of type information stored in the cue phrase storage unit 111, or a character string that is so similar as to satisfy a predetermined condition. Note that the first range is, for example, the first line containing the character string in the contract text, or within a predetermined amount from the beginning of the contract text (for example, within a predetermined number of lines, within a predetermined amount of data, or within a predetermined percentage from the beginning of the contract text). A character string that is so similar as to satisfy a predetermined condition has the highest similarity.

[0069] The similarity between two character strings is, for example, the Levenshtein distance, and the process of obtaining this is a well-known technique. (2) How to obtain information about the contracting party

[0070] The attribute value acquisition unit 131, for example, searches the contract document for characters that match any of the characters in the party terms "A," "B," or "C" stored in the clue phrase storage unit 111, and acquires counterparty information that is a noun phrase within a predetermined distance from the characters in question.

[0071] The attribute value acquisition unit 131 searches for, for example, the characters "A," "B," and "C" that appear at the beginning of the contract text, and acquires from the characters "A," "B," and "C" the names of organizations or people that are close enough to satisfy a predetermined condition. The attribute value acquisition unit 131 determines, for example, a noun phrase consisting of a character string and a "joint stock company" such as "joint stock company" or "limited company" to be an organization name. The attribute value acquisition unit 131 excludes the name of the person associated with the contract information from the two or more acquired organization names or person names, and acquires the remaining one or more organization names or person names as the other party information. The name of the person is referred to as person identification information, as appropriate.

[0072] The attribute value acquisition unit 131, for example, performs morphological analysis on a character string in a predetermined second range of the contract text to acquire one or more noun phrases. Next, the attribute value acquisition unit 131 performs a prediction process using a machine learning algorithm with the name learner in the storage unit 11 to acquire whether each of the acquired one or more noun phrases is an organization name or a person's name. Next, the attribute value acquisition unit 131 acquires a noun phrase that has been determined to be an organization name or a person's name and whose distance to any character that matches a character in the party term stored in the cue phrase storage unit 111 is close enough to satisfy a predetermined condition, and acquires one or more names, excluding the person identification information, from the noun phrase as other party information.

[0073] As with the learning process, the algorithms for machine learning learning and prediction processes can be any of deep learning, random forest, decision tree, SVM, etc. The machine learning learning process module can be, for example, Tiny_SVM, TensorFlow functions, MicrosoftML functions, etc.

[0074] The second range is, for example, within a predetermined amount from the beginning of the contract document (for example, within a predetermined number of lines, within a predetermined amount of data, or within a predetermined percentage from the beginning of the contract document). The second range is, for example, within a predetermined amount from the end of the contract document (for example, within a predetermined number of lines from the last line, within a predetermined amount of data from the end, or within a predetermined percentage from the end of the contract document). (3) Method of obtaining contract conclusion date information

[0075] The attribute value acquisition unit 131 detects, for example, one or more character strings in the format of date information (for example, "year / month / day," " / / / / ," "Reiwa year / month / day," etc.) from the contract document. Next, the attribute value acquisition unit 131 determines, for example, whether or not one or more characters (for example, "desu") exist before and after the date information, and if not, acquires the date information as conclusion date information. Note that the technology for acquiring character strings in the format of date information from a document is a publicly known technology.

[0076] The attribute value acquisition unit 131 detects, for example, one or more character strings in the format of date information from within the contract text. Next, the attribute value acquisition unit 131 determines, for example, whether or not one or more characters exist before the first date information detected (the first position in the contract text), and if not, acquires the date information as the conclusion date information. Furthermore, the attribute value acquisition unit 131 determines, for example, whether or not one or more characters exist after the last date information detected (the last position in the contract text), and if not, acquires the date information as the conclusion date information. (4) How to obtain information on the start date and end date of the contract

[0077] For example, the attribute value acquisition unit 131 identifies two pieces of date information from the contract document that match a period pattern of "<date information> to <date information>" or "<date information> to <date information>". Such period patterns are stored in the cue phrase storage unit 111. Furthermore, <date information> indicates that it can be replaced with date information. Next, the attribute value acquisition unit 131 acquires the first <date information> in the identified pattern as start date information. Furthermore, the attribute value acquisition unit 131 acquires the last <date information> in the identified pattern as end date information.

[0078] Furthermore, when the attribute value acquisition unit 131 detects, for example, two pieces of date information that match a period pattern from the contract document, and a period term (e.g., "period") that is a clue phrase exists immediately before the pattern, the attribute value acquisition unit 131 acquires the first <date information> of the detected pattern as the start date information, and acquires the latter <date information> as the end date information.

[0079] The attribute value acquisition unit 131 detects date information, for example, from within the contract document. Then, the attribute value acquisition unit 131 determines whether or not an effect term is included in a sentence containing the detected date information. Next, the attribute value acquisition unit 131 acquires, as start date information, the date information from the sentence determined to contain an effect term.

[0080] The attribute value acquisition unit 131 detects date information, for example, from within the contract document. Then, the attribute value acquisition unit 131 determines whether or not a sentence containing the detected date information includes a closing term (for example, "ends with"). Next, the attribute value acquisition unit 131 acquires, as closing date information, the date information from the sentence determined to include a closing term. (5) How to obtain automatic contract renewal information

[0081] The attribute value acquisition unit 131, for example, determines whether or not any of the automatic renewal patterns indicating that the contract is an automatic renewal contract exists in the contract text, and if so, acquires automatic renewal information indicating automatic renewal. (6) How to obtain contract cancellation notice deadline information

[0082] For example, when the attribute value acquisition unit 131 acquires end date information, it acquires cancellation notice deadline information as shown below. That is, the attribute value acquisition unit 131 determines whether or not a deadline anticipation term (e.g., "the same applies thereafter") and a date term (e.g., "X months before" or "X months before") are present in the contract text, and if they are present, it acquires cancellation notice deadline information, which is the year, month, and date indicating the cancellation notice deadline, using the end date information and the date term. Note that the cancellation notice deadline information may also be a date term containing a numerical value (e.g., "1 month before"). (7) How to obtain contract amount information

[0083] The attribute value acquisition unit 131 acquires monetary amount expressions (for example, "~ yen" or "$~") from the contract text as monetary amount information.

[0084] The attribute value acquisition unit 131 detects, for example, a monetary expression from within the contract text. Next, the attribute value acquisition unit 131 determines, for example, whether a cue phrase of monetary information (e.g., "price" or "compensation") exists close enough to the monetary expression to satisfy a predetermined condition. If a cue phrase of monetary information exists, the monetary expression for the cue phrase is acquired as monetary information.

[0085] The storage support unit 132 performs storage support processing for storing two or more contract attribute values. The storage support processing is, for example, a storage process, or a process of transmitting to an external device (not shown) for storage in the external device. The storage destination of the two or more contract attribute values ​​may be the contract processing device 1 or another device.

[0086] It is preferable that the storage support unit 132 stores two or more contract attribute values ​​in association with the contract information from which the contract attribute values ​​were acquired. The two or more contract attribute values ​​may also include personal identification information.

[0087] The search unit 133 determines contract information that matches the received search information. The search unit 133 searches for contract information that matches the search information, for example, contract information in the contract information storage unit 113. Note that the contract information determined by the search unit 133 may be contract information stored in an external device (not shown). Furthermore, searching for contract information may also involve obtaining part of the contract information.

[0088] The post-processing unit 134 performs post-processing using one or more of the two or more contract attribute values ​​corresponding to the contract information. Here, the post-processing is, for example, processing performed by a notification unit 1341 (described later), processing performed by an update unit 1342 (described later), or processing performed by a specification unit 1343 (described later).

[0089] The notification means 1341, for example, acquires expiration date information corresponding to the contract information, and when it determines that the date indicated by the expiration date information is approaching so quickly that it satisfies predetermined conditions, it issues a notification regarding the renewal of the contract in the contract information. Note that the predetermined conditions are, for example, "1 month" or "60 days," and are stored in the storage unit 11.

[0090] For example, when the notification means 1341 determines that the date indicated by the cancellation notice deadline information corresponding to the contract information is approaching so quickly that it satisfies predetermined conditions, the notification means 1341 issues a notification regarding the cancellation of the contract in the contract information. Note that the predetermined conditions are, for example, "1 month" or "60 days," and are stored in the storage unit 11.

[0091] There is no restriction on the timing at which the notification means 1341 operates. For example, the notification means 1341 operates periodically for one or more pieces of contract information.

[0092] The update means 1342 acquires automatic update information corresponding to the contract information, and if the automatic update information indicates automatic update "enabled," acquires the automatic update date paired with the automatic update information, acquires the next end date information corresponding to the automatic update date, and updates the next end date information as the end date information. It is preferable that the update means 1342 updates the next end date information as the end date information when the date indicated by the current end date information has passed or the date indicated by the current end date information has arrived, or when the day indicated by the cancellation notice deadline information has passed or the date indicated by the cancellation notice deadline information has arrived.

[0093] The indicating means 1343 performs a process of indicating information using one or more contract attribute values. The indicating means 1343, for example, acquires start date information and end date information corresponding to contract information, acquires information on a validity period determined by the start date information and end date information, and performs a process of indicating the information on the validity period. Note that this indicating process is, for example, a process of transmitting the information to the terminal device 2. Also, this indicating process is, for example, a process of indicating the validity period in calendar information.

[0094] The indicating means 1343 performs processing for indicating a class (described later) for each inspection unit in the contract information, for example. The indicating means 1343 performs processing such that the portion of the inspection unit corresponding to the class "unfavorable" is output in a highlighted manner compared to other portions. This processing is, for example, processing such as changing the font of the portion of the inspection unit corresponding to the class "unfavorable" to bold, turning it in red, or underlining it.

[0095] The classification unit 135 analyzes one or more inspection units of the contract document and obtains a class for each inspection unit. An inspection unit is, for example, the entire contract information, a chapter in the contract information, an article in the contract information (for example, information classified by a heading that matches Article X), a clause in the contract information (for example, information classified by a numerical heading), a number in the contract information (for example, information classified by a "(numerical)" heading), or a sentence in the contract information. A class may also be called a classification. A class is information about whether a contract is disadvantageous or not. A class is, for example, one of three classifications: "disadvantageous," "advantageous," and "neutral." A class is, for example, one of two classifications: "disadvantageous" and "not disadvantageous."

[0096] The classification unit 135, for example, acquires a class for each of one or more inspection units of the contract document of one piece of contract information.

[0097] The classification unit 135 acquires, for example, a class for each of one or more inspection units of the contract text of each of two or more pieces of contract information. Each of two or more pieces of contract information is, for example, contract information for one organization or contract information for one person in charge.

[0098] The classification unit 135 may use, for example, (1) a machine learning method, or (2) a pattern matching method, etc. Examples of the two methods will be described below. (1) Machine learning method

[0099] The classification unit 135 accepts an inspection unit or a vector obtained from the inspection unit, and performs prediction processing using a machine learning algorithm using the class learner in the learning information storage unit 112 and the inspection unit or vector to obtain a class.

[0100] The classification unit 135, for example, receives an inspection unit, provides the inspection unit and a class learning device capable of multi-value classification to a module that performs machine learning prediction processing, executes the module, and obtains a class.

[0101] The classification unit 135, for example, accepts an inspection unit, constructs a vector (for example, a vector having the number of occurrences of each word as an element) from the inspection unit, provides the vector and a class learner capable of multi-value classification to a module that performs machine learning prediction processing, executes the module, and obtains a class.

[0102] The classification unit 135, for example, receives an inspection unit, and for each class, provides the inspection unit or vector and a class learner capable of performing binary classification of the class to a module that performs machine learning prediction processing, executes the module, and determines whether or not the inspection unit belongs to the class. Then, the classification unit 135 acquires the class that it is determined to belong to.

[0103] As described above, the class learner may be a learner capable of multi-value classification to acquire a class, or may be a learner for binary classification to determine whether or not a data belongs to a specific class. (2) Pattern matching method

[0104] The classification unit 135 determines, for each inspection unit, whether or not the inspection unit contains a sentence that matches a class determination pattern for determining a class in the storage unit 11 or has a similarity equal to or greater than a threshold. If the inspection unit contains such a sentence, the classification unit 135 acquires a party identifier and a class corresponding to the class determination pattern.

[0105] The related information acquisition unit 136 acquires related information using the classes acquired by the classification unit 135. The related information is information about the classes. The related information is information about unfavorable or favorable contract contents. The related information is the result of statistical processing of one or more classes acquired by the classification unit 135. The related information may be the class itself. The result of the statistical processing is, for example, a score. The score is, for example, an individual score or an overall score. The individual score is a score that indicates the degree of dearth of unfavorable items contained in one piece of contract information. The overall score is a score that indicates the degree of dearth of unfavorable items in one or more pieces of contract information that meet predetermined conditions. The overall score is, for example, the overall score of two or more pieces of contract information from one organization. The overall score is, for example, the overall score of two or more pieces of contract information from one organization for one period (for example, one fiscal year).

[0106] The related information acquisition unit 136, for example, performs statistical processing on one or more classes acquired by the classification unit 135 for each inspection unit, and calculates a score. The related information acquisition unit 136, for example, performs statistical processing on one or more classes acquired by the classification unit 135 for each one or two or more pieces of contract information, and calculates a score.

[0107] The unit score acquisition means 1361 acquires a unit score, which is the score of one piece of contract information, using one or more classes acquired by the classification unit 135 for each inspection unit in one piece of contract information.

[0108] The individual score acquisition means 1361, for example, acquires two or more inspection unit classes of one contract information, and acquires an individual score that becomes lower the more the number of "unfavorable" classes there are. The individual score acquisition means 1361, for example, acquires two or more inspection unit classes of one contract information, and acquires an individual score that becomes higher the more the number of "favorable" classes there are.

[0109] The individual score acquisition means 1361, for example, acquires two or more inspection unit classes of one contract information, calculates the proportion of the "unfavorable" class from the classes (number of "unfavorable" classes / number of inspections), and acquires a score using a decreasing function with the proportion as a parameter.The individual score acquisition means 1361, for example, acquires two or more inspection unit classes of one contract information, calculates the "number of "unfavorable" classes - number of "favorable" classes" from the classes, and acquires a score using a decreasing function with the difference as a parameter.

[0110] The single score acquisition means 1361, for example, acquires two or more inspection unit classes of one contract information, and from the classes, acquires the number of "unfavorable" classes and the number of "favorable" classes, and it is preferable that the fewer the "unfavorable" numbers and the more the "favorable" numbers, the higher the score acquired.

[0111] The overall score acquisition means 1362 uses two or more classes acquired by the classification unit 135 to acquire an overall score, which is the score of two or more pieces of contract information.

[0112] The individual score acquisition means 1361, for example, acquires the individual score of each of two or more pieces of contract information belonging to one group. Next, the overall score acquisition means 1362, for example, acquires a representative value (for example, an average, median, or total value) of the two or more pieces of contract score as an overall score. Note that the two or more pieces of contract information belonging to one group are, for example, contract information associated with one organization identifier, and contract information associated with one organization identifier and date information of a predetermined period.

[0113] The contribution information acquisition means 1363 acquires contribution information relating to the difference between the individual score acquired from the contract information at a second point in time after the first point in time and the individual score at the first point in time in the score storage unit 114. The contribution information is information indicating the contribution to legal work or the contribution to business. For example, the contribution information acquisition means 1363 acquires the difference between a second individual score acquired from the contract information at the second point in time corresponding to one contract and a first individual score acquired from the contract information at the first point in time corresponding to the one contract, and acquires contribution information with a higher score the greater the difference.

[0114] The contribution information acquisition means 1363 acquires contribution information relating to the difference between the overall score acquired from contract information at a second time point that is later than the first time point and the overall score at the first time point in the score storage unit 114. The contribution information acquisition means 1363 acquires, for example, the difference between a second overall score acquired from one or more pieces of contract information at the second time point that corresponds to one organization identifier and a first overall score acquired from one or more pieces of contract information at the first time point that corresponds to the one organization identifier, and acquires contribution information with a higher score as the difference increases.

[0115] When a class satisfies a predetermined condition, the recommendation acquisition means 1364 acquires recommendation information based on the test unit corresponding to the class. The predetermined condition is, for example, that the class is "unfavorable" or that the score is equal to or less than a threshold. The recommendation information is information presented to the user to improve an unfavorable situation of the contract, such as information that the test unit is unfavorable and information on the contract contents to overturn the test unit. For example, the unfavorable contract text and the favorable contract text are associated and stored in the storage unit 11.

[0116] The transmitting unit 14 transmits various types of information, such as related information.

[0117] The related information output unit 141 outputs related information. For example, the related information output unit 141 outputs one or more pieces of information selected from the group consisting of a single score, a total score, recommendation information, and contribution information.

[0118] Here, output usually means transmission to the terminal device 2. However, output may also be a concept that includes display on a display, projection using a projector, printing on a printer, sound output, storage on a recording medium, delivery of processing results to another processing device or another program, etc.

[0119] The contract information output unit 142 outputs all or part of the information contained in the contract information determined by the search unit 133. For example, the contract information output unit 142 outputs contract document information contained in the contract information determined by the search unit 133. For example, the contract information output unit 142 may output two or more attribute values ​​contained in the contract information determined by the search unit 133.

[0120] Here, output usually means transmission to the terminal device 2. However, output may also be a concept that includes display on a display, projection using a projector, printing on a printer, sound output, storage on a recording medium, delivery of processing results to another processing device or another program, etc.

[0121] Various types of information are stored in the terminal storage unit 21 constituting the terminal device 2. The various types of information include, for example, a user identifier, a terminal identifier, and an organization identifier of the organization to which the user belongs. The terminal identifier may also be considered as a user identifier.

[0122] The terminal reception unit 22 receives various instructions, information, etc. The various instructions, information, etc. include, for example, contract information and search information. The means for inputting the various instructions, information, etc. may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0123] The device processing unit 23 performs various types of processing. For example, the various types of processing include processing for configuring information received by the device receiving unit 25 into data to be displayed. For example, the various types of processing include processing for configuring instructions received by the device accepting unit 22 into instructions to be transmitted.

[0124] The terminal transmitting unit 24 transmits various instructions, information, etc. to the contract processing device 1. The various instructions, information, etc. are, for example, instructions configured by the terminal processing unit 23, instructions and information accepted by the terminal accepting unit 22, etc.

[0125] The terminal receiving unit 25 receives various types of information from the contract processing device 1. The various types of information include, for example, related information, contract information, and contract attribute values.

[0126] The terminal output unit 26 outputs various types of information. The various types of information include, for example, information accepted by the terminal acceptance unit 22, information received by the terminal reception unit 25, and information configured by the device processing unit 23. The various types of information include, for example, related information, contract information, and contract attribute values.

[0127] The storage unit 11, cue phrase storage unit 111, learning information storage unit 112, contract information storage unit 113, score storage unit 114, and terminal storage unit 21 are preferably non-volatile recording media, but can also be realized as volatile recording media.

[0128] There is no restriction on the process by which information is stored in the storage unit 11 etc. For example, information may be stored in the storage unit 11 etc. via a recording medium, information transmitted via a communication line etc. may be stored in the storage unit 11 etc., or information input via an input device may be stored in the storage unit 11 etc.

[0129] The receiving unit 12, the contract acceptance unit 121, the search information receiving unit 122, and the terminal receiving unit 25 are usually realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0130] The processing unit 13, attribute value acquisition unit 131, accumulation support unit 132, search unit 133, post-processing unit 134, classification unit 135, related information acquisition unit 136, notification means 1341, update means 1342, explicit indication means 1343, individual score acquisition means 1361, total score acquisition means 1362, contribution information acquisition means 1363, recommendation acquisition means 1364, and device processing unit 23 can typically be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are typically realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0131] The transmitting unit 14, the related information output unit 141, the contract information output unit 142, and the terminal transmitting unit 24 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

[0132] The terminal reception unit 22 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0133] The terminal output unit 26 may or may not include an output device such as a display, a speaker, etc. The terminal output unit 26 may be realized by driver software for an output device, or by a combination of driver software for an output device and the output device, etc.

[0134] Next, an example of the operation of the information system A will be described. First, an example of the operation of the contract processing device 1 will be described with reference to the flowchart of FIG.

[0135] (Step S401) The contract reception unit 121 determines whether or not contract information associated with an organization identifier has been received from the terminal device 2. If contract information has been received, the process proceeds to step S402, and if contract information has not been received, the process proceeds to step S409.

[0136] (Step S402) The attribute value acquisition unit 131 acquires the contract text from the contract information received in step S401.

[0137] (Step S403) The attribute value acquisition unit 131 acquires two or more contract attribute values ​​using the contract text acquired in step S402. An example of the attribute value acquisition process for acquiring the contract attribute values ​​will be described with reference to the flowchart in FIG.

[0138] (Step S404) The storage support unit 132 stores the two or more contract attribute values ​​acquired in step S403 in association with the received contract information and organization identifier. The storage destination is, for example, the contract information storage unit 113, but it may also be an external device. The organization identifier may also be considered to be one of the two or more contract attribute values.

[0139] (Step S405) The related information acquisition unit 136 performs related information acquisition processing. An example of the related information acquisition processing will be described with reference to the flowchart of FIG.

[0140] (Step S406) The storage support unit 132 stores the one or more pieces of related information acquired in step S405 in association with the contract information received in step S401.

[0141] (Step S407) The processing unit 13 determines whether to make a recommendation. If a recommendation is to be made, the process proceeds to step S408, and if a recommendation is not to be made, the process returns to step S401. Note that there are no restrictions on the conditions for making a recommendation. The processing unit 13 may decide to make a recommendation when there is a test target corresponding to the class "unfavorable."

[0142] (Step S408) The related information output unit 141 transmits the recommendation acquired in step S405 to the terminal device 2 that transmitted the contract information. The process returns to step S401.

[0143] (Step S409) The search information receiving unit 122 determines whether or not search information has been received. If search information has been received, the process proceeds to step S410, and if search information has not been received, the process proceeds to step S412.

[0144] (Step S410) The search unit 133 acquires information about the contract that matches the search information received in step S409.

[0145] (Step S411) The contract information output unit 142 transmits the information acquired in step S410 to the terminal device 2 that transmitted the search information. Return to step S401.

[0146] (Step S412) Post-processing unit 134 determines whether or not to perform post-processing. If post-processing is to be performed, the process proceeds to step S413, and if post-processing is not to be performed, the process proceeds to step S418. Note that, for example, when an instruction to perform post-processing is received, post-processing unit 134 determines to perform post-processing at a predetermined timing.

[0147] (Step S413) The post-processing unit 134 assigns 1 to the counter i.

[0148] (Step S414) The post-processing unit 134 determines whether or not the ith contract information to be post-processed exists. If the ith contract information exists, the process proceeds to step S415; if the ith contract information does not exist, the process returns to step S401. The contract information to be post-processed may be specified by information included in the received post-processing instruction, or may be all of the contract information stored in the storage unit 11. The post-processing unit 134 may also perform post-processing on the received contract information. The information included in the received post-processing instruction is, for example, information that identifies the contract information, an organization identifier.

[0149] (Step S415) The notification means 1341 performs notification processing for the i-th contract information. An example of the notification processing will be described with reference to the flowchart in FIG.

[0150] (Step S416) The update means 1342 performs update processing on the i-th contract information. An example of the update processing will be described with reference to the flowchart in FIG.

[0151] (Step S417) The post-processing unit 134 increments the counter i by 1. The process returns to step S414.

[0152] (Step S418) The related information acquisition unit 136 determines whether or not to perform statistical processing on the scores. If statistical processing is to be performed, the process proceeds to step S419, and if statistical processing is not to be performed, the process returns to step S401. Note that the related information acquisition unit 136 determines to perform statistical processing, for example, when an instruction to perform statistical processing is received or when a predetermined time arrives.

[0153] (Step S419) The related information acquisition unit 136 determines whether or not to acquire a total score. If the total score is to be acquired, the process proceeds to step S420, and if the total score is not to be acquired, the process proceeds to step S422. Note that any condition may be met for acquiring the total score.

[0154] (Step S420) The related information acquisition unit 136 acquires a total score. An example of the total score acquisition process will be described with reference to the flowchart in FIG.

[0155] (Step S421) The related information output unit 141 transmits the total score acquired in step S420 to the terminal device 2.

[0156] (Step S422) The related information acquisition unit 136 determines whether or not to acquire contribution information. If contribution information is to be acquired, the process proceeds to step S423, and if contribution information is not to be acquired, the process returns to step S401. Note that any condition may be met for acquiring contribution information.

[0157] (Step S423) The related information acquisition unit 136 acquires contribution information. An example of the contribution information acquisition process will be described with reference to the flowchart of FIG.

[0158] (Step S424) The related information output unit 141 transmits the contribution information acquired in step S423 to the terminal device 2. The process returns to step S401.

[0159] In the flowchart of FIG. 4, the process ends when the power is turned off or an interrupt occurs to end the process.

[0160] Next, the attribute value acquisition process in step S403 will be described with reference to the flowchart in FIG.

[0161] (Step S501) The attribute value acquisition unit 131 acquires type information from the contract document to be processed. An example of such type acquisition processing will be described with reference to the flowchart in FIG.

[0162] (Step S502) The attribute value acquisition unit 131 acquires counterparty information from the contract document to be processed. An example of such counterparty acquisition processing will be described with reference to the flowchart in FIG.

[0163] (Step S503) The attribute value acquisition unit 131 acquires the conclusion date information from the contract document to be processed. An example of such conclusion date acquisition processing will be described with reference to the flowchart of FIG.

[0164] (Step S504) The attribute value acquisition unit 131 acquires start date information and end date information from the contract document to be processed. An example of the start date / end date acquisition process will be described with reference to the flowchart in FIG.

[0165] (Step S505) The attribute value acquisition unit 131 acquires automatic update information from the contract document to be processed. An example of such automatic update acquisition processing will be described with reference to the flowchart in FIG.

[0166] (Step S506) The attribute value acquiring unit 131 acquires the cancellation notice deadline information from the contract document to be processed. An example of the cancellation notice deadline acquiring process will be described with reference to the flowchart in FIG.

[0167] (Step S507) The attribute value acquisition unit 131 acquires transaction amount information from the contract document to be processed. An example of such transaction amount acquisition processing will be described with reference to the flowchart in FIG.

[0168] Next, an example of the type acquisition process in step S501 will be described with reference to the flowchart in FIG.

[0169] (Step S601) The attribute value acquisition unit 131 acquires the character string of the header line of the target contract document.

[0170] (Step S602) The attribute value acquisition unit 131 assigns 1 to a counter i.

[0171] (Step S603) The attribute value acquiring unit 131 determines whether or not the i-th type information exists in the cue phrase storage unit 111. If the i-th type information exists, the process proceeds to step S604; if the i-th type information does not exist, the process proceeds to step S609.

[0172] (Step S604) The attribute value acquiring unit 131 acquires the similarity between the character string acquired in step S601 and the i-th type information.

[0173] (Step S605) The attribute value acquisition unit 131 determines whether or not the two character strings match based on the similarity acquired in step S604. If they match, the process proceeds to step S606, and if they do not match, the process proceeds to step S607.

[0174] (Step S606) The attribute value acquisition unit 131 stores the i-th type information as the type information that is the contract attribute value of the target contract information, and returns to the upper processing.

[0175] (Step S607) The attribute value acquiring unit 131 temporarily stores the similarity in a buffer (not shown) in association with the i-th type information.

[0176] (Step S608) The attribute value acquisition unit 131 increments the counter i by 1. The process returns to step S603.

[0177] (Step S609) The attribute value acquisition unit 131 accumulates the type information whose similarity satisfies the condition as type information, which is the contract attribute value of the target contract information. It returns to the upper level processing. The condition is, for example, "the similarity is maximum" or "the similarity is maximum and is equal to or greater than the threshold value."

[0178] Next, an example of the partner acquisition process in step S502 will be described with reference to the flowchart in FIG.

[0179] (Step S701) The attribute value acquisition unit 131 acquires a character string within a predetermined second range from the contract document to be processed.

[0180] (Step S702) The attribute value acquiring unit 131 performs, for example, morphological analysis on the character string acquired in step S701 to acquire one or more noun phrases.

[0181] (Step S703) The attribute value acquisition unit 131 assigns 1 to a counter i.

[0182] (Step S704) The attribute value acquisition unit 131 determines whether the i-th noun phrase is present among the noun phrases acquired in step S702. If the i-th noun phrase is present, the process proceeds to step S705; if the i-th noun phrase is not present, the process returns to the upper process.

[0183] (Step S705) The attribute value acquiring unit 131 uses the name learner in the storage unit 11 to determine, through machine learning prediction processing, whether the ith noun phrase is an organization name or a person's name.

[0184] (Step S706) If the determination result in step S705 is an organization name or a person's name, the attribute value acquiring unit 131 proceeds to step S707, and if it is not an organization name or a person's name, the attribute value acquiring unit 131 proceeds to step S712.

[0185] (Step S707) The attribute value acquiring unit 131 acquires a character string (a sentence, or two or more terms) that includes the i-th noun phrase and is within a predetermined distance from the i-th noun phrase.

[0186] (Step S708) The attribute value acquisition unit 131 determines whether the character string acquired in step S707 includes a party term (for example, "A" or "B"). If it includes a party term, the process proceeds to step S709; if it does not, the process proceeds to step S712.

[0187] (Step S709) The attribute value acquisition unit 131 acquires, for example, personal identification information associated with the contract information to be processed. Next, the attribute value acquisition unit 131 determines whether the i-th noun phrase matches the personal identification information. If they match, the process proceeds to step S712, and if they do not match, the process proceeds to step S710.

[0188] (Step S710) The attribute value acquisition unit 131 determines whether the i-th noun phrase has already been registered. If it has already been registered, the process proceeds to step S712, and if it has not already been registered, the process proceeds to step S711.

[0189] (Step S711) The attribute value acquisition unit 131 registers the ith noun phrase as the other party information. Note that registration means storing the noun phrase as one of the contract attribute values ​​in association with the contract information. Here, it is preferable that the attribute value acquisition unit 131 stores the other party information in pairs with the party term.

[0190] (Step S712) The attribute value acquiring unit 131 increments the counter i by 1. The process returns to step S704.

[0191] Next, an example of the conclusion date acquisition process in step S503 will be described with reference to the flowchart in FIG.

[0192] (Step S801) The attribute value acquisition unit 131 acquires all date information from the target contract document, paired with location information that identifies that location. Note that location information is, for example, an offset, a line number, etc., but any information that can identify a location within the contract document will do. Furthermore, the technology for acquiring date information and location information having a date structure (such as "year / month / day" or "xx / xx / xx") from a document is a publicly known technology.

[0193] (Step S802) The attribute value acquiring unit 131 assigns 1 to a counter i.

[0194] (Step S803) The attribute value acquisition unit 131 determines whether the i-th date information exists among the date information acquired in step S801. If the i-th date information exists, the process proceeds to step S804, and if the i-th date information does not exist, the process returns to the upper process.

[0195] (Step S804) The attribute value acquiring unit 131 temporarily stores the ith date information and location information as a pair.

[0196] (Step S805) The attribute value acquisition unit 131 determines whether the i-th date information is the first date information among the date information acquired in step S801. If it is the first date information, the process proceeds to step S807, and if it is not the first date information, the process proceeds to step S806.

[0197] (Step S806) The attribute value acquisition unit 131 determines whether the i-th date information is the last date information among the date information acquired in step S801. If it is the last date information, the process proceeds to step S807, and if it is not the last date information, the process proceeds to step S809.

[0198] (Step S807) The attribute value acquisition unit 131 determines whether or not any wording (for example, "is") exists before and after the i-th date information. If the wording exists, the process proceeds to step S808; if the wording does not exist, the process proceeds to step S809.

[0199] (Step S808) The attribute value acquiring unit 131 stores the i-th date information as contract conclusion date information in association with the contract information.

[0200] (Step S809) The attribute value acquiring unit 131 increments the counter i by 1. The process returns to step S803.

[0201] Next, an example of the start date / end date acquisition process in step S504 will be described with reference to the flowchart in FIG.

[0202] (Step S901) The attribute value acquisition unit 131 assigns 1 to a counter i.

[0203] (Step S902) The attribute value acquisition unit 131 determines whether the i-th date information exists among the date information acquired in step S801. If the i-th date information exists, the process proceeds to step S903, and if the i-th date information does not exist, the process returns to the upper process.

[0204] (Step S903) The attribute value acquisition unit 131 acquires a character string in a predetermined range following the i-th date information. The predetermined range may be, for example, the same line as the i-th date information, a sentence including the i-th date information, or a clause including the i-th date information.

[0205] (Step S904) The attribute value acquisition unit 131 assigns 1 to a counter j.

[0206] (Step S905) The attribute value acquiring unit 131 judges whether or not the j-th period pattern exists in the cue phrase storage unit 111. If the j-th period pattern exists, the process proceeds to step S906; if not, the process proceeds to step S912.

[0207] (Step S906) The attribute value acquiring unit 131 determines whether or not the character string acquired in step S903 is an expression of the j-th period pattern. If it is an expression of the j-th period pattern, the process proceeds to step S907, and if it is not an expression of the j-th period pattern, the process proceeds to step S911.

[0208] (Step S907) The attribute value acquiring unit 131 acquires a character string in a predetermined range before the i-th date information. The predetermined range may be, for example, one noun phrase, one sentence, one line, or the like, and is not restrictive.

[0209] (Step S908) The attribute value acquisition unit 131 determines whether or not a term of a period (for example, "period") is present in the character string acquired in step S907. If a term of a period is present, the process proceeds to step S909; if a term of a period is not present, the process proceeds to step S911.

[0210] (Step S909) The attribute value acquiring unit 131 acquires the first date information in the character string that matches the expression of the j-th period pattern as start date information, and stores it in association with the contract information.

[0211] (Step S910) The attribute value acquiring unit 131 acquires the later date information in the character string that matches the expression of the j-th period pattern as end information, associates it with the contract information, and stores it. Then, the process returns to the upper level process.

[0212] (Step S911) The attribute value acquiring unit 131 increments the counter j by 1. The process returns to step S905.

[0213] (Step S912) The attribute value acquisition unit 131 determines whether or not an effect term (e.g., "effect") is included in the character string acquired in step S903. If an effect term is included, the process proceeds to step S913; if an effect term is not included, the process proceeds to step S914.

[0214] (Step S913) The attribute value acquiring unit 131 acquires the i-th date information as start date information, and stores it in association with the contract information.

[0215] (Step S914) The attribute value acquisition unit 131 determines whether or not the character string acquired in step S903 includes a termination term (for example, "ends with"). If the termination term is included, the process proceeds to step S915; if the termination term is not included, the process proceeds to step S916.

[0216] (Step S915) The attribute value acquiring unit 131 acquires the i-th date information as end information, and stores it in association with the contract information.

[0217] (Step S916) The attribute value acquiring unit 131 increments the counter i by 1. The process returns to step S902.

[0218] Next, an example of the automatic update acquisition process in step S505 will be described with reference to the flowchart in FIG.

[0219] (Step S1001) The attribute value acquisition unit 131 assigns 1 to a counter i.

[0220] (Step S1002) The attribute value acquisition unit 131 determines whether or not the i-th automatic update pattern exists in the cue phrase storage unit 111. If the i-th automatic update pattern exists, the process proceeds to step S1003; if the i-th automatic update pattern does not exist, the process returns to the upper process.

[0221] (Step S 1003 ) The attribute value acquiring unit 131 acquires the i-th automatic update pattern from the cue phrase storage unit 111 .

[0222] (Step S1004) The attribute value acquiring unit 131 assigns 1 to a counter j.

[0223] (Step S1005) The attribute value acquisition unit 131 determines whether or not the jth inspection unit exists in the contract document. If the jth inspection unit exists, the process proceeds to step S1006, and if not, the process proceeds to step S1009. The inspection unit may be a sentence, a clause, or the like.

[0224] (Step S1006) The attribute value acquisition unit 131 determines whether or not a character string that matches the i-th automatic update pattern exists in the j-th inspection unit. If it exists, the process proceeds to step S1007, and if it does not exist, the process proceeds to step S1008.

[0225] (Step S1007) The attribute value acquiring unit 131 assigns "Yes" to the contract attribute value "Automatic Update Information." The contract attribute value "Automatic Update Information" is stored in association with the contract information.

[0226] (Step S1008) The attribute value acquiring unit 131 increments the counter j by 1. The process returns to step S1005.

[0227] (Step S1009) The attribute value acquiring unit 131 increments the counter i by 1. The process returns to step S1002.

[0228] In the flowchart of FIG. 10, if the determination result in step S1002 is "No," the attribute value acquisition unit 131 may assign "None" to the contract attribute value "Automatic Update Information" and store the contract attribute value in association with the contract information.

[0229] Next, an example of the cancellation notice deadline acquisition process in step S506 will be described with reference to the flowchart in FIG.

[0230] (Step S1101) The attribute value acquisition unit 131 determines whether or not the end date information for the target contract information has been acquired. If the end date information has been acquired, the process proceeds to step S1102, and if the end date information has not been acquired, the process returns to the upper processing.

[0231] (Step S1102) The attribute value acquiring unit 131 assigns 1 to a counter i.

[0232] (Step S1103) The attribute value acquiring unit 131 judges whether or not the i-th deadline anticipating term exists in the clue phrase storage unit 111. If the i-th deadline anticipating term exists, the process proceeds to step S1104; if not, the process returns to the upper process.

[0233] (Step S1104) The attribute value acquiring unit 131 acquires the i-th deadline anticipating term from the cue phrase storage unit 111.

[0234] (Step S1105) The attribute value acquiring unit 131 assigns 1 to a counter j.

[0235] (Step S1106) The attribute value acquisition unit 131 determines whether the jth inspection target exists in the target contract document. If the jth inspection target exists, the process proceeds to step S1107, and if the jth inspection target does not exist, the process proceeds to step S1115.

[0236] (Step S1107) The attribute value acquisition unit 131 determines whether the i-th deadline-anticipating term exists in the j-th test target. If the i-th deadline-anticipating term exists, the process proceeds to step S1108, and if the i-th deadline-anticipating term does not exist, the process proceeds to step S1114.

[0237] (Step S1108) The attribute value acquiring unit 131 acquires a character string that is a character string around the ith deadline-anticipating term in the jth test target and is at a distance from the ith deadline-anticipating term that satisfies a predetermined condition.

[0238] (Step S1109) The attribute value acquiring unit 131 assigns 1 to a counter k.

[0239] (Step S1110) The attribute value acquiring unit 131 determines whether or not the kth date term exists in the cue phrase storage unit 111. If the kth date term exists, the process proceeds to step S1111; if not, the process proceeds to step S1114.

[0240] (Step S1111) The attribute value acquisition unit 131 determines whether or not the kth date term exists in the character string acquired in step S1108. If the kth date term exists, the process proceeds to step S1112, and if the kth date term does not exist, the process proceeds to step S1113.

[0241] (Step S1112) The attribute value acquisition unit 131 acquires the date information of the part corresponding to the kth date term. The attribute value acquisition unit 131 also acquires the cancellation notice deadline information using the end date information and the date information. The process returns to the upper level process. For example, if the end date information is "July 31, 2020" and the date information is "two months ago," the attribute value acquisition unit 131 acquires the cancellation notice deadline information "May 31, 2020."

[0242] (Step S1113) The attribute value acquiring unit 131 increments the counter k by 1. The process returns to step S1110.

[0243] (Step S1114) The attribute value acquiring unit 131 increments the counter j by 1. The process returns to step S1106.

[0244] (Step S1115) The attribute value acquiring unit 131 increments the counter i by 1. The process returns to step S1103.

[0245] Next, an example of the transaction amount acquisition process in step S507 will be described with reference to the flowchart in FIG.

[0246] (Step S1201) The attribute value acquisition unit 131 assigns 1 to a counter i.

[0247] (Step S1202) The attribute value acquisition unit 131 determines whether or not the i-th inspection unit exists in the contract document. If the i-th inspection unit exists, the process proceeds to step S1203, and if not, the process returns to the upper processing. The inspection unit may be, for example, a sentence, a clause, or the like, and does not matter.

[0248] (Step S1203) The attribute value acquisition unit 131 determines whether the i-th inspection unit contains a monetary amount expression (such as "numeric string 'yen'" or "numeric string '$'"). If it contains a monetary amount expression, the process proceeds to step S1204; if it does not, the process proceeds to step S1210.

[0249] (Step S1204) The attribute value acquiring unit 131 acquires surrounding character strings that are close enough to the monetary amount expression to satisfy a predetermined condition.

[0250] (Step S1205) The attribute value acquiring unit 131 assigns 1 to a counter j.

[0251] (Step S1206) The attribute value acquisition unit 131 determines whether the jth transaction amount term exists in the cue phrase storage unit 111. If the ith transaction amount term exists, the process proceeds to step S1207; if the ith transaction amount term does not exist, the process proceeds to step S1210.

[0252] (Step S1207) The attribute value acquisition unit 131 determines whether the jth transaction amount term is included in the character string acquired in step S1204. If the jth transaction amount term is included, the process proceeds to step S1208; if the jth transaction amount term is not included, the process proceeds to step S1209.

[0253] (Step S1208) The attribute value acquiring unit 131 acquires the acquired amount expression as transaction amount information, associates it with the contract information, and stores it. The process returns to the upper level process.

[0254] (Step S1209) The attribute value acquiring unit 131 increments the counter j by 1. The process returns to step S1206.

[0255] (Step S1210) The counter i is incremented by 1. The process returns to step S1202.

[0256] Next, an example of the related information acquisition process in step S405 will be described with reference to the flowchart in FIG.

[0257] (Step S1301) The single score acquisition means 1361 assigns 1 to a counter i. Also, the single score acquisition means 1361 assigns 0 to the number of each class. Each class is, for example, "unfavorable", "advantageous", or "neutral".

[0258] (Step S1302) The unit score acquisition means 1361 determines whether the i-th inspection unit exists in the contract document to be inspected. If the i-th inspection unit exists, the process proceeds to step S1303, and if the i-th inspection unit does not exist, the process proceeds to step S1309.

[0259] (Step S1303) The simplex score acquisition means 1361 acquires the i-th inspection unit from the contract document.

[0260] (Step S1304) The single score acquisition means 1361 acquires the class of the i-th test unit. An example of such class acquisition processing will be described with reference to the flowchart in FIG.

[0261] (Step S1305) The simplex score acquisition means 1361 increments the number corresponding to the class acquired in step S1304 by one.

[0262] (Step S1306) The single score acquisition means 1361 determines whether the class acquired in step S1304 has the value "unfavorable." If the class has the value "unfavorable," proceed to step S1307, and if the class does not have the value "unfavorable," proceed to step S1308.

[0263] (Step S1307) The individual score acquisition means 1361 acquires the i-th inspection unit. Also, the individual score acquisition means 1361 acquires recommendation information corresponding to the i-th inspection unit. Then, the individual score acquisition means 1361 associates the i-th inspection unit with the recommendation information and temporarily stores them in a buffer (not shown).

[0264] The unit score acquiring means 1361 acquires, from the storage unit 11, recommendation information paired with a character string of an adverse clause whose similarity to the i-th inspection unit is large enough to satisfy a predetermined condition.

[0265] (Step S1308) The simplex score obtaining means 1361 increments the counter i by 1. The process returns to step S1302.

[0266] (Step S1309) The simplex score obtaining means 1361 calculates the simplex score using the number of each class.

[0267] (Step S1310) The unit score acquisition means 1361 stores the unit score acquired in step S1309 in association with the contract information.

[0268] (Step S1311) The unit score acquiring means 1361 uses the recommendation information acquired in step S1307 to configure recommendation information to be accumulated.

[0269] (Step S1312) The unit score acquisition means 1361 stores the recommendation information formed in step S1311 in association with the contract information, and returns to the upper level processing.

[0270] Next, an example of the class acquisition process in step S1304 will be described with reference to the flowchart in FIG.

[0271] (Step S1401) The classification unit 135 acquires the party's word (for example, "A").

[0272] (Step S1402) The classification unit 135 acquires the first-party term of the subject from the target test unit.

[0273] (Step S1403) The classification unit 135 determines the class of the subject in the unit of examination. An example of the unit of examination class determination process will be described with reference to the flowchart in FIG.

[0274] (Step S1404) The classification unit 135 judges whether the subject's party language in the check unit matches the person's party language. If they match, the process returns to the upper process, and if they do not match, the process proceeds to step S1405.

[0275] (Step S1405) The classification unit 135 determines whether the class determined in step S1403 is “disadvantageous.” If it is “disadvantageous,” the process proceeds to step S1406, and if it is not “disadvantageous,” the process proceeds to step S1407.

[0276] (Step S1406) The classification unit 135 assigns "advantageous" to the class, and returns to the upper level processing.

[0277] (Step S1407) The classification unit 135 determines whether the class determined in step S1403 is “advantageous.” If it is “advantageous,” the process proceeds to step S1408, and if it is not “advantageous,” the process returns to the upper process.

[0278] (Step S1408) The classification unit 135 assigns "disadvantage" to the class, and returns to the upper level processing.

[0279] Next, an example of the inspection unit class determination process in step S1403 will be described with reference to the flowchart in FIG.

[0280] (Step S1501) The classification unit 135 assigns 1 to a counter i.

[0281] (Step S1502) The classification unit 135 judges whether or not the i-th class determination pattern exists in the cue phrase storage unit 111. If it exists, the process proceeds to step S1503, and if it does not exist, the process proceeds to step S1508.

[0282] (Step S 1503 ) The classification unit 135 acquires the i-th class determination pattern from the cue phrase storage unit 111 .

[0283] (Step S1504) The classification unit 135 compares the test target with the i-th class determination pattern.

[0284] (Step S1505) The classification unit 135 determines whether the test target and the i-th class determination pattern are similar enough to satisfy a predetermined condition. If the predetermined condition is satisfied, the process proceeds to step S1506, and if the predetermined condition is not satisfied, the process proceeds to step S1507.

[0285] (Step S1506) The classification unit 135 acquires the class that pairs with the i-th class determination pattern, and returns to the upper-level processing.

[0286] (Step S1507) The classification unit 135 increments the counter i by 1. The process returns to step S1502.

[0287] (Step S1508) The classification unit 135 assigns the value "neutral" to the class.

[0288] In the flowchart of FIG. 15, the classification unit 135 may obtain the class of the examination unit using the machine learning method described above.

[0289] Next, an example of the notification process in step S415 will be described with reference to the flowchart in FIG.

[0290] (Step S1601) The notification means 1341 acquires date information indicating today's date from a clock (not shown).

[0291] (Step S1602) The notification means 1341 acquires the end date information paired with the contract information to be processed.

[0292] (Step S1603) The notification means 1341 determines whether the end date information satisfies a predetermined notification condition for the date information indicating today's date. If the condition is met, the process proceeds to step S1604, and if the condition is not met, the process proceeds to step S1606.

[0293] (Step S1604) The notification means 1341 acquires notification information corresponding to the end date information. The notification information or a template for the notification information is stored, for example, in the storage unit 11. The notification information or a template for the notification information is stored, for example, in the storage unit 11 in a pair with information specifying the end date information.

[0294] (Step S1605) The notification means 1341 transmits the notification information acquired in step S1604. Note that information specifying the destination (e.g., email address, telephone number, etc.) is stored in association with the target contract information, for example.

[0295] (Step S1606) The notification means 1341 acquires the contract cancellation deadline information paired with the contract information to be processed.

[0296] (Step S1607) The notification means 1341 determines whether the contract termination deadline information satisfies a predetermined notification condition for the date information indicating today's date. If the condition is met, the process proceeds to step S1608, and if the condition is not met, the process returns to the upper process.

[0297] (Step S1608) The notification means 1341 acquires notification information corresponding to the contract cancellation deadline information. The notification information or a template for the notification information is stored, for example, in the storage unit 11. The notification information or a template for the notification information is stored, for example, in the storage unit 11 in a pair with information specifying the contract cancellation deadline information.

[0298] (Step S1609) The notification means 1341 transmits the notification information acquired in step S1608. Note that information specifying the destination (e.g., email address, telephone number, etc.) is stored in association with the target contract information, for example.

[0299] Next, an example of the update process in step S416 will be described with reference to the flowchart in FIG.

[0300] (Step S1701) The update means 1342 acquires automatic update information paired with the contract information to be processed.

[0301] (Step S1702) The update means 1342 determines whether the information acquired in step S1701 indicates an automatic update. If the information indicates an automatic update, the process proceeds to step S1703, and if the information does not indicate an automatic update, the process returns to the upper processing.

[0302] (Step S1703) The update means 1342 acquires date information indicating today's date from a clock (not shown).

[0303] (Step S1704) The update means 1342 acquires the end date information paired with the contract information to be processed.

[0304] (Step S1705) The update means 1342 determines whether the end date information acquired in step S1704 satisfies a predetermined condition with respect to the date information indicating today's date. If the condition is satisfied, the process proceeds to step S1706, and if the condition is not satisfied, the process returns to the upper level process.

[0305] (Step S1706) The update means 1342 acquires end date information that identifies the next end date. The end date information that identifies the next end date is, for example, one year after the stored end date information. The end date information that identifies the next end date is, for example, N years after the stored end date information. "N years later" is information that is written in the contract information and is information that identifies the time to review the contract.

[0306] (Step S1707) The update means 1342 overwrites the old end date information with the end date information acquired in step S1706, and returns to the upper level processing.

[0307] 17, it is determined whether the end date information satisfies a predetermined condition with respect to the date information indicating the current date. However, the update means 1342 may also determine whether the cancellation notice deadline information satisfies a predetermined condition with respect to the date information indicating the current date.

[0308] Next, an example of the total score acquisition process in step S420 will be described with reference to the flowchart in FIG.

[0309] (Step S1801) The total score obtaining means 1362 reads out the individual scores paired with all the target contract information.

[0310] (Step S1802) The total score acquisition means 1362 acquires a representative value of the single scores equal to or greater than 1 acquired in step S1801. The process returns to the upper level process. This representative value is the total score here.

[0311] Next, an example of the contribution information acquisition process in step S423 will be described with reference to the flowchart in FIG.

[0312] (Step S1901) The contribution information acquiring unit 1363 acquires past scores of comparison targets.

[0313] (Step S1902) The contribution information acquisition unit 1363 acquires a score of interest. The score of interest is a score corresponding to contract information that is newer than the past score to be compared.

[0314] (Step S1903) The contribution information acquisition means 1363 calculates the difference between the score of interest and the past score to be compared. Next, the contribution information acquisition means 1363 acquires contribution information using this difference. The process returns to the upper level process.

[0315] In the flowchart of FIG. 19, the contribution information acquisition means 1363 normally uses the overall score, but may also use a single score corresponding to one piece of contract information.

[0316] Next, an example of the operation of the terminal device 2 will be described. The terminal reception unit 22 receives various instructions and information from the user (for example, instructions to acquire contract information, search information, individual scores, total scores, or contribution information). Next, the terminal processing unit 23 composes the instructions received by the terminal reception unit 22 into instructions to be transmitted. Next, the terminal transmission unit 24 transmits the various instructions and information to the contract processing device 1.

[0317] Furthermore, the terminal receiving unit 25 receives various information (for example, related information, contract information, contract attribute values, individual scores, total scores, and contribution information) from the contract processing device 1. Next, the terminal processing unit 23 composes the various information into information to be displayed. Next, the terminal output unit 26 outputs the information.

[0318] The specific operation of the information system A in this embodiment will be described below. A conceptual diagram of the information system A is shown in FIG.

[0319] It is assumed that the above-mentioned large amount of clue information is stored in the clue phrase storage unit 111 of the contract processing device 1. The clue information is information that serves as a clue for acquiring the contract attribute value from the contract text.

[0320] It is also assumed that the learning information storage unit 112 stores the above-mentioned name learner and class learner. The name learner is a learner for determining whether a received term is an organization name or a person's name. The class learner is a learner for determining the class (here, one of "unfavorable," "favorable," or "neutral") of the received inspection unit.

[0321] It is also assumed that the contract information storage unit 113 stores a contract information management table having the structure shown in FIG. 20. The contract information management table is a table that manages information about the contracts of each organization or individual. The contract information management table is a table that manages records that have an "ID," "user identifier," "organization identifier," "contract information," and "individual score." "ID" is information that identifies a record. "Contract information" here includes "type information," "counterparty information," "conclusion date information," "start date information," "end date information," "cancellation notice deadline information," "automatic renewal information," "amount information," and "file name." "File name" is the name of the file of contract information. It is assumed that the file identified by "file name" is stored in the contract information storage unit 113.

[0322] Also, it is assumed that the score storage unit 114 stores a total score management table having the structure shown in FIG. 21. The total score management table is a table that manages total scores related to contracts for each organization or individual and for each period. The total score management table is a table that manages records having an "ID," "organization identifier," "period identifier," and "total score." The "ID" is information that identifies the record. The "period identifier" is information that specifies the period of the contract information used to calculate the total score. The "period identifier" here is information that specifies the fiscal year. The "total score" here is, for example, contract information that pairs with the "organization identifier," and is the total score obtained using the contract information for the contract conclusion date for the period indicated by the "period identifier."

[0323] Furthermore, it is assumed that the storage unit 11 stores a user information management table in which two or more pieces of user information each having a user identifier and an organization identifier are stored.

[0324] Now, it is assumed that the user "U001" has used the terminal device 2 to send the contract in "fileA.pdf" to the contract processing device 1.

[0325] Next, the contract processing device 1 receives "fileA.pdf" and the user identifier "U001". Next, the contract processing device 1 obtains the organization identifier "Corporation A" that pairs with the user identifier "U001" from the user information management table. Furthermore, the contract processing device 1 uses the clue information in the clue phrase storage unit 111 and the name learner in the learning information storage unit 112 through the above-mentioned processing (for example, the processing described with reference to Figure 4, etc.) to obtain various contract attribute values ​​(type information, counterparty information,...automatic update information) of the record with "ID=1" in the table of Figure 20 from "fileA.pdf". On the other hand, it is assumed that the contract processing device 1 was unable to obtain amount information from "fileA.pdf".

[0326] Furthermore, through the above-described process, the contract processing device 1 uses a class learner to determine a class (here, "unfavorable," "favorable," or "neutral") for each inspection unit contained in "fileA.pdf" using a machine learning algorithm, and obtains the number of each of "unfavorable," "favorable," and "neutral." Next, the contract processing device 1 substitutes the number of each class into the arithmetic formula "single score = f (number of unfavorable, number of favorable, number of neutral)" or the arithmetic formula "single score = f (number of unfavorable, number of favorable)," executes the arithmetic formula, and obtains the single score of "fileA.pdf." Note that the arithmetic formula is a function that indicates a higher score for a larger number of unfavorables and a lower number of favorables. In this case, the arithmetic formula is a function that outputs the single score as an integer between 0 and 100. Then, the contract processing device 1 uses the arithmetic formula to calculate a single score of "75" for "fileA.pdf."

[0327] Next, the contract processing device 1 uses the various pieces of information acquired to create a record of "ID=1" in FIG. 20, and stores it in the contract information storage unit 113 together with the entity of "fileA.pdf".

[0328] The contract processing device 1 also transmits recommendation information constructed using the single score "75" and the inspection unit corresponding to "unfavorable" (for example, "The contract content of "<inspection unit>" is unfavorable. You may want to consider modifying the contract to improve it from next time onwards.") to the terminal device 2 of user "U001". Note that here, the explicit means 1343 of the contract processing device 1 may construct contract information that highlights the inspection unit corresponding to "unfavorable" in the contract information (for example, by writing it in red), and the contract processing device 1 may transmit the modified contract information to the terminal device 2. Note that <inspection unit> is a variable that contains the character string of the inspection unit.

[0329] Next, the terminal device 2 receives and outputs the single score "75" and the recommendation information.

[0330] The contract processing device 1 performs the above-described storage process of contract information every time contract information is received.

[0331] Also, assume that the contract processing device 1 performs notification processing for the record "ID=1" in FIG. 20, as follows. That is, assume that the notification means 1341 of the contract processing device 1 acquires date information "April 1, 2020" indicating today's date from a clock (not shown). The notification means 1341 also acquires cancellation notice deadline information "May 1, 2020" that pairs with the contract information of "ID=1" in the table of FIG. 20. The notification means 1341 then determines that the contract cancellation deadline information "May 1, 2020" satisfies the predetermined notification condition (within one month) for the date information "April 1, 2020" indicating today's date. Next, the notification means 1341 acquires notification information corresponding to the contract cancellation deadline information (for example, "The contract cancellation deadline of May 1, 2020 is approaching"). The notification means 1341 sends the acquired notification information to the contact address (separately managed) that is paired with the user identifier "U001."

[0332] Furthermore, it is assumed that the contract processing device 1 performs update processing on the record with "ID=1" in FIG. 20, for example, as follows. That is, it is assumed that the update means 1342 of the contract processing device 1 acquires date information "May 1, 2020" indicating today's date from a clock (not shown). The update means 1342 also acquires the cancellation notice deadline information "May 1, 2020" that pairs with the contract information with "ID=1" in the table of FIG. 20. The update means 1342 then determines that the contract cancellation deadline information "May 1, 2020" satisfies the predetermined notification condition (date information<=cancellation notice deadline information) for the date information "May 1, 2020" indicating today's date. Next, the update means 1342 acquires end date information "June 30, 2021" (one year later) that specifies the next end date. Next, the update means 1342 rewrites the end date information of the record with "ID=1" in FIG. 20 to "June 30, 2021."

[0333] Furthermore, the contract processing device 1 acquires a total score (here, for example, "72") using the individual scores paired with two or more pieces of contract information for which the date indicated by the contract date information paired with the organization identifier "Corporation A" falls within fiscal year 2019, using an increasing function (here, for example, a function for calculating an average value) with each individual score as a parameter, by performing the process of acquiring the total score described above. Next, the contract processing device 1 accumulates a record having the organization identifier "Corporation A", the period identifier "fiscal year 2019", and the total score "72" in the total score management table of FIG. 21. This record is the record with "ID=108" in FIG. 21.

[0334] Next, the contract processing device 1 acquires contribution information indicating the degree of contribution of the legal department of "Corporation A" to the business in fiscal year 2019 through the above-described processing. That is, the contribution information acquisition means 1363 of the contract processing device 1 acquires the overall score of "Corporation A" for fiscal year 2019, "72," from the table of FIG. 21. Next, the contribution information acquisition means 1363 acquires the overall score of "Corporation A" for fiscal year 2018, "65," from the table of FIG. 21. Next, the contribution information acquisition means 1363 calculates the difference of "7" between the score for fiscal year 2019 and the score of the comparison target for fiscal year 2018. Next, the related information output unit 141 sends the contribution information "7," which is the difference, to the contact point paired with the user identifier "U001" paired with "Corporation A."

[0335] As described above, according to this embodiment, appropriate management of contracts becomes easy.

[0336] Furthermore, according to this embodiment, the contract can be easily used appropriately.

[0337] Furthermore, according to this embodiment, contract renewal can be notified.

[0338] Furthermore, according to this embodiment, it is possible to classify the contents of the contracts.

[0339] Furthermore, according to this embodiment, it is possible to score the contract contents.

[0340] Furthermore, according to this embodiment, it is possible to present information that will result in an appropriate contract.

[0341] Furthermore, according to this embodiment, the degree of contribution can be presented using the change in the score for the contract.

[0342] In this embodiment, (1) the process of obtaining contract attribute values ​​from the contract information and storing the contract attribute values ​​together with the contract information and (2) the process of obtaining the score of the contract information may be performed separately and independently.

[0343] A contract processing device that performs only the processing of (1) is, for example, a contract processing device that includes a clue phrase storage unit that stores one or more clue phrases that serve as clues for obtaining contract attribute values, which are attribute values ​​of a contract; a contract reception unit that receives contract information; an attribute value acquisition unit that acquires a contract text from the contract information and uses the one or more clue phrases to acquire from the contract text two or more contract attribute values ​​from the contract text: contract type information, contract counterparty information, contract conclusion date information, contract effectiveness start date information, contract effectiveness end date information, contract automatic renewal information, contract termination notice deadline information, and contract amount information; and an accumulation support unit that performs accumulation support processing to accumulate the two or more contract attribute values.

[0344] In addition, a contract processing device that performs only (2) is, for example, a contract processing device that includes a contract reception unit that receives contract information, a classification unit that analyzes one or more inspection units of the contract text obtained from the contract information and obtains a class indicating whether the contract is disadvantageous or not, a related information acquisition unit that uses the class obtained by the classification unit to obtain related information regarding the class, and a related information output unit that outputs the related information.

[0345] Furthermore, the processing in this embodiment may be implemented by software. This software may be distributed by software download or the like. Furthermore, this software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software implementing the contract processing device 1 in this embodiment is the following program. That is, this program causes, for example, a computer that can access a cue phrase storage unit that stores one or more cue phrases that serve as clues for acquiring contract attribute values, which are attribute values ​​of a contract, to function as a contract reception unit that receives contract information, an attribute value acquisition unit that acquires a contract text from the contract information and acquires, from the contract text using the one or more cue phrases, two or more contract attribute values ​​selected from contract type information, contract counterparty information, contract conclusion date information, contract validity start date information, contract validity end date information, contract automatic renewal information, contract cancellation notice deadline information, and contract amount information, and a storage support unit that performs a storage support process to store the two or more contract attribute values.

[0346] Furthermore, this program is a program for functioning as, for example, a contract reception unit that receives contract information, a classification unit that analyzes one or more inspection units of the contract text obtained from the contract information and obtains a class indicating whether the contract is disadvantageous or not, a related information acquisition unit that uses the class obtained by the classification unit to obtain related information regarding the class, and a related information output unit that outputs the related information.

[0347] 22 shows the appearance of a computer that executes the programs described in this specification to realize the contract processing devices and the like of the various embodiments described above. The above-described embodiments can be realized by computer hardware and a computer program executed thereon. FIG. 22 is an overview of this computer system 300, and FIG. 23 is a block diagram of the system 300.

[0348] In FIG. 22, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

[0349] 23, computer 301 includes, in addition to CD-ROM drive 3012, MPU 3013, bus 3014 connected to CD-ROM drive 3012 etc., ROM 3015 for storing programs such as a boot-up program, RAM 3016 connected to MPU 3013 for temporarily storing instructions of application programs and providing temporary storage space, and hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.

[0350] A program that causes the computer system 300 to execute the functions of the contract processing device 1 of the above-described embodiment may be stored on a CD-ROM 3101, inserted into the CD-ROM drive 3012, and then transferred to the hard disk 3017. Alternatively, the program may be transmitted to the computer 301 via a network (not shown) and stored on the hard disk 3017. The program is loaded into the RAM 3016 when executed. The program may also be loaded directly from the CD-ROM 3101 or the network.

[0351] The program does not necessarily include an operating system (OS) or a third-party program that causes the computer 301 to execute the functions of the contract processing device 1 of the above-described embodiment. The program only needs to include instructions that call appropriate functions (modules) in a controlled manner to achieve the desired results. How the computer system 300 operates is well known, and a detailed description will be omitted.

[0352] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).

[0353] The computer that executes the program may be a single computer or a plurality of computers, that is, it may perform centralized processing or distributed processing.

[0354] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0355] Furthermore, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0356] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0357] As described above, the contract processing device according to the present invention has the effect of facilitating the appropriate management or use of contracts, and is useful as a contract management device, etc. [Explanation of symbols]

[0358] 1. Contract Processing Device 2. Terminal Device 11 Storage area 12 Receiving unit 13 Processing section 14 Transmitter 21 Terminal storage section 22 Terminal Reception 23 Terminal processing section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Unit 111 Handwriting storage section 112 Learning information storage unit 113 Contract information storage unit 114 Score storage 121 Contract Reception Department 122 Search information receiving unit 131 Attribute value acquisition unit 132 Accumulation Support Department 133 Search Department 134 Post-processing section 135 Classification Department 136 Related Information Acquisition Department 141 Related information output section 142 Contract information output section 1341 Notification means 1342 Update method 1343 Explicit means 1361 Single score acquisition method 1362 How to obtain the overall score 1363 Contribution Information Acquisition Method 1364 Recommendation Acquisition Method

Claims

1. a contract acceptance unit that accepts two or more pieces of contract information; a classification unit that performs prediction processing using a machine learning algorithm and a class learning device for each of the two or more pieces of contract information to obtain a class; a related information acquisition unit that acquires related information about the class by using the class acquired by the classification unit; a related information output unit that outputs the related information, The class learner a learning device obtained by performing a learning process using a machine learning algorithm using two or more sets of training data, each set being a pair of a sentence constituting a contract and a class of the sentence; The classification unit Obtain a class for each of one or more inspection units of the contract text of each of the two or more contract information; The related information acquisition unit a comprehensive score acquisition means for acquiring a comprehensive score, which is a score of the two or more contract information, using the two or more classes acquired by the classification unit; The related information output unit A contract processing device that outputs the overall score.

2. The related information acquisition unit a recommendation acquisition means for acquiring recommendation information based on the inspection unit corresponding to the class when the class satisfies a predetermined condition; The related information output unit The contract processing device according to claim 1 , wherein the recommendation information is output.

3. A contract processing method in which all of the processes performed by the contract processing device according to claim 1 or 2 are executed by a computer.

4. Computer, A program for causing the contract processing device according to claim 1 to function as the contract processing device.

Images