Information processing device, method, program

Abstract

Even after a contract has been signed, there is a need for technology that makes contract management even easier. [Solution] The memory unit stores the concluded contract and the access rights to view the concluded contract. The program causes one or more computer processors to perform the steps of receiving a request from a user to view the concluded contract and, in response to the viewing request, allowing the user to view the concluded contract according to the access rights. The program further causes one or more computer processors to perform the steps of obtaining information indicating that there have been changes in the members of the organizations of the parties to the concluded contract and, based on the information obtained in the acquisition step, notifying the user of the update of the access rights to view the concluded contract.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, method, and program.

Background Art

[0002] In conducting business activities, various contracts are concluded and the concluded contract documents are managed. With electronic contract services, document data is approved between parties and the approved document data is managed on the service. For example, as methods of electronic signature, there are a witness type, a party type, etc.

[0003] Patent Document 1 describes an electronic contract system. In Patent Document 1, as a method of electronic contract, uploading electronic data of a contract document to a cloud server, receiving an operation for the sender of the contract document to give consent, the sender designating the user of the recipient to whom the contract is requested, sending an email requesting the recipient to conclude consent, and receiving an operation for the recipient to give consent are described.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] When concluding a contract through an electronic contract, for a user who has performed an operation to give consent to the contract document, viewing authority for the concluded contract document is set. On the other hand, concluded contract documents are often managed on an annual basis based on the contract period, etc. During that time, since the organizational structure of the organization that is a party to the contract document may also be variously changed along with the growth of the business, etc., over time since conclusion, the viewing authority for the concluded contract document may become inappropriate.

[0006] Therefore, there is a need for technology that makes contract management even easier after the contract has been signed. [Means for solving the problem]

[0007] To solve the above problems, a program in one aspect of this disclosure is a program for operating a computer having one or more computer processors. The program stores concluded contracts and access rights to concluded contracts in a memory unit. The program causes one or more computer processors to perform the steps of receiving a request from a user to view concluded contracts, and allowing the user to view the concluded contracts in accordance with the access rights. The program further causes one or more computer processors to perform the steps of obtaining information indicating that there have been changes in the members of the organizations of the parties to the concluded contracts, and notifying the user of the update of access rights to the concluded contracts based on the information obtained in the acquisition step. [Effects of the Invention]

[0008] According to this disclosure, even after the contract has been concluded, it will be possible to make the management of the contract even easier, depending on the circumstances after the contract has been concluded. [Brief explanation of the drawing]

[0009] [Figure 1] Figure 1 shows the configuration of System 1. [Figure 2] Figure 2 shows the configuration of server 20. [Figure 3] Figure 3 shows the configuration of terminal 10. [Figure 4] Figure 4 shows the data structure of the user database 211. [Figure 5] Figure 5 shows the data structure of the contract management database 212. [Figure 6]Figure 6 shows the data structure of the document management database 213. [Figure 7] Figure 7 shows the data structure of the approval request database 214. [Figure 8] Figure 8 shows the data structure of the review history database 215. [Figure 9] Figure 9 shows the process flow for prompting the update of access permissions for managed document data based on updated personnel information. [Figure 10] Figure 10 shows the process flow for extracting documents where the parties involved are not affiliated with the organization, and prompting them to update their viewing permissions. [Figure 11] Figure 11 shows the process flow for which parties approve the setting of viewing permissions for specific users on document data. [Figure 12] Figure 12 shows an example screen that prompts the user to update their access permissions for managed document data based on updated personnel information. [Figure 13] Figure 13 shows an example screen that extracts documents where the person involved is not affiliated with the organization and prompts the user to update their viewing permissions. [Figure 14] Figure 14 shows an example of a screen where a party approves setting viewing permissions for specific users on document data. [Modes for carrying out the invention]

[0010] The embodiments of this disclosure will be described below with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference numerals, and repeated explanations are omitted. The following embodiments are not intended to unduly limit the content of this disclosure as described in the claims. Not all components shown in the embodiments are necessarily essential components of this disclosure. Also, each drawing is a schematic diagram and is not necessarily a strict illustration.

[0011] <1.1 System Configuration Diagram> Figure 1 shows the configuration of System 1.

[0012] The system 1 shown in FIG. 1 includes a server 20 for contract conclusion and document management services, a user's terminal 10, a server 93 for document review services, a server 94 for messaging services, a server 95 for artificial intelligence (large language model) services, and a server 96 for personnel management services. These devices are communicatively connected via a network 80.

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

[0014] The server 20 is a device for providing a service for contract conclusion by electronic contract and for providing a service for managing document data concluded by electronic contract. In the system 1, the contract conclusion service and the service for managing document data provided by the server 20 may be provided by different devices or different operators. For example, the server 20 provides a document management service, and in addition to the data of the contract signed with an electronic signature, it may optically read the contract signed on paper to extract the contract period, the presence or absence of automatic renewal of the contract, etc., and manage it as management information together with the read data of the contract. Thereby, when the expiration time of the contract period arrives, the user can be notified.

[0015] Also, the server 20 is a server that provides a service for supporting operations such as submission of requests for approval in an organization (business company, etc.) conducting business activities. The server 20 provides a service to the user, for example, enabling the design of a workflow for obtaining budget approval from multiple users.

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

[0017] Server 92 of the business support system service provides users with tools that can be used for the organization's business operations. Server 92 of the business support system service provides users with a system for submitting approval requests as part of the organization's business operations.

[0018] The document review service server 93 accepts document data such as contracts and term sheets that define contract terms, and provides users with information on whether each clause is advantageous or disadvantageous to the company, whether there are any missing clauses, and the importance of the review items, thereby supporting the review of the document data. The document review service server 93 provides the above review support service using rule-based or pre-trained models. As a rule-based approach, for example, it may be possible to perform rule-based reviews of document data by associating specific wording or expressions with pre-defined information on whether the conditions are advantageous or disadvantageous, and explanations. Alternatively, for example, it may be possible to provide the above review service by generating a pre-trained model that responds with review results to document data input, using data from expert reviews of contracts, term sheets, etc., as training data. Furthermore, 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 the user.

[0019] The messaging service server 94 provides tools for communication between users via text, voice, images, etc. The messaging service server 94 accepts posts from each user, for example, in a chat format, thread format, or other format, and allows users to view posts according to their message viewing permissions. The messaging service server 94 may also provide users with means of communication such as email.

[0020] Server 95 of the Large-Scale Language Model Service is a server that executes language processing tasks using language models built through learning processes including artificial intelligence (AI). An LLM (Large Language Model) is a model that has been pre-trained on large amounts of data (such as text data), for example, a large amount of web content on the internet, or a large amount of data stored in a designated database, and can perform various language processing tasks by being given a task.

[0021] The AI ​​service server 95 (sometimes referred to as the "large-scale language model service server 95") accepts prompt input in the form of text, images, audio, etc., and generates and responds with answers to those prompts. Examples of LLMs include GPT-3, GPT-4, and GPT-4o developed by OpenAI, and BERT developed by Google.

[0022] The human resources management service server 96 provides services to users, such as the human resources department, within organizations conducting business activities, supporting recruitment, labor management, and other related tasks. For example, the human resources management service server 96 manages a list of employees and updates the list whenever an employee joins or leaves the company. The human resources management service server 96 also holds information related to human resources management, such as employee salaries and employee evaluations. Server 20 may also obtain the list of employees by communicating with the human resources management service server 96 and update the user database 211, which will be described later.

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

[0024] Terminal 10 can be implemented, for example, as follows: • Handheld mobile devices such as smartphones and tablets • Stationary PC (Personal Computer), Laptop PC • Wearable devices worn by the user (watch-type, glasses-type, etc.) Terminal 10 includes a communication interface (IF) 12, an input device 13, an output device 14, memory 15, storage 16, and a processor 19.

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

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

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

[0028] Memory 15 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0029] Storage 16 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0030] The processor 19 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

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

[0032] Communication IF22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0033] Input / Output IF23 functions as an interface between an input device for receiving user input operations and an output device for presenting information to the user.

[0034] Memory 25 is for temporarily storing programs and data processed by programs, etc., and is a volatile memory such as DRAM (Dynamic Random Access Memory).

[0035] Storage 26 is for storing data, and can be, for example, flash memory or an HDD (Hard Disk Drive).

[0036] The processor 29 is hardware for executing the instruction set described in the program, and consists of an arithmetic unit, registers, peripheral circuits, etc.

[0037] <1.2 Functional Configuration of Server 20> Figure 2 shows the configuration of server 20. As shown in Figure 2, server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0038] The communications unit 201 performs processing to enable the server 20 to communicate with external devices.

[0039] The memory unit 202 stores various databases, such as the user database 211, the contract management database 212, the document management database 213, the approval request database 214, and the review history database 215.

[0040] User database 211 is a database for managing users.

[0041] User database 211 contains information necessary for using the services provided by server 20, such as the user's name and employee number. Further details will be provided later.

[0042] The contract signing management database 212 is a database that manages the contract signing process carried out by the electronic contract service provided by server 20. Further details will be described later.

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

[0044] The approval request database 214 is a database that manages applications for approval, such as those for concluding contracts. For example, server 20 communicates with server 92 of the business support system service to obtain information related to the approval request and update the approval request database 214. Further details will be described later.

[0045] Review History Database 215 is a database that manages the history of reviews performed on document data such as contracts. Further details will be provided later.

[0046] The control unit 203 is realized when the processor 29 reads a program stored in the memory unit 202 and executes instructions contained in the program. By operating according to the program, the control unit 203 performs the functions shown as the reception control module 2041, transmission control module 2042, user management module 2043, contract signing processing module 2044, document management module 2045, approval processing module 2046, authority management module 2047, and review processing module 2048.

[0047] The receive control module 2041 controls the process by which the server 20 receives signals from external devices according to a communication protocol.

[0048] The transmission control module 2042 controls the process by which the server 20 transmits signals to external devices according to a communication protocol.

[0049] The user management module 2043 is a module for managing information for each user using System 1. Specifically, the user management module 2043 accepts registration of each user's information and updates the user database 211.

[0050] The contract signing module 2044 controls the process of parties approving document data as part of the process of concluding a contract electronically. Specifically, the contract signing module 2044 notifies each user approving the document data and updates the contract signing management database 212 in response to the operation of approving the document data.

[0051] The document management module 2045 controls the process of managing document data by referring to the document management database 213. Specifically, based on the contract period information set in the document data, the document management module 2045 notifies the user of whether to renew the contract upon the expiration of the contract period, and updates the document management database 213 in response to user actions (such as renewing the contract).

[0052] The approval processing module 2046 receives an operation from a user to submit an approval request and controls the process by which approvers approve the request. Specifically, the approval processing module 2046 notifies each user who approves the request and updates the approval request database 214 in response to the operation to approve the request.

[0053] The access control module 2047 is a program module that manages access permissions for document data managed in the document management database 213.

[0054] More specifically, the access control module 2047 is a program module that retrieves personnel information managed by the personnel management service server 96 and notifies the user to review their access permissions to document data managed in the document management database 213 when there are changes in the organization's members (such as hiring, leaving, transfers, or organizational restructuring).

[0055] The review processing module 2048 records reviews of document data subject to review (for example, each clause of a contract is subject to review) and updates the review history database 215. The review processing module 2048 communicates with the document review service server 93 and sends the document data subject to review to the server 93, causing the server 93 to perform the review process. The module receives the results and updates the review history database 215. The review processing module 2048 also accepts operations from users performing reviews to review document data (for example, operations to input comments in association with the entire contract or each clause of the contract) and updates the review history database 215.

[0056] <1.3 Configuration of Terminal 10> Figure 3 shows the configuration of terminal 10.

[0057] As shown in Figure 3, terminal 10 includes multiple antennas (antenna 111, antenna 112), communication units corresponding to each antenna (first communication unit 120, second communication unit 121), 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 storage unit 180, and a control unit 190. Terminal 10 also has functions and configurations not specifically shown in Figure 3 (for example, a battery for maintaining power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in Figure 3, each block included in terminal 10 is electrically connected by a bus or the like.

[0058] Antenna 111 radiates signals emitted by terminal 10 as radio waves. Antenna 111 also receives radio waves from space and provides the received signals to first communication unit 120.

[0059] Antenna 112 radiates signals emitted by terminal 10 as radio waves. Antenna 112 also receives radio waves from space and provides the received signals to the second communication unit 121.

[0060] The first communication unit 120 performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 111 in order to communicate with other wireless devices. The second communication unit 121 also performs modulation and demodulation processing, etc., for the terminal 10 to transmit and receive signals via the antenna 112 in order to communicate with other wireless devices. The first communication unit 120 and the second communication unit 121 are a communication module that includes a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, etc. The first communication unit 120 and the second communication unit 121 perform modulation and demodulation, frequency conversion, etc., of the wireless signals transmitted and received by the terminal 10, and provide the received signal to the control unit 190.

[0061] The input device 130 has a mechanism for receiving user input operations. Specifically, the input device 130 is configured as a touchscreen and includes a touch-sensitive device 131. The touch-sensitive device 131 receives user input operations of the terminal 10. The touch-sensitive device 131 detects the user's contact position with the touch panel, for example, by using a capacitive touch panel. The touch-sensitive device 131 outputs a signal indicating the user's contact position detected by the touch panel to the control unit 190 as an input operation.

[0062] The display 132 displays data such as images, videos, and text in accordance with the control of the control unit 190. The display 132 is implemented by, for example, an LCD or an organic EL display.

[0063] The audio processing unit 140 modulates and demodulates the audio signal. The audio processing unit 140 modulates the signal received 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 implemented, for example, by an audio processing processor. The microphone 141 receives an audio input and provides the audio signal corresponding to that audio input to the audio processing unit 140. The speaker 142 converts the audio signal received from the audio processing unit 140 into sound and outputs the sound to the outside of the terminal 10.

[0064] 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. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and the current location of the terminal 10, which is equipped with a GPS module, is detected based on the received signals.

[0065] Camera 160 is a device that receives light using a photodetector and outputs it as an image. Camera 160 is, for example, a depth camera that can detect the distance from camera 160 to the object being photographed.

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

[0067] The storage unit 180 is composed of, for example, 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.

[0068] The control unit 190 controls the operation of the terminal 10 by reading the program stored in the memory unit 180 and executing the instructions contained in the program. The control unit 190 is, for example, an application processor. By operating according to the program, the control unit 190 performs 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 memory control unit 195.

[0069] The operation reception unit 191 processes input operations from the user to an input device such as a touch-sensitive device 131. Based on the coordinate information of the touch-sensitive device 131 where the user's finger or the like has made contact, the operation reception 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.

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

[0071] The data processing unit 193 performs calculations on the data received as input by the terminal 10 according to the program and outputs the calculation results to memory or other locations.

[0072] The notification control unit 194 performs the following processes: displaying the display image on the display 132, outputting sound to the speaker 142, and generating vibrations.

[0073] The memory control unit 195 controls the storage of data to the memory unit 180.

[0074] The various types of information stored by the memory unit 180 will now be explained. In a given situation, the memory unit 180 stores various types of information, such as user information 181.

[0075] User information 181 is information about a user who uses the services of server 20. User information 181 includes, for example, the user's employee number, name, and other information.

[0076] <2 Data Structure> Figure 4 shows the data structure of the user database 211. The user database 211 includes the following fields: "User ID", "Business ID", "Name", "Email Address", "Department", "Position", "Date of Hiring", "Date of Leaving", "Qualifications Held", "Transfer History", and "Permission Setting Availability".

[0077] The "User ID" field is information that identifies each user.

[0078] The "Business ID" field contains information that identifies each business.

[0079] The "Name" field contains the user's name information.

[0080] The "Email Address" field is information that identifies the user and serves as their contact information.

[0081] The "Department" field contains information about the user's department.

[0082] Specifically, the "Department" field may include the following information about the department to which the user belongs: • Departments that do not primarily handle legal affairs, such as business divisions and sales divisions. • Departments that primarily handle legal affairs, such as legal affairs departments and intellectual property departments. The "Job Title" field contains information about the user's job title.

[0083] The "Date of Joining" field contains information about the date the user joined the organization.

[0084] The "Resignation Date" field contains information about the date the user left the organization.

[0085] The "Qualifications Held" item contains information about the qualifications the user holds.

[0086] Specifically, the item "Qualifications Held" includes the following information regarding the qualifications held by the user. • Qualifications that demonstrate the expectation of possessing the knowledge necessary to review contracts, similar to that of a lawyer. • Qualifications that demonstrate knowledge of business activities, such as a Certified Management Consultant for Small and Medium Enterprises. • Qualifications such as Certified Public Accountant and Tax Accountant, which indicate that the individual possesses the necessary knowledge in accounting, taxation, and related fields. The "Transfer History" item contains information about the user's history of departmental transfers within the organization.

[0087] More specifically, the "Transfer History" item includes information such as the date and time the user transferred departments, information about the new department, and the position held after the transfer.

[0088] The item "Permission Setting Availability" refers to the extent to which user viewing permissions can be set for document data managed in the document management database 213.

[0089] The item "Permission Setting Availability" may include the following information regarding the scope of document data viewing permissions that can be set: • Specifying the department that manages the document data for which permissions can be set. • The type of permission to set (view only, download allowed, whether or not to set up notifications when the contract period for document data expires, etc.) • The scope of users who can set permissions (for example, can permissions be set for users in the same department as the user who has the permission, or for users across departments) Here, the permissions shown in the item "Permissions can be set" may be set in correspondence with the user's job title information. For example, server 20 may detect that a user has become a manager, such as by communicating with the personnel management service server 96 or by referring to a personnel information file managed within the organization, and update the item "Job Title" in the user database 211. When server 20 detects this, it may also update the information in the item "Permissions can be set" for a user within a predetermined range according to their job title (such as the range of users who can have permissions set and the types of permissions that can be set). Figure 5 shows the data structure of the contract management database 212. The contract management database 212 includes the following items: "Contract ID", "Sender ID", "Recipient ID", "Contract Target Data", "First Email Address", "Second Email Address", "Sending Date and Time", "User Signature Date and Time", "Contract Completion Date and Time", and "Status".

[0090] The item "Contract Signing ID" is information that identifies each step in the contract signing process.

[0091] Specifically, the item "Contract ID" includes identification information issued by server 20 when a new registration is accepted for the process of concluding an electronic contract by specifying an approver for document data that is subject to approval by the parties.

[0092] The "Sender ID" field is information that identifies the party who will be sending the document data when the party approves it.

[0093] Specifically, the item "Sender ID" may be associated with information about a business operator (Business ID) or information about a user (User ID) managed in the user database 211.

[0094] The "Recipient ID" field is information that identifies the recipient when they approve document data.

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

[0096] The item "Data Subject to Agreement" refers to the document data that the parties are required to approve.

[0097] Specifically, the item "Data subject to conclusion" refers to data (files such as PDFs) of transaction documents such as contracts, application forms, and quotations.

[0098] The item "First Email Address" is information that identifies the user who will be the sender in the process of concluding a contract by approving document data, and is the email address that serves as the contact address for that user.

[0099] Specifically, the item "First Email Address" is the email address of the user who performs the operation of sending the document data as the sender.

[0100] The item "Second Email Address" is information that identifies the user who approves the document data as the recipient in the process of concluding a contract by approving the document data, and is the email address that serves as the contact address for that user.

[0101] Specifically, the item "Second Email Address" is the email address of the user who approves the document data as the recipient. Note that there may be multiple users approving the document on each party's side, and if the user sending the document data specifies the email addresses of multiple users who will approve the document data, the contract management database 212 will also manage each of the specified email addresses.

[0102] The "Sending Date and Time" field contains information about the date and time when the sender, a user, initiated the process of requesting approval of the document data from each user.

[0103] The "User Signature Date and Time" field contains information about the date and time when the user performed an approval operation on the document data.

[0104] Specifically, the item "User Signature Date and Time" includes information about the timing when a user who has been requested to approve the document data reviews the document data, approves it, and the server 20 accepts this operation, thereby electronically signing the document data. The server 20 electronically signs the document data each time a user performs the approval operation, and stores the timing information in the signing management database 212.

[0105] The item "Date and Time of Contract Completion" contains information about the date and time when the contract was completed.

[0106] Specifically, the item "Contract Completion Date and Time" is recorded in the contract management database 212 when the contract is concluded using the electronic contract service provided by server 20. The contract is considered concluded when all users designated to approve the document data complete the approval process.

[0107] The "Status" field indicates the stage in the contract signing process.

[0108] Specifically, the item "Status" may include the following as stages in the contract signing process: • Before sending: Indicates that the document data has been registered on server 20 by the sender, but has not yet been sent to the recipient. • In Progress: Indicates that the document data has been sent, but approval by each user has not yet been completed. • Completed: Indicates that the contract has been finalized. • Rejected, Returned: Indicates a situation where the contract was not finalized due to circumstances such as the user not approving the document data, or a timeout occurring after a certain period of time had elapsed before approval was complete. Figure 6 shows the data structure of the document management database 213. The document management database 213 includes the following items: "Document Management ID", "Contract Signing ID", "Document Title", "Contract Start Date", "Contract Expiration Date", "Automatic Renewal Status", "Viewing Permission", and "Restricted Viewing Permission".

[0109] The "Document Management ID" field is information that identifies each document data being managed.

[0110] The "Contract Signing ID" field is information that identifies each contract signing procedure performed by the parties to approve the document data.

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

[0112] The "Document Title" field contains information about the title of the document data being managed.

[0113] Specifically, the item "Document Title" may be a term used as the type or name of a contract, such as a confidentiality agreement, a sales agreement, or a license agreement.

[0114] The item "Contract Start Date" is the information shown in the document data as the contract start date.

[0115] Specifically, the item "Contract Start Date" may be set to the following value: • When the contract is finalized, Server 20 reads the contract start date from the contract data. • Information received from the user as the contract start date The same applies to the following items: "Contract Expiration Date" and "Automatic Renewal Status".

[0116] The item "Contract Expiration Date" is the information shown in the document data as the contract's expiration date.

[0117] The item "Automatic Renewal Status" indicates, in the document data, whether or not the contract period will be automatically extended (automatically renewed) without the parties specifically renegotiating a new contract upon the expiration of the contract period.

[0118] The item "Viewing Permissions" contains information about users who have viewing permissions for documents (e.g., contracts) managed in the document management database 213.

[0119] The item "Viewing Permissions" may include the following users who have permission to view document data: - Users recorded in the contract management database 212 as users who approve document data. Note that the server 20 does not store information of users with viewing privileges in the document management database 213, but may identify users with viewing privileges for document data by referring to the users who approved the document data in the contract management database 212. • Information about the organizational departments (divisions, etc.) that can access document data. For example, a user belonging to the sales department may have access to certain document data. • Information about organizational positions that grant access to document data. For example, there may be document data that can only be viewed by executive officers, department heads, and other executives, depending on their position and hierarchy. For instance, members without an executive position may not be able to access the data, while members at the department head level or higher may be able to. • In the contract signing service provided by Server 20, in addition to the user who approves the document data, the server also accepts the designation of users to whom the data will be shared once the contract is signed. These designated users (the users to whom the data is transferred) are the ones specified. For example, in the case of minutes of a board meeting, a director may approve the document data, and then share the approved minutes with other users such as executive officers. • Users who have permission to view document data may include other users designated by users who approve document data, users who have permission to view document data, etc. (For example, a user who already has permission to view document data may approve granting viewing permission to a new user, thereby setting viewing permission for that new user.) The item "Restricted Viewing Permissions" refers to information about users who have restricted viewing permissions for documents (e.g., contracts) managed in the document management database 213, and the scope of information they can view.

[0120] The item "Restricted Viewing Permissions" may include the following as restrictions on the scope of what can be viewed: • Information about users who are allowed to view document data within a limited scope. It is also possible to retain information that can be referenced in association with the user's information, as follows: • The scope of document data that can be accessed. For example, clauses and certain wording of a contract (such as the amount or license scope) may not be accessible, while information necessary for managing the contract, such as the contract period and contract date, may be accessible. This allows even those who are not the administrator of the contract to search for the contract, but within a limited scope where they can access information necessary for managing the contract. Regarding document data, the scope of what can be referenced may be limited to the information of the parties involved. This allows for the search for necessary contracts based on the parties involved, even if the text of the contract itself is not accessible, and makes it possible to ascertain that a contract was even concluded. • The period during which document data can be accessed. For example, it may be possible to allow searching of document data for a limited period. Figure 7 shows the data structure of the approval request database 214. The approval request database 214 includes the fields "Approval Request ID", "Applicant ID", "Approver ID", "Application Date", "Approval Date", "Application Details", and "Contract ID".

[0121] The item "Approval Request ID" is information that identifies each approval request.

[0122] The "Applicant ID" field is information that identifies the user who submitted the approval request.

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

[0124] The "Approver ID" field is information that identifies the user who is the approver of the proposal.

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

[0126] The "Application Date" field contains information about the date and time when the system received the operation from the user who will be submitting the approval request data, in order to request approval of the approval request data from each user.

[0127] The "Approval Date" field contains information about the date and time when the user approved the data in the approval request.

[0128] The item "Application Details" contains information that shows the content of the approval request.

[0129] Specifically, the item "Application Details" includes the following contents of the approval request: • Conclusion of a contract • Budget approval • Expense claim The item "Contract Signing ID" is information that identifies each step in the contract signing process.

[0130] Specifically, the item "Contract Signing ID" may be associated with information (Contract Signing ID) that identifies each contract signing procedure, which is managed in the contract signing management database 212. This links the approval application data in the approval application database 214 with the contract signing data in the contract signing management database 212.

[0131] Figure 8 shows the data structure of the review history database 215. The review history database 215 includes the following items: "Review ID", "Document Data", "Document Management ID", "Review Date and Time", "Reviewing User", "Review Content", and "Review Requester's Rating".

[0132] The "Review ID" field is information that identifies each review performed on the document data.

[0133] The item "Document Data" contains information about the document data that will be reviewed.

[0134] The "Document Management ID" field is information that identifies each document data being managed.

[0135] Specifically, the item "Document Management ID" may be associated with information (Document Management ID) that identifies each document data managed in the document management database 213.

[0136] The "Review Date and Time" field contains information about the date and time the review was performed.

[0137] The item "Reviewing User" contains information about the user who conducted the review.

[0138] The item "Review Content" contains information that shows the results of the review.

[0139] Specifically, the item "Review Content" may include the following as a result of the review: • Results of the review by server 93 of the document review service (e.g., advantages / disadvantages of conditions, importance, proposed revisions) • Comments and suggested revisions entered by users (including information about the user who entered the review comment) The item "Review Requester's Rating" is information that shows the user's rating of the reviewer's review content.

[0140] Specifically, the item "Review Requester's Rating" includes the results of the user who requested the review evaluating the reviewer based on the actions they took with respect to the review results, and may include the following: • The user who requested the review sets a score for the review results. • The number of "likes" and other reactions on posts made to contact users about reviewing a product via messaging tools, etc. <3 operations> Figure 9 shows the process flow for prompting the update of access permissions for managed document data based on updated personnel information.

[0141] Server 20 stores signed contracts and access permissions for those contracts in the document management database 213. The document management module 2045 receives requests from users to view signed contracts and, in response to the request, allows the user to view the signed contracts according to their access permissions.

[0142] In step S921, the authorization management module 2047 of server 20 refers to a database of the organization's members (for example, a database managed by the human resources service server 96, or a user database 211 updated based on that database) and detects if there has been a change in the members' information. For example, the authorization management module 2047 may detect if a member's department has changed, a member's job title has changed, there has been an increase in members (new hires), or a decrease in members (departures). For example, the human resources department of the organization may periodically register information on members who have changed departments or newly hired members in the human resources service server 96, and based on this registered information, it may disseminate information about personnel changes within the organization. The authorization management module 2047 may also retrieve such registered information.

[0143] In step S923, the authorization management module 2047 of server 20 extracts relevant document data from the document data managed in the document management database 213 based on the information of the member whose information has changed. For example, the following may occur: • Contracts managed by the department to which a new member will belong when a new member joins the organization. For example, among the contracts managed by the legal department, some contracts may be made available for viewing by a new member joining the legal department, while others, such as M&A contracts, may not be available due to their high level of confidentiality. • When a member leaves an organization's department (e.g., transfers to another department, resigns), the contracts that the member can access (contracts the member has access to, contracts the member has access to in connection with their previous department, etc.) are specified. For example, a member working in the legal department may have access to contracts managed by the legal department, but upon transferring from the legal department to another department, their access to contracts managed by the legal department may be revoked. When an organization member's position changes, the documents they can access or cannot access may change depending on their position. For example, a promotion in rank may increase the amount of documents they can access. Conversely, being relieved of a position may decrease the range of documents they can access. In step S925, the authorization management module 2047 of server 20 notifies the user to review their viewing permissions for the extracted document data. For example, the authorization management module 2047 refers to the document management database 213 for the extracted document data and sends the above notification to users who have viewing permissions (e.g., users who approved the document data). In this way, the authorization management module 2047 notifies the user about updating the viewing permissions for the concluded contracts based on the information referred to in step S921.

[0144] Here, the user database 211 stores the member database, which manages the affiliations of members within the organization. The authorization management module 2047 obtains information indicating that the member database has been updated as information indicating that there has been a change in step S921. The authorization management module 2047 may also notify about the update of access permissions in response to the update of the member database.

[0145] Here, in step S923, the authorization management module 2047 may refer to a database of members, such as the user database 211, and extract the concluded contracts for which members of each department have viewing rights, for each department where members have changed within the organization. In step S925, the authorization management module 2047 may notify the members of the department of the update of the viewing rights for the extracted concluded contracts. The server 20 stores information (item "Permission Setting Availability") of members who can set viewing rights for concluded contracts for each department within the organization in the user database 211. The authorization management module 2047 may present the extracted concluded contracts to members who can set viewing rights within the department, while not presenting the extracted concluded contracts to members who cannot set viewing rights within the department.

[0146] Server 20 manages member databases such as user database 211, which contain information on new members joining the organization and information on members leaving the organization. In step S925, the authorization management module 2047 may accept reservations for viewing rights to signed contracts for at least one of the new members or the member leaving, depending on the timing of joining or leaving. That is, the authorization management module 2047 may reserve the setting of viewing rights to document data for new members and members leaving, and then activate the setting depending on the timing of joining (joining the company) for new members and the timing of leaving (transfer, resignation) for members leaving.

[0147] In step S911, terminal 10 receives an operation from the user to set viewing permissions for the extracted document data.

[0148] In step S927, the authorization management module 2047 of server 20 updates the document management database 213 based on the accepted viewing permission settings.

[0149] Here, server 20 manages information about the timing of transfers of members who are changing departments in a member database such as user database 211. When the authorization management module 2047 changes the access rights to signed contracts of a member who is transferring departments, it may delete the access rights the member had in their previous department after a predetermined period has elapsed following the transfer. This makes it possible to allow access to signed contracts during the handover period associated with the transfer, while preventing access to those contracts once the handover is expected to be complete.

[0150] Server 20 manages information about the roles of its members in a member database such as the user database 211. The authorization management module 2047 may change the access rights to signed contracts according to the member's role when the member's role changes.

[0151] Server 20 stores information about clients to whom the organization outsources its work in a member database such as the user database 211, and the outsourcing period information is managed as part of the client information. The authorization management module 2047 may set viewing permissions for contracts concluded within the outsourcing period based on the client's outsourcing period information, and may revoke viewing permissions when the outsourcing period has expired.

[0152] Here, concluded contracts managed in the document management database 213 are concluded electronically when the parties to the contract approve the contract and affix their electronic signatures. The conclusion processing module 2044 notifies the parties to the concluded contract of a link information to view the concluded contract once the electronic conclusion is complete. The authorization management module 2047 may grant the user permission to view the concluded contract, and the document management module 2045 may be configured to allow the user to view the concluded contract based on the link information.

[0153] Figure 10 shows the process flow for extracting documents where the parties involved are not affiliated with the organization, and prompting them to update their viewing permissions.

[0154] In step S1021, the authorization management module 2047 of server 20 refers to a database of the organization's members, such as the user database 211, and the document management database 213, and extracts document data for which the currently belonging members do not have viewing permissions set. For example, it is possible that all users who performed the operation to approve the document data have left the organization, for example, by resigning.

[0155] Server 20 stores a member database, similar to the user database 211, which manages the affiliations of members within an organization. This member database manages information about currently affiliated members and information about members who have been affiliated in the past.

[0156] The authorization management module 2047 extracts contracts from the document management database 213 that have been concluded and for which viewing privileges are not currently granted to any member, but are instead granted to a member who was formerly a member.

[0157] In step S1023, the authorization management module 2047 of server 20 searches for information indicating the process leading to the approval of the document data of the contract to be reviewed. For example, the authorization management module 2047 searches for information on the document data of the contract to be reviewed (information on the parties to the document data, information on when the contract was concluded, etc.) based on member posts stored on the messaging service server 94, as well as emails, etc. The authorization management module 2047 obtains a summary of the process leading to the approval by having the search results summarized, for example, by the large-scale language model service server 95.

[0158] Here, the server 20 may be configured in its storage unit 202 to store information about the circumstances leading to the conclusion of a contract, in association with the concluded contract. For example, as described above, the results of searching the messaging service server 94, email, etc., based on the information in the document data may be stored in the document management database 213 in association with the document data.

[0159] In step S1025, the authorization management module 2047 of the server 20 notifies the user to review their viewing permissions by sending the document data extracted in step S1021, along with a summary of the history, to the terminal 10. For example, the server 20 may maintain a setting to notify specific users (e.g., users in the general affairs department, legal department, etc.) about such contracts subject to review. In this way, the authorization management module 2047 notifies the user about updating the viewing permissions for the extracted contracts subject to review. Specifically, the authorization management module 2047 refers to the information on the history leading to the conclusion of the contract associated with the extracted contracts subject to review, and notifies the user of the summary of the history along with the contracts subject to review.

[0160] In step S1011, terminal 10 displays information about the process leading to the approval of the document data and accepts an operation to set viewing permissions for the document data.

[0161] Figure 11 shows the process flow for which parties approve the setting of viewing permissions for specific users on document data.

[0162] In step S1121, the authorization management module 2047 of the server 20 accepts an operation requesting that a party to the document data (for example, a user who is set to have viewing privileges in the "Viewing Privileges" field in the document management database 213, or a user who has approved the document data in the signing management database 212) approve the setting of viewing privileges for a specific user who does not have privileges set for the document data.

[0163] In step S1123, the authorization management module 2047 of server 20 notifies the parties to the document data whether they approve granting viewing rights to a specific user of the document data, and records the results of each party's actions in the document management database 213. In this way, the authorization management module 2047 may request a user who has viewing rights to approve an operation to grant viewing rights to a specific user who does not have viewing rights to the concluded contract. The authorization management module 2047 may also request a user who has viewing rights to approve an operation to grant viewing rights to a specific user, while restricting the scope of viewing of the concluded contract and enabling searching.

[0164] In step S1125, the authorization management module 2047 of server 20 notifies a specific user that access has been granted access by accepting an operation from each party approving the setting of access rights to view document data for that specific user. In this way, the authorization management module 2047 grants access rights to a specific user by accepting an operation from a user who has access rights to view the concluded contract approving the granting of access rights to that specific user.

[0165] The permission management module 2047 may also provide a function to search for signed contracts based on restrictions by accepting an operation from a user who has permission to view signed contracts to authorize a search for a specific user while restricting the scope of what that user can view.

[0166] In step S1111, terminal 10 accepts a request from a specific user who has been authorized to be granted viewing permission to search for document data based on the scope of what can be viewed.

[0167] In step S1127, the server 20 responds to the terminal 10 with the search results for document data based on the scope that a specific user can view.

[0168] In step S1113, terminal 10 displays the search results for document data based on the scope of what it can view.

[0169] <4. Screen Example> Figure 12 shows an example screen that prompts the user to update their access permissions for managed document data based on updated personnel information.

[0170] Operation screen 1200 is an operation screen that accepts operations to set viewing permissions for concluded contracts.

[0171] The account display area 1202 is the area that displays the user's account information.

[0172] More specifically, the account display area 1202 is the area that displays the user's name, etc.

[0173] Settings screen 1204 is the screen for setting viewing permissions for signed contracts.

[0174] In the illustrated example, settings screen 1204 displays an example of a change in the organization's members, such as a member transfer or new hire, and prompts the user to change the viewing permissions for signed contracts.

[0175] The confirmation operation unit 1206 is an operating component that accepts requests from users to confirm contracts that are available for viewing within their respective departments.

[0176] More specifically, the confirmation operation unit 1206 is an area that displays a list of contracts that the user has permission to view, in response to user actions. This makes it even easier to confirm which concluded contracts require changes in viewing permissions in response to changes such as member transfers or new hires.

[0177] The authorization setting operation unit 1208 is an operation component that, when there is a change in the organization's members, displays the details of the change for the relevant member, displays the relevant contracts, and accepts operations to change the viewing permissions for each contract.

[0178] The authorization setting operation unit 1208 may include the following as information to be displayed in association with a member: • Member's name, date of joining, date of leaving • Details of changes as a member of the organization (e.g., details of a transfer: previous department, new department, and timing of the transfer) • Contracts that have access rights before any changes occur in the organization's members' information (for example, before a transfer). It may also be possible to allow users to change their access rights for each contract. • After information about the organization's members changes (for example, after a transfer), it may be possible to set viewing permissions for some of the contracts managed by the department to which the member belongs (for example, setting viewing permissions for some contracts managed by the department, while setting permissions for contracts that are highly confidential and therefore not allowed to be viewed). The list display operation unit 1210 is an operation component that displays a list of related contracts (contracts for which viewing rights were granted before the transfer, and contracts to be managed by the department after the transfer) on a per-member basis of the organization, and accepts operations to set viewing rights for each contract.

[0179] The reservation operation unit 1212 is an operating component that accepts operations to set viewing permissions for contracts for new members of an organization, while displaying information such as the department to which they are expected to belong.

[0180] More specifically, the reservation operation unit 1212 is an operating component that, in response to user operations, displays a list of contracts managed by the department, information of newly assigned members (department to which they belong, job title, etc.), and accepts reservations for setting viewing permissions for contracts. Figure 13 shows an example screen that extracts documents where the person involved is not affiliated with the organization and prompts the user to update their viewing permissions.

[0181] The settings screen 1214 is an operation screen that accepts requests to set viewing permissions for contracts managed in the document management database 213 for which no users with the necessary permissions are currently registered.

[0182] The authorization setting operation unit 1216 is an operation component that displays information about contracts for which the authorized user is not affiliated with the organization, and accepts an operation to set the user to whom the user is granted viewing rights for said contract.

[0183] The authorization setting operation unit 1216 may display contract information, including the following: • Type of contract (e.g., M&A contract, non-disclosure agreement) • Contracting parties • The person responsible for the contract (the user who had access privileges; information including the user's name, department, and the date they left the organization). • The circumstances surrounding the conclusion of the contract (corresponding to Step S1025, etc.) • Setting viewing permissions (the information specified for the user to whom viewing permissions will be newly granted for the contract) The history confirmation operation unit 1218 is an operation component that accepts requests to display the history leading to the conclusion of the selected contract.

[0184] The history confirmation operation unit 1218 corresponds to the processes in steps S1025, S1011, etc.

[0185] The reservation operation unit 1220 is an operating component that extracts contracts for which there will no longer be users with viewing rights when a member who is leaving the organization due to retirement or other reasons actually leaves, and accepts an operation to specify (reserve the timing of granting) the user to whom viewing rights will be granted.

[0186] Figure 14 shows an example of a screen where a party approves setting viewing permissions for specific users on document data.

[0187] The approval request operation screen 1222 is an operation screen that accepts the operation of requesting approval from a user who already has viewing rights to grant viewing rights to a contract to a specific user.

[0188] The authorization designation unit 1224 is an operating component that accepts the designation of a user to whom new viewing rights will be granted for the contract, and the designation of the scope of viewing rights to be set for that user.

[0189] In the illustrated example, the authorization unit 1224 displays information about the department to which a user belongs and the period during which they joined the department for whom viewing privileges are newly granted. Furthermore, the scope of what the user can view is limited to administrative information such as the contract name and contract period, and the main text of the contract cannot be viewed. As a result, although the scope of what the newly granted viewing privileges can view is limited, the user can still search for the contract. Being able to search for the contract makes it much easier to prompt the user to review the contents of the contract by contacting the user who has viewing privileges.

[0190] The approval request operation unit 1226 is an operation component that receives an operation requesting a user who already has viewing rights (for example, a user who performed the operation of approving when concluding a contract) to approve the setting of new viewing rights for a specific user.

[0191] More specifically, the approval request operation unit 1226 is an operation component that, in response to user operations, presents the user who received the approval request with information about the contract to which new viewing rights will be granted, information about the user requesting approval to grant viewing rights, and information about the scope of any restrictions on the scope of viewing, if any. It then processes the operation to accept an approval request from a user who can approve it (for example, a user who already has viewing rights, or a user who performed an approval operation when concluding a contract).

[0192] <Variation> In addition to the embodiments described above, the following may also be used.

[0193] (1) System configuration: In the above embodiment, it was explained that each service provider provides their respective services using devices such as the server 92 for the business support system service, the server 93 for the document review service, the server 95 for the large-scale language model service, and the server 96 for the personnel management service. However, it is also possible that one service provider may provide multiple services. For example, one service provider may provide contract signing services, document management services, and business support (approval application) services.

[0194] (2) Types of document data: In the above description of the embodiment, the document data mainly consisted of examples of contracts. However, the document data may also include documents such as the following: These are documents related to labor relations and recruitment, primarily handled by the human resources department of an organization. Examples include employment contracts and notices of working conditions that employers present to employees during the hiring process.

[0195] (3) Persons with access rights to document data: In the description of the above embodiment, as shown in the example in Figure 6, examples of persons who have permission to view document data were described, such as the user who performed the operation to approve the document data in the conclusion of an electronic contract (each user approves and signs the document data) (contract management database 212), and the users designated by that user (users who are shared with the fact that the document data has been approved).

[0196] In addition, users who have reviewed the document data (review history database 215) may be designated as persons with viewing privileges for the document data. For example, the user who performed the review and the user who requested the review may perform the operation of setting the document data as a sealed letter. These users may be aware of the contents related to the conclusion of the contract during the review.

[0197] Additionally, the user who submitted the approval request to approve the document data may be designated as the person with access rights to view the document data (in the approval request database 214, the item "Contract ID" is associated with the document data for contract conclusion, i.e., the approval request ID).

[0198] Furthermore, server 20 may allow the designation of individuals with access rights to document data, such as accounting personnel and accounting professionals (certified public accountants). For example, it may be necessary to verify transaction data related to deposits and withdrawals, or settlement amounts related to court settlements, even if the contract details (payment amount, payment method, etc.) stipulated in the contract are confidential, because such verification is required for business purposes. Additionally, access rights may be granted to these individuals temporarily until the purpose of granting access rights is achieved. For example, as explained in the example in Figure 11, a user may be asked to request approval from a user who already has access rights to set access rights, along with the purpose of viewing the contract. The temporary access rights may be terminated when the user granting approval performs an operation to indicate to server 20 that the purpose of temporarily viewing the contract has been achieved.

[0199] (4) An opportunity to review access rights to signed contracts The above description of the embodiment explained an example in which a notification is issued to review access rights to concluded contracts, triggered by the acquisition of personnel change information. In addition, the following may also be used.

[0200] (4-1) Notification will be given around the time when personnel changes are likely to occur. For example, users may be notified to review their access permissions to signed contracts based on the arrival of a business company's fiscal year-end (quarterly, full-year, etc.). Business companies may reorganize their organizations based on their fiscal year-end. For example, server 20 may maintain information on each business's fiscal year-end and notify designated users, such as the legal department, to review their access permissions to signed contracts each time a quarter, half-year, or full year arrives.

[0201] (4-2) Depending on the size of the organization and the pace of its growth, notification In business companies, as the number of personnel in an organization increases, the organizational chart is updated and various organizations may be established. Server 20 may refer to the user database 211, etc., and when the number of personnel in an organization reaches a certain number (for example, when the number of people in the organization reaches a milestone number such as 100 or 1000), notify the designated users of that organization to review their access rights to signed contracts.

[0202] This allows for appropriate setting of access permissions for signed contracts as the organization expands.

[0203] Furthermore, the server 20 may refer to the user database 211, etc., and if the rate of increase (or decrease) in the number of personnel in the organization exceeds a certain rate, it may notify designated users of the organization to review their access rights to signed contracts. For example, in a personnel database, a list of newly hired members may be updated according to their hiring date. If the number of personnel joining the organization exceeds a certain number (for example, if the number of people joining in a month exceeds a certain number), the server 20 may notify users to review their access rights to signed contracts, as the rate of increase has exceeded a certain rate.

[0204] (4-3) Notification when personnel leave the organization (or department) due to retirement, transfer, secondment, etc. Managers may be involved in the conclusion of contracts in various ways, such as approving the proposal for a contract or approving its conclusion. Server 20 may also extract the concluded contracts related to the manager from the document management database 213 and notify specific users to review their viewing permissions if the personnel database records information such as a manager retiring, transferring to another department, transferring to an affiliated company, or being seconded to another organization.

[0205] Here, a specific user could be a user in a department where managing contracts is part of the job (for example, the legal department), or a user in a department that manages the handover process (for example, a department where a handover of duties is necessary in relation to the duties of the person in question, or a department that manages the fact that a handover has taken place, regardless of the content of the handover (such as the human resources department)).

[0206] Server 20 may refer to the personnel database and, if there are members returning to the organization or department (for example, when a secondment period ends and the member returns to the original organization, or when a member returns to the organization after a period of leave of absence or temporary leave (such as childcare leave)), extract at least one of the contracts for which an approval request was made, reviewed, or concluded during the period between the user leaving the organization (or department) and returning. Server 20 may then notify users such as the organization's administrator or the contract administrator whether or not to grant viewing rights to these contracts, accept the granting of viewing rights for the returning member, and update the viewing rights in the document management database 213.

[0207] (5) Others In the above embodiment, an example of a contract was described as the subject of review. In addition, the review may be conducted in the form of a term sheet that defines the contract terms, or it may be conducted on documents that contain information to customers, or transaction documents such as application forms.

[0208] While several embodiments of this disclosure have been described above, these embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications are permitted without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents.

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

[0210] In this specification, circuitry, unit, and means are hardware programmed to perform or execute the functions described herein. Such hardware may be any hardware disclosed herein, or any hardware known to be programmed to perform or execute the functions described herein.

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

[0212] <Note> The details described in the above embodiment are added below.

[0213] (Note 1) A program for operating a computer having one or more computer processors, wherein the program stores in its memory a contract that has been concluded and the right to view the contract that has been concluded, the program causes one or more computer processors to perform the steps of receiving a request from a user to view a contract that has been concluded, and allowing the user to view the contract that has been concluded according to the right to view it, and the program causes one or more computer processors to perform the steps of obtaining information indicating that there has been a change in the members of the organizations of the parties to the contract that have been concluded, and notifying the user of the update of the right to view the contract that has been concluded based on the information obtained in the obtaining step.

[0214] (Note 2) The program described in Appendix 1 stores a member database in its memory unit that manages the affiliations of members within an organization, retrieves information indicating that the member database has been updated as information indicating that there has been a change, and notifies the user about updating their access permissions in response to the update of the member database.

[0215] (Note 3) The program described in Appendix 2, in the notification step, refers to the member database and, for each department in the organization where a member has changed, extracts the concluded contracts for which the member of that department has viewing rights, and notifies the member of that department of the update of their viewing rights for the extracted concluded contracts.

[0216] (Note 4) The program, as described in Appendix 3, stores information in its memory unit about members who can set viewing permissions for concluded contracts for each department within the organization, and in the notification step, when updating the viewing permissions for concluded contracts extracted for a department, it presents the extracted concluded contracts to members who can set viewing permissions in that department, while not presenting the extracted concluded contracts to members who cannot set viewing permissions in that department.

[0217] (Note 5) A program described in any of the appendices 2 to 4, which manages information on new members joining the organization and information on members leaving the organization in a member database stored in the memory unit, and in the notification step, accepts reservations for access to concluded contracts for at least one of the new members or members leaving, depending on the timing of joining or leaving.

[0218] (Note 6) A program described in any of the appendices 2 to 5 that manages information on the timing of transfers of members who change departments in a member database stored in the memory unit, and when changing the access rights to signed contracts of a member who is transferring departments, deletes the access rights that the member had in their previous department after a predetermined period has elapsed after the transfer.

[0219] (Note 7) A program described in any of the appendices 2 to 6 that manages information on the positions of members in a member database stored in the memory unit, and changes the access rights to signed contracts according to the position when a member's position changes.

[0220] (Note 8) A program described in any of the appendices 1 to 7, configured in its memory unit to store information of clients to whom an organization outsources its work, managing information about the outsourcing period as part of the client information, setting viewing rights for contracts concluded within the outsourcing period based on the outsourcing period information, and clearing viewing rights when the outsourcing period has expired.

[0221] (Note 9) The memory unit stores a member database that manages the affiliations of members within an organization, and the member database manages information on currently affiliated members and information on members who were previously affiliated, and the program causes one or more computer processors to execute the following steps: extracting contracts that are subject to review from among the concluded contracts for which viewing rights are not set for currently affiliated members but are set for members who were previously affiliated, and notifying the system of the update of viewing rights for the extracted contracts subject to review, as described in any of the appendices 1 to 8.

[0222] (Note 10) The memory unit is configured to store information about the circumstances leading to the conclusion of a contract in association with the concluded contract, and the program, as described in Appendix 9, causes one or more computer processors to perform the step of referring to the information about the circumstances leading to the conclusion of the contract associated with the extracted contract subject to review, and notifying the result of summarizing the circumstances along with the contract subject to review.

[0223] (Note 11) The program is one of the programs described in any of Appendix 1 to 10, which causes one or more computer processors to perform the following steps: request a user who has access to view the concluded contract to authorize an operation to grant access to a specific user who does not have access to view the concluded contract; and receive an operation from a user who has access to view the concluded contract authorizing an operation to grant access to a specific user, thereby granting access to that specific user.

[0224] (Note 12) The program described in Appendix 11, which, in the requesting step, requests an operation to authorize granting viewing rights to a specific user by enabling searches while restricting the scope of viewing of concluded contracts, and in the granting viewing rights step, receives an operation from a user who has viewing rights to concluded contracts authorizing the enablement of searches while restricting the scope of viewing for a specific user, thereby providing a function to search concluded contracts based on the restrictions for that specific user.

[0225] (Note 13) A concluded contract is concluded electronically when the parties to the contract approve the contract and affix their electronic signatures; upon completion of the electronic conclusion, link information for viewing the concluded contract is notified to the parties to the concluded contract; and the program, as described in any of Appendix 1 to 12, includes setting up a storage unit to allow the user to view the concluded contract based on the link information, thereby granting the user the right to view the concluded contract.

[0226] (Note 14) A method for operating a computer having one or more computer processors, wherein a memory unit stores concluded contracts and access rights to concluded contracts, the method comprising: one or more computer processors receiving a request from a user to view concluded contracts; and allowing the user to view concluded contracts in accordance with the access rights; and further comprising: one or more computer processors obtaining information indicating that there have been changes in the members of the organizations of the parties to the concluded contracts; and, based on the information obtained in the obtaining step, notifying the user of an update to the access rights to the concluded contracts.

[0227] (Note 15) Information processing device, wherein a memory unit stores concluded contracts and access rights to concluded contracts, the control unit of the information processing device performs the steps of receiving a request from a user to view concluded contracts, and allowing the user to view the concluded contracts in accordance with the access rights, and the control unit further performs the steps of obtaining information indicating that there have been changes in the members of the organizations of the parties to the concluded contracts, and notifying the user of the update of access rights to concluded contracts based on the information obtained in the acquisition step.

[0228] (Note 16) A method for operating a computer equipped with a computer processor, the method comprising the steps of: the computer processor receiving a question input from a user in the form of voice data; generating a response content using a large-scale language model in response to the question input in the form of voice data; identifying an entity that will respond to the question based on the generated response content; and presenting information of the identified entity that will respond to the question to the user.

[0229] (Note 17) An information processing device wherein the control unit of the information processing device performs the following steps: receiving a question input from a user seeking advice in the form of voice data; generating a response content using a large-scale language model in response to the question input in the form of voice data; identifying an entity that will respond to the question based on the generated response content; and presenting information of the identified entity that will respond to the question to the user seeking advice. [Explanation of symbols]

[0230] 1: System 10: Terminal 13: Input device 14: Output device 15: Memory 16: Storage 19: Processor 20: Server 25: Memory 26: Storage 29: Processor 80: Network 92: Server 93: Server 94: Server 95: Server 96: Server 111: Antenna 112: Antenna 120: First Communications Department 121: Second Communications Department 130: Input device 131: Device 132: Display 140: Audio Processing Unit 141: Mike 142: Speaker 150: Location Information Sensor 160: Camera 170: Motion Sensor 180: Storage section 181: User Information 190: Control Unit 191: Operation Reception Section 192: Transceiver Unit 193: Data Processing Unit 194: Notification Control Unit 195: Memory Control Unit 201: Communications Department 202: Storage section 203: Control Unit 211: User Database 212: Contract Management Database 213: Document Management Database 214: Approval Request Database 215: Review History Database 1200: Operation screen 1202: Account display area 1204: Settings screen 1206: Verification Operation Unit 1208: Permission setting operation unit 1210: List display operation unit 1212: Reservation operation unit 1214: Setting screen 1216: Permission setting operation unit 1218: Latitude and longitude confirmation operation unit 1220: Reservation operation unit 1222: Approval request operation screen 1224: Permission specifying unit 1226: Approval request operation unit 2041: Reception control module 2042: Transmission control module 2043: User management module 2044: Conclusion processing module 2045: Document management module 2046: Submission processing module 2047: Permission management module 2048: Review processing module

Claims

1. A program for operating a computer having one or more computer processors, The memory unit stores the signed contract and the access rights to view the said signed contract. The program is configured on one or more computer processors. A step of receiving a request from the user to view the aforementioned concluded contract, In response to the aforementioned viewing request, the system will perform the step of allowing the user to view the concluded contract in accordance with the viewing authority. The program further provides the following to one or more computer processors: The steps include obtaining information indicating that there have been changes in the members of the organizations of the parties to the aforementioned concluded contract, A program that performs the following steps: a step of notifying the user of the renewal of access rights to the concluded contract based on the information obtained in the aforementioned acquisition step.

2. The aforementioned memory unit stores a member database that manages the affiliations of members within the organization. In the aforementioned acquisition step, information indicating that the member database has been updated is acquired as information indicating that the aforementioned change has occurred. The program according to claim 1, wherein in the notification step, it notifies the member database of the update of the access rights in response to the member database being updated.

3. In the aforementioned notification step, Referencing the aforementioned member database, extract the aforementioned concluded contracts for each department in the organization where the members have changed, and for each department, the members of that department have access rights to view them. The program according to claim 2, which notifies members of the department concerned of the renewal of their access rights to view the extracted concluded contracts.

4. The aforementioned memory unit stores information on members who can be granted access to concluded contracts for each department within the organization. The program according to claim 3, wherein in the notification step, with respect to the update of access rights for viewing the extracted concluded contracts for the department, the extracted concluded contracts are presented to members in the department who can set access rights, but the extracted concluded contracts are not presented to members in the department who cannot set access rights.

5. The member database stored in the memory unit manages information on members who newly join the organization and information on members who leave the organization. The program according to claim 2, wherein in the notification step, the program accepts a reservation for access to the concluded contract from at least one of the newly joining member or the leaving member, depending on the timing of joining or leaving.

6. The member database stored in the aforementioned memory unit manages information on the timing of transfers for members who change departments. The program according to claim 2, which, when changing the access rights of a member who is being transferred to the aforementioned department to view the aforementioned concluded contracts, deletes the access rights the member had in the previous department after a predetermined period has elapsed following the transfer.

7. The member database stored in the aforementioned memory unit manages information about the positions of the members. The program according to claim 2, which changes the access rights to the concluded contract in accordance with the position of the member in response to a change in the member's position.

8. The aforementioned memory unit is configured to store information about the client to whom the organization outsources its work, and the information of the outsourcing period is managed as part of the client's information. The program according to claim 1, which, based on the information of the contract period, sets access rights to the concluded contract within the contract period and deletes the access rights when the contract period has ended.

9. The aforementioned memory unit stores a member database that manages the affiliations of members within the organization, and the member database manages information on currently affiliated members and information on members who were previously affiliated. The program further provides the following to one or more computer processors: The steps include: extracting the contracts subject to review from the aforementioned concluded contracts for which viewing rights are not granted to the currently belonging members but are granted to members who previously belonged; The program according to claim 1, which performs the step of notifying the user of the update of access rights for the extracted contracts subject to review.

10. The memory unit is configured to store information about the circumstances leading to the conclusion of the contract, in association with the concluded contract document. The program further provides the following to one or more computer processors: The program according to claim 9, which performs the step of referring to information on the circumstances leading to the conclusion of the contract associated with the extracted contract subject to review, and notifying the user of the result of summarizing the circumstances along with the contract subject to review.

11. The program further provides the following to one or more computer processors: The steps include requesting a user who has access to view the aforementioned concluded contract to authorize granting access to a specific user who does not have access to view the aforementioned concluded contract, The program according to claim 1, which, by receiving an operation from a user who has the right to view the aforementioned concluded contract, authorizing the granting of viewing rights to the aforementioned specific user, causes the program to perform the step of granting viewing rights to the aforementioned specific user.

12. In the aforementioned step, the request is made to authorize the granting of viewing rights to the specific user by enabling searching while restricting the scope of the concluded contract that the user can view. The program according to claim 11, wherein in the step of granting viewing rights, the program receives an operation from a user who has viewing rights to the concluded contracts to authorize the specific user to enable searching while restricting the scope of what can be viewed, thereby providing the specific user with a function to search the concluded contracts based on the restrictions.

13. The aforementioned concluded contract is concluded electronically when the parties to the contract approve the contract and affix their electronic signatures, and upon completion of the electronic conclusion, a link information to view the concluded contract is notified to the parties to the contract. The program according to claim 1, which includes granting a user the right to view the concluded contract, and configuring the storage unit to allow the user to view the concluded contract based on the link information.

14. A method for operating a computer having one or more computer processors, The memory unit stores the signed contract and the access rights to view the said signed contract. The above method involves one or more computer processors, A step of receiving a request from the user to view the aforementioned concluded contract, In response to the aforementioned request for viewing, the following steps are performed: allowing the person to view the concluded contract in accordance with the viewing authority: The above method further involves the one or more computer processors, The steps include obtaining information indicating that there have been changes in the members of the organizations of the parties to the aforementioned concluded contract, A method comprising the steps of: notifying the person of the renewal of access rights to the concluded contract based on the information obtained in the aforementioned acquisition step; and

15. An information processing device, The memory unit stores the signed contract and the access rights to view the said signed contract. The control unit of the information processing device, A step of receiving a request from the user to view the aforementioned concluded contract, In response to the aforementioned request for viewing, the following steps are performed: allowing the person to view the concluded contract in accordance with the viewing authority: The control unit further, The steps include obtaining information indicating that there have been changes in the members of the organizations of the parties to the aforementioned concluded contract, An information processing device that performs the following steps: a step of notifying the user of the renewal of access rights to the concluded contract based on the information obtained in the aforementioned acquisition step.

Images