Debt management device, debt management method, and program

Abstract

Until now, there has been no platform that can manage the status of a claim in two or more phases from the time the claim is generated until the creditor and debtor agree on the claim settlement, and to expedite the settlement of the claim. [Solution] The above problem can be solved by a claim management device 1 which comprises a claim acquisition unit 121 which acquires claim information for a claim, a claim storage unit 131 which stores the claim information, a claim notification unit 141 which sends claim notification information to the debtor, a confirmation receiving unit 122 which receives confirmation information for the claim from the debtor, a confirmation storage unit 133 which stores the confirmation information in association with a claim identifier, a negotiation receiving unit 123 which receives negotiation information, a negotiation storage unit 134 which stores the negotiation information, an instruction receiving unit 124 which receives instructions to output claim status information, and an information sending unit 147 which sends claim status information in response to the output instruction.

Description

[Technical Field]

[0001] The present invention relates to a credit management device for facilitating the processing of credits. [Background technology]

[0002] Conventionally, there have been systems that allow card issuers or other electronic payment providers to obtain quick, desirable, and efficient resolution of customer disputes with merchants (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2015-535365 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the prior art, there was no platform that could manage the status of a claim in two or more phases from the time the claim is generated until the creditor and debtor agree on the claim settlement, and promote the settlement of the claim. [Means for solving the problem]

[0005] The claims management device of the first invention comprises a claims management unit that stores one or more pieces of claim status information that is information related to claim processing, and that is information that corresponds to a claim identifier that identifies a claim, and that can identify the current phase out of two or more phases from the occurrence of a claim until the creditor and debtor agree on claim processing; a claim acquisition unit that acquires claim information that has a creditor identifier that identifies a creditor, a debtor identifier that identifies a debtor, and claim content information related to the content of the claim; a claim storage unit that stores the claim information acquired by the claim acquisition unit in the claims management unit in association with the claim identifier; a claim notification unit that, in response to the acquisition of the claim information by the claim acquisition unit, acquires notification information that includes information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and transmits the notification information to the debtor; and a claim notification unit that receives confirmation information related to confirmation of the claim from the debtor terminal of the debtor. a confirmation receiving unit that receives the confirmation information, a confirmation storage unit that acquires the confirmation information to be stored in response to the confirmation receiving unit receiving the confirmation information, and stores the confirmation information in the claim management unit in association with a claim identifier; a negotiation receiving unit that receives negotiation information for extinguishing a claim from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation storage unit that stores the negotiation information received by the negotiation receiving unit in the claim management unit in association with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and a claim identifier; an instruction receiving unit that receives an instruction to output claim status information from the creditor terminal or debtor terminal; an information acquisition unit that acquires part or all of the claim status information corresponding to the output instruction from the claim management unit; and an information sending unit that sends part or all of the claim status information acquired by the information acquisition unit to the creditor terminal or debtor terminal.

[0006] This configuration makes it possible to provide a platform for managing the status of a claim in two or more phases from the time the claim is generated until the creditor and debtor agree on the processing of the claim, and for facilitating the processing of the claim.

[0007] In addition, the receivables management device of the second invention is a receivables management device that, compared to the first invention, further comprises a proposal content acquisition unit that acquires creditor information and debtor information from the receivables management unit when the negotiation information received by the negotiation receiving unit matches the proposal content creation conditions, and acquires proposal content, which is information including creditor information and debtor information, information including the content of the negotiation information, and information indicating a proposal regarding the processing of receivables, and a proposal content transmission unit that transmits the proposal content acquired by the proposal content acquisition unit to the creditor terminal or the debtor terminal.

[0008] With this configuration, it is possible to automatically create proposals regarding debt processing in accordance with the negotiation information.

[0009] In addition, the debt management device of the third invention is a debt management device in which, compared to the second invention, the proposal content sending unit sends the proposal content so that the negotiation information received by the negotiation receiving unit corresponds to the proposal content acquired by the proposal content acquisition unit.

[0010] With this configuration, negotiation information and proposal contents can be presented appropriately.

[0011] In addition, the receivables management device of the fourth invention, compared to the second or third invention, further includes a screen sending unit that sends screen information to the debtor terminal to allow the debtor to select one of two or more methods of receivables processing after the confirmation receiving unit receives the confirmation information, the negotiation receiving unit receives negotiation information from the debtor terminal including a receivables processing identifier that identifies one of the two or more methods of receivables processing, and the proposal content acquisition unit acquires creditor information and debtor information from the receivables management unit, and acquires proposal content that includes creditor information and debtor information and corresponds to the receivables processing identifier.

[0012] With this configuration, it is possible to automatically compose proposal content relating to debt settlement in accordance with negotiation information, and proposal content including a debt settlement identifier selected by the debtor.

[0013] In addition, the debt management device of the fifth invention is a debt management device that, compared to the fourth invention, further includes a mediation support unit that performs mediation support processing to support a group including a creditor and a debtor in conducting online mediation when the negotiation receiving unit receives negotiation information including a debt processing identifier indicating online mediation from a debtor terminal.

[0014] This configuration can support online arbitration of claims.

[0015] In addition, the debt management device of the sixth invention is a debt management device that, compared to any one of the first to fifth inventions, further comprises a judgment unit that judges whether the agreement conditions have been met using the negotiation information received by the negotiation receiving unit, and a necessary information sending unit that sends to the debtor necessary information, which is information necessary for the debtor to process the debt, when the judgment unit judges that the agreement conditions have been met.

[0016] With this configuration, when negotiations for debt settlement are concluded, the information necessary for debt settlement can be presented to the debtor.

[0017] In addition, the debt management device of the seventh invention is a debt management device that, compared to any one of the first to sixth inventions, further comprises a negotiation information output unit that outputs two or more pieces of negotiation information received by the negotiation receiving unit in the order in which they were received by the negotiation receiving unit and in a manner that makes it possible to understand whether the identifier to which the negotiation information corresponds is a creditor identifier or a debtor identifier.

[0018] This configuration makes it possible to provide a platform that manages the status of a claim in two or more phases from the time the claim is generated until the creditor and debtor agree on the processing of the claim, and promotes the processing of the claim.

[0019] In addition, the debt management device of the eighth invention is a debt management device that, compared to any one of the first to seventh inventions, further comprises an agreement document generation unit that generates an agreement document using the negotiation information when the negotiation information received by the negotiation receiving unit satisfies the agreement conditions, and an agreement document output unit that outputs the agreement document generated by the agreement document generation unit.

[0020] With this configuration, when an agreement is reached in negotiations regarding debt settlement, an agreement document can be automatically generated.

[0021] In addition, the debt management device of the ninth invention is a debt management device in which, compared to any one of the first to eighth inventions, the debt status information has phase-specific information that can identify the current phase out of two or more phases from the occurrence of the debt to the time the creditor and debtor agree on the processing of the debt, and further includes an update unit that updates the phase-specific information corresponding to the debt identifier in response to the application notification unit sending notification information to the debtor and in response to the confirmation receiving unit receiving confirmation information.

[0022] This configuration makes it possible to provide a platform for managing the status of a claim in two or more phases from the time the claim is generated until the creditor and debtor agree on the processing of the claim, and for facilitating the processing of the claim. [Effects of the Invention]

[0023] The debt management device of the present invention can provide a platform for managing the status of a debt in two or more phases from the time the debt is generated until the creditor and debtor agree on the debt processing, and for facilitating the processing of the debt. [Brief explanation of the drawings]

[0024] [Figure 1] Conceptual diagram of information system A in embodiment 1 [Figure 2] Block diagram of Information System A [Figure 3] Block diagram of the credit management device 1 [Figure 4] A flowchart illustrating an example of the operation of the claim management device 1. [Figure 5] A flowchart illustrating an example of the operation of the claim management device 1. [Figure 6] A flowchart illustrating an example of the process of configuring the notification information [Figure 7] A flowchart illustrating an example of the proposal content configuration process. [Figure 8] A flowchart illustrating an example of the agreement document generation process [Figure 9] Flowchart illustrating an example of the output information configuration process [Figure 10] A flowchart illustrating an example of the operation of the creditor terminal 2 [Figure 11] A flowchart illustrating an example of the operation of the debtor terminal 3 [Figure 12] A diagram showing an example of the flow of phases after filing a claim [Figure 13] A diagram showing an example of the creditor management table [Figure 14] Figure showing an example of the same credit management table [Figure 15] A diagram showing an example of the proposal template [Figure 16] A diagram showing an example of the agreement document template [Figure 17] An example of the case registration screen [Figure 18] FIG. 10 is a diagram showing an example of the notification information. [Figure 19] FIG. 10 is a diagram showing an example of the confirmation screen. [Figure 20] FIG. 10 is a diagram showing an example of the decision screen. [Figure 21] FIG. 10 is a diagram showing an example of the notification information. [Figure 22] FIG. 10 shows an example of the output screen. [Figure 23] FIG. 10 shows an example of the installment amount change screen. [Figure 24] FIG. 10 shows an example of the output screen. [Figure 25] FIG. 10 shows an example of the output screen. [Figure 26] Figure showing an example of payment schedule output [Figure 27] FIG. 10 shows an example of the output screen. [Figure 28] FIG. 10 shows an example of the output screen. [Figure 29] Block diagram of the computer system DETAILED DESCRIPTION OF THE INVENTION

[0025] Hereinafter, embodiments of a debt management device and the like will be described with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore repeated description may be omitted.

[0026] (Embodiment 1) In this embodiment, a description will be given of a bond management device that stores bond status information in pairs with a unique bond identifier.

[0027] In this embodiment, a description will be given of a credit management device that uses application information sent by a creditor to construct notification information to be notified to a debtor, and sends the notification information to the debtor's contact address.

[0028] In this embodiment, we will describe a debt management device that accepts access from a debtor based on notification information, receives confirmation information regarding the debtor's claim application, stores the confirmation information, and then stores negotiation information between the creditor and the debtor in correspondence with a debt identifier.

[0029] In this embodiment, a description will be given of a credit management device that acquires proposal contents based on negotiation information from a creditor or debtor, associates the proposal contents with the negotiation information, and stores the proposal contents.

[0030] In this embodiment, a description will be given of a credit management device that outputs a screen with two or more options during the negotiation process between a creditor and a debtor.

[0031] In this embodiment, a description will be given of a debt management device that performs processing to support online mediation when both the creditor and the debtor agree.

[0032] In this embodiment, a description will be given of a claim management device that determines whether or not the agreed conditions are met, and if the agreed conditions are met, transmits information necessary for claim processing to the debtor.

[0033] In this embodiment, a credit management device will be described that outputs negotiation information in a time series that shows the process of negotiations between a creditor and a debtor, and that allows one to understand which of the creditor and the debtor input the negotiation information.

[0034] In this embodiment, a description will be given of a debt management device that uses debt status information to generate and output an agreement document.

[0035] In this specification, information X being associated with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not important. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, or information Y may be included in information X, etc.

[0036] Furthermore, in this specification, selecting or determining information Z means obtaining information Z, obtaining a pointer to information Z, obtaining the ID of information Z, setting a flag on information Z, etc., and it is sufficient if information Z can be accessed.

[0037] 1 is a conceptual diagram of an information system A according to this embodiment. The information system A comprises a claim management device 1, one or more creditor terminals 2, and one or more debtor terminals 3.

[0038] The claim management device 1 is a server for managing information about claims. The claim management device 1 may manage information about two or more claims, including a claim for which one user is the creditor and a claim for which the same user is the debtor. The claim management device 1 may be, for example, a cloud server or an ASP server, but the type is not important.

[0039] The creditor terminal 2 is a terminal used by the creditor. The debtor terminal 3 is a terminal used by the debtor. The creditor terminal 2 and the debtor terminal 3 may be, for example, a personal computer, a smartphone, or a tablet terminal, but the type does not matter.

[0040] Fig. 2 is a block diagram of the information system A in this embodiment. Fig. 3 is a block diagram of the claim management device 1.

[0041] The claim management device 1 comprises a storage unit 11, a receiving unit 12, a processing unit 13, and a transmitting unit 14. The storage unit 11 comprises a claim management unit 111. Note that the storage unit 11 does not have to have the claim management unit 111. In other words, the claim management unit 111 may exist in an external device not shown.

[0042] The receiving unit 12 includes a request acquisition unit 121, a confirmation reception unit 122, a negotiation reception unit 123, and an instruction reception unit 124. The processing unit 13 includes a request storage unit 131, an update unit 132, a confirmation storage unit 133, a negotiation storage unit 134, a proposal content acquisition unit 135, a mediation support unit 136, a judgment unit 137, an agreement document generation unit 138, and an information acquisition unit 139. The transmitting unit 14 includes a request notification unit 141, a screen transmission unit 142, a proposal content transmission unit 143, a negotiation information output unit 144, a required information transmission unit 145, an agreement document output unit 146, and an information transmission unit 147.

[0043] The creditor terminal 2 comprises a creditor storage unit 21, a creditor reception unit 22, a creditor processing unit 23, a creditor transmission unit 24, a creditor reception unit 25, and a creditor output unit 26.

[0044] The debtor terminal 3 includes a debtor storage unit 31, a debtor reception unit 32, a debtor processing unit 33, a debtor transmission unit , a debtor reception unit 35, and a debtor output unit .

[0045] Various types of information are stored in the storage unit 11 that constitutes the claim management device 1. The various types of information include, for example, claim status information, various screen information, various conditions, various templates, and lawyer information, which will be described later.

[0046] Screen information is information for configuring a screen. Screen information is written in, for example, HTML or XML, but the implementation method is not important. Screen information, for example, corresponds to a selection object in other screen information. A selection object is an object that can be selected. A selection object is, for example, a button, a menu item, or a check box.

[0047] The various conditions include, for example, proposal content creation conditions and agreement conditions, which will be described later. The various conditions may be embedded in the program.

[0048] The various templates are, for example, a notification information template, a proposal content template, and an agreement document template. The notification information template is a template document for configuring notification information, which will be described later, and is a document that has variables. The proposal content template is a template document for configuring proposal content, and is a document that has variables. The agreement document template is a template document for configuring an agreement document, and is a document that has variables.

[0049] Lawyer information is information about lawyers who support online mediation. Lawyer information includes a lawyer identifier and lawyer contact information. Lawyer identifier is information that identifies a lawyer. Lawyer identifier is, for example, the lawyer's name, the lawyer's registration number, or the lawyer's ID. Lawyer contact information is information that indicates the lawyer's contact information. Lawyer contact information is, for example, the lawyer's email address, the lawyer's telephone number, or the ID for the lawyer to log in to the debt management device 1.

[0050] The claim management unit 111 stores one or more pieces of claim status information. The claim status information is information related to a claim. The claim status information identifies the current phase of one of two or more phases from the creation of a claim to settlement. The claim status information may also be information identifying the current phase of one of two or more phases from the filing of a claim to settlement. The agreement here is an agreement between a creditor and a debtor regarding the processing of a claim. A claim is a right that a creditor demands from a debtor to perform a certain action. The certain action here is typically the payment of money, but it can also be the delivery of goods or the provision of services, and the action demanded by a claim need not be limited. In other words, the type of claim handled here is preferably a monetary claim, but it can also be a material claim, an action claim, or other type of claim. A phase here refers to a specific state or period in the processing of a claim, from the creation of a claim to settlement or breakdown. A phase may also be referred to as a step, stage, or situation.

[0051] Claim status information can be said to be information related to claim processing. Claim status information can be said to be, for example, information for managing the status of claims. Claim status information is information that corresponds to a claim identifier. A claim identifier is information that identifies a claim. A claim identifier is, for example, a claim ID or a claim name (for example, the name of the application). Claim status information includes, for example, creditor information, debtor information, claim content information, confirmation information, negotiation information, proposal content, agreement document, phase-specific information, and various time information.

[0052] Creditor information is information about a creditor. Creditor information includes, for example, a creditor identifier and one or more creditor attribute values. The creditor identifier is information that identifies a creditor. The creditor identifier includes, for example, the creditor's ID, the creditor's name, the creditor's telephone number, the creditor's email address, and the creditor's terminal 2 IP address. Creditor attribute values ​​include, for example, the creditor's remittance destination information, the creditor's company name, the name of the creditor's company representative, and the creditor type, which indicates whether the creditor is a corporation or an individual. Remittance destination information is information used by a debtor to remit funds to a creditor. Remittance destination information includes, for example, bank account information, credit card information, and online payment information. Bank account information is information about a bank account required for bank transfers, including, for example, the bank name, branch name, and bank account number. Credit card information is information required for remittances using a credit card, including, for example, the credit card number and expiration date. Online payment information is information required for remittances using online payments, including, for example, an ID for online payments. Bank account information may also be referred to as account information, where appropriate.

[0053] Debtor information is information about a debtor. Debtor information includes, for example, a debtor identifier and one or more debtor attribute values. A debtor identifier is information that identifies a debtor. Debtor identifiers include, for example, the debtor's ID, the debtor's name, the debtor's telephone number, the debtor's email address, and the IP address of the debtor terminal 3. Debtor attribute values ​​include, for example, the debtor's contact information, the debtor's company name, the name of the debtor's company representative, the debtor's address, and the debtor type, which indicates whether the debtor is a corporation or an individual. Contact information includes, for example, an email address, a telephone number, and an SNS (e.g., Line (registered trademark), Slack (registered trademark)) ID.

[0054] The claim content information is information that specifies the content of the claim. For example, the claim content information includes the name of the claim, the claimed amount, and the original payment due date. If the claim is a right to request the return of a loaned item, the claim content information is, for example, information about the item to be returned and information that specifies the return destination.

[0055] Confirmation information is information that indicates that the debtor has confirmed the creditor's claim. Debtor confirmation means that the debtor acknowledges that the claim is their case. Confirmation information is, for example, a flag, but may also be replaced by the debt status information containing information that should be stored after the confirmation phase (for example, negotiation information). Confirmation information is, for example, confirmation time information. Confirmation time information is information that identifies when the debtor confirmed the claim. Confirmation time information is, for example, the date and time when the information was received from the debtor terminal 3. The time information that identifies the time may be the date, or the date and time, etc. The granularity of the time information is not important. Confirmation information may be information that allows one to understand that the debtor has confirmed the claim.

[0056] Negotiation information is information regarding negotiations between a creditor and a debtor regarding the processing of a debt. Negotiation information can be said to be information that specifies the content of negotiations between a creditor and a debtor regarding the processing of a debt. Information that specifies the content of negotiations is the negotiation content. Negotiation information may include an inputter identifier. The inputter identifier is information that identifies the person who proposed the negotiation content. The inputter identifier is, for example, information that indicates the creditor or information that indicates the debtor.

[0057] The negotiations here are negotiations to settle the debt. Negotiations are negotiations between the creditor and debtor regarding the settlement of the debt. Negotiation information includes, for example, a debt settlement identifier. The debt settlement identifier is information that identifies the method for settling the debt. The debt settlement identifier is, for example, an ID, the name of the debt settlement (for example, "pay by credit card now," "pay in full at the end of the following month," "pay in installments at the end of each month," "proposed adjustment of the amount," "I don't remember making the claim," "already paid directly," "request online mediation"). The debt settlement identifier includes, for example, a payment method identifier (for example, "credit card," "bank transfer," etc.), which is information that identifies the means of payment.

[0058] The proposal content is a document that describes the matters agreed upon by both parties when processing the debt identified by the debt processing identifier. The proposal content can be said to be information that indicates a proposal for processing the debt. The proposal content is information that includes creditor information (e.g., the creditor's name) and debtor information (e.g., the debtor's name), as well as the content of the negotiation information (e.g., the amount of each month's installment payment).

[0059] An agreement document is a document prepared when an agreement is reached in negotiations regarding the settlement of a debt, and it contains the details of the negotiations. The agreement document may include, for example, information about the creditor (e.g., the creditor's name), information about the debtor (e.g., the debtor's name), the method by which the debtor will pay the creditor, and the amount to be paid. Note that the agreement document may be the same as the final proposal in the negotiations.

[0060] Phase-specific information is information that can identify the current phase among two or more phases from the creation of a claim until the creditor and debtor agree on the claim's disposal. The phases that can be identified by phase-specific information do not have to be all of the two or more phases from the creation of a claim until the creditor and debtor agree on the claim's disposal. Phase-specific information is, for example, a phase identifier, but it does not have to be explicitly present in the claim status information. Phase-specific information may be any information that allows the phase to be determined from the claim status information. Phase-specific information may be information that can be determined from information contained in the claim status information or information that is not contained in the claim status information. For example, if the claim status information includes a filing time and a confirmation time but does not include negotiation information, the current phase can be determined to be the "negotiation" phase. In such a case, the phase-specific information is a phase identifier determined from the filing time and the confirmation time, or the filing time, the confirmation time, and non-existent negotiation information.

[0061] The two or more phases from the occurrence of a claim until the creditor and debtor agree on how to handle it are, for example, "filed," "awaiting confirmation," "confirmed," "negotiating," and "agreed." The "filed" phase is the phase in which the creditor files a claim with the debtor. The "awaiting confirmation" phase is the phase in which the creditor is waiting for the debtor to confirm the claim. Note that the "awaiting confirmation" phase may be the same as the "filed" phase. The "confirmed" phase is the phase in which the debtor confirms the claimed claim. The "negotiating" phase is the phase in which the creditor and debtor are negotiating how to handle the claim. The "agreed" phase is the phase in which an agreement is reached in negotiations for the handling of the claim. Note that the two or more phases from the occurrence of a claim until the creditor and debtor agree on how to handle it do not have to include the "claim occurrence" phase and the "agreement" phase.

[0062] The phases handled by the debt management device 1 may include phases after an agreement has been reached in negotiations. Such phases are, for example, "debt processing in progress" and "debt processing completed." The "debt processing in progress" phase is the phase after an agreement has been reached in negotiations and when the debt is being processed (for example, payment is being made). The "debt processing completed" phase is the phase when debt processing is completed. The phases handled by the debt management device 1 are preferably "filed," "waiting for confirmation," "confirmed," "negotiating," "agreed upon," "debt processing in progress," and "debt processing completed," but may also be some of the phases within a set of these phases. Furthermore, the phases handled by the debt management device 1 do not have to be all phases from the occurrence of a debt to the time when the creditor and debtor agree on the processing of the debt.

[0063] Further, the various types of time information are, for example, filing time information, confirmation time information, negotiation time information, agreement time information, and claim processing completion time information. Filing time information is information indicating when a claim was filed. Filing time information is, for example, information indicating when the claim acquisition unit 121 received the claim information. Negotiation time information is information indicating the time of negotiation. Negotiation time information is, for example, information indicating when the negotiation receiving unit 123 received the negotiation information. Agreement time information is information indicating when an agreement was reached. Agreement time information is, for example, information indicating when the judgment unit 137 determined that the agreement conditions described below have been met. Claim processing completion time information is information indicating when the processing of the claim is completed.

[0064] The receiving unit 12 receives various information and instructions from the creditor terminal 2 or the debtor terminal 3. The various information and instructions are, for example, case registration (described later), application information (described later), confirmation information, negotiation information, output instructions (described later), proposal content instructions (described later), agreement document instructions (described later), payment schedule instructions (described later), or payment information.

[0065] The payment information is information that identifies that a payment has been made by a debtor. The payment information is associated with a bond identifier. The payment information includes, for example, the payment amount.

[0066] The application acquisition unit 121 acquires application information. For example, the application acquisition unit 121 receives application information from the creditor terminal 2. For example, the application acquisition unit 121 receives a case registration having application information from the creditor terminal 2. The application acquisition unit 121 may read out application information from the storage unit 11 or an external device not shown. The method by which the application acquisition unit 121 acquires application information is not important.

[0067] Claim information is information about the claim being filed. Claim information may also be considered to include information about claims that may be filed in the future, and claim information is broadly understood. Claim information has a creditor identifier that identifies the creditor, a debtor identifier that identifies the debtor, and claim content information. Claim information may include creditor information having a creditor identifier and debtor information having a debtor identifier. Case registration is an instruction to register a case that is the subject of a claim being filed.

[0068] The claim acquisition unit 121 may, for example, acquire claim time information from a clock not shown, and construct claim information that includes the claim time information and the received claim information and is information to be accumulated.

[0069] The confirmation receiving unit 122 receives confirmation information regarding the confirmation of a claim from the debtor terminal 3 of the debtor. The confirmation receiving unit 122 typically receives the confirmation information from the debtor terminal 3 in response to notification information, described below, being sent to the debtor. The confirmation information is typically information indicating that the debtor has acknowledged the existence of a claim. The confirmation information received by the confirmation receiving unit 122 is typically associated with a claim identifier. The confirmation information received by the confirmation receiving unit 122 is typically associated with a claim identifier. The confirmation information received by the confirmation receiving unit 122 is, for example, a flag indicating that the claim has been confirmed, or a debtor identifier.

[0070] The confirmation receiving unit 122 may also receive non-existence information, which is information indicating the debtor's assertion that the claim does not exist.

[0071] After the confirmation receiving unit 122 receives the confirmation information, the negotiation receiving unit 123 receives negotiation information from the creditor terminal 2 of the creditor and the debtor terminal 3 of the debtor. The negotiation receiving unit 123 usually receives negotiation information alternately from the creditor terminal 2 and the debtor terminal 3. Negotiation is usually negotiation for the extinguishment of a claim. Note that the extinguishment of a claim can also be called the processing of a claim. The negotiation information received by the negotiation receiving unit 123 is usually associated with a claim identifier. The negotiation information received by the negotiation receiving unit 123 is usually associated with the creditor identifier of the creditor who sent the negotiation information or the debtor identifier of the debtor who sent the negotiation information.

[0072] The negotiation receiving unit 123 receives, for example, negotiation information including a debt settlement identifier that identifies one of two or more debt settlement methods from the debtor terminal 3. The negotiation receiving unit 123 receives, for example, negotiation information from the creditor terminal 2 or the debtor terminal 3, which is a creditor's proposal that includes the start month of installment payments for debt settlement and the payment amount for each month.

[0073] The negotiation receiving unit 123 receives, for example, negotiation information including a proposal for modifying the payment amount from the creditor terminal 2 or the debtor terminal 3.

[0074] The negotiation receiving unit 123 receives negotiation information from the debtor terminal 3, including, for example, "information to the effect that the debtor has no recollection of making the claim" and "information to the effect that the debtor has already made the payment directly."

[0075] The negotiation receiving unit 123 receives, for example, negotiation information including "information indicating a desire for online mediation" from the creditor terminal 2 or the debtor terminal 3.

[0076] The instruction receiving unit 124 receives various instructions from the creditor terminal 2 or the debtor terminal 3. The various instructions are, for example, an output instruction, a proposal content instruction, an agreement document instruction, or a payment schedule instruction.

[0077] An output instruction is an instruction to output the debt status information of the debt management unit 111. The output instruction corresponds to a debt identifier. The output instruction has, for example, a debt identifier. The instruction to output the debt status information may be considered to include an instruction to output part of the debt status information.

[0078] The proposal content instruction is an instruction to output the proposal content. The agreement document instruction is an instruction to output the agreement document. The payment schedule instruction is an instruction to output the payment schedule.

[0079] The processing unit 13 performs various types of processing, such as processing performed by a request storage unit 131, an update unit 132, a confirmation storage unit 133, a negotiation storage unit 134, a proposal content acquisition unit 135, a mediation support unit 136, a judgment unit 137, an agreement document generation unit 138, and an information acquisition unit 139.

[0080] The processing unit 13 stores the received payment information in the bond management unit 111 in association with the bond identifier.

[0081] The processing unit 13 acquires information according to the received instructions. The processing unit 13 acquires proposal content according to the received proposal content instruction from the receivables management unit 111. The processing unit 13 acquires an agreement document according to the received agreement document instruction from the receivables management unit 111. The processing unit 13 acquires a payment schedule according to the received payment schedule instruction from the receivables management unit 111.

[0082] The claim accumulation unit 131 accumulates the claim information acquired by the claim acquisition unit 121 in association with the claim identifier in the claim management unit 111. The accumulated claim information constitutes the claim status information of the claim management unit 111.

[0083] For example, when the information acquisition unit 139 receives application information from the creditor terminal 2, the application accumulation unit 131 generates a unique claim identifier and stores the application information in the claim management unit 111 in association with the claim identifier. Note that any method for generating a unique claim identifier is acceptable. For example, the application accumulation unit 131 acquires a unique number obtained by adding 1 to the most recently generated claim identifier.

[0084] The update unit 132 updates the phase identification information associated with the claim identifier in response to the claim notification unit 141 sending the notification information to the debtor. The update unit 132 typically stores information indicating that the current phase is the "waiting for confirmation" phase in the claim management unit 111. The update unit 132 may store the notification information in the claim management unit 111 in association with the claim identifier, or may store a flag indicating that the notification information has been sent in association with the claim identifier in the claim management unit 111. The update unit 132 may simply perform processing to identify that the phase has progressed as a result of the notification information being sent. This processing may be replaced by processing in which the claim storage unit 131 stores the claim information. The update unit 132 updates the phase identification information to, for example, phase identification information indicating that the current phase is the "waiting for confirmation" phase.

[0085] The update unit 132 updates the phase identification information associated with the bond identifier in response to the confirmation receiving unit 122 receiving the confirmation information. Here, the update unit 132 accumulates, for example, information indicating that the current phase is the "under negotiation" phase in the bond management unit 111. The update unit 132 may accumulate the confirmation information in the bond management unit 111 in association with the bond identifier, or may accumulate a flag indicating that the confirmation information has been received in association with the bond identifier in the bond management unit 111. The update unit 132 may simply perform processing to identify that the phase has progressed upon receipt of the confirmation information. This processing may be replaced by processing in which the confirmation accumulation unit 133 accumulates the confirmation information. The update unit 132 updates the phase identification information to, for example, phase identification information indicating that the current phase is the "under negotiation" phase.

[0086] In response to the confirmation receiving unit 122 receiving the confirmation information, the confirmation accumulation unit 133 acquires the confirmation information to be accumulated, associates the confirmation information with the claim identifier, and accumulates it in the claim management unit 111. The confirmation accumulation unit 133 acquires confirmation time information, which is time information, from a clock (not shown), for example, and accumulates confirmation information including the confirmation time information in the claim management unit 111, associates it with the claim identifier. The accumulated confirmation information may be the confirmation time information. In other words, the received confirmation information and the accumulated confirmation information may be different information. The confirmation information may be information that enables determination that the debtor has confirmed the filing of the claim.

[0087] The negotiation storage unit 134 stores the negotiation information received by the negotiation receiving unit 123 in the claim management unit 111 by correlating it with a creditor identifier that identifies the creditor who sent the negotiation information or a debtor identifier that identifies the debtor who sent the negotiation information, and a claim identifier.

[0088] When the negotiation receiving unit 123 receives negotiation information, the negotiation accumulation unit 134 may acquire negotiation time information from a clock (not shown) and accumulate negotiation information including the negotiation time information.When the negotiation receiving unit 123 receives negotiation information, the negotiation accumulation unit 134 may acquire an inputter identifier that specifies whether the person who sent the negotiation information is a creditor or a debtor, and accumulate negotiation information including the inputter identifier.

[0089] The proposal content acquisition unit 135 acquires proposal content using the negotiation information when the negotiation information received by the negotiation receiving unit 123 matches the proposal content creation conditions. It is preferable that the proposal content acquisition unit 135 acquires proposal content using credit status information.

[0090] The proposal creation conditions are the conditions for creating the proposal. For example, a proposal creation condition is that the negotiation information includes a debt settlement identifier that indicates a specific method out of two or more debt settlement methods (a specific debt settlement identifier is selected). For example, a specific debt settlement identifier is the debt settlement identifier "Pay now by credit card," "Pay in full at the end of the following month," "Pay in installments at the end of each month," "Propose to adjust the amount," "I don't remember the bill," "Already paid directly," or "I would like online mediation," out of the debt settlement identifiers "Pay now by credit card," "Pay in full at the end of the following month," "Pay in installments at the end of each month," or "Propose to adjust the amount." For example, a proposal creation condition is that the negotiation information includes the installment amount. For example, a proposal creation condition is that the received negotiation information includes information that does not exist in negotiation information previously received.

[0091] The proposal content acquisition unit 135 acquires creditor information and debtor information from the debt management unit 111, and acquires proposal content, which is information that includes the creditor information and the debtor information and indicates a proposal corresponding to one method of debt processing.

[0092] The proposal content acquisition unit 135, for example, constructs the proposal content by substituting creditor information and debtor information into a proposal content template paired with one or more respective debt settlement identifiers. The proposal content acquisition unit 135, for example, constructs the proposal content by substituting creditor information (e.g., creditor name) and debtor information (e.g., debtor name) and some or all of the negotiation information (e.g., payment amount) into a proposal content template paired with one or more respective debt settlement identifiers.

[0093] The mediation support unit 136 performs mediation support processing when the negotiation receiving unit 123 receives, from the debtor terminal 3, negotiation information including a debt settlement identifier that identifies one method corresponding to online mediation.

[0094] The mediation support process is a process for supporting a group including creditors and debtors in conducting online mediation. It is preferable that the group includes lawyers. The mediation support process is, for example, a process for sending conference information for an online conference to each member of the group. The conference information includes, for example, a URL for starting the online conference. The conference information includes, for example, the start date and time of the online conference. The online conference is, for example, a conference using Zoom (registered trademark) or Webex (registered trademark).

[0095] The determination unit 137 uses the negotiation information received by the negotiation receiving unit 123 to determine whether the agreed conditions are met.

[0096] An agreed condition is a condition for determining whether negotiations regarding debt settlement have been concluded. For example, an agreed condition is that the received negotiation information includes a debt settlement identifier indicating a specific method out of two or more debt settlement methods (a specific debt settlement identifier has been selected). For example, a specific debt settlement identifier is "Pay now by credit card" or "Pay in full at the end of the following month" out of the debt settlement identifiers "Pay now by credit card," "Pay in full at the end of the following month," "Pay in installments at the end of each month," "Propose to adjust the amount," "I don't remember the bill," "Already paid directly," and "Request online mediation." For example, an agreed condition is that the received negotiation information includes a payment method identifier. For example, an agreed condition is that negotiation information indicating that the debtor has agreed to the negotiation information sent from the creditor has been received. For example, an agreed condition is that negotiation information indicating that the creditor has agreed to the negotiation information sent from the debtor has been received.

[0097] The agreement document generation unit 138 generates an agreement document using one or more pieces of negotiation information when the negotiation information received by the negotiation receiving unit 123 satisfies the agreement conditions. It is preferable that the agreement document generation unit 138 pairs the generated agreement document with a bond identifier and stores it in the bond management unit 111.

[0098] The agreement document generation unit 138, for example, substitutes the creditor information, the debtor information, and information included in one or more pieces of negotiation information into the agreement document template in the storage unit 11, and generates an agreement document.

[0099] The information acquisition unit 139 acquires part or all of the claim status information corresponding to the output instruction from the claim management unit 111. The information acquisition unit 139 acquires, for example, part or all of the claim status information paired with the claim identifier included in the output instruction from the claim management unit 111.

[0100] The transmitting unit 14 transmits various types of information, such as notification information, screen information, proposal details, negotiation information, necessary information, and an agreement document, which will be described later.

[0101] In response to the application acquisition unit 121 acquiring the application information, the application notification unit 141 acquires notification information including information on the creditor identified by the creditor identifier contained in the application information and the debt content information, and transmits the notification information to the debtor. The information may be transmitted in a push-type transmission or a pull-type transmission.

[0102] When a transmission condition for transmitting specific screen information is met, the screen transmitting unit 142 transmits the specific screen information to the creditor terminal 2 or the debtor terminal 3. For example, after the confirmation receiving unit 122 receives confirmation information, the screen transmitting unit 142 transmits screen information to the debtor terminal 3 to allow the debtor to select one of two or more methods of debt settlement. For example, when the screen transmitting unit 142 receives a selection of a selected object from the creditor terminal 2 or the debtor terminal 3, it transmits screen information corresponding to the selected object to the creditor terminal 2 or the debtor terminal 3.

[0103] The proposal content sending unit 143 sends the proposal content acquired by the proposal content acquisition unit 135 to the creditor terminal 2 or the debtor terminal 3. The proposal content sending unit 143 may send the same proposal content to the creditor terminal 2 and the debtor terminal 3. For example, in response to receiving a proposal content instruction, the proposal content sending unit 143 sends the proposal content corresponding to the instruction.

[0104] It is preferable that the proposal content sending unit 143 sends the proposal content so that the negotiation information received by the negotiation receiving unit 123 corresponds to the proposal content acquired by the proposal content acquiring unit 135. This is because the negotiation information that is the basis of the proposal content can be grasped.

[0105] The negotiation information output unit 144 outputs two or more pieces of negotiation information received by the negotiation receiving unit 123. For example, the negotiation information output unit 144 outputs the two or more pieces of negotiation information received by the negotiation receiving unit 123 in the order in which they were received by the negotiation receiving unit 123, and in a manner that makes it possible to determine whether the identifier to which the negotiation information corresponds is a creditor identifier or a debtor identifier. For example, the negotiation information output unit 144 outputs screen information in which the negotiation information corresponding to the creditor identifier is aligned to the right or left of the screen, and screen information in which the negotiation information corresponding to the debtor identifier is aligned to the left or right of the screen.

[0106] Here, output usually means transmission to the creditor terminal 2 or the debtor terminal 3. However, output may also be a concept that includes display on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and delivery of processing results to other processing devices or other programs other than the creditor terminal 2 or the debtor terminal 3.

[0107] When the determination unit 137 determines that the conditions for agreement have been met, the necessary information sending unit 145 sends the necessary information to the debtor, which is information the debtor needs to process the debt. The necessary information usually includes payee information. The payee information is, for example, account information, credit card information, and online payment information. The necessary information is, for example, information indicating the mailing address for the loaned goods and information indicating the location where the service is to be received.

[0108] The agreement document output unit 146 outputs the agreement document generated by the agreement document generation unit 138. The agreement document output unit 146 transmits the agreement document to the creditor terminal 2 and the debtor terminal 3. When an agreement document instruction is received, the agreement document output unit 146 preferably transmits the agreement document corresponding to the instruction.

[0109] The information transmitting unit 147 transmits the information acquired by the processing unit 13 to the creditor terminal 2 or the debtor terminal 3. The information transmitting unit 147 transmits, for example, part or all of the debt status information acquired by the information acquiring unit 139 to the creditor terminal 2 or the debtor terminal 3. The information transmitting unit 147 transmits part or all of the debt status information to the creditor terminal 2 or the debtor terminal 3 that has sent an output instruction. The information transmitting unit 147 transmits, for example, the proposal content, the agreement document, or the payment schedule to the creditor terminal 2 or the debtor terminal 3 that has sent a proposal content instruction, an agreement document instruction, or a payment schedule instruction.

[0110] Various types of information are stored in the creditor storage unit 21 that constitutes the creditor terminal 2. The various types of information include, for example, a creditor identifier.

[0111] The creditor reception unit 22 receives various types of information, instructions, etc. Examples of the various types of information, instructions, etc. include application information, negotiation information, output instructions, proposal content instructions, agreement document instructions, and payment schedule instructions.

[0112] The means for inputting various information and instructions may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0113] The creditor processing unit 23 performs various processes. For example, the various processes are processes that convert received information, instructions, etc. into information, instructions, etc. with a structure to be sent. For example, the various processes are processes that convert received information into information with a structure to be output.

[0114] The creditor transmitting unit 24 transmits various information, instructions, etc. to the credit management device 1 or other devices (not shown). The various information, instructions, etc. are, for example, application information, negotiation information, and output instructions.

[0115] The creditor receiving unit 25 receives various types of information from the creditor, such as confirmation information, negotiation information, credit status information, and various types of screen information.

[0116] The creditor output unit 26 outputs various information, such as confirmation information, negotiation information, credit status information, and various screens.

[0117] Here, output is a concept that typically includes displaying on a display, projecting using a projector, printing on a printer, outputting sound, transmitting to an external device, storing on a recording medium, and handing over processing results to other processing devices or other programs.

[0118] Various types of information are stored in the debtor storage unit 31 that constitutes the debtor terminal 3. The various types of information include, for example, debtor identifiers.

[0119] The debtor reception unit 32 receives various types of information, instructions, etc. Examples of the various types of information, instructions, etc. include confirmation information, negotiation information, output instructions, proposal content instructions, agreement document instructions, and payment schedule instructions.

[0120] The means for inputting various information and instructions may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0121] The debtor processing unit 33 performs various types of processing. For example, the various types of processing are processing to convert received information, instructions, etc. into information, instructions, etc. with a structure to be sent. For example, the various types of processing are processing to convert received information into information with a structure to be output.

[0122] The debtor transmitting unit 34 transmits various information, instructions, etc. to the debt management device 1 or other devices (not shown). The various information, instructions, etc. are, for example, confirmation information, negotiation information, and output instructions.

[0123] The debtor receiving unit 35 receives various types of information from, for example, notification information, negotiation information, and debt status information.

[0124] The debtor output unit 36 ​​outputs various information, such as notification information, negotiation information, debt status information, and various screens.

[0125] The storage unit 11, the credit management unit 111, the creditor storage unit 21, and the debtor storage unit 31 are preferably non-volatile recording media, but may also be realized as volatile recording media.

[0126] There is no restriction on the process by which information is stored in the storage unit 11 etc. For example, information may be stored in the storage unit 11 etc. via a recording medium, information transmitted via a communication line etc. may be stored in the storage unit 11 etc., or information input via an input device may be stored in the storage unit 11 etc.

[0127] The receiving unit 12, the application acquisition unit 121, the confirmation receiving unit 122, the negotiation receiving unit 123, the instruction receiving unit 124, the creditor receiving unit 25, and the debtor receiving unit 35 are realized, for example, by wireless or wired communication means, but may also be realized by means of receiving broadcasts, etc.

[0128] The processing unit 13, the petition storage unit 131, the update unit 132, the confirmation storage unit 133, the negotiation storage unit 134, the proposal content acquisition unit 135, the mediation support unit 136, the judgment unit 137, the agreement document generation unit 138, the information acquisition unit 139, the creditor processing unit 23, and the debtor processing unit 33 can typically be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are typically realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type is not important. The petition acquisition unit 121, like the processing unit 13, may also be realized by a processor, memory, etc.

[0129] The transmitting unit 14, the application notification unit 141, the screen transmitting unit 142, the proposal content transmitting unit 143, the negotiation information output unit 144, the necessary information transmitting unit 145, the agreement document output unit 146, the information transmitting unit 147, the creditor transmitting unit 24, and the debtor transmitting unit 34 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

[0130] The creditor reception unit 22 and the debtor reception unit 32 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0131] The creditor output unit 26 and the debtor output unit 36 ​​may or may not include output devices such as a display, a speaker, etc. The creditor output unit 26 may be realized by driver software for an output device, or by a combination of driver software for an output device and an output device, etc.

[0132] Next, an example of the operation of the claim management device 1 will be described with reference to the flowcharts of FIGS.

[0133] (Step S401) The petition acquisition unit 121 determines whether or not a case registration has been received from the creditor terminal 2. If a case registration has been received, the process proceeds to step S402, and if not, the process proceeds to step S408.

[0134] (Step S402) The claim accumulation unit 131 acquires claim time information, which is date and time, from a clock (not shown). The claim accumulation unit 131 acquires claim information included in the case registration. The claim accumulation unit 131 accumulates information that has the claim information and the claim time information, constituting the claim information to be accumulated.

[0135] (Step S403) The claim accumulation unit 131 acquires a unique bond identifier.

[0136] (Step S404) The claim accumulation unit 131 accumulates the claim information acquired in step S402 in the claim management unit 111, paired with the claim identifier acquired in step S403. Here, the update unit 132 may update the phase identification information to "waiting for confirmation" in pair with the claim identifier.

[0137] (Step S405) The request notification unit 141 composes notification information. An example of the process of compose such notification information will be described with reference to the flowchart in FIG.

[0138] (Step S406) The application notification unit 141 acquires the creditor's contact information from the received application information.

[0139] (Step S407) The claim notification unit 141 transmits the notification information configured in step S405 to the contact point identified by the contact point information acquired in step S406. Return to step S401.

[0140] (Step S408) The confirmation receiving unit 122 determines whether confirmation information, etc. has been received from the debtor terminal 3. If confirmation information, etc. has been received, the process proceeds to step S409; if confirmation information, etc. has not been received, the process proceeds to step S411. Note that confirmation information, etc. refers to confirmation information or non-existence information. Furthermore, the received confirmation information, etc. is associated with a debt identifier.

[0141] (Step S409) The confirmation accumulation unit 133 acquires the bond identifier associated with the confirmation information and the like.

[0142] (Step S410) The confirmation accumulation unit 133 acquires confirmation time information from a clock (not shown). The confirmation accumulation unit 133 stores the confirmation information, including the confirmation time information, in the claim management unit 111 in association with the claim identifier acquired in step S409. Return to step S401. Note that if the information received here is confirmation information, the confirmation accumulation unit 133 may update the phase identification information associated with the claim identifier to "confirmed."

[0143] (Step S411) The negotiation receiving unit 123 determines whether negotiation information has been received from the creditor terminal 2 or the debtor terminal 3. If negotiation information has been received, the process proceeds to step S412; if not, the process proceeds to step S423. The received negotiation information is associated with a bond identifier.

[0144] (Step S412) The negotiation accumulation unit 134 acquires the bond identifier.

[0145] (Step S413) The negotiation accumulation unit 134 accumulates the negotiation information in association with the bond identifier in the bond management unit 111. The negotiation accumulation unit 134 may also acquire an inputter identifier and accumulate the negotiation information including the inputter identifier.

[0146] (Step S414) The proposal content acquisition unit 135 determines whether the received negotiation information matches the proposal content creation conditions. If the negotiation information matches the proposal content creation conditions, the process proceeds to step S415; if not, the process proceeds to step S417.

[0147] (Step S415) The proposal content acquisition unit 135 composes proposal content. An example of such proposal content composition processing will be described with reference to the flowchart in FIG.

[0148] (Step S416) The proposal content acquisition unit 135 stores the proposal content constructed in step S415 in the credit management unit 111 in association with the negotiation information.

[0149] (Step S417) The determination unit 137 determines whether the received negotiation information matches the agreed conditions. If it matches the agreed conditions, the process proceeds to step S418, and if it does not match, the process returns to step S401.

[0150] (Step S418) The agreement document generation unit 138 generates an agreement document. An example of such agreement document generation processing will be described with reference to the flowchart in FIG.

[0151] (Step S419) The agreement creation unit 138 stores the agreement acquired in step S418 in the bond management unit 111 in association with the bond identifier.

[0152] (Step S420) The processing unit 13 acquires a creditor identifier. The necessary information sending unit 145 acquires necessary information paired with the creditor identifier from the credit management unit 111. The necessary information is, for example, deposit destination information.

[0153] (Step S421) The processing unit 13 determines whether or not the necessary information was acquired in step S420. If the necessary information was acquired, the process proceeds to step S422, and if not, the process returns to step S401.

[0154] (Step S422) The necessary information transmitting unit 145 transmits the necessary information to the debtor. Return to step S401. Note that the means for transmitting the necessary information here is not important.

[0155] (Step S423) The instruction receiving unit 124 determines whether or not an output instruction has been received from the creditor terminal 2 or the debtor terminal 3. If an output instruction has been received, the process proceeds to step S424; if not, the process proceeds to step S428. The output instruction is associated with a credit identifier.

[0156] (Step S424) The information acquisition unit 139 acquires the bond identifier associated with the output instruction received in step S423.

[0157] (Step S425) The information acquisition unit 139 acquires the claim status information paired with the claim identifier acquired in step S424 from the claim management unit 111. Note that the claim status information acquired here may be a part of the claim status information of the claim management unit 111.

[0158] (Step S426) The information acquisition unit 139 composes information to be output using the credit status information acquired in step S425. An example of such output information composition processing will be described with reference to the flowchart of FIG.

[0159] (Step S427) The information transmitting unit 147 transmits the output information to the terminal that has transmitted the output instruction. Return to step S401.

[0160] (Step S428) The instruction receiving unit 124 determines whether or not a proposal content instruction has been received from the creditor terminal 2 or the debtor terminal 3. If a proposal content instruction has been received, the process proceeds to step S429; if not, the process proceeds to step S431. The proposal content instruction corresponds to one negotiation information.

[0161] (Step S429) The information acquisition unit 139 acquires from the claim management unit 111 the proposal content paired with the negotiation information corresponding to the proposal content instruction received in step S428.

[0162] (Step S430) The information transmitting unit 147 transmits the proposal content acquired in step S429 to the terminal that transmitted the proposal content instruction. Return to step S401.

[0163] (Step S431) The instruction receiving unit 124 determines whether or not an agreement document instruction has been received from the creditor terminal 2 or the debtor terminal 3. If an agreement document instruction has been received, the process proceeds to step S432; if not, the process proceeds to step S434. The agreement document instruction is associated with a credit identifier.

[0164] (Step S432) The information acquisition unit 139 acquires the bond identifier corresponding to the agreement document instruction received in step S431. The information acquisition unit 139 acquires the agreement document paired with the bond identifier from the bond management unit 111.

[0165] (Step S433) The information transmitting unit 147 transmits the agreement document acquired in step S432 to the terminal that transmitted the agreement document instruction. Return to step S401.

[0166] (Step S434) The instruction receiving unit 124 determines whether or not a payment schedule instruction has been received from the creditor terminal 2 or the debtor terminal 3. If a payment schedule instruction has been received, the process proceeds to step S435; if not, the process proceeds to step S437. The payment schedule instruction is associated with a credit identifier.

[0167] (Step S435) The information acquisition unit 139 acquires the bond identifier corresponding to the payment schedule instruction received in step S434. The information acquisition unit 139 acquires the total payment amount and monthly amount paired with the bond identifier from the bond management unit 111. The information acquisition unit 139 acquires the payment schedule using the total payment amount and monthly amount.

[0168] (Step S436) Information transmitting unit 147 transmits the payment schedule acquired in step S435 to the terminal that transmitted the payment schedule instruction. Return to step S401.

[0169] (Step S437) The receiving unit 12 determines whether or not payment information has been received. If payment information has been received, the process proceeds to step S438; if not, the process proceeds to step S439. The payment information is associated with the bond identifier.

[0170] (Step S438) The processing unit 13 stores the payment information in association with the bond identifier. Return to step S401.

[0171] (Step S439) The processing unit 13 determines whether or not the transmission conditions are met for transmitting specific screen information to the creditor terminal 2 or the debtor terminal 3. If the transmission conditions are met, the process proceeds to step S440, and if not, the process returns to step S401.

[0172] The transmission conditions include, for example, receiving confirmation information or specific negotiation information, or receiving a screen output instruction from the creditor terminal 2 or the debtor terminal 3. The transmission conditions are associated with the screen information to be transmitted.

[0173] (Step S440) The information acquisition unit 139 acquires screen information corresponding to the transmission condition from the storage unit 11. Note that the screen information corresponding to the transmission condition is, for example, screen information paired with the selected selection object.

[0174] (Step S441) The information transmitting unit 147 transmits the screen information acquired in step S440 to the creditor terminal 2 or the debtor terminal 3. The process returns to step S401.

[0175] In the flowcharts of FIGS. 4 and 5, the processing ends when the power is turned off or an interrupt occurs to end the processing.

[0176] Next, an example of the notification information configuration process in step S405 will be described with reference to the flowchart in FIG.

[0177] (Step S601) The claim notification unit 141 acquires a notification information template from the storage unit 11.

[0178] (Step S602) The claim notification unit 141 acquires a bond identifier, and then acquires information about the creditor that pairs with the bond identifier (for example, the name of the creditor).

[0179] (Step S603) The application notification unit 141 assigns the creditor's information to the variable in the notification information template for assigning the creditor's information.

[0180] (Step S604) The application notification unit 141 acquires information on the debtor (for example, the name of the debtor) that is paired with the bond identifier.

[0181] (Step S605) The application notification unit 141 assigns the information of the debtor to the variable in the notification information template for assigning the information of the debtor.

[0182] (Step S606) The application notification unit 141 acquires link information for accessing the claim content information paired with the claim identifier. The link information is usually a URL, but any information for accessing the claim content information will suffice.

[0183] (Step S607) The claim notification unit 141 assigns the link information to the variable in the notification information template for assigning the link information, and returns to the upper level processing.

[0184] Next, an example of the proposal content construction process in step S415 will be described with reference to the flowchart in FIG.

[0185] (Step S701) The proposal content acquisition unit 135 acquires a proposal content template from the storage unit 11.

[0186] The proposal content acquisition unit 135 acquires, for example, a debt settlement identifier included in the negotiation information, and acquires from the storage unit 11 a proposal content template that is paired with the debt settlement identifier.

[0187] (Step S702) The proposal content acquisition unit 135 acquires the bond identifier associated with the received negotiation information.

[0188] (Step S703) The proposal content acquisition unit 135 assigns 1 to a counter i.

[0189] (Step S704) The proposal content acquisition unit 135 determines whether the i-th variable exists in the proposal content template acquired in step S701. If the i-th variable exists, the process proceeds to step S705, and if not, the process returns to the upper level process.

[0190] (Step S705) The proposal content acquisition unit 135 acquires information corresponding to the i-th variable from the bond status information paired with the bond identifier.

[0191] (Step S706) The proposal content acquisition unit 135 substitutes the information acquired in step S705 into the i-th variable in the proposal content template.

[0192] (Step S707) The proposal content acquisition unit 135 increments the counter i by 1. The process returns to step S704.

[0193] Next, an example of the agreement document generation process in step S418 will be described with reference to the flowchart in FIG.

[0194] (Step S801) The agreement document generation unit 138 acquires an agreement document template from the storage unit 11.

[0195] (Step S802) The agreement document generation unit 138 acquires the bond identifier associated with the received negotiation information.

[0196] (Step S803) The agreement document generation unit 138 assigns 1 to a counter i.

[0197] (Step S804) The agreement document generation unit 138 determines whether the i-th variable exists in the agreement document template acquired in step S801. If the i-th variable exists, the process proceeds to step S805; if not, the process returns to the upper-level process.

[0198] (Step S805) The agreement document generation unit 138 acquires information corresponding to the i-th variable from the bond status information paired with the bond identifier.

[0199] (Step S806) The agreement document generation unit 138 substitutes the information acquired in step S805 into the i-th variable in the agreement document template.

[0200] (Step S807) The agreement document generation unit 138 increments the counter i by 1. The process returns to step S804.

[0201] Next, an example of the output information configuration process in step S426 will be described with reference to the flowchart in FIG.

[0202] (Step S901) The information acquisition unit 139 acquires, from the storage unit 11, screen information that is the basis for configuring output information.

[0203] (Step S902) The information acquisition unit 139 assigns 1 to a counter i.

[0204] (Step S903) The information acquisition unit 139 determines whether or not the i-th variable exists in the screen information. If the i-th variable exists, the process proceeds to step S904, and if not, the process proceeds to step S907.

[0205] (Step S904) The information acquisition unit 139 acquires a bond identifier. The information acquisition unit 139 acquires information corresponding to the i-th variable in the screen information from the bond status information paired with the bond identifier. The information corresponding to the i-th variable is, for example, the creditor name, debtor name, payment amount, payment start date, and payment due date.

[0206] (Step S905) The information acquisition unit 139 assigns the information acquired in step S904 to the ith variable in the screen information.

[0207] (Step S906) The information acquisition unit 139 increments the counter i by 1. The process returns to step S903.

[0208] (Step S907) The information acquisition unit 139 acquires application-related information using the application information in the claim status information that is paired with the claim identifier acquired in step S904. The application-related information is, for example, information indicating that a claim has been filed (e.g., "filed"), application time information (e.g., date and time), and the creditor's name.

[0209] (Step S908) The information acquisition unit 139 determines whether or not confirmation information exists in the bond status information paired with the bond identifier acquired in step S904. If confirmation information exists, the process proceeds to step S909; if not, the process returns to the upper level process.

[0210] (Step S909) The information acquisition unit 139 acquires confirmation-related information using the confirmation information of the claim status information paired with the claim identifier. The confirmation-related information may be, for example, information indicating that the claim application has been confirmed (e.g., "The case has been confirmed"), confirmation time information (e.g., date and time), and the debtor's name.

[0211] (Step S910) The information acquisition unit 139 assigns 1 to the counter i.

[0212] (Step S911) The information acquisition unit 139 determines whether the i-th negotiation information exists in the bond status information paired with the bond identifier acquired in step S904. If the i-th negotiation information exists, the process proceeds to step S912; if not, the process proceeds to step S919.

[0213] (Step S912) The information acquisition unit 139 acquires the creditor identifier or debtor identifier paired with the i-th negotiation information from the debt status information paired with the debt identifier. Note that the creditor identifier or debtor identifier will be referred to as the identifier as appropriate.

[0214] (Step S913) The information acquisition unit 139 determines whether or not the i-th negotiation information is associated with the proposal content. If the proposal content is associated, the process proceeds to step S914, and if the proposal content is not associated, the process proceeds to step S915.

[0215] (Step S914) The information acquisition unit 139 uses the i-th negotiation information and the proposal content to construct negotiation-related information to be output. Then, the process proceeds to step S916. Note that the negotiation-related information here includes, for example, a sentence explaining the negotiation information, negotiation time information, and link information to the proposal content.

[0216] (Step S915) The information acquisition unit 139 uses the i-th negotiation information to compose negotiation-related information to be output. Note that the negotiation-related information here includes, for example, a sentence explaining the negotiation information and negotiation-time information.

[0217] (Step S916) The information acquiring unit 139 places the i-th negotiation related information on the side specified by the identifier (for example, the right or left side of the screen) below the information that has already been placed.

[0218] (Step S917) The information acquisition unit 139 increments the counter i by 1. The process returns to step S911.

[0219] (Step S918) The information acquisition unit 139 determines whether or not an agreement has been reached. If an agreement has been reached, the process proceeds to step S919, and if an agreement has not been reached, the process returns to the upper level process.

[0220] (Step S919) The information acquisition unit 139 acquires necessary information paired with the bond identifier. The necessary information is usually deposit destination information.

[0221] (Step S920) The information acquisition unit 139 arranges the necessary information in the screen information, and returns to the upper-level processing.

[0222] Next, an example of the operation of the creditor terminal 2 will be described with reference to the flowchart of FIG.

[0223] (Step S1001) The creditor acceptance unit 22 judges whether or not the case registration has been accepted. If the case registration has been accepted, the process proceeds to step S1002, and if not, the process proceeds to step S1003.

[0224] (Step S1002) The creditor transmission unit 24 transmits the case registration accepted in step S1001 to the credit management device 1. The process returns to step S1001.

[0225] (Step S1003) The creditor receiving unit 22 judges whether or not an output instruction has been received. If an output instruction has been received, the process proceeds to step S1004, and if not, the process proceeds to step S1007.

[0226] (Step S1004) The creditor processing unit 23 acquires the bond identifier. The creditor transmitting unit 24 transmits the output instruction received in step S1003 to the bond management device 1 in association with the bond identifier.

[0227] (Step S1005) The creditor receiving unit 25 judges whether or not the output information has been received. If the output information has been received, the process proceeds to step S1006, and if not, the process returns to step S1005.

[0228] (Step S1006) The creditor processing unit 23 composes output information to be output from the received output information. The creditor output unit 26 outputs the output information. The process returns to step S1001.

[0229] (Step S1007) The creditor reception unit 22 judges whether or not the negotiation information has been received. If the negotiation information has been received, the process proceeds to step S1008, and if not, the process proceeds to step S1009.

[0230] (Step S1008) The creditor processing unit 23 acquires the bond identifier. The creditor transmitting unit 24 associates the negotiation information received in step S1007 with the bond identifier and transmits it to the bond management device 1. The process returns to step S1001.

[0231] (Step S1009) The creditor reception unit 22 determines whether or not a screen output instruction has been received. If a screen output instruction has been received, the process proceeds to step S1010; if not, the process proceeds to step S1013. The screen output instruction includes information that identifies the screen information.

[0232] (Step S1010) The creditor processing unit 23 acquires the bond identifier. The creditor transmitting unit 24 transmits the screen output instruction received in step S1009 to the credit management device 1 in association with the bond identifier.

[0233] (Step S1011) The creditor receiving unit 25 determines whether or not screen information has been received from the credit management device 1. If screen information has been received, the process proceeds to step S1012, and if not, the process returns to step S1011.

[0234] (Step S1012) The creditor processing unit 23 creates a screen from the screen information received in step S1011. The creditor output unit 26 outputs the screen. The process returns to step S1001.

[0235] (Step S1013) The creditor receiving unit 22 determines whether or not other instructions have been received. If other instructions have been received, the process proceeds to step S1014, and if not, the process returns to step S1001.

[0236] (Step S1014) The creditor processing unit 23 acquires the bond identifier. The creditor transmitting unit 24 transmits the instruction received in step S1013 to the credit management device 1 in association with the bond identifier.

[0237] (Step S1015) The creditor receiving unit 25 judges whether or not information has been received from the credit management device 1. If information has been received, the process proceeds to step S1016, and if information has not been received, the process returns to step S1015.

[0238] (Step S1016) The creditor processing unit 23 composes information to be output from the received information. The creditor output unit 26 outputs the information. The process returns to step S1001.

[0239] In the flowchart of FIG. 10, the process ends when the power is turned off or an interrupt occurs to end the process.

[0240] Next, an example of the operation of the debtor terminal 3 will be described with reference to the flowchart of FIG.

[0241] (Step S1101) The debtor receiving unit 35 determines whether or not notification information has been received from the debt management device 1. If notification information has been received, the process proceeds to step S1102, and if not, the process proceeds to step S1104. The received notification information is associated with a debt identifier.

[0242] (Step S1102) The debtor output unit 36 ​​outputs the notification information received in step S1101.

[0243] (Step S1103) The debtor receiving unit 32 determines whether or not confirmation information, etc. has been received. If confirmation information, etc. has been received, the process proceeds to step S1104, and if not, the process returns to step S1103.

[0244] (Step S1104) The debtor processing unit 33 acquires the bond identifier associated with the notification information. The debtor transmitting unit 34 associates the confirmation information and the like with the bond identifier and transmits it to the debt management device 1. Return to step S1101.

[0245] (Step S1105) The debtor receiving unit 32 determines whether or not an output instruction has been received. If an output instruction has been received, the process proceeds to step S1106, and if not, the process proceeds to step S1009.

[0246] (Step S1106) The debtor processing unit 33 acquires the bond identifier associated with the screen on which the output instruction is input. The debtor sending unit 34 sends the output instruction to the debt management device 1 in association with the bond identifier.

[0247] (Step S1107) The debtor receiving unit 35 determines whether or not the output information has been received. If the output information has been received, the process proceeds to step S1109, and if not, the process returns to step S1107.

[0248] (Step S1108) The debtor processing unit 33 composes output information to be output from the output information received in step S1107. The debtor output unit 36 ​​outputs the output information. The process returns to step S1101.

[0249] (Step S1109) The debtor receiving unit 32 judges whether or not the negotiation information has been received. If the negotiation information has been received, the process proceeds to step S1110, and if not, the process proceeds to step S1111.

[0250] (Step S1110) The debtor processing unit 33 acquires the bond identifier associated with the screen for inputting the negotiation information. The debtor transmission unit 34 transmits the negotiation information received in step S1109 to the debt management device 1 in association with the bond identifier. Return to step S1101.

[0251] (Step S1111) The debtor receiving unit 32 determines whether or not a screen output instruction has been received. If a screen output instruction has been received, the process proceeds to step S1112, and if not, the process proceeds to step S1115.

[0252] (Step S1112) The debtor processing unit 33 acquires the bond identifier. The debtor transmitting unit 34 transmits the screen output instruction received in step S1111 to the debt management device 1 in association with the bond identifier.

[0253] (Step S1113) The debtor receiving unit 35 determines whether or not screen information has been received from the debt management apparatus 1. If screen information has been received, the process proceeds to step S1114, and if not, the process returns to step S1113.

[0254] (Step S1114) The debtor processing unit 33 creates a screen from the screen information received in step S1113. The debtor output unit 36 ​​outputs the screen. The process returns to step S1101.

[0255] (Step S1115) The debtor receiving unit 32 determines whether or not other instructions have been received. If other instructions have been received, the process proceeds to step S1116, and if not, the process returns to step S1101.

[0256] (Step S1116) The debtor processing unit 33 acquires the bond identifier. The debtor transmitting unit 34 transmits the instruction received in step S1115 to the debt management device 1 in association with the bond identifier.

[0257] (Step S1117) The debtor receiving unit 35 judges whether or not information has been received from the debt management device 1. If information has been received, the process proceeds to step S1118, and if information has not been received, the process returns to step S1116.

[0258] (Step S1118) The debtor processing unit 33 composes information to be output from the received information. The debtor output unit 36 ​​outputs the information. The process returns to step S1101.

[0259] In the flowchart of FIG. 11, the process ends when the power is turned off or an interrupt occurs to end the process.

[0260] A specific example of the operation of the information system A in this embodiment will be described below. It is assumed that the claims handled by the claim management device 1 here are monetary claims. FIG. 12 shows the flow of phases in the claim management device 1, from the time a claim is generated until the creditor and debtor agree on claim processing and claim processing is completed. In FIG. 12, the phases progress in the order of "filed," "waiting for confirmation," "confirmed," "negotiating," "claim processing," and "claim processing completed." It is also assumed that "negotiating" may transition to "online mediation." It is also assumed that the phase progresses from "online mediation" to "claim processing" or "negotiation failure." The numbers above the character strings indicating each phase in FIG. 12 are phase identifiers that identify the phase. That is, the phase identifier for the "filed" phase is "1," "waiting for confirmation" is "2," "confirmed" is "3," "negotiating" is "4," "claim processing" is "5," "claim processing completed" is "6," "online mediation" is "7," and "negotiation failure" is "8." It should be noted that "debt processing in progress" refers to, for example, the stage of a payment in the middle of multiple installments.

[0261] The storage unit 11 of the debt management device 1 stores the creditor management table shown in Figure 13. The creditor management table is a table that manages information about creditors. The creditor management table is a table that manages creditor information registered by users in order to receive services from the debt management device 1. The creditor management table manages one or more records that have an "ID," "creditor identifier," "creditor name," "email address," and "payment destination information." The "creditor name," "email address," and "payment destination information" make up the creditor information. The "payment destination information" is, for example, bank account information.

[0262] The claims management unit 111 of the claims management device 1 stores a claims management table having the structure shown in Figure 14. The claims management table is a table that manages claim status information. The claims management table is a table that manages one or more records that have "claim identifier," "claim information," "confirmation information," "claim processing identifier," "phase identifier," "negotiation information," "time of negotiation," "proposal content," and "agreement document." "Claims information" has "claim content information," "creditor identifier," "debtor information," and "time of claim." "Confirmation information" has "time of confirmation." "Negotiation information" here has "inputter" and "negotiation content." "Inputter" has either "1," which indicates that the person inputting the negotiation information is the creditor, or "2," which indicates that the person inputting the negotiation information is the debtor.

[0263] The information that constitutes the "debt settlement identifier" here is "1" for "pay by credit card now," "2" for "pay in full at the end of the following month," "3" for "pay in installments at the end of each month," "4" for "suggestion to adjust the amount," "5" for "I don't remember the bill," "6" for "already paid directly," and "7" for "request online mediation." The "debt settlement identifier" may also have a payment method identifier. The payment method identifier is, for example, "A" for credit card payment and "B" for bank transfer.

[0264] The storage unit 11 of the debt management device 1 stores a proposal content template for each debt processing means identifier (Figure 15). The storage unit 11 of the debt management device 1 also stores an agreement document template for each debt processing means identifier (Figure 16). In the proposal content template and agreement document template, character strings enclosed in "<" and ">" are variables. Information is substituted into the variables to form the proposal content. The debtor's name is placed in the variable <debtor name>, and the creditor's name is placed in the variable <creditor name>.

[0265] In the above situation, it is assumed that Tanaka A, who has registered creditor information in the creditor management device 1, logs in to the creditor management device 1 using the creditor terminal 2.

[0266] Then, it is assumed that, through an operation by Tanaka A, the creditor terminal 2 receives screen information for filing a claim from the claim management device 1 and outputs the case registration screen shown in FIG.

[0267] Next, Tanaka A enters information into the fields of the screen shown in FIG. 17, such as "Name of the claim," "Amount claimed," and "Due date for payment of the main amount," and clicks the "Filing" button 1701.

[0268] Next, the creditor reception unit 22 of the creditor terminal 2 accepts the case registration in response to the instruction of button 1701. The case registration has the application information "<Application Case Name>X Company Non-Payment <Application Amount>100,000 <Payment Due Date of Main Unit>2924 / 8 / 1 <Creditor Identifier>C01... <Other Party Name>X Company... <Other Party Email Address>yy@x.jp". Next, the creditor transmission unit 24 transmits the case registration to the credit management device 1. It is assumed that the creditor identifier "C01" is stored in the creditor storage unit 21, for example.

[0269] Next, the claim acquisition unit 121 of the claim management device 1 receives the case registration from the creditor terminal 2. The claim acquisition unit 121 acquires the claim time "2024 / 8 / 11 09:00", which is the current date and time, from a clock (not shown). The claim acquisition unit 121 composes the claim information to be accumulated: "<Name of claim>X Company Non-payment <Claim amount>100,000 <Payment due date of main body>2924 / 8 / 1 <Creditor identifier>C01 ··· <Other party's name>X Company ···<Other party's email address>yy@x.jp <Claim time>2024 / 8 / 11 15:35". Next, the claim accumulation unit 131 acquires the unique claim identifier "1". Next, the claim accumulation unit 131 pairs the constructed claim information with the claim identifier "1" and accumulates it in the claim management table (Figure 14). This claim information is the claim information of "ID=1" in Fig. 14. Furthermore, the update unit 132 stores "1" as the phase identifier in the record of "ID=1" in Fig. 14.

[0270] Next, the application notification unit 141 of the debt management device 1 composes the notification information as follows. First, the application notification unit 141 composes the notification information of FIG. 18 in accordance with the operation of the notification information composition process described using the flowchart of FIG. 6. The application notification unit 141 composes the notification information by substituting information corresponding to each underlined part into the notification information template in FIG. 18, in which the underlined parts are variables. Next, the application notification unit 141 obtains the debtor's contact information "yy@x.jp" from the application information. Next, the application notification unit 141 sends the notification information (FIG. 18) to the contact specified by the contact information. Furthermore, the update unit 132 updates the phase identifier of "ID=1" in FIG. 14 from "1" to "2".

[0271] Next, the debtor terminal 3 receives and outputs the email that is the notification information (FIG. 18) from the claim management apparatus 1. Note that the trigger for outputting the notification information in the debtor terminal 3 does not matter.

[0272] Next, suppose that "Yamada Y," a person in charge at Company X, views the notification information (Figure 18) and clicks on URL 1801. Next, the debtor terminal 3 obtains screen information including the claim information corresponding to URL 1801 from the claim management device 1, and outputs a confirmation screen (Figure 19) based on the screen information. The confirmation screen is a screen on which the debtor confirms the claim application. Next, suppose that Yamada Y views the confirmation screen, checks the checkbox 1901 for "This is a claim for me," and clicks the "Next" button 1902. The debtor reception unit 32 of the debtor terminal 3 then receives the confirmation information. Next, the debtor processing unit 33 obtains the claim identifier "1" associated with the screen information. Next, the debtor processing unit 33 constructs the confirmation information to be sent, "<Confirmation result>Confirmation <Claims identifier>1." Next, the debtor transmission unit 34 transmits the confirmation information to the claim management device 1. The confirmation result "Confirmation" is information indicating that confirmation has been made, e.g., "1."

[0273] Next, the confirmation receiving unit 122 of the claim management device 1 receives the confirmation information "<Confirmation result> Confirmation <Claims identifier> 1" from the debtor terminal 3. Next, the confirmation accumulation unit 133 acquires the received claims identifier "1". Next, the confirmation accumulation unit 133 acquires the confirmation time "2024 / 8 / 11 15:50", which is the date and time, from a clock (not shown). Next, based on the confirmation information "<Confirmation result> Confirmation", the confirmation accumulation unit 133 accumulates the confirmation time "2024 / 8 / 11 15:50" in pair with the claims identifier "1". In addition, the update unit 132 updates the phase identifier from "2" to "3".

[0274] Next, the processing unit 13 determines that the transmission conditions are met by receiving the confirmation information, and obtains screen information that meets the transmission conditions from the storage unit 11. This screen information is screen information for constructing a decision screen. The decision screen is a screen for determining a debt settlement identifier. Next, the screen transmission unit 142 transmits the screen information to Yamada Y's debtor terminal 3.

[0275] The debtor terminal 3 receives the screen information and outputs a debt settlement identifier determination screen (Fig. 20). The screen in Fig. 20 has a history 2001 of debt settlement and buttons 2002 corresponding to each of the seven debt settlement identifier candidates.

[0276] Then, let us say that Yamada Y selects button 2003 from Figure 20. Let us also assume that Yamada Y enters the inquired installment amount of "5,000 yen" by pressing button 2003. Then, the debtor reception unit 32 of the debtor terminal 3 receives the negotiation information "<debt processing identifier>3 <installation amount>5000". The debtor processing unit 33 acquires the debt identifier "1" and composes the negotiation information to be transmitted "<debt identifier>1 <debt processing identifier>3 <installation amount>5000". Next, the debtor transmission unit 34 transmits the negotiation information to the debt management device 1.

[0277] Next, the negotiation receiving unit 123 of the debt management device 1 receives the negotiation information from the debtor terminal 3. Next, the negotiation accumulation unit 134 acquires the debt identifier "1" from the received negotiation information. The negotiation accumulation unit 134 also acquires the negotiation time "2024 / 8 / 11 16:01", which is the current date and time, from a clock not shown. The negotiation accumulation unit 134 also detects that the debt processing identifier is "3" (installment payment), acquires the claimed amount "100,000 yen" and installment amount "5,000 yen" that are paired with the debt identifier "1", acquires the payment start date, payment end date, and payment amount for each month (acquires the payment schedule), and accumulates them as a pair with the debt identifier "1". The payment schedule is accumulated in FIG. 14, but is not shown.

[0278] Next, the proposal content acquisition unit 135 determines that the debt settlement identifier "3" included in the received negotiation information matches the proposal content creation conditions. Then, the proposal content acquisition unit 135 composes the proposal content by the process described using the flowchart in Figure 7. Next, the proposal content acquisition unit 135 associates the composed proposal content with the negotiation information and stores it in the debt management table (Figure 14). This proposal content is file "P1".

[0279] Furthermore, in response to receiving the negotiation information, the processing unit 13 uses the notification information template in the storage unit 11 to create notification information to be sent to the creditor. This notification information is information for notifying the debtor of the proposal. Next, the sending unit 14 sends the notification information to the creditor. Note that the notification information template here is a document in which the underlined parts in Figure 21 are variables.

[0280] Next, creditor Tanaka A's creditor terminal 2 receives and outputs the notification information. Such notification information is shown in Figure 21. Figure 21 shows notification information configured by placing the creditor's name, installment amount, and link information 2101 for accessing negotiation information in the variable portion of the notification information template. Then, let us say that Tanaka A designated the URL 2101 in Figure 21.

[0281] The creditor terminal 2 then sends an instruction to send screen information corresponding to URL 2101 to the debt management device 1, receives the screen information from the debt management device 1, and outputs the screen shown in Fig. 22. The screen information constituting the screen in Fig. 22 is information constructed using the output information construction process described using the flowchart in Fig. 9.

[0282] Next, Tanaka A selects the "Propose change to installment amount" button 2201 on the screen of Fig. 22. The creditor terminal 2 then accepts the instruction and transmits to the credit management device 1 a screen output instruction in response to the instruction of the "Propose change to installment amount" button 2201.

[0283] Next, the instruction receiving unit 124 of the claim management device 1 receives the screen output instruction. Next, the information acquiring unit 139 acquires screen information corresponding to the screen output instruction from the storage unit 11. Next, the information sending unit 147 sends the screen information to Tanaka A's creditor terminal 2.

[0284] Next, Tanaka A's creditor terminal 2 receives the screen information and outputs the installment amount change screen shown in Fig. 23. Then, Tanaka A enters the proposed new installment amount of "20,000 yen" on the screen of Fig. 23 (2301 in Fig. 23).

[0285] Next, the creditor terminal 2 accepts the proposed new installment amount of "20,000 yen" and sends negotiation information including the installment amount of "20,000 yen" to the credit management device 1, pairing it with the credit identifier "1."

[0286] Next, the receiving unit 12 of the bond management device 1 receives the negotiation information including the installment amount "20,000 yen" in combination with the bond identifier "1."

[0287] Next, the proposal content acquisition unit 135 determines that the received negotiation information matches the proposal content creation condition "including the installment amount."

[0288] Next, the proposal content acquisition unit 135 acquires a proposal content template that pairs with the proposal content creation conditions from the storage unit 11 based on the proposal content configuration process described using the flowchart in Figure 7, and constructs the proposal content by substituting the installment amount "20,000 yen" and the creditor name, debtor name, and application amount that pair with the claim identifier "1" into the proposal content template. Next, the transmission unit 14 transmits the proposal content to Tanaka A's creditor terminal 2.

[0289] Next, the creditor terminal 2 receives and outputs the proposal content. An output example of the proposal content is 2031 in FIG.

[0290] Next, Tanaka A clicks the "Propose change to installment amount" button 2303 in Figure 23. The creditor terminal 2 then accepts the instruction to the button 203. Next, the creditor terminal 2 creates negotiation information "<bond identifier> 1 <installment amount> 20,000 yen <bond identifier> C01" and sends it to the bond management device 1.

[0291] Next, the negotiation receiving unit 123 of the debt management device 1 receives the negotiation information. Next, the negotiation accumulation unit 134 acquires the debt identifier "1" contained in the negotiation information. Also, assume that the negotiation accumulation unit 134 acquires the time information "2024 / 8 / 11 16:34" from a clock not shown. The negotiation accumulation unit 134 also acquires the claim amount "100,000 yen" and installment amount "20,000 yen" that are paired with the debt identifier "1," acquires the payment start date, payment end date, and payment amount for each month (acquires the payment schedule), and accumulates them in pairs with the debt identifier "1." The payment schedule is accumulated in FIG. 14, but is not shown.

[0292] Next, the proposal content acquisition unit 135 acquires the proposal content that was previously acquired. Next, the proposal content acquisition unit 135 associates the proposal content with the negotiation information (file "P2") and stores it in the debt management table (FIG. 14).

[0293] Next, the processing unit 13 determines that the transmission condition for transmitting specific screen information, "the proposal content has been configured," is met. Next, the information acquisition unit 139 configures screen information including the negotiation information and link information to the proposal content, etc. Next, the information transmission unit 147 transmits the screen information to Yamada Y's debtor terminal 3.

[0294] Next, the debtor terminal 3 receives the screen information and outputs the screen shown in FIG. 24. Then, let us say that Yamada Y. selects the "Accept revised installment amount" button 2401 in FIG. 24. The debtor terminal 3 then accepts the instruction to the button 2401. Next, the debtor terminal 3 obtains the information "<Negotiation result>Agreed" corresponding to the button 2401, composes negotiation information including the information "<Debt identifier>1 <Negotiation result>Agreed <Installment amount>20000 <Debtor identifier>Company X", and sends it to the debt management device 1.

[0295] Next, the negotiation receiving unit 123 of the debt management device 1 receives the negotiation information. The negotiation accumulation unit 134 acquires the debt identifier "1". The negotiation accumulation unit 134 acquires the current time, the agreement time "2024 / 8 / 11 16:39", from a clock (not shown). Next, the negotiation accumulation unit 134 accumulates the negotiation information "Agreement" and the agreement time in association with the debt identifier "1".

[0296] Next, the judgment unit 137 judges that the received negotiation information matches the agreement condition "the negotiation information includes '<negotiation result> agreement'." Next, the agreement document generation unit 138 generates an agreement document "A1" by the agreement document generation process described using the flowchart in Figure 8. Then, the agreement document generation unit 138 pairs the agreement document "A1" with the bond identifier "1" and stores it in the bond management table (Figure 14).

[0297] Next, in response to the instruction of the debtor (Yamada Y), button 2401 (FIG. 24), the information acquisition unit 139 acquires screen information to be sent to the creditor, which corresponds to the negotiation information "<Debt Identifier> 1 <Negotiation Result> Agreed <Installment Amount> 20000 <Debtor Identifier> X Company." Next, the information transmission unit 147 transmits the screen information to the creditor terminal 2.

[0298] Furthermore, the information acquisition unit 139 acquires screen information for the debtor to determine a debt settlement identifier in response to an instruction from the debtor's button 2401 (FIG. 24). Next, the information transmission unit 147 transmits the screen information to the debtor terminal 3.

[0299] Next, the creditor terminal 2 receives the screen information transmitted by the information transmission unit 147 and outputs the screen shown in Fig. 25. The screen in Fig. 25 shows the process of filing a claim, confirming the case, and negotiating until an agreement is reached.

[0300] Here, let us say that Tanaka A clicks the "Check payment schedule" button 2501 on the screen in Figure 25. The creditor terminal 2 then accepts the instruction, obtains the payment schedule corresponding to the instruction and paired with the credit identifier "1" from the credit management device 1, and outputs it. An example of such a payment schedule output is shown in Figure 26.

[0301] Furthermore, the debtor terminal 3 receives screen information for determining a debt settlement identifier and outputs a screen for determining a debt settlement identifier. An example of such a screen is shown in FIG.

[0302] Next, Yamada Y clicks the "Pay by bank transfer" button 2701 on the screen of the debtor terminal 3 shown in FIG.

[0303] Next, the debtor terminal 3 accepts the instruction and obtains the debt processing identifier "B." Let us assume that the debt processing identifier "A" is "payment by credit card" and the identifier "B" is "payment by bank transfer." Next, the debtor terminal 3 pairs the debt processing identifier "B" with the debt identifier "1" and sends it to the debt management device 1.

[0304] Next, the debt management device 1 receives the debt processing identifier "B" etc., pairs it with the debt identifier "1", and stores the debt processing identifier "B" in the debt management table (Fig. 14). As a result of this processing, the debt processing identifier "3,B" is stored in the record of "ID=1" in the debt management table.

[0305] Furthermore, the update unit 132 of the bond management device 1 updates the phase identifier paired with the bond identifier "1" to "5."

[0306] Next, the information acquisition unit 139 acquires the creditor identifier "C01" that pairs with the creditor identifier "1" from the credit management table (Figure 14). Next, the information acquisition unit 139 acquires the deposit destination information "Bank Account A" that pairs with the creditor identifier "C01". Next, the information acquisition unit 139 creates screen information that includes the deposit destination information "Bank Account A". Next, the information transmission unit 147 transmits the screen information to the debtor terminal 3.

[0307] Next, the debtor terminal 3 receives the screen information and outputs the screen shown in Fig. 28. In Fig. 28, 2801 is information on "Bank Account A".

[0308] As described above, according to this embodiment, it is possible to provide a platform for managing the status of a claim in two or more phases from the time the claim is generated until the creditor and debtor agree on the processing of the claim, and for facilitating the processing of the claim.

[0309] Furthermore, according to this embodiment, it is possible to automatically create proposals regarding debt processing in accordance with negotiation information.

[0310] Furthermore, according to this embodiment, the proposal content can be appropriately presented in association with the negotiation information, so that the proposal of the other party during negotiation can be grasped in detail.

[0311] Furthermore, according to this embodiment, the proposal content relating to the debt settlement according to the negotiation information and including the debt settlement identifier selected by the debtor can be automatically constructed.

[0312] Furthermore, according to this embodiment, online arbitration of claims can be supported.

[0313] Furthermore, according to this embodiment, when negotiations for debt settlement are concluded, it is possible to present the debtor with information necessary for debt settlement.

[0314] Furthermore, according to this embodiment, it is possible to provide a platform that manages the status of a claim in two or more phases from the time a claim is filed until the creditor and debtor agree on the processing of the claim, and that promotes the processing of the claim.

[0315] Furthermore, according to this embodiment, when an agreement is reached in negotiations regarding debt settlement, an agreement document can be automatically generated.

[0316] The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to the other embodiments in this specification. The software that realizes information system A in this embodiment is the following program.In other words, this program comprises a computer that can access a claims management unit that stores one or more pieces of claim status information that is information related to claim processing, information that corresponds to a claim identifier that identifies a claim, and that can identify the current phase out of two or more phases from the occurrence of a claim until the creditor and debtor agree on claim processing; a claim acquisition unit that acquires claim information that has a creditor identifier that identifies a creditor, a debtor identifier that identifies a debtor, and claim content information related to the content of the claim; a claim storage unit that stores the claim information acquired by the claim acquisition unit in the claim management unit in association with a claim identifier that identifies the claim that corresponds to the claim information; a claim notification unit that, in response to the acquisition of the claim information by the claim acquisition unit, acquires notification information that includes information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and transmits the notification information to the debtor; and receives confirmation information related to confirmation of the claim of the claim from the debtor terminal of the debtor. The program includes a confirmation receiving unit, a confirmation storage unit that acquires confirmation information to be stored in response to the confirmation receiving unit receiving the confirmation information, and stores the confirmation information in the debt management unit in association with the debt identifier, a negotiation receiving unit that receives negotiation information regarding negotiations between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information, a negotiation storage unit that stores the negotiation information received by the negotiation receiving unit in the debt management unit in association with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and the debt identifier, an instruction receiving unit that receives an instruction to output debt status information from the creditor terminal or the debtor terminal, an information acquisition unit that acquires part or all of the debt status information corresponding to the output instruction from the debt management unit, and an information sending unit that sends part or all of the debt status information acquired by the information acquisition unit to the creditor terminal or the debtor terminal.

[0317] FIG. 29 is a block diagram of a computer system 300 that executes the programs described in this specification to realize the claim management device 1 and the like according to the various embodiments described above.

[0318] In FIG. 29, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

[0319] 29, computer 301 includes, in addition to CD-ROM drive 3012, MPU 3013, bus 3014 connected to CD-ROM drive 3012 etc., ROM 3015 for storing programs such as a boot-up program, RAM 3016 connected to MPU 3013 for temporarily storing instructions of application programs and providing temporary storage space, and hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.

[0320] A program that causes computer system 300 to execute the functions of the claim management device 1 and the like of the above-described embodiment may be stored on CD-ROM 3101, inserted into CD-ROM drive 3012, and then transferred to hard disk 3017. Alternatively, the program may be sent to computer 301 via a network (not shown) and stored on hard disk 3017. The program is loaded into RAM 3016 when executed. The program may also be loaded directly from CD-ROM 3101 or the network.

[0321] The program does not necessarily have to include an operating system (OS) or a third-party program that causes the computer 301 to execute the functions of the claim management device 1 of the above-described embodiment. The program only needs to include instructions that call appropriate functions (modules) in a controlled manner and achieve the desired results. How the computer system 300 operates is well known, and a detailed description will be omitted.

[0322] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).

[0323] The computer that executes the program may be a single computer or a plurality of computers, that is, it may perform centralized processing or distributed processing.

[0324] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0325] Furthermore, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0326] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0327] As described above, the receivables management device 1 of the present invention has the effect of managing the status of a receivable in two or more phases from the time the receivable is generated until the creditor and debtor agree on the processing of the receivable, and of providing a platform for facilitating the processing of the receivable, and is useful as a server for managing receivables, etc. [Explanation of symbols]

[0328] A. Information Systems 1. Debt management device 2. Creditor terminal 3 Debtor terminal 11 Storage area 12 Receiving section 13 Processing section 14 Transmitter 21 Creditor Storage Unit 22 Creditor Reception Department 23 Creditor Processing Department 24 Creditor Transmission Department 25 Creditor Reception Department 26 Creditor Output Section 31 Debtor Storage Unit 32 Debtor Reception Department 33 Debtor Processing Department 34 Debtor Transmission Department 35 Debtor Receiving Department 36 Debtor Output Section 111 Credit Management Department 121 Petition Acquisition Division 122 Confirmation Receipt Unit 123 Negotiation Reception Department 124 Instruction receiving unit 131 Complaint Accumulation Division 132 Update Department 133 Confirmation storage unit 134 Negotiation Storage Unit 135 Proposal content acquisition section 136 Mediation Support Department 137 Judgment Department 138 Agreement Generation Unit 139 Information Acquisition Department 141 Notice of Action Division 142 Screen Transmission Unit 143 Proposal Content Transmission Department 144 Negotiation information output unit 145 Necessary Information Transmission Unit 146 Agreement document output section 147 Information Transmission Department

Claims

1. a claim acquisition unit that acquires claim information including a creditor identifier that identifies a creditor, a debtor identifier that identifies a debtor, and debt content information relating to the content of the debt; a claim storage unit that stores the claim information acquired by the claim acquisition unit in association with a claim identifier that identifies the claim corresponding to the claim information, in a claim management unit that stores one or more pieces of claim status information that can identify the current phase out of two or more phases from the occurrence of the claim until the creditor and the debtor agree on the processing of the claim, the claim information being information that corresponds to a claim identifier that identifies the claim; a claim notification unit that, in response to the claim acquisition unit acquiring the claim information, acquires notification information including information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and transmits the notification information to the debtor; a confirmation receiving unit that receives confirmation information regarding confirmation of the claim from the debtor terminal of the debtor; a confirmation storage unit that acquires confirmation information to be stored in response to the confirmation receiving unit receiving the confirmation information, and stores the confirmation information in the claim management unit in association with the claim identifier; a negotiation receiving unit that receives negotiation information regarding negotiation between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation storage unit that stores the negotiation information received by the negotiation receiving unit in the debt management unit in association with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and the debt identifier; an instruction receiving unit that receives an instruction to output credit status information from the creditor terminal or the debtor terminal; an information acquisition unit that acquires part or all of the debt status information corresponding to the output instruction from the debt management unit; a data transmission unit that transmits part or all of the debt status information acquired by the data acquisition unit to the creditor terminal or the debtor terminal;

2. a proposal content acquisition unit that acquires information on the creditor and the debtor from the debt management unit when the negotiation information received by the negotiation receiving unit matches a proposal content creation condition, and acquires proposal content, which is information including the information on the creditor and the debtor, information including the content of the negotiation information, and information indicating a proposal regarding the processing of the debt; 2. The debt management device according to claim 1, further comprising a proposal content transmission unit that transmits the proposal content acquired by the proposal content acquisition unit to the creditor terminal or the debtor terminal.

3. The proposal content transmission unit 3. The debt management device according to claim 2, wherein the proposal content is transmitted so that the negotiation information received by the negotiation receiving unit and the proposal content acquired by the proposal content acquiring unit correspond to each other.

4. a screen sending unit that sends screen information to the debtor terminal to allow the debtor to select one of two or more methods of debt settlement after the confirmation receiving unit receives the confirmation information, The negotiation receiving unit: receiving, from the debtor terminal, the negotiation information including a debt settlement identifier that identifies one of the two or more debt settlement methods; The proposal content acquisition unit A debt management device as described in claim 2, which obtains information on the creditor and the debtor from the debt management department, and obtains the proposal content, which is information including the creditor information and the debtor information and corresponds to the debt processing identifier.

5. A debt management device as described in claim 4, further comprising a mediation support unit that, when the negotiation receiving unit receives the negotiation information including the debt processing identifier indicating online mediation from the debtor terminal, performs mediation support processing to support a group including the creditor and the debtor in conducting online mediation.

6. a determination unit that determines whether or not an agreement condition is satisfied using the negotiation information received by the negotiation receiving unit; A debt management device as described in claim 1, further comprising a necessary information sending unit that sends necessary information to the debtor, which is information necessary for the debtor to process debts, when the judgment unit determines that the agreement conditions have been met.

7. The debt management device of claim 1 further comprises a negotiation information output unit that outputs the two or more pieces of negotiation information received by the negotiation receiving unit in the order in which they were received by the negotiation receiving unit, and in a manner that makes it possible to understand whether the identifier to which the negotiation information corresponds is a creditor identifier or a debtor identifier.

8. an agreement document generation unit that generates an agreement document using the negotiation information when the negotiation information received by the negotiation receiving unit satisfies an agreement condition; 2. The debt management device according to claim 1, further comprising an agreement document output unit that outputs the agreement document generated by said agreement document generation unit.

9. The claim status information includes phase specification information that can specify a current phase among two or more phases from the occurrence of the claim to the time when the creditor and the debtor agree on the processing of the claim, A debt management device as described in any one of claims 1 to 8, further comprising an update unit that updates phase-specific information corresponding to the debt identifier in response to the application notification unit sending the notification information to the debtor and in response to the confirmation receiving unit receiving the confirmation information.

10. A claim management method implemented by a claim management unit that stores one or more pieces of claim status information that is information related to claim processing, the information being associated with a claim identifier that identifies the claim, and that can identify the current phase out of two or more phases from the occurrence of the claim until the creditor and the debtor agree on the processing of the claim, a claim acquisition unit, a claim storage unit, a claim notification unit, a confirmation receiving unit, a confirmation storage unit, a negotiation receiving unit, a negotiation storage unit, an instruction receiving unit, an information acquisition unit, and an information transmission unit, a claim acquisition step in which the claim acquisition unit acquires claim information having a creditor identifier that identifies a creditor, a debtor identifier that identifies a debtor, and claim content information regarding the content of the claim; a claim accumulation step in which the claim accumulation unit accumulates the claim information acquired by the claim acquisition unit in the claim management unit in association with a claim identifier that identifies the claim corresponding to the claim information; a petition notification step in which the petition notification unit, in response to the petition acquisition unit acquiring the petition information, acquires notification information including information on the creditor identified by the creditor identifier contained in the petition information and the debt content information, and transmits the notification information to the debtor; a confirmation receiving step in which the confirmation receiving unit receives confirmation information regarding confirmation of the claim from the debtor terminal of the debtor; a confirmation accumulation step in which the confirmation accumulation unit acquires the confirmation information to be accumulated in response to the confirmation receiving unit receiving the confirmation information, and accumulates the confirmation information in the claim management unit in association with the claim identifier; a negotiation receiving step in which the negotiation receiving unit receives negotiation information regarding negotiation between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation accumulation step in which the negotiation accumulation unit accumulates the negotiation information received by the negotiation receiving unit in the debt management unit in association with a creditor identifier identifying the creditor or a debtor identifier identifying the debtor, and the debt identifier; an instruction receiving step in which the instruction receiving unit receives an instruction to output credit status information from the creditor terminal or the debtor terminal; an information acquisition step in which the information acquisition unit acquires part or all of the debt status information corresponding to the output instruction from the debt management unit; an information transmitting step in which the information transmitting unit transmits part or all of the debt status information acquired by the information acquiring unit to the creditor terminal or the debtor terminal.

11. a computer that can access a debt management unit that stores one or more pieces of debt status information that is information related to debt processing, that is information that corresponds to a debt identifier that identifies a debt, and that can identify the current phase out of two or more phases from the occurrence of a debt until the creditor and the debtor agree on the debt processing; a claim acquisition unit that acquires claim information including a creditor identifier that identifies a creditor, a debtor identifier that identifies a debtor, and debt content information relating to the content of the debt; a claim storage unit that stores the claim information acquired by the claim acquisition unit in association with a claim identifier that identifies the claim corresponding to the claim information; a claim notification unit that, in response to the claim acquisition unit acquiring the claim information, acquires notification information including information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and transmits the notification information to the debtor; a confirmation receiving unit that receives confirmation information regarding confirmation of the claim from the debtor terminal of the debtor; a confirmation storage unit that acquires confirmation information to be stored in response to the confirmation receiving unit receiving the confirmation information, and stores the confirmation information in the claim management unit in association with the claim identifier; a negotiation receiving unit that receives negotiation information regarding negotiation between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation storage unit that stores the negotiation information received by the negotiation receiving unit in the debt management unit in association with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and the debt identifier; an instruction receiving unit that receives an instruction to output credit status information from the creditor terminal or the debtor terminal; an information acquisition unit that acquires part or all of the debt status information corresponding to the output instruction from the debt management unit; A program for causing the information acquisition unit to function as an information transmission unit that transmits part or all of the debt status information acquired by the information acquisition unit to the creditor terminal or the debtor terminal.

Images