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

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 kind of guarantee business, there is a guarantee of a lease contract in which a lessee obtains a right to use a property by paying a rent to the lessor. The guarantee here guarantees that the lessee will surely pay the rent to the lessor, and guarantees that the rent will be paid instead if the renter delays the payment of the rent. It is also what you do. 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.

  In Patent Document 1, regarding the rent-related costs of rental properties, the effort to find a joint guarantor is reduced, the initial burden of deposits, security deposits, key money, etc. is reduced, the occupancy examination time is shortened, and the tenant / real estate management company / A system has been proposed for leasing companies that reduces the financial time burden and the recovery risk associated with leasing.

JP, 2006-71724, A

  In such a guarantee service, the guarantee operator does not immediately pay the rent on behalf of the lessee if the lessee does not pay the rent. In order to inquire about the situation, an email requesting to make a call may be sent.

  By the way, if the number of lease contracts guaranteed by the guarantee service provider increases, and the number of lessees who did not pay the rent without observing the contract increases, the volume of telephone reminder emails to be transmitted becomes enormous. As a result, the number of telephone calls made by the lessee increases, and if the telephone calls are concentrated, there is a problem that the guarantee operator may not be able to respond even if the lessee calls.

  Accordingly, the present invention has been made in view of the above problems, and an object thereof is to provide a debt management apparatus that performs guarantee work so that lessees' telephones are not concentrated as much as possible.

  In order to solve the above problems, the debt management device according to one aspect of the present invention may transmit a message to each of the plurality of debtors when there are a plurality of debtors who have delayed the performance of the debts. A debt management apparatus capable of allocating a message transmission timing according to a predetermined standard and a transmission unit for transmitting a message at a timing allocated by the allocation unit.

  In order to solve the above-described problem, the debt management method according to one aspect of the present invention provides a debt management method for transmitting a message to each of the plurality of debtors when there are a plurality of debtors whose implementation of the debt is delayed. The method includes an assigning step of assigning a timing for transmitting the message according to a predetermined criterion, and a transmitting step of transmitting the message at the timing assigned in the assigning step.

  In order to solve the above-described problem, the debt management program according to one aspect of the present invention may transmit a message to each of the plurality of debtors when there are a plurality of debtors who have delayed the performance of the debts. A debt management program that enables a computer to realize an assignment function for assigning a message transmission timing and a transmission function for sending a message at a timing assigned by the assignment function according to a predetermined standard.

  Further, in the debt management device, the allocating unit distributes the total number of messages to be transmitted before a predetermined time limit according to the number of time zones for transmitting the message to each time zone. It is good also as assigning the timing which transmits a message on the basis of these.

  Further, in the debt management apparatus, the message includes a content for requesting a telephone call, and the allocating unit according to the number of persons who can respond to the call for each of a plurality of time zones as a predetermined standard. The timing for transmitting a message may be assigned.

  In the debt management device, the debt management device may include a storage unit that stores information about the debtor, and the assigning unit may assign timing to the message based on information about the debtor as a predetermined reference. ,

  Further, in the debt management device, the debt management device further includes a management unit that stores payment delay information indicating that the debtor has made a non-payment, and the transmission unit sends a message in accordance with the payment delay information. It is good also as sending the message which changed the content of. Note that the payment delay information here refers to the number of non-payments and the total number of delays, which will be described later, and includes information such as the total number of defaults and the number of defaults (the number of times when debts are not included). As good as

  Moreover, in the said debt management apparatus, the management part may further memorize | store the information regarding a debtor, and a transmission part is good also as transmitting the message which changed the content of the message based on the information regarding a debtor.

  A debt management device, a debt management method, and a debt management program according to an aspect of the present invention transmit emails requesting a telephone call to a lessee in divided time zones. Therefore, it is possible to suppress as much as possible that the renters who call the phone after seeing the mail concentrate on the hour.

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 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 rental 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 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 block diagram which shows the function structural example of a debt management apparatus.

  The debt management device according to the present invention is a device capable of transmitting a message to each of the plurality of debtors when there are a plurality of debtors who have delayed the performance of the debts. The debt management device includes an assigning unit that assigns a timing for transmitting a message according to a predetermined criterion, and a transmitting unit that transmits the message at a timing assigned by the assigning unit.

  Here, the “debt management device” is a device that transmits a message to the debtor when the debtor is late in fulfilling the debt. The debt management device is also a device that supports a task of managing a debt contract exchanged between a creditor and a debtor. Here, operations related to the management of debt contracts include, for example, management of whether debts are actually being fulfilled, and claims to the debtor when the debtor is not fulfilling the debt. Good. 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.

  The “debtor” 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.

  Here, in the debt management apparatus, the “assignment unit” assigns the message transmission timing to the message, and is, for example, a processor or a dedicated circuit, but is not limited thereto. In the following, the assigning unit corresponds to the control unit 104. The allocating unit determines the total number of messages to be transmitted by a predetermined time limit in accordance with the number of time zones for transmitting the message and distributing the messages to be transmitted to each time zone as a predetermined reference. May be assigned. Alternatively, if the message includes a content requesting a call, the allocating unit may send a message according to the number of persons who can respond to the call for each of a plurality of time periods as a predetermined criterion. The transmission timing may be assigned. When the debt management device includes a storage unit that stores information about the debtor, the assignment unit may assign timing to the message based on information about the debtor as a predetermined reference.

  Here, the “predetermined standard” is a condition for determining at which timing a message for which debtor is to be transmitted. The conditions here are determined according to various conditions such as a time zone for transmitting a message, the number of time zones, the number of messages to be transmitted, and the attributes of the debtor of the transmission destination. For example, when there are X time periods for transmitting a message and the number of messages to be transmitted is Y, a standard that defines in which time period the Y messages are to be transmitted. However, this is not a limitation. In the following, in the embodiment, an example in which Y messages are distributed and transmitted as evenly as possible in X time zones is shown, and various specific examples are shown in supplement (1).

  Further, the “message” refers to a communication message for transmitting the contents relating to the debt transmitted from the debt management device to the terminal held by the debtor. The message is means for exchanging information such as e-mail, SMS (Short Message Service), and twitter (registered trademark). Here, “message content” is, for example, a communication message that tells the debtor the content of a call request, but the message content is not limited to this. For example, the URL of the website is also included in the content of the message. The message corresponds to a reminder mail in the following embodiment.

  The “message transmission timing” refers to the time for transmitting a message from the debt management device to the terminal held by the debtor. This time may be a one-time (one-time) time or a time having a time width. In the case of a time with a time width, the timing for transmitting a message corresponds to any time within the time width. In the following, as an example of the timing of message transmission, the time zone from 10 o'clock to 11 o'clock, the time zone from 11 o'clock to 12 o'clock, the time zone from 12 o'clock to 13 o'clock, the time zone from 13 o'clock to 14 o'clock, 14 Although the time zone from 15:00 to 15:00 is shown, the timing for transmitting a message is not limited to this example. The “number of time zones” refers to the time or number of time zones during which a message is transmitted when it is determined that the message is to be transmitted separately. In the above example, the number of time zones is 5, but the number of time zones for transmitting a message is not limited to 5. Further, the unit of the time zone does not need to be an hour unit, and may be, for example, a unit of two hours or a unit of one day as long as it is a unit of a predetermined time width.

  Further, the “predetermined deadline” is a deadline for sending a message to be sent to the debtor, and the date and time. This predetermined time limit is determined in advance by an administrator who manages the debt management device. The predetermined deadline is, for example, the end of the month if the debtor's performance is managed on a monthly basis, or the weekend, that is, until 18:00 on Friday if managed on a weekly basis. Further, a plurality of predetermined deadlines may be provided within a certain period, and may be determined, for example, as 18:00 on Monday, 18:00 on Wednesday, and 18:00 on Friday in one week. The predetermined time limit is not limited to these examples.

  “Distributing” a message in a time zone means that, for a plurality of messages to be transmitted by a predetermined time limit, each message is assigned to one of the time zones in which the message is determined to be transmitted. More specifically, it refers to associating a message with a time zone or time information for transmitting the message. For example, when 300 messages are transmitted and there are three message transmission time zones from the first time zone to the third time zone, 100 of the 300 messages are sent to the first time zone. Although it is assigned to the band, the other 100 messages are assigned to the second time zone, and the remaining 100 messages are assigned to the third time zone, this is not limited to this example.

  “Contents of requesting a call” refers to information requesting a call directly or indirectly, for example, a sentence such as “Please call me” or a phone number. It may be something that indirectly requests a call. Note that the content of requesting a call for a phone is not limited to this example.

  The “total number of messages” is the total number of messages to be transmitted before a predetermined time limit. The total number of messages basically corresponds to the number of obligors who have not fulfilled their obligations. For example, if there are 100 obligors who have not fulfilled their obligations even after their obligations have expired. The total number of messages is 100, but the example of the total number of messages is not limited to this.

  In addition, the “number of persons who can respond to a call” is the number of persons who can make a telephone response to a call made by a debtor, for example, the number of telephone operators on the debt management device side. This refers to the maximum number of people who can answer a call at one time (one hour), but is not limited to this example.

  Further, in the debt management device, the “transmission unit” transmits a message to a terminal held by the debtor at a timing assigned to the allocation unit for the message, and is, for example, a communication interface. It is not limited to this. In the following, the communication unit 101 corresponds to the transmission unit.

  In addition, when the debt management device further includes a management unit that stores payment delay information indicating that the debtor has made a non-payment, the transmission unit changes the content of the message according to the payment delay information The message may be transmitted.

  Here, the “payment delay information” is information indicating that at least the debtor has not fulfilled part or all of the debt by the deadline related to the debt. For example, the debtor A fulfills the debt. This is written data that is not included, but is not limited to this. The payment delay information corresponds to non-payment information in the following.

  “Message content” refers to the content of the message body, such as “Please call” or “Pay rent”, but is not limited to this. . Also, changing the content of the message means changing the matter to be communicated to the debtor, that is, the content of the message, its expression, or tone.

  The management unit may further store information on the debtor, and the transmission unit may transmit a message in which the content of the message is changed based on the information on the debtor.

  Here, “information about the debtor” is attribute information that characterizes the debtor, for example, information such as the debtor's name, age, occupation, gender, personality, and preference. It is not limited to.

  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 informed to the lessee 210. A power of attorney for obtaining permission to take measures is transmitted to the terminal 300 of the lessor 310, or (3) a request for actual legal action is sent to the terminal of the legal business worker (lawyer) 410. Or send to 400.

  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 e-mail for prompting (requesting) a call to the lessee among the guarantee work performed by the debt management device 100.

  In FIG. 2, T0 to T1, T1 to T2, and T2 to T3 are set as predetermined periods A, B, and C, respectively. 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. The reminder email requesting a phone call contains “Please call me” in the email body and includes an email requesting a phone call directly. "Please pay the rent", and emails that indirectly request phone calls, such as emails with phone numbers. 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. Hereinafter, details of the debt management device 100 will be described.

  FIG. 3 is a block diagram illustrating an example of a functional configuration of the debt management apparatus 100. As shown in FIG. 3, 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 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, and a non-payment information database 150. The contract database 110 is information indicating that a lease contract is exchanged by associating information indicating a lessee with information 5831 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. Details of the contract database 110, the lessee database 120, the lessor database 130, the message database 140, and the non-payment information database 150 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 generates a message for prompting the lessee to make a telephone request, and an allocation unit that allocates a time zone for transmitting the generated message to any one of a plurality of predetermined time zones And it functions as a management unit that accepts non-payment information from the communication unit 101 and updates the lessee database 120 and non-payment information database.

  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.

  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. 4 is a data conceptual diagram showing a data configuration example of the contract database 110. As shown in FIG. 4, 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. 4, 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 is 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 is deleted 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. 5 is a data conceptual diagram showing a data configuration example of the lessee database 120. As shown in FIG. 5, the lessee database 120 is information in which 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. 4 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. 5, 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. 6 is a data conceptual diagram showing a data configuration example of the lessor database 130. As shown in FIG. 6, 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. 4 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. 6, 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. 7 is a data conceptual diagram showing a data configuration example of the message database 140. As shown in FIG. 7, the message database 140 is information in which the delay condition 141 is associated with the message content 142. 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. 7, if the lessee has delayed payment of 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. 8 is a data conceptual diagram showing a data configuration example of the non-payment information database 150. As shown in FIG. 8, 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. 4 and 5 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. 8, the 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. 8, the lessee whose tenant ID 151 is “AAA” could not pay the rent for “May 2016” during the period. Non-payment information was received at 10:00 on the 1st of the month. In accordance with the non-payment information, the debt management device 100 transmits a reminder mail “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.

  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 FIG.9 and FIG.10. FIG. 9 is a flowchart showing an operation when the debt management device 100 receives non-payment information and payment information.

  As shown in FIG. 9, 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 S <b> 901), 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 S902). ).

  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. 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 S903), and returns to step S901.

  In step S901, when the received signal is not non-payment information (NO in step S901) but is payment information (YES in step S902), the communication unit 101 transmits the received payment information to the control unit 104. . If it is not payment information (NO in step S902), the process returns to step S901 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 S905).

  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 S903), and the process returns to step S901.

  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. 10 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 apparatus 100.

  As shown in FIG. 10, 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 S1001). 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 stands by until the transmission timing arrives (NO in step S1001).

  When the transmission timing of the reminder mail arrives (YES in step S1001), 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. 8, “−” is shown). The number of pieces of data at the location) is counted (step S1002).

  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 S1003).

  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 S1004).

  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 number of unpaid times 122e and the total number of delays 122f in the lessee database 120 for each lessee ID 151 acquired in step S1004. 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, a mail is generated with the message content 142 corresponding to the delay condition specified as satisfied as the mail text (step S1005).

  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 S1003 is reached (step S1006). 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 to the terminal of the destination renter as appropriate via the communication unit 101 (step S1007).

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

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

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

  FIG. 11B 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 exceeds “50 times”. The display example of dunning mail is shown.

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

<Summary>
As shown in the above embodiment, the debt management device 100 can automatically send an email requesting a call to a lessee who has failed to pay the consideration. The processing burden on the operator can be reduced. In addition, the debt management device 100 is configured to identify a partner to which a dunning mail should be transmitted, and automatically allocate and send it to each time slot, so that a call from a lessee is made according to the dunning mail. The time for receiving can be distributed as much as possible. Therefore, it is possible to avoid as much as possible the situation where the lessee makes a call in response to the reminder mail but the telephones are concentrated and cannot answer some of the telephones.

<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, it can be estimated from the date and time information that the time zone in which the lessee makes a call is included in the 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. For example, when the time zone in which there were many telephone responses was between 17:00 and 18:00, the reminder mail for the lessee is transmitted in the time zone from 14:00 to 15:00.

(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 failed to pay the rent. 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. 5 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.

(1-4) Other methods As a method for determining the time zone for sending other dunning emails, for example, for the first time the lessee who has failed to pay the consideration, each time zone is distributed to each time zone. It is good also as assigning to. Tenants who have paid for the first time often tend to respond quickly to calls. Therefore, when a dunning mail is sent, it means that there is a high possibility that a call from the lessee will come in near time. Therefore, in order to distribute the lessees who have failed to pay the consideration, the time period for transmitting the reminder mail is determined so that the time periods for transmitting the reminder mail to the lessee are distributed.

  (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 dunning mail that is accurately matched to the lessee, the possibility that the lessee will make a call 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 timing of sending the telephone reminder email may be determined appropriately by the operator of the debt management device 100. For example, at the stage of delinquent rent 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) The guarantee business described above is an aspect related to a guarantee contract related to a lease contract, and the contents of the contract are 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.

  (10) In the above embodiment, as an example of the time zone for transmitting the reminder mail, 10:00 to 11:00, 11:00 to 12:00, 12:00 to 13:00, 13:00 to 14:00, 14:00 to 15:00 The example which provides the time slot | zone of was demonstrated. This is an example of distributing a time zone for sending a reminder mail to be sent by 15:00 (time limit). That is, an example is shown in which the reminder mail to be transmitted is distributed to each time zone. However, it is needless to say that the distribution of the time zone for sending the reminder mail is not limited to this. For example, the time zone (period zone) may be set as follows.

  For example, at a certain point in the month, there are X reminder emails to be sent during the month (due date) (it can be said that there are X uncollected claims), and the remaining weekdays of the month are Y Suppose there was a day. In this case, in order to ensure Y days, X / Y reminding mails are sent on the 1st, and the X / Y reminding mails to be sent on the 1st are as shown in the above embodiment. It is good also as distributing and transmitting to each time slot | zone.

  At this time, in the above-described embodiment, the number of dunning mails to be transmitted is determined to be as uniform as possible in each time zone in which the dunning mail is transmitted, but this is not limited thereto. Under the following conditions, the number of reminder mails to be transmitted in each time zone may be transmitted unevenly.

  For example, it may be allocated based on a shift of a telephone operator who receives a call made by a lessee with respect to a reminder mail on the debt management side. For example, a operator at 10 o'clock to 11 o'clock, b operator at 11 o'clock to 12 o'clock, c operator at 12 o'clock to 13 o'clock, d operator at 13 o'clock to 14 o'clock, 1 o'clock to 15 o'clock , E operators are waiting. It is assumed that there are X reminder mails to be sent. In this case, the reminder mail transmitted between 10:00 and 11:00 may be (a × X) / (a + b + c + d + e). In other words, the value obtained by dividing the number of general emails to be sent by the total number of operators waiting in each time zone and the number of operators waiting in that time zone is sent in that time zone. It is good also as the number of reminding mails which should be done.

  Alternatively, as shown in the supplement (1) above, the transmission time may be allocated based on the information on the lessee, and as a result of the allocation, the number of reminder emails to be transmitted in each time slot is inadequate. It may be even.

  (11) Although not shown in the above embodiment, the lessee may be able to pay only a part of the consideration to be paid by the deadline. In such a case, the total number of delays and the number of unpaid payments are numerical values corresponding to the proportion paid (for example, if paying 30%, the amount of delay corresponding to the remaining 70% 0.7) may be added, or even if only a part is paid, it is not changed to paying the full amount, and 1 may be added.

  (12) 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. 12, 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 function 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, and the debt management program and various data are 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. Then, the object of the present invention is achieved by the computer (or CPU) reading the debt management program from the recording medium and executing it. 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. .

  (13) 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 modifications and corrections 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. .

  (14) The configuration shown in the above embodiment and the configuration shown in the reference example may be appropriately combined.

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

Claims (3)

A debt management device capable of transmitting a message including contents for requesting a call to each of the plurality of debtors when there are a plurality of debtors who have delayed the performance of the debts,
The total number of people who can respond to the call is divided by the total number of messages to be transmitted in a plurality of time zones, and the call is handled in each time zone of the plurality of time zones. A value obtained by multiplying the number of people that can be calculated as the number of messages to be transmitted in each time zone, and an assigning unit that assigns a timing for transmitting the message based on at least the calculated number of messages;
A transmission unit for transmitting the message at a timing allocated by the allocation unit;
A debt management device comprising: A debt management device capable of transmitting a message including contents for requesting a call to each of the plurality of debtors when there are a plurality of debtors who have delayed the performance of the debts,
Based on the total number of messages to be transmitted in a plurality of time zones and the number of persons who can respond to the call in each of the plurality of time zones , the number of messages to be transmitted in each time zone is calculated. And an assigning unit that assigns a timing for transmitting the message based on at least the calculated number of messages;
A transmission unit for transmitting the message at a timing allocated by the allocation unit;
A debt management device comprising: A debt management method capable of transmitting a message requesting a call to each of the plurality of debtors when there are a plurality of debtors who have delayed the performance of the debts,
Computer
Based on the total number of messages to be transmitted in a plurality of time zones and the number of persons who can respond to the call in each of the plurality of time zones , the number of messages to be transmitted in each time zone is calculated. And
Assigning a timing for transmitting the message based on at least the calculated number of messages;
Sending the message at the assigned timing;
Debt management method.

Images