JP6723856B2 - Debt management device, debt management method, debt management program - Google Patents

Description

The present invention relates to a debt management device, a debt management method, and a debt management program for executing a guarantee service that guarantees a lease contract.

Conventionally, as one type of debt guarantee business, there is one that guarantees the rent payment obligation of the lessee who has entered into a lease agreement. In the guarantee mentioned here, the guarantor is obliged to pay the rent on behalf of the renter to the lessor when the renter delays payment of the rent. The lessee is the one who pays the rent to rent the property, and the lessor is the one who receives the rent and rents the property.

In Patent Document 1, regarding the rent-related cost of a rental property, while reducing the time and effort for the resident to find a joint guarantor, the initial burden of security deposit, security deposit, key money, etc. is reduced, and the occupancy examination time is shortened,・ A system has been proposed for real estate management companies and renters to reduce the financial time burden and the risk of collection related to rent.

JP, 2016-71724, A

By the way, the guarantor takes legal measures to repay the renter if the renter does not pay the rent continuously for more than a predetermined period and fails to fulfill the contract to pay the consideration. That is, in the guarantee business, the guarantor may take legal measures on behalf of the lessor. The legal measures referred to here are delegated to lawyers who have the power to act and the lawyers act on their behalf. Although the guarantor needs to collect or prepare various documents for taking legal action, the problem is that the work is very troublesome for the guarantor. Further, not only the guarantor, but also the creditor had a similar problem when trying to take legal action.

Therefore, the present invention has been made in view of the above problems, and a debt management device capable of reducing the time and effort required when a creditor or a guarantor delegates a legal action to an attorney who does not fulfill the obligation. The purpose is to provide.

In order to solve the above problems, a debt management apparatus according to an aspect of the present invention is a debt management apparatus that collects necessary information necessary for entrusting a lawyer with a legal action for an obligor who does not perform its duties. A list information storage unit that stores list information including the name of the necessary information and contact information of the holder of the necessary information, and requests the holder to send the necessary information based on the list information. And a communication unit that performs communication for communication.

In order to solve the above-mentioned problems, a debt management method according to an aspect of the present invention is a debt management by a debt management device that collects necessary information necessary for entrusting a lawyer with a legal action for a debtor who does not fulfill its debt. A list information storing step of storing list information including a name of the necessary information and contact information of a holder of the necessary information, and the necessary information for the holder based on the list information. Communication step for performing communication for requesting delivery of

In order to solve the above problems, a debt management program according to an aspect of the present invention is a computer of a debt management apparatus that collects necessary information necessary for delegating a legal action to an obligor who does not fulfill an obligation to an attorney. A list information storage function for storing list information including the name of the necessary information and contact information of the holder of the necessary information, and requesting the holder to send the necessary information based on the list information And a communication function for performing communication for communication.

Further, in the debt management apparatus, the list information includes flag information indicating whether or not the necessary information has been sent, and the debt management apparatus further includes a determination unit that determines whether or not the necessary information has been sent. A switching unit that switches the flag information based on the determination of the determination unit may be provided.

Further, in the debt management device, re-communication is performed based on the flag information to perform communication for requesting to send the necessary information to a holder of the necessary information to which the necessary information has not been sent. It may be provided with a section.

The debt management device may further include a display unit that displays the list information.

Further, the debt management device may further include a necessary information storage unit that stores the necessary information and a necessary information sending unit that sends the necessary information stored in the necessary information storage unit.

The debt management device, the debt management method, or the debt management program according to an aspect of the present invention can reduce the burden of collecting or creating various documents for a creditor to take legal action.

It is explanatory drawing for demonstrating the concept of the guarantee work which concerns on the debt management apparatus which concerns on embodiment. It is explanatory drawing for demonstrating the process of the debt management apparatus which concerns on embodiment. It is explanatory drawing for demonstrating the process of the debt management apparatus which concerns on embodiment. It is a block diagram which shows the functional structural example of the debt management apparatus which concerns on embodiment. It is a data conceptual diagram which shows the data structural example of a contract database. It is a data conceptual diagram which shows the data structural example of a renter database. It is a data conceptual diagram which shows the data structural example of a lessor database. It is a data conceptual diagram which shows the data structural example of a message database. It is a data conceptual diagram which shows the data structural example of a nonpayment information database. It is a data conceptual diagram which shows the data structural example of list information. It is a figure which shows the example of the template of a power of attorney. It is a figure which shows the example of the template of a request letter. It is a flow chart which shows operation of a debt management device. It is a flow chart which shows operation of a debt management device. It is a flow chart which shows operation of a debt management device. It is a flow chart which shows operation of a debt management device. It is a flow chart which shows operation of a debt management device. (A), (b) is a figure which shows the example of a display of a dunning mail. FIG. 9 is a diagram showing a display example of an email requesting the transmission of necessary documents. It is a block diagram showing an example of functional composition of a debt management device.

The debt management device according to the present invention is a debt management device that collects necessary information necessary for delegating legal action to a debtor who does not fulfill its obligation, and is a holder of the necessary information and the necessary information. A list information storage unit that stores list information including information about the contact information, and a communication unit that performs communication for requesting the holder to send necessary information based on the list information.

Here, the “debtor” means a person (including a corporation) or an organization that has entered into a debt agreement with a creditor. The debtor is, for example, a renter who rents the property, but is not limited to this. In the following, the lessee 210 corresponds to the debtor. Further, the lessor 310 below corresponds to the creditor.

In addition, "legal action" means taking measures based on law such as litigation, for example, "initiating litigation" and includes, for example, "initiating litigation in the case of claim for performance of guarantee obligation". .. The example of “legal measures” is not limited to this.

Further, the "necessary information" is information required for each case for which a legal action is requested and includes information commonly required for each case and information individually required for each case. For example, when a legal action is taken as a matter based on non-compliance with a lease contract, information on the lease contract, notice of cancellation, and rent payment history is necessary information common to each case. On the other hand, the parking lot usage contract is necessary information depending on whether there is a renter who has a parking lot usage contract, and it is necessary information individually for each project. Further, the necessary information includes not only documents such as contracts but also simple information such as rent payment history information. Further, the necessary information also includes documents created by the debt management device (for example, a power of attorney or a cover letter). Note that the specific example of the necessary information shown here is an example, and the present invention is not limited to this.

Further, "collecting" means collecting necessary information in a group, receiving electronic data via a communication network, receiving the actual document if the necessary information is an actual document, or This includes receiving input of information indicating that the document has been received, and specifying necessary information stored in the debt management apparatus.

Further, here, the "debt management device" stores the list information including the name of the necessary information and the contact information of the holder of the necessary information, and based on the list information, Communication is performed to request the sending of necessary information. The debt management device is also a device that supports the business of managing the debt owed by the debtor. Here, in the business related to the management of debt contracts, for example, management of whether the debt is actually fulfilled, collecting necessary information when legal action is taken, and sending the collected necessary information to a lawyer May be included. The debt management apparatus is, for example, a computer system that manages the above-mentioned various operations, but is not limited to this. In the following, the debt management device 100 corresponds.

Further, the “name of necessary information” is information that can individually specify each of the various kinds of necessary information that exist, and means the name and identifier of the necessary information. The “necessary information name” refers to, for example, a “lease contract”, a “cancellation notice”, a “proxy letter”, or the like, but is not limited to this example.

Further, the “holder of necessary information” means a person or a device holding necessary information. For example, when the necessary information is a lease contract, the owner of the necessary information is the lessor. Further, when the necessary information is debt payment history information and the debt management apparatus holds the history information, the holder of the necessary information becomes the debt management apparatus. Note that this is an example, and the holder of the necessary information is not limited to this.

The "contact" is the contact information of the holder of the necessary information, such as the telephone number of the telephone held by the holder of the necessary information or the mail of the communication terminal held by the holder of the necessary information. The address, the address indicating the whereabouts of the holder of the necessary information, and the number or destination of the communication destination by facsimile communication held by the holder of the necessary information, are not limited to these. In the following, an email address is shown as an example.

Further, the “list information” is information that can specify the name of the necessary information and the holder of the necessary information for each of the plurality of necessary information. In the following, list information 160 corresponds.

The “list information storage unit” is a storage medium that stores the list information, and is realized by, for example, an HDD (Hard Disc Drive), an SSD (Solid State Drive), a flash memory, or the like. The example of the list information storage unit is not limited to this. The storage unit 102 corresponds to the following.

Further, “requesting for sending” means sending necessary information to the debt management device or its operator, which can be realized by sending by letter, sending by e-mail, etc., but other methods are used. May be.

The “communication unit” is for performing communication for requesting the holder to send necessary information based on the list information, and can be realized by, for example, a telephone or a communication interface for transmitting and receiving electronic mail. , But not limited to this. In the following, the communication unit 101 corresponds. Further, the “communication” here means transmitting a request for sending necessary information, and can be realized by, for example, sending a letter, calling, sending an electronic mail, etc., but is not limited to these examples.

The list information may include flag information indicating whether necessary information has been sent.
Here, the "flag information" is information indicating whether or not the necessary information has been sent. The “flag information” is also information for determining whether or not the debt management apparatus has collected the necessary information. The flag information is, for example, a binary value that can express that the necessary information has been sent by "1" or "○" and that the necessary information has not been sent by "0" or "x". Information. The flag information shown here is an example, and the present invention is not limited to this.

Further, the debt management device may further include a determination unit and a switching unit.

Here, the “determination unit” determines whether or not the necessary information has been sent, and is realized by, for example, a processor or a dedicated circuit, but the example of the determination unit is not limited to this. The control unit 104 corresponds to the following. Further, “determination” means determining whether or not necessary information has been sent. When the necessary information is received as electronic data, it is possible to judge whether or not the necessary information is sent depending on whether or not the necessary information is received. In addition, when the necessary information is received as an actual document, the judgment is made by inputting the information indicating that the necessary information has been received and the input of the electronic data of the document indicating the necessary information. However, these judgment examples are merely examples.

The “switching unit” switches flag information based on the determination of the determination unit, and is realized by, for example, a processor or a dedicated circuit, but the example of the switching unit is not limited to this. The control unit 104 corresponds to the following. Further, “switching flag information” means changing the flag information to information indicating that the necessary information has been sent when the flag information indicates that the necessary information has not been sent.

The debt management device may further include a recommunication unit.

The "re-communication unit" performs communication based on the flag information so as to request the holder of the necessary information for which the necessary information has not been sent, to send the necessary information. It can be realized by a communication interface for sending and receiving mail, but is not limited to this. In the following, the communication unit 101 corresponds. In other words, the re-communication unit reminds the holder of the necessary information to send the necessary information.

The debt management device may further include a display unit.

Here, the “display unit” displays the list information and is, for example, a monitor realized by an LCD or an organic EL display, but is not limited to this. In the following, an example is shown in which a monitor is connected to the debt management apparatus 100 and displayed. Further, here, “display” means to draw and output an image on a monitor, and specifically, to draw list information.

The debt management device may further include a necessary information storage unit.

The “necessary information storage unit” is a storage medium that stores necessary information, and is realized by, for example, an HDD (Hard Disc Drive), an SSD (Solid State Drive), a flash memory, or the like. The example of the section is not limited to this. The storage unit 102 corresponds to the following. In addition, “storage” means accumulating information in a storage medium.

The "necessary information sending unit" sends the necessary information stored in the necessary information storage unit, and can be realized by, for example, a telephone or a communication interface for sending and receiving electronic mail, but is not limited to this. In the following, the communication unit 101 corresponds. Further, "sending" means sending electronic data or actual documents to a destination, for example, sending a letter containing necessary information, sending electronic data of necessary information by e-mail, etc. It is not limited to this.

Hereinafter, as a debt management apparatus according to an aspect of the present invention, a debt management apparatus used in a guarantee business that guarantees a lease contract will be described as a specific example with reference to the drawings.

<Embodiment>
<Structure>
FIG. 1 is a conceptual diagram conceptually showing the system form of the guarantee work related to the debt management device 100. The debt management device 100 according to the present embodiment guarantees a lease contract exchanged between the lessor 310 and the lessee 210. Specifically, the lessee 210 makes a contract with the lessor 310 to rent the property 500 owned by the lessor 310 (or having the right to rent). As the lease contract, for example, it is assumed that the lessee 210 has a right to use the property 500 by paying a fixed rent (for example, 100,000 yen) regularly (for example, on a monthly basis). .. Here, the debt management device 100 guarantees to the lessor 310 that the lessee 210 regularly pays the rent as defined in the contract. Therefore, the guarantee management operator relating to the debt management device 100 pays the rent to the lessor 310 on behalf of the lessee 210 when the lessee 210 delays payment, or causes the lessee 210 to make payment. This guarantees the lessor 310. Further, when the debt management apparatus 100 pays the rent to the lessee 310 on behalf of the lessee 210, the debt management apparatus 100 charges the lessee 210 for the rent that has been reset.

Therefore, as a part of the guarantee operation, the debt management device 100 (1) calls the lessor 310 when the lessee 210 fails to pay the rent within the period defined by the contract. The debt management device 100 legally informs the lessee 210 when an e-mail is sent to the terminal 200 of the lessor 310 or (2) the lessee 210 delays payment and meets a predetermined condition. A process for delegating the measure to the lawyer 410 is executed.

Here, of the processes executed by the debt management device 100 according to the present embodiment, the above (1) will be described in detail. FIG. 2 is a conceptual diagram showing a process of sending a reminder e-mail for urging (requesting) a telephone call to a lessee in the guarantee work executed by the debt management device 100.

In FIG. 2, T0 to T1, T1 to T2, and T2 to T3 are set as predetermined periods A, B, and C, respectively. The predetermined periods A, B, and C are, for example, one month units from the date when the lessee 210 makes a lease contract with the lessee 310 as a starting date. It should be noted that the predetermined period may be the start date on the first day of January, or may be a predetermined predetermined day as the start date. The length of the predetermined period is not limited to one month, and may be a unit such as one week, two months, half a year, or one year.

Then, it is assumed that the content of the lease contract is to pay the rent for renting the property 500 during the predetermined period within the predetermined period. In the lease contract, if agreement is made between the lessee 210 and the lessor 310, it may be stipulated that the rent for a predetermined period be paid in the next predetermined period, or by the end of the next predetermined period. You may pay.

In FIG. 2, the lessee 210 pays the rent for the predetermined period A to the lessor 310 at t1. In addition, the lessee 210 pays the rent for the predetermined period B to the lessor 310 at t2. However, it is assumed that the rent for the predetermined period C is not paid from the lessee 210 to the lessor 310 during the predetermined period C.

Then, non-payment information indicating that the renter 210 has not paid the rent from the lessor 310 to the debt management apparatus 100 is transmitted to the debt management apparatus 100. Here, the nonpayment information may be configured to be transmitted by a consignor entrusted by the lessor 310 to manage the rent.

Upon accepting the non-payment information, the debt management device 100 sends a reminder mail requesting a telephone call to the lessee 210 indicated by the non-payment information. Accordingly, when the lessee 210 makes a call, it is possible to inquire about the circumstances. The debt management device 100 according to the present embodiment automatically transmits a reminder mail, reduces the processing load related to the guarantee work, and allows the lessee to make a call in response to the reminder mail. Try not to concentrate as much as possible.

Next, the process (2) will be described with reference to FIG. FIG. 3 shows a case in which the cases shown in FIG. 2 are connected in time series. As shown in FIG. 3, it is assumed that the lessee 210 neglects to pay the consideration (rent) in the predetermined period C and then fails to pay the consideration until the predetermined period F. Meanwhile, the lessor 310 transmits the nonpayment information from the terminal 300 to the debt management apparatus 100, and the debt management apparatus 100 transmits a reminder mail requesting a telephone call to the terminal 200 of the lessee 210.

Then, when the lessee 210 fails to pay the consideration for a fixed number of predetermined periods (here, 4), that is, when the rent for four months is delinquent, the debt management device 100 asks the lawyer. Ask legal counsel for legal action by preparing the necessary documents for delegating legal action. As a part of that, for example, as shown at t5 in the predetermined period G, the debt management device 100 provides the terminal 300 of the lessor 310 with one of the documents necessary for taking legal action. Send an email asking you to send it. Alternatively, or alternatively, the debt management device 100 creates a power of attorney for requesting the lawyer 410 a lawsuit relating to a claim for compensation by the guarantor when the guarantor restores the rent of the renter.

The lessor 310 confirms the request to send the received lease contract, and sends the held lease contract to the guarantor relating to the debt management device 100. The guarantor collects necessary documents such as a lease contract from the lessor 310, and uses the debt management device 100 to create a request letter for requesting legal action to the lessee 210. Then, the guarantor sends the created request letter together with the necessary documents to the lawyer 410.

Upon receiving a request from the guarantee business operator, the lawyer 410 is transferred with the authority regarding the debt of the lessee 210 and executes the processing relating to the legal action for the lessee 210. The debt management apparatus 100 according to the present embodiment is mainly intended to reduce the processing burden on the guarantor by collecting various documents necessary for delegating legal action to a lawyer.
Details of the debt management apparatus 100 will be described below.

FIG. 4 is a block diagram showing an example of the functional configuration of the debt management apparatus 100. As shown in FIG. 4, the debt management device 100 includes a communication unit 101, a storage unit 102, an input receiving unit 103, and a control unit 104. The debt management device 100 is a device that provides information for entrusting a lawyer with a legal action for a debtor who does not fulfill its debt.

The communication unit 101 has a function of performing communication with external devices (the terminal 200 of the lessee 210, the terminal 300 of the lessor 310, the terminal 400 of the lawyer 410, etc.). The communication unit 101 is a non-payment information indicating that the transmission unit that transmits an e-mail requesting a telephone call and the lessee have not paid the consideration (rent) in the time period determined according to the instruction from the control unit 104. Functions as a receiving unit that receives the. The communication unit 101 is not limited to wired or wireless communication as long as it can communicate with an external device. The communication protocol used for communication is not limited to any standard as long as it can communicate with an external device.

In accordance with the instruction from the control unit 104, the communication unit 101 transmits an email requesting a call to the terminal 200 of the lessee 210. In addition, the communication unit 101 indicates that the lessee 210 neglects to pay the rent from the terminal 300 of the lessor 310 or the terminal (not shown) of a company that manages the rent in response to a request from the lessor 310. The non-payment information is received and the non-payment information is transmitted to the control unit 104. Here, the non-payment information is assumed to include at least a renter ID that identifies the renter 210 and period information that identifies the period in which the non-payment is made, and is transmitted for each period in which the non-payment is made. And In addition, the communication unit 101 paid the rent for the period in which the lessee 210 was not paying, from the terminal 300 of the lessor 310 or the terminal of the dealer who manages the rent at the request of the lessor 310. The payment information indicating that is received, and the payment information is transmitted to the control unit 104. Here, it is assumed that the payment information includes at least a renter ID that identifies the renter 210, and is transmitted for each payment period. For example, if the renter has failed to pay the rent for four months and has paid the rent for three months, three pieces of payment information are transmitted.

The storage unit 102 is a storage medium having a function of storing various programs and data required for the debt management apparatus 100 to operate. The storage unit 102 can be realized by a storage device such as an HDD (Hard Disc Drive), SSD (Solid State Drive), or flash memory. The storage unit 102 stores a contract database 110, a lessee database 120, a lessor database 130, a message database 140, a nonpayment information database 150, and list information 160. The contract database 110 is information indicating that a lease contract is made by associating information indicating a renter with information indicating a renter. The renter database 120 is information on the attributes of the renter. The attributes mentioned here indicate characteristics of the renter, and include various things such as name, sex, age, and personality. The lessor database 130 is information regarding the attributes of the lessor. The property of the lessor here indicates the characteristics of the lessor, and includes various things such as name, sex, and address. The message database 140 is a database that shows the text of the body of an email that demands a telephone request from the debt management apparatus 100 to the lessee 210. The non-payment information database 150 is information for managing the renter who is not paying, among the renters. The list information 160 is information indicating various documents required when requesting a lawyer for a legal action regarding debt, and is a check list used for determining whether or not each information can be collected. Details of the contract database 110, the lessee database 120, the lessor database 130, the message database 140, the nonpayment information database 150, and the list information 160 will be described later.

Further, the storage unit 102 stores template information of a power of attorney sent to the lessor 310 and template information of a request letter sent to the lawyer 410. Details of the proxy letter template information and the request letter template information will be described later.

The input receiving unit 103 has a function of receiving an input from an operator of the debt management apparatus 100. The input receiving unit 103 can be realized by, for example, a character input device such as a keyboard or a pointing device such as a mouse. The input receiving unit 103 has a function of transmitting the input content received from the operator to the control unit 104.

The control unit 104 is a processor having a function of controlling each unit of the debt management apparatus 100. The control unit 104 controls each unit of the debt management apparatus 100 by executing the control program stored in the storage unit 102. The control unit 104 functions as a determination unit that determines whether or not necessary information has been sent, and a switching unit that switches flag information included in the list information 160 based on the determination of the determination unit.

When the non-payment information is transmitted from the communication unit 101, the control unit 104 identifies the renter ID indicated by the non-payment information, and adds 1 to each of the unpaid number 122e and the total delay number 122f for the renter. , Renter database 120 is updated. Further, the control unit 104 registers and updates the lessee ID indicated by the nonpayment information in the nonpayment information database 150 together with the date and time when the nonpayment information was received.

When the payment information is transmitted from the communication unit 101, the control unit 104 identifies the renter ID indicated by the payment information, and detects information corresponding to the renter ID and the corresponding period from the non-payment information database 150. Then, the control unit 104 updates the payment date and time 156 corresponding to the detected renter ID and the corresponding period by registering the reception date and time of the payment information in the non-payment information database 150.

When the start timing of the predetermined period relating to the transmission of the dunning email arrives, the control unit 104 determines the timing (time zone) for transmitting the dunning email, and the dunning email when the timing (time zone) arrives. And a transmission process for transmitting. Here, the predetermined period relating to the transmission of the dunning email is, for example, between 10:00 and 15:00 in one day, and the time period for transmitting the dunning email is from 10:00 to 11:00 and from 11:00 to 12:00. , 12:00 to 13:00, 13:00 to 14:00, and 14:00 to 15:00. It should be noted that the setting of this time zone is an example, and the number thereof is also an example.

The control unit 104 refers to the non-payment information database 150 to identify the other party to whom the dunning mail is transmitted. The control unit 104 identifies the lessee ID corresponding to the data for which the date and time information is not registered at the payment date and time in the non-payment information database 150, as the other party to whom the dunning mail is transmitted. Then, the control unit 104 identifies the mail address corresponding to the renter ID by referring to the renter database 120. Further, the control unit 104 identifies the unpaid number 122e and the total delay number 122f corresponding to the renter ID by referring to the renter database. Then, based on the identified unpaid number 122e and the total delay number 122f, the control unit 104 refers to the message database 140 and identifies the corresponding message content 142. Then, the control unit 104 generates, for each lessee, a reminder e-mail in which the specified message content is the text and the destination is the specified e-mail address.

The control unit 104 counts the total number of lessees who should send the specified dunning mail from the nonpayment information database 150. Then, the control unit 104 divides the counted total number by the total number of time periods for transmitting the dunning mail (here, 5). When the counted total is not divisible by the number of time zones, the control unit 104 distributes the remainder to any of the time zones and determines the number of mails to be transmitted in each time zone. For example, when the counted total number is “107”, the debt management device 100 determines that each time zone (10:00 to 11:00, 11:00 to 12:00, 12:00 to 13:00, 13:00 to 14:00, A minimum of 21 reminder emails are sent during each time period from 14:00 to 15:00), and the remaining two reminder emails are added one by one from the earliest one in each time zone. Therefore, in this example, the debt management apparatus 100 is 22 from 10:00 to 11:00, 22 from 11:00 to 12:00, 21 from 12:00 to 13:00, 21 from 13:00 to 14:00, and 14:00 from 15:00. Send 21 reminder emails. The 22 messages transmitted from 10:00 to 11:00 may be transmitted in any manner during the time period from 10:00 to 11:00, for example, 22 messages may be collectively transmitted at 10:00. Alternatively, half of the 22 copies at 10 o'clock may be transmitted and the other half at 10:30. Alternatively, 60 minutes may be divided by the number of mails to be sent, and the number of mails to be sent may be sequentially sent as the sending interval of the mails. It may be sent in batch or collectively. For example, when 2400 messages are transmitted in 60 minutes, 40 messages may be transmitted every minute. Then, the control unit 104 allocates each generated dunning mail to each time slot so that the number of mails to be transmitted in each time slot is reached. In the present embodiment, which reminder email is assigned to which time zone is randomly determined. As a result, the number of reminder emails to be sent in one time zone can be suppressed, and the number of calls made from the lessee's terminal in accordance with the reminder emails sent can also be suppressed. It is possible to reduce the possibility that the business operator cannot answer the phone.

Further, the control unit 104 refers to the unpaid number 122e of the renter database 120 and detects whether or not there is data whose number is a predetermined number or more (here, four or more). When the control unit 104 detects data in which the number of unpaid times 122e is four or more, the control unit 104 identifies the corresponding lessee ID. Then, the control unit 104 collects necessary information for delegating legal action to a lawyer for the lessee corresponding to the identified lessee ID. The control unit 104 reads out list information 160 indicating necessary information for delegating legal action to a lawyer from the storage unit 102. Here, the necessary information for delegating legal measures to a lawyer may differ depending on the individual case. That is, necessary information for delegating legal measures to lawyers includes information common to each case and information required individually for each case. For example, when a guarantor who has signed a guarantee contract based on a lease contract takes legal measures, the lease contract, notice of cancellation, and rent payment history information are common to each case and are necessary for legal measures. However, the guarantor may not hold any of the information that is owned by the lessor. Such information is information that the guarantor needs to collect as information common to each case. On the other hand, the parking lot usage contracts are not common to each project because some renters have signed a parking lot usage contract and others do not. Information. The control unit 104 transmits, via the communication unit 101, to a person or a group holding each piece of information included in the list information 160, an email requesting that the information be sent. Then, when an input indicating that each piece of information has been collected is received from the operator of the debt management apparatus 100 via the input receiving unit 103, the flag of the corresponding required document is switched to a value indicating collection completion. When all the flags of the list information 160 indicate collection completion, the control unit 104 outputs information indicating that collection of necessary information is completed to the terminal 400 of the lawyer 401. If the flag does not switch to a value indicating collection completion even after waiting for a predetermined period (for example, one week), the control unit 104 sends an email requesting the delivery of the document to the person or group holding the corresponding required document. Send again. Note that the control unit 104 may appropriately output the list information 160 as information indicating the collection status of each document. Although not shown, the output method may be realized by displaying on a monitor connected to the debt management apparatus 100, or by transmitting each information to an external device via the communication unit. It may be realized.

As a part of collecting the necessary information, the control unit 104 creates a power of attorney indicating that the lessor delegates the authority regarding the debt to the lawyer and sends it to the lessor. Specifically, the lessor ID that rents the property rented by the lessee is identified from the identified lessee ID by referring to the contract database 110. From the lessor ID specified by referring to the contract database, the control unit 104 refers to the lessor database 130 to specify the mail address of the lessor indicated by the lessor ID. Then, the control unit 104 generates a mail addressed to the specified mail address.

The control unit 104 creates a power of attorney to be attached to this mail by using the power of attorney template information stored in the storage unit 102. The control unit 104 appropriately adds each of the lessor information, the lessee information, and the rental property information to the power of attorney template information to create a power of attorney.

The renter information is the name of the renter who is behind on rent. The control unit 104 acquires the renter information from the name 122a of the renter database 120.

The lessor information is the name of the lessor who rents the property, and is the entity that delegates legal measures for the lessee to the guarantor relating to the debt management device 100. The control unit 104 acquires the lessor information from the name 132a of the lessor database 130.

The rental property information is the name and address of the property rented between the lessee and the lessor. The control unit 104 acquires rental property information from the property name 113a and address 113c of the contract database 110.

The control unit 104 attaches the power of attorney created by adding various types of information to the template, and sends the power of attorney via the communication unit 101.

In addition, when the control unit 104 receives an input of a request letter creation instruction from the operator of the debt management apparatus 100 via the input acceptance unit 103, the control unit 104 accepts the specification of the lease contract data and creates the request letter. The control unit 104 receives the designation of the lease contract data and extracts the lessor ID, the lessee ID, and the property information in the contract database 110. Then, based on the extracted information, a request letter is created with reference to the lessee database 120 and the lessor database 130. Then, the control unit 104 outputs the created request letter to an external device (for example, a printer (not shown)) via the communication unit 101.

The above is the configuration of the debt management apparatus 100.

<Data>
From here, various data related to the debt management apparatus 100 will be described.

FIG. 5 is a data conceptual diagram showing a data configuration example of the contract database 110. As shown in FIG. 5, the contract database 110 is information in which a lessee ID 111, a lessor ID 112, and property information 113 are associated with each other. The contract database 110 is information indicating that the renter indicated by the renter ID 111 and the renter indicated by the renter ID 112 have a lease contract for the property indicated by the corresponding property information 113. Is.

The renter ID 111 is identification information for the debt management device 100 to uniquely identify a person (or some group) who rents the property.

The lessor ID 112 is identification information for uniquely identifying a person (or some group) who owns the property and who rents the property to the corresponding lessee ID 111.

The property information 113 is information on properties rented between the renter indicated by the corresponding renter ID 111 and the renter indicated by the renter ID 112. The property information 113 includes a property name 113a, a rent 113b, and an address 113c.

The property name 113a is the name of the property rented between the lessee and the lessor.

The rent 113b is information indicating the price (rent) paid by the lessee to borrow the corresponding property name 113a from the lessor.

The address 113c is the address of the property indicated by the property name 113a, and is information indicating the location.

In the example of FIG. 5, the person whose renter ID 111 is “AAA” is rented by the person whose tenant ID 112 is “aaa” from “A Heights” in “Shibuya-ku, Tokyo...” Understand that you are renting for "5,000 yen". New data is added to the contract database 110 each time the guarantor relating to the debt management device 100 receives a guarantee for a new lease contract, and may be deleted when the lease contract is canceled between the parties. With the contract database 110, the debt management device 100 can recognize the contract between the lessee and the lessor.

FIG. 6 is a data conceptual diagram showing a data configuration example of the lessee database 120. As shown in FIG. 6, the renter database 120 is information in which the renter ID 121 and the renter attribute information 122 are associated with each other. The renter database 120 is information that defines information (attributes) relating to renters.

The renter ID 121 is identification information for the debt management device 100 to uniquely identify a person (or some group) who rents the property. The renter ID 121 and the renter ID 111 shown in FIG. 5 use the same identification information when indicating the same person (or group).

The renter attribute information 122 is information indicating attributes related to the renter indicated by the renter ID 121, and includes a name 122a, a gender 122b, an age 122c, an annual income 122d, an unpaid number 122e, and a total delay number 122f. It includes a mail address 122g and a telephone number 122h.
The name 122a is information indicating the name of the lessee.
The gender 122b is information indicating the gender of the lessee.
The age 122c is information indicating the age of the lessee.
The annual income 122d is information indicating the annual income of the lessee.

The unpaid number 122e is information indicating the number of times that the debtor has not yet fulfilled the obligation in the period in which the lessee did not pay the consideration to be paid in each predetermined period within the predetermined period. The unpaid number 122e is subtracted by the number of debts according to the amount paid by the control unit 104 when the lessee who has been delayed in payment has paid. Specifically, the control unit 104 subtracts “1” from the corresponding unpaid number 122e every time the payment information indicating that the payment is made is accepted.

The total number of delays 122f is information indicating the total number of times that the lessee did not pay the consideration to be paid in each predetermined period within the predetermined period. The total delay count 122f is incremented by "1" by the control unit 104 every time the nonpayment information about the corresponding lessee is accepted.

The mail address 122g is information indicating the address of the electronic mail set in the terminal owned by the lessee.

The telephone number 122h is information indicating the telephone number set on the telephone held by the lessee.

In the example of FIG. 6, the renter with the renter ID 121 of “AAA” has a name 122a of “Andrew”, a sex 122b of “male (M)”, and an age 122c of “23”. I'm old. Further, the annual income 122d of "Andrew" is "3.5 million yen", and the number 122e of unpaid payments is "4 times" at present, which means that the rent for four months is delinquent. Also, the total delay number 122f is "32 times", the email address 122g of the "Andrew" terminal is "AAA@docono.com", and the telephone number 122h is "090-0598-AAAA". Can understand. The renter database 120 is added when a new leasing contract is registered in the contract database 110 and a corresponding renter is not registered in the renter database 120. The information of the lessee is added by the operator of the debt management apparatus 100 via the input reception unit 103.

FIG. 7 is a data conceptual diagram showing a data configuration example of the lessor database 130. As shown in FIG. 7, the lessor ID 131 and the lessor attribute information 132 are associated with each other. The lessor database 130 is information that defines information (attributes) related to the lessor.

The lessor ID 131 is identification information for the debt management device 100 to uniquely identify a person (or some group) who rents the property. When the lessor ID 131 and the lessor ID 112 shown in FIG. 5 indicate the same person (or group), the same identification information is used.

The lessor attribute information 132 is information indicating attributes relating to the lesser indicated by the lessor ID 131, and includes a name 132a, a mail address 132b, a telephone number 132c, and an address 132d.
The name 132a is information indicating the name of the lessor.

The mail address 132b is information indicating the address of the electronic mail set on the telephone owned by the lessor.

The telephone number 132c is information indicating the telephone number set on the telephone held by the lessor.
The address 132d is information indicating the address of the lessor.

In the example of FIG. 7, the lessor with the lessor ID 131 of “aaa” has the name 132a of “Alex”. The email address 132b of the "Alex" terminal is "aaa@bzweb.ne.jp", the telephone number is "090-2342-aaa", and the address is "Minato-ku, Tokyo...". Can understand. The lessor database 130 is added when a new lease contract is registered in the contract database 110 and a corresponding lessor is not registered in the lessor database 130. The information of the lessor is added by the operator of the debt management apparatus 100 via the input reception unit 103.

FIG. 8 is a data conceptual diagram showing a data configuration example of the message database 140. As shown in FIG. 8, the message database 140 is information in which the delay condition 141 and the message content 142 are associated with each other. The message database 140 is information defining the content of the text of the dunning mail.

The delay condition 141 is information indicating a condition in which the renter is delaying payment of the rent (consideration), and here, a condition based on at least one of the total number of delays and the number of unpaid times is shown. When there are multiple conditions, when each condition is connected by and, it indicates that all the conditions are satisfied, and when each condition is connected by or, one of the multiple conditions is satisfied. It shows the case.

The message content 142 is information indicating the message content of the dunning mail transmitted by the debt management apparatus 100, that is, the content of the mail body according to the condition indicated by the delay condition 141.

In the example of FIG. 8, if the number of times the renter has delayed payment of rent (consideration), that is, the total number of delays is "5" and the number of unpaid times is "1", The content of the text of the e-mail sent is "I am a renter, XX guarantee company. Can you call 090-XXX-XXXX once? Thank you." ing. Here, the name of the renter is inserted in "the renter". The message database 140 is set so that the more the renter delays payment of the consideration, the more stringent the message content for the renter.

FIG. 9 is a data conceptual diagram showing a data configuration example of the non-payment information database 150. As shown in FIG. 9, in the nonpayment information database 150, the lessee ID 151, the reception date and time 152, the reminder mail transmission date and time 153, the nonpayment period 154, the telephone reception date and time 155, and the payment date and time 156 are associated with each other. It is the information provided. The non-payment information database 150 is information about the results of non-payments made by the lessee.

The renter ID 151 is identification information indicating a renter who has delayed payment of consideration. If the renter ID 151 is the same person, the same identification information as that of the renter ID in FIGS. 2 and 2 is used.

The reception date/time 152 is information indicating the date/time when the non-payment information was received.

The dunning e-mail transmission date and time 153 is information indicating the date and time when the dunning e-mail for reminding the telephone is transmitted. If the dunning mail has not been sent yet, the data will be blank. In FIG. 6, empty data is indicated by “-”. The dunning email transmission date and time 153 is information indicating the date and time when the dunning email was last transmitted.

The non-payment period 154 is information indicating a period in which the lessee has made a non-payment.

The telephone reception date and time 155 is information indicating the date and time when the lessee received a telephone call after sending the dunning mail. The telephone reception date and time 155 is information input by the operator of the debt management apparatus 100 via the input reception unit 103. The telephone reception date and time 155 is input every time there is a telephone call from the lessee.

The payment date/time 156 is information indicating the date/time when the corresponding lessee paid the consideration. As long as the payment date/time 156 does not include date/time information, the debt management apparatus 100 sends a reminder e-mail at regular intervals.

In the example of FIG. 9, the renter whose ID 151 is “AAA” could not pay the rent for “June 2016” by the end of May, so the debt management device 100 We will receive the non-payment information at 10:00 on June 1, 2016. In accordance with the non-payment information, the debt management device 100 sends a reminder mail at “10:00 on June 2, 2016”. In response to the reminder e-mail, the lessee makes a phone call to the company relating to the debt management device 100 on "June 2, 2016", and pays the rent on "June 2, 2016 19:38". Understand that you are making payments.

FIG. 10 is a data conceptual diagram of list information 160 showing information (documents) necessary for delegating legal measures to a lawyer. As shown in FIG. 10, the list information 160 is information in which a necessary information (document) name 1001, an information holder 1002, and flag information 1003 are associated with each other. The list information 160 may be prepared in advance, or may be created by receiving the input of the information (document) name 1001 and the information regarding the information holder 1002 from the operator at an appropriate timing.

The required information (document) name 1001 is information that can uniquely identify the information and documents required for delegating legal action to an attorney, and here the name of the information is shown for the sake of clarity. .. The information does not have to be a name, and may take a form other than the name as long as the information can uniquely identify each document. For example, identification information uniquely attached to the document name may be used.

The information holder 1002 is information indicating a person or a group holding corresponding necessary information (documents). Here, the person may include a corporation and the like. The control unit 104 collects necessary information (documents) corresponding to the information holder 1002, or executes a process for collection (for example, email transmission of a document delivery request).

The flag information 1003 is flag information indicating whether corresponding necessary information (document) has been collected. FIG. 10 shows the list information 160 in the initial state, and shows “0” as the information indicating that the collection has not been completed. When the list information 160 can be collected, the information indicating that the collection has been completed by the control unit 104. Is switched to "1". Note that, here, the flag information 1003 is expressed by “1” and “0”, but this is not the only case, and other information can be provided as long as it can be specified whether or not necessary information (documents) has been collected. It may be realized by the expression. The flag information 1003 indicates that necessary information (documents) can be obtained when the control unit 104 can extract corresponding necessary information (documents) from the storage unit 102, or from the operator of the debt management apparatus 100 via the input reception unit 103. When the input indicating that the collection has been completed is accepted, the control unit 104 switches from “0” to “1”.

By displaying the list information 160 on the display unit, the operator can confirm the list information 160, and by checking the progress of collecting the necessary information, the operator can manage the progress of collecting the necessary information. Further, when the operator confirms the list information 160 and finds that all necessary information is gathered, the operator knows when to send the document to the lawyer. Here, the display by the display unit may be a display on a monitor provided in the debt management apparatus 100, a display on a monitor connected to the debt management apparatus 100, or a display held by an operator. It may be displayed on the monitor of the terminal.

FIG. 11 is an example of the proxy template information. The power of attorney template information is image data to which the debt management apparatus 100 can write data. As shown in FIG. 11, the power of attorney 1100 includes, as the trustee information, a trustee address 1101 and a trustee name 1102, a body 1103, and a target person 1104 as information of a person or an organization to be legally acted, The property name 1105 and the property address 1106, and the delegator information include a date column 1107, a delegator name 1108, and a delegator address 1109.

The beneficiary address 1101 is the information of the beneficiary, and is the address of a lawyer who requests a legal action from the debt management apparatus 100.

The beneficiary name 1102 is the name of the beneficiary, and is the name of a lawyer who requests a legal action from the debt management apparatus 100.

The text 1103 is the text of the power of attorney, and is the information described in advance.

The target person 1104 is the name of the person or group whose guarantor relating to the debt management device 100 is the legal subject and whose rent has been delinquent for a predetermined period or longer. As the target person 1104, the name 122a of the data in which the unpaid number 122e of the lessee database 120 exceeds 4 is used.

The property name 1105 is the property that the person indicated by the target person 1104 is renting, and the property whose rent is delinquent. For the property name 1105, the property name 113a of the contract database 110 is used based on the renter ID 121 specified from the data in which the unpaid number 122e exceeds 4 times.

The property address 1106 is the address of the property indicated by the property name 1105. As the property address 1106, the address 113c of the contract database 110 is used.

The date column 1107 is a section filled in by the delegator, and is a column in which the date on which the delegator signs is entered. The date column 1107 is described in the power of attorney 1100 in advance.

The delegator's name 1108 is the name of the person who performs the delegation, and in the example of the present embodiment, the guarantor is a guarantor for the guarantee of the lease contract (rebuilding the rent). To do. The delegator's name 1108 identifies the lessor ID 112 associated in the contract database 110 based on the lessee ID 121 identified from the data in which the unpaid number 122e exceeds 4 times, and assigns it to the identified lessor ID 112. Based on this, the name 132a of the lessor database 130 is used. If the lessor delegates to a lawyer, the lessor becomes the delegator.

The delegator address 1109 is the address of the person indicated by the delegator name 1108. As the delegator address 1109, the address 132d of the lessor database 130 is used.

As described above, the power of attorney 1100 is composed of the contents described in advance or the information that can be acquired from the data held by the debt management apparatus 100. Therefore, the debt management apparatus 100 uses the template information of the power of attorney 1100. , Can automatically create a power of attorney. The power of attorney 1100 shown in FIG. 11 is an example, and it goes without saying that the content thereof changes depending on the subject of the delegation and the content of the legal measure.

FIG. 12 is an example of template information of a request letter. The request template information is image data in which the debt management apparatus 100 can write data. As shown in FIG. 12, the request letter 1200 includes a date column 1201, a destination column 1202, a requester column 1203, a body 1204, a target person or group 1205, a lessor 1206, a lessee 1207, and a property. First name 1208.

The date column 1201 is a column for inputting a date for transmitting the request letter 1200 input by the control unit 104.

The destination column 1202 is a destination to which the request letter is transmitted, is a destination relating to the lawyer 410 with which the debt management apparatus 100 is affiliated, and is a matter described in advance.

The client column 1203 is information relating to the guarantor relating to the debt management device 100, and is a matter described in advance.

The body 1204 is a sentence indicating the content of a request for taking legal action, and is a matter described in advance.

The target person or group 1205 is a person or group that is a legal target. For the target person or group 1205, the name 122a of the lessee database 120 is used based on the lessee ID input from the operator of the debt management apparatus 100.

The lessor 1206 is information indicating the person who rented the property to the person or group indicated by the target person or group 1205. For the lessor 1206, the name 132a obtained by referring to the lessor database 130 by using the lessor ID in the contract database 110 specified from the input lessor ID is used.

The renter 1207 is the name of the same person or group as the target person or group 1205, and is the name of the person or group renting the property.

The property name 1208 is the name of the property that the lessee indicated by the lessee 1207 has rented from the lessee indicated by the lessor 1206. As the property name 1208, the property name 113a of the contract database 110 specified from the input lessee ID is used.

As described above, the debt management device 100 can create a request letter, so that the work burden on the guarantor can be reduced. The request letter shown in FIG. 12 is also an example.

The above is the description of the data relating to the debt management apparatus 100.

<Operation>
From here, operation|movement of the debt management apparatus 100 which concerns on this Embodiment is demonstrated using the flowchart of FIGS. 12-15. FIG. 12 is a flowchart showing the operation of the debt management device 100 when receiving the nonpayment information and the payment information.

As shown in FIG. 13, the communication unit 101 of the debt management device 100 receives a signal from an external device. The communication unit 101 identifies what the received signal is by checking the header of the signal. When the received signal is the nonpayment information (YES in step S1301), the communication unit 101 transmits the nonpayment information to the control unit 104.

The control unit 104 extracts the lessee ID from the transmitted non-payment information. Then, the control unit 104 searches the renter database 120 based on the renter ID extracted from the nonpayment information. Then, the renter database 120 is updated by adding 1 to each of the unpaid number 122e and the total delay number 122f of the retrieved data, that is, the data corresponding to the renter ID of the nonpayment information (step S1302). ).

Next, the control unit 104 extracts the lessee ID and the nonpayment period from the transmitted nonpayment information. The control unit 104 newly registers the extracted lessee ID in the lessee ID 151 of the nonpayment information database 150. The control unit 104 registers the nonpayment period extracted from the nonpayment information in the nonpayment period 154 of the nonpayment information database 150 in association with the registered lessee ID. Then, the control unit 104 registers the date and time when the nonpayment information was received in the reception date and time 152 in association with the registered lessee ID (step S1303), and returns to step S1301.

In step S1301, if the received signal is not the nonpayment information (NO in step S1301) but the payment information (YES in step S1304), the communication unit 101 transmits the received payment information to the control unit 104. .. If it is not the payment information (NO in step S1304), the process returns to step S1301 and waits until the next signal is received.

The control unit 104 extracts the lessee ID from the transmitted payment information. Then, the control unit 104 searches the renter database 120 based on the renter ID extracted from the payment information. Then, the unpaid number 122e of the retrieved data, that is, the data corresponding to the renter ID of the payment information is subtracted by "1" to update the renter database 120 (step S1305).

The control unit 104 extracts the renter ID and the non-payment period from the transmitted payment information. The control unit 104 detects data corresponding to the extracted renter ID and nonpayment period from the nonpayment information database 150. Then, the date and time when the payment information is received is added to the payment date and time 156 of the retrieved data to update the non-payment information database 150 (step S1306), and the process returns to step S1301.

The above is the operation of the debt management device 100 when receiving the non-payment information or the payment information.

Next, an operation when the debt management device 100 transmits a telephone reminder mail will be described. FIG. 14 is a flowchart showing the operation of the debt management device 100 when transmitting a telephone reminder mail to a lessee who has not paid the consideration.

As shown in FIG. 14, the control unit 104 of the debt management device 100 determines whether or not the timing of sending the dunning mail has arrived based on the schedule (step S1401). The schedule is preliminarily set to start at a predetermined time (for example, every day) for each predetermined period (for example, every day), and the control unit 104 is a clock provided in the debt management apparatus 100. Thus, it is determined whether or not the transmission timing has arrived. The control unit 104 waits until the transmission timing arrives (NO in step S1401).

When the timing for sending the reminder mail arrives (YES in step S1401), the control unit 104 refers to the non-payment information database 150, and the payment date/time 156 is blank (“-” in the example of FIG. 6). The number of pieces of data corresponding to (location) is counted (step S1402).

The control unit 104 divides the counted number into the total number of the dunning mails to be transmitted by the number of time zones for sending the dunning mails (5 in this embodiment). As a result, the number of reminder emails to be sent in each time zone can be specified (step S1403).

The control unit 104 acquires, from the non-payment information database 150, the lessee ID 151 of the data in which the payment date/time 156 is blank. Then, the lessee database 120 is searched from the obtained lessee ID 151 to obtain the corresponding mail address 122g (step S1404).

The control unit 104 creates an email with the acquired email address as the destination for each lessee ID. Specifically, the control unit 104 acquires the number of unpaid payments 122e and the total number of delays 122f of the renter database 120 for each of the renter IDs 151 acquired in step S1404. Then, for each of the acquired unpaid number 122e and the total number of delays 122f, which of the delay conditions 141 of the message database 140 is satisfied is specified. Then, if satisfied, a message having the message content 142 corresponding to the specified delay condition as the body of the message is generated (step S1405).

The control unit 104 allocates each generated mail to each time slot so that the number of reminder mails to be transmitted in each time slot specified in step S1403 is reached (step S1406). That is, the time in the time zone assigned to each generated dunning mail is assigned as the transmission time.

Then, when the assigned time comes, the control unit 104 transmits the reminder mail to the terminal of the lessee of the transmission destination via the communication unit 101 via the communication unit 101 (step S1407).

The above is the operation relating to the transmission of the reminder mail of the debt management device 100.

FIG. 15 is a flowchart showing an operation related to a collection process in which the debt management device 100 collects information (documents) required to transfer the authority regarding debt to a lawyer.

As shown in FIG. 15, the control unit 104 of the debt management apparatus 100 determines whether or not there is data in which the unpaid number 122e is a predetermined number or more (for example, four or more) in the lessee database 120 (step S1501). ..

When there is data in which the unpaid number 122e is equal to or larger than the predetermined number (YES in step S1501), the control unit 104 executes the process in step S1502, and when there is no data in which the unpaid number 122e is equal to or larger than the predetermined number ((S1501)) ( If NO in step S1501), the process ends. It should be noted that, here, the transfer target person who takes legal action is automatically specified based on the number of unpaid payments 122e, but this is not the only case, and the operator takes legal action against the specific debtor. If you decide to take it, you can manually enter the specific debtor as the transferee. In addition, the control unit 104 of the debt management measure 100 actually transfers the transfer process to the monitor connected to the debt management device 100 together with information that can identify the prospective person before the transfer to the legal measure. It is also possible to display a GUI inquiring whether or not to carry out, and to execute subsequent transfer processing after accepting a decision input of the transfer processing for the displayed GUI.

In step S1502, the control unit 104 identifies the lessor ID of the data in which the number of unpaid payments 122e is a predetermined number or more (step S1502). Then, the control unit 104 reads out the list information 160 stored in the storage unit 102 (step S1503).

The control unit 104 executes a power of attorney creation and transmission process (step S1504). The details of the power of attorney creation and transmission process will be described later. The control unit 104 also executes a request letter creation process (step S1504). The details of the request letter creation process will also be described later.

The control unit 104 changes the flag information 1003 corresponding to the required information (document) name 1001 stored in the storage unit 102 from “0” to “1” in the list information 160 read in step S1503. Yes (step S1506).

The control unit 104 creates an e-mail requesting the information holder of the necessary information (document) whose flag information 1003 is “0” to send the corresponding necessary information, and transmits it via the communication unit 101. Yes (step S1507). Specifically, the control unit 104 creates and sends a mail requesting the document indicated by the required information (document) name 1001 to the partner indicated by the information holder 1002 of the list information 160.

The control unit 104 determines whether or not there is a reception input indicating that the necessary information (document) has been received from the operator via the input reception unit 103 (step S1508). The receipt input may be information indicating that the operator has received the corresponding document, or may be a record of electronic data of necessary information (document) in the storage unit 102. For example, when the information name in the list information 160 is “lease contract”, the data obtained by scanning the lease contract received from the lessor whose electronic file name is the same “lease contract” as the information name, When stored in the storage unit 102, the control unit 104 may determine that the “lease contract” is received and received.

When the necessary information (document) is received and input (step S1508), the control unit 104 sets the flag information 1003 corresponding to the received necessary information (document) from "0" to "1". Change to. That is, it switches to the information indicating that the necessary information has been collected (step S1509).

Next, the control unit 104 determines whether or not a predetermined time (for example, 5 days) has passed since the e-mail requesting the sending of the required documents was sent (step S1510). This predetermined time period is a standard time period for waiting for the receipt of an e-mail requesting a required document. If the predetermined time has not elapsed (NO in step S1510), the process returns to step S1508. If the predetermined time has elapsed (YES in step S1510), the control unit 104 determines whether all the flag information 1003 in the list information 160 is "1", that is, all the necessary information. It is determined whether the information and documents to be collected have been collected (step S1511). If all the flag information 1003 is not "1" (NO in step S1511), the process returns to step S1507. As a result, the information holder who has not sent the document can be sent a re-mail to request the information holder. When all the flag information 1003 is "1" (YES in step S1511), the control unit 104 notifies the operator's terminal that the required documents have been collected via the communication unit 101. To do. At this time, the control unit 104 may attach the collected electronic data of the necessary documents along with the request letter created in step S1505 and send it to the terminal 400 of the lawyer 410 by mail. The original document is separately mailed to the lawyer 410 by the operator.

With the above processing, the debt management device 100 can collect the documents required when requesting a lawyer to take legal action regarding the debt. Therefore, it is possible to reduce the human load conventionally required for this collection processing. You can

FIG. 16 is a flowchart showing the operation relating to the transmission of the proxy transmission mail by the debt management device 100.

As shown in FIG. 16, the control unit 104 of the debt management apparatus 100 identifies the renter ID 121 identified in step S1502 and the corresponding name 122a, and extracts the information (step S1601).

The control unit 104 refers to the contract database 110 based on the specified renter ID 121, specifies the corresponding lessor ID 112, the property name 113a as property information, and its address 113c, and extracts the information (step). S1602).

The control unit 104 refers to the lessor database 130 based on the identified lessor ID 112, identifies the corresponding lessor name 132a and the corresponding mail address 132b, and extracts the information (step S1603).

Based on the name 122a extracted in step S1601, the property name 113a and the address 113c extracted in step S1602, and the name 132a extracted in step S1603, the control unit 104 stores the power of attorney stored in the storage unit 102. The template information is read and a proxy is created (step S1604).

The control unit 104 creates a mail addressed to the mail address 132b extracted in step S1603 and requesting a seal (signature) to the extracted power of attorney (step S1605).

The control unit 104 attaches the power of attorney created in step S1605 to the created mail. After attaching the power of attorney to the mail, the control unit 104 transmits the mail created via the communication unit 101 to the terminal 300 of the lessor 310 (step S1606), and ends the process.

As described above, the debt management device 100 may automatically create a power of attorney for the guarantor to delegate the authority for the lessee 210 to take legal action, and automatically transmit the power of attorney to the lessor 310. it can.

FIG. 17 is a flowchart showing the operation relating to the request letter creation by the debt management apparatus 100.

As shown in FIG. 17, when the original letter of proxy signed (imprinted) is received from the lessor 310, the guarantor inputs an instruction for creating a request letter to the input acceptance unit 103 of the debt management apparatus 100. When the input acceptance unit 103 of the debt management apparatus 100 accepts an instruction input for creating a request letter (step S1701), the input acceptance unit 103 transmits it to the control unit 104.

The input reception unit 103 further receives the input of the lessee ID from the operator (step S1702). The input reception unit 103 transmits the received lessee ID to the control unit 104.

When the control unit 104 is instructed to input a request form, the control unit 104 reads the template information of the request form stored in the storage unit 102 (step S1703).

Upon receiving the input of the renter ID, the control unit 104 reads the name 122a for the renter ID from the renter database 120 (step S1704).

The control unit 104 identifies the corresponding lessor ID and property name 113a in the contract database 110 from the input lessee ID. The control unit 104 extracts the property name from the specified property name 113a (step S1705).

Then, the control unit 104 refers to the lessor database 130 to identify the name of the lessor from the identified lessor ID, and extracts the name (step S1706).

The control unit 104 inputs the request information by inputting the name of the lessee, the name of the lessor, the property name and the date and time when the request was created to the template information read in step S1703, in step S1704 to step S1705. Create (step S1707).

The control unit 104 outputs the created request letter to an external device via the communication unit 101 (step S1708), and ends the process. Here, the external device may display the created request letter as a monitor, or may print out the created request letter as a printer. If the letter to be sent to the lawyer 410 is only the request letter, it may be sent to the terminal 400 of the lawyer 410. In this case, the mail address of the terminal 400 is stored in the storage unit 102 in advance.

The above is the operation of the debt management apparatus 100 for creating a request letter.

<Display example>
FIG. 18 shows a display example of a reminder mail on the terminal 200 owned by the lessee 210.

FIG. 18A shows a display example of the reminder mail when the lessee is “Andrew” and the total number of delays of “Andrew” is “less than 10”.

FIG. 18B shows a case where the lessee is "Andrew" and the number of unpaid "Andrew" is "3 times or more" or the total number of delays is "50 times or more". Shows a display example of the reminder mail.

The renter makes a call by seeing the mail as shown in FIGS. 18(a) and 18(b).

FIG. 19 shows a display example of the document delivery request mail transmitted from the debt management apparatus 100 to the lessor on the terminal 300 owned by the lessor 310. The document delivery request email is an email sent by the debt management device 100 to a person or a group holding the document as necessary information, and is an email including the content to request the delivery of the document. Here, as an example of a document that the debt management apparatus 100 requests to send, an example of an e-mail when a request to send a lease contract is shown.

As shown in FIG. 19, the mail requesting to send the lease contract is sent to the lessor who rents the property to the lessee who has not fulfilled the contract. This lessor specifies the lessor ID 112 associated with the lessee ID 121 of the data in which the number of unpaid 122e is 4 or more in the lessee database 120, and the corresponding name and email address in the lessor database 130. Based on the above, the control unit 104 of the debt management apparatus 100 specifies.

In FIG. 19, the main body of the document delivery request mail is stored in the storage unit 102 of the debt management apparatus 100 as a substantially fixed sentence, and is a sentence excluding the address 1901, the target 1902, the information holder 1903, and the target 1904. Is remembered. As the address 1901, the name associated with the lessor ID specified from the lessee ID is used as described above. The target 1902 uses the name associated with the lessee ID. The information holder 1903 uses the same name as that used for the address 1901, and the target 1904 uses the same name as the target 1902.

In this way, the debt management device 100 can create and send a document delivery request mail. Then, the lessor 310 can confirm that the rental agreement must be sent as a required document by receiving and viewing this mail at the terminal 300.

<Summary>
As shown in the above-described embodiment, the debt management device 100 is required to detect a lessee who has failed the contract a predetermined number of times or more and request an attorney to make a lawsuit concerning the default of the contract. Can assist in collecting and presenting documents. Further, as a part of the support, the debt management device 100 identifies a lease contract or a lessor related to the lessee, and automatically uses the power of attorney template that is stored in advance to automatically make a lawsuit. You can create a power of attorney. Therefore, it is possible to reduce the processing load when executing a litigation related to guarantee work.

<Supplement>
Although the debt management apparatus 100 has been described according to the above-described embodiment, it goes without saying that the debt management apparatus 100 may be realized by another method. Hereinafter, other modes that the debt management apparatus can take will be described.

(1) In the above embodiment, the debt management device 100 simply divides the total number of reminder emails to be transmitted by the number of transmission time zones, and randomly extracts the reminder emails so that the number is reached. However, the time zone to be assigned may be determined according to the other party to whom the reminder mail is transmitted so that the timing of receiving calls is not concentrated. As a result, it is possible to further improve efficiency. Hereinafter, a configuration that the debt management apparatus 100 can adopt will be described as a method therefor.

(1-1) The time zone for sending the reminder mail is determined according to the past telephone record so that the lessee can easily make a call.

The non-payment information database 150 stores date and time information when a telephone call was made in response to a reminder mail for each renter who failed to pay the rent. Therefore, for each lessee, it can be estimated from the date and time information that the time when the lessee makes a call is a time zone when the lessee makes a call easily. Therefore, the control unit 104 may be configured to average the date and time information when the renters with the same renter ID are called and to send the reminder mail in the time zone closest to the average date and time.

(1-2) The time period for sending the dunning mail is determined according to the speed of the response from the sending of the dunning mail according to the past telephone record.

The non-payment information database 150 stores date and time information when a telephone call was made in response to a reminder mail for each renter who failed to pay the rent. Further, the non-payment information database 150 also stores the transmission date and time when the dunning mail was transmitted. The control unit 104 can specify the speed of response to the reminder mail of each lessee from the difference between these times. Regardless of the time zone in which the reminder email is sent, the less responsive renter can expect to make a call within the time zone in which the reminder email was sent. Therefore, it can be inferred that such a lessee can avoid the concentration of the call receiving time zone as much as possible by transmitting the dunning mail in such a manner as to be distributed in each time zone as much as possible. Therefore, the control unit 104 calculates the response time to the reminder mail for the lessee who has failed to pay the rent. If multiple data are registered for the same lessee, the average response time is calculated. Then, the lessee whose calculated response time (or its average value) is less than or equal to a predetermined threshold value (for example, one hour) is specified. Then, the control unit 104 determines a time period in which the dunning mail is transmitted so that the lessees whose response time (or its average value) is equal to or less than a predetermined threshold value are distributed in each time period as much as possible.

(1-3) The time period for transmitting the dunning mail is determined according to the attribute information of the lessee.

Although not shown in the renter database 120 shown in FIG. 2 of the above embodiment, the renter database 120 may include other attribute information. For example, the occupation information of the lessee may be included as an example. In such a case, the time period for transmitting the dunning mail may be determined from the attribute information of the occupation of the lessee.

For example, if the occupant's occupation is a company employee, the control unit 104 avoids the time zone in which it is estimated that he/she is normally employed, and sends a reminder mail during the time zone such as before work, during lunch break, and after work. May be configured. Also, if the renter's profession is a full-time housewife, it can be inferred that it is basically easy to make a call regardless of the time zone. May be determined. Alternatively, if the occupant's occupation is the food and drink business, the time zone for transmitting the dunning mail may be determined while avoiding the time zone during meals. Further, more roughly, a reminder mail may be transmitted to a lessee who is employed in the daytime and a reminder email may be transmitted to a lessee who is employed in the night at night.

(2) In the above embodiment, the text content of the dunning mail is determined by referring to the message database 140 from the number of unpaid renters 122e and the total number of delays 122f. As a condition for determining, the content other than the unpaid number 122e and the total delay number 122f may be determined as a condition.

For example, the renter database 120 may store the renter personality information in association with each renter. Then, in this case, the message database 140 may be information in which the personality information and the message content are associated with each other. For example, renters with a serious personality may be given a polite message to improve the likelihood of making a phone call, and renters with a weak personality may receive a slightly intimidating email. It may be possible to improve the possibility of making a phone call by using the mail, or, for a renter who is angry, it may be possible to increase the possibility of making a phone call by using an email with a mild expression. In addition, the content of the reminder email may be changed according to the renter's information such as the renter's gender, age, occupation, annual income, delinquency history (total number of delays and unpaid times), etc. Good. Therefore, the message database 140 may be information in which the lessee information is associated with the content of the text so as to indicate to which lessee the reminder mail is to be sent.

Also, the number of calls received can be adjusted depending on the content of the reminder mail. For example, depending on whether the text of the email is "please simply transfer" or "please call," the content of "please call" will increase the number of calls received. Tend. Therefore, the message database 140 may have a configuration in which different body contents are associated with each other according to the delinquency history. For example, if you have a total delay time of 30 times or more, put "Please call me" in the text content, and if the total delay time is less than 30 times, add "Simply" in the text content. Please make a description such as "Please transfer." With this configuration, the number of received power from the lessee can be adjusted also according to the content of the text of the dunning mail.

With such a configuration, it is possible to improve the possibility that the lessee will call by sending a reminder mail in accordance with attributes such as the lessee's personality and occupation.

(3) Although not described in the above-mentioned embodiment, the debt management device 100 transmits the dunning mail once, and after a certain time (for example, two hours), the telephone reception date and time 155 of the non-payment information database 150. If the date and time information is not included in the message, the dunning mail may be transmitted again. This can increase the possibility that the lessee will make a call.

(4) In the above embodiment, the contract database 110, the lessee database 120, and the lessor database 130 are updated by the operator of the debt management apparatus 100, but this is not the only option. The control unit 104 may update necessary information from the communication unit 101 from the terminal 300 of the lessor 310. For example, the terminal 300 transmits the contract information including the lessor, the lessee, and the property information, which is necessary to update the contract database 110, to the debt management apparatus 100, and the debt management apparatus 100 receives the contract information. May be registered in the contract database 110. Similarly, the renter database 120 and the renter database 130 may be configured so that the control unit 104 receives and updates necessary information.

(5) In the above embodiment, the debt management device 100 receives the nonpayment information that is transmitted when the lessee fails to pay the consideration in a predetermined period, and immediately prompts the telephone at the transmission timing in the next predetermined period. I decided to send an email, but this is not the case. The operator of the debt management device 100 may appropriately decide whether to send the telephone reminder email at this timing. For example, in the first rent delinquency stage, the telephone reminder email was not sent and the rent was delinquent for two consecutive months. You may send a telephone reminder email for the first time at a timing.

(6) In the above embodiment, the nonpayment information and the payment information when the lessee who has neglected to pay the consideration paid the consideration and receive the lessee database 120 and the nonpayment information database 150. However, this is not the only case. For each lessee, a similar configuration can be realized by accepting only payment information indicating that the payment has been paid, that is, the lessee who did not receive the payment information within the predetermined period for paying the consideration. Regarding the above, even if the total number of delays and the number of unpaid times are incremented by 1 and registered in the non-payment information database, the same structure as the above-described embodiment can be realized.

(7) In the above embodiment, the debt management apparatus 100 has shown an example in which the text of the telephone reminder mail is changed according to the total number of delays in payment of the rent or the number of continuous delays. However, it goes without saying that the trigger for changing the text of the email is not limited to the total number of delays and the number of unpaid times.

(8) In the above embodiment, the payment information is sent every period, but this is not the only case, and when the lessee pays the consideration for a plurality of periods together. The payment information may be sent once including the information for the period for which the consideration was paid. In this case, the control unit 104 extracts the information for the period included in the payment information, registers the date and time when the payment information is received in the payment date and time 156 of the corresponding multiple periods, and updates the non-payment information database 150. It may be done.

(9) In the above-described embodiment, the debt management apparatus 100 has shown an example of accepting the designation of one data in the contract database 110 from the operator and creating the request letter, but this is not the only case. If the request letter can be created, it may be created in another form. For example, the debt management device 100 creates a power of attorney for a case for which legal action is taken, but the power of attorney may be designated. As described above, since the power of attorney includes various corresponding information included in the request letter, it is possible to prepare information sufficient for creating the request letter.

(10) The above embodiment does not particularly describe the case where the lessee rents a plurality of properties. However, when the lessee rents a plurality of properties, it is necessary to register each lease contract in the contract database 110 as well. Further, since the same tenant may be registered in the tenant ID, the identification information is associated with each lease contract so that which lease contract can be more clearly distinguished. Then, the lessee database 120 is configured to count the number of unpaid payments and the total number of delays for each property, and also to store the identification information of the corresponding lease contract in association with each other. If each database is configured in this way, when creating a power of attorney or request, etc., if the identification information of the lease contract is specified, the power of attorney or request is created by uniquely identifying the lease contract. be able to.

(11) The above-mentioned guarantee work shows one mode of guarantee, and the contract content is not limited to the guarantee contract. The contract managed by the debt management device 100 may be a contract that is exchanged between at least two parties, and may be a contract that pays consideration from one to the other periodically or a plurality of times. The guarantee contract is not limited to the lease contract described in the embodiment. Also, the two parties mentioned here may be individuals or some kind of organization, for example, a company. Specific examples of the contract content here include, for example, (i) when the lessor manages a claim to the lessee in the lease contract, and (ii) in the lease contract, the claim management entrusted by the lessor When the company manages the claims to the lessees, (iii) manages the claims that are incurred for the trading value that is incurred under the continuous sales contract, and (iv) is based on the medical treatment fee contract in the hospital. Various cases are included, such as managing the debt that is incurred. Further, it goes without saying that the specific embodiment may be appropriately changed according to the contract content. For example, when the guarantee company in the guarantee contract uses the debt management apparatus, the non-payment information is transmitted to the debt management apparatus from the terminal of the lessor or a company that manages the rent of the lessor. However, when the rent management company of the lease contract uses the debt management device, the non-payment information is transmitted to the debt management device from the bank that handles the transfer destination account where the lessee pays the rent to the lessor. Become.

(12) The debt management device 100 according to the above-described embodiment effectively operates in the same way as the mode described in the above-described embodiment, when the debtor manages the debt, in addition to the management by the guarantor.

(13) In the above embodiment, the delegation of legal action to a lawyer was described, but the range of authority to be entrusted is not particularly described. Therefore, the scope of authority delegated here will be briefly described. For example, in the case of a lawsuit in which the lessor sues for renting, a lawyer is given a lawyer's agent for a building litigation claim litigation, an unpaid rent payment claim litigation, and a lease contract cancellation notice. In the case of a lawsuit filed by a guarantor, the lawyer is given the right to act in a claim for litigation. At this time, the debt management device 100 creates a power of attorney for both cases. Therefore, the storage unit 102 stores the template information according to the delegating subject, and the control unit 104 creates a power of attorney according to each delegation content. Further, as described in the supplement (12) above, when the lessor uses the debt management device 100 as a device for supporting the processing for entrusting a legal procedure to a lawyer, the lessor is the lessee. In regard to the lawsuits to be filed against the lawyer, the lessor will grant the attorney the power of representation for the building litigation claim lawsuit, the unpaid rent payment claim lawsuit, and the lease contract cancellation notice.

(14) In the above embodiment, each unit of the debt management apparatus 100 is realized by a logic circuit (hardware) or a dedicated circuit formed in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) or the like. Alternatively, it may be realized by software using a CPU (Central Processing Unit) and a memory. Further, each functional unit may be realized by one or a plurality of integrated circuits, and the functions of a plurality of functional units may be realized by one integrated circuit. The LSI may be referred to as VLSI, super LSI, ultra LSI, or the like depending on the degree of integration. In addition, the circuit may be realized by a reconfigurable circuit (for example, FPGA: Field Programmable Gate Away). When the debt management apparatus 100 is configured by a circuit, for example, as illustrated in FIG. 20, it may be configured by a communication circuit 101a, a storage circuit 102a, an input reception circuit 103a, and a control circuit 104a, and each circuit is Functions similar to those of the functional units described in the above embodiment are realized.

When each functional unit of the debt management apparatus 100 is implemented by software, the debt management apparatus 100 executes a command of a debt management program that is software that implements each function, the debt management program and various data are stored in a computer (or It is provided with a ROM (Read Only Memory) or a storage device (these are referred to as a "recording medium") recorded so as to be readable by a CPU, a RAM (Random Access Memory) for expanding the debt management program, and the like. Then, the computer (or CPU) reads the debt management program from the recording medium and executes the program to achieve the object of the present invention. As the recording medium, a "non-transitory tangible medium", for example, a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. Further, the debt management program may be supplied to the computer via any transmission medium (communication network, broadcast wave, or the like) capable of transmitting the debt management program. The present invention can also be realized in the form of a data signal embedded in a carrier wave, in which the debt management program is embodied by electronic transmission.

The debt management program can be implemented using, for example, a script language such as ActionScript or JavaScript (registered trademark), an object-oriented programming language such as Objective-C or Java (registered trademark), or a markup language such as HTML5. ..

(15) Although the present invention has been described based on the drawings and the embodiments, it should be noted that those skilled in the art can easily make various variations and modifications based on the present disclosure. Therefore, it should be noted that these variations and modifications are included in the scope of the present invention. For example, the functions and the like included in each means and each step can be rearranged so as not to logically contradict each other, and a plurality of means and steps can be combined or divided into one. ..

(16) The configurations shown in the above embodiments and the configurations shown in the reference examples may be combined as appropriate.

100 Debt Management Device 101 Communication Unit 102 Storage Unit 103 Input Reception Unit 104 Control Unit

Claims (14)

A debt management device that collects necessary information necessary for delegating legal action to a debtor who does not fulfill its obligations to a lawyer,
A list information storage unit that stores list information including the name of the necessary information and contact information of the holder of the necessary information;
A debt management apparatus comprising: a communication unit that performs communication for requesting the holder to send the necessary information based on the list information. The necessary information has a plurality of information,
The list information includes, for each required information, contact information of a holder who holds the required information,
The communication unit performs communication based on the list information to request a holder who holds the necessary information to send the necessary information.
The debt management device according to claim 1, characterized in that. The list information includes flag information indicating whether or not the necessary information has been sent,
The debt management device further comprises
A determination unit for determining whether or not the necessary information has been sent,
The debt management device according to claim 1 or 2 , further comprising a switching unit that switches the flag information based on the determination of the determination unit. The debt management device further includes a re-communication unit that performs communication for requesting the sending of the necessary information to a holder of the necessary information to which the necessary information has not been sent, based on the flag information. The debt management apparatus according to claim 3 , further comprising: The debt management device further comprises
The debt management device according to claim 4 , further comprising a display unit that displays the list information. The debt management device further comprises
A necessary information storage unit that stores the necessary information,
Debt management apparatus according to any one of claims 1 to 5, characterized in that it comprises the necessary information sending unit for sending the necessary information stored in the required information storage unit. The debt management device further comprises
A debtor information storage unit that stores debtor information in which the debtor and information indicating that the debt is not fulfilled when the debt by the debtor is not fulfilled are stored,
The communication unit requests, in the debtor information, to send necessary information for taking legal action to the debtor when there is a debtor that satisfies a predetermined condition in the state where the debt is not fulfilled. I do
The debt management device according to any one of claims 1 to 6, characterized in that. The debtor information, the debtor, the number of times that the debt is not fulfilled, is associated as information indicating that the debt is not fulfilled,
The predetermined condition is that the number of times the debt is not fulfilled is greater than or equal to a predetermined number of times.
The debt management device according to claim 7, wherein The communication unit sends a created mail with the mail address of the holder as a destination as a communication for requesting the sending of the necessary information.
The debt management device according to claim 7 or 8, characterized in that. The debt management device,
The electronic mail address is provided as a destination, and a control unit for automatically creating an email including a draft requesting the sending of necessary information is provided.
The communication unit transmits the mail created by the control unit
The debt management device according to claim 9, wherein The debt management device,
A message information storage unit that stores message information that holds the content of the draft of the mail,
The control unit automatically creates a mail including the name of the holder who holds the necessary information in the message information.
The debt management device according to claim 10, wherein The debt management device,
A correspondence information storage unit for storing correspondence information in which a debtor and a creditor corresponding to the debtor are associated with each other;
In the list information, when the holder of the necessary information is a creditor, the communication unit requests a creditor corresponding to a debtor who satisfies the predetermined condition to send the necessary information. To communicate
The debt management device according to any one of claims 7 to 11, characterized in that. A debt management method using a debt management device, which collects necessary information necessary for delegating a legal action for a debtor who does not fulfill its obligations to a lawyer,
A list information storing step of storing list information including a name of the necessary information and contact information of a holder of the necessary information;
And a communication step of performing communication for requesting the holder to send the necessary information based on the list information. In the computer of the debt management device, which collects the necessary information necessary for delegating the legal action against the debtor who does not fulfill the debt
A list information storage function for storing list information including the name of the necessary information and contact information of the holder of the necessary information,
A debt management program that realizes a communication function of performing communication for requesting the holder to send the necessary information based on the list information.

Images