Program, method, and information processing apparatus

Abstract

To provide a technique for further facilitating conclusion of contracts in consideration of a risk of failure to determine a person assigned to review.SOLUTION: A program causes a computer processor to execute the steps of: acquiring document data to be reviewed; specifying an attribute of a department of a user who reviews the acquired document data and summarizing the content in the document data to be reviewed by the user in accordance with the specified attribute of the department of the user; and presenting a result summarized in the summary step to the review user.SELECTED DRAWING: Figure 10

Description

[Technical Field]

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

[0002] In conducting business activities, various contracts are concluded and the concluded contracts are managed. Electronic contract services are also used to approve document data between the parties, and the approved document data is managed on the service. For example, there are witness and party-based electronic signature methods.

[0003] Prior to the conclusion of a contract, the terms of the contract are reviewed by the legal department, etc. Patent Document 1 describes a document creation system that aims to "support the creation of documents when risk is taken into consideration," and includes "a selection means for selecting the type of document to be created, a creation means for creating a document according to the selected document type, a risk diagnosis means for diagnosing the risk of the created document, and a display means for displaying the created document in association with the diagnosed risk."

[0004] According to the technology of Patent Document 1, this has the effect of "enabling document creators to easily create documents that take risk into consideration." [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-138746 Summary of the Invention [Problem to be solved by the invention]

[0006] If reviewing contracts is recognized as a primary function within an organization, such as the legal department, it is common practice to request a review.

[0007] On the other hand, there are limits to the scope of what the legal department can review. For example, purchasing costs in sales contracts can affect profits from business activities, so judgment on the business side is important, but departments that have difficulty making such judgments (such as the legal department) may assume that they will review the matter, and there is a risk that the review will not adequately address the risks that should be judged by the person requesting the review.

[0008] Therefore, there is a need for technology that makes it easier for review requesters to enter into contracts while taking into account risks that they cannot fully assess. [Means for solving the problem]

[0009] According to one embodiment of the present disclosure, there is provided a program for operating a computer having a computer processor, the program causing the computer processor to execute the steps of acquiring document data to be reviewed, identifying attributes of the department of a user who will review the acquired document data, and summarizing the content of the document data that the user should review in accordance with the identified attributes of the user's department, and presenting the results summarized in the summarizing step to the reviewing user. [Effects of the Invention]

[0010] According to the present disclosure, it becomes even easier to conclude a contract while taking into consideration risks that the review requester cannot fully assess. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing the configuration of the system 1. [Figure 2] FIG. 2 is a diagram showing the configuration of the server 20. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing the configuration of the terminal 10. As shown in FIG. [Figure 4]FIG. 4 is a diagram showing the data structure of the user database 211. As shown in FIG. [Figure 5] FIG. 5 is a diagram showing the data structure of the fastening management database 212. As shown in FIG. [Figure 6] FIG. 6 is a diagram showing the data structure of the document management database 213. As shown in FIG. [Figure 7] FIG. 7 is a diagram showing the data structure of the review history database 214. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing the data structure of the approval request database 215. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing the flow of processing for summarizing and displaying the contents of a contract according to the attributes of the reader of the contract. [Figure 10] Figure 10 shows an example of an operation screen that supports contract review by summarizing the contents of the contract according to the attributes of the reader of the contract. [Figure 11] FIG. 11 is an example of an operation screen that displays a list of review tasks and advances the workflow as reviews are completed by users in departments other than the legal department. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. The names and functions of the components are also the same. Therefore, detailed descriptions thereof will not be repeated.

[0013] <Outline of embodiment> <1.1 Overall system configuration> FIG. 1 is a diagram showing the configuration of the system 1.

[0014] 1 includes a server 20 for approval application, contract conclusion, and document management services, a user terminal 10, a server 93 for a document review service, a server 94 for a business information provision service, a large-scale language model service server 95, a server 96 for a personnel management service, a server 98 for a legal consultation task service, a server 99 for a budget management service, and a user terminal 10A. These devices are connected to each other via a network 80.

[0015] In the illustrated example, terminals such as terminal 10 and terminal 10A are shown as terminals used by users of the contract conclusion and document management service provided by server 20, and each user operates their own terminal.

[0016] In this embodiment, each device (terminal device, server, etc.) can also be considered as an information processing device. That is, a collection of devices can be considered as one "information processing device," and system 1 can be formed as a collection of multiple devices. The way in which multiple functions required to realize system 1 according to this embodiment are allocated to one or multiple pieces of hardware can be determined appropriately in consideration of the processing capacity of each piece of hardware and / or the specifications required for system 1.

[0017] The terminal 10 is a device operated by a user. The terminal 10 is realized, for example, as follows. · Handheld devices such as smartphones and tablets Desktop PCs (Personal Computers), laptop PCs Wearable devices worn by users (wristwatches, glasses, etc.) The terminal 10 includes a communication IF (Interface) 12 , an input device 13 , an output device 14 , a memory 15 , a storage 16 , and a processor 19 .

[0018] The communication IF 12 is an interface for inputting and outputting signals so that the terminal 10 can communicate with an external device.

[0019] The input device 13 is a device for receiving input operations from a user (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

[0020] The output device 14 is a device (such as a display or speaker) for presenting information to the user.

[0021] The memory 15 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0022] The storage 16 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

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

[0024] Server 20 is a device that provides a service for electronically concluding contracts and a service for managing document data concluded through electronic contracts. In system 1, the contract conclusion service provided by server 20 and the document data management service may be provided by different devices or different businesses. For example, server 20 may provide a document management service and, in addition to data on electronically signed contracts, optically read paper contracts with stamps to extract information such as the contract period and whether the contract is automatically renewed, and manage this information together with the scanned data on the contract as management information. This allows users to be notified when the contract period expires.

[0025] The server 20 is a server that provides services to support operations such as applications for approval in organizations (business companies, etc.) that conduct business activities. The server 20 provides a service to users that enables them to design a workflow for obtaining budget approval among multiple users, for example.

[0026] The server 20 includes a communication IF 22 , an input / output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

[0027] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0028] The input / output IF 23 functions as an interface with an input device for receiving input operations from the user and an output device for presenting information to the user.

[0029] The memory 25 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0030] The storage 26 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

[0031] The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0032] The document review service server 93 is a service that supports document data reviews by accepting document data such as contracts and term sheets that specify contract terms and providing users with information such as whether each clause is favorable or unfavorable to the company, whether there are any missing clauses, and the importance of review items. The document review service server 93 provides a service that supports the above review using a rule base or a trained model. For example, a rule base may be used to review document data by previously associating specific wording or expressions with favorable or unfavorable conditions and explanations. Furthermore, the above review service can be provided by using data obtained by experts reviewing contracts, term sheets, etc. as training data to generate a trained model that responds with review results in response to input document data. The document review service server 93 can also summarize the contents of contracts and generate review comments using a large-scale language model and provide the results to users.

[0033] The business information service server 94 is a service that collects information on organizations and groups such as business companies and provides information related to the credibility of these organizations. Information related to the credibility of organizations is accumulated by collecting publicly available information such as news articles and IR information, and also by the operator of the business information service independently collecting information through interviews, etc. Server 94 provides the following information related to the credibility of organizations. Whether the organization is (or may be) a party that falls under the conditions for contract termination, such as being an anti-social force. For example, there may be publicly available information, such as a database or news article, that indicates that the organization falls under the above conditions. The reputation of a business company or other organization, such as when consumers have a negative reaction and the information is spread in the news, on social media, etc. For example, information may be spread on social media with a certain number of impressions along with negative keywords. Information about business performance, such as sales, revenue (profit amount, profit margin, etc.), and assessment results regarding business continuity (continued losses, possibility of bankruptcy, bond ratings, etc.). The large-scale language model service server 95 is a server that executes language processing tasks using a language model constructed by a learning process including artificial intelligence (AI). An LLM (Large Language Model) is a server that has previously learned a large amount of large-scale data (text data, etc.), for example, web content on the Internet, or a large amount of data stored in a specified database, and can execute various language processing tasks by giving the model a task.

[0034] The large-scale language model service server 95 accepts prompt inputs such as text, images, and voice, and generates and responds to the prompts. Examples of LLMs include GPT-3 and GPT-4 developed by OpenAI, and BERT developed by Google.

[0035] The personnel management service server 96 provides services to support recruitment, labor, and other operations for users such as the personnel department of an organization that conducts business activities. The personnel management service server 96, for example, manages a list of employees, and updates the employee list each time an employee joins or leaves the company. The personnel management service server 96 stores information for managing human resources, such as employee salaries and employee evaluations.

[0036] The legal consultation task service server 98 is a service for departments (such as legal departments) that handle the work of receiving and responding to legal consultations, and imports work requests (such as term sheets and contract reviews) via messaging tools, emails, etc., and enables management of the list as tasks. The legal consultation task service server 98 works in conjunction with the above-mentioned messaging tools, etc., and when a user responds on the legal consultation task service, it posts the response to an external messaging tool, etc.

[0037] The budget management service server 99 provides a service for formulating a budget for business activities and managing actual results against the budget based on deposit and withdrawal data such as invoices. The budget management service server 99 may also be provided as a function in an accounting service that supports accounting work by aggregating invoice data, bank deposit and withdrawal data, etc., and automatically journalizing accounting transactions.

[0038] <1.2 Functional configuration of server 20> 2 is a diagram showing the configuration of the server 20. As shown in FIG. 2, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0039] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0040] The storage unit 202 stores various databases such as a user database 211, a contract management database 212, a document management database 213, a review history database 214, and an approval application database 215.

[0041] The user database 211 is a database for managing users.

[0042] The user database 211 contains information such as the user's name, employee number, etc., for using the services provided by the server 20. Details will be described later.

[0043] The contract conclusion management database 212 is a database that manages the contract conclusion process carried out by the electronic contract service provided by the server 20. Details will be described later.

[0044] The document management database 213 is a database for managing document data, and includes information for managing document data concluded through the electronic contract service provided by the server 20. Details will be described later.

[0045] The review history database 214 is a database that manages the history of reviews of document data such as contracts, etc. Details will be described later.

[0046] The approval request database 215 is a database that manages approval requests for concluding contracts, etc. Details will be described later.

[0047] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. By operating in accordance with the program, the control unit 203 performs functions shown as a reception control module 2041, a transmission control module 2042, a user management module 2043, a conclusion processing module 2044, a document management module 2045, a review content summary module 2046, and an approval application processing module 2047.

[0048] The reception control module 2041 controls the process by which the server 20 receives signals from external devices in accordance with a communication protocol.

[0049] The transmission control module 2042 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0050] The user management module 2043 is a module for managing information about each user who uses the system 1. Specifically, the user management module 2043 accepts registration of information about each user and updates the user database 211.

[0051] The conclusion processing module 2044 controls the process of the parties approving document data as a process for concluding a contract by electronic contract. Specifically, the conclusion processing module 2044 notifies each user who approves the document data, and updates the conclusion management database 212 in response to the operation of approving the document data.

[0052] The document management module 2045 controls the process of managing document data by referring to the document management database 213. Specifically, the document management module 2045 notifies the user whether to renew the contract when the contract period expires, based on the information about the contract period set in the document data, and updates the document management database 213 in response to the user's operation (such as renewal).

[0053] The review content summary module 2046 summarizes and displays the contents of the contract depending on the reader of the contract, as will be described in detail later.

[0054] The approval request processing module 2047 receives an operation to apply for approval from a user and controls the process in which the approver approves the approval. Specifically, the approval request processing module 2047 notifies each user who approves the approval request, and updates the approval request database 215 in response to the operation to approve the approval.

[0055] <1.3 Configuration of Terminal 10> FIG. 3 is a diagram showing the configuration of the terminal 10. As shown in FIG.

[0056] As shown in FIG. 3, the terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units (first communication unit 120, second communication unit 121) corresponding to the respective antennas, an input device 130 (including a touch-sensitive device 131), a display 132, an audio processing unit 140, a microphone 141, a speaker 142, a position information sensor 150, a camera 160, a motion sensor 170, a memory unit 180, and a control unit 190. The terminal 10 also has functions and configurations (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.) that are not specifically shown in FIG. 3. As shown in FIG. 3, the blocks included in the terminal 10 are electrically connected by a bus or the like.

[0057] The antenna 111 emits a signal emitted by the terminal 10 as a radio wave. The antenna 111 also receives a radio wave from space and provides the received signal to the first communication unit 120.

[0058] The antenna 112 emits a signal emitted by the terminal 10 as a radio wave. The antenna 112 also receives a radio wave from space and provides the received signal to the second communication unit 121.

[0059] The first communication unit 120 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 so that the terminal 10 can communicate with other wireless devices. The second communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the terminal 10 can communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are communication modules including a tuner, a received signal strength indicator (RSSI) calculation circuit, a cyclic redundancy check (CRC) calculation circuit, a high-frequency circuit, and the like. The first communication unit 120 and the second communication unit 121 perform modulation / demodulation, frequency conversion, and the like for wireless signals transmitted and received by the terminal 10, and provide the received signals to the control unit 190.

[0060] Input device 130 has a mechanism for accepting input operations by a user. Specifically, input device 130 is configured as a touch screen and includes touch-sensitive device 131. Touch-sensitive device 131 accepts input operations by a user of terminal 10. Touch-sensitive device 131 detects the user's touch position on the touch panel, for example, by using a capacitive touch panel. Touch-sensitive device 131 outputs a signal indicating the user's touch position detected by the touch panel to control unit 190 as an input operation.

[0061] The display 132 displays data such as images, videos, and text under the control of the control unit 190. The display 132 is realized by, for example, an LCD, an organic EL display, or the like.

[0062] The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates a signal provided from the microphone 141 and provides the modulated signal to the control unit 190. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the terminal 10.

[0063] The location information sensor 150 is a sensor that detects the location of the terminal 10, and is, for example, a GPS (Global Positioning System) module. The GPS module is a receiving device used in a satellite positioning system. The satellite positioning system receives signals from at least three or four satellites, and detects the current location of the terminal 10 equipped with the GPS module based on the received signals.

[0064] The camera 160 is a device that receives light with a light receiving element and outputs the received light as a captured image. The camera 160 is, for example, a depth camera that can detect the distance from the camera 160 to a subject being photographed.

[0065] The motion sensor 170 includes an acceleration sensor, an angular velocity sensor, etc., and detects the movement of the terminal 10 .

[0066] The storage unit 180 is configured with, for example, a flash memory, and stores data and programs used by the terminal 10. The various types of information stored in the storage unit 180 will be described later.

[0067] The control unit 190 controls the operation of the terminal 10 by reading a program stored in the storage unit 180 and executing instructions included in the program. The control unit 190 is, for example, an application processor. By operating in accordance with the program, the control unit 190 fulfills the functions of an operation reception unit 191, a transmission / reception unit 192, a data processing unit 193, a notification control unit 194, and a storage control unit 195.

[0068] Operation acceptance unit 191 performs processing to accept a user's input operation to an input device such as touch-sensitive device 131. Operation acceptance unit 191 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation, based on information about the coordinates where the user has touched touch-sensitive device 131 with a finger or the like.

[0069] The transmitting / receiving unit 192 performs processing for the terminal 10 to transmit and receive data to and from an external device such as the server 20 in accordance with a communication protocol.

[0070] The data processing unit 193 performs calculations on the data that the terminal 10 has received as input in accordance with a program, and outputs the calculation results to a memory or the like.

[0071] The notification control unit 194 performs processing for displaying a display image on the display 132, processing for outputting sound from the speaker 142, and processing for generating vibrations.

[0072] The storage control unit 195 controls the storage of data in the storage unit 180 .

[0073] A description will be given of various types of information stored in storage unit 180. In one aspect, storage unit 180 stores various types of information such as user information 181.

[0074] The user information 181 is information about a user who uses the services of the server 20. The user information 181 includes, for example, information such as the employee number and name of the user.

[0075] <2 Data Structure> 4 is a diagram showing the data structure of the user database 211. The user database 211 includes the following items: "User ID," "Business Operator ID," "Name," "Email Address," "Department," "Position," "Date of Employment," "Date of Resignation," and "Qualifications."

[0076] The item "user ID" is information that identifies each user.

[0077] The item "business operator ID" is information that identifies each business operator.

[0078] The item "Name" is information about the user's name.

[0079] The item "email address" is information that serves as the user's contact information.

[0080] The item "department" is information about the user's department.

[0081] Specifically, the item "department" may include the following as information about the department to which the user belongs: - Business departments, sales departments, etc. that do not primarily handle legal affairs Departments that primarily handle legal affairs, such as the legal department and intellectual property department The item "position" is information about the position of the user.

[0082] The item "Date of joining" is information about the date on which a user joined an organization.

[0083] The item "Retirement Date" is information about the date on which the user retired from the organization.

[0084] The item "Qualifications held" is information about qualifications held by the user.

[0085] Specifically, the item "Qualifications held" includes the following information as qualifications held by the user: Qualifications that are expected to give the knowledge to review contracts, such as a lawyer Qualifications that are expected to show knowledge of business activities, such as small and medium-sized enterprise management consultants Qualifications that are expected to have the necessary knowledge in accounting, tax, etc., such as certified public accountants and tax accountants 5 is a diagram showing the data structure of the agreement management database 212. The agreement management database 212 includes an item "agreement ID," an item "sender ID," an item "recipient ID," an item "data to be agreed upon," an item "first email address," an item "second email address," an item "sent date and time," an item "user signature date and time," an item "agreement completion date and time," and an item "status."

[0086] The item "contract ID" is information that identifies each contract conclusion procedure.

[0087] Specifically, the item "Conclusion ID" includes identification information issued by the server 20 when a new registration of a process for concluding an electronic contract by specifying an approver is accepted for document data to be approved by the parties.

[0088] The item "sender ID" is information for identifying the party who will be the sender when the party approves document data.

[0089] Specifically, the item "sender ID" may be associated with information about the business (business ID) or information about the user (user ID) managed in the user database 211.

[0090] The item "recipient ID" is information for identifying the party who will be the recipient when the party approves document data.

[0091] Specifically, the item "Receiver ID" is information that identifies the party designated by the sender's user as the receiver, and like the sender ID, may be associated with information about the business (business ID) or the user (user ID) managed in the user database 211.

[0092] The item "data to be concluded" is document data to be approved by the parties.

[0093] Specifically, the item "data to be concluded" indicates data (files such as PDF) of transaction documents such as contracts, applications, and estimates.

[0094] The item "primary email address" is an email address that serves as a contact point for the user who will be the sender in the process of concluding a contract by approving document data.

[0095] Specifically, the item "first email address" is the email address of the user who performs the operation to send document data as the sender.

[0096] The item "secondary email address" is an email address that serves as the contact address of the user who approves as a recipient in the process of concluding a contract by approving document data.

[0097] Specifically, the item "second email address" is the email address of the user who will approve the document data as the recipient. Note that there may be multiple users who approve the document data among the parties, and if the user who sends the document data specifies the email addresses of multiple users who will approve the document data, the specified email addresses are also managed in the agreement management database 212.

[0098] The item "transmission date and time" is information on the date and time when an operation to transmit document data was accepted from a user who will be the sender in order to request approval of the document data from each user.

[0099] The item "user signature date and time" is information on the date and time when the user performed an operation to approve the document data.

[0100] Specifically, the item "User Signature Date and Time" includes information on the timing when a user who has been requested to approve document data checks the document data, performs an operation to approve, and then digitally signs the document data by having the operation accepted by the server 20. The server 20 digitally signs the document data each time a user performs an operation to approve, and stores the timing information in the agreement management database 212.

[0101] The item "conclusion completion date and time" is information about the date and time when the conclusion of the contract was completed.

[0102] Specifically, when a contract is concluded using the electronic contract service provided by server 20, the item "Date and time of conclusion completion" stores the date and time information in the conclusion management database 212, assuming that the conclusion of the contract is completed when all users designated to approve the document data perform the approval operation.

[0103] The item "status" is information indicating the stage at which the contract conclusion work is currently underway.

[0104] Specifically, the item "status" may include the following as the stage of the contract conclusion process: Before sending: Indicates that the document data has been registered on the server 20 by the sender, but has not yet been sent to the recipient. - In Progress: Indicates that the document data has been sent and approval by each user has not yet been completed. Completed: Indicates that the contract has been concluded Rejected, returned: Indicates that the contract was not completed due to reasons such as the user not approving the document data, or a timeout occurring after a certain period of time had passed without approval being completed. 6 is a diagram showing the data structure of the document management database 213. The document management database 213 includes an item "document management ID," an item "contract ID," an item "document title," an item "contract start date," an item "contract expiration date," and an item "automatic renewal status."

[0105] The item "document management ID" is information for identifying each document data being managed.

[0106] The item "contract ID" is information that identifies each contract conclusion procedure that the parties have performed to approve the document data.

[0107] Specifically, the item "contract ID" may be associated with information (contract ID) that identifies each contract conclusion, which is managed in the contract management database 212.

[0108] The item "document title" is information about the title of the document data being managed.

[0109] Specifically, the item "document title" may be a word used as a type or name of a contract, such as a confidentiality agreement, a sales contract, or a license agreement.

[0110] The item "contract start date" is information indicated as the start date of the contract in the document data.

[0111] Specifically, the value of the item "contract start date" may be set as follows. When the contract is concluded, the server 20 reads the start date of the contract from the contract data. - Information entered by the user as the contract start date The same applies to the following items "Contract Expiration Date" and "Automatic Renewal Enabled."

[0112] The item "contract expiration date" is information indicated as the contract expiration date in the document data.

[0113] The item "automatic renewal" is information indicating whether the contract period is automatically extended (automatic renewal) when the contract period expires in the document data without the parties having to re-enter the contract.

[0114] 7 is a diagram showing the data structure of the review history database 214. The review history database 214 includes an item "review ID," an item "document data," an item "document management ID," an item "review date and time," an item "review user," an item "review content," and an item "review requester's evaluation."

[0115] The item "review ID" is information that identifies each review performed on document data.

[0116] The item "Document Data" is information about the document data to be reviewed.

[0117] The item "document management ID" is information for identifying each document data being managed.

[0118] Specifically, the item "document management ID" may be associated with information (document management ID) that identifies each piece of document data, which is managed in the document management database 213.

[0119] The item "review date and time" is information about the date and time when the review was performed.

[0120] The item "reviewer user" is information about the user who reviewed the item.

[0121] The item "review content" is information indicating the results of the review.

[0122] Specifically, the item "review content" may include the following as review results: - Review results by the document review service server 93 (advantages and disadvantages of the conditions, importance, proposed revisions, etc.) Comments and suggested corrections entered by users (including information about users who enter review comments) The item "rating of review requester" is information indicating the rating of the user who requested the review on the review content of the reviewer.

[0123] Specifically, the item "review requester's evaluation" includes the result of the user who requested the review evaluating the reviewer based on the operation performed on the review result, and the following are possible. The user who requested the review can set a score for the review result. The number of reactions, such as "likes," added to posts sent via messaging tools to contact users for reviews 8 is a diagram showing the data structure of the approval request database 215. The approval request database 215 includes an item "approval request ID," an item "applicant ID," an item "approver ID," an item "application date," an item "approval date," an item "application content," and an item "conclusion ID."

[0124] The item "approval request ID" is information that identifies each approval request.

[0125] The item "Applicant ID" is information that identifies the user who is the applicant for the approval request.

[0126] Specifically, the item "applicant ID" may be associated with user information (user ID) managed in the user database 211.

[0127] The item "Approver ID" is information that identifies the user who approves the approval request.

[0128] Specifically, the item "approver ID" may be associated with user information (user ID) managed in the user database 211.

[0129] The item "application date" is information about the date and time when an operation to transmit the approval request data was accepted from the applicant user in order to request each user to approve the approval request data.

[0130] The item "approval date" is information about the date and time when the user performed an operation to approve the data of the approval request.

[0131] The item "application content" is information indicating the content of the approval request.

[0132] Specifically, the item "application content" includes the content of the approval request, such as: Conclusion of contracts Budget approval Expense claim The item "contract ID" is information that identifies each contract conclusion procedure.

[0133] Specifically, the item "conclusion ID" may be associated with information (conclusion ID) that identifies each contract conclusion procedure, which is managed in the conclusion management database 212. This associates the data of the approval request in the approval request database 215 with the data of the contract conclusion in the conclusion management database 212.

[0134] <3 operations> FIG. 9 is a diagram showing the flow of processing for summarizing and displaying the contents of a contract according to the attributes of the reader of the contract.

[0135] In step S911, the terminal 10 accepts an operation to access the review support service. In the illustrated example, the server 20 provides the review support service.

[0136] In step S921, the server 20 presents the user with an operation screen for acquiring document data to be reviewed.

[0137] In step S913, the terminal 10 accepts an operation to designate document data to be reviewed on the operation screen.

[0138] In step S923, the server 20 identifies the attributes of the department of the user who reviews the acquired document data. Specifically, the server 20 refers to the user database 211 and identifies information such as the user's department, thereby identifying whether the department is a department that does not primarily handle legal affairs (whether it is a department such as the legal department) as an attribute of the reviewing user's department.

[0139] In step S925, the server 20 identifies document data to be compared, which is document data of the same type as the acquired document data to be reviewed and which is document data that has been managed as approved between the parties, by referring to the document management database 213. The server 20 may determine document data of the same type as follows. - Identify documents with the same type as document data - Document data that is the same type of transaction (in the case of purchasing goods, the objects of the transaction are determined to be the same type. For example, parts with different model numbers but the same category) is determined to be the same type of document data. The server 20 compares the document data to be compared with the document data to be reviewed and determines whether the conditions indicated in the document data to be reviewed are outliers compared to the conditions of the document data to be compared. For example, the server 20 may identify the average or median of the contract conditions (e.g., purchase price, period information, etc.) identified as being of the same type of document data, and determine whether the conditions are outliers based on whether the deviation from the conditions of the document data to be reviewed is greater than a certain level. For example, while the legal risk remains the same, there may be business risks, such as whether prices are being excessively reduced in order to achieve forecasts and actual results.

[0140] In step S927, the server 20 summarizes the content of the document data that the user should review, according to the attributes of the identified user's department, and presents the summarized results. The summary can be created, for example, as follows. The attributes of the reviewing user are associated with the clauses or phrases extracted from the contract and stored in advance. This allows you to extract specific clauses from the contract and extract keywords for specific clauses (amount, payment terms, etc.). The text of the contract is used as input, and a prompt including an instruction to summarize according to the user's attributes is sent to the large-scale language model (server 95), causing the large-scale language model to summarize. For example, if the user's department attribute is not the legal department, the reader's attributes may be defined in a prompt so that the large-scale language model can summarize in a way that can be understood by users who are not in the legal department. Also, if the user is in the business department and is a manager, a prompt may be generated to summarize conditions related to business risks (costs, payment methods, etc.), causing the large-scale language model to summarize. If the user's position is used as the user's attribute, and if the user has decision-making authority, the large-scale language model may summarize by outputting the user's contribution to the business.

[0141] For example, when the server 20 identifies the department attribute of the reviewing user as a department that does not primarily handle legal affairs, it summarizes the contents to be reviewed by summarizing the conditions related to sales or expenses, and presents the summarized conditions related to sales or expenses to the reviewing user.

[0142] For example, the server 20 may summarize payment terms as terms related to sales or expenses, and present the summarized payment terms to the user for review.

[0143] As described above, the server 20 generates a summary of the content to be reviewed, and may present the summary to the user by highlighting clauses or keywords in the contract that correspond to the summary of the content to be reviewed (for example, by highlighting only the amount or period), or may present only the summarized content (displaying the summarized content according to the purpose).

[0144] When document data to be compared is identified, the server 20 may inform the user that document data to be compared exists or may present the document data to be compared to the user. For example, the server 20 may present the user with the results of a comparison with past cases (contract terms such as amounts) from concluded contracts. This makes it easier for the user to determine business risks.

[0145] When the server 20 determines whether or not an outlier is present, the server 20 may present the determination result to the user who reviews the data.

[0146] The server 20 may summarize the content to be reviewed by the user by extracting at least one of clauses to be reviewed by the user or specific keywords included in the clauses to be reviewed, according to the attributes of the department of the reviewing user. The server 20 may present at least one of clauses to be reviewed or specific keywords included in the clauses to be reviewed to the reviewing user.

[0147] In step S915, the terminal 10 displays the results summarizing the contents to be reviewed.

[0148] In step S917, the terminal 10 accepts an operation indicating that the user has left a review.

[0149] In step S929, the server 20 stores the document data to be reviewed in the review history database 214 in association with information about the department of the user who performed the review.

[0150] The server 20 presents the attributes of the department of the user who reviewed the document. The attributes of the department of the reviewing user include a department that primarily handles legal affairs and a department that does not primarily handle legal affairs. The server 20 may display the attributes of the department of the reviewing user along with the document data, distinguishing between reviews by a department that primarily handles legal affairs and reviews by a department that does not primarily handle legal affairs. This makes it easy to determine the attributes of the user who reviewed the document data.

[0151] When a user from a department that does not primarily handle legal work is reviewing document data, the server 20 may be configured to enable at least one of the following processes: a request for approval or a contract conclusion process for the document data to be reviewed. This allows a user from a department other than the legal department to start a request for approval for contract conclusion after determining business risks, etc.

[0152] <4 Screen example> Figure 10 shows an example of an operation screen that supports contract review by summarizing the contents of the contract according to the attributes of the reader of the contract.

[0153] A screen 1200 is an operation screen that supports review of a contract.

[0154] The account display area 1210 is an area for displaying information about the account of a user who has logged in to a service provided by the server 20.

[0155] The review support information display area 1230 is an area that displays information summarizing the contents of the contract according to the user's attributes.

[0156] The review target data receiving section 1231 is an operation member that receives, from the user, the designation of data such as a contract to be reviewed.

[0157] The review data receiving unit 1231 corresponds to step S913 etc. In the illustrated example, data is received by specifying a URL, uploading a file, etc. When the server 20 acquires the document data to be reviewed, the server 20 may preview the details of the document data in response to a user operation on the review data receiving unit 1231.

[0158] The summary result display area 1232 is an area where the contents to be reviewed for the data specified by the user are summarized and the summary results are displayed.

[0159] The summary result display area 1232 corresponds to the processing of step S927 and the like.

[0160] As shown in the figure, the detailed display area information 1233 summarizes sales and expense conditions as review items to encourage judgment of business risks since the user is a user in the business division.

[0161] The acquired data viewing acceptance section 1234 is an operation member that accepts an operation to check document data to be reviewed.

[0162] The acquired data viewing acceptance unit 1234 displays the contract data in a preview or the like in response to a user operation.

[0163] The support information display area 1235 is an area that displays information that supports the review based on previously concluded contracts.

[0164] The comparison result display area 1236 is an area for displaying information that supports the determination of business risk by comparing the conditions of similar contracts concluded in the past with the conditions of the document data to be reviewed.

[0165] In the illustrated example, the comparison result display area 1236 displays that the terms of the transaction are outliers compared with the terms of past concluded contracts. This corresponds to the processing of steps S925, S927, etc.

[0166] The detailed display receiving section 1237 is an operation member that receives an operation to display the extracted contracts of the same type that have already been concluded.

[0167] The completion operation receiving section 1239 is an operation member that receives an operation from the user who is performing the review to notify him or her that the review has been completed.

[0168] FIG. 11 is an example of an operation screen that displays a list of review tasks and advances the workflow as reviews are completed by users in departments other than the legal department.

[0169] The task list display area 1250 is an area that displays a list of items (contracts, etc.) that the user is to review.

[0170] In the illustrated example, the task list display area 1250 also displays the status of reviews by other departments, and accepts operations to proceed to workflows such as requesting approval and concluding a contract.

[0171] The progress status display area 1251 is an area that displays the status of the contract to be reviewed being reviewed by each user.

[0172] As shown in the figure, the progress status display area 1251 displays the contract to be reviewed, the review status by each department conducting the review, and information on whether the subsequent workflow such as approval application can be executed. As shown in the figure, the results of reviews conducted by the legal department and the results of reviews conducted by departments other than the legal department are displayed separately.

[0173] The workflow starting unit 1252 is an operation member that accepts an operation to start a workflow for making an approval request.

[0174] In the illustrated example, the workflow starting unit 1252 has completed reviews by both the business department and the legal department, and is ready to start the workflow for approval application. The server 20 starts workflows such as approval application and contract conclusion in response to user operations on the workflow starting unit 1252.

[0175] The workflow starting unit 1253 is an operation member that accepts an operation to start a workflow for making an approval request.

[0176] In the illustrated example, the workflow starting unit 1253 indicates that the review by the legal department has been completed, but the review by the business department has not been completed, so the workflow for the approval request cannot be started. The server 20 does not accept any operations on the workflow starting unit 1253.

[0177] <Modification> In addition to the aspects described in the above embodiment, the following may be adopted.

[0178] In the above embodiment, it has been described that each business provides a service using each device, such as the business support system service server 92, the document review service server 93, the large-scale language model service server 95, and the human resources management service server 96. However, it is also possible for a single business to provide multiple services. For example, it is possible for a single business to provide a contract conclusion service, a document management service, and a business support (approval application) service.

[0179] In the above embodiment, an example of a contract document has been described as the subject of review. However, the review may be conducted in the form of a term sheet that defines the terms of the contract, a document that lists contact information for customers, or transaction documents such as application forms.

[0180] Although several embodiments of the present disclosure have been described above, these embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are intended to be included in the scope of the inventions and their equivalents as defined in the claims, as well as in the scope and spirit of the inventions.

[0181] The functions performed by the components described herein may be implemented in circuitry or processing circuitry, including general-purpose processors, application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), a CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, programmed to perform the described functions. A processor includes transistors and other circuits and is considered to be circuitry or processing circuitry. A processor may also be a programmed processor that executes programs stored in memory.

[0182] In this specification, a circuitry, unit, or means is hardware that is programmed to realize or performs the described functions, which may be any hardware disclosed herein or any hardware known to be programmed to realize or perform the described functions.

[0183] If the hardware is a processor considered to be a type of circuitry, the circuitry, means, or unit is a combination of the hardware and software used to configure the hardware and / or processor.

[0184] <Additional Notes> The matters explained in the above embodiment will be supplemented below.

[0185] (Appendix 1) A program for operating a computer having a computer processor, the program causing the computer processor to execute the steps of acquiring document data to be reviewed, identifying the attributes of the department of a user who will review the acquired document data, and summarizing the content of the document data that the user should review in accordance with the identified attributes of the user's department, and presenting the results summarized in the summarizing step to the user who will review.

[0186] (Appendix 2) A program as described in Appendix 1, in which, in the summarizing step, if the department attributes of the reviewing user are identified as not being a department that primarily handles legal affairs, the program summarizes conditions related to sales or expenses as a summary of the content to be reviewed, and in the presenting step, the program presents the summarized conditions related to sales or expenses to the reviewing user.

[0187] (Appendix 3) 3. The program of claim 2, wherein in the summarizing step, payment terms are summarized as terms related to sales or expenses, and in the presenting step, the summarized payment terms are presented to a user who reviews them.

[0188] (Appendix 4) The program described in any of Appendices 1 to 3 further causes the processor to execute a step of identifying comparison document data that is the same type of document data as the acquired review target document data and is document data that is managed as approved between the parties, and in the presentation step, presents the identified comparison document data to the reviewing user.

[0189] (Appendix 5) The program described in Appendix 4 further causes the processor to execute a step of comparing the document data to be compared with the document data to be reviewed and determining whether the conditions indicated in the document data to be reviewed are an outlier compared with the conditions of the document data to be compared, and in a presentation step, presents the determination result of whether or not the data is an outlier to the user reviewing.

[0190] (Appendix 6) The program according to any one of Appendices 4 to 5, further causing the processor to execute a step of identifying comparison document data that is the same type of document data as the acquired review target document data and is managed as document data that has been approved between the parties, and when the comparison target document data is identified, in a presentation step, presents to the reviewing user that there is comparison target document data.

[0191] (Appendix 7) A program described in any of Appendices 1 to 6, in which in the summarizing step, a summary is made by extracting at least one of the clauses that the reviewing user should review or specific keywords contained in the clauses that should be reviewed as content that the user should review, depending on the attributes of the department of the reviewing user, and in the presenting step, at least one of the clauses that should be reviewed or specific keywords contained in the clauses that should be reviewed is presented to the reviewing user.

[0192] (Appendix 8) The attributes of the department of the reviewing user include a department that primarily handles legal work and a department that does not primarily handle legal work, and the program further causes the processor to execute a step of storing the attributes of the department of the user who reviewed the document data to be reviewed in a memory unit, and in the presentation step, displays the attributes of the department of the user who reviewed the document data to be reviewed, distinguishing between reviews by a department that primarily handles legal work and reviews by a department that does not primarily handle legal work, and displays the attributes of the department of the reviewing user.

[0193] (Appendix 9) A program as described in Appendix 8, which enables at least one of the following processes to be performed on the document data to be reviewed: a request for approval or a contract conclusion process, when the document data to be reviewed is being reviewed by a user from a department that does not primarily handle legal work.

[0194] (Appendix 10) A method operated by a computer having a computer processor, the method comprising the steps of: acquiring document data to be reviewed by the computer processor; identifying attributes of the department of a user who will review the acquired document data; summarizing the content of the document data that the user should review in accordance with the identified attributes of the user's department; and presenting the results summarized in the summarizing step to the reviewing user.

[0195] (Appendix 11) An information processing device having a control unit, wherein the control unit executes the steps of acquiring document data to be reviewed, identifying the attributes of the department of a user who will review the acquired document data, and summarizing the content of the document data that the user should review in accordance with the attributes of the identified department of the user, and presenting the results summarized in the summarizing step to the user who will review.

Claims

1. A program for operating a computer having a computer processor, the program comprising: acquiring document data to be reviewed; a step of identifying an attribute of a department of a user who reviews the acquired document data, and summarizing the content of the document data to be reviewed by the user in accordance with the identified attribute of the department of the user; and presenting the results summarized in the summarizing step to the reviewing user.

2. In the summarizing step, when it is determined that the department of the user to be reviewed is not a department that mainly handles legal affairs, the contents to be reviewed are summarized by summarizing conditions related to sales or expenses; 2. The program according to claim 1, wherein in the presenting step, the summarized conditions relating to the sales or costs are presented to the reviewing user.

3. In the summarizing step, payment terms are summarized as terms related to the sales or expenses; 3. The program of claim 2, wherein the step of presenting presents the summarized payment terms to the reviewing user.

4. The program further causes the processor to Executing a step of identifying document data to be compared, which is document data of the same type as the acquired document data to be reviewed and which is document data that has been approved between the parties; 2. The program according to claim 1, wherein the step of presenting presents the identified document data to be compared to the user who reviews the document data.

5. The program further causes the processor to executing a step of comparing the document data to be compared with the document data to be reviewed, and determining whether a condition indicated in the document data to be reviewed is an outlier compared with a condition of the document data to be compared; 5. The program according to claim 4, wherein the step of presenting the result of the determination as to whether the value is an outlier is presented to the user who reviews the value.

6. The program further causes the processor to Executing a step of identifying document data to be compared, which is document data of the same type as the acquired document data to be reviewed and which is document data that has been approved between the parties; 5. The program according to claim 4, wherein, when the document data to be compared is identified, the presenting step presents the reviewing user with a message that the document data to be compared exists.

7. In the summarizing step, the summarization is performed by extracting, as the content to be reviewed by the user, at least one of clauses to be reviewed by the user or specific keywords included in the clauses to be reviewed, according to the attributes of the department of the reviewing user; 2. The program according to claim 1, wherein in the presenting step, at least one of the clause to be reviewed and a specific keyword included in the clause to be reviewed is presented to the reviewing user.

8. The department attributes of the reviewing users include a department that mainly handles legal affairs and a department that does not mainly handle legal affairs, The program further causes the processor to a step of storing in a storage unit the attributes of the department of the user who reviewed the document data to be reviewed; In the presenting step, an attribute of a department of a user who reviewed the document data to be reviewed is displayed; The program of claim 1, wherein the program displays the attributes of the department of the user who reviewed the document, distinguishing between reviews by a department that primarily handles legal services and reviews by a department that does not primarily handle legal services.

9. The program of claim 8, wherein the storage unit enables at least one of processing a request for approval or processing a contract for the document data to be reviewed when the document data to be reviewed is being reviewed by a user from a department that does not primarily handle legal work.

10. 1. A method for operating a computer having a computer processor, comprising: The method further comprises the steps of: acquiring document data to be reviewed; a step of identifying an attribute of a department of a user who reviews the acquired document data, and summarizing the content of the document data to be reviewed by the user in accordance with the identified attribute of the department of the user; presenting the results summarized in the summarizing step to the reviewing user.

11. An information processing device including a control unit, The control unit acquiring document data to be reviewed; a step of identifying an attribute of a department of a user who reviews the acquired document data, and summarizing the content of the document data to be reviewed by the user in accordance with the identified attribute of the department of the user; and presenting the results summarized in the summarizing step to the reviewing user.

Images