Information processing device, method, and program

Abstract

To provide a technique for making it easier to set transaction conditions according to the circumstances when conducting a transaction. [Solution] A program for operating a computer having one or more computer processors is provided. A storage unit stores information recording the progress of the conclusion of a contract for a project for which a contract has already been concluded between the parties. The program causes the one or more computer processors to execute the steps of summarizing the information recording the progress of the conclusion of the project for which a contract has already been concluded, and presenting the results of summarizing the information recording the progress in the summarizing step and information on the contract terms of the project for which a contract has already been concluded.

Description

[Technical Field]

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

[0002] There are services that help parties conclude transactions and conclude contracts. For example, electronic contract systems eliminate the need for stamps on paper contracts; instead, each user electronically approves the contents of the contract, and the contents of the contract are managed as approved.

[0003] Patent Document 1 addresses the issue that "the actual circumstances, such as the business and background of the other party (corporation, individual, etc.) entering into a contract may not be clear, and these circumstances may constantly change," and describes technology aimed at "further supporting users of electronic contract services." Patent Document 1 describes a program that "acquires performance data on contracts concluded by each user on a contract conclusion platform, which is accumulated on the contract conclusion platform where the parties to the contract accept operations for concluding the contract," "determines the creditworthiness of a first user on the contract conclusion platform based on the performance of contracts concluded in which the first user is a party, based on the performance data," and "presents the identified creditworthiness of the first user to a second user who will enter into a contract with the first user on the contract conclusion platform." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2022-156924 Summary of the Invention [Problem to be solved by the invention]

[0005] When conducting transactions, it is common to refer to the terms and conditions of contracts concluded in previous transactions. However, the terms and conditions of each transaction are often determined based on various circumstances at the time. For example, the transaction price may be set at the discretion of the person in charge at the time. Furthermore, the terms and conditions of each transaction may be determined within various transactions, such as when parties mutually purchase or provide services. Therefore, it is difficult to determine the extent to which terms and conditions from previous transactions can be used as reference. As a result, there is a risk that new transactions will be concluded under inappropriate terms or that transactions will not be promoted. Therefore, there is a need for technology that makes it easier to set transaction terms according to the circumstances.

[0006] An object of the present disclosure is to provide a technology that makes it easier to set transaction conditions according to the circumstances when conducting a transaction. [Means for solving the problem]

[0007] To solve the above problem, a program for operating a computer having one or more computer processors is provided. A storage unit stores information recording the progress of the conclusion of a contract for a project for which a contract has already been concluded between the parties. The program causes the one or more computer processors to execute the steps of summarizing the information recording the progress of the conclusion of the project for which a contract has already been concluded, and presenting the result of summarizing the information recording the progress in the summarizing step and information on the contract terms of the project for which a contract has already been concluded. [Effects of the Invention]

[0008] According to the present disclosure, it is possible to more easily set transaction conditions according to the circumstances. [Brief explanation of the drawings]

[0009] [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 template database 212. As shown in FIG. [Figure 6] FIG. 6 is a diagram showing the data structure of the approval request 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 fastening management database 215. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing the data structure of the document management database 216. As shown in FIG. [Figure 10] FIG. 10 is a diagram showing the data structure of the change target management database 217. As shown in FIG. [Figure 11] FIG. 11 is a diagram showing the flow of processing for identifying a contract template related to a legal amendment or a change in legal interpretation and accepting an operation from a user to edit the identified template. [Figure 12] FIG. 12 is a diagram showing the flow of processing for assigning a label to a contract template. [Figure 13] FIG. 13 is an example of an operation screen that displays the extracted results of contracts identified as being related to legal amendments or changes in legal interpretation, and accepts operations to edit them. [Figure 14] FIG. 14 shows an example of an operation screen that accepts an operation to notify related users about an edited template. [Figure 15] FIG. 15 is a diagram showing the data structure of the case history database 218. [Figure 16] FIG. 16 is a diagram showing the flow of processing for acquiring case history information from various databases, summarizing the acquired information, and updating the case history database 218. [Figure 17]FIG. 17 shows the flow of processing for extracting past cases with similar circumstances leading up to the conclusion of a new contract, and identifying the contract template used in the past case. [Figure 18] FIG. 18 shows an example of an operation screen that presents a contract template. [Figure 19] FIG. 19 shows an example of an operation screen that presents a contract template. [Figure 20] FIG. 20 is a diagram showing the data structure of the case management database 219. As shown in FIG. [Figure 21] FIG. 21 is a diagram showing the flow of processing for summarizing the process of concluding a contract already concluded with an existing customer in connection with a new transaction with the customer, and presenting the summarized results. [Figure 22] Figure 22 shows the process flow for assisting in the decision on whether or not to renew a contract by presenting a summary of past transaction history when managing concluded contracts. [Figure 23] FIG. 23 shows an example of an operation screen that displays a summary of past transactions with an existing customer in connection with a new transaction with the existing customer. [Figure 24] FIG. 24 shows an example of an operation screen that displays a summary of past transaction history when managing concluded contracts. [Figure 25] FIG. 25 is a diagram showing the flow of processing for accepting input of consultation details from the business division to the legal department. [Figure 26] FIG. 26 is a diagram showing the flow of processing for receiving a response from the legal department to a legal consultation from the business department. [Figure 27] FIG. 27 shows an example of an operation screen that accepts input of consultation details from the business division to the legal department. [Figure 28] FIG. 28 shows an example of an operation screen for receiving a response from the legal department to a legal consultation from the business department. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all drawings describing the embodiments, common components are designated by the same reference numerals, and repeated description will be omitted. Note that the following embodiments do not unduly limit the content of the present disclosure described in the claims. Furthermore, not all components shown in the embodiments are necessarily essential components of the present disclosure. Furthermore, each drawing is a schematic diagram and is not necessarily a precise illustration.

[0011] In the following description, a "processor" refers to one or more processors. The at least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may also be another type of processor such as a GPU (Graphics Processing Unit). The at least one processor may be single-core or multi-core.

[0012] Furthermore, the at least one processor may be a processor in the broad sense, such as a hardware circuit (for example, a field-programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) that performs part or all of the processing.

[0013] In the following explanation, information that produces an output for an input may be described using expressions such as "xxx table," but this information may be data of any structure, or may be a learning model such as a neural network that produces an output for an input. Therefore, an "xxx table" may be referred to as "xxx information."

[0014] Furthermore, in the following description, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0015] In addition, in the following explanation, processing may be described using the "program" as the subject, but since a program is executed by a processor to perform specified processing while appropriately using a memory unit and / or an interface unit, etc., the subject of the processing may also be the processor (or a device such as a controller that has that processor).

[0016] The program may be installed in a device such as a computer, or may be stored in, for example, a program distribution server or a computer-readable (e.g., non-transitory) recording medium. Also, in the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0017] Furthermore, in the following description, identification numbers are used as identification information for various objects, but other types of identification information (for example, identifiers including alphabetic characters or symbols) may also be used.

[0018] In addition, in the following description, when describing elements of the same type without distinguishing between them, reference symbols (or common symbols among the reference symbols) may be used, and when describing elements of the same type with distinction between them, the identification numbers (or reference symbols) of the elements may be used.

[0019] In the following description, the control lines and information lines are those that are considered necessary for the description, and do not necessarily represent all the control lines and information lines in the product. All components may be interconnected.

[0020] <Outline of embodiment> The first to fourth embodiments will be described below.

[0021] In the first embodiment, a technology is described that makes it easier to update the content of templates such as contracts managed by businesses in response to changes in legal amendments and legal interpretations, thereby facilitating smoother progress in organizational operations that use templates (drafting and concluding contracts, etc.). In the first embodiment, for example, it becomes easier for users who manage templates to update the content of templates in response to changes in the external environment, regulations, norms, etc., such as legal amendments.

[0022] In the second embodiment, we will explain a technology that makes it even easier to select an appropriate template when carrying out organizational work using templates, as templates for contracts and other documents managed by each business operator are prepared and improved according to their uses and purposes.

[0023] The third embodiment provides a technology that makes it easier for parties to determine whether the terms of a transaction are appropriate when concluding a contract. In individual transactions, transaction conditions, such as the subject matter of the transaction and discounts on the transaction price, may be determined based on various circumstances between the parties. Therefore, when entering into a new transaction, it is not always appropriate to simply follow the content of previous transactions. The third embodiment describes a technology that makes it easier to confirm the background of the case that led to the conclusion of a transaction. This can further promote the conclusion of the transaction and facilitate tasks such as creating a contract that meets the conditions and concluding the contract.

[0024] In the fourth embodiment, a technology that can further facilitate communication during legal consultations will be described. For example, when a business division requests legal consultation from the legal department, the business division staff may find it difficult to explain the background of the transaction to the legal department, which actually handles tasks such as contract drafting and contract review, or the level of explanation may vary significantly depending on the business division staff. Furthermore, the business division staff may not fully understand what information is desirable to provide to the legal department. Meanwhile, even for those providing legal consultations, it may be difficult to determine how to respond to staff from departments that do not routinely handle legal work, and creating a response may be a burden. Therefore, in the fourth embodiment, a technology that facilitates legal consultations between different divisions and makes it easier to achieve the desired goals, such as contract drafting and contract conclusion.

[0025] First Embodiment <1.1 Overall system configuration> FIG. 1 is a diagram showing the configuration of the system 1.

[0026] 1 includes a server 20 for a contract conclusion and document management service, a user terminal 10, a server 92 for a business support system service, a server 93 for a document review service, a server 94 for a law and precedent information service, a server 95 for an artificial intelligence (large-scale language model) service, a server 96 for a conference management service, a server 97 for a sales support system service, a server 98 for a messaging service, and a server 99 for a book browsing service. These devices are connected to each other via a network 80.

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

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

[0029] The server 20 may also be a server that provides services to support operations such as applications for approval in an organization (such as a business company) that conducts 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.

[0030] The terminal 10 is a device operated by a user.

[0031] The server 92 of the business support system service provides users with tools that can be used in the business of the organization. The server 92 of the business support system service provides users with a system for submitting approval requests as part of the business of the organization. The server 92 of the business support system service may communicate with the server 20 to provide the server 20 with data accumulated by the service related to the approval requests.

[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. For example, the document review service server 93 may include in a prompt the document data to be reviewed (such as contract data) and information indicating the review criteria, and instruct the large-scale language model service server 95 to conduct a review in accordance with the review criteria in the prompt, thereby receiving the output result from the large-scale language model service server 95 and generating review comments for the document data. The document review service server 93 may communicate with the server 20 and provide the server 20 with data accumulated by the document review service.

[0033] The server 94 of the law and precedent information service provides a service of storing information related to laws and presenting it to users. The server 94 of the law and precedent information service provides the following to users, for example: An information media that provides accessible articles that serve as references for practical use of contracts, etc. A legal search service that has a legal database and provides legal search results in response to user searches. A case law search service that has a case law database and provides case law search results in response to user searches. For example, the server 94 for the law and precedent information service may be an information medium operated by a business that provides a contract conclusion and document management service (server 20), a document review service (server 93), or the like.

[0034] 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.), such as web content on the Internet, or a large amount of data stored in a specified database, and can execute various language processing tasks by providing the task.

[0035] The artificial intelligence service server 95 (hereinafter sometimes referred to as the "large-scale language model service server 95") accepts prompt inputs in the form of text, images, voice, etc., and generates and responds to the prompts. Examples of LLMs include GPT-3 and GPT-4 developed by OpenAI, and BERT developed by Google.

[0036] The conference management service server 96 provides a service for managing minutes of conferences in organizations that conduct business activities, etc. The conference management service server 96 holds the following information. Information on meeting schedules, participants, etc. Information on agendas and minutes accumulated during meetings For example, the server 96 manages the identification information of an agenda and the contents of the agenda in a database, and also associates and stores the identification information of a meeting (associated with the meeting schedule and participant information) and the minutes information for each agenda in association with the identification information of the agenda. A meeting may proceed with multiple agenda items, and this makes it possible to extract the information on the meeting and the minutes information for each agenda item.

[0037] The conference management service server 96 may be capable of communicating with the server 20 to provide the server 20 with data accumulated by the conference management service.

[0038] The server 97 of the sales support system service provides a service that supports sales activities. The server 97 of the sales support system service provides the following to the user, for example: For each sales project, manage information such as the client, transaction details (amount, transaction object), transaction history (memos, minutes, etc.), and person in charge (your company, the counterparty, etc.) · Provide analysis of sales performance (such as trends in closing rates) for each sales team The server 97 of the sales support system service may communicate with the server 20 to provide the server 20 with data accumulated by the sales support system service.

[0039] The messaging service server 98 provides users with a service for sending and receiving various messages, such as text and files, between users. The service provided by the messaging service server 98 may be a social networking service in which an unspecified number of users participate, or a service in which members of an organization participate, or may provide an email sending and receiving function. Furthermore, users may send and receive messages one-to-one, or multiple users may form a group (sometimes called a channel) and send and receive messages. Each user may be able to post a reply to each user's post in thread format.

[0040] The messaging service server 98 may issue a unique URL for each message posted by each user, so that each user's post can be accessed from other services using the URL.

[0041] The book viewing service server 99 provides a service that allows users to view various electronic books, such as legal books. For example, electronic books can be viewed in accordance with a periodic payment, such as a monthly fee. It is also possible to set a fee for each electronic book and allow users to view the electronic books for which the fee has been paid.

[0042] The book browsing service server 99 may classify and display books. Examples of classification methods include the following. New books Regularly published magazines and books (list of back issues) Classification of books according to business (e.g., contract-related, M&A, reorganization, shareholder meetings, etc.) Classification of books according to jurisdiction (e.g., civil law, commercial law, corporate law, competition law, antitrust law, personal information protection law, etc.) 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.

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

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

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

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

[0047] 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).

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

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

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

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

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

[0053] 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).

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

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

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

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

[0058] The memory unit 202 stores various databases such as a user database 211, a template database 212, an approval application database 213, a review history database 214, a contract management database 215, a document management database 216, a change target management database 217, a case history database 218, and a case management database 219.

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

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

[0061] The template database 212 is a database that manages templates of documents, such as contracts, used in transactions between parties, as will be described in detail later.

[0062] The approval request database 213 is a database that manages approval requests for concluding contracts, etc. For example, the server 20 communicates with the server 92 of the business support system service, acquires information related to approval requests, and updates the approval request database 213. Details will be described later.

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

[0064] The contract conclusion management database 215 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.

[0065] The document management database 216 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.

[0066] The change target management database 217 is a database that manages the change work, the notification work after the change, etc. for the template whose contents are to be changed. Details will be described later.

[0067] The case history database 218 is a database that manages the transaction history of a case, which is a unit of transaction between the parties. Details will be described later.

[0068] The case management database 219 is a database for managing the contents of cases, which are units of transactions between the parties involved. Details will be described later.

[0069] 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 exhibits 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, an approval processing module 2046, an LLM usage module 2047, a review processing module 2048, a template management module 2049, and a summary presentation module 2050.

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

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

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

[0073] 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 215 in response to the operation of approving the document data.

[0074] The document management module 2045 controls the process of managing document data by referring to the document management database 216. 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 216 in response to the user's operation (such as renewal).

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

[0076] The LLM usage module 2047 is a program module that performs processing related to the use of LLM, such as generating prompts to be sent to the large-scale language model service server 95, sending the generated prompts as instructions to the large-scale language model service server 95, receiving results output by the large-scale language model service server 95 in response to the instructions (prompts), and performing processing using the received results.

[0077] The review processing module 2048 records a review of document data to be reviewed (for example, each clause of a contract is the subject of review) and updates the review history database 214. The review processing module 2048 communicates with the document review service server 93 and transmits the document data to be reviewed, causing the server 93 to perform review processing, receives the results, and updates the review history database 214. The review processing module 2048 also accepts an operation to review document data (for example, an operation to input comments associated with the entire contract or each clause of the contract) from the user who is performing the review, and updates the review history database 214.

[0078] The template management module 2049 is a program module that performs processes for managing templates, such as extracting document templates managed in the template database 212 that require content changes and updating the change target management database 217, accepting operations to edit templates, and notifying each user of the edited templates.

[0079] The summary presentation module 2050 is a program module that performs processes such as summarizing the contents of a case and the transaction history of the case using the LLM usage module 2047, updating the case history database 218 and the case management database 219 based on the summary results, and presenting the summary results to each user.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] The data processing unit 193 performs calculations on 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.

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

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

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

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

[0100] <2. Data Structure of the First Embodiment> 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."

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

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

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

[0104] The item "email address" is information that identifies a user and serves as contact information for the user.

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

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

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

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

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

[0110] 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 template database 212. The template database 212 includes the following items: "contract template ID," "contract document type," "contract data," "related law tag," "related issue tag," "link to explanation of related law / issue," "status," "use start time," and "use end time."

[0111] The item “contract template ID” is information that identifies each contract template managed by the server 20.

[0112] The item "contract document type" is information about the type of contract template.

[0113] The item "contract document type" may include contract templates and the like. Typical contract Atypical contracts Term sheet template The item "contract data" is information about a data file of a contract template.

[0114] More specifically, the item "contract data" is a data file in an editable format.

[0115] The item "related law tag" is information on the type of law related to the contract template.

[0116] The item "Related Law Tag" may include the following as types of laws related to the contract template. Information identifying the clauses of the contract template (for example, information on relevant laws and regulations for each clause such as "Article 3" or "Article 4, Paragraph 2") - Information on the relevant laws and regulations for the entire contract (type of contract, such as "confidentiality agreement"). The item "related issue tag" is information on the type of issue related to the contract template.

[0117] The item "Related Issue Tags" may include the following as types of issues related to the contract template: - Information identifying the clauses of the contract template (for example, for each clause such as "Article 3" or "Article 4, Paragraph 2") and information on the relevant issues -Information on relevant issues regarding the entire contract (contract type, such as "non-disclosure agreement") The item "Links to explanations of related laws and issues" is reference information that includes explanations of laws and issues related to the contract.

[0118] The item "Links to explanations of related laws and issues" may include the following as reference information: Link information to books included in the book browsing service provided by the book browsing service server 99. This may include information on links to sections in the books that explain the relevant laws and issues. Links to articles posted on websites that provide legal information Links to explanatory articles about laws and precedents provided by servers such as the Law and Precedent Information Service Links to guidelines, standards, etc. issued by public institutions The item "status" is information on the availability of the contract template.

[0119] The item "status" may include the following information on availability: Currently in use: Can be used as a template Before use: It is prepared as a template, but it is in a state before it can be used. For example, it may become available after a legal change is applied. · Under revision: The template is currently being revised. It may or may not be available as a template. - End of use: Not used as a template. For example, use as a template may be terminated due to the application of legal amendments. The item "use start time" is information about the timing to start using the template.

[0120] The item "End of Use" is information about the timing at which the use of the template will end.

[0121] 6 is a diagram showing the data structure of the approval request database 213. The approval request database 213 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."

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

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

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

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

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

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

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

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

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

[0131] 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 215. This associates the data of the approval request in the approval request database 213 with the data of the contract conclusion in the conclusion management database 215.

[0132] 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."

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

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

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

[0136] 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 216.

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

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

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

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

[0141] 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 agreement management database 215. The agreement management database 215 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."

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

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

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

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

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

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

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

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

[0150] The item "first email address" is information for identifying a user who will be the sender in the process of concluding a contract by approving document data, and is the email address that will be used to contact that user.

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

[0152] The item "secondary email address" is information for identifying a user who approves as a recipient in the process of concluding a contract by approving document data, and is an email address that serves as a contact point for that user.

[0153] 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 215.

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

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

[0156] 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 signing management database 215.

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

[0158] 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 215, assuming that the conclusion of the contract is completed when all users designated to approve the document data perform the approval operation.

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

[0160] 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. 9 is a diagram showing the data structure of the document management database 216. The document management database 216 includes an item "document management ID," an item "contract ID," an item "document title," an item "contract start date," an item "contract expiration date," an item "automatic renewal status," and an item "related parties."

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

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

[0163] 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 215.

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

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

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

[0167] 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."

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

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

[0170] The item "viewing authority" is information about users who are set as having viewing authority for documents (e.g., contracts) managed in the document management database 216. The server 20 may allow users who are set as related parties to a document to view the document, and may not allow users who are not set as related parties to view the document.

[0171] Specifically, the item "viewing authority" may manage the following users as information on related parties of document data: A user who is recorded as a user who approves the document data in the agreement management database 215. Note that the server 20 may identify the person concerned with the document data by referring to the user who approved the document data in the agreement management database 215, without storing the information on the person concerned in the document management database 216. In the contract conclusion service provided by the server 20, in addition to the user who approves the document data, the designated user (the transfer destination user) is accepted as the user to share the document data with once the conclusion is completed. For example, in the case of minutes of a board of directors meeting, a director may approve the document data and share the approved minutes with other users such as executive officers. -Other users designated by users who approve the document data and have the authority to view the document data as parties involved in the document data Furthermore, in the item "viewing authority," information identifying a department or division of an organization, rather than an individual, may be set. For example, information corresponding to the item "division" in the user database 211 may be set. In other words, by specifying the department or division that can view a document, any user in that department or division of the organization can view the document.

[0172] 10 is a diagram showing the data structure of the change target management database 217. The change target management database 217 includes the following items: an item "contract template ID," an item "contract document type," an item "contract data before change," an item "changed contract template," an item "editing status," an item "reflection in template database," an item "editor," an item "change target registration date," an item "editing completion date," an item "change notification recipient," an item "notification status," and an item "notification date."

[0173] The item “contract template ID” is information that identifies each contract template managed by the server 20.

[0174] The item “contract template ID” may be associated with the item “contract template ID” in the template database 212.

[0175] The item "contract document type" is information about the type of contract template.

[0176] The item “contract document type” may be associated with the item “contract document type” in the template database 212 .

[0177] The item "contract data before change" is information about the data file of the contract template that is the target of the change.

[0178] The item "changed contract template" is information about the data file of the template of the contract whose contents have been changed.

[0179] More specifically, the item "changed contract template" is a data file after changes to the template content have been finalized, a data file in which changes to the content are being made, and the like.

[0180] The item "edit status" is information on the status of changes to the template content.

[0181] The item "Editing Status" may include the following as the status of changes to the template content: Not started yet Editing (changes not yet finalized) Editing completed (changes confirmed) The item "reflection in template database" is information on whether or not the registration of the template whose contents have been changed in the template database 212 has been completed.

[0182] The item "reflected in template database" may include the following as a status indicating whether registration in the template database 212 has been completed. Before reflection (the template change is not completed and is not reflected. Or, the template change is completed, but registration in the template database 212 is not yet completed.) · Reflected (Registration of the changed template to the template database 212 has been completed) For example, the server 20 may accept an operation from the user to reflect changes to a template whose changes have been confirmed (item "editing status") in the template database 212 (it may also be possible to accept a specification of when the template will be available), and may add a record of the corresponding template to the template database 212 while setting the item "reflection to template database" to "reflected."

[0183] The item "editor" is information for identifying the user who will be responsible for editing the template to change its contents.

[0184] The item "editor" may be associated with the item "user ID" in the user database 211.

[0185] The item "change target registration date" is information on the timing when the template whose contents are to be changed was registered in the change target management database 217.

[0186] More specifically, the item "Change Target Registration Date" is information on the timing when a record was added to the change target management database 217 by accepting an operation from the user to specify that the contents of a template in the template database 212 are to be changed.

[0187] The item "edit completion date" is information about the timing when the changes to the template content were completed.

[0188] More specifically, the item "editing completion date" is information about the timing at which an operation to finalize the changes to the template was accepted from the user in charge of editing the template.

[0189] The item "contact for notifying changes" is information about the contact person for notifying changes to the template content.

[0190] More specifically, the item "notification destination of change" includes information on the destination of notification of changes to the content of the template, on a user-by-user or department-by-department basis.

[0191] The item "notification status" is information on the status of notification that the contents of the template have been changed.

[0192] The item "Notification Status" may include the following notification statuses: Unnotified (not yet notified) - Notified (notification has been sent to the recipient) The item "notification date" is information about the timing of notification that the contents of the template have been changed.

[0193] More specifically, the item "notification date" is information about the timing of notifying the item "notification recipient of change" that the content of the template has been changed (item "changed contract template"). The server 20 may be configured to accept reservations for notifying changes to the content of the template in advance, and the item "notification date" may include information about the timing of the reservation for notification.

[0194] <3. Operation of the First Embodiment> FIG. 11 is a diagram showing the flow of processing for identifying a contract template related to a legal amendment or a change in legal interpretation and accepting an operation from a user to edit the identified template.

[0195] The server 20 is configured to store one or more contract templates in the storage unit 202 as a template database 212. More specifically, the one or more contract templates are stored in the template database 212 in association with tags related to laws and regulations or issues. The template management module 2049 may associate the tags with the one or more contract templates in the template database 212 by extracting legal terms from at least one of the clause headings or clause bodies of the contract templates, identifying at least one of the laws and regulations or issues corresponding to the extracted legal terms, and storing the tags corresponding to at least one of the identified laws and regulations or issues in association with the contract templates from which the tags were extracted in the storage unit.

[0196] In step S1121, the template management module 2049 of the server 20 acquires information about legal amendments or changes in legal interpretation from the server 94 of the law precedent information provision service, etc. The template management module 2049 acquires information about legal amendments or changes in legal interpretation, by acquiring information about at least one of the laws or issues related to the legal amendments or changes in legal interpretation. For example, the template management module 2049 acquires information about legal amendments or changes in legal interpretation as follows. The system refers to explanatory articles about legal reforms from government agencies, legal books, media, etc., and identifies the laws and regulations mentioned in the explanatory articles. For example, it may extract words that include a word representing a law, such as "·· Law." It may also prompt the large-scale language model service server 95 to summarize the laws and regulations mentioned in the explanatory articles, and receive the output results. · Reference is made to expert commentaries on changes in legal interpretation (e.g., commentaries on legal precedents, commentaries in case law collections, etc.) to identify the issues corresponding to the changes in legal interpretation. For example, the issue may be identified by reference to the title of the commentary. Alternatively, a prompt may be given to the large-scale language model service server 95 to summarize the issues mentioned in the commentary, and the output result may be received.

[0197] In step S1123, the template management module 2049 of the server 20 identifies templates in the template database 212 that have clauses related to legal amendments or changes in legal interpretation.

[0198] The template management module 2049 may identify the above-mentioned template by referring to the template database 212 to identify the contract template associated with the tag corresponding to at least one of the laws and regulations or issues related to the change obtained in step S1121.

[0199] When the template management module 2049 identifies the template as described above, it registers a record in the change target management database 217 as the template to be changed.

[0200] In step S1125, the template management module 2049 of the server 20 refers to the change target management database 217 and presents the template identified in step S1123 to the user.

[0201] The template management module 2049 may present the identified template to the user by identifying keywords that need to be corrected among the clauses of the identified contract template, and displaying the identified keywords that need to be corrected separately from other wording in the body of the identified contract template.

[0202] For example, the template management module 2049 extracts terms contained in the explanatory article, etc. based on the information acquired in step S1121. For example, the template management module 2049 may identify keywords that need to be corrected in each clause of the template as follows. For example, terms that are indicated in explanatory articles and other materials as requiring revision of contract wording. Terms included in the title, headings, etc. of the document (for example, terms emphasized in the title such as "Compliance with the amendment to Article XX of the XX Law") Terms that appear frequently in the document A term included in the result of a response from the large-scale language model service server 95 based on an instruction to extract keywords from the document that need to be revised in response to legal amendments. As described above, the template management module 2049 extracts terms (or legal terms) based on the acquired information to identify keywords in each clause of the template that need to be revised. This makes it easier for users who edit templates in accordance with legal amendments or changes in legal interpretation to check the revisions that need to be made, further encouraging them to update their templates.

[0203] The template management module 2049 may present the identified template to the user, identify clauses in the identified contract template that require amendment, generate proposed amendments for the identified clauses that require amendment, and present the generated proposed amendments.

[0204] Here, the template management module 2049 may generate a proposed amendment for a clause that needs to be amended as follows. Instruct the server 95 of the large-scale language model service to create amendments to each clause based on the specified template clauses and articles related to legal amendments and changes in legal interpretation, and receive the amendments output by the server 95 of the large-scale language model service in response to the instructions. In step S1121, the acquisition of information regarding the amendment of law or the change in legal interpretation may be achieved by acquiring information on a commentary on the amendment of law or the change in legal interpretation. The template management module 2049 may generate an amendment proposal and present the generated amendment proposal by acquiring a sample amendment proposal from information on a commentary on the amendment of law or the change in legal interpretation and presenting the acquired amendment proposal. In this way, when the server 94 of the legal precedent information provision service provides a sample of an amendment proposal to a clause based on an amendment of law or a change in legal interpretation, the sample is acquired as an amendment proposal. The template management module 2049 updates the change target management database 217 based on the revision proposal generated as described above.

[0205] Here, the storage unit 202 may be configured to store one or more templates of evidence such as invoices, estimates, etc.

[0206] In step S1123, the template management module 2049 may identify a template of the voucher that needs to be revised in accordance with the legal amendment or change in legal interpretation. The template management module 2049 may present the identified template of the voucher.

[0207] In step S1111, the terminal 10 presents templates that need to be revised due to legal amendments or changes in legal interpretation. The terminal 10 accepts an operation to edit the template from the user and transmits the edited content of the user to the server 20.

[0208] In step S1127, the server 20 updates the template database 212 and the change target management database 217 in response to the operation to edit the identified template.

[0209] FIG. 12 is a diagram showing the flow of processing for assigning a label to a contract template.

[0210] In step S1221, the template management module 2049 of the server 20 refers to the change target management database 217 and identifies the notification destination of the information on the template for which the change has been completed. The server 20 may update the change target management database 217 regarding the notification destination information by accepting a designation from the user who edits the template, or may hold information on a user or department that has access authority to the template to be changed in the change target management database 217 as the notification destination.

[0211] In step S1223, the template management module 2049 of the server 20 refers to the change target management database 217 and notifies the relevant users (notification recipients) of the template changes and information about the modified templates for templates affected by the legal amendment or change in legal interpretation.

[0212] The template management module 2049 references the change target management database 217 as the notification destination, and notifies each user who can use the one or more contract templates of the template identified in step S1123 from among the one or more contract templates stored in the template database 212, and information on the modifications to be made to each clause of the identified template. The template management module 2049 may also notify each user who can use the template of information on a template that requires modification before the modification is completed. This allows users who use the template to know in advance that changes will be made to the template, and may enable smooth business operations before and after the template is modified.

[0213] The template management module 2049 may refer to the change target management database 217 and accept modifications to all templates identified in step S1123 in response to the legal amendments or changes in legal interpretation, and then notify each user who can use the one or more contract templates that the modifications to the templates have been completed.

[0214] In step S1211, the terminal 10 displays to the user or the like who uses the template the content of the modifications to the template that will be affected by the amendment to the law or the change in legal interpretation, and information about the modified template.

[0215] In step S1225, the template management module 2049 of the server 20 updates the template database 212 so that, when the time comes for the template to be applied, the revised version of the template is made available to each user, while the pre-revised version is not available to each user.

[0216] At least one of the template database 212 and the change target management database 217 is configured to store, for the one or more contract templates, versions amended due to the legal amendment or change in legal interpretation and versions before the amendment. The template management module 2049 may acquire information on the time when the legal amendment or change in legal interpretation will apply in step S1121. For example, the time when laws and regulations will apply is described in explanatory articles about the legal amendment or legal interpretation and in materials from public institutions. Furthermore, commentaries on legal precedents, etc., describe the date of court decisions regarding changes in legal interpretation. The template management module 2049 may acquire the above-mentioned time information by reading this information on the time. When the time when the one or more contract templates stored in the storage unit will apply arrives, the template management module 2049 may make the versions amended due to the legal amendment or change in legal interpretation available to each user, while controlling the versions before the amendment so that each user cannot use them.

[0217] <4. Screen Examples of the First Embodiment> FIG. 13 is an example of an operation screen that displays the extracted results of contracts identified as being related to legal amendments or changes in legal interpretation, and accepts operations to edit them.

[0218] The operation screen 1300 is an operation screen for accepting operations for managing templates.

[0219] The account display area 1302 is an area for displaying information about a user who logs in to use a service provided by the server 20 .

[0220] In the illustrated example, the account display area 1302 displays the user's name and department information.

[0221] The template list display area 1304 is an area for displaying a list of templates that need to be edited due to legal amendments or changes in legal interpretation.

[0222] The template list display area 1304 corresponds to the processing of steps S1125, S1111, etc. in FIG.

[0223] The confirmation operation unit 1306 is an operation member that accepts an operation to confirm the content of the legal amendment or change in legal interpretation.

[0224] The confirmation operation unit 1306 may accept an operation to confirm the content of the legal amendment or change in legal interpretation, which may include the following. - Operations to refer to articles, materials, amendments to clauses, etc., related to legal precedent information service servers 94, government agencies, etc., that provide explanatory articles, materials, amendments to clauses, etc., related to legal amendments or changes in legal interpretations. The change target display area 1308 is an area that displays templates that have been identified as needing editing due to changes in law or legal interpretation.

[0225] In the illustrated example, the change target display area 1308 displays the template type, file name, and the update status of the template clauses (in the illustrated example, the status is "not started"). In the example of Fig. 13, in response to a user's operation on the change target display areas 1308 and 1310, the content of the corresponding template may be confirmed and a transition may be made to a screen for editing each clause.

[0226] The change target display area 1310 is an area that displays templates that have been identified as needing editing due to changes in law or legal interpretation.

[0227] In the illustrated example, the change target display area 1310 displays the template type, file name, and template clause update status (in the illustrated example, the status is "editing completed"), similar to the change target display area 1308. In the example of Fig. 13, in response to a user's operation on the change target display areas 1308 and 1310, the content of the corresponding template may be confirmed and a transition may be made to a screen for editing each clause.

[0228] In this way, by displaying a list of identified templates along with the status of editing of the template clauses, the person in charge of updating the templates can easily understand the work that needs to be done, which may encourage them to update the templates.

[0229] In the example of Figure 14, a template whose changes have been completed (status is "editing completed") is displayed, and depending on the user's operation, the text of the template whose changes have been completed can be viewed, but editing cannot be accepted.

[0230] The impact rate display area 1312 is an area that displays information about the rate of templates that need to be updated due to legal amendments or changes in legal interpretation.

[0231] In the illustrated example, the impact ratio display area 1312 displays the total number of managed templates, the number of templates that need to be edited because they will be affected by the legal amendment or change in legal interpretation, and information on the percentage of those affected. This makes it easier to understand the approximate amount of work required to complete the template changes, and can encourage template updates.

[0232] The update deadline display area 1314 is an area that displays the deadline for completing confirmation and editing of the contents of templates that are affected by legal amendments or changes in legal interpretation.

[0233] In the illustrated example, a deadline for reviewing affected templates (such as updating clauses) based on the timing of the legal amendment is set and the set deadline is displayed in the update deadline display area 1314. This makes it possible to display on the screen the time when the template changes must be completed together with information from the above-mentioned change target display area 1310, impact rate display area 1312, etc., which may make it easier to plan the work of editing templates.

[0234] The conclusion status display area 1316 is an area that displays the past record of contract conclusion based on templates that are affected by legal amendments or changes in legal interpretation.

[0235] In the illustrated example, the conclusion status display area 1316 compares the affected template with the contracts managed as already concluded in the document management database 216, and displays the actual number of contracts that have been concluded using contracts created based on the template (for example, contracts concluded using the template for each clause, contracts in which the degree of agreement between the clauses of the concluded contract and the clauses of the template is above a certain percentage, etc.). This makes it easier to understand the extent to which updating the template will affect business operations, such as the extent to which a contract needs to be re-concluded or to warn existing business partners to use the updated template in new transactions, and makes it easier to take action in advance.

[0236] The approval request / review status display area 1318 is an area that displays the past record of contract reviews and approval request applications based on templates that are affected by legal amendments or changes in legal interpretation.

[0237] In the illustrated example, the approval / review status display area 1318 compares the affected template with the contracts managed in the approval request database 213 and the review history database 214, and displays the number of reviews or approval requests made for contracts created based on the template (for example, contracts concluded using the template for each clause, contracts in which the degree of match between each clause of the concluded contract and each clause of the template is above a certain percentage, etc.). This makes it possible to edit the template displayed in the change target display area 1308, etc., while referring to the past use history of the template, making the operation easier.

[0238] The affected department confirmation operation unit 1320 is an operation member that accepts an operation to confirm the department that will be affected by the change of the template.

[0239] In the illustrated example, the affected department confirmation operation unit 1320, in response to a user operation, displays information about the departments that are the notification destinations in the change target management database 217. As illustrated, information about the affected departments may be displayed for each template.

[0240] The database update operation section 1322 is an operation member that accepts an operation to confirm the edited content of a template that has been edited.

[0241] In the illustrated example, the database update operation unit 1322 registers a template with a status of "editing completed" in the template database 212 in response to a user operation.

[0242] FIG. 14 shows an example of an operation screen that accepts an operation to notify related users about an edited template.

[0243] The notification operation screen 1324 is an operation screen for accepting an operation to notify that a template has been corrected.

[0244] The list display area 1326 is an area for displaying a list of modified templates.

[0245] The affected department operation section 1328 is an operation member that accepts an operation to confirm the department that will be affected by the change in the contents of the template.

[0246] The affected department operation unit 1328 displays information about departments that will be affected by changes to the template content in response to user operations, and may include the following. Regarding the template for the content change, the departments managed as notification destinations in the change target management database 217 A user or a department to which the user belongs in the case where a request for approval (approval request database 213), a review (review history database 214), a contract conclusion (conclusion management database 215), or management of a concluded contract (document management database 216) has been carried out using a contract created based on a template for content changes. This allows the extent of the impact to be understood when notifying that the contents of the template have been changed, and allows work to be carried out in anticipation of inquiries, etc.

[0247] The notification destination confirmation operation section 1330 is an operation member that accepts an operation to confirm a notification destination to be notified that the contents of the template have been changed.

[0248] In the illustrated example, the notification destination confirmation operation unit 1330 refers to the change target management database 217 in response to a user operation, and displays the notification destination for each template whose contents have been changed.

[0249] The notification content display area 1332 is an area for displaying the content of the notification to the notification destination.

[0250] In the illustrated example, notification content display area 1332 accepts registration of the content to be notified to the notification recipient from the user in charge of notification or the user who edited the template, etc., and displays the accepted notification content. In addition, the notification content may be registered by issuing an instruction to have server 95 of the large-scale language model service summarize the changes to the contract template (which may also include an instruction to write this as the notification content) and receiving the output result.

[0251] The application time display area 1334 is an area that displays the time when the template with the changed content will be available to each user.

[0252] In the illustrated example, the application time display area 1334 displays, for example, information managed in the template database 212 as the item "use start time."

[0253] The notification operation section 1336 is an operation member that accepts an operation to notify the notification destination of a change in the content of the template based on each content displayed in the list display area 1326.

[0254] The notification operation unit 1336 corresponds to step S1223 in FIG.

[0255] <Summary of the First Embodiment> <Second embodiment> <5. Data Structure of the Second Embodiment> 15 is a diagram showing the data structure of the case history database 218. The case history database 218 includes an item "case history ID," an item "customer," an item "transaction target," an item "approval application ID," an item "conclusion ID," an item "minutes," an item "sales support tool log," an item "messaging tool log," an item "contract template used," an item "progress summary," an item "transaction completion date," and an item "status."

[0256] The item "case history ID" is information that identifies each piece of case history information.

[0257] The item "Customer" is information that identifies each customer in the case.

[0258] The item "Customer" may be associated with the item "Business ID" in the user database 211.

[0259] The item "transaction object" is information about the type of object involved in a transaction with a business partner.

[0260] More specifically, the item "transaction object" is information on goods, services, etc. that are the object of the transaction.

[0261] The item "approval request ID" is information that identifies the approval request related to the transaction.

[0262] The item “approval request ID” may be associated with the item “approval request ID” of the approval request database 213.

[0263] The item "contract ID" is information for identifying the contract conclusion relating to the transaction.

[0264] The item “contract ID” may be associated with the item “contract ID” of the contract management database 215 .

[0265] The item "minutes" is information on the minutes of the transaction.

[0266] The item "minutes" may include the following information about the minutes: - Data files related to the minutes themselves Link to the data file for the minutes Links to data in each service provided by the conference management service server 96, etc. (for example, the service may issue a unique URL for accessing posted content and data stored in a database) The item "sales support tool log" is information on a log that is accumulated in the server 97 of the sales support system service and records the details of the transaction.

[0267] More specifically, the item "Sales Support Tool Log" may be the data itself when the server 20 imports data managed by the server 97 of the sales support system service, or it may be a unique URL issued by the server 97 to access the data (information on the history of the transaction) that the server 97 holds in its database.

[0268] The item "messaging tool log" is information on messages stored in the messaging service server 98 that record the details of the transaction.

[0269] More specifically, the item "Messaging Tool Log" is either a link to data in each service provided by a messaging service server 98 or the like (for example, the service may issue a unique URL for accessing the posted content or data stored in a database), or the message data itself that server 20 obtains by establishing a communication connection with server 98.

[0270] The item "contract template used" is information that identifies the template used to create documents (contracts) related to transactions in a case.

[0271] The item “contract template used” may be associated with the item “contract template ID” in the template database 212.

[0272] The item "Progress Summary" is information resulting from summarizing information on the transaction history of a case, which is stored in each service.

[0273] More specifically, the item "Progress Summary" is information about the transaction history of a case that is accumulated in each service (item "Minutes of Meeting," item "Sales Support Tool Log," item "Messaging Tool Log," etc.), and is the output result information of the large-scale language model service server 95 in response to a prompt to summarize this information.

[0274] The item "transaction completion date" is information about the timing when the transaction related to the matter was completed.

[0275] More specifically, the item "Transaction Completion Date" is information on the timing at which the transaction was completed, i.e., when the contract was concluded (conclusion was completed in the conclusion management database 215) and when deposits and withdrawals related to the transaction were made.

[0276] The item "status" is information about the status of the transaction.

[0277] The item "status" may include the following as information on the status of the transaction: -Closed upon successful transaction -Deal not concluded and closed Each stage leading up to the conclusion of a contract (contract drafting, approval application, review, etc.) <6. Operation of the Second Embodiment> FIG. 16 is a diagram showing the flow of processing for acquiring case history information from various databases, summarizing the acquired information, and updating the case history database 218.

[0278] In step S1621, the template management module 2049 of the server 20 refers to the case history database 218 and acquires progress information for concluded cases for which contract conclusion has been completed from external tools such as the conference management service server 96, the sales support system service server 97, and the messaging service server 98. For example, the user may specify the progress information for each case that is managed in these external tools, causing the server 20 to acquire this progress information.

[0279] In this way, the server 20 stores information recording the process of concluding a contract for a case in which the parties have already concluded the contract in the case history database 218. The server 20 is also configured to store one or more contract templates in the template database 212.

[0280] Server 20 stores information on meeting minutes as information recording the progress of a case in case history database 218. The information on meeting minutes stored in case history database 218 may be at least either data on meeting minutes stored by a user of a first service that is a service that manages meeting minutes (conference management service server 96), or data on a document created in a second service that provides a cloud-based document creation tool.

[0281] In addition, the information recording the progress stored in the case history database 218 may be data recording sales activities for each case stored by a user of a third service (server 97 of the sales support system service) that provides sales support tools.

[0282] In addition, the information recording the progress stored in the case history database 218 may be a history of email sending and receiving or a history of message sending and receiving stored by a user of a fourth service that provides a messaging function (messaging service server 98).

[0283] Furthermore, the information recording the progress stored in the case history database 218 may be data on approval requests sent and received in the approval request service (server 92 of the business support system service).

[0284] In addition, the server 20 may store in the document management database 216, for projects for which a contract has already been concluded between the parties, information on the contract for the project or a term sheet defining the contract terms, in association with the project.

[0285] In step S1623, the summary presentation module 2050 of the server 20 refers to the case history database 218 and sends an instruction to the large-scale language model service server 95 to summarize the information recording the progress of the concluded case.

[0286] In step S1625, the summary presentation module 2050 of the server 20 receives the output result of the large-scale language model service server 95 and updates the case history database 218.

[0287] In this way, the summary presentation module 2050 summarizes the information recording the process of the conclusion of each case, which is accumulated in the case history database 218, and stores the summarized first summary result in the case history database 218. Here, the summary presentation module 2050 may obtain the first summary result by instructing the large-scale language model service server 95 to summarize the information recording the process of the conclusion of each case.

[0288] In this way, the transaction progress can be summarized for projects for which a contract has already been concluded.

[0289] FIG. 17 shows the flow of processing for extracting past cases with similar circumstances leading up to the conclusion of a new contract, and identifying the contract template used in the past case.

[0290] In step S1721, the template management module 2049 of the server 20 presents an operation screen for creating a contract for a project to the user of the terminal 10. The operation screen may be configured to accept an operation for searching for and selecting a template for the contract.

[0291] In step S1711, the terminal 10 accepts an operation to register progress information of a case from the user. For example, the terminal 10 registers progress information of a case related to a new transaction on an operation screen from the user. For example, the operation screen may accept input of progress information of a new transaction (for which a contract is about to be concluded), or may set a link (for example, a unique URL issued by these services) to data stored in the conference management service server 96, the messaging service server 98, etc., regarding the progress information of the transaction.

[0292] In step S1723, the template management module 2049 of the server 20 obtains information on the progress of the case in which a new contract is to be concluded between the parties by referring to an external tool, accepting input from the user, etc., and updates the case history database 218.

[0293] In step S1725, the template management module 2049 of the server 20 transmits, via the LLM usage module 2047, an instruction to the large-scale language model service server 95 to summarize progress information (information obtained from the case history database 218 as links to various services, etc.) for a case in which a new contract is to be concluded between the parties. The instruction to summarize is a prompt that includes an instruction to summarize the progress information in a predetermined number of characters or less.

[0294] In step S1727, the template management module 2049 of the server 20 receives the output result of the large-scale language model service server 95 through the processing of the LLM usage module 2047, and updates the case history database 218.

[0295] In this way, the template management module 2049 may summarize the progress information of a case in which a new contract is to be concluded between the parties, and store the summarized second summary result in the case history database 218. The template management module 2049 may obtain the second summary result by instructing the large-scale language model service server 95 to summarize the progress information of the case in which a new contract is to be concluded between the parties. In step S1729, the template management module 2049 of the server 20 refers to the case history database 218, compares information summarizing the progress of cases that have already been concluded with information summarizing the progress of cases for which a new contract is to be concluded, determines the degree of similarity, and extracts information about cases that have already been concluded based on the results of the determination.

[0296] In this way, the template management module 2049 extracts information on cases that have already been concluded that is similar to the progress information of the case for which a new contract is being concluded between the parties, based on information on the progress of the case and information recording the progress stored in the memory unit.

[0297] Here, the template management module 2049 may extract information about the already concluded project by referring to information about the minutes of the meeting in the change target management database 217. The template management module 2049 may extract information about the already concluded project based on data about the minutes of the already concluded project that is searched for in the first service (see step S1621) as having similar progress information, or data about documents about the already concluded project that is searched for in the second service (see step S1621) as having similar progress information. In this way, information about the already concluded project may be extracted based on the results of a search for similar projects in an external service.

[0298] The template management module 2049 may extract information on the already concluded cases based on the data of the sales activity records that are searched for as having similar progress information in the third service (see step S1621).

[0299] The template management module 2049 may also extract information about the already concluded cases that are searched for as having similar email sending and receiving history or similar messages sent and received in the fourth service (see step S1621).

[0300] The template management module 2049 may extract information on the already concluded cases that are similar to the data of the approval request.

[0301] The template management module 2049 may refer to the case history database 218 and extract information on similar cases that have already been concluded by comparing the first summary result (step S1625) and the second summary result (step S1727) for each case.

[0302] The template management module 2049 may perform the following operations: acquiring at least one of the contract type of the contract for the new project to be concluded between the parties or a term sheet defining the contract terms; determining the degree of match between the acquired contract type or at least one of the term sheet and the contracts or term sheets for each of the projects for which contracts have already been concluded and stored in the document management database 216; and extracting the projects for which contracts have already been concluded that are determined to have a high degree of match.

[0303] In step S1731, the template management module 2049 of the server 20 refers to the case history database 218 and identifies the template of the contract used in the extracted concluded case.

[0304] The template management module 2049 may identify a contract template by comparing the extracted contract used in the concluded case with one or more contract templates stored in the template database 212, and identifying a template that has a high degree of match.

[0305] In the case history database 218, information on the template that serves as the basis for the contract concluded for each case is associated and stored, and the template management module 2049 may identify the template information that is associated with the extracted concluded case.

[0306] In step S1733, the server 20 presents the identified contract template to the user.

[0307] The server 20 stores information recording the progress of the conclusion of a contract in a case history database 218 as the user uses a predetermined service. The template management module 2049 extracts information on the already concluded contract based on the information stored in the predetermined service. The template management module 2049 may output information on the identified contract template for the predetermined service, thereby causing the user to see the contract template information on the operation screen of the predetermined service.

[0308] Furthermore, the template management module 2049 may accept the designation of the specified service on an operation screen that accepts searches for the one or more contract templates stored in the template database 212, and display information on the already concluded case that has been extracted based on information recording the process of the conclusion that is accumulated in the specified specified service, and may also display information on the contract template that was used in the extracted already concluded case.

[0309] In step S1713, the terminal 10 displays the template of the contract used in the extracted concluded case.

[0310] <7 Screen Examples of the Second Embodiment> FIG. 18 shows an example of an operation screen that presents a contract template.

[0311] The sales management operation screen 1800 is an operation screen for a service (sales management service in the illustrated example) different from the service for managing contract templates (a service provided by the server 20).

[0312] In the illustrated example, the sales management operation screen 1800 communicates with the server 20 to display information managed by the server 20 on the operation screen.

[0313] The account display area 1802 is an area that displays the user's account in the sales management service.

[0314] The case display area 1804 is an area for displaying information about a case, which is a unit of a transaction related to sales.

[0315] The summary display area 1806 is an area where a summary of the case is displayed.

[0316] The summary display area 1806 displays a summary of the case, which may include: ·Business partners Transaction details (transaction target, quantity, etc.) ·status - Estimated date of transaction completion Transaction amount ·manager The details display area 1808 is an area where the details of the case are displayed.

[0317] The details display area 1808 displays the details of the case, which may include: Sales activity history (including sales activity records written by personnel) The external cooperation tool display area 1810 is an area that displays information about other services that are connected to the sales management service.

[0318] More specifically, the external cooperation tool display area 1810 is an area that connects to a contract management service provided by the server 20 as another service and displays information received from the contract management service. In the illustrated example, other cases with similar transaction histories are extracted for the case shown in the summary display area 1806, and the information on the contract templates used in those other cases is displayed as a result of receiving it from the server 20. This corresponds to the processing of steps S1731, S1733, S1713, etc. in FIG. 17.

[0319] The extracted matter display area 1812 is an area for displaying an outline of a matter for which a contract has been concluded and which has been extracted as being similar to the matter to be newly transacted.

[0320] The extracted case display area 1812 corresponds to steps S1731, S1733, S1713, etc. in FIG.

[0321] The template display area 1814 is an area for displaying templates that have been extracted as having similar transaction history and have been used in cases for which a contract has already been concluded.

[0322] In the example shown, the template display area 1814 displays the results of a query to the server 20 regarding information on the contract template used in a case with a similar transaction history, by referring to the case history database 218.

[0323] The concluded contract display area 1816 is an area for displaying the concluded contract for a case that has already been concluded and that has been extracted as having a similar transaction history.

[0324] In the example shown, the concluded contract display area 1816 displays the results of a query to the server 20 for information on the contract concluded in a case with a similar transaction history, by referring to the case history database 218.

[0325] FIG. 19 shows an example of an operation screen that presents a contract template.

[0326] The contract conclusion / document management operation screen 1900 is an operation screen for accepting operations in the services (contract conclusion, document management services) provided by the server 20.

[0327] The account display area 1902 is an area for displaying the accounts of users who use the services provided by the server 20.

[0328] The template display area 1904 is an area that displays the template of the contract to be used in the case in response to a user operation.

[0329] The search operation section 1906 is an operation member that accepts an operation to designate a search key (for example, free text) for templates that the server 20 manages in the template database 212.

[0330] In the illustrated example, the search operation unit 1906 accepts a search key input from the user, and accepts an operation to search for templates of each contract managed in the template database 212 according to the search key.

[0331] The other case operation section 1908 is an operation member that accepts an operation to specify a service different from the service provided by the server 20 and extract another case having a similar transaction history.

[0332] More specifically, the other case operation unit 1908 connects to these services by accepting operations that specify each service, such as the conference management service server 96, the sales support system service server 97, the messaging service server 98, and the business support system service server 92.

[0333] The conference management service designation section 1910 is an operation member that accepts the designation of the server 96 for the conference management service.

[0334] In the illustrated example, the conference management service designation unit 1910 may specify other cases with similar transaction histories by having the server 20 connect to the conference management service server 96 in response to a user operation, reading in case information, and registering the information in the case history database 218. Specifying cases with similar histories may involve specifying other cases with similar transaction histories on the services provided by the server 96, or it may involve importing data from various services into the case history database 218 (for example, the user obtaining links to information stored in the various services and registering it in the server 20), and then comparing the results of summarizing the transaction histories to specify other similar cases.

[0335] The sales support service designation section 1912 is an operation member that accepts the designation of the server 97 of the sales support system service.

[0336] In the example shown in the figure, the sales support service designation unit 1912 may connect the server 20 to the sales support system service server 97 in response to user operation, read the case information, register the information in the case history database 218, and identify other cases with similar transaction histories.

[0337] The messaging service designation section 1914 is an operation member that accepts the designation of the server 98 of the messaging service.

[0338] In the illustrated example, the messaging service designation unit 1914 may cause the server 20 to connect to the messaging service server 98 in response to user operation, read the case information, register the information in the case history database 218, and identify other cases with similar transaction histories.

[0339] The workflow service designation section 1916 is an operation member that accepts the designation of the server 92 for the business support system service.

[0340] In the illustrated example, the workflow service designation unit 1916 may connect the server 20 to the business support system service server 92 in response to user operation, read the case information, register the information in the case history database 218, and identify other cases with similar transaction histories.

[0341] The similar case display area 1918 is an area where the server 20 has identified other cases with similar transaction histories by referring to case data stored in other services, and displays the contract templates used in the identified other cases and the concluded contracts.

[0342] The case summary display area 1920 is an area for displaying a summary of the extracted case (other cases with similar progress).

[0343] In the illustrated example, the case summary display area 1920 displays a link to data stored in the server 96 of the conference management service as the minutes of the case.

[0344] The template display area 1922 is an area for displaying templates that have been extracted as having similar transaction histories and have been used in cases for which a contract has already been concluded.

[0345] In the example shown, the template display area 1922 displays the results of a query to the server 20 regarding information on the contract template used in a case with a similar transaction history, by referring to the case history database 218.

[0346] The concluded contract display area 1924 is an area for displaying the concluded contract for the case that has already been concluded and that has been extracted as having a similar transaction history.

[0347] In the example shown, the concluded contract display area 1924 displays the results of a query to the server 20 for information on the contract concluded in a case with a similar transaction history, by referring to the case history database 218.

[0348] <Third embodiment> <8 Data Structure of the Third Embodiment> 20 is a diagram showing the data structure of the case management database 219. The case management database 219 includes the following items: an "case management ID," an "client," an "object of transaction," an "approval application ID," an "conclusion ID," an "progress summary," an "case registration date," an "in charge," an "contract terms," ​​an "in charge of client," an "transaction completion date," and an "status."

[0349] The item "case management ID" is information for identifying each case.

[0350] The item "Customer" is information that identifies each customer in the case.

[0351] In the illustrated example, the item "Customer" is the same as the item "Customer" in the case history database 218 of FIG.

[0352] The item "transaction object" is information about the type of object involved in a transaction with a business partner.

[0353] In the illustrated example, the item "transaction object" is the same as the item "transaction object" in the case history database 218 of FIG.

[0354] The item "approval request ID" is information that identifies the approval request related to the transaction.

[0355] In the illustrated example, the item "approval request ID" is the same as the item "approval request ID" in the case history database 218 of FIG.

[0356] The item "contract ID" is information for identifying the contract conclusion relating to the transaction.

[0357] In the illustrated example, the item "Conclusion ID" is the same as the item "Conclusion ID" in the case history database 218 of FIG.

[0358] The item "Progress Summary" is information resulting from summarizing information on the transaction history of a case, which is stored in each service.

[0359] In the illustrated example, the item "Progress Summary" is the same as the item "Progress Summary" in the case history database 218 in Fig. 15. The item "Progress Summary" may include the content of the prompt given to the large-scale language model service server 95, the result output by the large-scale language model service server 95 in response to the prompt (which may include the source referenced when the large-scale language model service server 95 generated the answer), and information on the date and time of the output.

[0360] The item "case registration date" is information about when case information was registered in the record.

[0361] The item "person in charge" is information about the name of the person in charge or department in charge of the case.

[0362] The item "contract terms" is information on the contents of a contract, or the contents of a term sheet that defines the terms of a contract, as a document that defines the transaction terms for a project.

[0363] More specifically, the item "Contract terms" includes a data file of the contract, a data file of the term sheet, text of the contract terms, and the like.

[0364] The item "Customer Person in Charge" is information on the name of the person in charge or department in charge of the customer related to the matter.

[0365] The item "transaction completion date" is information about the timing when the transaction related to the matter was completed.

[0366] In the illustrated example, the item "transaction completion date" is the same as the item "transaction completion date" in the case history database 218 of FIG.

[0367] The item "status" is information about the status of the transaction.

[0368] In the illustrated example, the item "status" is the same as the item "status" in the case history database 218 of FIG.

[0369] <9. Operation of the Third Embodiment> FIG. 21 is a diagram showing the flow of processing for summarizing the process of concluding a contract already concluded with an existing customer in connection with a new transaction with the customer, and presenting the summarized results.

[0370] In step S2121, the summary presentation module 2050 of the server 20 presents to the user of the terminal 10 an operation screen for accepting the registration of a case.

[0371] The server 20 stores, in the case management database 219 or the case history database 218, information that records the progress of the conclusion of a case for which a contract has already been concluded between the parties.

[0372] Server 20 stores information on the minutes of meetings as information recording the progress in case history database 218. The information on the minutes of meetings stored in case history database 218 may be at least either data on minutes of meetings stored by a user of a first service (conference management service server 96), which is a service that manages minutes of meetings, or data on documents created in a second service that provides a cloud-based document creation tool.

[0373] The information recording the progress stored in the case history database 218 may be data recording sales activities for each case stored by a user of a third service (server 97 of the sales support system service) that provides sales support tools.

[0374] The information recording the progress stored in the case history database 218 may be a history of email sending and receiving or a history of message sending and receiving stored by users of a fourth service that provides messaging functions (messaging service server 98).

[0375] The information recording the progress stored in the case history database 218 may be data on the approval request sent and received in the approval request service (server 92 of the business support system service).

[0376] In step S2111, the terminal 10 displays an operation screen and accepts an operation from the user to register the contents of a new transaction item.

[0377] In step S2123, the summary presentation module 2050 of the server 20 acquires information on the case relating to the new transaction and updates the case management database 219.

[0378] The summary presentation module 2050 may acquire information indicating that a new case has been registered in a predetermined service that manages cases related to transactions (for example, a service different from the service provided by the server 20, more specifically, a service provided by the server 97 of the sales support system service), or may acquire information related to the new case from the predetermined service. In this way, when case information is registered in a service different from the service provided by the server 20, the server 20 may acquire case information from the other service and update the case management database 219 by receiving a notification from the other service, for example.

[0379] In addition, the summary presentation module 2050 may obtain information indicating that the case related to the new transaction has been processed in at least one of the services for requesting approval for new transactions (server 92 of the business support system service, request application database 213), the service for reviewing contracts (server 93 of the document review service, review history database 214), and the service for concluding contracts (server 20, conclusion management database 215, document management database 216) (for example, by receiving notification from these services when the case information is registered in each service), obtain the case information, and update the case management database 219.

[0380] In step S2125, if the new transaction is with an existing customer, the summary presentation module 2050 of the server 20 summarizes information recording the progress of past transactions with the existing customer. For example, the summary presentation module 2050 may determine that the new transaction is with an existing customer by comparing the information of the business partner involved in the new transaction with the information of the business partner of a case for which a contract has been concluded in the past (or by referring to the fact that the business partner is registered in the business partner master, etc.).

[0381] The summary presentation module 2050 may summarize by providing an instruction to the large-scale language model to summarize the progress recorded information and receiving a result generated by the large-scale language model in response to the instruction. The summary presentation module 2050 generates a prompt including the progress recorded information and an instruction to summarize the progress recorded information, and transmits the generated prompt to the large-scale language model service server 95. In this way, the summary presentation module 2050 provides an instruction to the large-scale language model service server 95 to summarize the progress recorded information related to past transactions.

[0382] The summary presentation module 2050 may also generate a summary by extracting important words, phrases, and sentences to be included in the summary based on recorded progress information, without relying on the large-scale language model service server 95.

[0383] The summary presentation module 2050 may target the information in the minutes of meetings in the case history database 218, summarize the information that records the progress, and register the summarized results in a record in the case history database 218 or the case management database 219.

[0384] The summary presentation module 2050 may summarize the information recording the progress, targeting at least either the minutes data stored in the first service (the conference management service server 96, as described in step S2121 of FIG. 21) or the document data stored in the second service (a service providing a cloud-based document creation tool, as described in step S2121 of FIG. 21).

[0385] The summary presentation module 2050 may be configured to summarize the information recording the progress of the sales activities stored in the third service (the server 97 of the sales support system service, as described in step S2121 of FIG. 21).

[0386] The summary presentation module 2050 may summarize the information recording the progress of at least one of the history of email sending and receiving or the history of messages sent and received in the fourth service (messaging service server 98, as described in step S2121 of Figure 21).

[0387] The summary presentation module 2050 may summarize the information recording the progress, targeting the data of the approval request (the server 92 of the business support system service, the approval request database 213).

[0388] The summary presentation module 2050 may give the instruction to the large-scale language model service server 95 to summarize the concluded project by including the reason for the discount in the summary result, and receive the summary generated in accordance with the instruction from the large-scale language model service server 95. This makes it easy to understand the reasons for discounts in past transactions.

[0389] The summary presentation module 2050 may give the instruction to the large-scale language model service server 95 to summarize the master contract, the status of related contracts related to the master contract, and the contents of the master contract and the contents of the related contracts for the concluded case, and receive the summary generated in accordance with the instruction from the large-scale language model service server 95. For example, in the document management database 216, if there are other contracts related to an already concluded contract (for example, a concluded contract and a memorandum about that contract, or a contract related to a basic contract and an individual contract based on the basic contract), information on these associations may be retained (for example, information on related records (for example, the item "document management ID") may be retained in the document management database 216). The summary presentation module 2050 generates a prompt containing instructions to summarize the relationships between multiple related contracts (for example, "summarize the contents of the concluded contract and the contents of the memorandum for this contract," "summarize the contents of the contract of the basic contract and the contents of other contracts related to the basic contract") for information on contracts related to previously concluded cases (document management database 216), while also including information on other related contracts in the prompt, and sends the generated prompt to the large-scale language model service server 95.

[0390] In step S2127, the summary presentation module 2050 of the server 20 receives the output result of the large-scale language model service server 95 and updates the case management database 219.

[0391] In step S2129, the summary presentation module 2050 of the server 20 refers to the case management database 219 and presents to the user of the terminal 10 the results of summarizing the information recording the progress of past transactions, as well as information on the contract terms of the cases for which contracts have already been concluded (contracts, term sheets, etc.) relating to the summary.

[0392] In this way, the summary presentation module 2050 acquires information on a case related to a new transaction, and if the acquired new transaction is with an existing customer, summarizes information recording the progress of past transactions with the existing customer. The summary presentation module 2050 presents the results of summarizing the progress of past transactions with the existing customer to the user.

[0393] The summary presentation module 2050 may acquire information indicating that a new case has been registered in a specified service that manages transaction cases (such as a service provided by the server 97 of the sales support system service), and when information on the new transaction case is registered in the specified service, present the summarized results in processing such as step S2125.

[0394] The summary presentation module 2050 may acquire information indicating that the case related to the new transaction has been processed in at least one of a service for requesting approval for a new transaction, a service for reviewing a contract, and a service for concluding a contract, and when the case related to the new transaction has been processed in these services, present the summarized results in processing such as step S2125.

[0395] In step S2113, the terminal 10 displays a summary of the progress of the past transaction and the contract terms of the past transaction.

[0396] Figure 22 shows the process flow for assisting in the decision on whether or not to renew a contract by presenting a summary of past transaction history when managing concluded contracts.

[0397] In step S2221, the document management module 2045 of the server 20 refers to the document management database 216 and extracts those contracts whose contract periods are about to expire from among the concluded contracts. For example, the document management module 2045 extracts those whose contract periods are about to expire within a certain period of time (those whose contract periods are about to expire within a few months, etc.).

[0398] The server 20 is configured to manage information on contracts for concluded projects in the document management database 216. When a period based on the managed contract expires, the document management module 2045 notifies the parties involved in the contract whether or not the contract needs to be renewed.

[0399] In step S2223, the summary presentation module 2050 of the server 20 transmits an instruction to the large-scale language model service server 95 to summarize information recording the conclusion process for an already concluded contract whose contract term is expiring. In this way, the summary presentation module 2050 summarizes the conclusion process for the contract related to the need for renewal as the term based on the contract arrives.

[0400] In step S2225, the summary presentation module 2050 of the server 20 receives the output result of the large-scale language model service server 95 and updates the case management database 219.

[0401] In step S2227, the summary presentation module 2050 of the server 20 presents to the user of the terminal 10 (for example, a user with permission to view the contract) a summary of the information recording the conclusion process and information on the contract terms at the time of conclusion (contract, term sheet, etc.) along with a notification of whether renewal is necessary for the contract whose contract term is about to expire. In this way, the summary presentation module 2050 makes the above-mentioned presentation in response to the expiration of the term based on the contract.

[0402] In step S2211, the terminal 10 displays a notification as to whether or not the contract, whose contract term is about to expire, needs to be renewed, a summary of the progress of past transactions, and the contract terms of the past transactions.

[0403] In step S2213, the terminal 10 receives an instruction from the user as to whether or not an update is required, and transmits the instruction to the server 20.

[0404] In step S2229, the document management module 2045 of the server 20 updates the document management database 216 etc. based on the instruction as to whether or not an update is required.

[0405] <10 Screen Examples of the Third Embodiment> FIG. 23 shows an example of an operation screen that displays a summary of past transactions with an existing customer in connection with a new transaction with the existing customer.

[0406] The matter registration operation screen 2300 is an operation screen for accepting an operation to register information about a matter relating to a transaction.

[0407] In the illustrated example, the case registration operation screen 2300 may be an operation screen for a service provided by the server 20, or may be an operation screen for accepting the registration of cases provided by a service different from the service provided by the server 20, such as a service provided by the server 97 of the sales support system service.

[0408] The account display area 2302 is an area for displaying the account that uses the service.

[0409] The new case display area 2304 is an area for displaying the registered contents of a case relating to a new transaction.

[0410] The case information designation section 2306 is an operation member that accepts designation of the contents of the case.

[0411] In the illustrated example, the case information designation unit 2306 receives designation from the user of the details of the case, such as the business partner, the subject of the transaction, the transaction quantity, the deadline for the transaction, etc. The details of the case input in the case information designation unit 2306 are registered as case information in the case management database 219, the services provided by the sales support system service server 97, etc.

[0412] The registration operation section 2308 is an operation member that accepts an operation to register the contents of the case designated in the case information designation section 2306 in the service or the like provided by the server 20 .

[0413] In the illustrated example, the registration operation unit 2308 transmits the content specified in the case information specification unit 2306 to the server 20, etc., in response to a user operation. This causes the case information to be registered in the case management database 219, etc. This corresponds to steps S2111, S2113, etc. in FIG. 21.

[0414] The similar case list display area 2310 is an area that displays a list of cases extracted as cases related to similar past transactions based on the content of the new transaction.

[0415] In the illustrated example, the similar case list display area 2310 indicates that the transaction is a new transaction with an existing customer, and also displays a list of similar cases from past transactions with the existing customer. In the processing of step S2129 etc., when a new transaction with an existing customer is made, the degree of similarity to past transactions with the existing customer may be evaluated, and cases with a higher degree of similarity may be displayed in the list first. For example, the degree of similarity between a new transaction and a past transaction may be determined as follows: Transactions involving the same or similar objects. For example, in the case of a transaction involving a mobile phone, transactions involving similar mobile devices or transactions involving goods or services (such as communication services) associated with the mobile phone may be deemed to be similar. Transactions with similar amounts · Cases where the person in charge of the other party to the transaction is the same · Projects where the person in charge on your side of the transaction is the same The extracted case display area 2312 is an area for displaying the contents of the extracted case.

[0416] The extracted deal display area 2312 corresponds to step S2129 etc. in Fig. 21. In the example shown, a summary of the transaction progress, including the reason for the discount, is displayed.

[0417] The progress confirmation operation section 2314 is an operation member that accepts an operation to confirm the progress of a transaction regarding an extracted past matter.

[0418] In the illustrated example, the progress confirmation operation unit 2314 responds with information stored in the item "progress summary" and the like of the case management database 219 in response to a user operation.

[0419] The condition confirmation operation section 2316 is an operation member that accepts an operation to confirm the contract conditions of the extracted past case.

[0420] In the illustrated example, the condition confirmation operation unit 2316 responds to the user's operation by sending information on the contract conditions such as the contract concluded for the extracted case or a term sheet.

[0421] The extracted case display area 2318 is an area for displaying the contents of the extracted case.

[0422] FIG. 24 shows an example of an operation screen that displays a summary of past transaction history when managing concluded contracts.

[0423] The contract management operation screen 2320 is an operation screen that accepts operations for managing concluded contracts as document data.

[0424] The account display area 2322 is an area where an account is displayed.

[0425] The search display area 2324 is an area that displays information for searching for concluded contracts.

[0426] The search term specification section 2326 is an operation member that accepts specification of a search term for searching for concluded contracts.

[0427] The search operation section 2328 is an operation member that accepts an operation to search for concluded contracts based on a specified search term.

[0428] In the illustrated example, the search operation unit 2328 accepts input of search terms to perform a search, but the large-scale language model service server 95 may also accept searches by inputting natural language in chat format (for example, "I would like to search for the contract concluded with AA Company").

[0429] The renewal target display area 2330 is an area for displaying a list of contracts for which it is determined whether or not renewal is necessary based on the expiration of the contract period.

[0430] The extracted case display area 2332 is an area for displaying information on transactions of contracts extracted as contracts whose contract periods are about to expire.

[0431] In the illustrated example, the extracted case display area 2332 displays information summarizing the progress of the transaction, such as "there is a related contract to the basic contract," that is, information indicating the relationship between multiple related contracts.

[0432] The progress confirmation operation section 2334 is an operation member that accepts an operation to confirm the progress of a transaction regarding an extracted past matter.

[0433] The progress check operation section 2334 corresponds to the progress check operation section 2314 in FIG.

[0434] The condition confirmation operation section 2336 is an operation member that accepts an operation to confirm the contract conditions of the extracted past case.

[0435] The condition confirmation operation section 2336 corresponds to the condition confirmation operation section 2316 in FIG.

[0436] The renewal necessity designation section 2338 is an operation member for receiving designation of whether or not a contract whose contract term is about to expire needs to be renewed.

[0437] In the example shown in the figure, the update necessity designation unit 2338, in response to user operation, if an update is necessary, manages this information on the server 20, and provides the user with the process of reviewing the contract terms, creating a contract, and concluding the contract.

[0438] The extracted case display area 2340 is an area for displaying information on transactions of contracts that have been extracted as contracts whose contract periods are about to expire.

[0439] <Fourth embodiment> <11 Operation of the Fourth Embodiment> FIG. 25 is a diagram showing the flow of processing for accepting input of consultation details from the business division to the legal department.

[0440] In step S2521, the summary presentation module 2050 of the server 20 presents an operation screen for accepting input of legal consultation to a user (e.g., a user of the business division) seeking legal consultation. At this time, the summary presentation module 2050 of the server 20 may present an operation screen for accepting designation of information sources to be summarized, items to be included in the summary, etc., to summarize information recording the progress of a transaction to the user seeking legal consultation.

[0441] In step S2511, the terminal 10A receives an input from the user requesting legal consultation with the legal department. The terminal 10A may receive an operation from the user on the operation screen to summarize information recording the progress of the transaction.

[0442] In step S2523, the summary presentation module 2050 of the server 20 receives from a first user information on legal consultation regarding legal matters for a second user who is a user in a different department from the first user, and stores the information in a database.

[0443] The summary presentation module 2050 identifies information recording the progress of the received legal consultation. For example, the summary presentation module 2050 may identify information recording the progress of the legal consultation by receiving from the user designation of information on a transaction case stored in the case history database 218, the case management database 219, the sales support system service server 97, etc.

[0444] The summary presentation module 2050 summarizes the identified information recording the progress. Here, the summary presentation module 2050 transmits an instruction to the large-scale language model service server 95 to summarize the identified information recording the progress of the transaction related to the legal consultation.

[0445] The server 20 stores information recording the progress of a transaction in a case history database 218, a case management database 219, the server 97 of the sales support system service, and the like.

[0446] The server 20 stores information on the minutes of the meeting as information recording the progress in the case history database 218, etc. The information on the minutes of the meeting stored in the case history database 218, etc. may be at least either data on minutes of the meeting stored by a user of a first service (a conference management service server 96) that is a service that manages the minutes of the meeting, or data on a document created in a second service that provides a cloud-based document creation tool.

[0447] The information recording the progress stored in the case history database 218, etc. may be data recording sales activities for each case stored by a user of a third service (server 97 of the sales support system service) that provides sales support tools.

[0448] The information recording the progress stored in the case history database 218, etc. may be a history of email sending and receiving or a history of message sending and receiving stored by users of a fourth service that provides messaging functions (messaging service server 98).

[0449] The information recording the progress stored in the case history database 218 or the like may be data on the approval request sent and received in the approval request service (server 92 of the business support system service).

[0450] The summary presentation module 2050 may specify the content to be summarized by the large-scale language model service server 95, and then obtain a summary including the specified content, as follows.

[0451] More specifically, the summary presentation module 2050 may generate a prompt including the recorded information of the progress and an instruction to summarize the progress including an overview of the business, and provide the generated prompt to the server 95 of the large-scale language model service, thereby summarizing the recorded information of the progress including the overview of the business.

[0452] The summary presentation module 2050 may generate a prompt including the recorded information of the progress and an instruction to summarize the progress including the information of the parties involved as an overview of the business, and provide the generated prompt to the server 95 of the large-scale language model service, thereby summarizing the recorded information of the progress including the information of the parties involved.

[0453] The summary presentation module 2050 may generate a prompt including an instruction to summarize the information of the parties, including at least one of information about the party paying the costs of the transaction or information about the party receiving the costs, and provide the generated prompt to the large-scale language model service server 95, thereby summarizing the recorded information of the progress, including at least one of information about the party paying the costs or information about the party receiving the costs, as information of the parties.

[0454] The summary presentation module 2050 may generate a prompt including the recorded information on the progress and an instruction to summarize the information on the parties, including whether the transaction is for a foreign company or a domestic company, and provide the generated prompt to the server 95 of the large-scale language model service, thereby summarizing the recorded information on the progress, including the information on the parties, including whether the transaction is for a foreign company or a domestic company.

[0455] The summary presentation module 2050 may generate a prompt including the recorded information of the progress and an instruction to summarize the handling of personal information as an overview of the business, and provide the generated prompt to the server 95 of the large-scale language model service, thereby summarizing the recorded information of the progress including the handling of personal information.

[0456] The summary presentation module 2050 may generate a prompt including the recorded information of the progress and an instruction to summarize the progress as an overview of the business, including at least one of the purpose or goal to be achieved by concluding the contract, and provide the generated prompt to the server 95 of the large-scale language model service, thereby summarizing the recorded information of the progress, including at least one of the purpose or goal to be achieved by concluding the contract.

[0457] In step S2525, the summary presentation module 2050 of the server 20 receives the summary of the transaction progress from the large-scale language model service server 95, and presents the summary of the progress to the user of the terminal 10A.

[0458] In step S2513, the terminal 10A displays a summary of the transaction progress. The terminal 10A accepts an operation from the user to transmit the content of the legal consultation to the legal department.

[0459] In step S2527, the summary presentation module 2050 of the server 20 accumulates a summary of the transaction progress and the content of the consultation with the legal department in a database. The summary presentation module 2050 notifies the department (e.g., the legal department) that a legal consultation is available.

[0460] In this way, the summary presentation module 2050 presents to the second user a summary of the information recording the progress of the legal consultation accepted in steps S2511 and S2523.

[0461] FIG. 26 is a diagram showing the flow of processing for receiving a response from the legal department to a legal consultation from the business department.

[0462] In step S2621, the summary presentation module 2050 of the server 20 presents an operation screen that displays the content of the legal consultation from another department and accepts a response to the user of the department that handles the legal consultation (legal department).

[0463] The summary presentation module 2050 may summarize the recorded progress information by giving an instruction to the large-scale language model service server 95 to summarize the recorded progress information, without relying on the operation of a user (e.g., a user in the legal department) answering the legal consultation.

[0464] The summary presentation module 2050 may also accept an operation to summarize the recorded progress information from the user who answers the legal consultation. In this way, the summary presentation module 2050 may provide the same process as step S2523 in Fig. 25 to the user of the terminal 10B (the legal department, the user of the department who answers the legal consultation).

[0465] In step S2611, the terminal 10B displays the content of the legal consultation from the other department and a summary of the transaction progress. The terminal 10B accepts an input of a response from the user. The summary presentation module 2050 of the server 20 may accept, from the user on the operation screen, an operation to generate information to be added to the response to the legal consultation.

[0466] In step S2623, the summary presentation module 2050 of the server 20 sends an instruction to the large-scale language model service server 95 to generate information to be added to the answer to the legal consultation.

[0467] More specifically, the summary presentation module 2050 may execute a step of generating a response from the second user who responds to the legal consultation to the first user who provided the legal consultation, and in this step, the response may be generated by at least one of adding an explanation of legal terms to the content of the response entered by the second user, or adding a rephrased sentence without using legal terms.

[0468] Here, the summary presentation module 2050 may refer to a score related to the first user's legal consultation experience, and generate the answer according to the first user's score.

[0469] In step S2625, the summary presentation module 2050 of the server 20 receives the results of generating information to be added to the response to the legal consultation from the large-scale language model service server 95, and presents the generated results to the user of the terminal 10B.

[0470] In step S2613, the terminal 10B displays information to be added to the answer to the legal consultation. The terminal 10B accepts an operation from the user to transmit the content of the answer to the legal consultation to the user who has made the legal consultation.

[0471] In step S2627, the summary presentation module 2050 of the server 20 stores the content of the response to the legal consultation in a database. The summary presentation module 2050 notifies the response to the legal consultation to the user of the department that requested the legal consultation. The response to the legal consultation may include information entered by the user providing the response and the result of the server 20 generating information to be added to the response in steps S2623, S2625, etc.

[0472] <12 Screen Examples of the Fourth Embodiment> FIG. 27 shows an example of an operation screen that accepts input of consultation details from the business division to the legal department.

[0473] The consultation input operation screen 2700 is an operation screen for accepting input of legal consultation.

[0474] In the illustrated example, the consultation input operation screen 2700 may be an operation screen for a service provided by the server 20, or may be an operation screen for accepting posts of communication between users provided by a service different from the service provided by the server 20, such as a service provided by the messaging service server 98.

[0475] The account display area 2702 is an area for displaying the account that uses the service.

[0476] The consultation content display area 2704 is an area for displaying the content of the legal consultation.

[0477] The consultation content designation section 2706 is an operation member that accepts designation of the content of legal consultation.

[0478] In the illustrated example, the consultation content designation unit 2706 accepts the legal consultation input from the user in free text. The content of the legal consultation input in the consultation content designation unit 2706 is registered as legal consultation information in a database managed by the server 20, a service provided by the messaging service server 98, etc.

[0479] The progress summary display area 2708 is an area for displaying a summary of the transaction progress relating to the legal consultation.

[0480] In the illustrated example, the progress summary display area 2708 accepts an operation to specify the information source that records the transaction progress, as will be described later, and an operation to specify the content to be included in the summary. The illustrated screen example corresponds to the processing of steps S2523, S2525, S2513, etc. in FIG. 25.

[0481] The information source designation section 2710 is an operation member that accepts designation of an information source from which the transaction progress is to be summarized.

[0482] In the illustrated example, the information source designation unit 2710 indicates that the user has designated a link to the minutes of the conference stored in the conference management service server 96 as the information source summarizing the progress of the transaction. In addition to the data stored in the server 20, the information source designation unit 2710 may also accept designation from the user of data stored in each system, such as the business support system service server 92, the document review service server 93, the sales support system service server 97, and the messaging service server 98, as the information source.

[0483] The summary content specification section 2712 is an operation member that accepts specification of the content to be included in the summary of the transaction progress.

[0484] The summary content designation unit 2712 accepts designation of the content to be included in the summary of the transaction progress, which may include the following. - Information on stakeholders as part of the business overview (when responding to legal consultations, it may be necessary to refer to information on stakeholders, and there may be matters that the payer and the payee need to take note of) - In terms of business overview, is it a transaction with a foreign company or a domestic company? (When answering legal inquiries, the applicable law may differ depending on whether the company is a foreign company or a domestic company) Handling of personal information (we may respond to legal consultations in consideration of laws and regulations regarding personal information) Purpose of the transaction or contract (we may provide legal advice in order to achieve the purpose of the transaction) The summary generation operation section 2714 is an operation member that accepts an operation to summarize the progress of a transaction.

[0485] The summary generation operation unit 2714 corresponds to the processes of steps S2511, S2523, S2525, etc. in FIG.

[0486] The summary display area 2716 is an area where the generated summary is displayed.

[0487] The summary display area 2716 corresponds to the processing of steps S2525, S2513, etc. in FIG.

[0488] The consultation sending operation section 2718 is an operation member that accepts an operation to send the content of the legal consultation to a user in a department that will provide an answer to the legal consultation.

[0489] The consultation transmission operation section 2718 corresponds to the processing of steps S2513, S2527, etc. in FIG.

[0490] FIG. 28 shows an example of an operation screen for receiving a response from the legal department to a legal consultation from the business department.

[0491] The consultation response operation screen 2720 is an operation screen for replying to legal consultations.

[0492] In the example shown, the consultation response operation screen 2720 may be an operation screen for a service provided by the server 20, or may be an operation screen for accepting posts of communication between users provided by a service different from the service provided by the server 20, such as a service provided by the messaging service server 98.

[0493] The account display area 2722 is an area where an account is displayed.

[0494] The consultation summary display area 2724 is an area for displaying a summary of the consultation content.

[0495] In the illustrated example, the consultation summary display area 2724 displays that the consultation is from the relevant department (business department) based on the department (business department) of the user seeking legal advice.

[0496] The consultation content display area 2726 is an area for displaying the content of the legal consultation input by the client.

[0497] The progress summary display area 2728 is an area for displaying information summarizing the progress of the transaction related to the consultation content.

[0498] The progress summary display area 2728 corresponds to the processing of step S2611 in FIG.

[0499] The summary generation operation section 2730 is an operation member that accepts an operation to summarize the progress of a transaction.

[0500] In the illustrated example, the summary generation operation unit 2730 receives an operation to summarize the transaction progress from a user who is an answerer of a legal consultation. In response to the user's operation, the summary generation operation unit 2730 may display a screen similar to that described in the progress summary display area 2708 in Fig. 25 and receive an operation to generate a summary from the user.

[0501] The client information display area 2732 is an area for displaying information about the client.

[0502] In the illustrated example, the client information display area 2732 displays the client's score, the number of years of experience, the number of cases handled, and other information. Although not illustrated, information such as the client's name and department may also be displayed. The server 20 may evaluate each user based on the client's experience in the organization (e.g., number of years of experience, number of transactions involved, number of contracts concluded based on transactions, number of legal consultations provided stored in the server 20, etc.). For example, the higher the experience, the higher the evaluation may be. By displaying the evaluation results of the client's experience in the client information display area 2732, the server 20 can provide the answering user with a reference when entering the content of their answer, making it easier for them to create an answer. For example, for a client evaluated as having extensive experience, the answerer may prepare a concise answer using legal terminology, while for a client evaluated as having insufficient experience, the answerer may enter a more detailed answer, attach reference materials such as guidelines, and enter an answer without using technical terms. This makes it easier for the answerer to prepare an answer appropriate to the level of experience.

[0503] The answer content display area 2734 is an area for displaying the input content of the answer to the legal consultation.

[0504] The answer content display area 2734 corresponds to the processing of steps S2611, S2613, etc. in FIG.

[0505] The answer specification section 2736 is an operation member that accepts specification of an answer to a legal consultation.

[0506] In the illustrated example, the answer specification section 2736 accepts input of an answer in free text.

[0507] The supplemental content specification section 2738 is an operation member for accepting specification of the target to be generated when generating information to be added to a response to a legal consultation.

[0508] In the example shown, the supplementary content specification unit 2738 accepts specifications from the user, such as adding explanations of technical terms such as legal terms contained in the answer, or generating an answer sentence that does not use technical terms.

[0509] The supplement generation operation section 2740 is an operation member that accepts an operation to generate information to be added to a response to a legal consultation.

[0510] In the illustrated example, the supplement generation operation section 2740 accepts an operation to generate information that supplements the answer, including the content specified in the supplement content specification section 2738.

[0511] The generated result display area 2742 is an area for displaying the results of generating information that supplements the answer.

[0512] The generation result display area 2742 corresponds to the processing of steps S2623, S2625, S2613, etc. in FIG.

[0513] The reply sending operation section 2744 is an operation member that accepts an operation to send a reply to a legal consultation to the sender.

[0514] In the illustrated example, the answer sending operation section 2744 sends an answer to the user of the client in response to the user's operation, including the content entered in the answer specification section 2736 and the generated information supplementing the answer displayed in the generated result display area 2742.

[0515] <Modification> The technical matters described in the above embodiments may be combined with each other.

[0516] (1) First Embodiment

[0517] (1-1) Sources of information on legal amendments and changes in legal interpretation In the first embodiment, an example has been described in which information provided by the server 94 of the law precedent information providing service is referenced to obtain information on legal amendments or changes in legal interpretation.

[0518] In addition, legal magazines, publishers of books, and media outlets providing legal information may periodically publish information on legal amendments and changes in legal interpretations, along with the information they publish. For example, they may periodically publish the above information through e-mail newsletters, articles on websites, etc., and this information may be available for reference on websites.

[0519] The server 20 may obtain information about legal amendments and changes in legal interpretation by referring to the periodically published email newsletters, etc. For example, the server 95 of the large-scale language model service may summarize the contents of the information sources mentioned above that mention legal amendments and changes in legal interpretation.

[0520] (1-2) How to link templates with relevant laws and precedents (template database 212) In addition to what has been described in the above embodiment, the server 20 may also manage each template managed in the template database 212 by grouping the templates by type. For example, multiple types of contracts, such as non-disclosure agreements, outsourcing contracts, and sales contracts, may be managed as belonging to the same group.

[0521] The server 20 may manage related laws, regulations, clauses, etc. by grouping contract types as a unit. This allows for extraction of related contracts in response to legal amendments and changes in legal interpretation, by simply extracting the templates for the grouped contracts, making template management even easier.

[0522] (1-3) Application to documents other than contract templates In addition to the above-described features of the first embodiment, the server 20 may extract security checklists that require modification in response to legal amendments or changes in legal interpretations. Security checklists are used by companies and organizations to evaluate and audit security measures, and are provided in the form of questions, checklists, etc. For example, when there is a change in the requirements for evaluation items such as ISMAP (Information System Security Management and Assessment Program) (e.g., when there is a change in the requirements for outsourcee management), it becomes necessary to add items or modify existing items in the security checklists being managed.

[0523] The server 20 may store information such as relevant laws and regulations, issues, and security evaluation system requirements for each item on the security checklist, and may detect any changes to these and notify the administrator of the security checklist.

[0524] (1-4) When new laws and regulations are enacted and implemented When a new law is enacted and enforced, server 20 may acquire information on the laws, issues, etc. that will be affected by the enactment of the new law (for example, the enactment of a new law abolishes the operation of an old law), and may identify the information on templates that will be affected when the new law is enacted and enforced, and may issue notifications to change the contents of the templates.

[0525] (2) Second Embodiment

[0526] (2-1) Method of extracting already concluded cases that are similar to the progress information of the case to be concluded In addition to the example described above, already concluded cases may be extracted as follows. Similarity of business partners. For example, whether the companies are of similar size, whether the transaction details (purchased items, consignment details, etc.) are similar (for example, whether the transaction falls under the Subcontract Act, whether the products involved in the transaction are of the same type, whether the transaction involves both products and services such as consulting, whether there will be additional purchases after the transaction, etc.). Similarity of transaction type. For example, whether you are the ordering party or the receiving party (purchasing party or not), whether you sell via an agent or directly.

[0527] (3) Third Embodiment

[0528] (3-1) Source of information from which progress records are obtained In addition to the above, a fault management system and an incident management table may be included as sources of information recording the progress of a transaction.

[0529] For example, a discount may be given in a transaction because the customer was unable to use the service, etc. due to a failure or accident in the service, etc. As described above, the server 20 may refer to the history of service, etc. failures managed by the failure management system, as well as the occurrence and history of incidents, as information sources that record the progress of the transaction, and generate information summarizing the progress including these.

[0530] (4) Regarding the Fourth Embodiment

[0531] (4-1) How to generate a paraphrase of the answer In the above example, when generating a sentence that paraphrases the response to the legal consultation, for example, a prompt that generates a sentence without using legal terminology may be generated by referring to a description in a book provided by the book reading service server 99, which is prepared for beginners, and a prompt including the sentence of the response to the legal consultation and the description in the book may be provided to the large-scale language model service server 95, thereby generating a sentence that paraphrases the above response.

[0532] The network is composed of the Internet, a LAN, various mobile communication systems constructed by wireless base stations, etc. For example, the network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks (e.g., Wi-Fi (registered trademark)) that can connect to the Internet via a predetermined access point. In the case of a wireless connection, communication protocols include, for example, Z-Wave (registered trademark), ZigBee (registered trademark), and Bluetooth (registered trademark). In the case of a wired connection, the network also includes a direct connection using a USB (Universal Serial Bus) cable, etc.

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

[0534] A database refers to a relational database, which manages data sets called masters and tables in a tabular format structurally defined by rows and columns, by relating them to each other. In a database, a table is called a table, a master, a column in a table is called a column, and a row in a table is called a record. In a relational database, relationships between tables and masters can be set and associated.

[0535] Typically, each table and each master has a column set as a primary key to uniquely identify a record, but setting a primary key to a column is not essential. The control unit can cause the processor 901 to add, delete, or update records in specific tables and masters stored in the storage unit according to various programs.

[0536] Furthermore, by storing data, various programs, and various databases in the storage unit, it can be considered that the information processing device and information processing system according to the present disclosure have been manufactured.

[0537] Note that the databases and masters in this disclosure may include any data structure in which information is structurally defined (such as a list, dictionary, associative array, or object). The data structure also includes data that can be considered as a data structure by combining data with functions, classes, methods, etc. written in any programming language.

[0538] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that implements the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for providing such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs, optical disks, magneto-optical disks, CD-Rs, magnetic tape, non-volatile memory cards, and ROMs.

[0539] Furthermore, the program code that realizes the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, and Java (registered trademark).

[0540] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read and execute the program code stored in the storage means or storage medium.

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

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

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

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

[0545] (Addendum) The matters described in the above embodiments will be supplemented below.

[0546] <Additional Notes to the First Embodiment>

[0547] (Appendix 1) A program for operating a computer having one or more computer processors, configured to store one or more contract templates in a memory unit, the program causing the one or more computer processors to execute the steps of obtaining information regarding legal amendments or changes in legal interpretation, identifying templates stored in the memory unit that have clauses related to the legal amendments or changes in legal interpretation, and presenting the identified templates to a user.

[0548] (Appendix 2) A program as described in Appendix 1, in which one or more contract templates are stored in a memory unit in association with tags related to laws and regulations or issues, and in the acquisition step, information related to legal amendments or changes in legal interpretation is acquired by acquiring information on at least one of the laws and regulations or issues related to the legal amendments or changes in legal interpretation, and in the identification step, a contract template is identified that is associated with a tag corresponding to at least one of the laws and regulations or issues related to the acquired changes.

[0549] (Appendix 3) The program described in Appendix 2 further causes one or more computer processors to extract legal terms from at least one of the clause headings or clause bodies of the contract template by associating tags with one or more contract templates in the memory unit, identifying at least one of the laws or issues corresponding to the extracted legal terms, and storing tags corresponding to at least one of the identified laws or issues in the memory unit in association with the contract template from which the tags were extracted.

[0550] (Appendix 4) A program described in any of Appendices 1 to 3, in which, in the presentation step, the identified template is presented to the user by identifying keywords that need to be corrected among the clauses of the identified contract template and displaying the identified keywords that need to be corrected separately from other wording in the body of the identified contract template.

[0551] (Appendix 5) A program described in any of Appendices 1 to 4, in which, in the presentation step, the identified template is presented to the user by identifying clauses in the identified contract template that require amendment, generating proposed amendments for the identified clauses that require amendment, and presenting the generated proposed amendments.

[0552] (Appendix 6) The program described in Appendix 5, wherein, in the acquiring step, acquiring information regarding legal amendments or changes in legal interpretation includes acquiring explanatory information regarding legal amendments or changes in legal interpretation, and, in the presenting step, generating proposed amendments and presenting the generated proposed amendments includes acquiring a sample proposed amendment from the explanatory information regarding legal amendments or changes in legal interpretation acquired in the acquiring step, and presenting the acquired proposed amendments.

[0553] (Appendix 7) A program as described in any of Appendices 1 to 6, which causes one or more computer processors to further execute the steps of: accepting from a user an operation to modify each clause of the identified template in response to legal amendments or changes in legal interpretation, and storing the operation in association with the template in a memory unit; and notifying each user who can use one or more contract templates of the template identified in the identifying step, from among the one or more contract templates stored in the memory unit, and information on the modifications to be made to each clause of the identified template.

[0554] (Appendix 8) A program as described in Appendix 7, in which, in the notification step, the program accepts modifications to all templates identified in the identification step in response to legal amendments or changes in legal interpretation, and notifies each user who can use one or more contract templates that modifications to the templates have been completed.

[0555] (Appendix 9) A program as described in any of Appendices 1 to 8, wherein the memory unit is configured to store one or more contract templates in versions amended due to legal amendments or changes in legal interpretation and in versions before amendment; the acquiring step acquires information on the time when the legal amendments or changes in legal interpretation will apply; and the program further controls one or more computer processors so that, depending on the arrival of the time when the amendments or changes in legal interpretation will apply, the versions of one or more contract templates stored in the memory unit that have been amended due to legal amendments or changes in legal interpretation are made available to each user, while the versions before amendments are not made available to each user.

[0556] (Appendix 10) A program described in any of Appendices 1 to 9, wherein the memory unit is configured to store one or more templates of supporting documents such as invoices, estimates, etc., and in the identifying step, identifies a template of a supporting document that needs to be revised due to a legal amendment or a change in legal interpretation, and in the presenting step, presents the template of the identified supporting document.

[0557] (Appendix 11) A method for operating a computer having one or more computer processors, the method being configured to store one or more contract templates in a memory unit, the method comprising the steps of: acquiring information regarding legal amendments or changes in legal interpretation; identifying templates stored in the memory unit that have clauses related to the legal amendments or changes in legal interpretation; and presenting the identified templates to a user.

[0558] (Appendix 12) An information processing device configured to store one or more contract templates in a memory unit, wherein a control unit of the information processing device executes the steps of acquiring information regarding legal amendments or changes in legal interpretation, identifying templates stored in the memory unit that have clauses related to legal amendments or changes in legal interpretation, and presenting the identified templates to a user.

[0559] <Additional Notes on the Second Embodiment>

[0560] (Appendix 1) A program for operating a computer having one or more computer processors, wherein a memory unit stores information recording the progress of the conclusion of a case in which a contract has already been concluded between the parties, and the memory unit is configured to store one or more contract templates, and the program causes the one or more computer processors to execute the following steps: extracting information about already concluded cases that is similar to the progress information of the new case in which a contract is to be concluded, based on the progress information of the case in which a contract is to be newly concluded between the parties and the information recording the progress stored in the memory unit; identifying the contract template used in the extracted already concluded case; and presenting the identified contract template.

[0561] (Appendix 2) A program as described in Appendix 1, in which information on minutes of meetings is stored in a memory unit as information recording progress, and in the extraction step, information on cases that have already been concluded is extracted by referring to the information on minutes of meetings in the memory unit.

[0562] (Appendix 3) The program described in Appendix 2, wherein the information on meeting minutes stored in the memory unit is at least either data on minutes stored by a user of a first service that manages meeting minutes, or data on documents created in a second service that provides a cloud-based document creation tool, and the extraction step extracts information on already concluded cases based on data on minutes of already concluded cases that are searched for in the first service as having similar progress information, or data on documents of already concluded cases that are searched for in the second service as having similar progress information.

[0563] (Appendix 4) A program described in any of Appendices 1 to 3, wherein the information recording the progress stored in the memory unit is data recording sales activities for each case stored by a user of a third service that provides sales support tools, and the extraction step extracts information about cases that have already been concluded based on data recording sales activities that are searched for in the third service as having similar progress information.

[0564] (Appendix 5) A program described in any of Appendices 1 to 4, wherein the information recording the progress stored in the memory unit is a history of email sending and receiving or a history of message sending and receiving stored by a user of a fourth service that provides a messaging function, and the extraction step extracts information about already concluded cases that are searched for as having similar email sending and receiving histories or similar messages sent and received in the fourth service.

[0565] (Appendix 6) A program described in any of Appendices 1 to 5, in which the information recording the progress stored in the memory unit is data on approval requests sent and received in the approval request service, and the extraction step extracts information on cases that have already been concluded and have similar data on the approval request.

[0566] (Appendix 7) The program according to any one of appendices 1 to 6, wherein in the extraction step, information on cases that have already been concluded is extracted by summarizing information that records the progress of the conclusion of each case, which is accumulated in a memory unit, and storing the first summarized result; summarizing information on the progress of cases in which a new contract is to be concluded between the parties, and storing the second summarized result; and comparing the first summarized result with the second summarized result to determine the degree of similarity, thereby extracting information on cases that have already been concluded.

[0567] (Appendix 8) The program described in Appendix 7, wherein in the extraction step, at least one of a first summary result or a second summary result is obtained by instructing the large-scale language model to summarize information recording the progress of the conclusion of each case, and by instructing the large-scale language model to summarize information on the progress of a case in which a new contract is to be concluded between the parties, the program obtains the first summary result and extracts information on similar cases that have already been concluded by comparing the first summary result and the second summary result for each case stored in the memory unit.

[0568] (Appendix 9) A program as described in any of Appendices 1 to 8, wherein the memory unit stores information on the contract for a project for which a contract has already been concluded between the parties, or on a term sheet defining the contract terms, in association with the project; and the extraction step performs the following operations: acquiring at least one of the contract type for a new project for which a contract is to be concluded between the parties, or the term sheet defining the contract terms; determining the degree of match between the acquired contract type or at least one of the term sheet and the contract or term sheet for each project for which a contract has already been concluded and stored in the memory unit; and extracting projects for which a contract has already been concluded that are determined to have a high degree of match.

[0569] (Appendix 10) A program described in any of Appendices 1 to 9, in which in the identification step, the contract template is identified by comparing the contract used in the extracted concluded case with one or more contract templates stored in a memory unit, and identifying the template with a high degree of match.

[0570] (Appendix 11) A program described in any of Appendices 1 to 10, in which a memory unit stores, for each case, information on a template that serves as the basis for the contract concluded for that case, and in the identification step, identifies information on the template that is associated with the extracted concluded case.

[0571] (Appendix 12) A program described in any of Appendices 1 to 11, in which a memory unit stores information recording the process of concluding a contract as a user uses a specified service, and in an extraction step, extracts information about cases that have already been concluded based on the information stored in the specified service, and in a presentation step, outputs information about the identified contract template to the specified service, thereby presenting the contract template information on the operation screen of the specified service.

[0572] (Appendix 13) A program as described in any of Appendices 1 to 12, in which a memory unit accumulates information recording the process of concluding a contract as a user uses a specified service, and in the presentation step, a contract template is presented by accepting the designation of a specified service on an operation screen that accepts searches for one or more contract templates stored in the memory unit, and displaying information about cases that have already been concluded, extracted based on the information recording the process of concluding a contract that is accumulated in the specified specified service, and displaying information about the contract template used in the extracted cases that have already been concluded.

[0573] (Appendix 14) A method for operating a computer having one or more computer processors, wherein a memory unit stores information recording the progress of the conclusion of a case in which a contract has already been concluded between the parties, and the memory unit is configured to store one or more contract templates, the method comprising the steps of: extracting, by the one or more computer processors, information on already concluded cases that is similar to the progress information of the new case in which a contract is to be concluded, based on the progress information of the case in which a contract is to be newly concluded between the parties and the information recording the progress stored in the memory unit; identifying the contract template used in the extracted already concluded case; and presenting the identified contract template.

[0574] (Appendix 15) An information processing device in which a memory unit stores information recording the progress of the conclusion of a case in which a contract has already been concluded between the parties, and the memory unit is configured to store one or more contract templates, and a control unit of the information processing device executes the steps of: extracting information about already concluded cases that is similar to the information about the progress of a case in which a contract is to be newly concluded between the parties, based on the information about the progress of the case in which a contract is to be newly concluded and the information recording the progress stored in the memory unit; identifying the contract template used in the extracted already concluded case; and presenting the identified contract template.

[0575] <Additional Notes on the Third Embodiment>

[0576] (Appendix 1) A program for operating a computer having one or more computer processors, which stores information in a memory unit that records the progress of the conclusion of a project for which a contract has already been concluded between the parties, and causes the one or more computer processors to execute the steps of summarizing the information that records the progress of the conclusion of the project for which a contract has already been concluded, and presenting the results of summarizing the information that records the progress in the summarizing step, and information on the contract terms of the project for which a contract has already been concluded that relates to the summary.

[0577] (Appendix 2) A program as described in Appendix 1, in which information on minutes of a meeting is stored in a memory unit as information recording the progress, and in a summarizing step, the information on minutes of a meeting stored in the memory unit is summarized as the information recording the progress.

[0578] (Appendix 3) The information on the minutes of a meeting stored in the memory unit is at least either minutes data stored by a user of a first service that manages minutes of meetings, or document data created in a second service that provides a cloud-based document creation tool, and in the summarizing step, the program described in Appendix 2 summarizes the information recording the progress, targeting at least either the minutes data stored in the first service or the document data stored in the second service.

[0579] (Appendix 4) A program described in any of Appendices 1 to 3, in which the information recording the progress accumulated in the memory unit is data recording sales activities for each case accumulated by users of a third service that provides sales support tools, and in the summarizing step, the information recording the progress is summarized using the data recording sales activities accumulated in the third service.

[0580] (Appendix 5) A program described in any of Appendices 1 to 4, in which the information recording the progress stored in the memory unit is a history of email sending and receiving or a history of message sending and receiving stored by a user of a fourth service that provides a messaging function, and in the summarizing step, the information recording the progress is summarized for at least either the history of email sending and receiving or the history of messages sent and received in the fourth service.

[0581] (Appendix 6) The information recording the progress stored in the memory unit is the data of the approval request sent and received in the approval request service, and in the summarizing step, the program described in any of Appendices 1 to 5 summarizes the information recording the progress for the approval request data.

[0582] (Appendix 7) 7. The program according to any one of appendices 1 to 6, wherein in the summarizing step, the summarizing includes providing an instruction to a large-scale language model to summarize the progress-recorded information, and receiving a result generated by the large-scale language model in response to the instruction.

[0583] (Appendix 8) The program described in Appendix 7, wherein in the summarizing step, instructions are given to the large-scale language model to summarize the reasons for discounts in already concluded cases, and the program receives the summary generation results in accordance with the instructions from the large-scale language model.

[0584] (Appendix 9) A program as described in any of Appendices 7 to 8, wherein in the summarizing step, instructions are given to the large-scale language model to summarize the master contract, the status of related contracts related to the master contract, and the contents of the master contract and the contents of the related contracts for concluded cases, and the program receives the summary generation result in accordance with the instructions from the large-scale language model.

[0585] (Appendix 10) The program described in any of Appendices 1 to 9 causes one or more computer processors to execute a step of acquiring information on a case related to a new transaction, and if the acquired new transaction is with an existing customer, summarizes information recording the progress of past transactions with the existing customer in a summarizing step, and presents the results of summarizing the progress of past transactions with the existing customer in a presenting step.

[0586] (Appendix 11) A program as described in Appendix 10, wherein in the acquiring step, information indicating that a new case has been registered in a specified service that manages transaction cases is acquired, and when information on a new transaction case is registered in the specified service, a summarized result is presented in the presenting step.

[0587] (Appendix 12) A program according to any one of Appendices 10 to 11, wherein in the acquiring step, information indicating that a case related to a new transaction has been processed in at least one of a service for requesting approval for a new transaction, a service for reviewing a contract, and a service for concluding a contract is acquired, and when a case related to a new transaction has been processed in the service, a summarized result is presented in the presenting step.

[0588] (Appendix 13) A program described in any of Appendices 1 to 12, which is configured to manage, in a memory unit, information on contracts for concluded projects, and notify whether the contract needs to be renewed when a period based on the managed contract arrives, and in a summarizing step, summarize the process for concluding the contract regarding whether renewal is necessary when a period based on the contract arrives, and in a presenting step, present the process when a period based on the contract arrives.

[0589] (Appendix 14) A method for operating a computer having one or more computer processors, wherein a memory unit stores information recording the progress of the conclusion of a contract for a project for which a contract has already been concluded between the parties, and the method executes the steps of the one or more computer processors summarizing the information recording the progress of the conclusion of the project for which a contract has already been concluded, and presenting the result of summarizing the information recording the progress in the summarizing step and information on the contract terms of the project for which a contract has already been concluded, related to the summary.

[0590] (Appendix 15) An information processing device in which a memory unit stores information recording the progress of the conclusion of a case in which a contract has already been concluded between the parties, and a control unit of the information processing device executes the steps of summarizing the information recording the progress of the conclusion of the concluded case, and presenting the result of summarizing the information recording the progress in the summarizing step and information on the contract terms of the concluded case related to the summary.

[0591] <Additional Notes on the Fourth Embodiment>

[0592] (Appendix 1) A program for operating a computer having one or more computer processors, wherein a memory unit stores information recording the progress toward contract conclusion for a case involving a transaction between parties, and the program causes the one or more computer processors to execute the following steps: accepting information about legal consultation regarding legal matters from a first user for a second user who is a user in a different department from the first user; identifying information recording the progress related to the accepted legal consultation and summarizing the identified information recording the progress; and presenting to the second user the summarized information recording the progress related to the legal consultation accepted in the accepting step.

[0593] (Appendix 2) A program as described in Appendix 1, in which information on minutes of a meeting is stored in a memory unit as information recording the progress, and in a summarizing step, the information on minutes of a meeting stored in the memory unit is summarized as the information recording the progress.

[0594] (Appendix 3) The information on the minutes of a meeting stored in the memory unit is at least either minutes data stored by a user of a first service that manages minutes of meetings, or document data created in a second service that provides a cloud-based document creation tool, and in the summarizing step, the program described in Appendix 2 summarizes the information recording the progress, targeting at least either the minutes data stored in the first service or the document data stored in the second service.

[0595] (Appendix 4) the progress record information stored in the storage unit is data of a record of sales activities for each case stored by a user of a third service that provides a sales support tool; A program described in any one of appendices 1 to 3, in which in the summarizing step, information recording the progress is summarized using data on records of sales activities accumulated in the third service.

[0596] (Appendix 5) the information recording the progress stored in the storage unit is a history of email transmission and reception or a history of message transmission and reception stored by a user of a fourth service that provides a messaging function, A program described in any one of appendices 1 to 4, in which in the summarizing step, the program summarizes the recorded information of the progress of at least one of the history of email sending and receiving or the history of messages sent and received in the fourth service.

[0597] (Appendix 6) The information recording the progress stored in the memory unit is the data of the approval request sent and received in the approval request service, and in the summarizing step, the program described in any of Appendices 1 to 5 summarizes the information recording the progress for the approval request data.

[0598] (Appendix 7) 7. The program according to any one of appendices 1 to 6, wherein in the summarizing step, the summarizing includes providing an instruction to a large-scale language model to summarize the progress-recorded information, and receiving a result generated by the large-scale language model in response to the instruction.

[0599] (Appendix 8) 8. The program of claim 7, wherein in the summarizing step, the progress recorded information is summarized by giving an instruction to the large-scale language model to summarize the progress recorded information without the operation of the second user.

[0600] (Appendix 9) A program described in any of Appendices 7 to 8, wherein in the summarizing step, a prompt including the recorded information on the progress and an instruction to summarize the progress including an overview of the business is generated, and the generated prompt is provided to a large-scale language model, thereby summarizing the recorded information on the progress including the overview of the business.

[0601] (Appendix 10) The program described in Appendix 9, wherein in the summarizing step, a prompt including the recorded information of the progress and an instruction to summarize the progress including the information of the parties as an overview of the business is generated, and the generated prompt is provided to a large-scale language model, thereby summarizing the recorded information of the progress including the information of the parties.

[0602] (Appendix 11) The program described in Appendix 10, wherein in the summarizing step, a prompt is generated that includes information on the recorded progress and an instruction to summarize the information on the parties, including at least one of information on the party paying the costs of the transaction or information on the party receiving the costs, and the generated prompt is provided to a large-scale language model, thereby summarizing the information on the recorded progress, including at least one of information on the party paying the costs or information on the party receiving the costs, as information on the parties.

[0603] (Appendix 12) 12. A program as described in any of Appendices 10 to 11, wherein in the summarizing step, a prompt is generated including information on the recorded progress and instructions to summarize information on the parties, including whether the transaction is for a foreign company or a domestic company, and the generated prompt is provided to a large-scale language model to summarize the information on the recorded progress, including information on the parties, including whether the transaction is for a foreign company or a domestic company.

[0604] (Appendix 13) A program described in any of Appendices 9 to 12, wherein in the summarizing step, a prompt is generated that includes information on the recorded progress and instructions to summarize the information, including the handling of personal information, as an overview of the business, and the generated prompt is provided to a large-scale language model, thereby summarizing the information on the recorded progress, including the handling of personal information.

[0605] (Appendix 14) A program described in any of Appendices 9 to 13, wherein in the summarizing step, a prompt is generated that includes information on the recorded progress and an instruction to summarize the progress as an overview of the business, including at least one of the objectives or goals to be achieved by concluding the contract, and the generated prompt is provided to a large-scale language model, thereby summarizing the information on the recorded progress, including at least one of the objectives or goals to be achieved by concluding the contract.

[0606] (Appendix 15) A program described in any of Appendices 1 to 14, wherein in the presentation step, the information on the legal consultation received from the first user and the results summarized in the step of summarizing the legal consultation are both displayed on an operation screen to present to the second user.

[0607] (Appendix 16) 16. The program of any one of Appendices 1 to 15, further causing one or more computer processors to execute a step of generating a response from a second user who has received legal advice to the first user, wherein in the step of generating a response, the response is generated by at least one of adding an explanation of legal terms to the content of the response entered by the second user, or adding a rephrased sentence without using legal terms.

[0608] (Appendix 17) 17. The program of claim 16, wherein in the step of generating an answer, the program refers to a score related to the first user's legal consultation experience and generates an answer based on the first user's score.

[0609] (Appendix 18) A method for operating a computer having one or more computer processors, wherein a memory unit stores information recording the progress toward contract conclusion for a case involving a transaction between parties, and the method includes the steps of the one or more computer processors receiving, from a first user, information about a legal consultation regarding legal matters for a second user who is a user in a different department from the first user; identifying information recording the progress related to the received legal consultation and summarizing the identified information recording the progress; and presenting to the second user the summarized information recording the progress related to the legal consultation received in the receiving step.

[0610] (Appendix 19) An information processing device, in which a memory unit stores information recording the progress toward contract conclusion for a case involving a transaction between parties, and a control unit of the information processing device executes the steps of accepting, from a first user, information about legal consultation regarding legal matters for a second user who is a user in a different department from the first user, identifying information recording the progress related to the accepted legal consultation and summarizing the identified information recording the progress, and presenting to the second user the summary of the information recording the progress related to the legal consultation accepted in the accepting step.

Claims

1. A program for operating a computer having one or more computer processors, The program causes the one or more computer processors to: For new contracts, there is a step of summarizing the transaction history of the project; presenting the summarized results to each user; The memory unit stores information that records the process of concluding a contract. In the summarizing step, the program summarizes the transaction history of the case based on the information recording the progress of the contract conclusion stored in the memory unit.

2. the storage unit stores information on minutes of the meeting as the information recording the progress, 2. The program according to claim 1, wherein in the summarizing step, the transaction history of the matter is summarized using the information of the minutes of the meeting stored in the storage unit.

3. The information of the minutes of the meeting stored in the storage unit is Data on minutes of a meeting stored by a user of a first service that is a service for managing minutes of a meeting; or Data of documents created in a second service that provides a cloud-based document creation tool; At least one of the following is true: The program of claim 2, wherein in the summarizing step, the information recording the progress is summarized for at least one of the minutes data stored in the first service or the document data stored in the second service.

4. the information recording the progress stored in the storage unit is data of a record of sales activities for each case stored by a user of a third service that provides a sales support tool, 2. The program according to claim 1, wherein in the summarizing step, the information recording the progress is summarized for the data of the sales activity records accumulated in the third service.

5. the information recording the progress stored in the storage unit is a history of email transmission and reception or a history of message transmission and reception stored by a user of a fourth service that provides a messaging function, 2. The program according to claim 1, wherein in the summarizing step, the recorded information is summarized for at least one of the history of sending and receiving emails or the history of messages sent and received in the fourth service.

6. The information recording the progress stored in the storage unit is data of a request for approval transmitted and received in a request for approval service, The program according to claim 1 , wherein in the summarizing step, the information recording the progress is summarized for the data of the approval request.

7. In the summarizing step, the summarizing includes: providing instructions to a large-scale language model summarizing the logged information; and receiving a result generated by the large-scale language model in response to the instruction.

8. In the summarizing step, the instructions are given to the large-scale language model, providing instructions to summarize the reason for the discount, including the reason for the discount in the summary result; and receiving, from the large-scale language model, a result of generating the summary in response to the instruction.

9. In the summarizing step, the instructions are given to the large-scale language model, providing said instructions summarizing the status of a master agreement and any related agreements relating to said master agreement, including the contents of said master agreement and the contents of said related agreements; and receiving, from the large-scale language model, a result of generating the summary in response to the instruction.

10. The program causes the one or more computer processors to: Execute a step of acquiring information on a new transaction; If the acquired new transaction is with an existing customer, the summarizing step summarizes information recording the progress of past transactions with the existing customer; 2. The program according to claim 1, wherein the step of presenting presents a summary of the history of past transactions with the existing customer.

11. In the acquiring step, information indicating that a new case has been registered is acquired in a predetermined service that manages cases related to transactions; 11. The program according to claim 10, wherein the step of presenting presents the summarized results when information on the new transaction is registered in the predetermined service.

12. In the acquiring step, information indicating that the matter related to the new transaction has been processed in at least one of a service for requesting approval for the new transaction, a service for reviewing the contract, and a service for concluding the contract is acquired, 11. The program according to claim 10, wherein the step of presenting presents the summarized results when the new transaction has been processed in the service.

13. 1. A method of operating a computer having one or more computer processors, comprising: The method further comprises the step of: For new contracts, there is a step of summarizing the transaction history of the project; presenting the summarized results to each user; The memory unit stores information that records the process of concluding a contract. In the summarizing step, the process of the transaction for the case is summarized using the information that records the process of concluding the contract stored in the memory unit.

14. An information processing device, a control unit of the information processing device, For new contracts, there is a step of summarizing the transaction history of the project; presenting the summarized results to each user; The memory unit stores information that records the process of concluding a contract. In the summarizing step, the information processing device summarizes the transaction history of the case based on the information recording the progress of the contract conclusion stored in the storage unit.

Images