Program, method, and information processing device

Abstract

To provide a technique for reducing an unnecessary risk because of continuation of transactions by facilitating judgment of for example whether transactions should be continued with a concerned party already having transactions, and conditions of transactions should be reconsidered.SOLUTION: A storage section holds document data approved among the parties concerned. Provided is a program for allowing a computer processor to execute a step of detecting a change in information regarding at least one of organization management of the parties concerned contract conclusion regarding the parties concerned of document data in the document data held in the storage section, and a step of reporting to the other of the parties concerned of document data when detecting a change in information for one of the parties concerned of the document data.SELECTED DRAWING: Figure 11

Description

[Technical Field]

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

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

[0003] Patent Document 1 addresses the issue of "ensuring the conclusion and cancellation of a contract and storing electronic contracts," and describes a technology that "includes a contract application client that sends contract application information to a contract acceptance server via a communications network and receives contract information from the contract acceptance server, a contract acceptance server that receives application information from the client via the communications network, generates contract information from the contract application information, and sends the contract information to the client, and a contract storage server that obtains communication messages between the client and the contract acceptance server, attaches electronic signatures to the communication messages, and stores the communication messages and the electronic signatures."

[0004] According to the technology of Patent Document 1, this has the effect of "ensuring the conclusion and cancellation of a contract, allowing the storage of the contract, and also making it possible to detect any misconduct by the contract recipient in the conclusion of an electronic contract." [Prior art documents] [Patent documents]

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

[0006] When a business starts a transaction, it evaluates the counterparty from various perspectives, including creditworthiness, before registering them as a trading partner and concluding a contract.

[0007] On the other hand, even while a contract is concluded and a transaction is ongoing, the other party's circumstances may change from moment to moment. Therefore, even after a contract is concluded, a situation may arise in which, according to one's own standards, the transaction should not be continued. Therefore, it may not be desirable to continue the transaction despite such circumstances.

[0008] Therefore, there is a need for technology that makes it easier to decide whether to continue a transaction with an existing counterparty or to review the terms of the transaction, thereby reducing unnecessary risks associated with continuing the transaction as much as possible. [Means for solving the problem]

[0009] According to one embodiment of the present disclosure, there is provided a program for operating a computer having a computer processor, wherein document data approved between the parties is stored in a memory unit, and the program causes the computer processor to execute the steps of: detecting, in the document data stored in the memory unit, a change in information regarding at least one of the parties to the document data, the organizational operations of the parties to the contract, consumer response, and performance; and, upon detecting a change in information regarding one of the parties to the document data, notifying the other party to the document data. [Effects of the Invention]

[0010] According to the present disclosure, even after a contract has been concluded, it is possible to easily decide whether to continue a transaction or review the terms of the transaction, thereby minimizing unnecessary risks associated with continuing the transaction. [Brief explanation of the drawings]

[0011] [Figure 1]FIG. 1 is a diagram showing the configuration of the system 1. [Figure 2] FIG. 2 is a diagram showing the configuration of the server 20. As shown in FIG. [Figure 3] FIG. 3 is a diagram showing the configuration of the terminal 10. As shown in FIG. [Figure 4] FIG. 4 is a diagram showing the data structure of the user database 211. As shown in FIG. [Figure 5] FIG. 5 is a diagram showing the data structure of the fastening management database 212. As shown in FIG. [Figure 6] FIG. 6 is a diagram showing the data structure of the document management database 213. As shown in FIG. [Figure 7] FIG. 7 is a diagram showing the data structure of the review history database 214. As shown in FIG. [Figure 8] FIG. 8 is a diagram showing the data structure of the approval request database 215. As shown in FIG. [Figure 9] FIG. 9 is a diagram showing the data structure of the party evaluation database 216. [Figure 10] FIG. 10 is a diagram showing the flow of processing for notifying a party to review an already concluded contract and encourage them to re-conclude the contract in response to an event that has occurred on the other party's side. [Figure 11] FIG. 11 is a diagram showing the flow of processing in which an event that has occurred is notified to the other party at the stage of a transaction, and a review of the conditions for the transaction is encouraged. [Figure 12] Figure 12 shows an operation screen that notifies the other party to an already concluded contract of an event that has occurred and encourages them to review the terms of the contract and re-conclude it. [Figure 13] Figure 13 shows an operation screen that notifies the other party of an event that has occurred during a transaction and prompts them to review the terms of the contract. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0014] 1 includes a contract conclusion and document management service server 20, a user terminal 10, a document review service server 93, a business information provision service server 94, a large-scale language model service server 95, an accounting processing service server 96, a book and precedent viewing service server 98, an approval application service server 99, and a user terminal 10A. These devices are connected to each other via a network 80.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0034] The accounting processing service server 96 provides services that support accounting and bookkeeping operations, such as a service that allows you to create and send invoices, estimates, delivery notes, etc., and a service that acquires deposit and withdrawal data and performs automatic accounting journal entries, etc.

[0035] The book and precedent viewing service server 98 is a service that allows users to view electronic content such as magazines and books. For example, by paying a fixed fee periodically, users can view electronic books in the legal field, etc. The book and precedent viewing service server 98 also accumulates court precedents in a database and provides precedents in response to user search operations.

[0036] The approval request application service server 99 is a server that provides a service to support operations such as approval requests in an organization (such as a business company) that conducts business activities. The approval request application service server 99 provides a service to a user that enables the user to design a workflow for obtaining budget approval among multiple users, for example.

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

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

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

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

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

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

[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 the server 20. Details will be described later.

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

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

[0046] The party evaluation database 216 stores evaluation results of whether or not to continue a transaction with a potential business operator based on information provided by the business operator information providing service server 94, and stores information on books, precedents, etc. obtained by searching the book and precedent viewing service server 98. For example, keywords for searching the book and precedent viewing service server 98 can be obtained by extracting keywords from the information provided by the business operator information providing service server 94. Details will be described later.

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

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

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

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

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

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

[0053] The party evaluation module 2046 evaluates the possibility of continuing a transaction with a business based on information provided by the business information providing service server 94, etc., and updates the party evaluation database 216. Details will be described later.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0134] 9 is a diagram showing the data structure of the party evaluation database 216. The party evaluation database 216 includes an item "business operator ID," an item "evaluation time," an item "evaluation score," an item "organizational management (internal control)," an item "consumer response (reputation)," an item "performance," and an item "reference information."

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

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

[0137] The item "evaluation time" is information about the time when the business was evaluated.

[0138] Specifically, the item "evaluation time" includes information such as the timing of the evaluation or the period during which the evaluation was performed.

[0139] The item "evaluation score" is a score that evaluates the possibility of continuing to do business with a business.

[0140] Specifically, the item "evaluation score" may be a score that the server 20 evaluates the likelihood of continuing transactions with each business based on information such as news collected by the business information service server 94, or may store evaluation values ​​of businesses evaluated by an external system such as the business information service server 94. For example, the score may be calculated based on credit information provided by an external system. For example, the server 20 may calculate a credit score based on whether the parties pay expenses on time, etc., based on deposit and withdrawal information managed by the invoicing service, deposit and withdrawal management service, and accounting support service, by communicating with the accounting processing service server 96. It is possible that a party may actively provide a credit score to the other party in order to increase the likelihood of a transaction.

[0141] The item "organizational management (internal control)" is information on the organizational management and internal control of the business.

[0142] Specifically, the item "organizational management (internal control)" stores information on the time when there is a news article or the like about the internal control of a business by communicating with the business information providing service server 94. Examples of information on organizational management and internal control include the following: - Events where the responsibility of management is relatively low, such as embezzlement Information about incidents of harassment - Events where guidance was given by supervisory authorities, such as the Labor Standards Inspection Office The server 94 of the business information providing service evaluates businesses based on the above information. The item "consumer response (reputation)" is information about the reputation of the business operator.

[0143] Specifically, the item "Consumer Reaction (Reputation)" communicates with the business information service server 94 and stores information on the history of negative reactions from consumers to businesses that have been spread and covered in the news, social media, etc., or the score that the business information service server 94, etc., has calculated based on these.

[0144] The item "performance" is information about the performance of the business operator.

[0145] Specifically, the "Performance" item stores information about performance such as sales, revenue (profit amount, profit margin, etc.), and evaluation results regarding business continuity (continued deficit, possibility of bankruptcy, bond rating, continued non-payment, etc.) by communicating with the business information service server 94.

[0146] The item "reference information" is information that serves as a reference for each piece of information such as events related to internal control, reputation, and business performance.

[0147] Specifically, the item "Reference Information" includes information on books, precedents, etc. that serve as references for news articles on matters related to internal control, reputation, business performance, etc., and is collected from the book and precedent viewing service server 98. This allows for the acquisition of insights into the resolution of matters mentioned in news articles (for example, the occurrence of harassment) through legal proceedings.

[0148] <3 operations> FIG. 10 is a diagram showing the flow of processing for notifying a party to review an already concluded contract and encourage them to re-conclude the contract in response to an event that has occurred on the other party's side.

[0149] In step S1021, the server 20 detects, in the document data held in the document management database 213, that there has been a change in information regarding the creditworthiness of the party to the document data (the party to the contract conclusion managed in the contract management database 212, indicated by the conclusion ID). For example, the server 20 communicates with the server 94 of the business information provision service, and collects information indicating news articles, financial information, reactions on social media, etc., about the party. The server 20 detects that there has been a change in information regarding at least one of the organizational management, consumer reaction, and performance information of the party to the contract conclusion for the party in the document data, and updates the party evaluation database 216. In response to the change in the above information, the server 20 identifies a score that evaluates the possibility of continuing transactions with the party, and updates the party evaluation database 216.

[0150] In step S1023, when the server 20 detects that there has been a change in the credibility of one of the parties to the document data, it notifies the other party to the document data.

[0151] The server 20 may identify information that serves as the basis for a legal judgment depending on the type of event that has changed for one of the parties, and notify the other party of the identified information that serves as the basis for a legal judgment. This makes it easier to infer how to interpret the occurring event from information in books, precedents, etc. For example, if the type of event is one that may result in civil or criminal proceedings, the server 20 may notify the other party of precedent information that serves as the basis for a legal judgment, which is information on precedents corresponding to the proceedings.

[0152] When there is a change in the information relating to the business performance of one of the parties, the server 20 evaluates the continuity of the transaction in terms of business performance and notifies the other party of the evaluation result.

[0153] Here, the server 20 may accept from the user a designation of the type of event for which a change is to be detected, and notify the designated user of a change in the designated type of event to the relevant parties. This allows the user to receive notifications according to their criteria for determining which event to focus on (for example, whether to place importance on the reputation of the consumer), making it easier for them to decide whether to continue the transaction, etc.

[0154] The server 20 may notify the parties of positive information regarding creditworthiness when deciding whether to continue a transaction. For example, the server 20 may communicate with the accounting processing service server 96 to notify the parties that they have paid expenses on time based on the deposit and withdrawal information managed by the billing service, deposit and withdrawal management service, and accounting support service. For example, a party may actively provide the other party with a credit score based on the deposit and withdrawal history to increase the likelihood of a transaction. The server 20 may notify the other party of the score managed in the party evaluation database 216.

[0155] In step S1011, the terminal 10 displays that there has been a change in the credibility of the party to the document data.

[0156] In step S1013, the terminal 10 accepts an operation to review the conditions of the contract and re-conclude the contract. In the description of this embodiment, it is assumed that the user selects to prepare a contract with revised conditions and re-conclude the contract.

[0157] In step S1025, the server 20 executes a process to approve the new document data for which the parties have re-agreed on the terms and conditions for the parties to conclude a contract (application for approval, contract conclusion, etc.; conclusion management database 212, document management database 213, approval application database 215, etc.).

[0158] In step S1027, the server 20 stores the new re-agreed document data for which approval processing has been performed in the document management database 213 in association with the document data related to the notification (document data for which the conditions are to be revised).

[0159] When concluding a contract for new document data, the server 20 may acquire information about the user associated with the document data related to the notification (for example, by referring to the conclusion management database 212, identify the user who is set in the workflow at the time of concluding the contract for which the terms are to be reviewed. It may also be possible to acquire information about the user who is set in the approval request database 215), and set the acquired user information as the user who will approve the conclusion of the contract for the new document data (application for approval, contract conclusion, etc.; conclusion management database 212, approval request database 215).

[0160] FIG. 11 is a diagram showing the flow of processing in which an event that has occurred is notified to the other party at the stage of a transaction, and a review of the conditions for the transaction is encouraged.

[0161] In step S1121, the server 20 presents the user with an operation screen for acquiring document data for conducting a transaction between the parties.

[0162] In step S1111, the terminal 10 accepts an operation to specify document data for conducting a transaction between the parties, such as a contract, purchase order, or quotation.

[0163] In step S1123, in response to acquiring document data for a transaction, the server 20 detects that there has been a change in credit information for the parties to the document data who are the trading partners of the document data (e.g., the addressee of an estimate, the parties to a contract) and who are parties to the document data stored in the document management database 213.

[0164] For example, the server 20 accepts an operation to register document data that is the subject of a contract in the contract conclusion system. The server 20 acquires document data that is the subject of a contract that is registered in the contract conclusion system and that is related to an approval request for approving the document data.

[0165] In this way, in order to conclude a contract, a user who will be the sender may upload contract data to the server 20. In addition, the server 20 may acquire an estimate or the like issued in the accounting processing service.

[0166] In step S1125, the server 20 notifies the other party of the document data for the transaction of information relating to changes in the credit information.

[0167] For example, the server 20 may notify the contract signing system of information regarding changes in information about the other party of the document data that is the subject of the contract, in response to an operation to register the contract to be signed. For example, when the sender uploads a contract to sign a contract, the server 20 notifies the sender that there has been a change in the credit information about the other party. This allows the sender to decide whether to continue the transaction or review the terms of the transaction when creating or uploading new documents related to a transaction with a party with whom they have previously done business and concluded a contract (for example, uploading a contract to sign a contract or creating a quote for a transaction).

[0168] When a user receives a request for approval of document data in concluding a contract, the server 20 may notify the user of information about changes in the information of the other party to the document data in response to acquiring the document data related to the approval request. This allows the user to recognize, at the time of approving the document data for a transaction, whether or not there has been a change in the information about the other party's credit since the last time the transaction was conducted.

[0169] <4 Screen example> Figure 12 shows an operation screen that notifies the other party to an already concluded contract of an incident and prompts them to review the terms of the contract and re-conclude it. This corresponds to the process explained in Figure 10.

[0170] The screen 1200 is an operation screen that displays a list of concluded contracts and assists in the decision of whether to review the conditions and re-conclude a contract in which the information of the parties has changed.

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

[0172] The list display area 1220 is an area for displaying a list of contracts in which information relating to the creditworthiness of the parties has changed.

[0173] The period designation receiving section 1221 is an operation member that receives the designation of the range for contract extraction.

[0174] The target designation receiving unit 1222 is an operation member for receiving, from the user, designation of which event has changed when there is a change in information relating to the trustworthiness of the party.

[0175] For example, when the target designation receiving unit 1222 receives the designation of an event related to internal control, it can display a list of contracts with parties in which there has been a change in the event related to internal control.

[0176] The extracted contract display area 1223 is an area that displays contracts extracted based on the conditions specified in the period specification receiving area 1221 and the target specification receiving area 1222, and receives from the user the specification of the contract whose details are to be displayed.

[0177] As shown in the figure, the extracted contract display area 1223 displays the following to help the user decide whether to leave the contract as is or to change the conditions and re-conclude the contract. If there are any changes in your credit information, the details and the date and time of the changes Reference books and case law information The details display area 1230 is an area that displays events in which information relating to the creditworthiness of the parties has changed and the contract data for the contract specified in the extracted contract display area 1223, and accepts user operations.

[0178] The contract data 1232 is an area that displays each clause stipulated in the contract.

[0179] The contract data 1232 may be displayed as a preview of a file in PDF format, etc. Also, each clause of the contract may be displayed with the review results of each clause by the review service server 93 added as comments.

[0180] The management information display area 1233 is an area for displaying information managed in the document management database 213 and information managed in the party evaluation database 216, such as the parties to the contract and the contract expiration date.

[0181] The confirmation item display area 1234 is an area for displaying a draft of the revised conditions when the conditions are revised and re-signed.

[0182] The confirmation item display area 1234 can provide the user with proposed amendments to the clauses of the contract in response to an event that has occurred (proposals to revise the terms in response to changes in credit), for example, by storing such amendments in the server 20. The server 20 may also suggest amendments to the clauses to the user depending on the type of event. For example, if a negative event has occurred related to business performance, the possibility of collection may be increased by shortening the payment deadline, etc.

[0183] The proposed amendment display area 1235 is an area for accepting an operation to display a proposed amendment to the contract when the conditions are changed and the contract is to be re-signed, as in the processing of steps S1013 and S1025.

[0184] The workflow execution receiving unit 1236 is an operation member that receives an operation to start the process of re-entering a contract (application for approval, contract conclusion) based on the proposed amendment to the contract, as in the process of step S1025.

[0185] Figure 13 shows an operation screen that notifies the other party of an event that has occurred during the transaction and prompts them to review the terms of the contract. This corresponds to the process described in Figure 11.

[0186] The list display area 1250 is an area for displaying a list of contracts in which information relating to the creditworthiness of the parties has changed.

[0187] The list display area 1250 accepts uploads of documents such as contracts for transactions, and displays a list of documents (contracts, etc.) from past transactions if there has been a change in credit information about a trading partner since the previous transaction.

[0188] The data specification receiving section 1251 is an operation member that receives uploading of documents for a transaction.

[0189] The details display section 1252 is an area that displays the event of the change and reference information when there is a change in the information relating to the creditworthiness of the party.

[0190] The condition edit receiving section 1253 is an operation member that receives an operation to edit the uploaded document data.

[0191] The condition edit receiving unit 1253 displays the contents of the uploaded document data to receive edits to the document data. Once edits have been made to the document data, the edits are stored in the server 20. This allows the user to be provided with an opportunity to review the conditions when making a transaction if there has been a change in credit information since the previous transaction when the contract was concluded.

[0192] The transmission acceptance section 1254 is an operation member that accepts an operation to transmit uploaded document data to a partner.

[0193] The receiving contract list 1260 is an area that displays a list of document data for which approval of the contract is requested as the receiver when concluding the contract.

[0194] As shown in the figure, the received contract list 1260 notifies the user when a contract approval request is received that there has been a change in the information about the other party's credit since the last transaction. This makes it easy to decide whether to approve the document data related to the approval request as is or to review the conditions.

[0195] The details display section 1262 is an area that displays the event of the change and reference information when there is a change in the information relating to the creditworthiness of the party.

[0196] The rejection operation receiving unit 1263 is an operating member that receives an operation to reject or cancel the document data related to the approval request without approving it.

[0197] As shown in the figure, the rejection operation receiving unit 1263 receives an operation from the user to approve, reject, or cancel the document data after the user recognizes in the detailed display unit 1262 that there has been a change in the information regarding the other party's credit.

[0198] The approval operation receiving unit 1264 is an operating member that receives an operation to approve document data related to an approval request.

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

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

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

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

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

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

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

[0206] (Appendix 1) A program for operating a computer having a computer processor, which stores document data approved between the parties in a memory unit, and causes the computer processor to execute the steps of detecting, in the document data stored in the memory unit, a change in information about at least one of the parties to the document data that relates to the organizational management, consumer response, or performance of the parties to the contract, and, when a change in information about one of the parties to the document data is detected, notifying the other party to the document data.

[0207] (Appendix 2) The program further causes the processor to execute a step of acquiring document data for a transaction between the parties, and in the detecting step, detects that there has been a change in information in response to acquiring the document data for the transaction, and in the notifying step, notifies the other party of the acquired document data for the transaction of information regarding the change in information in response to the acquisition.

[0208] (Appendix 3) A program as described in Appendix 2, in which, in the acquisition step, an operation to register the document data that is the subject of the contract conclusion in the contract conclusion system is accepted as the acquisition of document data for the transaction, and, in the notification step, information regarding changes in information about the other party of the document data that is the subject of the contract conclusion is notified in accordance with the registration operation.

[0209] (Appendix 4) A program described in any of Appendices 2 to 3, wherein in the acquiring step, document data for conducting a transaction is acquired, as document data that is the subject of contract conclusion registered in a contract conclusion system and is related to an approval request to approve the document data, and in the notifying step, in response to acquiring the document data related to the approval request, notifies information regarding changes in information about the other party of the document data.

[0210] (Appendix 5) A program described in any of Appendices 1 to 4, in which, in the notification step, information that serves as the basis for a legal judgment is identified depending on the type of event that has changed for one of the parties, and the identified information that serves as the basis for the legal judgment is notified to the other party.

[0211] (Appendix 6) A program as described in Appendix 5, in which, in the notification step, if the type of event is one that may result in civil or criminal proceedings, information on precedents corresponding to the proceedings is notified as information that serves as the basis for legal judgment.

[0212] (Appendix 7) A program as set forth in any of Appendices 1 to 6, wherein in the notification step, if there is a change in information regarding performance of one of the parties, the program evaluates the continuity of the transaction in terms of performance and notifies the other party of the evaluation results.

[0213] (Appendix 8) The program is a program described in any of Appendices 1 to 7, further causing the processor to execute a step of receiving from the user a designation of the type of event for which a change is to be detected, and in the notification step, notifying the designated user of the relevant party that there has been a change in the designated type of event.

[0214] (Appendix 9) A program described in any of Appendices 1 to 8, which causes the processor to further execute the steps of: performing a process to approve new document data, the terms of which have been re-agreed upon between the parties, for the document data related to the notification, for the purpose of entering into a contract; and storing the new re-agreed document data, for which the approval process has been performed, in a memory unit in association with the document data related to the notification.

[0215] (Appendix 10) A program as described in Appendix 9, in which, in a step of performing approval processing, when entering into a contract for new document data, information of a user associated with the document data to be notified is obtained, and the obtained user information is set as the user who will approve the entry into a contract for the new document data.

[0216] (Appendix 11) A method for operating a computer having a computer processor, wherein document data approved between parties is stored in a memory unit, and the method executes the steps of: detecting, in the document data stored in the memory unit, that there has been a change in information for the parties to the document data, regarding at least one of the information relating to the organizational management, consumer response, and performance of the parties to the contract; and, upon detecting that there has been a change in information for one of the parties to the document data, notifying the other party to the document data.

[0217] (Appendix 12) An information processing device having a control unit, wherein document data approved between the parties is stored in a memory unit, and the control unit executes the steps of: detecting, in the document data stored in the memory unit, a change in information about at least one of the parties to the document data, which is related to the organizational management, consumer response, and performance of the parties to the contract; and, when it detects a change in information about one of the parties to the document data, notifying the other party to the document data.

Claims

1. A program for operating a computer having a computer processor, The storage unit stores document data approved by the parties, The program causes the computer processor to: detecting, in the document data stored in the storage unit, a change in information regarding at least one of the parties to the contract, including organizational management, consumer response, and business performance of the parties to the contract; and when detecting that a change has occurred in the information of one of the parties to the document data, notifying the other of the parties to the document data.

2. The program further causes the processor to Executing a step of acquiring document data for a transaction between the parties; In the detecting step, detecting that the information has changed in response to obtaining document data for the transaction; 2. The program according to claim 1, wherein in the notifying step, in response to the acquisition, information relating to changes in the information of the other party of the document data for the transaction acquired is notified.

3. In the acquiring step, an operation to register the document data to be the subject of the contract conclusion in a contract conclusion system is accepted as acquiring document data for the transaction, 3. The program according to claim 2, wherein in the notifying step, information relating to the change in information is notified for the other party of the document data that is the subject of the contract in response to the registration operation.

4. In the acquiring step, as acquiring document data for the transaction, document data that is the subject of contract conclusion registered in a contract conclusion system and is related to an approval request for approving the document data is acquired; 3. The program according to claim 2, wherein in the notifying step, in response to obtaining the document data related to the approval request, information related to the change in information about the other party of the document data is notified.

5. 2. The program of claim 1, wherein in the notification step, information that serves as the basis for a legal judgment is identified depending on the type of event that has changed for one of the parties, and the identified information that serves as the basis for the legal judgment is notified to the other party.

6. 6. The program according to claim 5, wherein, in the notification step, if the type of event is one that may result in civil or criminal proceedings, information on precedents corresponding to the proceedings is notified as information that serves as the basis for the legal judgment.

7. 2. The program of claim 1, wherein, in the notifying step, if there is a change in the information regarding the performance of one of the parties, the continuity of the transaction in terms of performance is evaluated and the result of the evaluation is notified to the other of the parties.

8. The program further causes the processor to receiving, from a user, a designation of a type of event for detecting the occurrence of the change; 2. The program according to claim 1, wherein the notifying step notifies the designated user of a change in the type of event designated by the designation.

9. The program further causes the processor to a step of performing a process for approving the conclusion of a contract between the parties with respect to new document data for which the parties have re-agreed on the terms of the document data related to the notification; The program according to claim 1 , further comprising a step of storing the new document data for which the approval process has been carried out in the storage unit in association with the document data related to the notification.

10. In the step of performing the approval process, When concluding the contract for the new document data, acquiring user information associated with the document data in the notification; 10. The program according to claim 9, further comprising: setting the acquired user information as a user who will approve the conclusion of a contract for the new document data.

11. 1. A method of operating a computer having a computer processor, comprising: The storage unit stores document data approved by the parties, The method further comprises the steps of: detecting, in the document data stored in the storage unit, a change in information regarding at least one of the parties to the contract, including organizational management, consumer response, and business performance of the parties to the contract; and upon detecting that the information has changed for one of the parties to the document data, notifying the other party to the document data.

12. An information processing device including a control unit, The storage unit stores document data approved by the parties, The control unit detecting, in the document data stored in the storage unit, a change in information regarding at least one of the parties to the contract, including organizational management, consumer response, and business performance of the parties to the contract; and when detecting that there has been a change in the information for one of the parties of the document data, notifying the other of the parties of the document data.

Images