JP7750818B2 - Loan management device, loan management method, and loan management program - Google Patents

Description

The present invention relates to a loan management device, a loan management method, and a loan management program.

Patent Document 1 discloses a configuration that simulates the repayment of a relatively long-term, large-value loan, such as a home loan or car loan, in which the remaining loan amount at a given point in time is repaid in full.

Japanese Patent Application Laid-Open No. 2017-188111

However, the invention described in Patent Document 1 above is unable to perform a calculation simulation by switching between the interest amount and full repayment amount on the desired full repayment date, taking into account whether or not repayment will occur on the deduction dates between now and the desired full repayment date. This means that the debtor's financial planning cannot be accurately planned, which could lead to late payments or bad debts.

The present invention was made in consideration of the above-mentioned problems, and aims to provide a loan management device, loan management method, and loan management program that can simulate the calculation of the full repayment amount on the desired full repayment date for a specified small loan, taking into account whether or not there will be any scheduled repayments on the scheduled repayment dates up to the desired full repayment date.

In order to solve the above-mentioned problems and achieve the objectives, the loan management device of the present invention is a loan management device equipped with a memory unit and a control unit, wherein the memory unit comprises: a contract storage means for storing contract data that sets the loan amount, loan interest rate, and agreed repayment date of a small loan; and a log storage means for storing log data that links transaction dates including the agreed repayment date and the loan balance; and the control unit comprises: a request acquisition means for acquiring a simulation request that sets the full repayment date and whether or not repayment will be made on the agreed repayment dates up to the full repayment date; and a simulation means for calculating the simulated full repayment amount of the small loan on the full repayment date based on the contract data, the log data, and the simulation request.

In the loan management device of the present invention, the control unit further includes a billing acquisition means for acquiring final billing data that sets the billing amounts for the scheduled repayment dates up to the full repayment date, and the simulation means, based on the final billing data, the contract data, the log data, and the simulation request, calculates the interest appropriation amount for the scheduled repayment date if there is a repayment on the scheduled repayment date up to the full repayment date, calculates the new loan balance by subtracting the billing amount from the sum of the loan balance and the interest appropriation amount, acquires the loan balance on the scheduled repayment date immediately before the full repayment date as the principal repayment amount with deposit, calculates the interest repayment amount on the full repayment date, and calculates the sum of the principal repayment amount with deposit and the interest repayment amount as the full repayment amount with deposit.

Furthermore, in the loan management device of the present invention, the simulation means, based on the billing confirmation data, the contract data, the log data, and the simulation request, if there is a repayment on the scheduled repayment date up to the full repayment date, acquires the log data in which the most recent scheduled repayment date is set as simulation log data, calculates the interest appropriation amount on the scheduled repayment date set in the simulation log data, updates the simulation log data by calculating the new loan balance as the sum of the loan balance and the interest appropriation amount minus the billing amount, acquires the loan balance on the scheduled repayment date immediately before the full repayment date as the deposited principal repayment amount, calculates the deposited interest repayment amount on the full repayment date, and calculates the sum of the deposited principal repayment amount and the deposited interest repayment amount as the deposited full repayment amount.

Furthermore, in the loan management device of the present invention, the simulation means, based on the contract data, the log data, and the simulation request, if the presence or absence of repayment on the scheduled repayment date up to the full repayment date is "no," acquires the loan balance as the principal-free repayment amount, calculates the interest-free repayment amount on the full repayment date, and calculates the sum of the principal-free repayment amount and the interest-free repayment amount as the full repayment amount.

In the loan management device of the present invention, the simulation means is further characterized in that, based on the billing confirmation data, the contract data, the log data, and the simulation request, if the presence or absence of repayment on the scheduled repayment date up to the full repayment date is "no," the simulation means obtains the loan balance as the principal-free repayment amount, calculates the interest-free repayment amount on the full repayment date, calculates the sum of the principal-free repayment amount and the interest-free repayment amount as the full repayment amount without deposit, and obtains the comparison result between the full repayment amount with deposit and the full repayment amount without deposit.

Furthermore, in the loan management device according to the present invention, the simulation means is further characterized in that it displays a billing amount inquiry screen in which the simulated full repayment amount is set.

In addition, in the loan management device according to the present invention, the request acquisition means displays a billing amount inquiry screen on which the user can set whether or not to repay the full repayment date and the scheduled repayment dates up to the full repayment date, and acquires the simulation request.

The loan management method of the present invention is a loan management method executed by a loan management device equipped with a memory unit and a control unit, wherein the memory unit includes a contract storage means for storing contract data that sets the loan amount, loan interest rate, and agreed repayment date of a small loan, and a log storage means for storing log data that links transaction dates including the agreed repayment date and the loan balance, and the method includes a request acquisition step executed by the control unit for acquiring a simulation request that sets the full repayment date and whether or not repayment will be made on the agreed repayment date up to the full repayment date, and a simulation step for calculating the simulated full repayment amount of the small loan on the full repayment date based on the contract data, the log data, and the simulation request.

The loan management program of the present invention is a loan management program to be executed by a loan management device having a memory unit and a control unit, wherein the memory unit comprises a contract storage means for storing contract data that sets the loan amount, loan interest rate, and agreed repayment date of a small loan, and a log storage means for storing log data that links transaction dates including the agreed repayment date and the loan balance, and the control unit executes a request acquisition step for acquiring a simulation request that sets the full repayment date and whether or not repayment will be made on the agreed repayment date up to the full repayment date, and a simulation step for calculating the simulated full repayment amount of the small loan on the full repayment date based on the contract data, the log data, and the simulation request.

The present invention has the effect of meeting the debtor's financial planning needs by allowing the debtor to accurately grasp the future full repayment amount. Furthermore, the present invention has the effect of enabling the debtor to accurately carry out financial planning, which leads to the prevention of delinquencies and bad debts, thereby improving the recovery rate of loans and interest. Furthermore, the present invention has the effect of meeting the debtor's needs while preventing the creditor (finance company) from the risk of bad debts, thereby contributing to the creditor's management efficiency. Furthermore, the present invention has the effect of providing a system for managing personal loans from the perspective of a finance company, which allows the creditor to properly collect interest, a source of revenue. Furthermore, the present invention has the effect of meeting the debtor's financial planning needs by allowing the debtor to accurately grasp the future full repayment amount. Furthermore, the present invention has the effect of enabling the debtor to accurately grasp the future full repayment amount by performing a simulation by switching between treating the payment as having been made or not made on the scheduled repayment date, if there is a scheduled repayment date before the full repayment date. Furthermore, according to the present invention, by virtually maintaining a transaction log and virtually updating the transaction log for the deposit transaction processing on the contract date, it is possible to use the updated transaction log data to simulate the full repayment amount on the specified date (full repayment date).

FIG. 1 is a diagram showing an example of a simulation schedule in this embodiment. FIG. 2 is a diagram showing an example of a simulation schedule in this embodiment. FIG. 3 is a block diagram showing an example of the configuration of the loan management device according to this embodiment. FIG. 4 is a flowchart showing an example of the processing of the loan management apparatus according to this embodiment. FIG. 5 is a diagram showing an example of a loan management process according to this embodiment. FIG. 6 is a diagram showing an example of a loan management process according to this embodiment. FIG. 7 is a diagram showing an example of a loan management process according to this embodiment. FIG. 8 is a diagram showing an example of a loan management process according to this embodiment. FIG. 9 is a diagram showing an example of the loan management process in this embodiment. FIG. 10 is a diagram showing an example of a loan management process according to this embodiment. FIG. 11 is a diagram showing an example of a loan management process according to this embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to this embodiment.

[1. Overview]
First, an overview of the present invention will be described with reference to Figures 1 and 2. Figures 1 and 2 are diagrams showing an example of a simulation schedule in this embodiment.

The money lending industry has traditionally been active in small loans to individuals, and when full repayments are made after the next repayment date, there is a growing need to know the full repayment amount when it is debited from the account on the next repayment date.

However, previously, if there was a deduction date between now and the full repayment date, the calculated full repayment amount for the full repayment date did not take the deduction date into account, and the logic for calculating interest from the deduction date to the full repayment date was not established as a function.

The full repayment amount calculation simulation function in this embodiment provides a mechanism that allows for calculation simulation of the full repayment amount as of a specified date, and for two scenarios: when there is an agreed repayment date (withdrawal date) by the specified date and when there is or is not an agreed repayment.

As shown in Figure 1, in this embodiment, if the full repayment date, on which the debtor wishes to repay the full amount, is before the withdrawal date, the full repayment amount is calculated without any deposits being made until the full repayment date.

Also, as shown in Figure 2, in this embodiment, if the full repayment date is after the withdrawal date, you can select whether or not you will receive a deposit on the withdrawal date, and the full repayment amount will be calculated to reflect that selection.

2. Configuration
An example of the configuration of the loan management device 100 according to this embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing an example of the configuration of the loan management device 100 according to this embodiment.

As shown in FIG. 3, the loan management device 100 is a commercially available desktop personal computer. Note that the loan management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The loan management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the loan management device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the loan management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has the function of communicating data with other devices via the communication line. Here, the network 300 has the function of connecting the loan management device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network).

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in conjunction with a mouse. Note that, below, the output device 114 may be referred to as the monitor 114 or the printer 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The memory unit 106 stores various databases, tables, files, and the like. The memory unit 106 also stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The memory unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The memory unit 106 includes a contract database 106a and a log database 106b.

The contract database 106a stores contract data for small loans. Here, the contract database 106a may store contract data that sets the small loan contract number, loan amount, loan interest rate, and scheduled repayment date.

Log database 106b stores log data for small loans. Here, log database 106b may store log data linked to the transaction date, including the scheduled repayment date of the small loan, and the loan balance. Here, the log data may include the contract number, serial number, data category, transaction date, loan amount, loan interest rate, principal allocation amount, interest allocation amount, and loan balance.

The control unit 102 is a CPU or the like that provides overall control of the loan management device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs. Functionally, the control unit 102 includes a billing acquisition unit 102a, a request acquisition unit 102b, and a simulation unit 102c.

The billing acquisition unit 102a acquires billing data for small loans. Here, the billing acquisition unit 102a may acquire final billing data that sets the billing amount for the scheduled repayment dates up to the full repayment date for the small loan. Here, the final billing data may be set in association with the contract number, billing date, and billing amount. The billing acquisition unit 102a may also acquire deduction request data for the small loan. Here, the deduction request data may be set in association with the customer number, scheduled repayment date, and billing amount.

The request acquisition unit 102b acquires a loan repayment simulation request. Here, the request acquisition unit 102b may acquire a simulation request that sets the full repayment date and whether or not repayment will occur on the scheduled repayment dates up to the full repayment date. The request acquisition unit 102b may also acquire a simulation request by displaying a billing amount inquiry screen that allows the user to set the full repayment date and whether or not repayment will occur on the scheduled repayment dates up to the full repayment date.

The simulation unit 102c calculates the simulated full repayment amount for the small loan on the full repayment date based on the contract data, log data, and simulation request. Here, the simulation unit 102c may calculate the simulated full repayment amount for the small loan on the full repayment date based on the contract data, log data, and simulation request. Furthermore, if there is a repayment or non-repayment on the scheduled repayment date up to the full repayment date based on the billing confirmation data, contract data, log data, and simulation request, the simulation unit 102c may calculate the interest appropriation amount for that scheduled repayment date, calculate the new loan balance as the sum of the loan balance and the interest appropriation amount minus the billing amount, obtain the loan balance on the scheduled repayment date immediately before the full repayment date as the principal repayment amount with deposit, calculate the interest repayment amount with deposit on the full repayment date, and calculate the sum of the principal repayment amount with deposit and the interest repayment amount as the full repayment amount with deposit. In addition, based on the billing confirmation data, contract data, log data, and simulation request, if there is a repayment or non-repayment on the scheduled repayment date up to the full repayment date, the simulation unit 102c may obtain the log data in which the most recent scheduled repayment date is set as simulation log data, calculate the amount of interest to be applied on the scheduled repayment date set in the simulation log data, update the simulation log data by calculating the new loan balance as the sum of the loan balance and the interest applied amount minus the billing amount, obtain the loan balance on the scheduled repayment date closest to the full repayment date as the principal repayment amount with deposit, calculate the interest repayment amount on the full repayment date, and calculate the sum of the principal repayment amount with deposit and the interest repayment amount as the full repayment amount with deposit. Furthermore, based on the contract data, log data, and simulation request, if there is no indication of whether a repayment will be made on the scheduled repayment date up to the full repayment date, the simulation unit 102c may acquire the remaining loan balance as the principal-free repayment amount, calculate the interest-free repayment amount on the full repayment date, and calculate the sum of the principal-free repayment amount and the interest-free repayment amount as the full repayment amount. Furthermore, based on the billing confirmation data, contract data, log data, and simulation request, if there is no indication of whether a repayment will be made on the scheduled repayment date up to the full repayment date, the simulation unit 102c may acquire the remaining loan balance as the principal-free repayment amount, calculate the interest-free repayment amount on the full repayment date, calculate the sum of the principal-free repayment amount and the interest-free repayment amount as the full repayment amount, and acquire a comparison result between the full repayment amount with a deposit and the full repayment amount without a deposit. Furthermore, the simulation unit 102c may display a billing amount inquiry screen in which the simulated full repayment amount is set. The simulation unit 102c may also display a billing amount inquiry screen that sets the results of a comparison between the full repayment amount with deposit and the full repayment amount without deposit.

3. Specific Examples
A specific example of this embodiment will be described with reference to FIGS.

[Loan Management Processing]
An example of the loan management process in this embodiment will now be described with reference to Fig. 4. Fig. 4 is a flowchart showing an example of the process of the loan management apparatus 100 in this embodiment.

As shown in FIG. 4, the request acquisition unit 102b displays on the output device 114 a billing amount inquiry screen that allows the user to set the full repayment date and whether or not repayment will occur on the scheduled repayment dates up to the full repayment date via the input device 112, and acquires a simulation request that sets the full repayment date and whether or not repayment will occur on the scheduled repayment dates up to the full repayment date (step SA-1).

The simulation unit 102c then determines whether the simulation request is set to include repayments on the scheduled repayment dates up to the full repayment date (step SA-2).

If the simulation unit 102c determines that the simulation request specifies whether or not repayment will occur on the scheduled repayment dates up to the full repayment date (step SA-2: Yes), it transitions the process to step SA-3.

Then, the simulation unit 102c acquires the log data stored in the log database 106b and the log data for which the most recent contracted repayment date is set based on the simulation request as simulation log data (step SA-3).

The simulation unit 102c then calculates the interest appropriation amount for the scheduled repayment date set in the simulation log data based on the billing confirmation data acquired by the billing acquisition unit 102a and the contract data stored in the contract database 106a, and updates the simulation log data by calculating the new loan balance as the sum of the loan balance and the interest appropriation amount minus the billing amount (step SA-4).

Then, based on the billing confirmation data acquired by the billing acquisition unit 102a, the contract data stored in the contract database 106a, and the simulation request, the simulation unit 102c acquires the loan balance on the scheduled repayment date immediately prior to the full repayment date as the principal repayment amount with deposit, calculates the interest repayment amount on the full repayment date, and calculates the sum of the principal repayment amount with deposit and the interest repayment amount as the full repayment amount with deposit (step SA-5).

The simulation unit 102c then displays the billing amount inquiry screen on the output device 114, with the full repayment amount set (step SA-6), and ends the process.

On the other hand, if the simulation unit 102c determines that the simulation request specifies that there will be no repayment on the scheduled repayment dates up to the full repayment date (step SA-2: No), it transitions the processing to step SA-7.

Then, based on the billing confirmation data acquired by the billing acquisition unit 102a, the contract data stored in the contract database 106a, the log data stored in the log database 106b, and the simulation request, the simulation unit 102c acquires the remaining loan balance as the principal-free repayment amount, calculates the interest-free repayment amount on the full repayment date, and calculates the sum of the principal-free repayment amount and the interest-free repayment amount as the full repayment amount (step SA-7).

The simulation unit 102c then displays the billing amount inquiry screen on the output device 114, with the full repayment amount set to the amount without payment (step SA-8), and ends the process.

Now, with reference to Figures 5 to 8, an example of the loan management process with deposit in this embodiment will be described. Figures 5 to 8 are diagrams showing an example of the loan management process in this embodiment.

As shown in Figures 5 and 6, in this embodiment, when a user specifies 2022/4/20 as the full repayment date via the billing inquiry screen and selects "with deposit simulation" as the deposit availability option, (1) in the simulation log data generation process, the log data with the largest log SEQ (the most recent transaction) is acquired as the simulation log data. Here, the "data category" in this embodiment may be a category that holds the type of transaction.

As shown in Figure 7, in this embodiment, the next scheduled repayment date: 4/5/2022 and the repayment amount: 40,000 yen are identified from the confirmed billing data. Note that in this embodiment, if the confirmed billing data cannot be obtained, the billing amount set in the withdrawal request data is identified as the repayment amount. As shown in Figures 5 and 7, in this embodiment, (2) as a deposit simulation, the simulation log data is updated assuming that a repayment will occur on the scheduled repayment date. Here, as shown in Figure 7, in this embodiment, the confirmed billing data identifies the repayment amount as 40,000 yen.

As shown in Figures 5 and 8, in this embodiment, (3) a billing amount calculation simulation is performed to calculate the billing amount in the case of repayment on April 20, 2022, from the simulation log data updated in (2).

As shown in Figure 5, in this embodiment, the repayment amount calculated by the billing amount calculation is displayed on the billing amount inquiry screen.

Furthermore, an example of the deposit/no-loan management process in this embodiment will be described with reference to Figures 9 to 11. Figures 9 to 11 are diagrams showing an example of the loan management process in this embodiment.

As shown in Figures 9 and 10, in this embodiment, if the user specifies 2022/4/20 as the full repayment date via the billing inquiry screen and selects "No deposit simulation" as the deposit availability, (1) the log data acquisition process acquires the log data with the largest log SEQ (the most recent transaction).

As shown in Figures 9 and 11, in this embodiment, (2) a billing amount calculation simulation is performed to calculate the billing amount in the case of repayment on April 20, 2022, from the log data in (1).

As shown in Figure 9, in this embodiment, the repayment amount calculated by the billing amount calculation is displayed on the billing amount inquiry screen.

[4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

5. Other Embodiments
The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the loan management device 100, the components shown in the figure are functional concepts and do not necessarily have to be physically configured as shown.

For example, all or any part of the processing functions of the loan management device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the loan management device 100 as needed. That is, a computer program that works in conjunction with the OS to issue commands to the CPU and perform various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and works in conjunction with the CPU to form the control unit.

In addition, this computer program may be stored on an application program server connected to the loan management device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes memory cards, USB (Universal Serial Bus) memories, 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 more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

The various databases stored in the memory unit 106 are storage devices such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

The loan management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as such an information processing device to which any peripheral device is connected. The loan management device 100 may also be implemented by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments may be implemented in any combination, or embodiments may be implemented selectively.

The present invention is useful in industries such as the financial industry, including non-banking industries, where money lending can be conducted.

REFERENCE SIGNS LIST 100 Loan management device 102 Control unit 102a Bill acquisition unit 102b Request acquisition unit 102c Simulation unit 104 Communication interface unit 106 Storage unit 106a Contract database 106b Log database 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (9)

A loan management device including a memory unit and a control unit,
The storage unit
a contract storage means for storing contract data that sets the loan amount, loan interest rate, and contract repayment date of the small loan;
a log storage means for storing log data set in association with transaction dates including the scheduled repayment date and loan balances;
Equipped with
The control unit
a request acquisition means for acquiring a simulation request that sets the full repayment date and whether or not repayment will occur on the scheduled repayment dates up to the full repayment date;
a simulation means for calculating a simulated full repayment amount of the small loan on the full repayment date based on the contract data, the log data, and the simulation request;
A loan management device comprising: The control unit
a claim acquisition means for acquiring claim determination data that sets the claim amount for the contracted repayment date up to the full repayment date;
Further provided with
The simulation means
The loan management device of claim 1, characterized in that if there is a repayment on the scheduled repayment date up to the full repayment date based on the billing confirmation data, the contract data, the log data, and the simulation request, the device calculates the amount of interest to be applied on the scheduled repayment date, calculates the new loan balance by subtracting the billing amount from the sum of the loan balance and the interest applied amount, obtains the loan balance on the scheduled repayment date immediately before the full repayment date as the principal repayment amount with deposit, calculates the interest repayment amount on the full repayment date, and calculates the sum of the principal repayment amount with deposit and the interest repayment amount as the full repayment amount with deposit. The simulation means
3. The loan management device according to claim 2, characterized in that, if there is a repayment on the scheduled repayment date up to the full repayment date based on the billing confirmation data, the contract data, the log data, and the simulation request, the log data in which the most recent scheduled repayment date is set is obtained as simulation log data, the interest appropriation amount on the scheduled repayment date set in the simulation log data is calculated, the amount obtained by subtracting the billing amount from the sum of the loan balance and the interest appropriation amount is calculated as the new loan balance, the simulation log data is updated, the loan balance on the scheduled repayment date that is most recent before the full repayment date is obtained as the principal repayment amount with deposit, the interest repayment amount on the full repayment date is calculated, and the sum of the principal repayment amount with deposit and the interest repayment amount is calculated as the full repayment amount with deposit. The simulation means
The loan management device described in claim 1, characterized in that, based on the contract data, the log data, and the simulation request, if there is no repayment on the scheduled repayment date up to the full repayment date, the loan balance is obtained as the principal-free repayment amount, the interest-free repayment amount on the full repayment date is calculated, and the sum of the principal-free repayment amount and the interest-free repayment amount is calculated as the full repayment amount without deposit. The simulation means
Furthermore, based on the billing confirmation data, the contract data, the log data, and the simulation request, if the repayment status on the scheduled repayment date up to the full repayment date is no, the loan balance is obtained as the principal-free repayment amount, the interest-free repayment amount on the full repayment date is calculated, the sum of the principal-free repayment amount and the interest-free repayment amount is calculated as the full repayment amount without deposit, and the comparison result between the full repayment amount with deposit and the full repayment amount without deposit is obtained. The simulation means
2. The loan management device according to claim 1, further comprising: a request amount inquiry screen in which the simulated full repayment amount is set. The request acquisition means
The loan management device according to claim 1 or 2, characterized in that it displays a billing amount inquiry screen on which it is possible to set whether or not to repay on the full repayment date and the scheduled repayment dates up to the full repayment date, and acquires the simulation request. A loan management method to be executed by a loan management device having a storage unit and a control unit,
The storage unit
a contract storage means for storing contract data that sets the loan amount, loan interest rate, and contract repayment date of the small loan;
a log storage means for storing log data set in association with transaction dates including the scheduled repayment date and loan balances;
Equipped with
Executed in the control unit:
a request acquisition step of acquiring a simulation request that sets the full repayment date and whether or not repayment will be made on the scheduled repayment dates up to the full repayment date;
a simulation step of calculating a simulated full repayment amount of the small loan on the full repayment date based on the contract data, the log data, and the simulation request;
A loan management method comprising: A loan management program to be executed by a loan management device having a storage unit and a control unit,
The storage unit
a contract storage means for storing contract data that sets the loan amount, loan interest rate, and contract repayment date of the small loan;
a log storage means for storing log data set in association with transaction dates including the scheduled repayment date and loan balances;
Equipped with
In the control unit,
a request acquisition step of acquiring a simulation request that sets the full repayment date and whether or not repayment will be made on the scheduled repayment dates up to the full repayment date;
a simulation step of calculating a simulated full repayment amount of the small loan on the full repayment date based on the contract data, the log data, and the simulation request;
Loan management program to implement.