JP2018014061A - Debt management device, debt management method, and debt management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a debt management device for providing information for entrusting a lawyer with a legal action to a tenant if the tenant fails to perform a contract meeting a prescribed condition in a guarantee business for guaranteeing a lease contract.SOLUTION: A debt management device for collecting necessary information necessary to entrust a lawyer with a legal action to a debtor who fails to perform their obligations includes: a list information storage unit for storing list information including a name of the necessary information and information on a contact address of a holder of the necessary information; and a communication unit for communicating with the holder for requesting delivery of the necessary information on the basis of the list information.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a debt management apparatus, a debt management method, and a debt management program for executing a guarantee business for guaranteeing a lease contract.

  Conventionally, as a type of guarantee business related to debt, there is one that guarantees a rent payment obligation of a lessee who has concluded a lease contract. In this guarantee, the guarantor is obliged to pay the rent on behalf of the lessee to the lessor if the lessee has delayed payment of the rent. The lessee is the side who pays the rent and rents the property, and the lessor is the side who receives the rent and rents the property.

  According to Patent Document 1, regarding the rent-related costs of rental properties, the occupant's effort to find a joint guarantor is reduced, the initial burden such as a security deposit, security deposit, key money, etc. is reduced, and the occupancy examination time is shortened.・ Systems have been proposed for real estate management companies and leasing companies that reduce the financial time burden and the collection risk associated with leasing.

JP, 2006-71724, A

  By the way, the guarantor takes legal measures to reimburse the lessee if the lessee does not pay the rent continuously for a predetermined period or more and does not execute the contract to pay the consideration. That is, in the guarantee business, the guarantor may take legal measures on behalf of the lessor. Legal measures here are delegated to a lawyer who has the right to act on behalf of the lawyer, and the attorney will act on their behalf. Although the guarantor needs to collect or prepare various documents for taking legal action, the work has been problematic because it is very time-consuming for the guarantor. In addition, not only the guarantor but also the creditor had a similar problem when trying to take legal action.

  Accordingly, the present invention has been made in view of the above problems, and a debt management apparatus capable of reducing the trouble when a creditor or a guarantor delegates legal measures against a debtor who does not fulfill a debt to a lawyer. 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 required to delegate a legal action against a debtor who does not perform duties to a lawyer. A list information storage unit for storing list information including a name of the necessary information and contact information of a holder of the necessary information, and requesting 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-described problem, a debt management method according to one aspect of the present invention includes a debt management apparatus that collects necessary information required to delegate a legal action to a lawyer for a debtor who does not fulfill a debt to a lawyer. A list information storing step for storing list information including information of 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. And a communication step for performing communication for requesting the transmission of.

  In order to solve the above-described problem, a debt management program according to one aspect of the present invention is provided in a computer of a debt management apparatus that collects necessary information required to delegate a legal action for a debtor who does not fulfill a debt to a lawyer. 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.

  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. And a switching unit that switches the flag information based on the determination of the determination unit.

  Further, in the debt management apparatus, re-communication for performing communication for requesting delivery 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 It is good also as providing a part.

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

  The debt management apparatus may further include a necessary information storage unit that stores necessary information and a necessary information transmission unit that transmits necessary information stored in the necessary information storage unit.

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

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 function 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 lessee 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 non-payment 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 flowchart which shows operation | movement of a debt management apparatus. It is a flowchart which shows operation | movement of a debt management apparatus. It is a flowchart which shows operation | movement of a debt management apparatus. It is a flowchart which shows operation | movement of a debt management apparatus. It is a flowchart which shows operation | movement of a debt management apparatus. (A), (b) is a figure which shows the example of a display of a dunning mail. It is a figure which shows the example of a display of the mail of a request to send a required document. It is a block diagram which shows the function structural example of a debt management apparatus.

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

  Here, “obligor” means a person (including a corporation) or an organization that has concluded a debt contract with a creditor. The debtor is, for example, a renter who leases the property, but is not limited to this. In the following, the borrower corresponds to the lessee 210. The creditor corresponds to the lessor 310 in the following.

  In addition, “legal measures” means taking measures based on law such as litigation, for example, “proposing a lawsuit”, and including, for example, “proposing a lawsuit for a guarantee obligation claim case” . Note that examples of “legal measures” are not limited to this.

  “Necessary information” is information required for each case for which a legal action is requested, and includes information that is commonly required for each case and information that is required for each case. For example, when a legal measure based on a default on a lease contract is performed as a project, the lease contract, the cancellation notice, and the rent payment history information are necessary information common to the projects. On the other hand, the parking lot use contract is necessary information depending on the presence or absence of a renter who has signed a parking lot usage contract, and is necessary information individually for each project. The necessary information includes not only documents such as contracts but also simple information such as rent payment history information. Further, the necessary information includes a document (for example, a proxy or a cover letter) created by the debt management device. In addition, the specific example of the required information shown here is an example, and is not limited to this.

  “Collecting” means gathering necessary information, receiving electronic data via a communication network, receiving the actual document when the necessary information is a real document, or It includes receiving input of information indicating that the document has been received, and specifying necessary information stored in the debt management device.

  In addition, here, the “debt management device” stores list information including the name of necessary information and contact information of the holder of the necessary information, and based on the list information, Communication is performed to request transmission of necessary information. The debt management device is also a device that supports a task of managing debts owed by the debtor. Here, in the business related to the management of debt contracts, for example, management of whether debts are actually fulfilled, collecting necessary information when taking legal action, and sending the collected necessary information to lawyers May be included. The debt management device is, for example, a computer system that manages the various operations described above, but is not limited thereto. In the following, the debt management apparatus 100 corresponds.

  “Necessary information name” refers to information that can individually identify various types of necessary information, and refers to names and identifiers of necessary information. “Necessary information name” means, for example, “lease agreement”, “cancellation notice”, “proxy”, etc., but is not limited to this example.

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

  The “contact” is the contact information of the holder of the necessary information. For example, 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. An address, an address indicating the location of a holder of necessary information, and a communication destination number or destination by facsimile communication held by the holder of necessary information are not limited to these. In the following, an e-mail address is shown as an example.

  The “list information” is information that can specify the name of the necessary information and the holder of the necessary information for each of a plurality of necessary information. The list information 160 corresponds to the following.

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

  “Request to send” means to send necessary information to the debt management device or its operator, which can be realized by, for example, sending by letter, sending by e-mail, etc. May be.

  Further, the “communication unit” performs communication for requesting the holder to send necessary information based on the list information. For example, the “communication unit” can be realized by a telephone or a communication interface for sending and receiving e-mails. However, it is not limited to this. In the following, the communication unit 101 corresponds. “Communication” here refers to transmitting a request for sending necessary information, and can be realized by sending a letter, calling, sending an e-mail, etc., but is not limited to these examples.

The list information may include flag information indicating whether or not necessary information has been sent.
Here, “flag information” is information indicating whether or not necessary information has been sent. The “flag information” is also information for determining whether or not the debt management device has collected the necessary information. The flag information is, for example, a binary value that can be expressed by “1” or “◯” that necessary information has been sent, and can be expressed by “0” or “×” that no required information has been sent. Information. Note that the flag information shown here is an example, and the present invention is not limited to this.

  The debt management device may further include a determination unit and a switching unit.

  Here, the “determination unit” determines whether or not necessary information has been sent. For example, the “determination unit” is realized by a processor or a dedicated circuit, but examples of the determination unit are not limited thereto. The control unit 104 corresponds to the following. “Determining” means determining whether or not necessary information has been sent. In the determination, when the necessary information is received as electronic data, it is possible to determine whether the necessary information has been sent depending on whether the necessary information has been received. In addition, when the necessary information is received as a real document, the determination is made by accepting input of information indicating that the necessary information has been received or input of electronic data of a document indicating the necessary information. However, these determination examples are only examples.

  The “switching unit” switches the flag information based on the determination by 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 thereto. The control unit 104 corresponds to the following. “Switching flag information” means changing to information indicating that necessary information has been sent when the flag information indicates that necessary information has not been sent.

  The debt management device may further include a re-communication unit.

  The “re-communication unit” performs communication for requesting a holder of necessary information to which necessary information has not been transmitted based on the flag information, for example, a telephone or electronic This 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 necessary information to send necessary information.

  The debt management device may further include a display unit.

  Here, the “display unit” displays list information and is a monitor realized by, for example, an LCD or an organic EL display, but is not limited thereto. In the following, an example is shown in which a monitor is connected to the debt management apparatus 100 and displayed. 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 a part is not restricted to this. The storage unit 102 corresponds to the following. “Storage” refers to storing information in a storage medium.

  The “necessary information sending unit” sends necessary information stored in the necessary information storage unit. For example, the “necessary information sending unit” can be realized by a telephone or a communication interface for sending and receiving e-mails, but is not limited thereto. In the following, the communication unit 101 corresponds. “Sending” means sending electronic data or actual documents to a destination, for example, sending a letter including necessary information or sending electronic data of necessary information by e-mail. This is not a limitation.

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

<Embodiment>
<Configuration>
FIG. 1 is a conceptual diagram conceptually showing a system form of guarantee work related to the debt management apparatus 100. The debt management apparatus 100 in the present embodiment guarantees a lease contract exchanged between the lessor 310 and the lessee 210. Specifically, the lessee 210 enters into a contract with the lessor 310 to lease the property 500 that the lessor 310 owns (or has the right to lease). As the lease contract, for example, it is assumed that the lessee 210 obtains the right to use the property 500 by paying a fixed rent (for example, 100,000 yen) periodically (for example, in units of one month). . Here, the debt management device 100 guarantees the lessor 310 that the lessee 210 periodically pays the rent as defined in the contract. Therefore, the guarantee management business operator related to the debt management apparatus 100 pays the rent to the lessor 310 on behalf of the lessee 210 when the lessee 210 delays the payment, or causes the lessee 210 to make the payment. This is guaranteed to the lessor 310. Further, when paying the rent to the lessor 310 on behalf of the lessee 210, the debt management device 100 charges the lessee 210 for the new rent.

  To that end, the debt management device 100, as part of the guarantee business, (1) calls the lessor 310 when the lessee 210 fails to pay the rent within the period specified in the contract. When the lessee 210 delays payment and satisfies a predetermined condition, the debt management device 100 is legally instructed to the lessee 210. A process for delegating the measure to the lawyer 410 is executed.

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

  In FIG. 2, T0 to T1, T1 to T2, and T2 to T3 are set as predetermined periods A, B, and C, respectively. For the predetermined periods A, B, and C, for example, the day when the lessee 210 enters into a lease agreement with the lessor 310 is set as the starting date, and the period is set in units of one month. In the predetermined period, one day of January may be set as the starting date, or a predetermined date set in advance may be set as the starting date. The length of the predetermined period is not limited to one month, but may be a unit such as one week, two months, half a year, or one year.

  Further, it is assumed that the lease contract is defined as paying a rent for renting the property 500 for a predetermined period within a predetermined period. In the lease contract, if an agreement is made between the lessee 210 and the lessor 310, it may be determined that the rent for a predetermined period is paid in the next predetermined period, or the next day until the end of the predetermined period. It may be paid.

  In FIG. 2, the lessee 210 pays the rent for a predetermined period A to the lessor 310 at t1. Further, the lessee 210 pays the rent for a 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 to the debt management apparatus 100 from the lessor 310 is transmitted to the debt management apparatus 100. Here, the non-payment information may be configured to be transmitted by a consignor commissioned by the lessor 310 to manage the rent.

  When the non-payment information is received, the debt management device 100 transmits a dunning email requesting a call to the lessee 210 indicated by the non-payment information. Thereby, when there is a call from the lessee 210, an inquiry about the situation can be made. The debt management device 100 according to the present embodiment automatically transmits a dunning mail, reduces the processing load related to the guarantee work, and makes a call from a lessee made in response to the dunning 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 example connected to the time series of the case shown in FIG. As shown in FIG. 3, it is assumed that the lessee 210 fails 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 non-payment information from the terminal 300 to the debt management apparatus 100, and the debt management apparatus 100 transmits a reminder email requesting a call to the terminal 200 of the lessee 210.

  Then, when the lessee 210 continuously fails to pay the compensation for a predetermined number of predetermined periods (here, 4), that is, when the rent for four months is delinquent, the debt management device 100 calls the lawyer. Prepare the documents necessary for delegating legal action and ask lawyer for legal action. As part of this, for example, as shown at t5 in a predetermined period G, the debt management apparatus 100 may use a lease contract as one of the documents necessary for taking legal action against the terminal 300 of the lessor 310. Send an email requesting a mail. Alternatively, the debt management device 100 creates a power of attorney for requesting the lawyer 410 to make a lawsuit relating to a demand for redress by the guarantor when the guarantor changes the rent of the lessee.

  The lessor 310 confirms the request to send the received lease agreement, and sends the held lease agreement to the guarantor associated with the debt management apparatus 100. The guarantor collects necessary documents such as a lease contract from the lessor 310 and creates a request for requesting legal action against the lessee 210 using the debt management device 100. Then, the guarantor sends the prepared request to the lawyer 410 together with necessary documents.

The lawyer 410 receives a request from the guarantee business operator, and transfers the authority regarding the debt of the lessee 210 and executes a process related to legal measures for the lessee 210. The purpose of the debt management apparatus 100 according to the present embodiment is to reduce the processing burden on the guarantor mainly by collecting various documents necessary for delegating legal measures to a lawyer.
Hereinafter, details of the debt management device 100 will be described.

  FIG. 4 is a block diagram illustrating an example of a 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 reception unit 103, and a control unit 104. The debt management device 100 is a device that provides information for delegating a legal action for a debtor who does not fulfill a debt to a lawyer.

  The communication unit 101 has a function of executing 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.). Non-payment information indicating that the transmission unit and the renter who have sent the e-mail for making a telephone request in the time zone determined according to the instruction from the control unit 104 have not paid the consideration (rent). Functions as a receiving unit. If the communication unit 101 can execute communication with an external device, the communication mode does not ask wired or wireless. Further, 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 an instruction from the control unit 104, the communication unit 101 transmits an e-mail with a content requesting a call to the terminal 200 of the lessee 210. In addition, the communication unit 101 indicates that the lessee 210 has failed to pay the rent from the terminal 300 of the lessor 310 or the terminal (not shown) of the renter in response to a request from the lessor 310. Non-payment information is received, and the non-payment information is transmitted to the control unit 104. Here, the non-payment information includes at least a lessee ID that identifies the lessee 210 and period information that identifies a non-payment period, and is transmitted for each non-payment period. 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 merchant managing the rent in response to a request from the lessor 310. 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 lessee ID that identifies the lessee 210, and is transmitted every period during which payment is made. For example, if the renter is delinquent for four months and rents for three months, three payment information is transmitted.

  The storage unit 102 is a storage medium having a function of storing various programs and data necessary for the operation of the debt management apparatus 100. The storage unit 102 can be realized by a storage device such as an HDD (Hard Disc Drive), an SSD (Solid State Drive), or a flash memory. The storage unit 102 stores a contract database 110, a lessee database 120, a lessor database 130, a message database 140, a non-payment information database 150, and list information 160. The contract database 110 is information indicating that a lease contract is exchanged by associating information indicating a lessee with information indicating a lessor. The lessee database 120 is information on the attributes of lessees. The attribute here indicates the characteristics of the lessee, and includes various things such as name, gender, age, and personality. The lessor database 130 is information on the attributes of the lessor. The attribute of the lessor here indicates the characteristics of the lessor, and includes various things such as name, gender, and address. The message database 140 is a database showing the text of the body of an email that requests a call request from the debt management device 100 to the lessee 210. The non-payment information database 150 is information for managing non-payment lessees among lessees. The list information 160 is information indicating various documents necessary when requesting a lawyer for a legal measure relating to debt, and is a check list used to determine whether or not each information has been collected. Details of the contract database 110, the lessee database 120, the lessor database 130, the message database 140, the non-payment information database 150, and the list information 160 will be described later.

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

  The input receiving unit 103 has a function of receiving an input from the 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 a 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 by the determination unit.

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

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

  When the start timing of the predetermined period related to the transmission of the dunning mail has arrived, the control unit 104 determines the timing (time period) for transmitting the dunning mail, and the dunning mail when the timing (time period) has arrived. And a transmission process for transmitting. Here, the predetermined period related to the transmission of the reminder mail is, for example, between 10:00 and 15:00 of the day, and the time zone for transmitting the reminder mail is from 10:00 to 11:00, from 11:00 to 12:00. It is assumed that five time zones from 12:00 to 13:00, 13:00 to 14:00, and 14:00 to 15:00 are set. Note that the setting of the time zone is an example, and the number thereof is only an example.

  The control unit 104 specifies a partner to which the reminder mail is transmitted with reference to the non-payment information database 150. The control unit 104 identifies a lessee ID corresponding to data for which date / time information is not registered for the payment date / time in the non-payment information database 150 as a partner to which the dunning mail is transmitted. Then, the control unit 104 specifies an email address corresponding to the lessee ID with reference to the lessee database 120. In addition, the control unit 104 identifies the number of unpaid 122e and the total number of delays 122f corresponding to the lessee ID with reference to the lessee database. Then, based on the specified number of unpaid 122e and the total number of delayed times 122f, the control unit 104 refers to the message database 140 and specifies the corresponding message content 142. And the control part 104 produces | generates the dunning mail for every lessee which uses the specified message content as a text, and makes the mail address which specified the destination.

  The control unit 104 counts the total number of lessees who should send the specified reminder mail from the non-payment information database 150. Then, the control unit 104 divides the total number counted by the total number of time slots (here, 5) for sending the reminder mail. When the total number counted is not divisible by the number of time zones, the control unit 104 determines the number of mails to be transmitted in each time zone so that the remainder is distributed to any of the time zones. For example, when the total number counted is “107”, the debt management device 100 is set in each time zone (10 o'clock to 11 o'clock, 11 o'clock to 12 o'clock, 12 o'clock to 13 o'clock, 13 o'clock to 14 o'clock, (At 14:00 to 15:00), at least 21 reminder emails are sent, and the remaining two emails are sent one by one from the earliest in each time zone. Therefore, in this example, the debt management apparatus 100 has 22 messages from 10:00 to 11:00, 22 messages from 11:00 to 12:00, 21 messages from 12:00 to 13:00, 21 messages from 13:00 to 14:00, and 14:00 to 15:00. Send 21 reminder emails. Note that the 22 messages transmitted from 10 o'clock to 11 o'clock may be transmitted in a time zone between 10 o'clock and 11 o'clock, for example, 22 messages may be transmitted collectively at 10 o'clock. Alternatively, half of the 22 messages may be transmitted at 10 o'clock and the remaining half may be transmitted at 10:30. Alternatively, the number obtained by dividing 60 minutes by the number of emails to be sent may be sequentially sent as a sending interval for sending emails. It is good also as sending it collectively. For example, when 2400 messages are transmitted in 60 minutes, 40 messages may be transmitted every minute. And the control part 104 allocates each produced | generated reminder mail to each time slot | zone so that it may become the number of mails which should be transmitted in each time slot | zone. In this embodiment, which reminder mail is assigned to which time zone is determined at random. As a result, since the number of dunning emails to be sent in one time zone can be reduced, the number of calls made from the lessee's terminal can also be reduced in accordance with the sent dunning emails. It is possible to reduce the possibility that the merchant cannot answer the phone.

  Further, the control unit 104 refers to the unpaid number 122e in the lessee database 120 and detects whether there is data whose number is equal to or greater than a predetermined number (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 specifies a corresponding lessee ID. And the control part 104 collects the required information for entrusting a legal measure to a lawyer with respect to the lessee corresponding to the specified lessee ID. The control unit 104 reads list information 160 indicating necessary information for delegating legal measures to a lawyer from the storage unit 102. Here, the information required to delegate legal action to a lawyer may vary depending on the individual case. In other words, the necessary information for delegating legal measures to a lawyer includes information common to each case and information necessary for each case individually. For example, when a guarantor who has concluded a guarantee contract based on a lease contract takes legal measures, the lease contract, cancellation notice, and rent payment history information are information necessary for legal measures in common with each project. However, some information is owned by the lessor and may not be held by the guarantor. Such information is information that must be collected by the guarantor as information common to each case. On the other hand, because there are some renters who have entered into a parking lot use contract and others who do not have a parking lot use contract, etc., it is not information that is common to each project, but is required individually for each plan. Information. The control unit 104 transmits, via the communication unit 101, a mail requesting the person or group holding each piece of information included in the list information 160 to send the information. And when the input which shows having collected about each information from the operator of the debt management apparatus 100 via the input reception part 103 is received, the flag of a corresponding required document is switched to the value which shows collection completion. When all the flags in the list information 160 indicate that collection is complete, the control unit 104 outputs information indicating that collection of necessary information has been completed to the terminal 400 of the lawyer 401. If the flag does not change to a value indicating completion of collection even after waiting for a predetermined period (for example, one week), the control unit 104 sends an email requesting the person or organization holding the corresponding required document to send the 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 device 100, or by transmitting each information to an external device via a communication unit. It may be realized.

  As 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 lessee ID that leases the property rented by the lessee is identified with reference to the contract database 110 from the identified lessee ID. The control unit 104 identifies the e-mail address of the lessor indicated by the lessor ID from the lessor ID identified with reference to the contract database with reference to the lessor database 130. Then, the control unit 104 generates a mail whose destination is the specified mail address.

  The control unit 104 creates a proxy attached to the mail using the template information of the proxy stored in the storage unit 102. The control unit 104 creates a power of attorney by appropriately adding each of the lessor information, the lessee information, and the rental property information to the template information of the power of attorney as necessary.

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

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

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

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

  In addition, when receiving an instruction to create a request from the operator of the debt management apparatus 100 via the input receiving unit 103, the control unit 104 receives the designation of lease contract data and creates a request. The control unit 104 accepts designation of lease contract data, and extracts the lessor ID, lessee ID, and property information in the contract database 110. Based on the extracted information, a request form is created while referring to the lessee database 120 and the lessor database 130. Then, the control unit 104 outputs a request letter created 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, the various data which concern on the debt management apparatus 100 are demonstrated.

  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 a lease contract for the property indicated by the corresponding property information 113 is concluded between the lessee indicated by the lessee ID 111 and the lessor indicated by the lessor ID 112. It is.

  The lessee 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 relating to a property that is rented between the lessee indicated by the corresponding lessee ID 111 and the lessor indicated by the lessor 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 that is rented between the lessee and the lessor.

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

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

  In the example of FIG. 5, a person whose tenant ID 111 is “AAA” has a property “A Heights” in “Shibuya-ku, Tokyo ...” from a person whose tenant ID 112 is “aaa”. It can be understood that it is rented at “5,000 yen”. The contract database 110 may be deleted when new data is added each time the guarantor associated with the debt management apparatus 100 receives a guarantee for a new lease contract, and when the lease contract is canceled between the parties. Due to the presence of the contract database 110, the debt management apparatus 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 lessee database 120 is information in which a lessee ID 121 and lessee attribute information 122 are associated with each other. The lessee database 120 is information that defines information (attributes) related to lessees.

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

The lessee attribute information 122 is information indicating attributes relating to the lessee indicated by the lessee ID 121, and includes a name 122a, a gender 122b, an age 122c, an annual income 122d, an unpaid count 122e, a total delay count 122f, It includes a mail address 122g and a telephone number 122h.
The name 122a is information indicating the name of the lessee.
The sex 122b is information indicating the sex 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 non-payment count 122e is information indicating the number of times that the lessee has not paid the consideration to be paid every predetermined period within the predetermined period and has not yet fulfilled the debt. The unpaid number 122e is subtracted by the number of debts corresponding to the amount paid by the control unit 104 when there is a payment from a lessee who has delayed payment. Specifically, every time payment information indicating that payment has been made is received, the control unit 104 subtracts “1” from the corresponding non-payment count 122e.

  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 every predetermined period within the predetermined period. The total delay count 122f is incremented by “1” by the control unit 104 every time non-payment information about the corresponding lessee is received.

  The e-mail address 122g is information indicating an e-mail address set in the terminal owned by the lessee.

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

  In the example of FIG. 6, the lessee whose renter ID 121 is “AAA” has the name 122a of “Andrew”, the gender 122b of “male (M)”, and the age 122c of “23”. I am old. In addition, the annual income 122d of “Andrew” is “3.5 million yen”, and the unpaid number of times 122e is currently “4 times”, which means that the rent for four months is delinquent. The total number of delays 122f is “32 times”, the mail address 122g of the terminal “Andrew” is “AAA@docono.com”, and the telephone number 122h is “090-0598-AAAA”. Can understand. The lessee database 120 is added when a new lease contract is registered in the contract database 110 and the corresponding lessee is not registered in the lessee database 120. The information relating to the lessee is added by the operator of the debt management apparatus 100 via the input receiving 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 lessor 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 e-mail address 132b is information indicating an e-mail address set in the telephone held by the lessor.

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

  In the example of FIG. 7, the renter whose renter ID 131 is “aaa” has the name 132 a “Alex”. In addition, the mail address 132b of the terminal “Alex” is “aaa@bzweb.ne.jp”, the telephone number is “090-2342-aaa”, and the address is “Minato-ku, Tokyo ...”. I can understand that. The lessor database 130 is added when a new lease contract is registered in the contract database 110 and the corresponding lessor is not registered in the lessor database 130. The information relating to the lessor is added by the operator of the debt management device 100 via the input receiving 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 that defines the text content of the dunning mail.

  The delay condition 141 is information indicating a condition in which the lessee has delayed payment of the rent (consideration), and here, a condition based on at least one of the total number of delay times and the number of unpaid times is indicated. When there are multiple conditions, if each condition is connected with “and”, it indicates that all conditions are satisfied. If each condition is connected with “or”, one of the multiple conditions is satisfied. Indicates the case.

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

  In the example of FIG. 8, if the number of times that the lessee has delayed payment of the rent (consideration), that is, if the total number of delays is “5” and the number of unpaid is “1”, The content of the e-mail is sent as follows: “Thanks to the lessee, XX guarantee company. Can you call 090-XXX-XXX once? Thank you.” ing. Here, the name of the lessee is inserted in “lessee”. The message database 140 is set so that the content of the message becomes more severe for the lessee as the lessee delays payment of the consideration.

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

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

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

  The dunning mail transmission date and time 153 is information indicating the date and time when the dunning mail for calling the telephone is transmitted. If the dunning mail has not been sent yet, it becomes empty data. In FIG. 6, empty data is indicated by “−”. The dunning mail transmission date and time 153 is information indicating the date and time when the dunning mail was last transmitted.

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

  The telephone reception date and time 155 is information indicating the date and time when a telephone call is received from a lessee after transmission of a reminder 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 a lessee.

  The payment date and time 156 is information indicating the date and time when the corresponding lessee has paid the price. Unless date and time information is included in the payment date and time 156, the debt management apparatus 100 transmits a reminder email at regular intervals.

  In the example of FIG. 9, the lessee whose tenant ID 151 is “AAA” has not been able to pay the rent for “June 2016” by the due date at the end of May. Non-payment information was received at 10:00 on June 1, 2016 ". In accordance with the non-payment information, the debt management apparatus 100 transmits a reminder mail at “10:00 on June 2, 2016”. Upon receipt of the reminder mail, the lessee called the contractor 100 related to the debt management device 100 on “June 2, 2016” and rented the rent at “June 2, 2016 19:38”. You can understand that you are paying.

  FIG. 10 is a data conceptual diagram of list information 160 indicating information (documents) necessary for delegating legal measures to a lawyer. As shown in FIG. 10, the list information 160 is information in which necessary information (document) name 1001, 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 information (document) name 1001 and information on the information holder 1002 from an operator at an appropriate timing.

  Necessary information (document) name 1001 is information that can uniquely identify information and documents necessary for delegating a legal measure to a lawyer. Here, the name of the information is shown for easy understanding. . 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, it may be identification information uniquely assigned to the document name.

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

  The flag information 1003 is flag information indicating whether or not the corresponding necessary information (documents) has been collected. FIG. 10 shows the list information 160 in the initial state, and “0” is shown as information indicating that the information has not been collected. When the information can be collected, the control unit 104 indicates that information has been collected. To “1”. Here, the flag information 1003 is expressed by “1” and “0”. However, this is not limited thereto, and other information may be used as long as it is possible to specify whether or not necessary information (documents) has been collected. It is good also as realizing with expression of. The flag information 1003 is obtained when necessary information (documents) corresponding to the control unit 104 can be extracted from the storage unit 102 or from the operator of the debt management apparatus 100 via the input reception unit 103. When an input indicating that the data has been collected is received, 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 can monitor the progress of collecting the necessary information by monitoring the progress of collecting the necessary information. In addition, the operator can check the list information 160 and know that all necessary information has been prepared. 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 held by an operator. It may be displayed on the monitor of the terminal that performs.

  FIG. 11 is an example of proxy template information. The template information of the power of attorney 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 delegate information, a recipient address 1101 and a delegate name 1102, a text 1103, and a target person 1104 as information on a person or group subject to legal action. The property name 1105, the property address 1106, and date field 1107, the delegate name 1108, and the delegate address 1109 are included as delegate information.

  The person in charge address 1101 is information on the person in charge and is the address of a lawyer who requests legal measures from the debt management device 100.

  The name of the person in charge 1102 is the name of the person in charge and is the name of a lawyer who requests legal measures from the debt management apparatus 100.

  A text 1103 is a text of the power of attorney, and is information that is described in advance.

  The target person 1104 is the name of a person or group whose legal guarantee is taken by the guarantor related to the debt management apparatus 100 and whose rent is delinquent for a predetermined period or more. As the target person 1104, the name 122a of the data whose unpaid number 122e of the lessee database 120 exceeds 4 times is used.

  The property name 1105 is a property name that is rented by the person indicated by the target person 1104 and is behind with the rent. As the property name 1105, the property name 113a of the contract database 110 is used based on the lessee ID 121 specified from the data in which the number of unpaid 122e exceeds four.

  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 column where the delegator fills in, and is a column where the date when the delegator signs is signed. The date column 1107 is described in the proxy 1100 in advance.

  The name of the delegator 1108 is the name of the person who makes the delegation. In the example in this embodiment, since the guarantee company guarantees the lease contract (renewed the rent), the guarantee company is applicable. To do. The delegate 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 number of unpaid 122e exceeds 4 times, and assigns the identified lessor ID 112 to the identified lessor ID 112. Based on this, the name 132a of the lessor database 130 is used. In addition, if the lessor entrusts the lawyer to a lawyer, the lessor becomes the delegate.

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

  As described above, power of attorney 1100 is composed of information that can be acquired from the contents described in advance or data held by debt management apparatus 100, so that debt management apparatus 100 can use the template information of power of attorney 1100. , Can automatically create a proxy. Note that the power of attorney 1100 shown in FIG. 11 is an example, and it goes without saying that the content changes depending on the subject to be delegated and the content of legal measures.

  FIG. 12 shows an example of request template information. The request template information is image data to which the debt management apparatus 100 can write data. As shown in FIG. 12, the request form 1200 includes a date field 1201, a destination field 1202, a requester field 1203, a text 1204, a target person or group 1205, a lessor 1206, a lessee 1207, a property Name 1208.

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

  The address field 1202 is a destination to which a request is transmitted, and is an address related to the lawyer 410 with whom the debt management apparatus 100 is affiliated, and is an item described in advance.

  The requester column 1203 is information relating to the guarantee company related to the debt management apparatus 100, and is an item described in advance.

  A main text 1204 is a text indicating the content of a request for taking a legal measure, and is a matter described in advance.

  The target person or group 1205 is a person or group that is subject to legal action. 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 a person who has leased the property to the person or group indicated by the target person or group 1205. The lessor 1206 uses the name 132a obtained by referring to the lessor database 130 using the lessor ID in the contract database 110 specified from the input lessee ID.

  The lessee 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 that leases the property.

  The property name 1208 is the name of the property borrowed from the lessor indicated by the lessor 1206 by the lessee indicated by the lessee 1207. 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, since the debt management apparatus 100 can create a request, it is possible to reduce the burden on the guarantor. The request form shown in FIG. 12 is also an example.

  The above is the description of the data related 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 an operation when the debt management device 100 receives non-payment information and payment information.

  As illustrated 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 non-payment information (YES in step S1301), the communication unit 101 transmits the non-payment information to the control unit 104.

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

  Next, the control unit 104 extracts the lessee ID and the non-payment period from the non-payment information transmitted. The control unit 104 newly registers the extracted lessee ID in the lessee ID 151 of the non-payment information database 150. The control unit 104 registers the non-payment period extracted from the non-payment information in the non-payment period 154 of the non-payment information database 150 in association with the registered lessee ID. Then, the control unit 104 registers the date and time when the non-payment information is received in the received 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 non-payment information (NO in step S1301) but is payment information (YES in step S1304), the communication unit 101 transmits the received payment information to the control unit 104. . If it is not 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 a lessee ID from the transmitted payment information. Then, the control unit 104 searches the lessee database 120 based on the lessee ID extracted from the payment information. Then, the renter database 120 is updated by subtracting “1” from the unpaid number 122e of the searched data, that is, the data corresponding to the renter ID of the payment information (step S1305).

  The control unit 104 extracts a lessee ID and a non-payment period from the transmitted payment information. The control unit 104 detects data corresponding to the extracted lessee ID and the non-payment period from the non-payment 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, the non-payment information database 150 is updated (step S1306), and the process returns to step S1301.

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

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

  As shown in FIG. 14, the control unit 104 of the debt management apparatus 100 determines whether or not the transmission timing of the reminder mail has arrived based on the schedule (step S1401). It is assumed that the schedule is set in advance to start at a predetermined time (for example, 10:00) every 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 comes (NO in step S1401).

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

  The control unit 104 divides the counted number as the total number of the dunning mails to be transmitted by the number of time zones (5 in this embodiment) for transmitting the dunning mails. Thereby, the number of dunning mails which should be transmitted in each time slot can be specified (Step S1403).

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

  The control unit 104 generates a mail with the acquired mail address as a transmission destination for each lessee ID. Specifically, the control unit 104 acquires the unpaid number 122e and the total number of delays 122f in the lessee database 120 for each lessee ID 151 acquired in step S1404. Then, for each of the acquired non-payment count 122e and the total delay count 122f, it is specified which of the delay conditions 141 of the message database 140 is satisfied. Then, an e-mail is generated with the message content 142 corresponding to the delay condition specified as satisfied as the e-mail body (step S1405).

  The control unit 104 assigns 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 of the time zone assigned to each generated reminder mail is assigned as the transmission time.

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

  The above is the operation related to the transmission of the reminder mail of the debt management apparatus 100.

  FIG. 15 is a flowchart showing an operation related to a collection process for collecting information (documents) required for the debt management apparatus 100 to transfer authority related to debt to a lawyer.

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

  When there is data for which the number of unpaid times 122e is equal to or greater than the predetermined number of times (YES in step S1501), the control unit 104 executes the process of step S1502, and when there is no data for which the number of unpaid times 122e is equal to or greater than the predetermined number of times ( In step S1501, NO), the process ends. In this case, the transfer target subject to legal action is automatically identified based on the number of outstanding payments 122e, but this is not the case, and the operator does not take legal action against a specific debtor. If the decision is taken, the specific debtor can be manually entered as the person to be transferred. Moreover, before transferring to legal measures, the control unit 104 of the debt management measure 100 actually transfers the information to the monitor connected to the debt management device 100 together with information that can identify the prospective person to be transferred. It is also possible to display a GUI that inquires whether or not to perform the process, and after receiving a determination input for the transfer process for the displayed GUI, the subsequent transfer process may be executed.

  In step S1502, the control unit 104 identifies the lessor ID of data whose unpaid number 122e is equal to or greater than the predetermined number (step S1502). Then, the control unit 104 reads the list information 160 stored in the storage unit 102 (step S1503).

  The control unit 104 executes proxy creation / transmission processing (step S1504). Details of the proxy creation / transmission process will be described later. In addition, the control unit 104 executes a request form creation process (step S1504). Details of the request form 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. (Step S1506).

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

  The control unit 104 determines whether there is a receipt input indicating that 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 recording of necessary information (document) in the storage unit 102 of electronic data. 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 having the name of the electronic file as “lease contract” is the same as the information name, When stored in the storage unit 102, the control unit 104 may determine that a “rental contract” has been received.

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

  Next, the control unit 104 determines whether or not a predetermined time (for example, 5 days) has elapsed since the e-mail requesting transmission of the required document has been transmitted (step S1510). This predetermined time is a reference time for waiting until receipt after sending an email 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 or not all the flag information 1003 is “1” in the list information 160, that is, all the necessary information. It is determined whether information and documents to be collected have been collected (step S1511). If the flag information 1003 is not all “1” (NO in step S1511), the process returns to step S1507. As a result, it is possible to prompt the information holder who has not sent the document by sending an e-mail again. When all the flag information 1003 is “1” (YES in step S1511), the control unit 104 notifies the operator's terminal that the necessary 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 form created in step S1505 and send it to the terminal 400 of the lawyer 410 by mail. The original document is mailed separately to the lawyer 410 by the operator.

  With the above processing, the debt management apparatus 100 can collect documents required when requesting legal measures related to debts from a lawyer. Can do.

  FIG. 16 is a flowchart showing an operation related to the transmission of the proxy transmission mail by the debt management apparatus 100.

  As shown in FIG. 16, the control unit 104 of the debt management apparatus 100 identifies the lessee 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 identified lessee ID 121, identifies the corresponding lessor ID 112, the property name 113a as the property information, and the 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 mail address 132b, and extracts the information (step S1603).

  Based on the name 122a extracted in step S1601, the property name 113a and 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 out and a proxy is created (step S1604).

  The control unit 104 creates a mail requesting the stamp (signature) for the extracted power of attorney destined for the mail address 132b extracted in step S1603 (step S1605).

  The control unit 104 attaches the proxy generated in step S1605 to the generated mail. When the proxy 104 is attached to the e-mail, the control unit 104 transmits the e-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 can create a power of attorney that delegates the authority for the guarantor to take legal action with respect to the lessee 210, and can automatically transmit it to the lessor 310. it can.

  FIG. 17 is a flowchart showing an operation related to the creation of a request form by the debt management apparatus 100.

  As shown in FIG. 17, upon receipt of the original power of attorney signed from the lessor 310, the guarantor inputs a request letter creation instruction to the input receiving unit 103 of the debt management apparatus 100. When the input receiving unit 103 of the debt management apparatus 100 receives an instruction input for request form creation (step S1701), the input receiving unit 103 transmits it to the control unit 104.

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

  When the control unit 104 receives the request form creation instruction input, the control unit 104 reads the template information of the request form stored in the storage unit 102 (step S1703).

  When receiving the input of the lessee ID, the control unit 104 reads the name 122a for the lessee ID from the lessee 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 a property name from the identified property name 113a (step S1705).

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

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

  The control unit 104 outputs the created request form to an external device via the communication unit 101 (step S1708), and ends the process. Here, the external apparatus may display the created request form as a monitor, for example, or may print out the created request form as a printer. Further, when the letter to be sent to the lawyer 410 is only a 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 according to the request form creation.

<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 a reminder mail when the lessee is “Andrew” and the total number of delays of “Andrew” is “less than 10”.

  FIG. 18B shows the case where the lessee is “Andrew” and the number of unpaid “Andrew” satisfies “3 times or more” or the total number of delays “50 times or more”. The display example of dunning mail is shown.

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

  FIG. 19 shows a display example on the terminal 300 held by the lessor 310 of the document sending request mail transmitted from the debt management device 100 to the lessor. The document sending request mail is a mail that the debt management device 100 transmits to a person or group holding the document as necessary information, and includes contents for requesting the sending of the document. Here, an example of an e-mail when the debt management apparatus 100 requests the sending of a lease contract as a document to be sent is shown.

  As shown in FIG. 19, the email requesting the sending of the lease contract is transmitted to the lessor who rents the property to the lessee who has not fulfilled the contract. The 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 Is specified by the control unit 104 of the debt management apparatus 100.

  In FIG. 19, the text of the document sending 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 described above, the address 1901 uses a name associated with the lessor ID specified from the lessee ID. The object 1902 uses a name associated with the lessee ID. The same name as the name used for the address 1901 is used for the information holder 1903, and the same name as the target 1902 is used for the target 1904.

  In this way, the debt management apparatus 100 can create and send a document sending request mail. Then, the lessor 310 can confirm that the lease contract must be sent as a necessary document by receiving and viewing this mail at the terminal 300.

<Summary>
As shown in the above embodiment, the debt management apparatus 100 is required to detect a lessee who has failed to perform a contract more than a predetermined number of times and to request a lawyer regarding the default of the contract to a lawyer. Can assist in collecting and presenting documents. In addition, as part of the support, the debt management apparatus 100 automatically determines the lease contract related to the lessee and the lessor, and automatically uses the previously stored proxy template. A power of attorney can be created. Therefore, it is possible to reduce the burden of processing when executing a lawsuit relating to the guarantee business.

<Supplement>
Although the debt management apparatus 100 has been described according to the above embodiment, it goes without saying that the debt management apparatus 100 may be realized by other methods. 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 dunning mails to be transmitted by the number of transmission time zones, and randomly extracts the dunning mails so as to be the number. However, it is also possible to determine the time zone to be assigned according to the other party who sends the reminder mail so that the timing of receiving calls is not concentrated. Thereby, further efficiency improvement can be achieved. Hereinafter, the structure which the debt management apparatus 100 can take as a technique for that is demonstrated.

  (1-1) A time zone in which a dunning mail is transmitted is determined according to the past telephone performance so as to meet the timing at which it is assumed that the lessee can easily make a call.

    The non-payment information database 150 stores information on the date and time when a telephone call is made in response to a reminder email for each renter who has delinquently rented. Therefore, for each lessee, from the date and time information, it can be estimated that the time when the lessee made a call is a time zone in which the lessee can easily make a call. Therefore, the control unit 104 may take a configuration in which the date and time information on the calls of the lessees with the same lessee ID is averaged and the reminder mail is transmitted in the time zone closest to the average date and time.

  (1-2) A time zone for transmitting the reminder mail is determined according to the speed of the response from the transmission of the reminder mail according to the past telephone results.

    The non-payment information database 150 stores information on the date and time when a telephone call is made in response to a reminder email for each renter who has delinquently rented. The non-payment information database 150 also stores the transmission date and time when the dunning mail is transmitted. The control unit 104 can specify the speed of response to the urgency mail of each lessee from the difference between these times. A renter with a quick response can expect to make a call within the time zone in which the dunning mail is sent, regardless of which time zone the dunning mail is sent. Therefore, it can be estimated that such a lessee can transmit the reminder mail so as to be dispersed in each time zone as much as possible so that the time zone for receiving calls can be concentrated as little as possible. Therefore, the control unit 104 calculates the response time for the reminder mail for the lessee who has been behind with the rent. If multiple data are registered for the same lessee, the average response time is calculated. Then, a lessee whose calculated response time (or an average value thereof) is equal to or less than a predetermined threshold (for example, 1 hour) is specified. And the control part 104 determines the time slot | zone which transmits a reminder mail so that a lessee whose response time (or the average value) is below a predetermined threshold may be disperse | distributed to each time slot | zone as much as possible.

  (1-3) A time zone for transmitting the reminder mail is determined according to the lessee attribute information.

    Although not shown in the lessee database 120 shown in FIG. 2 of the above embodiment, the lessee 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, it is good also as determining the time slot | zone which transmits a dunning mail from the attribute information of a tenant's occupation.

  For example, if the occupation of the lessee is a company employee, the control unit 104 avoids a time period estimated to be a normal job, and sends a reminder email at a time period such as before work, during lunch break, or after work. It may be configured. Or, if the occupation of the lessee is a full-time housewife, it can be assumed that it is basically easy to make a call at any time, so when deciding when to send, May be determined. Alternatively, if the occupation of the lessee is the restaurant business, the time zone for sending the reminder mail may be determined avoiding the time zone for meals. In addition, it is possible to send a reminder email at noon to a lessee who works in the day, and send a reminder email at night to a lessee who works 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 renter's unpaid number 122e and the total number of delays 122f. The condition for determining may be determined using conditions other than the unpaid count 122e and the total delay count 122f as conditions.

  For example, lessee personality information may be stored in the lessee database 120 in association with each lessee. In this case, the message database 140 may be information in which personality information and message content are associated with each other. For example, for a tenant with a serious personality, you may improve the possibility of making a call with a polite message, or for a tenant with a weak personality, a somewhat intimidating email The possibility of making a phone call may be improved, and the possibility of making a phone call with a mild expression as much as possible may be improved for a renter who tends to get angry. In addition, the content of the dunning email may be changed according to the lessee's information such as the lessee's gender, age, occupation, annual income, delinquency history (total number of delays and unpaid) Good. For this purpose, the message database 140 may be information in which information on a lessee is associated with the content of the text and associated with the lessee's information to indicate to the lessee what kind of reminder email to send.

  The number of incoming calls can also be adjusted according to the text content of the reminder mail. For example, the number of received power increases when the content of the email text is "Please just transfer" or "Please call me" if the content is "Please call me" Tend. Therefore, the message database 140 may have a configuration in which different text contents are associated in accordance with the non-payment history. For example, for a person who has a total delay number of 30 or more, put a sentence “Please call” in the text content, and for a person who has a total delay number of less than 30, simply add “ It may be configured to include the statement “Please transfer money”. With this configuration, the number of received power from the lessee can be adjusted according to the text content of the dunning mail.

  By taking such a configuration and transmitting a reminder mail tailored to attributes such as the lessee's personality and occupation, the possibility of the lessee calling may be improved.

  (3) Although not described in the above embodiment, the debt management device 100 transmits a reminder email once, and then receives a telephone reception date and time 155 of the non-payment information database 150 after a certain time (for example, two hours later). If the date / time information is not included in the message, the reminder mail may be transmitted again. Thereby, the possibility that the lessee makes a call can be increased.

  (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 limited thereto. Necessary information from the communication unit 101 may be received from the terminal 300 of the lessor 310 and the control unit 104 may update the information. For example, the terminal 300 transmits contract information including a lessor, a lessee, and property information necessary for updating the contract database 110 to the debt management apparatus 100, and the debt management apparatus 100 receives the received 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 non-payment information transmitted when the lessee fails to pay the consideration in the 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 determine whether to send a telephone reminder email at this timing. For example, at the rent delinquency stage in the first month, the telephone reminder email is not sent and the rent is delinquent for two consecutive months. It is also possible to send a telephone reminder email for the first time at the timing.

  (6) In the above embodiment, the non-payment information and the payment information when the renter who has not paid the consideration paid the compensation received the renter database 120 or the non-payment information database 150. Although the example which performs update of this was demonstrated, this is not the limitation. For each lessee, the same configuration can be realized simply by accepting only payment information indicating that payment has been made, that is, a lessee who has not received payment information within a predetermined period of time to pay the consideration. With respect to the above, the same configuration as in the above embodiment can be realized by adding 1 to the total number of delays and the number of unpaid and registering in the non-payment information database.

  (7) In the above embodiment, the debt management device 100 has shown an example in which the text of the telephone reminder email is changed according to the total number of rent payment delays or the number of consecutive 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 or the number of unpaid payments.

  (8) In the above embodiment, the payment information is transmitted every one period. However, this is not the case, and when the lessee has paid for a plurality of periods together, The payment information may be transmitted at a time including information for a period during which the consideration is paid. In this case, the control unit 104 extracts information for a period included in the payment information, and registers the date and time when the payment information is received in the payment date and time 156 of a plurality of periods corresponding thereto, and updates the non-payment information database 150. It is good to do.

  (9) In the above embodiment, the debt management apparatus 100 has shown an example in which a request is created by accepting designation of one piece of data in the contract database 110 from the operator, but this is not limited thereto. If a request letter can be created, it may be created in another form. For example, the debt management apparatus 100 creates a proxy for a matter for which a legal action is taken, but this proxy may be designated. As described above, since the power of attorney contains various corresponding information included in the request, information sufficient for creating the request can be prepared.

  (10) In the above embodiment, there is no particular description about the case where the lessee rents a plurality of properties. However, when a lessee rents a plurality of properties, it is necessary to register each lease contract in the contract database 110 as well. In addition, since there is a possibility that a plurality of the same lessees are registered in the lessee ID, identification information is associated with each lease contract so that the lease contracts can be more clearly distinguished. The lessee database 120 is configured to count the number of unpaid payments and the total number of delays for each property, and also stores the corresponding lease contract identification information in association with each other. If each database is configured in this way, the identification of the lease contract is specified when creating a proxy or request, etc., and the creation of a proxy or request is executed by uniquely identifying the lease be able to.

  (11) The guarantee business described above is one aspect related to the 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 stipulates that payment should be paid periodically or multiple times from one to the other. It is not limited to the guarantee contract related to the lease contract as shown in the embodiment. In addition, the two parties mentioned here may be individuals or some kind of organization, for example, a company. Specific examples of contracts here include, for example, (i) when a lessor manages a claim to a lessee in a lease contract, or (ii) a claim management entrusted by a lessor in a lease contract If the company manages the claims to the lessee, (iii) if it manages the claims arising on the purchase and sale price based on the ongoing sales contract, or (iv) based on the hospital medical fee contract This includes various cases such as managing the receivables. Needless to say, the specific embodiment is appropriately changed according to the contents of the contract. For example, when a guarantee company in a guarantee contract uses a debt management device, the non-payment information is transmitted to the debt management device from the terminal of the lessor or the trader who manages the rent of the lessor. However, if the rent management company of the lease contract uses the debt management device, the non-payment information will be sent to the debt management device from the bank that handles the bank account to which the lessee pays the rent to the lessor. Become.

  (12) The debt management apparatus 100 in the above embodiment works effectively in the management of the debt by the lessor in addition to the management by the guarantor, as in the aspect shown in the above embodiment.

  (13) In the above embodiment, the delegation of legal measures to a lawyer has been described, but the scope of authority to be delegated is not particularly described. Therefore, the scope of authority to be delegated is briefly described here. For example, in the case of a lawsuit in which the lessor is suing for rent, the lawyer is granted the right to act on the notice of building clearing claim, unpaid rent payment lawsuit, and lease contract cancellation. In case of a lawsuit filed against a lease by a guarantor, the attorney is granted the right to act on the claim for compensation. At this time, the debt management apparatus 100 creates a proxy for both cases. Therefore, the storage unit 102 stores template information corresponding to the subject to be delegated, and the control unit 104 creates a delegation letter corresponding to each delegation content. Further, as shown in the supplement (12) above, when the lessor uses the debt management device 100 as a device for supporting the process for delegating legal measures to a lawyer, the lessor In relation to lawsuits that are scheduled against the property, the lessor will grant the lawyer the right to act on the building clearing claim lawsuit, the unpaid rent demand lawsuit, and the lease contract cancellation notice.

  (14) In the above embodiment, each part of the debt management device 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. Each functional unit may be realized by one or a plurality of integrated circuits, and the functions of the plurality of functional units may be realized by a single integrated circuit. An LSI may be called a VLSI, a super LSI, an ultra LSI, or the like depending on the degree of integration. The circuit may be realized by a reconfigurable circuit (for example, FPGA: Field Programmable Gate Away). When the debt management device 100 is configured by a circuit, for example, as shown in FIG. 20, the debt management device 100 may be configured by a communication circuit 101a, a storage circuit 102a, an input reception circuit 103a, and a control circuit 104a. The same function as each functional unit shown in the above embodiment is realized.

  When each functional unit of the debt management apparatus 100 is realized by software, the debt management apparatus 100 is configured to execute a command of a debt management program, which is software that implements each function, the debt management program and various data stored in a computer (or A ROM (Read Only Memory) or a storage device (referred to as “recording medium”) recorded so as to be readable by a CPU), a RAM (Random Access Memory) for developing the debt management program, and the like are provided. And the objective of this invention is achieved when a computer (or CPU) reads the said debt management program from the said recording medium, and is performed. As the recording medium, a “non-temporary tangible medium” such as a tape, a disk, a card, a semiconductor memory, a programmable logic circuit, or the like can be used. Moreover, the said debt management program may be supplied to the said computer via arbitrary transmission media (a communication network, a broadcast wave, etc.) which can transmit the said 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 examples, it should be noted that those skilled in the art can easily make various changes 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 included in each means, each step, etc. can be rearranged so that there is no logical contradiction, and a plurality of means, steps, etc. can be combined or divided into one. .

  (16) The configuration shown in the above embodiment and the configuration shown in the reference example may be combined as appropriate.

100 Debt management device 101 Communication unit 102 Storage unit 103 Input reception unit 104 Control unit

Claims (7)

A debt management device that collects the necessary information to delegate legal action against a debtor who does not fulfill a debt to a lawyer,
A list information storage unit for storing list information including the name of the necessary information and contact information of the holder of the necessary information;
A debt management device comprising: a communication unit that performs communication for requesting the holder to send the necessary information to the holder based on the list information. The list information includes flag information indicating whether the necessary information has been sent,
The debt management device further includes:
A determination unit for determining whether or not the necessary information has been sent;
The debt management device according to claim 1, further comprising: a switching unit that switches the flag information based on the determination of the determination unit. The debt management device further includes, based on the flag information, a re-communication unit that performs communication for requesting transmission of the necessary information to a holder of the necessary information to which the necessary information has not been transmitted. The debt management apparatus according to claim 2, wherein the debt management apparatus is provided. The debt management device further includes:
The debt management apparatus according to claim 3, further comprising a display unit that displays the list information. The debt management device further includes:
A necessary information storage unit for storing the necessary information;
The debt management device according to any one of claims 1 to 4, further comprising a necessary information sending unit that sends the necessary information stored in the necessary information storage unit. A debt management method by a debt management device that collects necessary information for delegating legal measures against a debtor who does not fulfill a debt to a lawyer,
A list information storage step for storing list information including a name of the necessary information and contact information of a holder of the necessary information;
A debt management method including a communication step of performing communication for requesting the holder to send the necessary information to the holder based on the list information. On the computer of the debt management device that collects the necessary information to delegate the legal action against the debtor who does not fulfill the debt to the lawyer,
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 for performing communication for requesting the holder to send the necessary information based on the list information.

Images