Information processing device, method, program

Abstract

There is a need for technology that will make the process of confirming payments even easier. [Solution] The memory unit is configured to store contract data, which is a concluded contract document that has been approved by the parties to the contract and specifies the terms and conditions of the contract. The program causes one or more computer processors to perform the following steps: extract the contract terms for payments, including the amount to be paid, and the information of the other party to the contract, from among the contract documents stored in the memory unit in association with the user, for contracts for which payment of expenses is received, and store them as a payment confirmation list in association with the user; obtain a record of payments related to the user's transactions; compare a list of payment records, which associates the name of the transferor and the amount to be paid, included in the payment record obtained in the acquisition step, with a payment confirmation list generated based on the contract, and output the comparison result.

Description

Technical Field

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

Background Art

[0002] In business activities, transactions are carried out while concluding contracts between parties. When concluding a contract, various departments within each party review the contract terms, deliberate on the wording of the contract, and then proceed to draft the contract. In addition, based on comments on each clause of the contract document from the counterparty to the contract, the parties agree on the contract terms, finalize the content of the contract document, and conclude the contract.

[0003] Patent Document 1 points out that the problem to be solved is to "provide a technology that makes payment omissions less likely to occur", and as a means for solving the problem, it describes that "the control unit receives contract information related to a contract. The contract information includes payment information related to payment. Based on the payment information, the control unit outputs payment application information. The payment application information is information for applying for payment within an organization".

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of Invention

Problems to be Solved by the Invention

[0005] Upon conclusion of a contract, transactions are performed based on the content of the contract document, and payments of expenses are made or received (deposited), but it is difficult and labor-intensive to confirm whether the content of the contract document matches the deposited amount. In addition, it is difficult to confirm which contract document the received deposit corresponds to, and there is a risk of overlooking an unpaid amount.

[0006] Therefore, there is a need for technology that will make the process of confirming payments even easier. [Means for solving the problem]

[0007] According to one embodiment, a program is provided for operating a computer having one or more computer processors. The memory unit is configured to store contract data, which is a concluded contract document that defines the terms and conditions of the contract and has been approved by the parties to the contract. The program causes one or more computer processors to perform the following steps: extract the contract terms for payments, including the amount to be paid, and the information of the other party to the contract, from among the contract documents stored in the memory unit in association with the user, for contracts for which payment of fees is received, and store them as a payment confirmation list in association with the user; acquire records of payments related to the user's transactions; compare a list of payment records, which associates the name of the remitter and the amount to be paid, included in the payment records acquired in the acquisition step, with a payment confirmation list generated based on the contract, and output the comparison result. [Effects of the Invention]

[0008] This disclosure makes it possible to further simplify the process of confirming payments. [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 template database 212. [Figure 6] Figure 6 shows the data structure of the approval request database 213. [Figure 7] Figure 7 shows the data structure of the review history database 214. [Figure 8] Figure 8 shows the data structure of the contract management database 215. [Figure 9] Figure 9 shows the data structure of the document management database 216. [Figure 10] Figure 10 shows the data structure of the legal consultation management database 217. [Figure 11] Figure 11 shows the data structure of the payment confirmation list database 218. [Figure 12] Figure 12 shows the data structure of the deposit record database 219. [Figure 13] Figure 13 shows the process flow for generating a payment confirmation list based on concluded contracts, comparing it with payment records to extract unpaid transactions, and determining who is responsible for contacting those with unpaid transactions. [Figure 14] Figure 14 shows an example of an operation screen that generates a payment confirmation list based on concluded contracts, compares it with payment records to extract unpaid transactions, and determines who is responsible for contacting those with unpaid transactions. [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] Further, in the following description, a "processor" refers to one or more processors. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be another type of processor such as a GPU (Graphics Processing Unit). The at least one processor may be single-core or multi-core.

[0012] Further, the at least one processor may be a processor in a broad sense, such as a hardware circuit (for example, an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit)) that performs part or all of the processing.

[0013] Further, in the following description, an expression such as "xxx table" may be used to describe information from which an output can be obtained for an input, but this information may be data of any structure, or may be a learned model such as a neural network that generates an output for an input. Accordingly, the "xxx table" can be referred to as "xxx information".

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

[0015] Further, in the following description, processing may be described with a "program" as the subject, but since the program is executed by a processor to perform defined processing as appropriate using a storage unit and / or an interface unit or the like, the subject of the processing may be the processor (or a device such as a controller having the processor).

[0016] The program may be installed on a device such as a computer, or it may reside on a program distribution server or a computer-readable (e.g., non-temporary) recording medium. Furthermore, in the following description, two or more programs may be implemented as a single program, or one program may be implemented as two or more programs.

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

[0018] Furthermore, in the following explanations, when describing similar elements without distinction, a reference code (or a common code among reference codes) may be used, and when describing similar elements with distinction, the element's identification number (or reference code) may be used.

[0019] Furthermore, in the following explanation, only control lines and information lines deemed necessary for the explanation are shown, and not all control lines and information lines in the product are necessarily shown. All components may be interconnected.

[0020] <Outline of the Embodiment> The embodiments will be described below.

[0021] <First Embodiment> <1.1 System Configuration Diagram> Figure 1 shows the configuration of System 1.

[0022] System 1, shown in Figure 1, includes a contract signing and document management service server 20, a user terminal 10, a business support system service server 92, a document review service server 93, an artificial intelligence (large-scale language model) service server 95, a document creation service server 96, and a sales support system service server 97. These devices are connected via a network 80.

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

[0024] Server 20 is a device that provides services for concluding contracts electronically and for managing document data concluded electronically. It should be noted that in System 1, the contract conclusion service provided by Server 20 and the document data management service may be provided by separate devices or different service providers. For example, Server 20 provides a document management service and, in addition to electronically signed contract data, may also optically scan paper contracts with seals to extract information such as the contract period and whether the contract is automatically renewed, and manage this information along with the scanned contract data. This allows for notifications to be sent to the user when the contract period expires.

[0025] Server 20 may also be a server that provides services to support tasks such as submitting approval requests to organizations (business companies, etc.) that conduct business activities. For example, Server 20 provides a service to users that enables them to design a workflow for obtaining budget approval with multiple users.

[0026] Terminal 10 is a device operated by the user.

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

[0028] 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. For example, the document review service server 93 may prompt the large-scale language model service server 95 with the document data to be reviewed (such as contract data) and information indicating the review criteria, and instruct the server 95 to perform the review according to the review criteria. By receiving the output of the large-scale language model service server 95, the server 93 may generate review comments for the document data. The document review service server 93 may also communicate with server 20 to provide the server 20 with data accumulated by the document review service.

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

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

[0031] The document creation service server 96 provides a service for managing document data such as meeting minutes in organizations conducting business activities. Server 96 can issue URLs (Uniform Resource Locators) for accessing document data, and for example, if the user account of a user of the document creation service has access rights to the document data, the document data can be accessed via the URL. The document creation service server 96 may also be linked with a server that provides a schedule management service with calendar functionality, so that user accounts are common to both services. For example, having a user account may allow access to both the schedule management service and the document creation service. In this case, if document data from the document creation service is associated with a schedule, access rights to that document data may be set for users participating in the schedule.

[0032] The document creation service server 96 may communicate with server 20 to provide server 20 with data accumulated by the document creation service.

[0033] The sales support system service server 97 provides services to support sales activities. For example, the sales support system service server 97 provides the following to the user: • For each sales project, manage information such as the client, transaction details (amount, goods), transaction history (memos, meeting minutes, etc.), and responsible parties (our company, the other party, etc.). • Provide analysis results of sales performance for each sales team (e.g., trends in closing rates). The server 97 of the sales support system service may communicate with the server 20 to provide the server 20 with the data accumulated by the sales support system service.

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

[0035] Terminal 10 can be implemented, for example, as follows: • Handheld mobile devices such as smartphones and tablets • Stationary PCs (Personal Computers), Laptop PCs • 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0050] The memory unit 202 stores various databases, including a user database 211, a template database 212, a proposal application database 213, a review history database 214, a contract signing management database 215, a document management database 216, a legal consultation management database 217, a payment confirmation list database 218, and a payment record database 219.

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

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

[0053] Template Database 212 is a database that manages templates for documents used in transactions between parties, such as contracts. Further details will be provided later.

[0054] The approval request database 213 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 213. Further details will be described later.

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

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

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

[0058] Legal Consultation Management Database 217 is a database for managing consultations made to the department responsible for legal consultations. Further details will be provided later.

[0059] The payment confirmation list database 218 is a database of payment confirmation lists generated from concluded contracts. Further details will be provided later.

[0060] The deposit record database 219 is a database of deposit records generated through integration with banks and accounting systems. Further details will be provided later.

[0061] 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, LLM utilization module 2047, review processing module 2048, template management module 2049, consultation processing module 2050, and payment confirmation processing module 2051.

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

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

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

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

[0066] The document management module 2045 controls the process of managing document data by referring to the document management database 216. 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 216 in response to user actions (such as renewing the contract).

[0067] 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 213 in response to the operation to approve the request.

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

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

[0070] The template management module 2049 is a program module that performs template management processes for document templates managed in the template database 212, such as accepting operations to register templates, editing templates, and notifying each user about edited templates.

[0071] The consultation processing module 2050 is a program module that updates databases such as the legal consultation management database 217 by processing consultations to the department in charge of consultations and by predicting the workload of consultations to the department in charge of consultations.

[0072] The payment confirmation processing module 2051 is a program module that generates a list of payment confirmations based on concluded contracts and updates the payment confirmation list database 218, generates a payment record database 219 related to payment records, and performs various processes such as payment confirmation processing and setting the person in charge in the case of non-payment by comparing these.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0093] <2 Data Structure> Figure 4 shows the data structure of the user database 211. The user database 211 includes the fields "User ID", "Business ID", "Name", "Email Address", "Department", "Position", "Date of Employment", "Date of Resignation", and "Qualifications Held".

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

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

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

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

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

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

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

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

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

[0103] 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. Figure 5 shows the data structure of the template database 212. The template database 212 includes the following items: "Contract template ID", "Contract document type", "Contract data", "Related legal tags", "Related issue tags", "Links to explanations of related laws and issues", "Status", "Start date of use", and "End date of use".

[0104] The item "Contract Template ID" is information that identifies each contract template managed by server 20.

[0105] The item "Contract Document Type" contains information about the type of contract template.

[0106] The item "Contract Document Type" may include contract templates and the following: Typical contract • Atypical contracts Term sheet template The item "Contract Data" contains information about the data file for the contract template.

[0107] More specifically, the item "Contract Data" is a data file in an editable format.

[0108] The item "Related Legal Tags" contains information about the types of laws and regulations related to the contract template.

[0109] The item "Related Legal Tags" may include the following as types of laws related to the contract template: • Information identifying the clauses in the contract template (for example, clauses such as "Article 3" or clauses such as "Article 4, Paragraph 2"), and relevant legal information for each clause. • Information on the entire contract (including the type of contract, such as a "non-disclosure agreement") and relevant laws and regulations. The item "Related Issue Tags" contains information about the types of issues related to the contract template.

[0110] The item "Related Issue Tags" may include the following as types of issues related to the contract template: • Information identifying the clauses in the contract template (for example, clauses such as "Article 3" or clauses such as "Article 4, Paragraph 2"), along with information on related issues for each clause. • Information on the entire contract (including the type of contract, such as a "non-disclosure agreement") and related issues. The item "Links to Explanations of Relevant Laws and Issues" contains reference information that includes explanations of laws and issues related to the contract.

[0111] The item "Links to explanations of related laws and issues" may include the following as reference information: • Information on links to books included in the book browsing service provided by server 99. This may also include links to sections in the book that explain the relevant laws and issues. • Information on links to articles posted on information media that provide legal information on websites. • Information on links to explanatory articles about laws or precedents, provided by Server 94 and other servers of the Legal and Case Law Information Provision Service. • Links to guidelines, standards, etc. issued by public institutions. The "Status" field indicates whether the contract template is available for use.

[0112] The "Status" field may include the following information regarding availability: • In use: Available as a template • Before use: A template is provided, but it is not yet usable. For example, it may become usable after a legal amendment is applied. • Under revision: The template is currently being revised. It may be considered unusable as a template, or it may be considered usable. • Termination of Use: Not currently used as a template. For example, its use as a template may be terminated due to the application of legal revisions. The item "Start Date of Use" contains information about when the template began to be used.

[0113] The item "Usage Termination Date" contains information about when the template will no longer be used.

[0114] Figure 6 shows the data structure of the approval request database 213. The approval request database 213 includes the fields "Approval Request ID", "Applicant ID", "Approver ID", "Application Date", "Approval Date", "Application Details", and "Contract ID".

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

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

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

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

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

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

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

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

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

[0124] 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 215. This links the approval application data in the approval application database 213 with the contract signing data in the contract signing management database 215.

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

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

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

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

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

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

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

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

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

[0134] 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. Figure 8 shows the data structure of the contract management database 215. The contract management database 215 includes the following fields: "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".

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

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

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

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

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

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

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

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

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

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

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

[0146] 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 215 will also manage each of the specified email addresses.

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

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

[0149] 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 and approves the document data, 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 215.

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

[0151] Specifically, the item "Contract Completion Date and Time" is recorded in the contract management database 215 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.

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

[0153] 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 9 shows the data structure of the document management database 216. The document management database 216 includes the following items: "Document Management ID", "Contract Signing ID", "Document Title", "Contract Start Date", "Contract Expiration Date", "Automatic Renewal Status", and "Viewing Permission".

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

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

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

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

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

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

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

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

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

[0163] The item "Viewing Permission" is information about users who are set to have viewing permission for documents (e.g., contracts) managed in the document management database 216. Server 20 may allow users set as stakeholders of a document to view the document, and may not allow users who are not set to view the document to view it.

[0164] Specifically, the "Viewing Permissions" item may be used to manage the following users as stakeholders in the document data. - Users recorded in the contract management database 215 as users who approve document data. Note that the server 20 may identify the parties involved in the document data by referring to the users who approved the document data in the contract management database 215, rather than retaining the information of the parties involved in the document management database 216. • 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. • Other users designated by users who approve the document data, users who have permission to view the document data, etc. Furthermore, the "Viewing Permissions" item may be configured to include information that identifies departments or divisions within an organization, rather than individuals. For example, it may be possible to configure information corresponding to the "Department" item in user database 211. In other words, by defining which departments or divisions can view documents, users in those departments or divisions within the organization can view the documents.

[0165] Figure 10 shows the data structure of the legal consultation management database 217. The legal consultation management database 217 includes the following fields: "Consultation ID", "Consultation Date and Time", "Consultant User ID", "Consultant Department", "Consultation Title", "Consultation Content", "Consultation Type", "Source of Consultation Content Extraction", "Summary of Extracted Consultation Content", "Consultation Content Extraction Date and Time", "Response Date and Time", "Respondent User ID", "Respondent Department", "Response Content", and "Consultation Status".

[0166] The "Consultation ID" field is information that identifies each individual consultation history between departments.

[0167] The item "Consultation Date and Time" indicates the time when the consultation was received.

[0168] More specifically, the item "Consultation Date and Time" includes information about the timing when a consultation request was sent to a specific department, such as the legal department, from another department via messaging tools or similar means.

[0169] The item "Consultant User ID" is information that identifies the user who made the consultation.

[0170] The item "Consultant User ID" may be associated with the item "User ID" in user database 211.

[0171] The "Consultant Department" field contains information about the department to which the user who submitted the consultation belongs.

[0172] The item "Consultant Department" may be associated with the item "Department" in user database 211.

[0173] The item "Consultation Title" contains information about the brief title of the consultation.

[0174] More specifically, the item "Consultation Title" may be the title set by the consultant, or it may include the result summarized by the server 95 of the large-scale language model service based on the consultation content.

[0175] The item "Consultation Details" contains information about specific consultations from other departments.

[0176] More specifically, the item "Consultation Details" includes information about the consultation details entered by the person seeking advice.

[0177] The item "Type of consultation" contains information about the attributes of the consultation content.

[0178] More specifically, the item "Type of consultation" may include information on the type set by the person seeking consultation or the user of the department handling the consultation, or attribute information assigned by the server 95 of the large-scale language model service based on information such as the content of the consultation and the department of the person seeking consultation.

[0179] The item "Source of Consultation Content" contains information about the source from which the consultation content was extracted.

[0180] More specifically, the item "Source of Consultation Content" may be the result of the user making the consultation specifying a link to a post made in the messaging tool, or it may include business data on the consultation content collected by Server 20 without user operation, such as data created by the department making the consultation, which is managed by the messaging service server 98, the sales support system service server 97, the document creation service server 96, etc., and which contains specific keywords related to the consultation (for example, words that frequently appear in consultations with the legal department, such as "contract" and "legal risk," or words that are set in advance by the legal department, etc.).

[0181] The item "Summary of extracted consultation content" contains information summarizing the consultation content extracted from the information source.

[0182] More specifically, the item "Summary of Extracted Consultation Content" includes information obtained by identifying business data that meets certain conditions, such as containing specific keywords, from the information source, and summarizing the content of that data using the large-scale language model service server 95, etc. The summarization method may involve abstractly summarizing the content mentioned in the information source (for example, abstracting the themes being discussed), or by extracting the most important words from those mentioned in the information source. The summary may be in sentence form or word form.

[0183] The item "Date and time of extraction of consultation content" contains information about when the consultation content was extracted.

[0184] More specifically, the item "Date and time of extraction of consultation content" may be the time when the business data was generated at the information source that was extracted, or it may include information about the time when the extraction was performed.

[0185] The "Response Date and Time" field indicates the timing at which the response to the inquiry was provided by the department responsible for the response.

[0186] The item "Respondent User ID" is information that identifies the user who initiated the consultation.

[0187] The item "Respondent User ID" may be associated with the item "User ID" in user database 211.

[0188] The "Respondent Department" field contains information about the department to which the user who submitted the consultation belongs.

[0189] The item "Respondent Department" may be associated with the item "Department" in user database 211.

[0190] The item "Response Content" contains information about the response provided by the respondent to the consultation.

[0191] The "Consultation Status" field provides information about the current status of the consultation.

[0192] More specifically, the item "Consultation Status" includes statuses such as "Not Response," "Response Completed," etc.

[0193] Figure 11 shows the data structure of the payment confirmation list database 218. The payment confirmation list database 218 includes the following items: "Payment Confirmation List ID", "Business ID", "Document Management ID", "Customer Name", "Invoice Amount", "Expected Payment Date", "Invoice Issued Flag", "Payment Matching Status", "Payment Confirmation Date and Time", and "Contact Person".

[0194] The item "Payment Confirmation List ID" is an identifier used to uniquely identify each record in each payment confirmation list.

[0195] The "Business ID" field is identification information used to identify the organization using the payment confirmation list.

[0196] The "Business ID" field can be associated with the "Business ID" field in user database 211.

[0197] The item "Document Management ID" is a unique identifier for the contract extracted from the contract data.

[0198] The item "Document Management ID" can be associated with the item "Document Management ID" in document management database 216.

[0199] The item "Customer Name" is the name of the counterparty (customer) to the relevant contract, and is information used to identify the customer when confirming payment.

[0200] The item "Invoiced Amount" is the amount invoiced based on the contract and is numerical data used for comparison when matching payments.

[0201] The item "Expected Payment Date" is the payment deadline or expected payment date stipulated in the contract, and is date information used to verify it against the actual payment date.

[0202] The "Invoice Issued Flag" item indicates whether or not an invoice has already been issued; 1 means issued, and 0 means not issued.

[0203] The "Payment Reconciliation Status" item shows the result of reconciling the billing information based on the contract with the actual payment records (e.g., bank data / accounting system data), indicating a status such as successful, mismatched, or unpaid.

[0204] The item "Payment Confirmation Date and Time" is the date and time when the payment confirmation (matching) process was finally performed, and is used for managing the timing of data updates and reconfirmations.

[0205] The item "Contact Person" is the name of the person (or group) responsible for contacting and following up in the event of any discrepancies in the matching results (e.g., non-payment, discrepancy in amount, etc.).

[0206] Figure 12 shows the data structure of the deposit record database 219. The deposit record database 219 includes the fields "Record ID", "Remitter Name", "Deposit Amount", "Deposit Date", "Customer Name", "Deposit Method", "Deposit Processing Status", "Attached Detail File Path", and "Modified Flag".

[0207] The "Record ID" field is an identification number used to uniquely identify each deposit record data, and it is a non-repeating value within the system.

[0208] The item "Remitter Name" is information indicating the name of the account holder used for the deposit (the name of the individual or company displayed as the payer).

[0209] The item "Amount Received" is the actual amount received as recorded in the accounting system, and is usually managed in yen and treated as a numerical value.

[0210] The item "Payment Date" is the date the payment was made as recorded in the accounting system, and is date and time information used to verify consistency with the processing date and closing date.

[0211] The item "Customer Name" is the name of the customer to whom the transfer was made, as registered in the deposit record. This information, along with the account information, is used to verify the recipient.

[0212] The item "Payment Method" indicates the payment method or transfer method used at the time of payment and is attribute information used for classification within the system.

[0213] The "Deposit Processing Status" field indicates the status of the transaction (e.g., successful, error), such as whether the deposit record was processed successfully or if an error occurred.

[0214] The item "Attached Details File Path" is data file information that indicates the path or file name of the file containing the details of the deposit output from the accounting system.

[0215] The "Modified Flag" item indicates whether the contents of the deposit record have been corrected or confirmed at a later date. Typically, 1 indicates confirmed and 0 indicates unconfirmed.

[0216] <3 operations> Figure 13 shows the process flow for generating a payment confirmation list based on concluded contracts, comparing it with payment records to extract unpaid transactions, and determining who is responsible for contacting those with unpaid transactions.

[0217] In step S1311, terminal 10 receives an operation from the user to select or upload contract data. This triggers the start of the process of extracting billing information based on the contract.

[0218] The following explains the process of issuing invoices (payment deadline), extracting customer names and expected payment amounts, and verifying that the contract and payment amounts match, making it easy to match contracts and payments and ensuring no unpaid amounts are overlooked, all in accordance with the billing information specified in the contract.

[0219] This processing flow divides the tasks between the terminal and the server, including the automatic extraction of expected payment amounts from contracts, integration with external systems, automatic information verification, inconsistency detection, and final assignment of responsible personnel. Furthermore, by allowing users to check the status in real time on their terminals, it becomes easier to respond to payment confirmations.

[0220] The document management database 216 of the memory unit 202 is configured to store contract data, which is a signed contract document that has been approved by the parties to the contract and specifies the terms and conditions of the contract.

[0221] In step S1321, the payment confirmation processing module 2051 of the server 20 processes the received contract data using OCR or an analysis engine, or analyzes the contract data managed in the document management database 216 to extract and structure each item of billing information (e.g., customer name, billing amount, payment deadline, etc.).

[0222] In this manner, the payment confirmation processing module 2051 extracts the contract terms for payment, including the payment amount, and the information of the other party to the contract, from among the contracts stored in the storage unit 202 in association with the user, for contracts for which payment of expenses is to be received, and stores them as a payment confirmation list (payment confirmation list database 218) in association with the user. • Example of a payment confirmation list based on a contract: Extract information from the contract, including price (the amount received as the seller), party (the name of the other party at the time of payment confirmation), and payment date (the payment date as stipulated in the contract). The payment confirmation processing module 2051 may also extract information on the transaction price and the timing of the payment, as contract terms for payments received, based on the terms and conditions of the contract, and store this information as a list for payment confirmation.

[0223] In step S1312, terminal 10 receives a screen operation from the user and sends a request to retrieve deposit records from the bank or accounting system.

[0224] In step S1322, the deposit confirmation processing module 2051 of the server 20 retrieves the deposit record for the user's transaction. The deposit confirmation processing module 2051 retrieves the deposit record data (e.g., name of the transferor, deposit amount, deposit date, etc.) via the bank or accounting system API, normalizes it, and stores it in the deposit record database 219. • Bank deposit records, deposit records imported into the accounting system The deposit confirmation processing module 2051 may acquire deposit records related to the user's transactions, which may include at least one of the deposit records imported into the accounting system or deposit records related to the bank account.

[0225] In step S1323, the payment confirmation processing module 2051 of the server 20 compares a list of payment records (payment record database 219) that associates the remitter's name and the payment amount included in the acquired payment record with a list for payment confirmation (payment confirmation list database 218) generated based on the contract, and outputs the comparison result. The payment confirmation processing module 2051 automatically compares and matches the stored billing information with the payment records. The payment confirmation processing module 2051 performs matching processing based on each item (customer, amount, payment date, etc.) and determines whether there is a match or a mismatch. • How to present the results of comparing the actual deposit amount with the deposit confirmation list based on the contract: Display that the parties are correct but the deposit amount differs from that in the contract. The payment confirmation processing module 2051 may output a comparison result, and if there are matching parties in both the payment record list and the payment confirmation list, but the record of the payment amount differs from the contract terms relating to the payment, it may output a statement indicating that the record of the payment amount differs from the contract terms relating to the payment. • How to present the results of comparing the actual deposit amount with the deposit confirmation list based on the contract: The amount may match, but the parties to the contract and the parties to the deposit may not match (for example, there is a possibility that the transfer was made under a different name (different company, individual)). The payment confirmation processing module 2051 may output a comparison result, and if the payment amount recorded in the payment record list and the payment confirmation list matches the contract terms, but the name of the remitter in the payment record does not match the party in the contract, it may output a statement to that effect. • Extraction of the list of unpaid items (method for generating a list for contacting payment confirmation): Based on the comparison, items for which the counterparty is not found and there is no matching amount are extracted as the list of unpaid items. The payment confirmation processing module 2051 may output the comparison results, and may output as a list of unpaid amounts any payments from the payment confirmation list in which the party is not extracted from the payment record and there is no matching amount. • Setting up contact information and contact persons for unpaid items: The unpaid item list should include who will contact the person responsible (contact person) and who to contact for verification (recipient). The payment confirmation processing module 2051 may output a list of unpaid transactions, and may output a list of unpaid transactions that includes user information related to the contract for the transaction in question, as well as user information related to the notification of the unpaid transaction.

[0226] The payment confirmation processing module 2051 may assign the contracting person or group of organizations to the person responsible for contacting those who have not received payment and to the party to whom the non-payment should be reported. The payment confirmation processing module 2051 may output a list of non-payments that includes the user responsible for the contract or the group of organizations responsible for the contract as information related to the user of the non-payment transaction, and the contact person for reporting the non-payment.

[0227] In step S1313, terminal 10 displays a summary of the matching results sent from server 20 (e.g., normal, amount mismatch, customer mismatch, unpaid) on the screen and provides feedback to the user on the situation.

[0228] In step S1324, the payment confirmation processing module 2051 of server 20 automatically detects discrepancies or cases where no corresponding payment record exists (unpaid) based on the matching results, and sets an error flag or alert status for each record. • Providing management with information to help them decide whether to continue doing business with the company: Credit assessment based on a list of unpaid accounts. Creditworthiness is assessed to decrease depending on the history of unpaid accounts. The payment confirmation processing module 2051 evaluates each party included in the list of unpaid accounts, and may perform a step to evaluate each party according to the length of time the transaction parties have been included in the list of unpaid accounts. For example, each party may be evaluated such that the longer the period in which they have been included in the list of unpaid accounts, the lower their creditworthiness. Alternatively, even if a transaction party has been included in the list of unpaid accounts, each party may be evaluated such that the shorter the period in which they have been included, the higher their creditworthiness.

[0229] More specifically, the payment confirmation processing module 2051 may display the results of the credit assessment based on the frequency of payment confirmation and the likelihood of payment after confirmation. The payment confirmation processing module 2051 may also evaluate the parties to transactions included in the list of unpaid transactions based on at least one of the following: the frequency of contacting them regarding payment confirmation and the likelihood of payment after contacting them regarding payment confirmation. For example, the more frequently payment confirmations are made, the lower the creditworthiness; the lower the likelihood of payment after contacting them regarding payment confirmation (e.g., a certain period of time elapses between contacting them and payment not being made), the lower the creditworthiness; and the less frequently payment confirmations are made and the higher the likelihood of payment after contacting them regarding payment confirmation (e.g., payment is made after only one contact regarding payment confirmation), the higher the creditworthiness. • When issuing a notice prompting a review of contract terms (at the time of contract renewal), the results of the credit assessment will be displayed (the results of the credit assessment will be displayed as reference when deciding whether to renew the contract). The payment confirmation processing module 2051 provides notifications based on the contract period for the contract data of concluded contracts stored in the document management database 216 of the storage unit 202 (for example, upon the expiration of the contract period, it provides a notification to confirm whether or not the contract will be renewed before the expiration date). The payment confirmation processing module 2051 may also provide a notification regarding the contract period along with the results of an evaluation of the counterparty to the contract. • Invoice Issuance: Issue invoices based on contract terms. Set up automatic invoice issuance. The payment confirmation processing module 2051 may also perform a step of issuing invoice data based on the contract terms regarding the amount for the contract data of concluded contracts stored in the document management database 216 of the storage unit 202. For example, in an invoice issuance service, it may send instructions to issue an invoice based on the parties, contract amount, payment deadline, etc., of the contract data. In addition, if invoices are issued periodically (e.g., maintenance contracts, consulting contracts), it may be possible to set up automatic invoice issuance based on the parties, contract amount, payment deadline, etc., of the contract data.

[0230] In step S1314, terminal 10 displays detailed information and warning messages regarding the mismatch / non-payment status, prompting the user to review and decide on necessary actions (e.g., manual re-verification or corrective input).

[0231] In step S1325, the payment confirmation processing module 2051 of server 20 aggregates the overall comparison results and automatically determines and assigns the person responsible for contacting those who have not made payments, based on rules within the system (e.g., past contact history, assigned area, contract information, etc.).

[0232] In step S1315, terminal 10 displays the final result report and information of the person responsible for contacting the unpaid customer (name, contact information, etc.) on the screen, providing it as a trigger for alert notifications and the next action (initiating contact).

[0233] <4 Screen Examples> Figure 14 shows an example of an operation screen that generates a payment confirmation list based on concluded contracts, compares it with payment records to extract unpaid transactions, and determines who is responsible for contacting those with unpaid transactions.

[0234] Operation screen 1400 is a screen that generates a payment confirmation list based on the concluded contract, compares it with the payment record, extracts transactions with outstanding payments, and determines who is responsible for contacting those with outstanding payments.

[0235] The operation screen 1400 corresponds to each process in Figure 13.

[0236] The contract status list display area 1402 displays basic contract information such as the trading partner, amount, and payment due date in a list format, and highlights any discrepancies in the amount or parties using color coding and icons.

[0237] The payment reconciliation result display area 1404 is an area that highlights the reconciliation results between billing information and payment records using color coding and icons, categorized by status such as normal, mismatch, and insufficient payment.

[0238] The unpaid list display area 1406 is an area that displays cases determined to be unpaid in a list format, and simultaneously displays the assigned person and contact status for each item to ensure visibility.

[0239] The credit assessment summary display area 1408 is an area that displays a list of summary information such as credit scores and assessment results based on the payment history and contact history of each contract.

[0240] The contract and payment record parallel display area 1410 is an area that displays individual contract data and corresponding payment records side-by-side or top-and-bottom for comparison, highlighting discrepancies such as amounts and differences between parties to make them easier to see.

[0241] The contact history display area 1412 is an area that displays the contact status by the person in charge, past contact history, and reminder settings in a timeline or list format.

[0242] The Person in Charge Assignment Designation Unit 1414 is an input field for specifying the person in charge of contacting unpaid cases using a dropdown list or selection items, and is an operating component that accepts the designation.

[0243] The contact status specification unit 1416 is a text box for entering and registering the contact status and remarks for each case in free text, and is an operating component that accepts specifications.

[0244] The reminder setting operation unit 1418 is an operation button for confirming the registration or update of a reminder for unpaid cases, and is an operation component that accepts operations.

[0245] The search / filter specification section 1420 is an input object such as a dropdown, checkbox, or date picker for narrowing down the displayed data, and is an operating component that accepts specifications.

[0246] The screen update operation unit 1422 is a button that allows the user to re-acquire the latest contract and payment information and update the entire screen; it is an operating component that accepts user input.

[0247] The data export operation unit 1424 is an operation button for exporting the displayed list information to a file in a format such as a CSV spreadsheet, and is an operation component that accepts such operations.

[0248] <Other> The features described in each of the above embodiments can be combined. In the above description of embodiments, an example was described in which the server 20 communicates with the server 95 of the large-scale language model service to prompt the large-scale language model and have it execute processing. In this way, the server 20 can prompt a system that performs language processing to perform information processing according to the prompt. Such an information processing system that performs language processing may use an external device (for example, the server 95 of the large-scale language model service), or it may be executed by an information processing system built into the server 20 or terminal 10 (for example, a processor for language processing).

[0249] A network consists of various mobile communication systems, such as the internet, LANs, and wireless base stations. For example, a network includes 3G, 4G, and 5G mobile communication systems, LTE (Long Term Evolution), and wireless networks that can connect to the internet via designated access points (e.g., Wi-Fi®). When connecting wirelessly, communication protocols include, for example, Z-Wave®, ZigBee®, and Bluetooth®. When connecting via a wired connection, the network also includes connections made directly via USB (Universal Serial Bus) cables, etc.

[0250] Furthermore, by distributing all or part of each hardware configuration across multiple computers and connecting them to each other via a network, a computer can be virtually realized. Thus, the concept of a computer includes not only computers housed in a single enclosure or case, but also virtualized computer systems.

[0251] A database, specifically a relational database, is used to manage and link together tabular data sets called masters, which are structurally defined by rows and columns. In a database, tables are called tables, masters are called masters, the columns of tables are called columns, and the rows of tables are called records. In a relational database, relationships can be established and linked between tables and masters.

[0252] Typically, each table and master has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit can instruct the processor 901 to add, delete, or update records in specific tables and masters stored in the memory unit, according to various programs.

[0253] Furthermore, by storing data, various programs, and various databases in the storage unit, the information processing apparatus and the information processing system according to the present disclosure can be regarded as being manufactured.

[0254] Note that the database and master in the present disclosure may include any data structure (such as a list, dictionary, associative array, or object) in which information is structurally defined. The data structure shall also include data that can be regarded as a data structure by combining data with functions, classes, methods, etc. described in any programming language.

[0255] Furthermore, some or all of the respective configurations, functions, processing units, processing means and the like described above may be implemented in hardware, for example, by designing them as integrated circuits. The present invention can also be implemented by software program code that realizes the functions of the embodiments. In this case, a computer is provided with a storage medium on which the program code is recorded, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the aforementioned embodiments, and the program code itself and the storage medium storing the same constitute the present invention. As the storage medium for supplying such program code, for example, a flexible disk, CD-ROM, DVD-ROM, hard disk, SSD, optical disk, magneto-optical disk, CD-R, magnetic tape, non-volatile memory card, ROM and the like are used.

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

[0257] Furthermore, by distributing the program code of the software that implements the functions of the embodiments via a network, the program code may be stored in a storage means such as a hard disk or a memory of a computer, or a storage medium such as a CD-RW or a CD-R, and a processor included in the computer may read and execute the program code stored in the storage means or the storage medium.

[0258] The functions implemented by the components described in the present specification may be implemented in circuitry or processing circuitry, including general purpose processors, special purpose processors, integrated circuits, ASICs (Application Specific Integrated Circuits), CPU (a Central Processing Unit), conventional circuits, and / or combinations thereof, that are programmed to implement the described functions. A processor includes transistors and other circuits, and is regarded as circuitry or processing circuitry. The processor may be a programmed processor that executes a program stored in a memory.

[0259] In the present specification, circuitry, a unit, and a means are hardware that is programmed to implement the described functions, or hardware that executes the described functions. The hardware may be any hardware disclosed in the present specification, or any hardware known to be programmed to implement or execute the described functions.

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

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

[0262] (Note) The details described in each of the above embodiments are noted below.

[0263] (Note 1) A program for operating a computer having one or more computer processors, configured in a memory unit to store contract data, which is a concluded contract document that specifies the terms and conditions of the contract and has been approved by the parties to the contract, the program causing one or more computer processors to perform the following steps: extract the contract terms for payments, including the amount to be paid, and the information of the other party to the contract, from among the contract documents stored in the memory unit in association with the user, for contracts for which payment of fees is received, and store them as a payment confirmation list associated with the user; obtain a record of payments related to the user's transactions; compare a list of payment records, which associates the name of the remitter and the amount to be paid, included in the payment record obtained in the acquisition step, with a payment confirmation list generated based on the contract, and output the comparison result.

[0264] (Note 2) In the retention step, for contracts receiving payment of fees, the program extracts information on the transaction price and the timing of the payment, based on the contract terms of the contract, and retains this information as a list for payment confirmation, as contract terms for payment including the amount received, as described in Appendix 1.

[0265] (Note 3) A program as described in either Appendix 1 or 2, which, in the acquisition step, acquires records of deposits related to user transactions, specifically records of deposits imported into an accounting system or records of deposits related to a bank account.

[0266] (Note 4) In the output step, the program outputs the comparison result, and if there are matching parties in both the list of deposit records and the list of deposit confirmations, but the record of the deposit amount differs from the contract terms relating to the deposit, the program outputs a statement indicating that the record of the deposit amount differs from the contract terms relating to the deposit, as described in any of the appendices 1 to 3.

[0267] (Note 5) In the output step, the program outputs the comparison result, and if the recorded amount of the deposit matches the contract terms in the deposit record list and the deposit confirmation list, but the name of the remitter in the deposit record does not match the party in the contract, it outputs a statement to that effect, as described in any of the appendices 1 to 4.

[0268] (Note 6) In the output step, the program outputs the comparison results, and among the payment confirmation list, those for which no party is extracted in the payment record and no matching amount exists are output as a list of unpaid amounts, as described in any of the appendices 1 to 5.

[0269] (Note 7) The program described in Appendix 6 outputs a list of unpaid items, which in the output step includes user information related to the contract for the transaction in question, as well as user information related to the notification of the unpaid item.

[0270] (Note 8) The program according to Appendix 7, wherein in the outputting step, an unpaid list including, as the information of the user related to the contract for the unpaid transaction, the user who is the person in charge of the contract or the group of the organization in charge of the contract, as the information of the contact person in charge of the unpaid notification, is output.

[0271] (Appendix 9) The program according to any one of Appendices 6 to 8, which causes one or more computer processors to further execute a step of evaluating each party included in the unpaid list, wherein each party is evaluated according to a period during which the party to the transaction is included in the unpaid list.

[0272] (Appendix 10) The program according to Appendix 9, wherein in the evaluating step, the party to the transaction included in the unpaid list is evaluated according to at least one of a frequency of sending payment confirmation notifications and a probability of payment after sending the payment confirmation notification.

[0273] (Appendix 11) The program according to any one of Appendices 9 to 10, which causes one or more computer processors to further execute a step of sending a notification based on the contract period for the contract data of the concluded contract stored in the storage unit, wherein in the notifying step, the notification regarding the contract period is sent together with the result evaluated in the step of evaluating the counterparty to the contract.

[0274] (Appendix 12) The program according to any one of Appendices 1 to 11, which causes one or more computer processors to further execute a step of issuing invoice data for the contract data of the concluded contract stored in the storage unit, based on the contract conditions regarding the amount of money.

[0275] (Appendix 13) A method performed by a computer having one or more computer processors, wherein the storage unit is configured to store contract data, which is a concluded contract document that specifies the terms and conditions of the contract and has been approved by the parties to the contract, the method comprising: one or more computer processors extracting, from among the contract documents stored in the storage unit in association with a user, the contract terms for payments, including the amount to be paid, and the information of the other party to the contract, and storing them as a payment confirmation list in association with the user; obtaining a record of payments relating to the user's transactions; comparing a list of payment records, which associates the name of the remitter and the amount to be paid, included in the payment record obtained in the obtaining step, with a payment confirmation list generated based on the contract, and outputting the comparison result.

[0276] (Note 14) Information processing device, configured in a memory unit to store contract data, which is a concluded contract document that has been approved by the parties to the contract and specifies the terms and conditions of the contract, wherein the control unit of the information processing device performs the following steps: extracting contract terms for payments, including the amount to be paid, and information of the other party to the contract, from among the contract documents stored in the memory unit in association with the user, for contract documents for which payment of expenses is received, and storing them as a payment confirmation list in association with the user; acquiring records of payments related to the user's transactions; comparing a list of payment records, which associates the name of the remitter and the amount to be paid, included in the payment records acquired in the acquisition step, with a payment confirmation list generated based on the contract, and outputting the comparison result.

Claims

1. A program for operating a computer having one or more computer processors, The memory unit is configured to store contract data, which is a signed contract document that has been approved by the parties to the contract and specifies the terms and conditions of the contract. The program is configured on one or more computer processors. The steps include extracting the contract terms regarding payment, including the amount received, and the information of the other party to the contract, from among the contracts stored in the memory unit in association with the user, for contracts that receive payment of fees, and storing them as a payment confirmation list in association with the user, The steps include obtaining a record of the deposit related to the user's transaction, A program that performs the steps of: comparing a list of deposit records, which associates the name of the remitter and the amount of the deposit included in the deposit record obtained in the aforementioned acquisition step, with the deposit confirmation list generated based on the contract, and outputting the comparison result.

2. The program according to claim 1, in the step of retaining, extracts information on the price of the transaction and information on the timing of the payment of the transaction as contract terms for the payment of the payment, including the amount of payment, based on the contract terms of the contract, with respect to the contract for which payment of the expenses is to be received, and retains them as a list for payment confirmation.

3. The program according to claim 1, wherein in the step of acquiring the above-mentioned acquisition, the program acquires at least one of the following: a record of deposit related to the user's transaction, which is a record of deposit imported into an accounting system or a record of deposit related to a bank account.

4. The program according to claim 1, wherein in the output step, the comparison result is output, and if there are matching parties in both the list of deposit records and the list for deposit confirmation, but the record of the deposit amount differs from the contract terms relating to the deposit, the program outputs a statement indicating that there are records of deposit amounts that differ from the contract terms relating to the deposit.

5. The program according to claim 1, wherein, in the output step, the comparison result is output, and if the record of the deposit amount matches the contract terms in the deposit record list and the deposit confirmation list, but the name of the remitter in the deposit record does not match the party in the contract, that fact is output.

6. The program according to claim 1, wherein, in the output step, the comparison results are output, and among the payment confirmation list, those for which no party is extracted in the payment record and no matching amount exists are output as a list of unpaid amounts.

7. The program according to claim 6, wherein in the output step, the output of the list of unpaid invoices includes, as the user information relating to the contract for the transaction relating to the unpaid invoice, the user information relating to the notification of the unpaid invoice.

8. The program according to claim 7, which in the output step outputs a list of unpaid transactions, including, as user information related to the contract for the unpaid transaction, the user of the person in charge of the contract or the group of organizations in charge of the contract, and as contact person information for contacting the person who will contact

9. The program further provides the following to one or more computer processors: The program according to claim 6, which performs the step of evaluating each party included in the list of unpaid invoices, wherein the evaluation of each party is performed according to the period of time that the parties to the transaction are included in the list of unpaid invoices.

10. The program according to claim 9, which in the evaluation step evaluates the parties to the transactions included in the list of unpaid transactions according to at least one of the frequency of contacting them to confirm payment and the likelihood of payment after contacting them to confirm payment.

11. The program further provides the following to one or more computer processors: The memory unit is made to execute a step of notifying the contract holder of the contract data of the concluded contracts based on the contract period. The program according to claim 9, wherein in the step of making the notification, along with the notification regarding the contract period, the program also notifies the other party to the contract of the results of the evaluation conducted in the evaluation step.

12. The program further provides the following to one or more computer processors: The program according to claim 1, which causes the program to execute a step of issuing invoice data based on the contract terms regarding the amount of the contract data of the concluded contract stored in the memory unit.

13. A method performed by a computer having one or more computer processors, The memory unit is configured to store contract data, which is a signed contract document that has been approved by the parties to the contract and specifies the terms and conditions of the contract. The above method involves one or more computer processors, The steps include extracting the contract terms regarding payment, including the amount received, and the information of the other party to the contract, from among the contracts stored in the memory unit in association with the user, for contracts that receive payment of fees, and storing them as a payment confirmation list in association with the user, The steps include obtaining a record of the deposit related to the user's transaction, A method comprising the steps of: comparing a list of deposit records, which associates the name of the remitter and the deposit amount included in the deposit record obtained in the aforementioned acquisition step, with the deposit confirmation list generated based on the contract, and outputting the comparison result.

14. An information processing device, The memory unit is configured to store contract data, which is a signed contract document that has been approved by the parties to the contract and specifies the terms and conditions of the contract. The control unit of the information processing device, The steps include extracting the contract terms regarding payment, including the amount received, and the information of the other party to the contract, from among the contracts stored in the memory unit in association with the user, for contracts that receive payment of fees, and storing them as a payment confirmation list in association with the user, The steps include obtaining a record of the deposit related to the user's transaction, An information processing device that performs the steps of: comparing a list of deposit records, which associates the name of the remitter and the deposit amount included in the deposit record obtained in the aforementioned acquisition step, with the deposit confirmation list generated based on the contract, and outputting the comparison result.

Images