Information processing device, method, program

Abstract

There is a need for technology that can encourage more reliable payment fulfillment when there is a contractual obligation to pay. [Solution] 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 steps of: detecting that there is a payment obligation in the terms and conditions defined in the contract data; and, if there is a payment obligation in the contract data, charging the parties to the contract in accordance with that obligation without requiring them to perform a payment operation.

Description

Technical Field

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

Background Art

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

[0003] Conclusion of contracts through electronic contracts is also being promoted. Patent Document 1 points out that it is an issue to "prevent unauthorized agency by a person without authority in an electronic contract service", and describes that "by enabling appropriate setting of an approver on the receiver side of the electronic contract service, it is possible to suppress unauthorized agency in a case where a receiver without approval authority is set."

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of Invention

Problems to be Solved by the Invention

[0005] After a contract is concluded, payment based on the contract terms is performed, and various payment methods can be used. However, for some contracts, it is difficult to take countermeasures in a case where the obligation is not fulfilled (for example, non-payment of child support) even though payment is stipulated as an obligation.

[0006] Therefore, there is a need for technology that can encourage more reliable payment fulfillment when there is a contractual obligation to pay. [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 specifying the terms and conditions of the contract, approved by the parties to the contract. The program causes one or more computer processors to perform the steps of: detecting that there is a payment obligation in the terms and conditions specified in the contract data; and, if there is a payment obligation in the contract data, charging the parties to the contract in accordance with that obligation without requiring a payment operation. [Effects of the Invention]

[0008] This disclosure can encourage more reliable payment fulfillment when there is a contractual payment obligation. [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 process flow for detecting whether or not there is a payment obligation from contract data, and for automatically processing charges if the obligation is confirmed. [Figure 11] Figure 11 shows the process flow for handling non-payments based on contract data, including applying service usage restrictions at a predetermined time and recalculating the credit score. [Figure 12] Figure 12 is an example of an operation screen that displays details such as contract contents, payment obligations, and payment terms to the user, and shows the execution status when the system automatically charges. [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] Furthermore, in the following description, "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). At least one processor may be single-core or multi-core.

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

[0013] Furthermore, in the following description, expressions 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] Furthermore, in the following description, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be a single table.

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

[0016] The program may be installed in an apparatus such as a computer, or may be stored in, for example, a program distribution server or a computer-readable (for example, non-transitory) 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 description, identification numbers are used as identification information for various targets, but types of identification information other than identification numbers (for example, identifiers including alphabetic characters and codes) may be adopted.

[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, such as the user database 211, template database 212, approval request database 213, review history database 214, contract signing management database 215, document management database 216, and legal consultation management database 217.

[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 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, and consultation processing module 2050.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0100] Specifically, the item "Qualifications Held" includes the following information regarding the qualifications held by the user. • Qualifications that are expected to demonstrate expertise in reviewing 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".

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0162] <3 operations> Figure 10 shows the process flow for detecting whether or not there is a payment obligation from contract data, and for automatically processing charges if the obligation is confirmed.

[0163] In step S1011, terminal 10 accepts an operation from the user to confirm the contents of the contract (including whether or not there is a payment obligation) and to input or select contract data.

[0164] In step S1012, terminal 10 sends the contract data entered or selected by the user to the server.

[0165] The following explains the process of enforcing payment through billing for obligations as per the contract terms, and the process of setting unfavorable consequences for non-payment (such as inability to use the service or difficulty in obtaining a loan) to encourage payment.

[0166] The document management module 2045 on server 20 either extracts a contract specified by the user or a contract that the user has signed, analyzes the contract data, and verifies whether payment obligations are defined. If payment obligations are confirmed, it extracts the information necessary for settlement, initiates integration with the partnered payment system, and performs automatic billing. Finally, it records the processing results as a log and sends the results back to terminal 10 to provide feedback to the user. Through this processing flow, payment obligations based on contract terms are automatically detected, and billing is performed regardless of user operation. Furthermore, by integrating processes such as updating credit scores based on payment status and applying penalties, the system can set adverse effects such as usage restrictions to encourage payment fulfillment.

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

[0168] In step S1021, the document management module 2045 of server 20 detects that there is a payment obligation in the contract terms defined in the contract data. If the user specifies a contract, the document management module 2045 analyzes the contract data received from terminal 10 and checks whether the contract terms include an item regarding a payment obligation.

[0169] In step S1022, the document management module 2045 of server 20 extracts the information necessary for settlement (such as payment method and account information) if a payment obligation is recognized. • Billing method: Billing is done by linking the payment application with the contract signing and document management service. The document management module 2045 may also acquire information that identifies the user of a contracting party in a payment application used by that party to the contract relating to the contract data. • Payment methods: Bank account application with payroll deposit settings, credit card The document management module 2045 may also acquire information about bank accounts or credit cards used by the parties to a contract relating to contract data.

[0170] In step S1023, the document management module 2045 of server 20, if there is a payment obligation in the contract data, charges the parties to the contract according to that obligation without requiring any payment operation. The document management module 2045 communicates with the linked payment system or payment gateway and automatically executes the billing process. • Payment methods:

[0171] (Charged through a payment service linked to contract signing and document management services) The document management module 2045 stores contract data in the document management database 216 of the storage unit 202 through a service that manages contract data. The document management module 2045 may also perform billing through a function that processes payments related to the management of contract data, which is provided in the service that manages contract data.

[0172] (Charging via payment application) The document management module 2045 may also perform billing through the payment application based on the information obtained in step S1022 regarding the users of the parties to the contract.

[0173] (Charges are made via bank account or credit card) The document management module 2045 may also charge users of the contracting parties through their bank accounts or credit cards, based on the information obtained in step S1022. • Method of prompting payment: Transfer of assets. When a user making a payment purchases a product or service, the right to use, own, etc., that product or service is managed as belonging to the recipient of the payment. Document Management Module 2045 may stipulate that when a party obligated to make a payment under a contract pays for the cost of purchasing a product or service, the ownership of the product or the right to use the service relating to such payment shall belong to the party entitled to receive the payment under the contract. • Billing conditions: If mandatory, payment will be compulsory; if not mandatory, payment will be based on user action. Document management module 2045 may charge users when there is a payment obligation under a contract, regardless of whether the user of the paying party performs a payment operation, while charging users when there is no payment obligation under a contract requires the user of the paying party to perform a payment operation.

[0174] Document Management Module 2045 may be designed to enforce payments between individuals (e.g., child support) that are based on obligations and are made on an ongoing basis, rather than between corporations or between corporations and individuals. Document Management Module 2045 may charge users in contracts between individuals where there is a payment obligation, regardless of whether the paying party's user performs a payment operation. However, if the payment under the contract is not an obligation, it may charge users in contracts where there is a payment obligation, and charge users in contracts where a corporation is included as a party, unless the paying party's user performs a payment operation.

[0175] In step S1024, the document management module 2045 of server 20 records the result of the billing process (success or failure) in the system log and notifies terminal 10 of the result information.

[0176] In step S1013, terminal 10 displays the billing results received from the server on the screen and provides feedback to the user regarding the processing status.

[0177] Figure 11 shows the process flow for handling non-payments based on contract data, including applying service usage restrictions at a predetermined time and recalculating the credit score.

[0178] In step S1121, the document management module 2045 of the server 20 monitors contract data and settlement information and detects that payment has not been made within a specified period (out of payment status).

[0179] In step S1122, the document management module 2045 of the server 20, after detecting non-payment, transitions to non-payment branching processing at a predetermined time (e.g., after the grace period has elapsed). Based on the non-payment status, it applies penalties to the affected user, such as service usage restrictions, to encourage payment. Specifically, it implements processes such as reducing the communication speed of communication services or transitioning to a state where some functions are unavailable. • Enforceable payment: Restricts the user's use of a specified service if payment is not made despite being charged for something for which payment is required. Document management module 2045 may also perform a step to restrict the use of a specified product or service by the user of the party obligated to pay if there is a payment obligation in the contract data and the process of billing the party to the contract fails to make the payment.

[0180] Document management module 2045 may restrict the use of services other than contract execution and document management services. Document management module 2045 may restrict the use of services other than those that perform contract execution related to contract data.

[0181] More specifically, document management module 2045 may restrict the use of communications (e.g., reduced communication speed, reduced communication capacity, or suspension of communication services). Document management module 2045 may also restrict the use of other services, such as restricting the use of communication services used by users who have payment obligations under the contract.

[0182] More specifically, the document management module 2045 may be used as a service (mini-app) integrated into a super app such as a payment system, or it may result in unfavorable or impossible contract terms for insurance, loans, etc. The document management module 2045 may also restrict the use of other services, such as restricting the use of a service that is linked to a payment application used by a user who has a payment obligation under a contract.

[0183] In step S1123, the document management module 2045 of the server 20 simultaneously reflects information on unpaid bills and recalculates the user's credit score using the credit evaluation module. The document management module 2045 calculates the credit score based on the payment history under the contract and stores the calculated user's credit score in the user database 211 of the storage unit 202.

[0184] Thus, the document management module 2045 may calculate a credit score based on whether or not payments have been made to those for which payment obligations exist. The document management module 2045 evaluates the creditworthiness of a user based on the payment history of users who have been charged according to contract terms, using the processing shown in Figure 10, etc. The document management module 2045 may also present the evaluated creditworthiness of the user.

[0185] On the other hand, incentives for payment may be set to encourage payment. For example, the document management module 2045 may offer benefits such as access to services available in the super app described above, or access to them under favorable conditions, if payment is made in accordance with the contract terms. The document management module 2045 may also offer benefits for use in certain products or services as the user's creditworthiness is assessed.

[0186] In step S1124, the document management module 2045 of the server 20 records the results of the restriction measures and creditworthiness reassessment in the system log, generates update information and notification content, and sends them to the terminal 10.

[0187] In step S1111, terminal 10 receives notification information and update content sent from server 20, displays the latest restriction status and credit score on the screen, and provides feedback to the user.

[0188] <4 Screen Examples> Figure 12 is an example of an operation screen that displays details such as contract contents, payment obligations, and payment terms to the user, and shows the execution status when the system automatically charges.

[0189] Operation screen 1200 is an operation screen that displays details such as contract contents, payment obligations, and payment terms to the user.

[0190] The operation screen 1200 corresponds to each process in Figure 11. The operation screen 1200 displays the execution status when the system automatically charges. It is also an operation screen that displays service usage restrictions (such as reduced communication speed and restrictions on the use of payment apps) and penalties that apply when payment is not made, as well as the credit score.

[0191] The contract details display area 1202 is an area that displays an overall overview of contract information, including contract terms, payment obligations, payment conditions, and contract status, all in one place.

[0192] The automatic billing execution status display area 1204 is an area that displays the status of the automatic billing execution result, such as success, failure, or processing, in real time.

[0193] The service usage restriction display area 1206 is an area that displays examples of restrictions that apply when payment is not made, such as reduced communication speed and restrictions on some functions of the payment application.

[0194] The penalty details and credit score display area 1208 is an area that displays the details of the applied penalty and the recalculated user credit score in numerical and graphical format.

[0195] The consent confirmation operation unit 1210 is a button that the user presses to agree to the presented contract details and payment terms and to confirm the conclusion of the contract, and is an operating component that accepts the operation.

[0196] The screen update operation unit 1212 is an operation button for reacquiring the latest information such as the automatic billing execution status, service usage restrictions, and credit score, and reflecting it on the screen; it is an operation component that accepts operations.

[0197] The penalty details specification section 1214 is a menu-style item for switching and selecting detailed displays, such as the breakdown and priority of applied penalties, and is an operating component that accepts specifications.

[0198] The restriction removal request designation unit 1216 is a selection item for the user to indicate their intention to remove currently applied service usage restrictions, and is an operating member that accepts the designation.

[0199] The feedback input screen 1218 is an input area and operation screen for users to enter inquiries, opinions, or objections in free text format.

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

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

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

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

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

[0205] Furthermore, by storing data, various programs, and various databases in the memory unit, the information processing device and information processing system related to this disclosure can be considered to have been manufactured.

[0206] Furthermore, the databases and masters in this disclosure may include any data structures (lists, dictionaries, associative arrays, objects, etc.) in which information is structurally defined. Data structures also include data that can be considered as data structures by combining data with functions, classes, methods, etc., written in any programming language.

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

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

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

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

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

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

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

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

[0215] (Note 1) A program for operating a computer having one or more computer processors, wherein the memory unit is configured to store contract data, which is a concluded contract document specifying the terms and conditions of the contract, approved by the parties to the contract, and the program causes one or more computer processors to perform the steps of: detecting that there is a payment obligation in the terms and conditions of the contract specified in the contract data; and, if there is a payment obligation in the contract data, charging the parties to the contract in accordance with that obligation without requiring a payment operation.

[0216] (Note 2) The program described in Appendix 1 stores contract data in a memory unit through a service for managing contract data, and performs billing in the billing step through a function that processes payment related to the management of contract data, provided by the service for managing contract data.

[0217] (Note 3) The program is one of the programs described in either Appendix 1 or 2, which causes one or more computer processors to perform the step of obtaining information that identifies the users of the parties to a contract in a payment application used by the parties to the contract relating to the contract data, and in the step of charging, charges the users of the parties relating to the contract through the payment application based on the information obtained in the step of obtaining information about the users of the parties relating to the contract.

[0218] (Note 4) The program is one of the programs described in any of Appendix 1 to 3, which causes one or more computer processors to perform a step of obtaining bank account or credit card information used by the parties to a contract relating to contract data, and in a billing step, bills through the bank account or credit card of the party's user based on the information obtained in the step of obtaining information about the party's user relating to the contract.

[0219] (Note 5) A program as described in any of Annexes 1 to 4, wherein, in the billing step, if the party obligated to make payments under the contract pays for the purchase of a product or service, the ownership of the product or the right to use the service relating to such payment shall belong to the party entitled to receive the payment under the contract.

[0220] (Note 6) A program as described in any of the appendices 1 to 3, which, in the billing step, bills when there is a contractual obligation to pay, without requiring a payment operation from the paying party's user, but bills when there is no contractual obligation to pay, requires the paying party's user to perform a payment operation.

[0221] (Note 7) The program described in Appendix 6, in the billing step, billing occurs in the case of a contract between individuals where there is an obligation to pay under that contract, even without the user of the paying party performing a payment operation; however, if there is no obligation to pay under the contract, billing occurs when the user of the paying party performs a payment operation; and in the case of a contract in which a corporation is included as a party, billing does not occur unless the user of the paying party performs a payment operation, and billing occurs when the user performs a payment operation.

[0222] (Note 8) The program is one of the programs described in any of Appendix 1 to 6, which causes one or more computer processors to perform a step that restricts the use of a specified product or service by the user of a party obligated to pay if the contract data has a payment obligation and charges the party to the contract but payment is not made.

[0223] (Note 9) The program described in Appendix 8 restricts the use of services other than the service used to conclude contracts relating to contract data, in the step of restricting.

[0224] (Note 10) In the step of restricting, the program described in Appendix 9 restricts the use of other services, specifically restricting the use of communication services used by users who have payment obligations under the contract.

[0225] (Note 11) In the step of restricting, a program described in any of the appendices 9 to 10 that restricts the use of other services, specifically by restricting the use of services that are linked to payment applications used by users who have a contractual obligation to pay.

[0226] (Note 12) The program is one of the programs described in any of Appendix 1 to 11, which causes one or more computer processors to perform the steps of: evaluating the creditworthiness of a user who has been charged in the billing step, based on the user's payment history in accordance with the billing; and presenting the creditworthiness of the user evaluated in the evaluation step.

[0227] (Note 13) The program described in Appendix 12, which causes one or more computer processors to perform a step of granting users benefits for using a given product or service, with the higher the user's assessed creditworthiness.

[0228] (Note 14) A method performed by a computer having one or more computer processors, wherein a memory unit is configured to store contract data, which is a concluded contract document specifying the terms and conditions of the contract, approved by the parties to the contract, the method comprising: one or more computer processors detecting that there is a payment obligation in the terms and conditions specified in the contract data; and, if there is a payment obligation in the contract data, charging the parties to the contract in accordance with the obligation without performing a payment operation.

[0229] (Note 15) Information processing device, wherein the storage 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, and the control unit of the information processing device performs the steps of: detecting that there is a payment obligation in the terms and conditions specified in the contract data; and, if there is a payment obligation in the contract data, charging the parties to the contract in accordance with the obligation without requiring a payment operation.

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. A step of detecting that there is a payment obligation under the contract terms defined in the aforementioned contract data, A program that, if there is a payment obligation in the aforementioned contract data, causes the contracting party to perform the step of charging the party to the contract without requiring a payment operation, in accordance with that obligation.

2. The service for managing the contract data stores the contract data in the storage unit. The program according to claim 1, wherein in the step of charging, the charging is performed through a function that processes payment related to the management of contract data, provided in the service for managing the contract data.

3. The program further provides the following to one or more computer processors: The procedure involves performing the step of obtaining information that identifies the user of the contracting party in the payment application used by the contracting party relating to the aforementioned contract data. The program according to claim 1, which, in the step of charging, performs the charging through the payment application based on the information obtained in the step of obtaining information about the user of the party to the contract.

4. The program further provides the following to one or more computer processors: The procedure involves obtaining information on bank accounts or credit cards used by the parties to the contract relating to the aforementioned contract data. The program according to claim 1, wherein in the billing step, the billing is performed through the bank account or credit card of the user of the party to the contract, based on the information obtained in the acquisition step regarding the user of the party to the contract.

5. The program according to claim 1, wherein, in the step of charging, if a party obligated to make a payment under the contract makes a payment for the purchase of a product or service, the ownership of the product or the right to use the service relating to such payment belongs to the party entitled to receive payment under the contract.

6. The program according to claim 1, wherein in the step of charging, if there is a payment obligation under the contract, charging is performed without the user of the paying party performing a payment operation, whereas if there is no payment obligation under the contract, charging is performed when the user of the paying party performs a payment operation.

7. In the aforementioned billing step, if the contract is between individuals and there is an obligation to pay under that contract, billing will occur without the user of the paying party performing a payment operation. However, if there is no obligation to pay under the contract, billing will occur when the user of the paying party performs a payment operation. The program according to claim 6, which, in the case of a contract in which a legal entity is a party, does not charge unless the user of the paying party performs a payment operation, and charges when the user performs a payment operation.

8. The program further provides the following to one or more computer processors: The program according to claim 1, which, if the contract data indicates that there is a payment obligation and the process of charging the parties to the contract is performed but payment is not made, causes the program to perform a step of restricting the use of a specified product or service by the user of the party obligated to make the payment.

9. The program according to claim 8, wherein in the step of restricting, the use of a service other than the service that concludes a contract relating to the contract data is restricted.

10. The program according to claim 9, wherein in the step of restricting, the use of the other services is restricted, thereby restricting the use of a communication service used by a user who has a contractual obligation to pay.

11. The program according to claim 9, wherein in the step of restricting, by restricting the use of the other services, the program restricts the use of a service that is linked to a payment application used by a user who has a payment obligation under the contract.

12. The program further provides the following to one or more computer processors: A step to evaluate the creditworthiness of a user who has been charged in the aforementioned charging step, based on their payment history in accordance with the charges, The program according to claim 1, which performs the steps of: presenting the user's creditworthiness as evaluated in the aforementioned evaluation step;

13. The program further provides the following to one or more computer processors: The program according to claim 12, which performs a step of granting a benefit for using a predetermined product or service the higher the creditworthiness of the user as assessed.

14. 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, A step of detecting that there is a payment obligation under the contract terms defined in the aforementioned contract data, A method for performing the following steps: if there is a payment obligation in the contract data, charge the party to the contract in accordance with that obligation without performing a payment operation.

15. 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, A step of detecting that there is a payment obligation under the contract terms defined in the aforementioned contract data, An information processing device that, if there is a payment obligation in the contract data, performs the step of charging the parties to the contract in accordance with that obligation without performing a payment operation.

Images