Claims management device, claim 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 settlement of the claim, and can facilitate the settlement of the claim. [Solution] The above problem can be solved by a claim management device 1 which is equipped with 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 of the claim from the debtor, a confirmation storage unit 133 which stores the confirmation information in correspondence with the 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 an instruction to output claim status information, and an information sending unit 147 which transmits claim status information in response to the output instruction.

Description

[Technical field]

[0001] The present invention relates to a claim management device and the like for facilitating the processing of claims. [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 US Pat. No. 5,333,632). [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 for managing the status of a claim in two or more phases from the occurrence of the claim to the time when the creditor and the debtor agree on the settlement of the claim, and for facilitating the settlement of the claim. [Means for solving the problem]

[0005] The claim management device of the first invention includes a claim management unit that stores one or more claim status information pieces that are information related to claim processing, the information pieces being associated with a claim identifier that identifies the claim, and that can identify a current phase out of two or more phases from the occurrence of a claim until the creditor and the debtor agree on the processing of the claim; a claim acquisition unit that acquires claim information having 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 the claim identifier; a claim notification unit that acquires notification information including information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, in response to the claim acquisition unit acquiring the claim information, and transmits the notification information to the debtor; and a claim notification unit that receives confirmation information related to confirmation of the claim of the claim from the debtor terminal of the debtor. a confirmation receiving unit which receives the confirmation information from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information, and stores the confirmation information in the debt management unit in association with a debt identifier; a negotiation receiving unit which receives negotiation information for extinguishing a debt 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 which 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 a debt identifier; an instruction receiving unit which receives an instruction to output debt status information from the creditor terminal or debtor terminal; an information acquiring unit which acquires part or all of the debt status information corresponding to the output instruction from the debt management unit; and an information transmitting unit which transmits part or all of the debt status information acquired by the information acquiring 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, compared to the first invention, is a receivables management device that further includes 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 the creditor information and the debtor information, information including the content of the negotiation information, and information indicating a proposal regarding the processing of the receivables, and a proposal content transmission unit that transmits the proposal content acquired by the proposal content acquisition unit to a creditor terminal or a debtor terminal.

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

[0009] In addition, 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, the negotiation information and the proposal contents can be presented appropriately.

[0011] In addition, the claims management device of the fourth invention, compared to the second or third inventions, 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 claims processing methods after the confirmation receiving unit receives the confirmation information, the negotiation receiving unit receives negotiation information from the debtor terminal including a claims processing identifier that identifies one of the two or more claims processing methods, and the proposal content acquisition unit acquires creditor information and debtor information from the claims management unit, and acquires proposal content including the creditor information and the debtor information and corresponding to the claims processing identifier.

[0012] With this configuration, the proposal content regarding the debt settlement corresponding to the negotiation information and including the debt settlement identifier selected by the debtor can be automatically configured.

[0013] In addition, the debt management device of the fifth invention, compared to the fourth invention, is a debt management device further including a mediation support unit which 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, with respect to any one of the first to fifth inventions, further includes 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, it is possible to present the debtor with information necessary for debt settlement.

[0017] In addition, the debt management device of the seventh invention is a debt management device that, with respect to any one of the first to sixth inventions, further comprises a negotiation information output unit that outputs two or more 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 occurrence of the claim 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, with respect to any one of the first to seventh inventions, further includes 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 claims management device of the ninth invention is a claims management device according to any one of the first to eighth inventions, in which the claims status information has phase-specific information capable of identifying the current phase out of 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, and further includes an update unit which updates the phase-specific information corresponding to the claim 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.

[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. Effect of the Invention

[0023] The claims management device of the present invention can provide a platform for managing the status of claims in two or more phases from the occurrence of a claim to the time when the creditor and debtor agree on the processing of the claim, and for facilitating the processing of the claim. [Brief description of the drawings]

[0024] [Figure 1] Conceptual diagram of information system A in embodiment 1. [Diagram 2] Block diagram of Information System A [Diagram 3] Block diagram of the credit management device 1 [Figure 4] A flowchart for explaining an example of the operation of the claim management device 1. [Diagram 5] A flowchart for explaining an example of the operation of the claim management device 1. [Figure 6] A flowchart illustrating an example of a process for configuring the notification information. [Figure 7] A flowchart illustrating an example of the proposed content configuration process. [Figure 8] A flowchart illustrating an example of the agreement document generation process. [Figure 9] 11 is a flowchart illustrating an example of the output information configuration process. [Figure 10] A flowchart for explaining an example of the operation of the creditor terminal 2 [Figure 11] A flowchart for explaining 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] A diagram showing an example of the credit management table. [Figure 15] A diagram showing an example of the proposal content template [Figure 16] A diagram showing an example of the agreement document template [Figure 17] A diagram showing an example of the case registration screen [Figure 18] FIG. 13 is a diagram showing an example of the notification information. [Figure 19] FIG. 13 is a diagram showing an example of the confirmation screen. [Figure 20] FIG. 13 shows an example of the decision screen. [Figure 21] FIG. 13 is a diagram showing an example of the notification information. [Figure 22] FIG. 13 shows an example of the output screen. [Diagram 23] FIG. 13 shows an example of the installment amount change screen. [Figure 24] FIG. 13 shows an example of the output screen. [Diagram 25] FIG. 13 shows an example of the output screen. [Figure 26] A sample output of the payment schedule is shown below. [Figure 27] FIG. 13 shows an example of the output screen. [Figure 28] FIG. 13 shows an example of the output screen. [Figure 29] Block diagram of the computer system DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] Hereinafter, an embodiment of a claim management device and the like will be described with reference to the drawings. In the embodiments, components with the same reference numerals perform similar operations, so repeated description may be omitted.

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

[0027] In this embodiment, a claim management device will be described which uses application information sent by a creditor to construct notification information to be sent to a debtor, and sends the notification information to a contact address of the debtor.

[0028] In this embodiment, we will describe a claim management device that accepts access from a debtor based on notification information, receives confirmation information of the debtor's claim application, stores the confirmation information, and then stores negotiation information between the creditor and debtor in correspondence with a claim 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 a 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 having two or more options during the course of negotiation between a creditor and a debtor.

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

[0032] In this embodiment, a description will be given of a claim management device that judges whether or not an agreement condition is satisfied, and if the agreement condition is satisfied, transmits information required for claim processing to the debtor.

[0033] In this embodiment, a credit management device will be described which outputs negotiation information in a time-series manner so that the process of negotiations between a creditor and a debtor can be understood and which of the creditor and the debtor inputs the negotiation information.

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

[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 for information Z, etc., and is sufficient as long as information Z can be accessed.

[0037] 1 is a conceptual diagram of an information system A in this embodiment. The information system A comprises a claim management device 1, one or more claimant 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 is, 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 are, for example, a so-called personal computer, a smartphone, or a tablet terminal, but the type is not important.

[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 claim acquisition unit 121, a confirmation receiving unit 122, a negotiation receiving unit 123, and an instruction receiving unit 124. The processing unit 13 includes a claim 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 claim 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 comprises a debtor storage unit 31, a debtor receiving unit 32, a debtor processing unit 33, a debtor transmitting unit , a debtor receiving unit 35, and a debtor output unit .

[0045] Various types of information are stored in the storage unit 11 constituting 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 described in, for example, HTML or XML, but the implementation method is not important. Screen information corresponds to, for example, 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 are, 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 having variables. The proposal content template is a template document for configuring proposal contents, and is a document having variables. The agreement document template is a template document for configuring an agreement document, and is a document having variables.

[0049] Lawyer information is information about a lawyer who supports 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 contact information for a lawyer. 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 claim status information. The claim status information is information about claims. The claim status information is information that can specify the current phase of two or more phases from the occurrence of a claim to agreement. The claim status information may be information that can specify the current phase of two or more phases from the filing of a claim to agreement. The agreement here is an agreement between a creditor and a debtor on the processing of a claim. A claim is a right that a creditor demands a certain action from a debtor. The certain action here is usually the payment of money, but it may also be the delivery of an object, the provision of a service, etc., and the action demanded by the claim does not have to be limited. In other words, the type of claim handled here is preferably a monetary claim, but it does not matter whether it is a material claim, an action claim, etc. In addition, the phase here is a specific state or period in the progress of the processing of a claim from the occurrence of a claim to agreement or breakdown, etc. A phase may be called a step, stage, situation, etc.

[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] The creditor information is information about a creditor. The creditor information has, for example, a creditor identifier and one or more creditor attribute values. The creditor identifier is information that identifies a creditor. The creditor identifier is, 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. The creditor attribute value is, for example, the creditor's deposit information, the creditor's company name, the name of the creditor's company representative, and the creditor type indicating whether the creditor is a corporation or an individual. The deposit information is information that allows a debtor to deposit money to a creditor. The deposit information is, for example, bank account information, credit card information, and online payment information. The bank account information is information about a bank account required for bank transfer, and has, for example, the bank name, branch name, and bank account number. The credit card information is information required for depositing money using a credit card, and has, for example, a credit card number and expiration date. The online payment information is information required for depositing money using an online payment, and is, for example, an ID for online payment. The bank account information may be called account information as appropriate.

[0053] Debtor information is information about a debtor. Debtor information has, for example, a debtor identifier and one or more debtor attribute values. Debtor identifier is information that identifies a debtor. Debtor identifier is, for example, a debtor ID, a debtor name, a debtor telephone number, a debtor email address, and an IP address of the debtor terminal 3. Debtor attribute values ​​are, for example, debtor contact information, the debtor's company name, the name of the debtor company representative, the debtor's address, and a debtor type indicating whether the debtor is a corporation or an individual. Contact information is, 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. The claim content information includes, for example, the name of the claim case, the claimed amount, and the original payment due date. If the claim is a right to request the return of a lent item, the claim content information includes, for example, information on the item to be returned and information that specifies the return destination.

[0055] The confirmation information is information indicating that the debtor has confirmed the creditor's claim. The debtor's confirmation means that the debtor acknowledges that the claim is his / her own case. The confirmation information is, for example, a flag, but may be replaced by the debt status information having information that should be stored after the confirmation phase (for example, negotiation information). The confirmation information is, for example, confirmation time information. The confirmation time information is information that specifies the time when the debtor confirmed the claim. The confirmation time information is, for example, the date and time when the information was received from the debtor terminal 3. The time information that specifies the time may be the date, or the date and time, etc. The granularity of the time information is not important. The confirmation information may be information that allows the debtor to know that he / she has confirmed the claim.

[0056] Negotiation information is information regarding negotiations between a creditor and a debtor regarding the processing of a claim. 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 claim. Information that specifies the content of the negotiation 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 indicating a creditor or information indicating a debtor.

[0057] The negotiations here are negotiations to settle the debt. The negotiations are until the creditor and debtor reach an agreement regarding the settlement of the debt. The 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," "Proposal to adjust the amount," "I don't remember making the bill," "Already paid directly," "I would like 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 contents are documents that describe the matters agreed upon by both parties when processing the debt identified by the debt processing identifier. The proposal contents can be said to be information that indicates a proposal regarding the debt processing. The proposal contents are information that includes creditor information (e.g., the creditor's name) and debtor information (e.g., the debtor's name), and information that includes the content of the negotiation information (e.g., the amount for each month in installments).

[0059] An agreement document is a document that is prepared when an agreement is reached in negotiations regarding the settlement of a claim, and includes the details of the negotiations. For example, an agreement document may include 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 an agreement document may be the same as the final proposal in the negotiations.

[0060] The phase-specific information is information that can specify the current phase out of two or more phases from the occurrence of a claim until the creditor and the debtor agree on the processing of the claim. The phase that can be identified by the phase-specific information does not have to be all of the two or more phases from the occurrence of a claim until the creditor and the debtor agree on the processing of the claim. The phase-specific information is, for example, a phase identifier, but it does not have to be explicitly present in the claim status information. The phase-specific information may be information that allows the phase to be determined from the claim status information. The phase-specific information may be information that can be determined from information that the claim status information has or information that the claim status information does not have. For example, when the claim status information has the time of filing and the time of confirmation but does not have negotiation information, it can be determined that the current phase is the "negotiation" phase, so in such a case, the phase-specific information is a phase identifier that is determined from the time of filing and the time of confirmation, or the time of filing and the time of confirmation, and non-existent negotiation information.

[0061] The two or more phases from the occurrence of a claim until the creditor and the debtor agree on the processing of the claim are, for example, "filed," "awaiting confirmation," "confirmed," "negotiating," and "agreed." The "filed" phase is the phase in which the creditor files a claim against the debtor. The "awaiting confirmation" phase is the phase in which the debtor is waiting for confirmation of the claim. 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 the debtor are negotiating about the processing of the claim. The "agreed" phase is the phase in which an agreement is reached in the negotiations for the processing of the claim. The two or more phases from the occurrence of a claim until the creditor and the debtor agree on the processing of the claim do not have to include the "creation of a claim" phase and the "agreement" phase.

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

[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. The filing time information is information indicating the time when the claim was filed. The filing time information is, for example, information indicating the time when the claim acquisition unit 121 received the claim information. The negotiation time information is information indicating the time of negotiation. The negotiation time information is, for example, information indicating the time when the negotiation receiving unit 123 received the negotiation information. The agreement time information is information indicating the time when an agreement was reached. The agreement time information is, for example, information indicating the time when the judgment unit 137 judges that the agreement conditions described below have been satisfied. The claim processing completion time information is information indicating the time 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 corresponds to a credit identifier. The payment information includes, for example, a payment amount.

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

[0067] Claim information is information regarding the claim being filed. Claim information may also be considered to include information regarding claims that may be filed in the future, and claim information is understood broadly. 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.

[0068] The claim acquisition unit 121 may, for example, acquire claim time information from a clock not shown, and configure the claim information to be stored as information having the claim time information and the received claim information.

[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 normally 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 normally information indicating that the debtor has acknowledged the existence of a claim. The confirmation information received by the confirmation receiving unit 122 normally corresponds to a claim identifier. The confirmation information received by the confirmation receiving unit 122 normally corresponds to a claim identifier. The confirmation information received by the confirmation receiving unit 122 is, for example, a flag indicating that the claim for a claim has been confirmed, or a debtor identifier.

[0070] The confirmation receiving unit 122 may 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 normally receives negotiation information alternately from the creditor terminal 2 and the debtor terminal 3. Negotiations are normally negotiations for the extinguishment of a claim. The extinguishment of a claim may also be referred to as the processing of a claim. The negotiation information received by the negotiation receiving unit 123 normally corresponds to a claim identifier. The negotiation information received by the negotiation receiving unit 123 normally corresponds to 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 that is a debtor's proposal including the start month and each month's payment amount when making installment payments for debt settlement from the debtor terminal 2 or the debtor terminal 3.

[0073] The negotiation receiving unit 123 receives, for example, negotiation information including a proposal for amending 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 the invoice" and "information to the effect that the debtor has already paid the invoice 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 bond status information of the bond management unit 111. The output instruction corresponds to a bond identifier. The output instruction has, for example, a bond identifier. The instruction to output the bond status information may be considered to include an instruction to output part of the bond 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 claim 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 claim management unit 111 in association with the claim 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 claim management unit 111. The processing unit 13 acquires an agreement document according to the received agreement document instruction from the claim management unit 111. The processing unit 13 acquires a payment schedule according to the received payment schedule instruction from the claim management unit 111.

[0082] The claim storage unit 131 stores the claim information acquired by the claim acquisition unit 121 in the claim management unit 111 in association with the claim identifier. The stored claim information constitutes the claim status information of the claim management unit 111.

[0083] For example, when the information acquisition unit 139 receives claim information from the creditor terminal 2, the claim accumulation unit 131 generates a unique claim identifier and accumulates the claim 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 claim accumulation unit 131 acquires a unique numeric value 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 usually accumulates information indicating that the current phase is the phase "waiting for confirmation" in the claim management unit 111. The update unit 132 may accumulate the notification information in the claim management unit 111 in association with the claim identifier, or may accumulate a flag indicating that the notification information has been sent in the claim management unit 111 in association with the claim identifier. The update unit 132 may perform a process for identifying that the phase has progressed as a result of the notification information being sent. Such a process may be replaced by a process in which the claim accumulation unit 131 accumulates 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 phase "waiting for confirmation".

[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 phase "under negotiation" 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 confirmation identifier, or may accumulate a flag indicating that the confirmation information has been received in the bond management unit 111 in association with the bond identifier. The update unit 132 may perform a process for identifying that the phase has progressed as a result of the confirmation information being received. Such a process may be replaced by a process 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 phase "under negotiation".

[0086] In response to confirmation receiving unit 122 receiving confirmation information, confirmation accumulation unit 133 acquires the confirmation information to be accumulated, associates the confirmation information with the claim identifier, and accumulates it in claim management unit 111. For example, confirmation accumulation unit 133 acquires confirmation time information, which is time information, from a clock not shown, and accumulates confirmation information including the confirmation time information in claim management unit 111 by associating it with the claim identifier. Note that the accumulated confirmation information may be confirmation time information. In other words, the received confirmation information and the accumulated confirmation information may be different information. The confirmation information may be any 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 in correspondence 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 obtain negotiation time information from a clock (not shown) and accumulate the negotiation information including the negotiation time information. When the negotiation receiving unit 123 receives negotiation information, the negotiation accumulation unit 134 may obtain an inputter identifier that specifies whether the person who transmitted the negotiation information is a creditor or a debtor, and accumulate the negotiation information including the inputter identifier.

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

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

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

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

[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 a creditor and a debtor to conduct mediation online. It is preferable that the group includes a lawyer. The mediation support process is, for example, a process of transmitting 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 or not the agreed conditions are satisfied.

[0096] The agreed condition is a condition for judging whether negotiations regarding the debt settlement have been concluded. For example, the agreed condition is that the received negotiation information includes a debt settlement identifier indicating a specific method among two or more debt settlement methods (a specific debt settlement identifier has been selected). For example, the specific debt settlement identifier is the debt settlement identifier "pay now by credit card" or "pay in full at the end of the next month" among the debt settlement identifiers "pay by credit card now", "pay in full at the end of the next month", "pay in installments at the end of each month", "suggestion to revise the amount", "no recollection of the bill", "already paid directly", and "request online mediation". For example, the agreed condition is that the received negotiation information includes a payment instrument identifier. For example, the agreed condition is that negotiation information indicating that the debtor has agreed to the negotiation information transmitted from the creditor has been received. For example, the agreed condition is that negotiation information indicating that the debtor has agreed to the negotiation information transmitted 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 reception unit 123 satisfies the agreement conditions. It is preferable that the agreement document generation unit 138 stores the generated agreement document in the claim management unit 111 in a pair with a claim identifier.

[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 a 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, a 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 transmission unit 14 transmits various types of information, such as notification information, screen information, proposal content, negotiation information, necessary information, and an agreement document, which will be described later.

[0101] In response to the application acquisition unit 121 acquiring 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 debt content information, and transmits the notification information to the debtor. The information may be transmitted in a push-type or pull-type manner.

[0102] When a transmission condition for transmitting specific screen information is satisfied, 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 for allowing the debtor to select one of two or more methods of debt processing to the debtor terminal 3. For example, when the screen transmitting unit 142 receives a selection of a selection object from the creditor terminal 2 or the debtor terminal 3, it transmits screen information corresponding to the selection 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 on which the proposal content is based 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 the negotiation receiving unit 123 received them, and in a manner that makes it possible to know 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 to which the creditor identifier corresponds is aligned to the right or left of the screen, and screen information in which the negotiation information to which the debtor identifier corresponds 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 judgment unit 137 judges that the agreement conditions are satisfied, the necessary information transmission unit 145 transmits necessary information, which is information necessary for the debtor to carry out debt processing, to the debtor. The necessary information usually includes payee information. 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 loaned goods and information indicating the location where the service is to be enjoyed.

[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, a 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 a part or all of the debt status information to the creditor terminal 2 or the debtor terminal 3 that has transmitted an output instruction. The information transmitting unit 147 transmits, for example, the proposal contents, the agreement document, or the payment schedule to the creditor terminal 2 or the debtor terminal 3 that has transmitted a proposal contents instruction, an agreement document instruction, or a payment schedule instruction.

[0110] Various types of information are stored in the creditor storage unit 21 constituting the creditor terminal 2. The various types of information are, for example, creditor identifiers.

[0111] The creditor reception unit 22 receives various information, instructions, etc. Examples of the various 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, a keyboard, a mouse, or a menu screen.

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

[0114] The creditor transmission 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 information from, for example, confirmation information, negotiation information, credit status information, and various 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 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 handing over the processing results to other processing devices or other programs.

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

[0119] The debtor receiving unit 32 receives various information, instructions, etc. Examples of the various 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, a keyboard, a mouse, or a menu screen.

[0121] The debtor processing unit 33 performs various types of processing. For example, the various types of processing are processing for converting received information, instructions, etc. into information or instructions with a structure to be sent. For example, the various types of processing are processing for converting 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 using 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 inputted 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 for receiving broadcasts, etc.

[0128] The processing unit 13, the application 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 usually be realized by a processor, a memory, etc. The processing procedure of the processing unit 13, etc. is usually realized by software, and the software is recorded in a recording medium such as a ROM. However, it may be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter. The application acquisition unit 121 may be realized by a processor, a memory, etc., like the processing unit 13.

[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 receiving unit 22 and the debtor receiving unit 32 can be realized by device drivers for 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 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 judges 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 configures the claim information to be accumulated as information having the claim information and the claim time information.

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

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

[0137] (Step S405) The request notification unit 141 composes notification information. An example of the process of compiling 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 specified by the contact information acquired in step S406. Return to step S401.

[0140] (Step S408) The confirmation receiving unit 122 judges whether or not confirmation information, etc. has been received from the debtor terminal 3. If confirmation information, etc. has been received, the process proceeds to step S409, and 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 or the like.

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

[0143] (Step S411) The negotiation receiving unit 123 judges whether or not 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, and if negotiation information has not been received, the process proceeds to step S423. The received negotiation information corresponds to a credit identifier.

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

[0145] (Step S413) The negotiation accumulation unit 134 accumulates the negotiation information in the bond management unit 111 in association with the bond identifier. 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 judges whether the received negotiation information matches the proposal content creation conditions. If the proposal content creation conditions are met, the process proceeds to step S415. If the proposal content creation conditions are not met, the process proceeds to step S417.

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

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

[0149] (Step S417) The judgment unit 137 judges 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 generating unit 138 generates an agreement document. An example of such an agreement document generating process will be described with reference to the flowchart of FIG.

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

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

[0153] (Step S421) The processing unit 13 judges 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 judges 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, and if not, the process proceeds to step S428. The output instruction corresponds to the 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 debt 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 judges 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, and 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 judges 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, and if not, the process proceeds to step S434. The agreement document instruction corresponds to the 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 judges 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, and if not, the process proceeds to step S437. The payment schedule instruction corresponds to the credit identifier.

[0167] (Step S435) The information acquisition unit 139 acquires a 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 judges whether or not payment information has been received. If payment information has been received, the process proceeds to step S438. If payment information has not been received, 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. The process returns to step S401.

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

[0172] The transmission condition is, for example, receipt of confirmation information or specific negotiation information, or receipt of a screen output instruction from the creditor terminal 2 or the debtor terminal 3. The transmission condition is 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 FIG. 4 and FIG. 5, the process ends when the power is turned off or an interrupt is issued to end the process.

[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 request 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 on the creditor that is paired 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 claim identifier.

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

[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 may be any information for accessing the claim content information.

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

[0184] Next, an example of the proposal content structuring 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 a bond identifier corresponding to 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 judges whether or not 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 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 assigns the information acquired in step S705 to 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 a bond identifier corresponding to the received negotiation information.

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

[0197] (Step S804) The agreement document generation unit 138 judges whether or not 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, and if not, the process returns to the upper 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 generating 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 acquiring unit 139 acquires, from the storage unit 11, screen information that is the basis for constructing output information.

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

[0204] (Step S903) The information acquisition unit 139 judges 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, the debtor name, the payment amount, the payment start date, and the payment due date.

[0206] (Step S905) The information acquiring unit 139 assigns the information acquired in step S904 to the i-th variable in the screen information.

[0207] (Step S906) The information acquiring 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 name of the creditor.

[0209] (Step S908) The information acquisition unit 139 judges 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, and 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 is, 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 acquiring unit 139 assigns 1 to a counter i.

[0212] (Step S911) The information acquisition unit 139 judges whether or not 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, and if not, the process proceeds to step S919.

[0213] (Step S912) The information acquisition unit 139 acquires the creditor identifier or debtor identifier that is paired with the i-th negotiation information from the credit status information that is paired with the credit identifier. Note that the creditor identifier or debtor identifier is appropriately called the identifier.

[0214] (Step S913) The information acquisition unit 139 judges 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 configure 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 acquiring unit 139 increments the counter i by 1. The process returns to step S911.

[0219] (Step S918) The information acquisition unit 139 judges 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 that is paired with the bond identifier. The necessary information is usually deposit destination information.

[0221] (Step S920) The information acquiring unit 139 arranges the necessary information in the screen information, and then 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 transmitting 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 reception 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 a credit identifier. The creditor transmitting unit 24 transmits the output instruction received in step S1003 to the credit management device 1 in association with the credit 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. Return 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 a credit identifier. The creditor transmission unit 24 transmits the negotiation information received in step S1007 in association with the credit identifier to the credit management device 1. The process returns to step S1001.

[0231] (Step S1009) The creditor reception unit 22 judges 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 for identifying the screen information.

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

[0233] (Step S1011) The creditor receiving unit 25 judges 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. Return to step S1001.

[0235] (Step S1013) The creditor receiving unit 22 judges 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 a credit identifier. The creditor transmission unit 24 transmits the instruction received in step S1013 to the credit management device 1 in association with the credit 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. Return to step S1001.

[0239] In the flowchart of FIG. 10, the process ends when the power is turned off or an interrupt is issued 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 judges 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. Note that 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 judges 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 claim identifier associated with the notification information. The debtor transmitting unit 34 transmits the confirmation information, etc., in association with the claim identifier, to the claim management device 1. Return to step S1101.

[0245] (Step S1105) The debtor receiving unit 32 judges 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 a bond identifier associated with the screen on which the output instruction is input. The debtor transmitting unit 34 transmits the output instruction to the debt management device 1 in association with the bond identifier.

[0247] (Step S1107) The debtor receiving unit 35 judges 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. Return to step S1101.

[0249] (Step S1109) The debtor reception 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. If the negotiation information has not been received, the process proceeds to step S1111.

[0250] (Step S1110) The debtor processing unit 33 acquires a claim 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 claim management device 1 in association with the claim identifier. Return to step S1101.

[0251] (Step S1111) The debtor receiving unit 32 judges 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 a 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 judges whether or not screen information has been received from the debt management device 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. Return to step S1101.

[0255] (Step S1115) The debtor receiving unit 32 judges 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 accepted in step S1115 to the bond 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 not, 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. Return 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. 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 when a claim arises until the creditor and debtor agree on claim processing and the claim processing is completed. In FIG. 12, the phases progress in the order of "filed", "waiting for confirmation", "confirmed", "negotiating", "claim processing in progress", and "claim processing completed". In addition, it is assumed that "negotiating" may transition to "online mediation in progress". In addition, it is assumed that the phase progresses from "online mediation in progress" to "claim processing in progress" or "negotiation failure". The numbers above the character strings indicating each phase in FIG. 12 are phase identifiers that identify the phase. In other words, the phase identifier for the phase "filed" is "1", "waiting for confirmation" is "2", "confirmed" is "3", "negotiating" is "4", "claim processing in progress" is "5", "claim processing completed" is "6", "online mediation in progress" is "7", and "negotiation failure" is "8". It should be noted that "debt being processed" refers to, for example, the stage of a payment being made in multiple installments.

[0261] The storage unit 11 of the debt management device 1 stores a creditor management table shown in FIG. 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. "Payment destination information" is, for example, bank account information.

[0262] The claims management section 111 of the claims management device 1 stores a claims management table having the structure shown in FIG. 14. The claims management table is a table that manages claims 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", "negotiation time", "proposal content", and "agreement document". "Claims information" has "claim content information", "creditor identifier", "debtor information", and "claim time". "Confirmation information" has "confirmation time". "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. For example, the payment method identifier is "A" for credit card payment and "B" for bank transfer.

[0264] The storage unit 11 of the debt management device 1 stores a proposed 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 proposed content template and the agreement document template, character strings enclosed in "<" and ">" are variables. Information is substituted for the variables to form the proposed 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 credit management device 1, uses the creditor terminal 2 to log in to the credit management device 1.

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

[0267] Next, Tanaka A enters information into each field of the screen in FIG. 17, such as “petition case name,” “petition amount,” and “payment date of the main body,” and selects the “file” button 1701 .

[0268] Next, the creditor reception unit 22 of the creditor terminal 2 accepts the case registration in response to the instruction of the button 1701. The case registration has the claim information "<Case name>X Company Non-payment <Claim amount>100,000 <Payment date of main body>2924 / 8 / 1 <Creditor identifier>C01···<Other party's name>X Company···<Other party's 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 configures the claim information to be stored as "<Claim Case Name>X Company Non-Payment <Claim Amount>100,000 <Payment Date of Main Body>2924 / 8 / 1 <Creditor Identifier>C01 ··· <Other Party Name>X Company ···<Other Party 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 configured claim information with the claim identifier "1" and accumulates it in the claim management table (FIG. 14). This claim information is the claim information of "ID=1" in Fig. 14. Furthermore, the update unit 132 stores the phase identifier "1" in the record of "ID=1" in Fig. 14.

[0270] Next, the claim notification unit 141 of the claim management device 1 configures the notification information as follows. First, the claim notification unit 141 configures the notification information of FIG. 18 according to the operation of the notification information configuration process described using the flowchart of FIG. 6. The claim notification unit 141 configures 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 claim notification unit 141 obtains the debtor's contact information "yy@x.jp" from the claim information. Next, the claim notification unit 141 transmits the notification information (FIG. 18) to the contact specified by the contact information. The update unit 132 also 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 device 1. Note that there is no restriction on the trigger for outputting the notification information in the debtor terminal 3.

[0272] Next, assume that "Yamada Y", a person in charge at Company X, sees the notification information (Fig. 18) and clicks on URL 1801. Next, the debtor terminal 3 acquires screen information including the claim information corresponding to URL 1801 from the claim management device 1, and outputs a confirmation screen (Fig. 19) based on the screen information. The confirmation screen is a screen for the debtor to confirm the claim. Next, assume that Yamada Y looks at the confirmation screen, checks the check box 1901 "This is a claim against me", and selects the "Next" button 1902. Then, the debtor reception unit 32 of the debtor terminal 3 accepts the confirmation information. Next, the debtor processing unit 33 acquires the claim identifier "1" corresponding to the screen information. Next, the debtor processing unit 33 composes the confirmation information "<Confirmation result>Confirmation <Claims identifier>1" to be transmitted. 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, for example, "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 storage unit 133 acquires the received claims identifier "1". Next, the confirmation storage 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 storage 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 matches the transmission conditions from the storage unit 11. Such screen information is screen information for constituting a decision screen. The decision screen is a screen for deciding the 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 so far, and buttons 2002 corresponding to each of the seven debt settlement identifier candidates.

[0276] Then, suppose that Yamada Y selects button 2003 from FIG. 20. Also suppose that Yamada Y inputs the inquired installment amount "5000 yen" by pressing button 2003. The debtor receiving unit 32 of the debtor terminal 3 then receives the negotiation information "<debt processing identifier>3 <installment 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 <installment amount>5000". Next, the debtor transmitting unit 34 transmits the negotiation information to the debt management device 1.

[0277] Next, the negotiation receiving unit 123 of the claim management device 1 receives the negotiation information from the debtor terminal 3. Next, the negotiation accumulation unit 134 acquires the claim 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 claim processing identifier is "3" (installment payment), acquires the claim amount "100,000 yen" and the installment amount "5,000 yen" that are paired with the claim identifier "1", acquires the payment start date, payment end date, and payment amount for each month (acquires the payment schedule), and accumulates them in a pair with the claim 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. The proposal content acquisition unit 135 then composes the proposal content by the process described using the flowchart in FIG. 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 (FIG. 14). The 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 compose notification information to be sent to the creditor. Such notification information is information for notifying the debtor of the debtor's proposal. Next, the transmission unit 14 transmits 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, the creditor's terminal 2 of creditor Tanaka A receives the notification information and outputs it. Such notification information is shown in Fig. 21. Fig. 21 shows notification information in which the creditor's name, the installment amount, and link information 2101 for accessing negotiation information are placed in the variable portion of the notification information template. It is then assumed that Tanaka A has designated the URL 2101 in Fig. 21.

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

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

[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 transmitting unit 147 transmits the screen information to the creditor terminal 2 of Tanaka A-san.

[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 inputs the proposed new installment amount "20,000 yen" on the screen in Fig. 23 (2301 in Fig. 23).

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

[0286] Next, the receiving unit 12 of the claim management device 1 receives the negotiation information including the installment amount "20,000 yen" in combination with the claim 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 composition process explained using the flowchart in Fig. 7, and substitutes the said installment amount "20,000 yen" and the creditor name, debtor name, and claim amount that pair with the claim identifier "1" into the said proposal content template to compose the proposal content. Next, the transmission unit 14 transmits the said 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] 23, "Propose change to installment amount" button 2303. The creditor terminal 2 then accepts the instruction to the button 203. The creditor terminal 2 then creates negotiation information "<obligation identifier>1 <installment amount>20,000 yen <obligation identifier>C01" and transmits it to the obligation management device 1.

[0291] Next, the negotiation receiving unit 123 of the claim management device 1 receives the negotiation information. Next, the negotiation storage unit 134 acquires the claim identifier "1" contained in the negotiation information. Also, it is assumed that the negotiation storage unit 134 acquires time information "2024 / 8 / 11 16:34" from a clock not shown. The negotiation storage unit 134 also acquires the claim amount "100,000 yen" and installment amount "20,000 yen" that are paired with the claim 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 claim identifier "1". Note that the payment schedule is accumulated in FIG. 14, but is not shown.

[0292] Next, the proposal content acquisition unit 135 acquires the proposal content previously acquired. Next, the proposal content acquisition unit 135 associates the proposal content with the negotiation information (file "P2") and accumulates it in the claim 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 satisfied. 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 the debtor terminal 3 of Yamada Y.

[0294] Next, the debtor terminal 3 receives the screen information and outputs the screen of FIG. 24. Then, assume that Yamada Y presses 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 claim management device 1 receives the negotiation information. The negotiation accumulation unit 134 acquires the claim identifier "1". The negotiation accumulation unit 134 acquires the current time, the time of agreement "2024 / 8 / 11 16:39", from a clock (not shown). Next, the negotiation accumulation unit 134 accumulates the negotiation information "Agreement" and the time of agreement in association with the claim 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 Fig. 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 (Fig. 14).

[0297] Next, the information acquisition unit 139 acquires screen information corresponding to the negotiation information "<obligation identifier> 1 <negotiation result> agreed <installment amount> 20000 <obligor identifier> X Company" in response to the instruction of the debtor (Yamada Y)'s button 2401 (FIG. 24), which is to be sent to the creditor. Next, the information transmission unit 147 transmits the screen information to the creditor terminal 2.

[0298] In addition, the information acquisition unit 139 acquires screen information for the debtor to determine the debt processing identifier in response to the instruction of 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, suppose that Tanaka A clicks the "Check payment schedule" button 2501 on the screen in Fig. 25. The creditor terminal 2 then accepts the instruction, obtains from the credit management device 1 the payment schedule that corresponds to the instruction and that is paired with the credit identifier "1", and outputs it. An example of such a payment schedule output is shown in Fig. 26.

[0301] Moreover, 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, it is assumed that Yamada Y clicks on 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 debt processing identifier "A" is "payment by credit card" and "B" is "payment by bank transfer." Next, the debtor terminal 3 sends the debt processing identifier "B" to the debt management device 1, pairing it with the debt identifier "1."

[0304] Next, the claim management device 1 receives the claim processing identifier "B" and the like, pairs it with the claim identifier "1," and stores the claim processing identifier "B" in the claim management table (Fig. 14). Note that as a result of this processing, the claim processing identifier "3,B" is stored in the record of "ID=1" in the claim 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 (FIG. 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 constructs screen information including 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, a platform can be provided that manages the status of a claim in two or more phases out of 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, and promotes the processing of the claim.

[0309] Furthermore, according to this embodiment, the contents of a proposal regarding debt processing according to the negotiation information can be automatically constructed.

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

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

[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] In addition, according to this embodiment, a platform can be provided that manages the status of a claim in two or more phases out of two or more phases from the filing of a claim to the time when the creditor and debtor agree on the processing of the claim, and 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 a program such as the following.In other words, this program includes a computer that can access a claim management unit that stores one or more claim status information that is information regarding claim processing, 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 the debtor agree on the claim processing, a claim acquisition unit that 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 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 corresponding to the claim information, a claim notification unit that acquires notification information including information on the creditor identified by the creditor identifier contained in the claim information and the claim content information in response to the claim acquisition unit acquiring the claim information, and transmits the notification information to the debtor, and receives confirmation information regarding confirmation of the claim of the claim from the debtor terminal of the debtor. The program has a confirmation receiving unit, a confirmation storage unit which 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 correspondence with the debt identifier, a negotiation receiving unit which 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 which stores the negotiation information received by the negotiation receiving unit in the debt management unit in correspondence with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and the debt identifier, an instruction receiving unit which receives an instruction to output debt status information from the creditor terminal or the debtor terminal, an information acquisition unit which acquires part or all of the debt status information corresponding to the output instruction from the debt management unit, and an information transmission unit which transmits 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 for causing computer system 300 to execute functions such as those of the claim management device 1 of the above-mentioned 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 transmitted 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-mentioned embodiment. The program only needs to include an instruction portion that calls appropriate functions (modules) in a controlled manner and achieves 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 transmitting step (processing that is performed only by hardware).

[0323] The program may be executed by a single computer or a plurality of computers, that is, centralized processing or distributed processing may be performed.

[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] 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 claims management device 1 of the present invention has the effect of managing the status of a claim in two or more phases out of two or more phases from the occurrence of a claim to the time when the creditor and debtor agree on the claim processing, and can provide a platform for facilitating the processing of claims, and is useful as a server or the like for managing claims. [Explanation of symbols]

[0328] A. Information Systems 1. Credit 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 Creditors Receiving 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 Petitions and Acquisitions Division 122 Confirmation Receiving Department 123 Negotiation Reception Department 124 Instruction receiving unit 131 Complaint Accumulation Division 132 Update Department 133 Confirmation storage unit 134 Negotiations Storage Department 135 Proposal content acquisition section 136 Mediation Support Department 137 Judgment Department 138 Agreement document 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 having 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 a claim management unit in which one or more claim status information pieces corresponding to a claim identifier that identifies a claim and that can identify a current phase among two or more phases from the occurrence of a claim until an agreement is reached between a creditor and a debtor on the processing of the claim are stored, in association with the claim identifier that identifies the claim that corresponds to the claim information; a claim notification unit which, 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 information on the claim content, and transmits the notification information to the debtor; a confirmation receiving unit for receiving confirmation information regarding the 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, after the confirmation receiving unit receives the confirmation information, negotiation information regarding negotiation between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor; 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 for receiving an instruction to output credit status information from the creditor terminal or the debtor terminal; an information acquisition unit that acquires a part or all of the credit status information corresponding to the output instruction from the credit management unit; a information transmitting section for transmitting a part or all of the claim status information acquired by the information acquiring section 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 creditor information and the debtor information, information including the content of the negotiation information, and information indicating a proposal regarding the processing of the debt; 2. A claim 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 claim management device according to claim 2, wherein the proposal content is transmitted so that the negotiation information received by the negotiation receiving unit corresponds to the proposal content acquired by the proposal content acquiring unit.

4. a screen sending unit that sends screen information to the debtor terminal for allowing 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 claim management device as described in claim 2, which obtains the creditor information and the debtor information from the claim management section, and obtains the proposal content, which is information including the creditor information and the debtor information and corresponds to the claim processing identifier.

5. The debt management device as described in claim 4, further comprising a mediation support unit which, when the negotiation receiving unit receives the negotiation information including the debt settlement identifier indicating online mediation from the debtor terminal, performs a mediation support process 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 to the debtor necessary information, which is information necessary for the debtor to process debt when the judgment unit determines that the agreement conditions are met.

7. The debt management device of claim 1 further comprises a negotiation information output unit which outputs the two or more negotiation information received by the negotiation receiving unit in the order in which the negotiation information was received by the negotiation receiving unit and in a manner which 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 claim 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 capable of specifying 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 claim 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 claim 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 storing one or more pieces of claim status information relating to claim processing, the information being associated with a claim identifier that identifies the claim, and capable of identifying a 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 method comprising: 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 for identifying a creditor, a debtor identifier for identifying a debtor, and debt content information relating to the content of the debt; a claim storage step in which the claim storage unit stores the claim information acquired by the claim acquisition unit in the claim management unit in association with a claim identifier that identifies a claim corresponding to the claim information; a claim notification step in which the claim notification unit, 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 step in which the confirmation receiving unit receives confirmation information regarding confirmation of the claim from the debtor terminal of the debtor; a confirmation storage step in which the confirmation storage unit 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 step of receiving, by the negotiation receiving unit, negotiation information regarding negotiation between the creditor and the debtor from a creditor terminal of the creditor and a debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation storage step in which the negotiation storage unit 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 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 a part or all of the claim status information corresponding to the output instruction from the claim management unit; and an information transmitting step in which the information transmitting unit transmits a part or all of the claim status information acquired by the information acquiring unit to the creditor terminal or the debtor terminal.

11. a computer that can access a claims management section that stores one or more pieces of claim status information that is information related to claims 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 when the claim is generated until the creditor and the debtor agree on the processing of the claim; a claim acquisition unit that acquires claim information having 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 a claim corresponding to the claim information; a claim notification unit which, 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 information on the claim content, and transmits the notification information to the debtor; a confirmation receiving unit for receiving confirmation information regarding the 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, after the confirmation receiving unit receives the confirmation information, negotiation information regarding negotiation between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor; 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 for receiving an instruction to output credit status information from the creditor terminal or the debtor terminal; an information acquisition unit that acquires a part or all of the credit status information corresponding to the output instruction from the credit management unit; A program for causing the information acquisition unit to function as an information transmission unit that transmits a part or all of the debt status information acquired by the information acquisition unit to the creditor terminal or the debtor terminal.

Images