Business support device, business support method, and business support program

Abstract

This system assists with setting the next repayment date for loan products, thereby reducing the workload of the person in charge. [Solution] A business support device that assists in setting the next scheduled repayment date in loan operations, where the repayment period of a loan made to a customer is divided into multiple installments, and the repayment amount corresponding to the installment period is collected from the customer by the due date belonging to each installment period, wherein the decision unit determines whether or not to update the scheduled repayment date to the scheduled repayment date of the next installment period based on predetermined decision criterion information included in the customer's loan data. If the calculation unit obtains a decision result to update the scheduled repayment date, it calculates the due date belonging to the period obtained by adding a predetermined period to the current scheduled repayment date as the next scheduled repayment date. The update processing unit updates the next scheduled repayment date included in the customer's transaction data to the date of the calculated due date.

Description

Technical Field

[0006] , , ,

[0005] , , ,

[0007] , , ,

[0001] The present invention relates to a business support device, a business support method, and a business support program.

Background Art

[0002] Patent Document 1 (Japanese Patent Application Laid-Open No. 2024-159107) discloses a server aiming to improve convenience regarding repayment of loaned amounts.

[0003] In paragraphs 0241, 0261 to 0263 of this Patent Document 1, it is described that a reminder notice is sent by repayment agreement update processing based on the user not making repayment on the agreed repayment date.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Here, in the financing business, the occurrence state of delinquency is recognized by comparing the current date with the next scheduled repayment date. Since it affects the collection of late payment damages, the setting of the next scheduled repayment date is very important from the viewpoints of profitability and business continuity (compliance with laws).

[0006] The present invention has been made in view of the above problems, and an object thereof is to provide a business support device, a business support method, and a business support program for supporting the setting operation of the next scheduled repayment date.

Means for Solving the Problems

[0007] ​To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention is a business support device that assists in setting the next scheduled repayment date in loan operations, in which the repayment amount of the loan corresponding to the installment period is collected from the customer by the agreed date belonging to each installment period, which is divided into multiple installments, and the business support device assists in setting the next scheduled repayment date in loan operations, and comprises: a determination unit that determines whether or not to update the scheduled repayment date to the scheduled repayment date of the next installment period based on predetermined judgment criterion information included in the customer's loan data; a calculation unit that, if a determination result for updating the scheduled repayment date is obtained, calculates the agreed date belonging to the period obtained by adding a predetermined period to the current scheduled repayment date as the next scheduled repayment date; and an update processing unit that updates the next scheduled repayment date included in the customer's transaction data to the date of the calculated agreed date.

[0008] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the business support method according to the present invention is a business support method for a business support device that supports the setting of the next scheduled repayment date in a loan business in which the repayment amount of the loan corresponding to the installment period is collected from the customer by the agreed date belonging to each installment period, which is divided into multiple installments, and the method comprises: a determination step in which a determination unit determines whether or not to update the scheduled repayment date to the scheduled repayment date of the next installment period based on predetermined determination criterion information included in the customer's loan data; a calculation step in which, if a determination result for updating the scheduled repayment date is obtained, the agreed date belonging to the period obtained by adding a predetermined period to the current scheduled repayment date is calculated as the next scheduled repayment date; and an update processing step in which an update processing unit updates the next scheduled repayment date included in the customer's transaction data to the calculated agreed date.

[0009] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support program according to the present invention provides a computer for a business support device that assists in setting the next scheduled repayment date in loan operations, where the repayment amount of the loan corresponding to the installment period is collected from the customer by the agreed date belonging to each installment period, which is divided into multiple installment periods for which the repayment period of the loan loan made to the customer has been divided. This computer is configured to function as a determination unit that determines whether or not to update the scheduled repayment date to the scheduled repayment date of the next installment period based on predetermined judgment criterion information included in the customer's loan data; a calculation unit that, if a determination result for updating the scheduled repayment date is obtained, calculates the agreed date belonging to the period obtained by adding a predetermined period to the current scheduled repayment date as the next scheduled repayment date; and an update processing unit that updates the next scheduled repayment date included in the customer's transaction data to the date of the calculated agreed date. [Effects of the Invention]

[0010] This invention can reduce the workload of the person in charge by assisting with the task of setting the next repayment date. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a block diagram showing the hardware configuration of the business support device according to the embodiment. [Figure 2] Figure 2 shows an example of a repayment pattern master table. [Figure 3] Figure 3 shows an example of the data format of loan data. [Figure 4] Figure 4 shows an example of the data format of transaction data. [Figure 5] Figure 5 is a schematic diagram showing an overview of the update operation for the next repayment due date, which is performed, for example, when a payment is received, by the business support device of the embodiment. [Figure 6] Figure 6 shows an example of a contract input screen where the details of a contract with a customer are entered. [Figure 7] Figure 7 shows an example of loan data generated based on the input on the contract input screen. [Figure 8]Figure 8 shows an example of transaction data generated based on the input on the contract input screen. [Figure 9] Figure 9 shows an example of transaction data generated when a customer makes their first deposit. [Figure 10] Figure 10 shows transaction data with the next repayment due date updated. [Modes for carrying out the invention]

[0012] The following describes in detail, based on the drawings, an example of applying the present invention to a terminal device of a lending company that lends money to customers through a predetermined loan product and collects repayments from customers at predetermined intervals, such as monthly, as an embodiment of the business support device. However, the present invention is not limited to the following embodiments.

[0013] (overview) In lending operations, a default is determined by comparing today's date with the next scheduled repayment date. For example, if today's date is less than today's date, a default is considered to have occurred. Conversely, if today's date is greater than or equal to today's date, no default is considered to have occurred. Setting the next scheduled repayment date is extremely important from the perspective of profitability and business continuity (legal compliance), as it affects the collection of late payment penalties.

[0014] In the process of setting the next repayment date, it is necessary to individually check whether it is acceptable to update the next repayment date when a payment is received from the customer, and if it is acceptable to update the next repayment date, then that new repayment date must be determined. If it is mistakenly determined that the customer is in arrears state at this time, it will result in the inconvenience of setting an incorrect date as the next repayment date.

[0015] Here, the method for determining the next repayment due date can be determined by the characteristics of the loan product. Therefore, by setting the criteria for determining the next repayment due date for each product type, and determining (whether to update or not; if updating, setting it automatically) the next repayment due date when a payment is received from the customer, the workload of the person in charge can be reduced.

[0016] In the business support device according to the embodiment, reference information for automatically determining the next repayment scheduled date is master-managed, and for the contract data of a customer, reference information corresponding to the product characteristics of the loan product is set. When a repayment is received from a customer, based on the reference information set for that customer, it is automatically determined whether to update the next repayment scheduled date according to the repayment amount and the repayment timing. Then, based on this determination result, the next repayment scheduled date is updated or not updated.

[0017] To achieve such a thing, the business support device according to the embodiment master-manages the automatic determination settings of the next repayment scheduled date for each product characteristic (repayment pattern) of the loan product.

[0018] For the reference information for determining whether to update the next repayment scheduled date, any one (or multiple) of the following three is selected and set.

[0019] 1. Determine by repayment amount (if it is greater than or equal to the threshold value, calculate and set the next repayment scheduled date. 2. Shortage amount conversion days method (determine according to the actual repayment timing). 3. Unconditionally proceed as long as there is a deposit (calculate the next repayment scheduled date if there is a deposit).

[0020] For example, in a normal financing business, the reference information of "1" is selected. On the other hand, for loan products for students or loan products that handle a large number of non-performing loans, since the recovery rate is low and the burden of collection work is imposed, the reference information of the "2" shortage amount conversion days method is selected, or the reference information of the "3" unconditional deposit is selected.

[0021] That is, in the business support device according to the embodiment, when there is an application for financing from a customer and the contract content is registered, the repayment pattern master table (see FIG. 2) is referred to, and the desired settings (reference information) are reflected in the contract and held in the contract data.

[0022] When a customer (debtor) makes a repayment, the system automatically determines whether or not to update the next repayment due date based on the judgment criteria information stored in the customer's contract data, as described below.

[0023] For example, in the case of a customer whose monthly repayment is 30,000 yen and whose judgment criterion is set to "1", if a repayment amount of 30,000 yen or more is deposited, the next repayment due date will be updated to advance by one month. On the other hand, if the deposited repayment amount is less than 30,000 yen, the next repayment due date will not be advanced. In this case, since the next repayment due date is not updated, it will be judged as delinquent once the date has passed the current repayment due date.

[0024] (Hardware configuration) As shown in Figure 1, the business support device 1 of this embodiment, which is a terminal device for a lending company, comprises a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5.

[0025] Output device 7 may include a display unit of a monitor device (including a home television), a printing device, or a speaker device. Input device 6 may include a keyboard device, a mouse device, a microphone device, or a monitor device that works in conjunction with a mouse device to provide a pointing device function.

[0026] The communication interface unit 4 is connected to a network 50, such as a wide-area network like the Internet or a private network like a LAN (Local Area Network). The customer terminal device 51 and the bank terminal device 52 of the bank where the customer's account is opened are connected to this network 50.

[0027] The customer accesses the business support device 1 via the customer terminal device 51 to contract for the desired loan product and borrow the desired amount of money. The customer also accesses the bank terminal device 52 via the customer terminal device 51 to make monthly repayments to the lending company (performs a deposit operation to the lending company).

[0028] For the memory unit 2, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used.

[0029] Memory Unit 2 stores a business support program that assists in setting the next repayment date, thereby reducing the workload of the person in charge.

[0030] Furthermore, this memory unit 2 is equipped with a repayment pattern master table 11, a loan data storage unit 12, and a transaction data storage unit 13, which are memory areas.

[0031] The repayment pattern master table 11 stores various criteria information for determining whether or not to update the next repayment due date. Specifically, as shown in Figure 2, the repayment pattern master table 11 stores the repayment pattern code, repayment method name, next repayment date determination category, and next repayment date determination number of days, each associated with the other, as judgment criterion information.

[0032] The example in Figure 2 shows that the repayment method name "Equal Principal and Interest Payments, No Planned Repayments" and the next repayment date determination category "1: Monthly Repayment Amount" have been added to the judgment criteria information for the repayment pattern code "HPC-1". The example in Figure 2 also shows that the repayment method name "Equal Principal and Interest Payments, No Planned Repayments, Shortfall Calculation", the next repayment date determination category "2: Number of Days for Shortfall Calculation", and the next repayment date determination number of days "5 days" have been added to the judgment criteria information for the repayment pattern code "HPC-2". Furthermore, the example in Figure 2 shows that the repayment method name "Equal Principal and Interest Payments, No Planned Repayments, Unconditional" and the next repayment date determination category "3: Unconditional Payment" have been added to the judgment criteria information for the repayment pattern code "HPC-3".

[0033] The "1: Monthly Repayment Amount" next repayment date determination category indicates that the criteria information for that repayment pattern is that if the deposit amount ≥ the monthly repayment amount, the next repayment date will be updated. The "2: Number of Days Equivalent to a Shortfall" next repayment date determination category indicates that the criteria information for that repayment pattern is that the number of days equivalent to a shortfall is subtracted from the number of days for determining the next repayment date to determine whether or not to update the next scheduled repayment date. The "3: Unconditional Deposit" next repayment date determination category indicates that the criteria information for that repayment pattern is that if even 1 yen is deposited, the next scheduled repayment date will be updated.

[0034] The "next repayment date determination period" is the number of days used to calculate the determination period, which is compared with the number of days from the payment date to the most recent scheduled repayment date (contract date) when the determination criteria information for the repayment pattern code of "HPC-2" is selected. More details will be provided later.

[0035] "Equal principal and interest payments" refers to a repayment method where the total amount of principal and interest is equal throughout the repayment period (equal principal and interest payment method or equal principal and interest repayment method).

[0036] The loan data storage unit 12 stores loan data, including contract information for customers who have contracted for loan products. This loan data includes the contract number, the product code of the loan product, the repayment pattern code of the judgment criteria information set for that customer, the next repayment date judgment category, the number of days for the next repayment date judgment, the monthly repayment amount, the loan interest rate, and the contract date.

[0037] The settlement date can be set to any desired date, such as the 25th of each month.

[0038] The transaction data storage unit 13 stores transaction data corresponding to the payment history with the customer. This transaction data includes the same contract number as the contract number assigned to the loan data (the customer's unique contract number), the next scheduled repayment date, the loan balance, the payment date, and the payment amount. Of these, the loan balance is the amount obtained by subtracting the current payment amount from the previous loan balance. The business support device 1 of this embodiment determines whether or not to update the next scheduled repayment date based on the judgment criteria information. If it is determined that the next scheduled repayment date should be updated, the next scheduled repayment date in this transaction data is updated.

[0039] Please note that if it is decided not to update the next repayment due date, this transaction data will not be updated. Therefore, if the next repayment due date passes without the payment date being updated, it will be considered a default.

[0040] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the memory unit 2, and functions as a determination unit 21, calculation unit 22, update processing unit 23, output control unit 24, communication control unit 25, and data generation unit 26, as shown in Figure 1.

[0041] In this example, the decision unit 21 to the data generation unit 26 are described as being implemented in software based on the business support program, but all or part of the decision unit 21 to the data generation unit 26 may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0042] The communication control unit 25 controls communication with the customer terminal device 51 and accepts applications and contracts for loan products. The communication control unit 25 also controls communication with the bank terminal device 52 and processes deposit requests from customers.

[0043] The business support device 1 of this embodiment is a business support device that assists in setting the next scheduled repayment date in loan operations, where the repayment period of a loan made to a customer is divided into multiple installments, and the repayment amount corresponding to the installment period is collected from the customer by the agreed date for each installment period.

[0044] The decision unit 21 determines whether or not to update the repayment due date to the repayment due date of the next installment period, based on predetermined decision criteria information (repayment pattern in Figure 2) included in the customer's loan data.

[0045] If the calculation unit 22 obtains a decision from the decision unit 21 to update the repayment due date, it calculates the next repayment due date as the due date that falls within the period obtained by adding a predetermined period to the current repayment due date.

[0046] The update processing unit 23 updates the next scheduled repayment date included in the customer's transaction data (see Figure 4) to the calculated settlement date (= settlement date of the next month).

[0047] Customer loan data includes: The first decision criterion information (repayment pattern of HPC-1 in Figure 2) is to update the repayment due date if the amount received from the customer is equal to or greater than the repayment amount, and not update the repayment due date if the amount received from the customer is less than the repayment amount. A second set of criteria information (repayment pattern of HPC-2 in Figure 2) is used to determine whether the repayment date will be updated if the number of days from the payment date to the most recent scheduled repayment date is less than or equal to a predetermined number of days, and whether the repayment date will not be updated if the number of days from the payment date to the most recent scheduled repayment date exceeds a predetermined number of days, and A third set of criteria information (repayment pattern for HPC-3 in Figure 2) that updates the repayment due date if payment is received by the due date, and does not update the repayment due date if payment is not received by the due date. One of the following criteria information is added (see Figure 3).

[0048] The decision unit 21 determines whether or not to update the repayment due date based on the decision criteria information (one of the repayment patterns from HPC-1 to HPC-3) attached to the customer's loan data.

[0049] For example, if a second set of judgment criteria information is added to the customer's loan data, the judgment unit 21 will determine whether or not to update the next repayment due date as follows.

[0050] In other words, the determination unit 21 calculates the "number of days to convert to a deficit" by multiplying the deficit amount by 365 days (the number of days in a year) and then dividing the result by multiplying the loan interest rate to the customer by the loan balance immediately before the current deposit.

[0051] Next, the determination unit 21 calculates the "determination period" by subtracting the number of days for calculating the shortfall from the number of days for determining the next scheduled repayment date, which is pre-set in the repayment pattern master table 11.

[0052] The determination unit 21 then determines to update the repayment due date if the number of days between the payment date and the most recent repayment due date is less than or equal to the determination number of days. Based on this determination, the update processing unit 23 updates the next repayment due date in the transaction data shown in Figure 4.

[0053] Furthermore, the judgment unit 21 determines not to update the repayment due date if the number of days between the payment date and the most recent repayment due date exceeds the judgment period. In this case, the next repayment due date in the transaction data is not updated. As a result, once the next repayment due date, which has not been updated, has passed since the payment date, the person in charge will determine that the payment is overdue.

[0054] (Update action for the next repayment due date) Figure 5 is a schematic diagram showing an overview of the update operation for the next repayment due date, which is performed, for example, when a payment is made, by the business support device 1 of the embodiment. As shown in Figure 5, the repayment pattern master table 11 registers the next repayment date determination category and the number of days for determining the next repayment date, corresponding to various repayment patterns (HPC-1 to HPC-3), as explained using Figure 2.

[0055] When a customer requests a loan (application), the person in charge specifies the display of the contract input screen via the input device 6. The output control unit 24 then displays the contract input screen shown in Figure 6 via the output device 7. On this contract input screen shown in Figure 6, the person in charge inputs contract details such as the contract number, loan product code, repayment pattern code, monthly repayment amount, next repayment date, loan balance, loan interest rate, and due date.

[0056] Figure 6 shows an example where the contract number "KY-0" is automatically assigned by the control unit 3, and a loan product with product code "S-1" is contracted with the customer. Figure 6 also shows an example where the judgment criterion information for the repayment pattern code "HPC-2" is set based on the repayment pattern master table 11 shown in Figure 2.

[0057] Figure 6 also shows an example where the current loan balance is "100,000 yen (initial loan amount)," the monthly repayment amount is set to "5,000 yen," and the next scheduled repayment date is set to "November 25, 2024." Furthermore, Figure 6 shows an example where the loan interest rate is set to "5% per annum," and the contract date (monthly repayment date) is set to "the 25th of each month."

[0058] Once the contract details are entered and the person in charge presses the execute button, the data generation unit 26 generates loan data as exemplified in Figure 7 based on the contract details entered via the contract input screen and stores it in the loan data storage unit 12.

[0059] The loan data shown in Figure 7 includes the contract number, product code, and repayment pattern code corresponding to the contract details described above. In this example, the repayment pattern is set to "HPC-2" as the decision criterion information. Therefore, as shown in Figure 2, the loan data is generated to include the "5 days" next repayment date determination period set for this "HPC-2" repayment pattern.

[0060] The monthly repayment amount, loan interest rate, and due date are set at "5,000 yen," "5%," and "25th of the month," respectively, based on the contract details mentioned above.

[0061] Furthermore, once the contract details are entered and the execution button is pressed by the person in charge, the data generation unit 26 generates the initial transaction data, as illustrated in Figure 8, and stores it in the transaction data storage unit 13. This example in Figure 8 represents transaction data for a situation where there are still several days until the next scheduled repayment date of November 25, 2024, which is the first repayment date, and no payment has been received from the customer. Therefore, the loan balance is "100,000 yen," which is the loan amount.

[0062] Next, as shown in Figure 5, the customer makes the payment by the next scheduled payment date. Let's assume that the contract stipulated a monthly payment of 5,000 yen, and on November 23, 2024, two days before the scheduled payment date of November 25, 2024, the customer made a payment of "4,970 yen". Based on the input by the person in charge, the data generation unit 26 generates transaction data as shown in Figure 9, with the payment date set to November 23, 2024, and the payment amount set to "4,970 yen," and this data is stored in the transaction data storage unit 13.

[0063] (How the HPC-2 repayment pattern works) When transaction data corresponding to a deposit is generated, the determination unit 21 refers to the customer's loan data (see Figure 7) and detects the repayment pattern set for that customer. In this example, as shown in Figure 9, the customer's repayment pattern is set to the "HPC-2" repayment pattern, which determines whether or not to update the next scheduled deposit date based on the number of days for which the deficit is calculated. If it is determined that the "HPC-2" repayment pattern is set, the calculation unit 22 performs the following calculation to calculate the number of days from the deposit date to the next scheduled deposit date (contract date).

[0064] Number of days until the most recent settlement date = Settlement date of loan data - Payment date = November 25th - November 23rd = 2 days

[0065] Next, the calculation unit 22 calculates the deficit amount resulting from this deposit by performing the following calculations.

[0066] Shortfall = Monthly repayment amount from loan data - Amount received this time = 5,000 yen - 4,970 yen = 30 yen

[0067] Next, the calculation unit 22 calculates the number of days equivalent to the deficit by performing the following calculation.

[0068] Number of days to calculate the deficit = (Amount of deficit × Number of days in a year) ÷ (Loan balance in transaction data × Loan interest rate in lending data) = (30 yen × 365 days) ÷ (100,000 yen × 5%) = 2 days

[0069] Next, the calculation unit 22 refers to the repayment pattern master table 11 shown in Figure 2 and detects the number of days for determining the next repayment date set for the "HPC-2" repayment pattern. In this example, "5 days" is set as the number of days for determining the next repayment date. The calculation unit 22 calculates the number of days for determining the next repayment date by performing the following calculation based on the number of days for calculating the deficit and the number of days for determining the next repayment date.

[0070] Decision period = Number of days for determining the next repayment date in repayment pattern master table 11 - Number of days for calculating the deficit = 5 days - 2 days = 3 days

[0071] Once the number of days for judgment is calculated in this way, the update processing unit 23 will not update the next repayment due date if "number of days until the most recent contract date (repayment due date) > number of days for judgment". If "number of days until the most recent contract date (repayment due date) ≤ number of days for judgment", it will execute the update process for the next repayment due date.

[0072] Here, Figure 10(a) shows the transaction data before the next repayment due date was updated, and Figure 10(b) shows the transaction data after the next repayment due date was updated. In the example above, "the number of days until the most recent contract date (repayment due date) is 2 days ≤ the number of days for judgment is 3 days." Therefore, the calculation unit 22 calculates the month to which the next repayment due date belongs by performing the following calculation.

[0073] The month in which the next repayment due date falls = Next repayment due date in the transaction data + 1 month = November 25, 2024 + 1 month = December 2024

[0074] The calculation unit 22 then calculates the contract date belonging to the calculated month (the 25th in this example) as the next scheduled repayment date (next scheduled repayment date = December 25, 2024).

[0075] Based on the calculation results of the calculation unit 22, the update processing unit 23 updates the next scheduled repayment date in the transaction data from "November 25, 2024" to "December 25, 2024," which is the contract date of the following month, as shown in Figure 10(b). As a result, the customer's payment deadline is reset to the contract date of the following month.

[0076] Furthermore, if "number of days until the most recent due date (scheduled repayment date) > number of days for judgment," the update processing unit 23 will not update the next scheduled repayment date. Therefore, the person in charge will determine that the payment is overdue once the current date has passed the scheduled repayment date.

[0077] (How the HPC-1 repayment pattern works) Next, for example, when transaction data corresponding to a deposit is generated, the determination unit 21 determines that the repayment pattern set for that customer is "HPC-1".

[0078] In this case, the update processing unit 23 updates the next repayment date if "deposit amount ≥ monthly repayment amount". However, if "deposit amount < monthly repayment amount", the next repayment date is not updated.

[0079] For example, if the "monthly repayment amount" is 5,000 yen, but the "amount paid" is 4,970 yen, then "amount paid < monthly repayment amount," and the update processing unit 23 does not update the next repayment date (the next scheduled repayment date in the transaction data remains November 25th). The determination of whether a default has occurred is made by comparing today's date with the next scheduled repayment date. Therefore, this debt will be determined to be in default when November 26th arrives.

[0080] (How the HPC-3 repayment pattern works) Next, for example, when transaction data corresponding to a deposit is generated, the determination unit 21 determines that the repayment pattern set for that customer is the "HPC-3" repayment pattern.

[0081] The repayment pattern for "HPC-3" is one in which the next repayment date is updated whenever even 1 yen is deposited. Therefore, the update processing unit 23 updates the next scheduled repayment date in the transaction data from "November 25, 2024" to "December 25, 2024," which is the contract date of the following month, at the time the transaction data is generated. As a result, the customer's payment deadline is reset to the contract date of the following month.

[0082] (Data output format) The output control unit 24 reads the loan data generated in this manner from the loan data storage unit 12 and the transaction data from the transaction data storage unit 13 at the timing specified by the person in charge, and outputs them via the output device 7.

[0083] For example, the output device 7 can be a display device, a printing device, or a speaker device. The output control unit 24 converts transaction data, etc., into display information, print information, or audio information and supplies it to the corresponding device. This makes it possible to obtain display output, print output, or audio output of transaction data, etc. Alternatively, the output device 7 may be the storage unit 2 or an external storage device. Furthermore, the communication control unit 25 may output transaction data, etc., to a server device on the network 50 for storage.

[0084] (Effects of the embodiment) As is clear from the above description, the business support device 1 of the embodiment can accurately determine and set the next repayment date regardless of the level of the person in charge, by setting judgment criterion information corresponding to the product characteristics (repayment pattern) of the loan product for each customer.

[0085] Furthermore, since the determination of the next repayment due date can be done automatically, it prevents errors by staff in determining whether or not a payment is overdue.

[0086] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving operational efficiency and promoting appropriate management decisions by companies, and therefore can contribute to SDGs Goals 8 and 9.

[0087] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0088] Furthermore, this invention can contribute to strengthening control and governance, and therefore can contribute to achieving the 16 goals of the SDGs.

[0089] [Other embodiments] The present invention can be implemented in various different forms within the scope of the technical idea described in the claims, even in embodiments other than those described above.

[0090] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually. Alternatively, all or part of the processes described as being performed manually may be performed automatically by known methods or the like.

[0091] Furthermore, unless otherwise specified, the processing procedures, control procedures, specific names, registration data for each process, information including parameters such as search conditions, screen examples, and database configuration shown in the specification or drawings can be arbitrarily changed.

[0092] Furthermore, with respect to the business support device 1, each component shown in the diagram is a functional concept and does not necessarily have to have the physical configuration shown. For example, the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be implemented in whole or in any part by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or by hardware using wired logic.

[0093] The program is recorded on a non-temporary, computer-readable recording medium containing programmed instructions for the information processing device to execute the processes described in the embodiment, and is mechanically read by the business support device 1 as needed. In other words, the storage unit 2, such as ROM or HDD, records a computer program that works in cooperation with the OS (Operating System) to give instructions to the control unit 3 (CPU) and perform various processes. This computer program is loaded into RAM, unpacked, and executed by the control unit 3 as appropriate.

[0094] Furthermore, the business support program for this business support device 1 may be stored on another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0095] Furthermore, the business support program for executing the processes described in the embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product.

[0096] Here, any "portable physical medium" can be used as the "recording medium," such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical Disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0097] Furthermore, "program" refers to a data processing method written in any language or writing method, regardless of whether it is source code or binary code.

[0098] Furthermore, the term "program" is not necessarily limited to a single, monolithic entity, but also includes those that are distributed as multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions.

[0099] Furthermore, for the specific configuration, reading procedure, and post-reading installation procedure for the business support device 1 of the embodiment, well-known configurations or procedures can be used.

[0100] The storage unit 2 is a storage means such as memory devices like RAM and ROM, fixed disk devices like hard disks, flexible disks, and optical disks, and stores various programs, tables, databases, and web page files used for various processing or website provision.

[0101] Furthermore, the business support device 1 may be composed of a known personal computer device or an information processing device such as a workstation, or it may be composed of an information processing device to which any peripheral devices are connected. In addition, the information processing device may be implemented by implementing software (including programs or data, etc.) that realizes the processing described in the embodiment.

[0102] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing or integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above can be selectively implemented by arbitrarily combining the embodiments described above. [Industrial applicability]

[0103] This invention is particularly suitable for application in the financial industry to the process of setting the next repayment date for loan products. [Explanation of symbols]

[0104] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input devices 7 Output device 11. Repayment Pattern Master Table 12 Loan data storage unit 13 Transaction data storage unit 21 Judgment Department 22 Calculation Section 23 Update Processing Unit 24 Output Control Unit 25 Communication Control Unit

Claims

1. A business support device that assists in setting the next scheduled repayment date in loan operations, which involves collecting the repayment amount of the loan corresponding to each installment period, which is to be paid by the customer by the agreed date for each installment period, when the repayment period of a loan made to a customer is divided into multiple installments, A determination unit that determines whether or not to update the repayment due date to the repayment due date of the next installment period based on predetermined judgment criteria information included in the customer's loan data, If a decision is made to update the repayment due date, the calculation unit calculates the next repayment due date as the date of the agreement that falls within the period obtained by adding a predetermined period to the current repayment due date. An update processing unit that updates the next scheduled repayment date included in the customer's transaction data to the calculated date of the agreement, A business support device having the following features.

2. The loan data of the aforementioned customer includes: A first set of criteria information which updates the repayment due date if the amount received from the customer is equal to or greater than the repayment amount, and does not update the repayment due date if the amount received from the customer is less than the repayment amount. A second set of criteria information for determining whether to update the repayment due date if the deposit amount is less than the aforementioned repayment amount, and if the number of days from the deposit date to the most recent aforementioned repayment due date is less than or equal to a predetermined number of days, and if the number of days from the deposit date to the most recent aforementioned repayment due date exceeds a predetermined number of days, and, A third set of criteria information that updates the repayment due date if payment is made by the aforementioned repayment due date, and does not update the repayment due date if payment is not made by the aforementioned repayment due date. One of the following criteria information is added: The determination unit makes a determination whether or not to update the repayment due date based on the determination criteria information attached to the customer's loan data. The business support device according to claim 1, characterized by the following:

3. If the second judgment criterion information is added to the loan data of the customer, the judgment unit will The number of days equivalent to the deficit is calculated by multiplying the deficit amount by 365 days and then dividing the result by the product of the loan interest rate to the customer and the loan balance immediately prior to the current deposit. The number of days for determining the next scheduled repayment date is calculated by subtracting the number of days for calculating the deficit from the number of days for determining the next scheduled repayment date that is pre-set in the repayment pattern master table. If the number of days from the payment date to the most recent repayment due date is less than or equal to the number of days used for the determination, the decision will be made to update the repayment due date; if the number of days from the payment date to the most recent repayment due date exceeds the number of days used for the determination, the decision will be made not to update the repayment due date. The business support device according to claim 2, characterized by the following:

4. A business support method for a business support device that assists in setting the next scheduled repayment date in a loan business, which involves collecting the repayment amount of the loan corresponding to each installment period, which is to be paid by the customer by the agreed date for each installment period, when the repayment period of a loan made to a customer is divided into multiple installments, A decision step in which the decision unit determines whether or not to update the repayment due date to the repayment due date of the next installment period based on predetermined decision criterion information included in the customer's loan data, If the calculation unit determines that the repayment due date should be updated, the calculation step involves calculating the next repayment due date as the date of the agreement that falls within the period obtained by adding a predetermined period to the current repayment due date. The update processing unit performs an update processing step in which it updates the next scheduled repayment date included in the customer's transaction data to the calculated date of the agreement date, A business support method that has the following characteristics.

5. A computer in a business support device that assists in setting the next scheduled repayment date in loan operations, where the repayment period of a loan made to a customer is divided into multiple installments, and the repayment amount corresponding to the installment period is collected from the customer by the agreed date for each installment period. A determination unit that determines whether or not to update the repayment due date to the repayment due date of the next installment period based on predetermined judgment criteria information included in the customer's loan data, If a decision is made to update the repayment due date, the calculation unit calculates the next repayment due date as the date of the agreement that falls within the period obtained by adding a predetermined period to the current repayment due date. An update processing unit updates the next scheduled repayment date included in the customer's transaction data to the calculated date of the agreement. A business support program designed to function as such.

Images