Claim management device, claim management method, and program

Abstract

[Problem] There is no platform in the prior art for managing the status of a claim in two or more phases among two or more phases from the occurrence of the claim to an agreement between the creditor and the debtor upon the processing of the claim, and for promoting the processing of the claim. [Solution] The present invention can solve the above-mentioned problem by providing a claim management device 1 which comprises: a petition acquisition unit 121 that acquires petition information for a claim; a petition storage unit 131 that stores the petition information; a petition notification unit 141 that transmits notification information for the claim to a debtor; a confirmation reception unit 122 that receives confirmation information for the claim petition from the debtor; a confirmation storage unit 133 that stores the confirmation information in association with a claim identifier; a negotiation reception unit 123 that receives negotiation information; a negotiation storage unit 134 that stores the negotiation information; an instruction reception unit 124 that receives an instruction for outputting claim status information; and an information transmission unit 147 that transmits the claim status information according to the output instruction.

Description

Debt management device, debt management method, and program

[0001] The present invention relates to a claim management device that supports activities for claim processing. The present invention also relates to a negotiation support device that supports negotiations regarding claims submitted by claimants. The present invention particularly relates to a negotiation support device that supports activities for claim processing.

[0002] In this context, a petition refers to the resolution of various disputes, including, for example, the processing of debts. A petition is usually a petition made by a petitioner against a respondent. The petitioner is the person making the petition. The respondent is the person against whom the petition is made. A petition may be any matter that is the subject of negotiation. Various disputes include, for example, disputes regarding the eviction of a building, disputes regarding increases in building rent, negotiations regarding retirement benefits, disputes regarding retirement conditions, disputes regarding the repayment of loaned money, and disputes regarding unpaid fees for services provided. Disputes can also be called disputes, disputes, etc.

[0003] Previously, there was a system that allowed card issuers or other electronic payment providers to obtain a quick, desirable, and efficient resolution of customer disputes with merchants (see US Pat. No. 6,233,999).

[0004] Special Publication No. 2015-535365

[0005] However, in the prior art, there was no 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.

[0006] Furthermore, in the prior art, when a claim for a debt is accepted, it is not possible to automatically set up a bank account for the collection of the debt.

[0007] Furthermore, in the prior art, it was not possible to automatically determine the accounting information for which a claim should be filed from the accounting information stored in the accounting management department.

[0008] Furthermore, until now, there has been no platform that supports activities for processing receivables at multiple stages.

[0009] The claims management device of the first invention comprises a claims management unit that stores one or more claims status information pieces that are 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 the occurrence of the claim until the creditor and the debtor agree on the processing of the claim; a claim acquisition unit that acquires claim information that has a creditor identifier that identifies the creditor, a debtor identifier that identifies the debtor, and claim content information related to the content of the claim; a claim storage unit that stores the claim information acquired by the claim acquisition unit in the claims management unit in association with the claim identifier; a claim notification unit that, in response to the acquisition of the claim information by the claim acquisition unit, acquires notification information that includes information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and transmits the notification information to the debtor; and a claim notification unit that receives confirmation information related to the confirmation of the claim from the debtor terminal of the debtor. a confirmation receiving unit that receives the confirmation information, a confirmation storage unit that acquires the confirmation information to be stored in response to the confirmation receiving unit receiving the confirmation information, and stores the confirmation information in the claim management unit in association with a claim identifier; a negotiation receiving unit that receives negotiation information for extinguishing a claim from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation storage unit that stores the negotiation information received by the negotiation receiving unit in the claim management unit in association with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and a claim identifier; an instruction receiving unit that receives an instruction to output claim status information from the creditor terminal or debtor terminal; an information acquisition unit that acquires part or all of the claim status information corresponding to the output instruction from the claim management unit; and an information sending unit that sends part or all of the claim status information acquired by the information acquisition unit to the creditor terminal or debtor terminal.

[0010] This configuration provides 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.

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

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

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

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

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

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

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

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

[0019] In addition, the debt management device of the sixth invention is a debt management device that, compared to any one of the first to fifth inventions, further comprises a judgment unit that judges whether the agreed 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 agreed conditions have been met.

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

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

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

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

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

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

[0026] This configuration provides 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.

[0027] The claims management device of the present invention is a claims management device comprising: a claims management unit that stores one or more pieces of claim status information, which is information associated with a claim identifier that identifies a claim and can identify the current phase out of two or more phases from the time the claim is generated until the creditor and debtor agree on the processing of the claim; a claim acquisition unit that acquires claim information having a creditor identifier that identifies the creditor, a debtor identifier that identifies the 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 claims management unit in association with the claim identifier; an account creation unit that generates a virtual bank account in association with the claim identifier and acquires account information that identifies the virtual account; an account storage unit that stores the account information acquired by the account creation unit in the claims management unit in association with the claim identifier; an account transmission unit that transmits the account information to the debtor; an instruction receiving unit that receives an instruction to output claim status information from a creditor terminal or debtor terminal; an information acquisition unit that acquires part or all of the claim status information corresponding to the output instruction from the claims management unit; and an information transmission unit that transmits part or all of the claim status information acquired by the information acquisition unit to the creditor terminal or debtor terminal.

[0028] With this configuration, when a claim for a debt is accepted, a bank account can be automatically set up for the collection of the debt.

[0029] In addition, the claims management device of the present invention is a claim management device that, in addition to the above-mentioned invention, further comprises an application notification unit that, in response to the application acquisition unit acquiring application information, acquires notification information including creditor information identified by the creditor identifier contained in the application information and claim content information, and sends the notification information to the debtor; a confirmation receiving unit that receives confirmation information regarding confirmation of the claim application from the debtor terminal of the debtor; and a confirmation storage unit that, in response to the confirmation information received by the confirmation receiving unit, acquires confirmation information to be stored, associates the confirmation information with the claim identifier, and stores the confirmation information in the claims management unit.

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

[0031] In addition, the debt management device of the present invention is a debt management device that, compared to the above invention, further comprises a negotiation receiving unit that receives negotiation information for extinguishing the debt from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information, and a negotiation storage unit that 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 a debt identifier.

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

[0033] In addition, the receivables management device of the present invention, compared to the above invention, further includes a judgment unit that judges whether the information received from the creditor terminal or debtor terminal matches the account conditions, which are the conditions for obtaining account information, and the account generation unit is a receivables management device that obtains account information that identifies a virtual account when the judgment unit determines that the account conditions are met.

[0034] With this configuration, a bank account can be automatically established only if the account conditions are met.

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

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

[0037] In addition, the debt management device of the present invention is a debt management device in which, compared to the above 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.

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

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

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

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

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

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

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

[0045] In addition, the receivables management device of the present invention is a receivables management device that, compared to the above invention, further comprises a negotiation information output unit that outputs two or more pieces of negotiation information received by the negotiation receiving unit in the order in which they were received by the negotiation receiving unit, and in a manner that makes it possible to understand whether the identifier to which the negotiation information corresponds is a creditor identifier or a debtor identifier.

[0046] This configuration makes it possible to provide a platform that manages the status of a claim in two or more phases among two or more phases from the occurrence of a claim to the processing of the claim, and promotes the processing of the claim.

[0047] In addition, the debt management device of the present invention is a debt management device that, compared to the above invention, further comprises an agreement document generation unit that generates an agreement document using the negotiation information when the negotiation information received by the negotiation receiving unit satisfies the agreement conditions, and an agreement document output unit that outputs the agreement document generated by the agreement document generation unit.

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

[0049] In addition, compared to the above invention, the debt management device of the present invention is a debt management device in which the debt status information has phase identification information that can identify the current phase out of two or more phases from the occurrence of the debt to the processing of the debt, and further includes an update unit that updates the phase identification information corresponding to the debt identifier in response to the application notification unit sending notification information to the debtor and in response to the confirmation receiving unit receiving confirmation information.

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

[0051] The claims management device of the present invention is a claims management device that includes: a claims management unit that stores one or more pieces of claim status information that is information associated with a claim identifier that identifies a claim and that can identify the current phase out of two or more phases from the time the claim is generated until the creditor and debtor agree on the processing of the claim; a determination unit that determines accounting information that meets the claim conditions from the accounting management unit that stores one or more pieces of accounting information that have a billing destination identifier that identifies the billing destination, a billing amount, and date information that identifies the date related to the billing; a claim acquisition unit that uses the accounting information determined by the determination unit to acquire claim information that has a creditor identifier that identifies the creditor, a debtor identifier that identifies the debtor, and claim content information related to the content of the claim; a claim storage unit that stores the claim information acquired by the claim acquisition unit in the claims management unit in association with the claim identifier; an instruction receiving unit that receives an instruction to output claim status information from a creditor terminal or debtor terminal; an information acquisition unit that acquires part or all of the claim status information corresponding to the output instruction from the claims management unit; and an information sending unit that transmits part or all of the claim status information acquired by the information acquisition unit to the creditor terminal or debtor terminal.

[0052] With this configuration, the accounting information for which a claim should be filed can be automatically determined from the accounting information stored in the accounting management department.

[0053] In addition, the receivables management device of the present invention, compared to the above invention, further comprises a user management unit in which two or more pieces of user information having application conditions corresponding to creditor identifiers are stored, and the determination unit is a receivables management device that determines accounting information that meets the application conditions corresponding to the creditor identifiers from one or more pieces of accounting information corresponding to the creditor identifiers.

[0054] With this configuration, the accounting information for claiming a claim can be automatically determined from the accounting information stored in the accounting management department according to conditions that differ for each creditor.

[0055] In addition, the receivables management device of the present invention is a receivables management device that, in contrast to the above invention, is equipped with a payment receiving unit that receives payment information indicating payment from a debtor for a receivable, and a payment storage unit that, when the payment receiving unit receives the payment information, stores payment-related information in the accounting management unit indicating that a payment corresponding to the payment information has been made.

[0056] With this configuration, when a debtor makes a payment for a receivable, information about the payment can be accumulated and managed in the accounting management department.

[0057] In addition, the receivables management device of the present invention, compared to the above invention, further comprises an access management unit in which access information for accessing an accounting management device having an accounting management unit is stored, corresponding to each of two or more creditor identifiers, and the determination unit is a receivables management device that uses the access information corresponding to the creditor identifiers to access the accounting management device and determine accounting information that meets the application conditions corresponding to the creditor identifiers.

[0058] With this configuration, by accessing two or more accounting management devices, it is possible to automatically determine the accounting information for filing claims for two or more creditors from the accounting information stored in the accounting management devices.

[0059] In addition, the claims management device of the present invention is a claims management device that, compared to the above invention, further comprises an inquiry unit that inquires of the creditor corresponding to the accounting information determined by the determination unit as to whether or not to file a claim with the billing destination, a response receiving unit that receives a response to the inquiry from the creditor, and a claim notification unit that, when the response receiving unit receives a response indicating that a claim will be filed, obtains notification information including information on the creditor identified by the creditor identifier contained in the claim information and claim content information, and sends the notification information to the debtor.

[0060] With this configuration, after automatically selecting accounting information for which a claim should be filed from the accounting information stored in the accounting management department, the creditor can decide whether or not to file a claim.

[0061] In addition, the debt management device of the present invention is a debt management device in which, compared to the above invention, the inquiry unit determines whether to make an inquiry to the billing party as to whether or not to file a debt claim, and only if it determines that an inquiry should be made, does it inquire to the billing party as to whether or not to file a debt claim.

[0062] With this configuration, it is possible to inquire of the creditor whether or not to file a claim only when an inquiry is necessary.

[0063] In addition, the debt management device of the present invention is a debt management device in which, compared to the above invention, inquiry conditions are stored in correspondence with creditor identifiers, and the inquiry unit acquires the inquiry conditions corresponding to the creditor identifiers, determines whether the inquiry conditions are met, and only if it determines that the inquiry conditions are met, inquires of the billing party as to whether to file a debt claim.

[0064] With this configuration, it is possible to ask creditors whether or not to file a claim under different conditions depending on the creditor.

[0065] In addition, the claims management device of the present invention is a claims management device that, compared to the above invention, further comprises a confirmation receiving unit that receives confirmation information regarding confirmation of a claim application from the debtor's debtor terminal, and a confirmation storage unit that acquires the confirmation information to be stored in response to the confirmation receiving unit receiving the confirmation information, and stores the confirmation information in the claims management unit in association with a claim identifier.

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

[0067] In addition, the debt management device of the present invention is a debt management device that, compared to the above invention, further comprises a negotiation receiving unit that receives negotiation information for extinguishing the debt from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information, and a negotiation storage unit that 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 a debt identifier.

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

[0069] In addition, the receivables management device of the present invention is a receivables management device that, compared to the above invention, further comprises an account generation unit that generates a virtual bank account in correspondence with a receivables identifier and acquires account information that identifies the virtual account, an account storage unit that stores the account information acquired by the account generation unit in correspondence with the receivables identifier in the receivables management unit, and an account transmission unit that transmits the account information to the debtor.

[0070] With this configuration, a bank account can be automatically set up for collection of debts.

[0071] In addition, the receivables management device of the present invention, compared to the above invention, further includes a judgment unit that judges whether the information received from the creditor terminal or debtor terminal matches the account conditions, which are the conditions for obtaining account information, and the account generation unit is a receivables management device that obtains account information that identifies a virtual account when the judgment unit determines that the account conditions are met.

[0072] With this configuration, a bank account can be automatically established only if the account conditions are met.

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

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

[0075] In addition, the debt management device of the present invention is a debt management device in which, compared to the above 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.

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

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

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

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

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

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

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

[0083] In addition, the receivables management device of the present invention is a receivables management device that, compared to the above invention, further comprises a negotiation information output unit that outputs two or more pieces of negotiation information received by the negotiation receiving unit in the order in which they were received by the negotiation receiving unit, and in a manner that makes it possible to understand whether the identifier to which the negotiation information corresponds is a creditor identifier or a debtor identifier.

[0084] This configuration makes it possible to provide a platform that manages the status of a claim in two or more phases among two or more phases from the occurrence of a claim to the processing of the claim, and promotes the processing of the claim.

[0085] In addition, the debt management device of the present invention is a debt management device that, compared to the above invention, further comprises an agreement document generation unit that generates an agreement document using the negotiation information when the negotiation information received by the negotiation receiving unit satisfies the agreement conditions, and an agreement document output unit that outputs the agreement document generated by the agreement document generation unit.

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

[0087] In addition, compared to the above invention, the debt management device of the present invention is a debt management device in which the debt status information has phase identification information that can identify the current phase out of two or more phases from the occurrence of the debt to the processing of the debt, and further includes an update unit that updates the phase identification information corresponding to the debt identifier in response to the application notification unit sending notification information to the debtor and in response to the confirmation receiving unit receiving confirmation information.

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

[0089] The claim management device of the present invention comprises 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 relating to the content of the claim; a claim management unit that stores one or more pieces of claim status information including claim information, which is information that corresponds to the claim identifier that identifies the claim; a claim storage unit that stores the claim information acquired by the claim acquisition unit in association with the claim identifier that identifies the claim that corresponds to the claim information; and a notification process that acquires notification information that includes information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and uses the notification information to notify the debtor. a claim notification unit, which, in response to the claim acquisition unit acquiring the claim information, performs first notification processing to notify the debtor of first notification information from a first entity, the first notification information including creditor information identified by a creditor identifier contained in the claim information and claim content information; and second notification means, after the first notification means has performed the first notification processing, to notify the debtor of second notification information from a second entity different from the first entity, the second notification information including creditor information identified by a creditor identifier contained in the claim information and claim content information.

[0090] This configuration can support activities for processing claims in at least two stages.

[0091] In addition, the debt management device of the present invention is a debt management device in which, compared to the above invention, the application notification unit is equipped with a third notification means that performs third notification processing to notify the debtor of third notification information from a third entity different from the first entity and the second entity, which is third notification information including information on the creditor identified by the creditor identifier contained in the application information and debt content information after the second notification means has performed the second notification processing.

[0092] This configuration can support activities for processing claims at least in three stages.

[0093] In addition, the receivables management device of the present invention, compared to the above invention, further comprises a transition judgment unit that judges whether a transition condition, which is a condition for changing the entity that notifies the notification information, has been met, and the second notification means is a receivables management device that performs second notification processing when the transition judgment unit judges that the transition condition has been met.

[0094] With this configuration, when a transition condition is satisfied, the process can proceed to the next stage in a multi-stage activity for processing a receivable.

[0095] Furthermore, in the credit management device of the present invention, the first entity is the creditor, and the first notification process is a process for the company to urge the creditor to pay.

[0096] This configuration makes it possible to support activities for processing claims at multiple stages.

[0097] Furthermore, in the claim management device of the present invention, the second entity is a claim management device that is an agent of the creditor.

[0098] This configuration can support activities for processing claims in at least two stages.

[0099] Furthermore, in the claim management device of the present invention, compared to the above invention, the third entity is a claim management device, and the third notification process is a claim management device that is a process for mediation.

[0100] This configuration can support activities for processing claims at least in three stages.

[0101] In addition, the receivables management device of the present invention, compared to the above invention, further comprises a negotiation receiving unit that receives negotiation information regarding negotiations between a creditor and a debtor from the creditor's creditor terminal and the debtor's debtor terminal, and a judgment unit that uses the negotiation information received by the negotiation receiving unit to judge whether the agreement conditions have been met, and the transition condition is a condition regarding the period after the first notification means performs the first notification processing during which the judgment unit does not judge that the agreement conditions have been met.

[0102] With this configuration, when a transition condition regarding the period until an agreement is reached is satisfied, the multi-stage activity for processing a claim can move to the next stage.

[0103] In addition, the debt management device of the present invention, compared to the above invention, further includes a negotiation receiving unit that receives negotiation information regarding negotiations between a creditor and a debtor from the creditor's creditor terminal and the debtor's debtor terminal, and the transition condition is a condition regarding the negotiation information.

[0104] With this configuration, when a transition condition regarding negotiation information is satisfied, the process can proceed to the next stage in a multi-stage activity for processing a debt.

[0105] The negotiation support device of the present invention comprises a petition acquisition unit that acquires petition information having a petitioner identifier that identifies the petitioner, a respondent identifier that identifies the respondent, and petition content information related to the content of the petition; a petition management unit that stores one or more petition status information including petition information, which is information that corresponds to the petition identifier that identifies the petition; a petition storage unit that stores the petition information acquired by the petition acquisition unit in association with the petition identifier that identifies the petition that corresponds to the petition; and a notification process that acquires notification information that includes information on the petitioner identified by the petitioner identifier contained in the petition information and petition content information, and uses the notification information to notify the respondent. a first notification means for performing first notification processing to notify the respondent of first notification information from a first entity, the first notification information including information on the complainant identified by a complainant identifier contained in the complaint information and complaint content information, in response to the complaint information being acquired by the complaint acquisition unit; and second notification means for performing second notification processing to notify the respondent of second notification information from a second entity different from the first entity, the second notification information including information on the complainant identified by a complainant identifier contained in the complaint information and complaint content information, after the first notification means has performed the first notification processing.

[0106] This arrangement can support complaint processing activities in at least two stages.

[0107] Furthermore, in the negotiation support device of the present invention, in contrast to the above invention, the claim notification unit is a negotiation support device that is equipped with a third notification means that performs third notification processing to notify the respondent of third notification information from a third entity different from the first entity and the second entity, which is third notification information including claimant information identified by a claimant identifier contained in the claim information and claim content information after the second notification means has performed the second notification processing.

[0108] This configuration can support complaint processing activities at least three levels.

[0109] In addition, the negotiation support device of the present invention, compared to the above invention, further includes a transition judgment unit that judges whether a transition condition, which is a condition for changing the entity that notifies the notification information, has been met, and the second notification means is a negotiation support device that performs second notification processing when the transition judgment unit judges that the transition condition has been met.

[0110] With this configuration, when a multi-stage activity for processing a claim is performed, the process can proceed to the next stage when the transition condition is satisfied.

[0111] Furthermore, in the negotiation support device of the present invention, compared to the above invention, the first entity is the complainant, and the first notification process is a process for urging the company to comply.

[0112] This configuration allows for multi-stage support of complaint processing activities.

[0113] Furthermore, in the negotiation support device of the present invention, in contrast to the above invention, the second entity is a negotiation support device that is an agent of the claimant.

[0114] This arrangement can support complaint processing activities in at least two stages.

[0115] Furthermore, in the negotiation support device of the present invention, compared to the above invention, the third entity is a negotiation support device, and the third notification process is a process for mediation.

[0116] This configuration can support complaint processing activities at least three levels.

[0117] In addition, the negotiation support device of the present invention, compared to the above invention, further comprises a negotiation receiving unit that receives negotiation information regarding the negotiation between the claimant and the respondent from the claimant terminal of the claimant and the respondent terminal of the respondent, and a judgment unit that judges whether the agreement conditions have been met using the negotiation information received by the negotiation receiving unit, and the transition condition is a condition regarding the period during which the judgment unit does not judge that the agreement conditions have been met after the first notification means performs the first notification processing.

[0118] This structure allows for the multi-stage process for processing a complaint to move to the next stage once the transition conditions regarding the time required to reach an agreement are met.

[0119] In addition, the negotiation support device of the present invention, compared to the above invention, further comprises a negotiation receiving unit that receives negotiation information regarding the negotiation between the claimant and the respondent from the claimant terminal of the claimant and the respondent terminal of the respondent, and the transition condition is a condition regarding the negotiation information.

[0120] With this configuration, in a multi-stage activity for processing a claim, if a transition condition regarding negotiation information is satisfied, the process can proceed to the next stage.

[0121] The claim management device according to the present invention can provide a platform that supports activities for processing claims, such as claim filing, at multiple stages.

[0122]

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

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

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

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

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

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

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

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

[0131] In this embodiment, a credit management device will be described that outputs negotiation information in a time series format showing the process of negotiations between a creditor and a debtor, and in a manner that makes it possible to know which of the creditor and the debtor input the negotiation information.

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

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

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

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

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

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

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

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

[0140] The receiving unit 12 includes a request 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 request storage unit 131, an update unit 132, a confirmation storage unit 133, a negotiation storage unit 134, a proposal content acquisition unit 135, a mediation support unit 136, a judgment unit 137, an agreement document generation unit 138, and an information acquisition unit 139. The transmitting unit 14 includes a request notification unit 141, a screen transmission unit 142, a proposal content transmission unit 143, a negotiation information output unit 144, a required information transmission unit 145, an agreement document output unit 146, and an information transmission unit 147.

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

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

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

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

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

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

[0147] Lawyer information is information about the 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 lawyer's contact information. Lawyer contact information is, for example, the lawyer's email address, the lawyer's telephone number, or the ID for the lawyer to log in to the debt management device 1.

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

[0149] 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 associated with 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.

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

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

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

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

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

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

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

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

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

[0159] The two or more phases from the occurrence of a claim until the creditor and 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 with the debtor. The "awaiting confirmation" phase is the phase in which the debtor is waiting for confirmation of the claim. Note that the "awaiting confirmation" phase may be the same phase as the "filed" phase. The "confirmed" phase is the phase in which the debtor confirms the claimed claim. The "negotiating" phase is the phase in which the creditor and debtor are negotiating on the processing of the claim. The "agreed" phase is the phase in which an agreement is reached in negotiations for the processing of the claim. Note that the two or more phases from the occurrence of a claim until the creditor and debtor agree on the processing of the claim do not have to include the "claim occurrence" phase and the "agreement" phase.

[0160] The phases handled by the claim management device 1 may include phases after an agreement has been 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 has been reached in negotiations and when the claim is being processed (for example, payment is being made). The "claim processing completed" phase is the phase when 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 also be some of the phases within 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 until the creditor and debtor agree on claim processing.

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

[0162] The receiving unit 12 receives various information and instructions from the creditor terminal 2 or the debtor terminal 3. The various information and instructions include, 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.

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

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

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

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

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

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

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

[0170] 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 creditor's proposal including the start month and each month's payment amount when installments are made to pay the money for debt settlement from the creditor terminal 2 or the debtor terminal 3.

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

[0172] The negotiation receiving unit 123 receives negotiation information from the debtor terminal 3, including, for example, "information indicating that the debtor has no recollection of the claim" and "information indicating that the debtor has already paid the claim directly."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0193] The determination unit 137 determines whether the agreed conditions are satisfied using the negotiation information received by the negotiation receiving unit 123 .

[0194] The agreed condition is a condition for determining whether negotiations regarding 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 is selected). For example, the specific debt settlement identifier is "Pay now by credit card" or "Pay in full at the end of the following month" among the debt settlement identifiers "Pay now by credit card," "Pay in full at the end of the following month," "Pay in installments at the end of each month," "Propose amount adjustment," "I don't remember this bill," "Already paid directly," and "Request online mediation." For example, the agreed condition is that the received negotiation information includes a payment method identifier. For example, the agreed condition is that negotiation information indicating the debtor's agreement to the negotiation information sent from the creditor has been received. For example, the agreed condition is that negotiation information indicating the creditor's agreement to the negotiation information sent from the debtor has been received.

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

[0196] The agreement document generation unit 138 generates an agreement document, for example, by substituting 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.

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

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

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

[0200] When a transmission condition for transmitting specific screen information is met, the screen sending unit 142 sends 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 sending unit 142 sends screen information to the debtor terminal 3 for allowing the debtor to select one of two or more methods of debt settlement. For example, when the screen sending unit 142 receives a selection of a selected object from the creditor terminal 2 or the debtor terminal 3, it sends screen information corresponding to the selected object to the creditor terminal 2 or the debtor terminal 3.

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

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

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

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

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

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

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

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

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

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

[0211] The creditor processing unit 23 performs various processes. For example, the various processes are processes for converting received information, instructions, etc. into information, instructions, etc. 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.

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

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

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

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

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

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

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

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

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

[0221] The debtor receiving unit 35 receives various types of information, such as notification information, negotiation information, and debt status information.

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

[0223] 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 by volatile recording media.

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

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

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

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

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

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

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

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

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

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

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

[0235] (Step S405) The claim 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.

[0236] (Step S406) The application notification unit 141 obtains the debtor's contact information from the received application information.

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

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

[0239] (Step S409) The confirmation accumulation unit 133 acquires the bond identifier associated with the confirmation information, etc.

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

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

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

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

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

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

[0246] (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.

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

[0248] (Step S418) The agreement document creating unit 138 creates an agreement document. An example of such an agreement document creating process will be described with reference to the flowchart in FIG.

[0249] (Step S419) The agreement creation unit 138 stores the agreement obtained in step S418 in the claim management unit 111 in association with the claim identifier.

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

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

[0252] (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.

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

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

[0255] (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.

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

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

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

[0259] (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.

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

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

[0262] (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.

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

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

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

[0266] (Step S436) The 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.

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

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

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

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

[0271] (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.

[0272] (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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0288] (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.

[0289] (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.

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

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

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

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

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

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

[0296] (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.

[0297] (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.

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

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

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

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

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

[0303] (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 may be, for example, the creditor name, debtor name, payment amount, payment start date, and payment due date.

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

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

[0306] (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., "A claim has been filed"), application time information (e.g., date and time), and the name of the creditor.

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

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

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

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

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

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

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

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

[0315] (Step S916) The information acquisition 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.

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

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

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

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

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

[0321] (Step S1001) The creditor acceptance unit 22 determines whether or not a 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.

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

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

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

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

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

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

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

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

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

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

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

[0333] (Step S1013) The creditor acceptance unit 22 determines whether or not other instructions have been accepted. If other instructions have been accepted, the process proceeds to step S1014; if not, the process returns to step S1001.

[0334] (Step S1014) The creditor processing unit 23 acquires the 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.

[0335] (Step S1015) The creditor receiving unit 25 determines 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.

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

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

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

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

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

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

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

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

[0344] (Step S1106) The debtor processing unit 33 acquires the bond identifier associated with the screen for inputting the output instruction. The debtor sending unit 34 sends the output instruction to the debt management device 1 in association with the bond identifier.

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

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

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

[0348] (Step S1110) The debtor processing unit 33 acquires the 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0365] Next, Tanaka A enters information into the fields of the screen of FIG. 17, such as "Name of the claim," "Amount claimed," and "Payment date of the main body," and then clicks the "File" button 1701.

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

[0367] 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 current date and time, "2024 / 8 / 11 09:00," which is the claim time, from a clock (not shown). The claim acquisition unit 121 constructs the claim information to be stored: "<Name of claim> X Company Non-payment <Claim amount> 100,000 <Payment due date of main body> 2924 / 8 / 1 <Creditor identifier> C01 ... <Other party 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 constructed 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 "1" as the phase identifier in the record of "ID=1" in Fig. 14.

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

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

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

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

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

[0373] The debtor terminal 3 receives the screen information and outputs the 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.

[0374] Then, let us assume that Yamada Y. selects button 2003 from Figure 20. Also, let us assume that Yamada Y. inputs the inquired installment amount of "5,000 yen" by pressing button 2003. Then, the debtor reception unit 32 of the debtor terminal 3 receives the negotiation information "<debt processing identifier> 3 <installment amount> 5,000". 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> 5,000". Next, the debtor transmission unit 34 transmits the negotiation information to the debt management device 1.

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

[0376] 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 constructs the proposal content using the process described using the flowchart in Figure 7.The proposal content acquisition unit 135 then associates the constructed proposal content with the negotiation information and stores it in the debt management table (Figure 14).This proposal content is file "P1."

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

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

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

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

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

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

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

[0384] Next, the receiving unit 12 of the claim management device 1 receives the negotiation information including the installment amount "20,000 yen" paired with the claim identifier "1."

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

[0386] 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 described using the flowchart in Figure 7, and substitutes the installment amount of "20,000 yen" and the creditor name, debtor name, and application amount that pair with the claim identifier "1" into the proposal content template to compose the proposal content. Next, the transmission unit 14 transmits the proposal content to Tanaka A's creditor terminal 2.

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

[0388] Next, Tanaka A selects the "Propose change to installment amount" button 2303 in Figure 23. 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 sends it to the debt management device 1.

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

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

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

[0392] Next, the debtor terminal 3 receives the screen information and outputs the screen shown in Figure 24. Then, let us say that Yamada Y. selects the "Accept revised installment amount" button 2401 in Figure 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 transmits it to the debt management device 1.

[0393] 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 agreement time "2024 / 8 / 11 16:39," from a clock (not shown). Next, the negotiation accumulation unit 134 stores the negotiation information "Agreement" and the agreement time in association with the claim identifier "1."

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

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

[0396] In addition, the information acquisition unit 139 acquires screen information for the debtor to determine the debt settlement 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.

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

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

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

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

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

[0402] Next, the claim management device 1 receives the claim processing identifier "B" and stores the claim processing identifier "B" in the claim management table (FIG. 14) in pairs with the claim identifier "1." 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.

[0403] In addition, the update unit 132 of the claim management device 1 updates the phase identifier paired with the claim identifier "1" to "5".

[0404] 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 creates screen information that includes the deposit destination information "Bank Account A". Next, the information transmission unit 147 transmits the screen information to the debtor terminal 3.

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

[0406] As described above, according to this embodiment, a platform can be provided that manages the status of a claim in two or more phases from the time the claim is generated until the creditor and debtor agree on the processing of the claim, and promotes the processing of the claim.

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

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

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

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

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

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

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

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

[0415] (Embodiment 2) This embodiment differs from embodiment 1 in that a virtual bank account is created in association with a bond identifier, and the account information of the virtual account is stored in association with the bond identifier. In addition, in this embodiment, it is preferable to create a virtual bank account only when the account conditions are met.

[0416] This embodiment may perform all of the processing of each device described in embodiment 1. Furthermore, claims handled in this embodiment are usually monetary claims.

[0417] The information system B in this embodiment comprises a claim management device 4, one or more creditor terminals 2, and one or more debtor terminals 3. The conceptual diagram of the information system B is the same as that in Figure 1, except that the reference numeral for the claim management device 4 is different.

[0418] The claim management device 4 is a server for storing information about claims. The claim management device 4 may store 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 4 may be, for example, a cloud server or an ASP server, but the type is not important.

[0419] The block diagram of the information system A in this embodiment is the same as that in Fig. 2, except that the reference numeral for the claim management device 4 is different. Fig. 29 is a block diagram of the claim management device 4.

[0420] The claim management device 4 includes a storage unit 11, a receiving unit 12, a processing unit 43, and a transmission unit 44. The processing unit 43 includes a claim accumulation unit 131, an update unit 132, a confirmation accumulation unit 133, a negotiation accumulation unit 134, a proposal content acquisition unit 134, a mediation support unit 135, a judgment unit 431, an agreement document generation unit 137, an information acquisition unit 138, an account generation unit 432, and an account accumulation unit 433. The transmission unit 44 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, an information transmission unit 147, and an account transmission unit 441.

[0421] The processing unit 43 constituting the claim management device 4 performs various types of processing. The various types of processing are, for example, processing performed by the application storage unit 131, update unit 132, confirmation storage unit 133, negotiation storage unit 134, proposal content acquisition unit 134, mediation support unit 135, judgment unit 431, agreement document generation unit 137, information acquisition unit 138, account generation unit 432, or account storage unit 433. It is preferable that the processing unit 43 performs all or part of the processing performed by the processing unit 13.

[0422] The judgment unit 431 judges whether the information received from the creditor terminal 2 or the debtor terminal 3 matches the account conditions. The judgment unit 431 may perform all or part of the processing performed by the judgment unit 136. For example, the negotiation receiving unit 123 may use the received negotiation information to judge whether the agreed conditions are met.

[0423] The information received from the creditor terminal 2 or the debtor terminal 3 is, for example, application information, confirmation information, or negotiation information.

[0424] The account conditions are conditions for the account generation unit 432 to acquire account information. The account conditions are, for example, that the claim acquisition unit 121 has acquired the claim information, that an agreement has been reached in the negotiations (that the agreement conditions have been met), and that the processing means identifier included in the received negotiation information is information indicating a "bank account."

[0425] The account creation unit 432 creates a virtual bank account in association with the bond identifier and acquires account information that identifies the virtual account. For example, the account creation unit 432 provides information unique to the bond (e.g., a bond identifier) ​​to an API that creates a virtual bank account, executes the API, and acquires the account information. For example, the account creation unit 432 passes the "bank name," "bank code," "branch name," and "account holder" to the API that creates a virtual bank account, executes the API, and acquires account information with a unique number. Note that the "account holder" is, for example, the name of the bank account operated by the bond management device 1. The "bank name," "bank code," "branch name," and "account holder" are stored in the storage unit 11.

[0426] Note that creating a virtual account includes issuing an instruction to create a virtual account. Creating a virtual account may also involve executing an API that creates a virtual account.

[0427] It is preferable that the account creation unit 432 acquires account information that identifies the virtual account when the determination unit 431 determines that the account conditions are met.

[0428] The account storage unit 433 stores the account information acquired by the account creation unit 432 in association with the bond identifier in the bond management unit 111. It is preferable that the account information acquired by the account creation unit 432 is unique for each bond.

[0429] The transmitting unit 44 transmits various types of information, such as notification information, screen information, proposal details, negotiation information, account information, and agreement documents.

[0430] The account sending unit 441 sends to the debtor the account information acquired by the account creation unit 432. For example, when the determination unit 431 determines that the agreement conditions are met, the account sending unit 441 sends the account information to the debtor so that the debtor can process the claim.

[0431] Next, an example of the operation of the claim management device 4 will be described with reference to the flowcharts of Figure 30 and Figure 5. In the flowchart of Figure 30, the description of the same steps as in Figure 4 or Figure 5 will be omitted.

[0432] (Step S3001) The judgment unit 431 judges whether the received information associated with the bond identifier satisfies the account conditions. If the account conditions are met, the process proceeds to step S3002; if not, the process returns to step S401.

[0433] (Step S3002) The account generation unit 432 etc. performs account acquisition processing. Return to step S401. An example of the account acquisition processing will be described with reference to the flowchart in FIG.

[0434] In the flowchart of FIG. 30, if the necessary information in S422 is account information, the account sending unit 441 sends the account information to the debtor.

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

[0436] Next, an example of the account acquisition process in step S3002 will be described with reference to the flowchart in FIG.

[0437] (Step S3101) The account creation unit 432 acquires information such as the account holder's name from the storage unit 11. The information such as the account holder's name is information necessary to open a new virtual account. The information such as the account holder's name includes, for example, the account holder's name, bank name, bank code, and branch name.

[0438] (Step S3102) The account creation unit 432 opens a new virtual account using the account name and other information acquired in step S3101 and passes it to the API.

[0439] (Step S3103) The account creation unit 432 executes the API.

[0440] (Step S3104) The account creation unit 432 executes the API to determine whether or not an account number, etc. has been acquired. If an account number, etc. has been acquired, the process proceeds to step S3105; if an account number, etc. has not been acquired, the process returns to step S3104.

[0441] (Step S3105) The account generation unit 432 generates account information including the acquired account number, etc.

[0442] (Step S3106) The account storage unit 433 acquires the bond identifier of the target bond.

[0443] (Step S3107) The account storage unit 433 stores the account information configured in step S3105 in the claim management unit 111 in association with the claim identifier acquired in step S3106.

[0444] (Step S3108) The judgment unit 431 judges whether or not to send the account information to the debtor. If the account information is to be sent, the process proceeds to step S3109; if not, the process returns to the upper level processing. Note that the account information is sent to the debtor only when the sending conditions are met. An example of the sending conditions being met is when the agreed conditions are met.

[0445] (Step S3109) The account sending unit 441 sends the account information constructed in step S3105 to the debtor, and then returns to the upper level processing.

[0446] A specific example of the operation of information system B in this embodiment will be described below. The specific example of the operation of information system B is generally similar to the specific example of the operation of information system A described in embodiment 1. However, it differs in that when the account conditions are met, the account creation unit 432 acquires account information that identifies a virtual account, and the account accumulation unit 433 pairs the account information with a bond identifier and accumulates it in the bond management table.

[0447] That is, it is assumed that the claim management unit 111 of the claim management device 4 stores a claim management table having the structure shown in Fig. 32. Compared to the claim management table of Fig. 14, the claim management table of Fig. 32 stores account information of an automatically acquired virtual account in each record. The account information is unique information that pairs with a claim identifier.

[0448] Then, as explained in the specific operations in the first embodiment, the account information of the virtual account is sent to the debtor on the screen shown in FIG.

[0449] As described above, according to this embodiment, when a claim for a debt is accepted, a virtual bank account can be automatically set up for the collection of the debt.

[0450] Furthermore, according to this embodiment, it is possible to provide a platform for managing the status of a claim in two or more phases out of two or more phases from the time a claim is generated until the claim is processed, and for facilitating the processing of the claim.

[0451] Furthermore, according to this embodiment, a bank account can be automatically established only when the account conditions are met.

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

[0453] Furthermore, according to this embodiment, the negotiation information and proposal contents can be presented appropriately.

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

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

[0456] Furthermore, according to this embodiment, when negotiations for debt settlement are concluded, the information necessary for debt settlement can be presented to the debtor.

[0457] The software for realizing the claim management device 4 in this embodiment is the following program. In other words, this program comprises a computer that can access a claim management unit that stores one or more pieces of claim status information, which is information associated with a claim identifier that identifies a claim and can identify the current phase out of two or more phases from the occurrence of a claim until the creditor and 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 relating 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, and a virtual bank account management unit that stores the claim information in association with the claim identifier. The program functions as an account generation unit that generates and acquires account information that identifies the virtual account, an account storage unit that stores the account information acquired by the account generation unit in the debt management unit in association with the debt identifier, an account transmission unit that transmits the account information to the debtor, an instruction receiving unit that receives an instruction to output debt status information from the creditor terminal or the debtor terminal, an information acquisition unit that acquires part or all of the debt status information corresponding to the output instruction from the debt management unit, and an information transmission unit that transmits part or all of the debt status information acquired by the information acquisition unit to the creditor terminal or the debtor terminal.

[0458] (Embodiment 3) In this embodiment, a description is given of a claim management device that determines accounting information that matches the claim application conditions from an accounting management unit that stores accounting information. Note that the claim application conditions may be different for each user.

[0459] In this embodiment, a claim management device will be described that queries the user as to whether or not to file a claim based on accounting information that meets the claim conditions.

[0460] In this embodiment, a claim management device will be described that queries the user as to whether or not to file a claim only based on accounting information that meets query conditions.

[0461] In this embodiment, a description will be given of a claim management device that receives payment information for claims and stores it in an accounting management section.

[0462] In this embodiment, a credit management device manages access information to an accounting management device equipped with an accounting management section, and uses the access information to access the accounting management device will be described.

[0463] 33 is a conceptual diagram of an information system C in this embodiment. The information system C comprises a credit management device 5, one or more creditor terminals 2, one or more debtor terminals 3, and one or more accounting management devices 6.

[0464] The claim management device 5 is a server for managing information about claims. The claim management device 5 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 5 may be, for example, a cloud server or an ASP server, but the type is not important.

[0465] The accounting management device 6 is a device that manages accounting information, which will be described later. The accounting management device 6 is, for example, a Yayoi Accounting (registered trademark) server, a Freee (registered trademark) server, or a Kanjo Bugyo (registered trademark) server. The accounting management device 6 is, for example, a cloud server or an ASP server, but the type is not important.

[0466] 34 is a block diagram of the information system C in this embodiment. FIG. 35 is a block diagram of the claim management device 5.

[0467] The claim management device 5 includes a storage unit 51, a receiving unit 52, a processing unit 53, and a transmission unit 44. The storage unit 51 includes a claim management unit 111, a user management unit 511, and an access management unit 512. The receiving unit 52 includes a response receiving unit 521, a confirmation receiving unit 122, a negotiation receiving unit 123, an instruction receiving unit 124, and a payment receiving unit 521. The processing unit 53 includes a determination unit 531, an inquiry unit 532, a claim acquisition unit 533, a claim storage unit 131, an update unit 132, a confirmation storage unit 133, a negotiation storage unit 134, a proposal content acquisition unit 134, an arbitration support unit 135, a judgment unit 431, an agreement document generation unit 138, an information acquisition unit 139, an account generation unit 432, an account storage unit 433, and a payment storage unit 534. The transmission unit 44 includes a claim notification unit 141, a screen transmission unit 142, a proposal content transmission unit 143, a negotiation information output unit 144, a necessary information transmission unit 145, an agreement document output unit 146, an information transmission unit 147, and an account transmission unit 441.

[0468] The accounting management device 6 includes an accounting management unit 61 .

[0469] Various types of information are stored in the storage unit 51 that constitutes the debt management device 5. The various types of information include, for example, debt status information, user information (described later), access information (described later), various screen information, various conditions, various templates, and lawyer information. The various conditions include, for example, application conditions (described later) and inquiry conditions (described later). It is preferable that default application conditions and default inquiry conditions are stored in the storage unit 51. It goes without saying that the various conditions may also be embedded in the program.

[0470] The user management unit 511 stores one or more pieces of user information. User information is information about a user, and a user is a person who uses the debt management device 5. In this case, a user is typically a person who can become a creditor. User information may also be creditor information. User information corresponds to, for example, a user identifier. The user identifier may also be a creditor identifier. The user identifier may also be a debtor identifier. User information has one or more user attribute values. User attribute values ​​have, for example, a creditor name, application conditions, and inquiry conditions.

[0471] The claim conditions are conditions for filing a claim for a debt. The claim conditions are conditions related to accounting information. The claim conditions include, for example, a date condition. The claim conditions include, for example, a date condition and an amount condition. The claim conditions include a condition that payment for the claim has not been made. The date condition is a condition related to a date. For example, the date condition is "the payment deadline has passed," "a period of time equal to or longer than the threshold has passed since the payment deadline," or "a period of time equal to or longer than the threshold has passed since the claim date." The amount condition is a condition related to the claim amount (claim amount). For example, the amount condition is "the claim amount is equal to or greater than the threshold" or "the claim amount is equal to or less than the threshold."

[0472] An inquiry condition is a condition for inquiring of a creditor as to whether or not to make an inquiry when accounting information that matches the application condition exists. An inquiry condition is, for example, an inquiry flag condition or an amount condition. An inquiry flag condition is a condition related to an inquiry flag. An inquiry flag is a flag that indicates whether or not to make an inquiry. An inquiry flag can be, for example, either "inquire (e.g., "1")" or "do not inquire (e.g., "0")." An amount condition is a condition related to the application amount. An amount condition is, for example, that the application amount is less than or equal to a threshold value.

[0473] The access management unit 512 stores one or more pieces of access information. Access information is information for accessing the accounting management device 6. Access information is information for accessing the accounting management device 6 used by a creditor. Examples of access information include the IP address of the accounting management device 6, a login ID and password for accessing the accounting management device 6, and API (Application Programming Interface) information for accessing the accounting management device 6. It is preferable that the access information be associated with a creditor identifier. In other words, it is preferable that the access management unit 512 stores access information for each creditor.

[0474] The receiving unit 52 receives various information and instructions from the creditor terminal 2 or the debtor terminal 3. The various information and instructions include, for example, a response, case registration, application information, confirmation information, negotiation information, output instructions, proposal content instructions, agreement document instructions, payment schedule instructions, or payment information, which will be described later.

[0475] The response receiving unit 521 receives a response to an inquiry from a creditor. The response from the creditor is usually received from the creditor terminal 2. The response is a response to an inquiry about whether or not to file a claim. The response may be, for example, "file (e.g., "1")" or "do not file (e.g., "0")." The response preferably includes information for constituting the claim information. The response may include, for example, the case name, the claim amount, the payment due date, the name of the billing party, contact information, etc.

[0476] The payment receiving unit 521 receives payment information. The payment receiving unit 521 typically receives payment information from a creditor or a debtor. Receipt from a creditor is typically received from the creditor terminal 2. Receipt from a debtor is typically received from the debtor terminal 3.

[0477] The payment information is information about a payment from a debtor for a claim. The received payment information is associated with a claim identifier. The payment information includes, for example, the payment amount, information indicating whether the payment has been completed, and the payment date.

[0478] The processing unit 53 performs various processes, such as processes performed by the decision unit 531, the inquiry unit 532, the application acquisition unit 533, or the payment accumulation unit 534.

[0479] The determination unit 531 determines one or more pieces of accounting information that meet the application conditions from the accounting management unit 61, which stores one or more pieces of accounting information. The determination unit 531 typically determines accounting information that meets the application conditions from accounting information for which payment has not been completed.

[0480] The accounting management unit 61 is normally included in the accounting management device 6, which is an external device other than the claim management device 5. However, the claim management device 5 may also include the accounting management unit 61.

[0481] Accounting information is information related to a creditor's billing of a debtor. Accounting information includes a billing recipient identifier and date information. Accounting information includes, for example, a billing source identifier and an invoice image. Accounting information includes, for example, creditor information with a billing source identifier. Accounting information is associated with a creditor identifier. The billing recipient identifier is, for example, the name of the billing recipient or the billing recipient's ID. The billing source identifier is, for example, the name of the billing source or the billing source's ID. The billing recipient identifier may be the same as the debtor identifier or the debtor name. The billing source identifier may be the same as the creditor identifier or the creditor name. Date information is information that identifies a date. Date information is, for example, the billing date, the payment due date, or the billing date and payment due date.

[0482] The determination unit 531 determines, for example, from one or more pieces of accounting information corresponding to a creditor identifier, accounting information that matches the application conditions associated with the creditor identifier.

[0483] The determination unit 531 accesses the accounting management device 6 using, for example, access information associated with the creditor identifier, and determines accounting information that matches the application conditions associated with the creditor identifier.

[0484] The determination unit 531, for example, searches one or more accounting management devices 6 and determines accounting information that meets the application conditions.

[0485] The timing or trigger for the determination unit 531 to determine the transaction information is not important. It is preferable for the determination unit 531 to perform processing to determine the transaction information periodically. For example, the determination unit 531 performs processing to determine the transaction information at a predetermined time (for example, "12:00 on the 1st of every month," "0:00 every day," or "10:00 every Monday"). For example, the determination unit 531 performs processing to determine the transaction information when instructions are received from the user. The timing for determining the transaction information is the timing of the automatic claim.

[0486] The inquiry unit 532 inquires of the creditors corresponding to each of the one or more pieces of accounting information determined by the determination unit 531 as to whether or not to file a claim for a claim related to the accounting information with the billing destination. The means and timing of the inquiry are not important. The inquiry unit 532, for example, sends inquiry information including one or more pieces of accounting information determined by the determination unit 531 to the creditor. When the creditor terminal 2 accesses the claim management device 5, the inquiry unit 532, for example, sends inquiry information including one or more pieces of accounting information determined by the determination unit 531 to the creditor terminal 2.

[0487] The inquiry information is information for inquiring of the creditor as to whether or not to file a claim for a claim related to the accounting information. The inquiry information may include, for example, part or all of the accounting information.

[0488] The claim acquisition unit 533 uses the accounting information determined by the determination unit 531 to acquire claim information having a creditor identifier, a debtor identifier, and claim content information. The claim acquisition unit 533 acquires claim information, for example, when the response to the inquiry is information indicating "file a claim." Note that the claim content information includes, for example, the claim amount contained in the accounting information, the case name contained in the accounting information, and the payment due date contained in the accounting information. The claim amount is the claim amount.

[0489] The claim accumulation unit 131 accumulates the claim information acquired by the claim acquisition unit 533 in the claim management unit 111 in association with the claim identifier.

[0490] When the payment receiving unit 521 receives payment information, the payment accumulation unit 534 accumulates payment-related information indicating that a payment corresponding to the payment information has been made in the accounting management unit 61. The payment accumulation unit 534 accumulates payment-related information in association with transaction information. The payment-related information may be part or all of the payment information, or may be information indicating that payment has been completed. The payment-related information may also be information used to cancel the transaction information corresponding to the payment.

[0491] The accounting management unit 61 that constitutes the accounting management device 6 stores one or more pieces of accounting information. Each of the one or more pieces of accounting information is associated with a billing source identifier. The billing source identifier may be the same as the creditor identifier.

[0492] The storage unit 51, user management unit 511, access management unit 512, and accounting management unit 61 are preferably non-volatile recording media, but can also be realized using volatile recording media.

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

[0494] The receiving unit 52, the response receiving unit 521, and the payment receiving unit 521 are usually realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0495] The processing unit 53, the decision unit 531, the inquiry unit 532, the claim acquisition unit 533, and the payment accumulation unit 534 can usually be realized by a processor, a memory, etc. The processing procedures of the processing unit 53, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0496] Next, an example of the operation of the credit management device 5 will be described using the flowcharts of Figures 36, 37, and 38. Note that in Figures 36, 37, and 38, explanations of steps that are the same as those in Figures 30 and 5 will be omitted. Also, here, if the answer is "N" in step S439, the process proceeds to step S3601 in Figure 38.

[0497] (Step S3601) The decision unit 531 determines whether it is time for an automatic claim. If it is time for an automatic claim, the process proceeds to step S3602, and if it is not time for an automatic claim, the process proceeds to step S3611.

[0498] (Step S3602) The determination unit 531 performs a determination process. An example of the determination process will be described with reference to the flowchart in FIG.

[0499] (Step S3603) The inquiring unit 532 assigns 1 to the counter i.

[0500] (Step S3604) The query unit 532 determines whether the i-th transaction information exists among the transaction information determined in step S3602. If the i-th transaction information exists, proceed to step S3605; if not, return to step S401.

[0501] (Step S3605) The inquiry unit 532 acquires the creditor identifier corresponding to the billing destination identifier for the i-th transaction information. Note that the creditor identifier may also be the billing source identifier.

[0502] (Step S3606) The inquiry unit 532 acquires the inquiry condition corresponding to the creditor identifier from the user management unit 511. The inquiry condition may be the same for all creditors.

[0503] (Step S3607) The inquiring unit 532 determines whether the inquiring condition is satisfied. If the inquiring condition is satisfied, the process proceeds to step S3608, and if not, the process proceeds to step S3611.

[0504] (Step S3608) The inquiry unit 532 uses the i-th transaction information to obtain inquiry information.

[0505] (Step S3609) The inquiry unit 532 transmits the inquiry information acquired in step S3608 to the creditor identified by the creditor identifier acquired in step S3605. The transmission to the creditor is usually to the creditor terminal 2.

[0506] (Step S3610) The inquiring unit 532 increments the counter i by 1. The process returns to step S3604.

[0507] (Step S3611) The claim acquisition unit 533 acquires claim information using the i-th accounting information. Similar to the process described using the flowchart in Figure 30, the processing unit 53 executes steps S404 to S407, and then executes steps S3001 and S3002. Proceed to step S3610.

[0508] (Step S3612) The reply receiving unit 521 determines whether or not a reply to the inquiry has been received from the creditor. If a reply has been received, the process proceeds to step S3613; if not, the process returns to step S401.

[0509] (Step S3613) The claim acquisition unit 533 determines whether the response is “claim” or “do not claim.” If the response is “claim,” the process proceeds to step S3614, and if the response is “do not claim,” the process returns to step S401.

[0510] (Step S3614) The claim acquisition unit 533 acquires the transaction information corresponding to the inquiry for the response. The claim acquisition unit 533 uses the transaction information to acquire the transaction information. The process proceeds to step S403.

[0511] (Step S3615) The payment receiving unit 521 determines whether or not payment information has been received. If payment information has been received, the process proceeds to step S3616, and if not, the process proceeds to step S439.

[0512] (Step S3616) The payment accumulation unit 534 accumulates payment-related information indicating that payment corresponding to the payment information received in step S3615 has been made in the accounting management unit 61. Return to step S401.

[0513] In the flowcharts of FIGS. 36, 37, and 38, the processing ends when the power is turned off or an interrupt occurs to end the processing.

[0514] Next, an example of the determination process in step S3602 will be described with reference to the flowchart in FIG.

[0515] (Step S3901) The determination unit 531 assigns 1 to a counter i.

[0516] (Step S3902) The decision unit 531 determines whether or not the i-th creditor exists. If the i-th creditor exists, the process proceeds to step S3903; if not, the process returns to the upper level process.

[0517] The determining unit 531 determines whether the i-th creditor exists by determining whether the i-th user information exists in the user management unit 511, for example.

[0518] (Step S3903) The determining unit 531 acquires the creditor identifier of the i-th creditor from the user management unit 511. The creditor identifier may be a user identifier.

[0519] (Step S3904) The determining unit 531 acquires the access information paired with the creditor identifier of the i-th creditor from the access management unit 512.

[0520] (Step S3905) The decision unit 531 acquires the application conditions corresponding to the creditor identifier of the i-th creditor from the user management unit 511. Note that the application conditions may be common to all creditors.

[0521] (Step S3906) The determination unit 531 uses the access information acquired in step S3904 to access the accounting management unit 61 corresponding to the access information. The determination unit 531 then acquires from the accounting management unit 61 one or more pieces of accounting information corresponding to the creditor identifier acquired in step S3903.

[0522] (Step S3907) The determination unit 531 assigns 1 to the counter j.

[0523] (Step S3908) The determination unit 531 determines whether the jth transaction information is present among the transaction information acquired in step S3906. If the jth transaction information is present, the process proceeds to step S3909; if not, the process proceeds to step S3912.

[0524] (Step S3909) The decision unit 531 determines whether the jth transaction information satisfies the claim conditions acquired in step S3905. If the claim conditions are met, the process proceeds to step S3910; if not, the process proceeds to step S3911.

[0525] (Step S3910) The decision unit 531 associates the jth accounting information with the creditor identifier of the i-th creditor and temporarily stores it in a buffer (not shown).

[0526] (Step S3911) The determination unit 531 increments the counter j by 1. The process returns to step S3908.

[0527] (Step S3912) The determination unit 531 increments the counter i by 1. The process returns to step S3902.

[0528] A specific example of the operation of the information system C in this embodiment will be described below. The claim management section 111 of the claim management device 5 stores a claim management table having the structure shown in FIG.

[0529] The user management unit 511 also stores a user management table shown in FIG. 40. The user management table is a table for managing user information. The user management table manages one or more records each having an "ID," "creditor identifier," "creditor name," "email address," "application conditions," and "inquiry conditions." The "ID" is information that identifies the record.

[0530] The default application conditions stored in the storage unit 51 are "<Date condition> Today - Payment due date = 1st <Amount condition> None." In other words, the default application condition is "the payment deadline has passed." The default application condition does not have an amount condition. The application condition for "ID=1" is that payment has not been made one week after the payment due date, regardless of the amount. The application condition for "ID=2" is "-" indicating that this is the default application condition. The application condition for "ID=3" indicates that a claim will be filed if the claim amount is greater than 80,000 yen and the payment due date has passed. It goes without saying that the application conditions also include failure to make payment by the debtor.

[0531] The inquiry condition for "ID=1" indicates that if the application amount is 100,000 yen or less, the creditor will be inquired as to whether or not to file a claim with the debtor. The inquiry condition for "ID=2" "1" indicates that for claims that meet the application conditions, the creditor will always be inquired as to whether or not to file a claim. The inquiry condition for "ID=3" "0" indicates that for claims that meet the application conditions, the creditor will be inquired as to whether or not to file a claim with the debtor without inquiring.

[0532] Furthermore, the access management unit 512 stores the access management table shown in FIG. 41. The access management table is a table for managing access information. The access management table manages one or more records that have an "ID," "creditor identifier," and "access information." The "access information" includes an "accounting management device identifier," "login ID," "password," and "API." The "API" includes a "search API" and an "update API." The "accounting management device identifier" is information that identifies the accounting management device 6. The accounting management device identifier is, for example, the IP address of the accounting management device 6 or a URL for accessing the accounting management device 6. The "login ID" is the creditor's ID (user ID) for logging in to the accounting management device 6. The "password" is the password for logging in to the accounting management device 6. The "search API" is an API for searching for the necessary accounting information from the accounting management device 6. The search API has definition information for one or more parameters that make up the search conditions. The "update API" is an API for updating the accounting information in the accounting management device 6. Updating transaction information here typically refers to the process of adding payment information to transaction information. Note that "API" refers to, for example, a function, method, or execution module.

[0533] A specific example of the operation of information system C in this embodiment differs from a specific example of the operation of information system B in embodiment 2 in that the receivables management device 5 automatically acquires claim information through processing by the claim acquisition unit 533, etc., and that when the receivables management device 5 receives payment information, it updates the accounting information in the accounting management device 6. Below, an example of the processing by which the receivables management device 5 automatically acquires claim information through processing by the claim acquisition unit 533, etc. will be explained in Specific Example 1, and an example of the processing by which the receivables management device 5 updates the accounting information in the accounting management device 6 when it receives payment information will be explained in Specific Example 2.

[0534] (Specific Example 1) Assume that the decision unit 531 of the claim management device 5 obtains the current time "2024 / 8 / 8 0:00" from a clock (not shown). Next, the decision unit 531 determines that it is time for automatic filing. Assume that the timing for automatic filing is "0:00" every day. The decision unit 531 then performs the decision processing described using the flowchart in Figure 39 as follows. That is, the decision unit 531 obtains the creditor identifier "C01" of the first creditor from the user management table (Figure 40). The decision unit 531 also obtains the filing condition "today - payment due date >= 7 days" corresponding to the creditor identifier "C01" from the user management table (Figure 40).

[0535] The determination unit 531 also obtains the access information paired with the creditor identifier "C01" from the access management table (Figure 41). Using the access information, the determination unit 531 accesses the accounting management device 6 "M01" corresponding to the access information and obtains a large amount of accounting information corresponding to the creditor identifier "C01."

[0536] Next, the decision unit 531 determines from the numerous pieces of accounting information that one piece of accounting information, "<Case name> X Company unpaid <Invoice amount> 100,000 <Payment due date> 2024 / 8 / 1 9:00 <Invoice recipient name> X Company <Contact information> yy@x.jp <Payment amount> 0 ...", is unpaid and satisfies the acquired claim condition "Today - payment due date > = 7 days".

[0537] Next, the inquiry unit 532 obtains the inquiry condition "claim amount <= 100,000" corresponding to the creditor identifier "C01" from the user management table (FIG. 40). Then, the inquiry unit 532 determines that the inquiry condition is met based on the inquiry condition and "<claim amount> 100,000".

[0538] Next, the inquiry unit 532 constructs inquiry information using one piece of accounting information. Next, the inquiry unit 532 obtains the email address "ta@c.com" that pairs with the creditor identifier "C01". Next, the inquiry unit 532 sends the obtained inquiry information to the email address "ta@c.com" of the creditor identified by the creditor identifier "C01".

[0539] Next, the creditor terminal 2 of the creditor "Tanaka A" receives and outputs the inquiry information. An example of such inquiry information is shown in FIG.

[0540] Suppose that creditor "Tanaka A" carefully considers whether or not to file a claim, and then, on August 11, 2024, selects the "File" button 4201 on the screen of FIG. 42. Next, Tanaka A's creditor terminal 2 accepts the instruction. Next, the creditor terminal 2 constructs a response to the effect that "I will file a claim" and transmits the response to the claim management device 5. The constructed response includes, for example, information contained in the inquiry information. For example, the response is "<Response> File a claim <Case name> X Company non-payment <Billing amount> 100,000 <Payment due date> August 1, 2024 9:00 <Billing party name> X Company <Contact information> yy@x.jp <Payment amount> 0 ...".

[0541] Next, the response receiving unit 521 of the claim management device 5 receives the response to the inquiry from the creditor terminal 2 of the creditor. Next, the claim acquisition unit 533 determines from the received response that the response is "file a claim." Next, the claim acquisition unit 533 acquires the accounting information corresponding to the inquiry that corresponds to the response, "<Case name> X Company Non-payment <Invoice amount> 100000 <Payment due date> 2024 / 8 / 1 9:00 <Invoice recipient name> X Company <Contact information> yy@x.jp <Payment amount> 0 ...." The claim acquisition unit 533 acquires the current time, the claim time "2024 / 8 / 11 15:35," from a clock (not shown). Next, the claim acquisition unit 533 uses the accounting information to acquire the claim information "<Case name> X Company non-payment <Claim amount> 100,000 <Payment due date> 2024 / 8 / 1 9:00 <Creditor identifier> C01 <Billing name> X Company <Contact information> yy@x.jp <Time of claim> 2024 / 8 / 11 15:35 ...".

[0542] Next, the claim accumulation unit 131 acquires a unique bond identifier "1." Next, the claim accumulation unit 131 accumulates the acquired claim information in the bond management table (FIG. 14) in pairs with the bond identifier "1." This claim information is the claim information of "ID=1" in FIG. 32. In addition, the update unit 132 accumulates the phase identifier "1" in the record of "ID=1" in FIG. 14.

[0543] The subsequent processing is the same as the processing described in the specific operation example of the first embodiment or the specific operation example of the second embodiment.

[0544] The credit management device 5 then accesses the accounting information of each creditor from the second onwards and performs the above-mentioned processing.

[0545] (Specific Example 2) Suppose that the payment receiving unit 521 of the debt management device 5 receives payment information "<Debt Identifier> 1 <Payment Amount> 20000 <Payment Date> 2024 / 9 / 30" from Tanaka A's creditor terminal 2, which indicates that payment has been made for the debt status information "ID=1" in the debt management table of Figure 32, paired with the creditor identifier "C01."

[0546] The payment accumulation unit 534 acquires the bond identifier "1" contained in the received payment information, and acquires the case name "X Company Non-Payment", the application amount "100,000", and the creditor name "X Company" that are paired with the bond identifier "1" from the bond management table (Figure 32). Next, the payment accumulation unit 534 uses the acquired information to compose payment-related information indicating that payment has been made on the bond: "<Creditor Identifier> C01 <Case Name> X Company Non-Payment <Billing Amount> 100,000 <Billee Name> X Company <Payment Amount> 20,000 <Payment Date> 2024 / 9 / 30."

[0547] Next, the payment accumulation unit 534 obtains the update API "uf(pn, ...)" that pairs with the creditor identifier "C01" from the access management table (Figure 41). Next, using the constructed payment-related information, the payment accumulation unit 534 substitutes information into the arguments of the API "uf(pn, ...)" to construct "uf(C01, X Company Non-Payment, 100000, X Company, 20000, 2024 / 9 / 30)." By executing this API, the payment accumulation unit 534 adds information to the accounting information in the accounting management device 6 that manages Tanaka A's accounting information, indicating that the amount "20000" was paid on "2024 / 9 / 30." Note that the update API has the structure "uf(creditor identifier, case name, invoice amount, invoice recipient name, payment amount, payment date)."

[0548] Through the above process, the receivable management device 5 can update the accounting information in the accounting management device 6 by receiving payment information for the receivable.

[0549] As described above, according to this embodiment, it is possible to automatically determine the accounting information for which a claim should be filed from the accounting information stored in the accounting management department.

[0550] Furthermore, according to this embodiment, it is possible to automatically determine the accounting information for claiming a claim from the accounting information stored in the accounting management department, based on different conditions for each creditor.

[0551] Furthermore, according to this embodiment, when a debtor makes a payment for a credit, information relating to the payment can be accumulated and managed in the accounting management department.

[0552] In addition, according to this embodiment, by accessing two or more accounting management devices, it is possible to automatically determine the accounting information for which claims should be filed for two or more creditors from the accounting information stored in the accounting management devices.

[0553] Furthermore, according to this embodiment, after automatically selecting accounting information for which a claim should be filed from the accounting information stored in the accounting management department, the creditor can decide whether or not to file a claim.

[0554] Furthermore, according to this embodiment, only when an inquiry is necessary, the creditor can be inquired as to whether or not to file a claim.

[0555] Furthermore, according to this embodiment, it is possible to inquire of creditors whether or not they wish to file a claim under different conditions depending on the creditor.

[0556] Furthermore, according to this embodiment, it is possible to provide a platform for managing the status of a claim in two or more phases out of two or more phases from the time a claim is generated until the claim is processed, and for facilitating the processing of the claim.

[0557] Furthermore, according to this embodiment, a bank account for collecting debts can be automatically set up.

[0558] Furthermore, according to this embodiment, a bank account can be automatically established only when the account conditions are met.

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

[0560] Furthermore, according to this embodiment, the negotiation information and proposal contents can be presented appropriately.

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

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

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

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

[0565] The software that realizes the claim management device 5 in this embodiment is the following program. In other words, this program is a program for causing a computer that can access a claims management unit that stores one or more pieces of claim status information, which is information associated with a claim identifier that identifies a claim and can identify the current phase out of two or more phases from the time the creditor and debtor agree on the processing of the claim, to function as: a determination unit that determines accounting information that meets the claim conditions from the accounting management unit that stores one or more pieces of accounting information having a billing destination identifier that identifies the billing destination, a billing amount, and date information that identifies the date related to the billing; a claim acquisition unit that uses the accounting information determined by the determination unit to acquire claim information having a creditor identifier that identifies the creditor, a debtor identifier that identifies the debtor, and claim content information related to the content of the claim; a claim storage unit that stores the claim information acquired by the claim acquisition unit in the claims management unit in association with the claim identifier; an instruction receiving unit that receives an instruction to output claim status information from the creditor terminal or the debtor terminal; an information acquisition unit that acquires part or all of the claim status information corresponding to the output instruction from the claims management unit; and an information sending unit that transmits part or all of the claim status information acquired by the information acquisition unit to the creditor terminal or the debtor terminal.

[0566] (Embodiment 4) In this embodiment, a debt management device will be described that sequentially urges debt settlement in multiple stages, starting with subjects in different positions. Note that multiple stages refers to, for example, two or three stages, but it can also be four or more stages. Note that the subjects are, for example, the creditor (principal), lawyer (agent), or system (debt management device 7, described later).

[0567] In this embodiment, a description will be given of a debt management device that transitions to an (n+1)th stage activity when a transition condition is satisfied in an nth stage activity for debt processing. Note that the activity is an activity for debt processing.

[0568] The information system D comprises a claim management device 7, one or more creditor terminals 2, and one or more debtor terminals 3. The conceptual diagram of the information system D in this embodiment is the same as that in Figure 1, except that the reference numerals for the claim management devices are different.

[0569] 43 is an example of a block diagram of the claim management device 7 constituting the information system D in this embodiment. The claim management device 7 of the information system D may include all or some of the components of any of the claim management device 1, claim management device 4, or claim management device 5.

[0570] The claim management device 7 includes a storage unit 71, a receiving unit 72, a processing unit 73, and a transmission unit 74. The storage unit 71 includes a claim management unit 711. The receiving unit 72 includes a claim acquisition unit 121, a confirmation reception unit 122, a negotiation reception unit 123, an instruction reception unit 124, and a transition instruction reception unit 721. The processing unit 73 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, an information acquisition unit 139, and a transition judgment unit 731. The transmission unit 74 includes a claim notification unit 741, 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.

[0571] Here, the request notification unit 741 includes a first notification means 7411, a second notification means 7412, and a third notification means 7413. The request notification unit 741 may include only the first notification means 7411 and the second notification means 7412. The request notification unit 741 may also include a fourth or subsequent notification means.

[0572] Various types of information are stored in the storage unit 71 that constitutes the claim management device 7. The various types of information include, for example, claim status information, various screen information, various conditions, various templates, and lawyer information.

[0573] The various conditions are, for example, one or more of the transition conditions, proposal content creation conditions, and agreement conditions, which will be described later. Note that the various conditions may be embedded in the program.

[0574] Here, lawyer information refers to information about the lawyer who represents the creditor, or information about the lawyer who supports online mediation. Lawyer information includes a lawyer identifier and lawyer contact information. The lawyer identifier is information that identifies the lawyer. The lawyer identifier is, for example, the lawyer's name, the lawyer's registration number, or the lawyer's ID. The lawyer contact information is information that indicates the lawyer's contact information. The 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 7.

[0575] The claim management unit 711 stores one or more pieces of claim status information. Claim status information is information related to claims. In this embodiment, the claim status information is information that identifies the current stage in the activities for claim processing, which are carried out in multiple stages. In each of the two or more stages, a different entity urges or negotiates the activities for claim processing. Note that different entities usually mean that different entities notify the debtor.

[0576] The claim status information in this embodiment is, for example, information that identifies the current phase out of two or more phases from the creation of a claim to agreement. The claim status information may also be information that identifies the current phase out of two or more phases from the filing of a claim to agreement. A phase in this embodiment is a specific state or period in the progress of claim-related processing from the creation of a claim to agreement or breakdown, etc. A phase may also be called a step, a situation, etc. The phase in this embodiment is not the stage described above.

[0577] The debt status information here includes information that identifies the stage. The information that identifies the stage is, for example, a stage identifier that identifies the stage, and an entity identifier that identifies the entity that will be urging or negotiating activities to process the debt. The stage identifier may be the same information as the entity identifier. In other words, the entity may be determined once the stage is determined. The entity identifiers are, for example, "creditor," "creditor identifier," "system," "lawyer (or agent)," and "lawyer identifier (or agent identifier)." The entity identifiers "creditor" and "creditor identifier" indicate that the stage is a company-wide demand. The entity identifier "system" indicates that the stage is a mediation stage by the debt management device 7. The entity identifiers "lawyer (or agent)" and "lawyer identifier (or agent identifier)" indicate that the stage is a negotiation stage by an agent.

[0578] The credit status information includes, for example, creditor information, debtor information, credit content information, confirmation information, negotiation information, proposal content, agreement document, stage identifier, subject identifier, phase specification information, and various time information.

[0579] The receiving unit 72 receives various information and instructions from the creditor terminal 2 or the debtor terminal 3. The various information and instructions include, for example, transition instructions, case registration, application information, confirmation information, negotiation information, output instructions, proposal content instructions, agreement document instructions, payment schedule instructions, and payment information, which will be described later.

[0580] The transition instruction receiving unit 721 receives a transition instruction from the creditor terminal 2. The transition instruction is usually associated with a credit identifier.

[0581] A transition instruction is an instruction to advance from the current stage to the next stage among multiple stages in the activity for processing a debt. The transition instruction includes, for example, a debtor identifier and a debt identifier.

[0582] The processing unit 73 performs various processes, such as processes performed by the request 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, or the transition judgment unit 731.

[0583] The transition determination unit 731 determines whether or not a transition condition, which is a condition for changing the entity that notifies the notification information, is satisfied.

[0584] The transition conditions are, for example, a condition regarding the negotiation period, a condition regarding the negotiation information, and a condition regarding the number of negotiations.

[0585] The condition related to the negotiation period is, for example, that the period from the start of the activity at the current stage until the negotiation is concluded has exceeded a threshold or has become longer than the threshold. The condition related to the negotiation period is, for example, a condition related to the period from the first notification means 7411 performing the first notification process until the determination unit 137 determines that the agreement conditions have been met. The condition related to the negotiation period is, for example, a condition related to the payment due date. The condition related to the payment due date is, for example, that the payment due date has passed, or that a threshold or more has passed since the payment due date has passed.

[0586] The conditions related to the negotiation information are conditions related to the negotiation information received by the negotiation receiving unit 123. For example, the condition related to the negotiation information is that the difference between the conditions presented by the creditor (e.g., the repayment amount or the number of installments) and the negotiation information sent by the debtor (e.g., the repayment amount or the number of installments) is equal to or greater than a threshold value. For example, the condition related to the negotiation information is that the negotiation information sent by the debtor does not satisfy the conditions presented by the creditor.

[0587] The condition regarding the number of negotiations is, for example, that negotiation information has been exchanged between the creditor and the debtor N times or more (N is a natural number of 2 or more).

[0588] The transmitter 74 transmits various types of information. The various types of information include, for example, notification information, first notification information (described later), second notification information (described later), third notification information (described later), screen information, proposal details, negotiation information, required information, and agreement documents. Note that the first notification information, second notification information, and third notification information are examples of notification information.

[0589] The application notification unit 741 acquires notification information including information on the creditor identified by the creditor identifier contained in the application information and information on the claim content, and performs notification processing using the notification information. The notification processing is a process for notifying the debtor about the claim. It is preferable that the notification processing be performed in multiple stages, as described below. The means of notification to the debtor is not important. Notification means include, for example, email, web system (software), fax, telephone, sending a short message, notification using SNS, and mail. Note that notification or support for notification may be performed using two or more notification means in the notification processing (first notification processing, second notification processing, or third notification processing).

[0590] The notification means used by the application notification unit 741 to notify the debtor at each stage from the first stage to the nth stage may be the same or different.

[0591] The notification process is, for example, a process of sending notification information to the debtor, a process of sending a URL specifying the location on a device where the notification information is located to the debtor, a process of faxing the notification information to the debtor, or a process of supporting the mailing of a demand letter including the notification information. The process of supporting the mailing is, for example, a process of printing the demand letter and a process of printing the address for mailing. Note that the demand letter may also be called a demand letter, a warning letter, etc.

[0592] The first notification means 7411 performs first notification processing in response to acquisition of the claim information by the claim acquisition unit 121. It is preferable that the first notification means 7411 immediately performs first notification processing when the claim acquisition unit 121 acquires the claim information, but the first notification processing may be performed after a period of time has elapsed after acquisition of the claim information.

[0593] The first notification process is a process of notifying the debtor of first notification information from a first entity (e.g., a creditor). The first notification process is a process for notifying the debtor about the debt.

[0594] The first notification information includes information on the creditor identified by the creditor identifier included in the application information and information on the content of the claim. It is preferable that the first notification information includes a first entity identifier (e.g., the name of the creditor, the name of the agent) that identifies the first entity.

[0595] It is preferable that the first notification information, the second notification information, and the third notification information are different from each other, but they may be the same except for the information regarding the subject.

[0596] The first entity is, for example, the creditor (principal person), but may also be a third party other than the creditor. The third party may be, for example, a lawyer acting as an agent, or the credit management device 7 (system).

[0597] If the first entity is a creditor, the first notification process is a process for the creditor's own company to demand payment.

[0598] The second notification means 7412 performs the second notification process after the first notification means 7411 performs the first notification process. It is preferable that the second notification means 7412 performs the second notification process when the transition determination unit 731 determines that the first transition condition is satisfied. Note that the first transition condition is an example of a transition condition. For example, the second notification means 7412 performs the second notification process when the transition instruction receiving unit 721 receives a transition instruction in the first stage situation.

[0599] The second notification process is a process of notifying the debtor of the second notification information from the second entity. The second notification process is a process for notifying the debtor about the claim.

[0600] The second notification information includes information on the creditor identified by the creditor identifier contained in the application information and information on the content of the claim. Typically, the second notification information is different from the first notification information. It is preferable that the second notification information includes a second entity identifier (e.g., the name of the agent, the name of the creditor) that identifies the second entity.

[0601] The second entity is different from the first entity. The second entity is, for example, an agent of the creditor (usually a lawyer), the credit management device 7 (system), or the creditor (principal person).

[0602] When the second entity is the claim management device 7 (system), the second notification process is a process for mediation.

[0603] The third notification means 7413 performs the third notification process after the second notification means 7412 performs the second notification process. It is preferable that the third notification means 7413 performs the second notification process when the transition determination unit 731 determines that the second transition condition is satisfied. The second transition condition is an example of a transition condition. It is preferable that the second transition condition is different from the first transition condition, but they may be the same. For example, the third notification means 7413 performs the third notification process when the transition instruction receiving unit 721 receives a transition instruction in the second stage situation.

[0604] The third notification process is a process of notifying the debtor of third notification information from a third entity. The third notification process is a process for notifying the debtor about the claim.

[0605] The third notification information typically includes information on the creditor identified by the creditor identifier included in the application information and information on the content of the claim. It is preferable that the third notification information includes a third entity identifier (e.g., the name of the attorney) that identifies the third entity.

[0606] The third entity is different from the first entity and the second entity, and may be, for example, an agent of the creditor (usually a lawyer), the credit management device 7 (system), or the creditor (principal person).

[0607] When the third entity is the claim management device 7 (system), the third notification process is a process for mediation.

[0608] After the first notification process is performed by the first notification means 7411, any negotiations may be conducted between the first entity and the creditor in the first stage. After the first notification process is performed by the first notification means 7411, support may be provided by the credit management device 7, as described in the first embodiment, for example.

[0609] After the second notification process is performed by the second notification means 7412, any negotiations may be conducted between the second entity and the creditor in the second stage. After the second notification process is performed by the second notification means 7412, support may be provided by the credit management device 7, as described in the first embodiment, for example.

[0610] After the third notification process is performed by the third notification means 7413, any negotiations may be conducted between the third entity and the creditor in the third stage. After the third notification process is performed by the third notification means 7413, support may be provided by the credit management device 7, as described in the first embodiment, for example.

[0611] The support provided by the receivables management device 7 in the first, second, and third stages in negotiations between the subject and the debtor after notification of the notification information may be the same or different.

[0612] The storage unit 71 and the debt management unit 711 are preferably non-volatile recording media, but can also be realized by volatile recording media.

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

[0614] The receiving unit 72 and the transition instruction receiving unit 721 are usually realized by wireless or wired communication means.

[0615] The processing unit 73 and the transition determination unit 731 can usually be realized by a processor, memory, etc. The processing procedures of the processing unit 73, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0616] The transmitting unit 74, the request notifying unit 741, the first notifying means 7411, the second notifying means 7412, and the third notifying means 7413 are realized by, for example, wireless or wired communication means.

[0617] Next, an example of the operation of the claim management device 7 will be described using the flowcharts of Figures 44 to 46. Note that in the flowcharts of Figures 44 to 46, explanations of steps that are the same as those in Figure 4 or Figure 5 will be omitted.

[0618] (Step S4401) The first notification unit 7411 etc. performs first notification processing. An example of the first notification processing will be described with reference to the flowchart in FIG.

[0619] (Step S4402) The processing unit 73 associates the stage flag "1" with the bond identifier acquired in step S403 and stores it in the bond management unit 711. Return to step S401. The stage flag is an example of a stage identifier.

[0620] (Step S4403) The transition instruction receiving unit 721 determines whether or not a transition instruction has been received from the creditor terminal 2. If a transition instruction has been received, the process proceeds to step S4404, and if a transition instruction has not been received, the process proceeds to step S4406.

[0621] (Step S4404) The processing unit 73 acquires the bond identifier associated with the transition instruction.

[0622] (Step S4405) The processing unit 73 etc. performs transition processing for the processing of the bond identified by the bond identifier acquired in step S4404. Return to step S401.

[0623] An example of the transition process will be described with reference to the flowchart in Fig. 48. The transition process is a process for shifting the stage of the debt processing.

[0624] (Step S4406) The transition determination unit 731 determines whether or not it is time to perform the transition determination process. If it is time to perform the transition determination process, the process proceeds to step S4407, and if it is not time to perform the transition determination process, the process proceeds to step S408.

[0625] The timing of the transition determination process is not important, and the timing of the transition determination process may be, for example, when a predetermined time arrives or when negotiation information transmitted from the debtor terminal 3 is received.

[0626] (Step S4407) The transition determination unit 731 assigns 1 to the counter i.

[0627] (Step S4408) The transition determination unit 731 determines whether the i-th bond identifier of the bond that is the target of the transition determination process exists. If the i-th bond identifier exists, the process proceeds to step S4409; if not, the process returns to step S401.

[0628] The bond identifier of the bond that is the target of the transition determination process is, for example, the bond identifier of the bond management unit 711 or the bond identifier that corresponds to the received negotiation information.

[0629] (Step S4409) The transition determination unit 731 performs transition determination processing for the i-th bond identified by the i-th bond identifier. An example of the transition determination processing will be described with reference to the flowchart of FIG.

[0630] The transition determination process is a process for determining whether or not to transition to a different stage in the negotiation of the debt settlement.

[0631] (Step S4410) If the result of the determination is "transition", the process proceeds to step S4411, and if the result is "no transition", the process proceeds to step S4413.

[0632] (Step S4411) The processing unit 73 acquires the i-th bond identifier.

[0633] (Step S4412) The processing unit 73 etc. performs transition processing for transitioning the processing stage of the bond identified by the i-th bond identifier. An example of the transition processing will be described with reference to the flowchart of FIG.

[0634] (Step S4413) The transition determination unit 731 increments the counter i by 1. The process returns to step S4408.

[0635] In the flowcharts of FIGS. 44 to 46, the processing ends when the power is turned off or an interrupt occurs to end the processing.

[0636] Next, an example of the first notification process in step S4401 will be described with reference to the flowchart in Fig. 47. Note that in the flowchart in Fig. 47, the description of the same steps as in Fig. 4 will be omitted.

[0637] (Step S4701) The first notification means 7411 acquires a first entity identifier. For example, the first notification means 7411 acquires a first entity identifier that does not change depending on the creditor from the storage unit 71. For example, the first notification means 7411 acquires a first entity identifier that pairs with a creditor identifier from the storage unit 71. In other words, the first entity may be fixed or may change depending on the creditor.

[0638] (Step S4702) The first notification means 7411 composes notification information including information on the first subject identified by the first subject identifier. Then, the process proceeds to step S406.

[0639] The process of configuring the notification information here may be the same as the process described using the flowchart in FIG. 6, except that the notification information includes information on the first subject.

[0640] Next, an example of the transition process in steps S4405 and S4412 will be described with reference to the flowchart in FIG.

[0641] (Step S4801) The claim notification unit 741 acquires from the claim management unit 711 a stage flag paired with a claim identifier that identifies the target claim.

[0642] (Step S4802) If the step flag is "1", proceed to step S4803, and if it is "2", proceed to step S4805.

[0643] (Step S4803) The second notification unit 7412 performs second notification processing. An example of the second notification processing will be described with reference to the flowchart in FIG.

[0644] (Step S4804) The processing unit 73 updates the stage flag paired with the bond identifier to "2." The process returns to step S401.

[0645] (Step S4805) The processing unit 73 determines whether or not to perform the third notification process. If the third notification process is to be performed, the process proceeds to step S4806, and if not, the process proceeds to step S4808.

[0646] The processing unit 73 may always determine to perform the third notification process. Alternatively, the processing unit 73 may obtain information paired with the creditor identifier or the credit identifier, for determining whether to perform the third notification process, from the storage unit 71, and use the information to determine whether to perform the third notification process.

[0647] (Step S4806) The third notification unit 7413 performs third notification processing. An example of the third notification processing will be described with reference to the flowchart in FIG.

[0648] (Step S4807) The processing unit 73 updates the stage flag paired with the bond identifier to "3." The process returns to step S401.

[0649] (Step S4808) The processing unit 73 stores information to the effect that the debt processing has ended unsuccessfully in the debt management unit 711. The process returns to step S401.

[0650] Next, an example of the second notification process in step S4803 will be described with reference to the flowchart of Fig. 49. Note that in the flowchart of Fig. 49, the description of the same steps as in Fig. 4 will be omitted.

[0651] (Step S4901) The second notification means 7412 acquires a second subject identifier. For example, the second notification means 7412 acquires a second subject identifier that does not change depending on the creditor from the storage unit 71. For example, the second notification means 7412 acquires a second subject identifier that pairs with the creditor identifier from the storage unit 71. In other words, the second subject may be fixed or may change depending on the creditor.

[0652] (Step S4902) The second notification means 7412 constructs notification information including information on the second subject identified by the second subject identifier. Note that the notification information construction process may be the same as the process described using the flowchart in Figure 6, except that it includes information on the second subject. Proceed to step S406.

[0653] Next, an example of the third notification process in step S4806 will be described with reference to the flowchart in FIG.

[0654] (Step S5001) The third notification unit 7413 acquires a third notification information template from the storage unit 71.

[0655] (Step S5002) The third notification means 7413 acquires a third entity identifier. For example, the third notification means 7413 acquires a third entity identifier that does not change depending on the creditor from the storage unit 71. For example, the third notification means 7413 acquires a third entity identifier that pairs with the creditor identifier from the storage unit 71. In other words, the third entity may be fixed or may change depending on the creditor.

[0656] (Step S5003) The third notification unit 7413 acquires, from the storage unit 71, third subject information paired with the third subject identifier acquired in step S5002.

[0657] (Step S5004) The third notification unit 7413 substitutes the third subject information acquired in step S5003 into the third notification information template acquired in step S5001. Then, the process proceeds to step S602.

[0658] (Step S5005) The third notification unit 7413 prints the third notification information acquired in step S5004, and returns to the upper processing.

[0659] 50, the information substitution in steps S603 and S605 is substitution into the third notification information template. Furthermore, upon completion of the information substitution in step S605, the construction of the third notification information to be output is completed.

[0660] 50, the printed third notice information is usually sent to the debtor by mail. However, the third notice means 7413 may also notify the debtor of the third notice information by other means such as email.

[0661] Furthermore, the processing performed in the flowchart of FIG. 50 may be the same as the processing in FIG. 47 or FIG. 49, except that the subject information is different.

[0662] Next, an example of the transition determination process in step S4409 will be described with reference to the flowchart in FIG.

[0663] (Step S5101) The transition determination unit 731 acquires from the claim management unit 711 the claim management information paired with the claim identifier of the target claim.

[0664] (Step S5102) The transition determination unit 731 assigns 1 to a counter i.

[0665] (Step S5103) The transition determination unit 731 determines whether or not the i-th transition condition exists in the storage unit 71. If the i-th transition condition exists, the process proceeds to step S5104; if not, the process proceeds to step S5108.

[0666] (Step S5104) The transition determination unit 731 acquires one or more pieces of information to be used for determining the i-th transition condition. The one or more pieces of information may be, for example, the start date of the negotiations and today's date, the due date and today's date, the conditions presented by the creditor and the negotiation information received from the debtor, and the number of times the negotiation information has been exchanged.

[0667] (Step S5105) The transition determination unit 731 determines whether the i-th transition condition is satisfied using one or more pieces of information acquired in step S5104. If the i-th transition condition is satisfied, the process proceeds to step S5106, and if not, the process proceeds to step S5107.

[0668] (Step S5106) The transition determination unit 731 assigns "transition" to the variable "determination result." The process returns to the upper level process.

[0669] (Step S5107) The transition determination unit 731 increments the counter i by 1. The process returns to step S5103.

[0670] (Step S5108) The transition determination unit 731 assigns "no transition" to the variable "determination result." The process returns to the upper level process.

[0671] A specific example of the operation of the information system D in this embodiment will be described below.

[0672] The storage unit 71 that constitutes the debt management device 7 stores the creditor management table shown in Figure 52. 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 7. The creditor management table here manages one or more records that have an "ID," "creditor identifier," "creditor name," "email address," "payment destination information," "first stage," "second stage," "third stage," "first transition condition," and "second transition condition." The "creditor name," "email address," and "payment destination information" constitute creditor information.

[0673] "First stage," "second stage," and "third stage" are pieces of information that identify the subject of each stage to which the debtor transitions for debt processing. "1" indicates that the subject is the creditor (principal). "2" indicates that the subject is the debt management device 7 (system). "3" indicates that the subject is an attorney acting as an agent. If "second stage" or "third stage" is "- (empty)," this indicates that the creditor will not transition to that stage, that is, the debtor will only be notified up to the previous stage.

[0674] The "first transition condition" is information for transitioning from the "first stage" to the "second stage." The "second transition condition" is information for transitioning from the "second stage" to the "third stage." Here, the transition conditions are conditions related to the period and the number of negotiations. The transition condition "period >= 10 days" indicates that the stage will transition if an agreement has not been reached even after 10 days or more have passed since the notification (after the start of negotiations). The transition condition "payment due date has passed" indicates that the stage will transition if an agreement has not been reached even after the payment due date has passed. The transition condition "number of negotiations >= 4" indicates that the stage will transition if an agreement has not been reached even after four or more exchanges of negotiation information (presentation of conditions, whether or not to accept the conditions).

[0675] Furthermore, in the creditor management table shown in Figure 52, the subject of each stage and the transition conditions are managed for each creditor. In other words, here, the creditor can specify the subject of each stage and the transition conditions. It is preferable that the creditor can specify the subject of each stage and the transition conditions for each bond identifier. In Figure 52, the subject of each stage and the transition conditions are managed for each bond identifier.

[0676] The claims management unit 711 of the claims management device 7 stores a claims management table having the structure shown in Fig. 53. The claims management table is a table that manages claim status information. The claims management table here is a table that manages one or more records that have "claim identifier," "application information," "confirmation information," "claim processing identifier," "phase identifier," "negotiation information," "time of negotiation," "proposal content," "agreement document," and "stage flag."

[0677] The "stage flag" is information that identifies the current stage among multiple stages of negotiations and can take the value "1," "2," or "3." The stage flags "1," "2," and "3" indicate the first, second, and third stages, respectively.

[0678] Furthermore, the storage unit 71 of the debt management device 7 stores lawyer information about the attorney who is the agent corresponding to the entity identifier "3." Here, the lawyer information is assumed to be "<Law firm> Legal Professional Corporation ABC <Attorney in charge> Tanaka Hajime <Address> 〒060-0031 Sapporo City...." Note that, here, only one piece of lawyer information is stored in the storage unit 71, but lawyer information may also be managed for each creditor identifier or each debt identifier. In other words, debtors may be notified using different lawyer names for each creditor or each debt.

[0679] In the above situation, suppose that company H (creditor identifier "C02"), which operates a gym, inputs claim information for Mr. Yamada A, a member of the gym who has unpaid monthly membership fees, into creditor terminal 2. Creditor terminal 2 then accepts the claim information, pairs it with creditor identifier "C02," and sends a case registration including the claim information to creditor management device 7.

[0680] The claim acquisition unit 121 of the claim management device 7 receives the case registration from the creditor terminal 2. Next, the claim accumulation unit 131 creates the claim information to be accumulated by the above-mentioned processing, and accumulates the claim information in the claim management table. The accumulated claim information is the claim information of "ID=2" in the claim management table (Figure 53).

[0681] Next, the first notification means 7411 obtains "First stage = 1 (principal entity)" that pairs with the creditor identifier "C02" from the creditor management table (Figure 52). The first notification means 7411 also obtains the application information that pairs with the creditor identifier "C02" from the creditor management table (Figure 53). Next, the first notification means 7411 obtains a first notification information template that corresponds to the first entity identifier "1 (principal entity)" from the storage unit 71. The first notification means 7411 then substitutes the debtor's name, creditor information, application amount, etc. contained in the application information into the first notification information template to construct the first notification information.

[0682] Next, the first notification means 7411 acquires the email address "zz@z.jp" of the debtor "Yamada A." from the application information.

[0683] Next, the first notification means 7411 sends the constructed first notification information to the email address "zz@z.jp".

[0684] Next, Yamada A's debtor terminal 3 receives and outputs the first notice information. An example of such first notice information is shown in FIG.

[0685] Thereafter, Yamada A. does not contact the first notice information (FIG. 54) he received by email, and the payment due date "January 31, 2025" passes.

[0686] The transition determination unit 731 then obtains the first transition condition "past due date" that is paired with the creditor identifier "2" and the payment date "January 31, 2025" that is paired with the creditor identifier "2." The transition determination unit 731 also obtains today's date, "February 1, 2025," from a clock (not shown). The transition determination unit 731 then determines that the first transition condition is satisfied.

[0687] Next, the second notification means 7412 obtains the second stage "2" paired with the creditor identifier "C02" from the creditor management table (FIG. 52).The second notification means 7412 then changes the subject from "Company H (principal)" to the credit management device 7 (system), and performs, for example, the processing described in embodiment 1 (particularly the processing described as a specific example of the operation of information system A).The second notification means 7412 also updates the stage flag paired with the credit identifier "2" from "1" to "2."

[0688] During the second stage of mediation by information system A, the exchange of negotiation information between H Company and Yamada A has reached the fourth time, and the judgment unit 137 has determined that the two parties have not reached an agreement (have not met the conditions for agreement).

[0689] Next, the transition determination unit 731 obtains the second transition condition "number of negotiations >= 4" that is paired with the creditor identifier "C02" from the creditor management table (FIG. 52).The transition determination unit 731 then checks the negotiation information for "ID=2" in the credit management table (FIG. 53), confirms that no agreement has been reached and that four negotiation information exchanges have occurred, and determines that the second transition condition is met.

[0690] Next, the application notification unit 741 obtains the stage flag "2" that pairs with the bond identifier "2" from the bond management table (Figure 53). Next, the processing unit 73 obtains the third stage "3" that pairs with the creditor identifier "C02". Because the third stage is not NULL, the processing unit 73 determines that the third notification process should be performed.

[0691] Next, the third notification means 7413 performs the third notification process as follows. That is, the third notification means 7413 obtains a third notification information template from the storage unit 71. Here, the third notification information template is a postcard template for notifying the debtor by mail. Next, the third notification means 7413 obtains the third subject identifier "3." Next, the third notification means 7413 obtains the lawyer information, which is the third subject information corresponding to the third subject identifier "3," from the storage unit 71. Next, the third notification means 7413 substitutes the obtained third subject information into the obtained third notification information template. Furthermore, the third notification means 7413 obtains the creditor information and substitutes it into the third notification information template. Furthermore, the third notification means 7413 obtains the debtor information and substitutes it into the third notification information template. With the above steps, the third notification information to be notified to the debtor is completed. Next, the third notification means 7413 prints the third notification information. An example of such printed third notification information is shown in FIG. 55. In Figure 55, (A) is the front side of the postcard, and (B) is the back side of the postcard. In addition, the third notification means 7413 updates the stage flag paired with the bond identifier "2" from "2" to "3."

[0692] Then, for example, the person in charge of operating the debt management device 7 mails a postcard written by a lawyer to the debtor, Mr. Yamada A.

[0693] It is assumed that Mr. Yamada A sees a postcard that arrived in the name of a lawyer and transfers the monthly gym membership fee. It is preferable that the credit management unit 711 also manages the fact that such a transfer has been made.

[0694] As described above, according to this embodiment, activities for processing claims can be supported in multiple stages, for example, two or three stages.

[0695] Furthermore, according to this embodiment, when a transition condition is satisfied in a multi-stage activity for processing a claim, the process can move to the next stage.

[0696] Furthermore, according to this embodiment, when a transition condition regarding the period until an agreement is reached is satisfied in a multi-stage activity for processing a claim, the process can move to the next stage.

[0697] Furthermore, according to this embodiment, in the case of multi-stage activities for processing a debt, if a transition condition related to negotiation information is satisfied, it is possible to move to the next stage.

[0698] 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 the claims management device 7 in this embodiment is the following program. In other words, this program causes a computer to: The claim management unit stores one or more pieces of claim status information including claim information, which is information corresponding to a claim identifier that identifies a claim, and functions as a claim storage unit that stores the claim information acquired by the claim acquisition unit in association with a claim identifier that identifies the claim that corresponds to the claim information, and a claim notification unit that acquires notification information including information on the creditor identified by the creditor identifier contained in the claim information and claim content information, and performs notification processing, which is processing for notifying the debtor using the notification information, and the claim notification unit, in response to the acquisition of the claim information by the claim acquisition unit, acquires the previous claim information contained in the claim information. This is a program for causing the computer to function as comprising: a first notification means for performing first notification processing to notify the debtor of the first notification information from a first entity, the first notification information including information on the creditor identified by the creditor identifier and information on the content of the claim; and a second notification means for performing second notification processing to notify the debtor of second notification information from a second entity different from the first entity, the second notification information including information on the creditor identified by the creditor identifier contained in the application information and information on the content of the claim, after the first notification means has performed the first notification processing.

[0699] In the first, second, third, and fourth embodiments, the processing of claims other than the processing of claims may be supported. In other words, the claim management device 1, the claim management device 4, the claim management device 5, and the claim management device 7 may be negotiation support devices that support the processing of claims other than the processing of claims.

[0700] In the first, second, third, and fourth embodiments, the claims may be referred to as claims. The claim identifiers may be referred to as claim identifiers. The creditors may be referred to as claimants. The debtors may be referred to as defendants.

[0701] The creditor terminal 2 may be a terminal used by a claimant filing a claim for some kind of dispute. In other words, the creditor terminal 2 may also be called the claimant terminal 2.

[0702] The debtor terminal 3 may be a terminal used by the respondent against whom some kind of dispute is filed. In other words, the debtor terminal 3 may also be called the respondent terminal 3.

[0703] Claim status information regarding various claims may be stored in the claim management unit 111 and the claim management unit 711. In other words, the claim management unit 111 and the claim management unit 711 may be referred to as a claim management unit 811, which will be described later. The claim status information, which will be described later, may be the claim status information described above.

[0704] (Embodiment 5) In this embodiment, a negotiation support device will be described that sequentially urges parties with different positions to process applications in multiple stages. Note that multiple stages refers to, for example, two or three stages, but may also be four or more stages. Note that the parties may be, for example, a petitioner (principal) such as a creditor, a lawyer (agent), or a system (negotiation support device 8, described later).

[0705] In this embodiment, a negotiation support device will be described that transitions to an (n+1)th stage activity when a transition condition is satisfied in an nth stage activity for claim processing. Note that the activity is an activity for claim processing.

[0706] The claim management device 7 of embodiment 4 is capable of managing not only claims but also applications. In other words, the claim management device 7 is a device that manages applications other than claims and supports application processing, and the negotiation support device 8 is a device that manages applications other than claims and supports application processing. The negotiation support device 8 has all or some of the components of the claim management device 7. The negotiation support device 8 can execute all or some of the functions of the claim management device 7.

[0707] The information system E comprises a negotiation support device 8, one or more claimant terminals 2, and one or more respondent terminals 3. The claimant terminal 2 is a terminal equivalent to the creditor terminal 2. The respondent terminal 3 is a terminal equivalent to the debtor terminal 3.

[0708] The conceptual diagram of information system E in this embodiment is the same as Fig. 1 except for the name and reference numeral of negotiation support device 8. Negotiation support device 8 is a server, such as a cloud server or an ASP server, but the type is not important.

[0709] A block diagram of information system E is shown in Figure 56. A block diagram of negotiation support device 8 is shown in Figure 57.

[0710] The claimant terminal 2 comprises a claimant storage unit 21, a claimant reception unit 22, a claimant processing unit 23, a claimant transmission unit 24, a claimant reception unit 25, and a claimant output unit 26. The claimant storage unit 21, the claimant reception unit 22, the claimant processing unit 23, the claimant transmission unit 24, the claimant reception unit 25, and the claimant output unit 26 perform the same processing as the creditor storage unit 21, the creditor reception unit 22, the creditor processing unit 23, the creditor transmission unit 24, the creditor reception unit 25, and the creditor output unit 26, respectively.

[0711] The respondent terminal 3 comprises a respondent storage unit 31, a respondent reception unit 32, a respondent processing unit 33, a respondent transmission unit 34, a respondent reception unit 35, and a respondent output unit 36.

[0712] The respondent storage unit 31, the respondent reception unit 32, the respondent processing unit 33, the respondent transmission unit 34, the respondent reception unit 35, and the respondent output unit 3 perform the same processing as the debtor storage unit 31, the debtor reception unit 32, the debtor processing unit 33, the debtor transmission unit 34, the debtor reception unit 35, and the debtor output unit 36, respectively.

[0713] The negotiation support device 8 includes a storage unit 81, a receiving unit 82, a processing unit 83, and a transmitting unit 84. The storage unit 81 includes a claim management unit 811. The receiving unit 82 includes a claim acquisition unit 121, a confirmation receiving unit 122, a negotiation receiving unit 123, an instruction receiving unit 124, and a transition instruction receiving unit 721. The processing unit 73 includes a claim storage unit 131, an updating 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, an information acquisition unit 139, and a transition judgment unit 731. The transmission unit 74 includes a claim notification unit 741, 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.

[0714] The complaint management unit 811 stores one or more pieces of complaint status information. The complaint status information is information related to the complaint. For example, the complaint status information is information that identifies the current phase among two or more phases from the filing of a complaint to an agreement. The agreement here refers to an agreement between the complainant and the respondent regarding the complaint's handling. The complaint status information may also be information that identifies the current phase among two or more phases from filing to an agreement. A phase is a specific state or period in the progress of complaint-related handling, from filing to an agreement or breakdown, etc. A phase may also be referred to as a step, a situation, or the like. The complaint status information is information that identifies the current stage in the activities for complaint handling, which are carried out in multiple stages. At each of the two or more stages, a different entity prompts or negotiates the activities for complaint handling. Note that different entities typically mean different entities that notify the respondent.

[0715] The petition status information can be said to be, for example, information for managing the status of a petition. The petition status information is information associated with a petition identifier. A petition identifier is information that identifies a petition. A petition identifier is, for example, a petition ID or a petition name (e.g., the name of the petition case). The petition status information includes, for example, petitioner information, respondent information, petition content information, confirmation information, negotiation information, proposal content, agreement document, phase-specific information, and various time information.

[0716] The claim status information here includes information that identifies the stage. The information that identifies the stage is, for example, a stage identifier that identifies the stage, and an entity identifier that identifies the entity that will prompt or negotiate activities to process the claim. The stage identifier may be the same information as the entity identifier. In other words, the entity may be determined once the stage is determined. The entity identifiers are, for example, "claimant," "claimant identifier," "system," "lawyer (or agent)," and "lawyer identifier (or agent identifier)." The entity identifiers "claimant" and "claimant identifier" indicate that the stage is a company prompt. The entity identifier "system" indicates that the stage is a mediation stage by the negotiation support device 8. The entity identifiers "lawyer (or agent)" and "lawyer identifier (or agent identifier)" indicate that the stage is a negotiation stage by an agent.

[0717] The petition status information includes, for example, petitioner information, respondent information, petition content information, confirmation information, negotiation information, proposal content, agreement document, stage identifier, subject identifier, phase specification information, and various time information.

[0718] Complainant information is information about the complainant. Complainant information includes, for example, a complainant identifier and one or more complainant attribute values. The complainant identifier is information that identifies the complainant. The complainant identifier is, for example, the complainant's ID, the complainant's name, the complainant's telephone number, the complainant's email address, and the IP address of the complainant terminal 2. Complainant attribute values ​​are, for example, the complainant's remittance information, the complainant's company name, the name of the complainant's company representative, and the complainant type, which indicates whether the complainant is a corporation or an individual. Remittance information is information used by the respondent to remit funds to the complainant.

[0719] Respondent information is information about the respondent. Respondent information includes, for example, a respondent identifier and one or more respondent attribute values. Respondent identifier is information that identifies the respondent. Respondent identifiers are, for example, the respondent's ID, the respondent's name, the respondent's telephone number, the respondent's email address, and the IP address of the respondent terminal 3. Respondent attribute values ​​are, for example, the respondent's contact information, the respondent's company name, the name of the respondent company's representative, the respondent's address, and the respondent type, which indicates whether the respondent 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.

[0720] 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, the claimed amount, and the original payment due date. If the claim is a request for the return of a loaned item, the claim content information includes, for example, information about the item to be returned and information specifying the return destination.

[0721] Next, an example of the operation of negotiation support device 8 will be described using the flowcharts of Figures 58 to 60. Note that in the flowcharts of Figures 58 to 60, descriptions of steps that are the same as those in Figure 4, Figure 5, Figure 44, Figure 45, or Figure 46 will be omitted.

[0722] In addition, in each flowchart from Figures 58 to 60, the "creditor terminal 2" in each flowchart from Figures 4, 5, 44 to 46, etc. is replaced with "petitioner terminal 2", "debtor terminal 3" is replaced with "respondent terminal 3", "claim identifier" is replaced with "claim identifier", "claim management unit 111" is replaced with "claim management unit 811", "creditor" is replaced with "petitioner", "debtor" is replaced with "respondent", "claim" is replaced with "claim", "claim identifier" is replaced with "claim identifier", "claim content information" is replaced with "claim content information", "claim status information" is replaced with "claim status information", etc.

[0723] In addition, in this embodiment, in the first notification processing described using the flowchart of Figure 47, the transition processing described using the flowchart of Figure 48, the second notification processing described using the flowchart of Figure 49, the third notification processing described using the flowchart of Figure 50, and the transition judgment processing described using the flowchart of Figure 51, "creditor" is replaced with "petitioner," "debtor" is replaced with "respondent," "creditor identifier" is replaced with "petitioner identifier," "debtor identifier" is replaced with "respondent identifier," "claim processing" is replaced with "claim processing," "claim management information" is replaced with "claim management information," "claim management unit 711" is replaced with "claim management unit 811," etc.

[0724] As described above, according to this embodiment, activities for processing a complaint can be supported in multiple stages, for example, two or three stages.

[0725] Furthermore, according to this embodiment, when a transition condition is satisfied in a multi-stage activity for processing a claim, the process can move to the next stage.

[0726] Furthermore, according to this embodiment, when a transition condition regarding the period until an agreement is reached is satisfied in a multi-stage activity for processing a complaint, the process can proceed to the next stage.

[0727] Furthermore, according to this embodiment, in the case of multi-stage activities for processing a claim, if a transition condition regarding negotiation information is satisfied, the process can proceed to the next stage.

[0728] The processing in this embodiment may be implemented by software. This software may be distributed by software download, etc. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software that implements the claims management device 7 in this embodiment is the following program. In other words, this program causes a computer to function as: a claim acquisition unit that acquires claim information having a claimant identifier that identifies the claimant, a respondent identifier that identifies the respondent, 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 a claim management unit in which one or more pieces of claim status information, which is information corresponding to the claim identifier that identifies the claim and includes the claim information, in association with a claim identifier that identifies the claim associated with the claim; and a claim notification unit that acquires notification information including information on the claimant identified by the claimant identifier contained in the claim information and the claim content information, and uses the notification information to perform notification processing, which is processing to notify the respondent; The complaint notification unit is a program for causing the computer to function as comprising: a first notification means that, in response to the complaint acquisition unit acquiring the complaint information, performs first notification processing to notify the respondent of first notification information from a first entity, the first notification information including information on the complainant identified by the complainant identifier contained in the complaint information and the complaint content information; and a second notification means that, after the first notification means has performed the first notification processing, performs second notification processing to notify the respondent of second notification information from a second entity different from the first entity, the second notification information including information on the complainant identified by the complainant identifier contained in the complaint information and the complaint content information.

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

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

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

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

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

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

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

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

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

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

[0739] As described above, the claim management device 7 according to the present invention has the effect of being able to support activities for claim processing at multiple stages, and is useful as a server or the like that supports claim processing.

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 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 a claim management unit that stores one or more pieces of claim status information, the claim information being information that corresponds to a claim identifier that identifies a claim and that can identify the current phase out of two or more phases from the occurrence of a claim until the creditor and debtor agree on the processing of the claim; a claim notification unit that, in response to the claim acquisition unit acquiring the claim information, acquires notification information including information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and sends the notification information to the debtor; a confirmation receiving unit that receives confirmation information regarding confirmation of the claim of the claim from the debtor terminal of the debtor; a confirmation storage unit that, in response to the confirmation receiving unit receiving the confirmation information, acquires the confirmation information to be stored and stores the confirmation information in the claim management unit in association with the claim identifier. A debt management device comprising: a negotiation receiving unit that receives negotiation information regarding negotiations between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation storage unit that stores the negotiation information received by the negotiation receiving unit in the debt management unit by correlating it with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and the debt identifier; an instruction receiving unit that receives an instruction to output debt status information from the creditor terminal or the debtor terminal; an information acquisition unit that acquires part or all of the debt status information corresponding to the output instruction from the debt management unit; and an information sending unit that transmits part or all of the debt status information acquired by the information acquisition unit to the creditor terminal or the debtor terminal.

2. A debt management device as described in claim 1, further comprising: a proposal content acquisition unit that acquires information about the creditor and the debtor from the debt management unit when the negotiation information received by the negotiation receiving unit meets 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 debt; and a proposal content transmission unit that transmits the proposal content acquired by the proposal content acquisition unit to the creditor terminal or the debtor terminal.

3. A debt management device as described in claim 2, wherein 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.

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

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

6. A debt management device as described in claim 1, further comprising: 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 that is information necessary for the debtor to process debts when the judgment unit judges that the agreement conditions have been met.

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

8. A debt management device as described in claim 1, further comprising: 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.

9. A claim management device as described in any one of claims 1 to 8, wherein the claim status information has phase-specific information that can identify the current phase out of two or more phases from the occurrence of the claim to the time when the creditor and debtor agree on the processing of the claim, and further comprises an update unit that 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.

10. A claim management method realized by a claim management unit that stores one or more pieces of claim status information, which is information related to claim processing and corresponds to a claim identifier that identifies the claim, and which can identify 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, 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, comprising: a claim acquisition step in which the claim acquisition unit acquires claim information having a creditor identifier that identifies the creditor, a debtor identifier that identifies the debtor, and claim content information related to the content of the claim; and 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 the claim that corresponds to the claim information. a petition notification step in which the petition notification unit, in response to the petition acquisition unit acquiring the petition information, acquires notification information including information on the creditor identified by the creditor identifier contained in the petition information and the claim content information, and transmits the notification information to the debtor; a confirmation reception step in which the confirmation reception unit receives confirmation information regarding confirmation of the petition for the claim from the debtor terminal of the debtor; a confirmation storage step in which the confirmation storage unit, in response to the confirmation reception unit receiving the confirmation information, acquires confirmation information to be stored and stores the confirmation information in the claim management unit in association with the claim identifier; a negotiation reception step in which the negotiation reception unit, after receiving the confirmation information, receives negotiation information regarding negotiation between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor; a negotiation storage step in which the negotiation storage unit stores the negotiation information received by the negotiation reception unit in association with the creditor identifier identifying the creditor or the debtor identifier identifying the debtor and the claim identifier in the claim management unit. 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; and an information acquiring step in which the information acquiring unit acquires part or all of the credit status information corresponding to the output instruction from the credit management unit.an information transmitting step in which the information transmitting unit transmits part or all of the debt status information acquired by the information acquiring unit to the creditor terminal or the debtor terminal.

11. A computer that can access a claims management unit that stores one or more pieces of claim status information, which is information related to claim processing and corresponds to a claim identifier that identifies a claim, and which can identify the current phase out of two or more phases from the occurrence of a claim until the creditor and debtor agree on claim processing; a claim acquisition unit that acquires claim information 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 correspondence with a claim identifier that identifies the claim corresponding to the claim information; a claim notification unit that, in response to the claim acquisition unit acquiring the claim information, acquires notification information including information on the creditor identified by the creditor identifier contained in the claim information and the claim content information, and sends the notification information to the debtor; and a confirmation receiving unit that receives confirmation information related to confirmation of the claim for 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 debt management unit in association with the debt identifier; a negotiation receiving unit that receives negotiation information regarding negotiations between the creditor and the debtor from the creditor terminal of the creditor and the debtor terminal of the debtor after the confirmation receiving unit receives the confirmation information; a negotiation storage unit that stores the negotiation information received by the negotiation receiving unit in the debt management unit in association with a creditor identifier that identifies the creditor or a debtor identifier that identifies the debtor, and the debt identifier; an instruction receiving unit that receives an instruction to output debt status information from the creditor terminal or the debtor terminal; an information acquisition unit that acquires part or all of the debt status information corresponding to the output instruction from the debt management unit; and a program that functions as an information sending unit that transmits part or all of the debt status information acquired by the information acquisition unit to the creditor terminal or the debtor terminal.

Images