JP7804563B2 - Loan management system, loan management method, and loan management program - Google Patents

Description

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

For example, when a change occurs to a loan repayment schedule (i.e., recalculation of monthly repayment schedule), the contract must be terminated (i.e., paid off in full) and the repayment schedule must be re-registered (i.e., calculated) based on the new contract terms. A conventional system for changing a loan repayment schedule is disclosed, for example, in Patent Document 1.

Japanese Patent Application Laid-Open No. 2021-140525

However, the above-mentioned Patent Document 1 does not state anything about flexibly rearranging repayment schedule data in accordance with the debtor's circumstances.

The present invention was made in consideration of the above, and aims to provide a loan management system, loan management method, and loan management program that can flexibly rearrange repayment schedule data according to the borrower's circumstances.

To solve the above-mentioned problems and achieve the objectives, the present invention provides a loan management system equipped with a control unit, which is configured to be able to access repayment schedule data including customer numbers, number of repayments, scheduled repayment dates, repayment amounts, principal repayment amounts, interest repayment amounts, monthly loan balances, bonus loan balances, and loan interest rates, and which is characterized by having a repayment schedule reorganization means that, when a reorganization category and reorganization start date are specified for a target customer number on the repayment schedule reorganization screen, reorganizes the repayment schedule data for the target customer number based on the specified reorganization category and reorganization start date.

Furthermore, according to one aspect of the present invention, the restructuring classification may include a change from no bonus repayment to bonus repayment, a change from bonus repayment to no bonus repayment, a reduction in repayment amount for a fixed period in which only interest is repaid, or a reduction in repayment amount for a fixed period in which principal and interest are repaid.

Furthermore, according to one aspect of the present invention, when the restructuring category is changed from "without bonus repayment" to "with bonus repayment," and the restructuring start date, monthly post-restructuring balance, and bonus month are specified on the restructuring schedule screen, the restructuring means leaves the restructuring schedule before the restructuring start date unchanged, and recalculates the restructuring schedule by dividing the balance from the restructuring start date onwards into monthly and bonus payments.In this case, it may also be possible to calculate in advance how many bonus payments will arrive by the final monthly repayment date, and reverse-calculate the repayment amount per bonus payment to restruct the restructuring schedule data.

Furthermore, according to one aspect of the present invention, when the restructuring category is changed from "with bonus repayment" to "without bonus repayment," and a restructuring start date is specified on the restructuring schedule screen, the restructuring means may leave the restructuring schedule before the restructuring start date unchanged, add the bonus balance as of the restructuring start date to the monthly balance, recalculate the restructuring schedule based on the monthly repayment amount before the restructuring, and restructure the restructuring schedule data.

Furthermore, according to one aspect of the present invention, when a fixed period of reduced repayment amounts with interest-only repayments is specified as the repayment classification, the repayment schedule restructuring means may, when the repayment start date and reduction period are specified on the repayment schedule restructuring screen, calculate a repayment schedule from the repayment start date onwards in which only interest is repaid during the reduced period, leaving the repayment schedule before the restructuring start date unchanged, and after the reduction period ends, recalculate the repayment schedule based on the monthly repayment amount before the restructuring, and restructure the repayment schedule data.

Furthermore, according to one aspect of the present invention, when a fixed period of repayment amount reduction for repayment of principal and interest is specified as the repayment type, and the repayment start date, reduction period, and reduced monthly repayment amount are specified on the repayment schedule recalculation screen, the repayment schedule recalculation means may leave the repayment schedule before the repayment start date unchanged, and calculate a repayment schedule from the repayment start date onwards in which the repayment amount per reduction period is the reduced monthly repayment amount, and after the reduction period ends, recalculate the repayment schedule based on the monthly repayment amount before the recalculation, and reorganize the repayment schedule data.

Furthermore, to solve the above-mentioned problems and achieve the objectives, the present invention provides a loan management method executed by an information processing device equipped with a control unit, wherein the control unit is configured to be able to access repayment schedule data including customer number, number of repayments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, monthly loan balance, bonus loan balance, and loan interest rate, and the method includes a repayment schedule reorganization step executed by the control unit, which, when a reorganization category and reorganization start date are specified for a target customer number on a repayment schedule reorganization screen, reorganizes the repayment schedule data for the target customer number based on the specified reorganization category and reorganization start date.

Furthermore, to solve the above-mentioned problems and achieve the objectives, the present invention provides a loan management program to be executed by an information processing device equipped with a control unit. The control unit is configured to be able to access repayment schedule data including customer number, number of repayments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, monthly loan balance, bonus loan balance, and loan interest rate. When a repayment schedule reorganization category and reorganization start date are specified for a target customer number on a repayment schedule reorganization screen executed by the control unit, the loan management program executes a repayment schedule reorganization process that reorganizes the repayment schedule data for the target customer number based on the specified reorganization category and reorganization start date.

The present invention has the advantage of making it possible to flexibly rearrange repayment schedule data according to the debtor's circumstances.

FIG. 1 is a block diagram showing an example of the configuration of a loan management system according to this embodiment. FIG. 2 is a flowchart for explaining an outline of the overall processing of the control unit of the loan management system according to this embodiment. FIG. 3 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 4 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 5 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 6 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 7 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 8 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 9 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to the present embodiment. FIG. 11 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 12 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 13 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 14 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 15 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 16 is a diagram for explaining a specific example of the processing of the control unit of the loan management system according to this embodiment. FIG. 17 is a diagram for explaining a specific example of the processing of the control unit of the loan management system 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]
For example, monthly repayments are calculated based on the details of the loan agreement, so if there are any changes to the repayment terms, a business contract must be signed.

As a result, when a change occurred to the repayment schedule (i.e., recalculation of monthly repayments), the contract had to be terminated (i.e., paid off in full) and the repayment schedule had to be recalculated based on the new contract terms. The system also recognized it as a separate contract.

In this case, the loan amount (= balance immediately before the change) and contract date (= change date) registered after the repayment schedule change would differ from the contents of the contract signed at the time, causing problems with various external collaborations.

While some changes to repayment schedules can already be handled using existing technology, primarily due to interest rate fluctuations and early repayments, this embodiment provides a loan management system that can flexibly rearrange repayment schedule data (for example, changing whether or not a bonus is given, or reducing repayment amounts for a certain period of time) depending on the borrower's circumstances (for example, the current COVID-19 situation, etc.).

When restructuring repayment schedules, the restructuring is not carried out immediately after the debtor's request, but rather after discussion with the debtor. In this embodiment of the loan management system, when restructuring is carried out, it is possible to specify "when" the restructuring should begin and what the "repayment amount" should be after the restructuring.

In addition, since repayment schedules are often simulated when discussing with debtors, simulations can also be performed.

In this embodiment, when rearranging repayment schedules, the following rearrangements are possible:

(1) No bonus repayment → Bonus repayment (2) Bonus repayment → No bonus repayment (3) Repayment amount reduced for a certain period (I) Repayment of interest only (principal repayment is deferred)
(II) Repay the principal + interest (reduce the amount of principal repayment)

The loan management system of this embodiment is widely applicable to the lending industry, including the financial and non-banking industries that handle deed loan products such as mortgages.

2. Configuration
FIG. 1 is a block diagram showing an example of the configuration of a loan management system 100 according to this embodiment. The loan management system 100 is, for example, a commercially available desktop personal computer. Note that the loan management system 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer. In FIG. 1 , the loan management system 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108. The units included in the loan management system 100 are connected to each other so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the loan management system 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 system 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 home television), 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.

The memory unit 106 stores various databases, tables, files, and the like. The memory unit 106 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 stores various data such as loan information data, repayment schedule data, and deposit data.

Loan information data may include the contract date, loan date, loan amount, loan interest rate, repayment method, bonus payment, bonus month, contract date, number of repayments, monthly repayment amount, bonus repayment amount, first repayment date, customer number, and contract number.

The repayment schedule data may include the customer number, branch number, number of payments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, loan balance (monthly), loan balance (bonus), and loan interest rate.

Deposit data may include the deposit date, deposit amount, principal application amount, interest application amount, loan balance, customer number, and branch number.

The control unit 102 is a CPU or the like that provides overall control of the loan management system 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 performs various information processing operations based on these stored programs.

The control unit 102 is configured to be able to access loan information data, repayment schedule data, etc. stored in the memory unit 106. Note that the loan information data, repayment schedule data, etc. may also be stored elsewhere (e.g., on the server 200), as long as the control unit 102 is able to access it.

Functionally, the control unit 102 comprises an application input unit 102a, a deposit processing unit 102b, a repayment schedule reorganization unit 102c, and a screen display control unit 102d.

When an application for a loan contract is made, the application input unit 102a inputs loan information data and repayment schedule data in response to, for example, an operator's operations on the loan information input screen displayed on the monitor 114, and registers the data in the memory unit 106.

When a deposit is made, the deposit processing unit 102b inputs the deposit data in response to, for example, an operator's operation on the deposit input screen displayed on the monitor 114, and registers the data in the memory unit 106.

When an application for repayment schedule reorganization is made, the repayment schedule reorganization unit 102c reorganizes the repayment schedule data, for example, in response to an operator's operation on the repayment schedule reorganization screen displayed on the monitor 114.

In this case, when a reorganization category and reorganization start date are specified for the target customer number on the reorganization schedule reorganization screen, the reorganization schedule reorganization unit 102c may reorganize the reorganization schedule data for the target customer number based on the specified reorganization category and reorganization start date.

In addition, restructuring categories may include switching from no bonus repayments to bonus repayments, from bonus repayments to no bonus repayments, reducing the repayment amount for a certain period with interest only repayments, or reducing the repayment amount for a certain period with principal and interest repayments.

In addition, when the restructuring category is changed from "without bonus repayment" to "with bonus repayment," the repayment schedule restructuring unit 102c, upon specifying the restructuring start date, monthly post-restructuring balance, and bonus month on the repayment schedule restructuring screen, leaves the repayment schedule before the restructuring start date unchanged, and recalculates the repayment schedule by dividing the balance from the restructuring start date onwards into monthly and bonus payments.In this case, it may be possible to calculate in advance how many bonus payments will arrive by the final monthly repayment date, and then reverse-calculate the repayment amount per bonus payment to restruct the repayment schedule data.

In addition, when the restructuring category is changed from "with bonus repayment" to "without bonus repayment," and the restructuring start date is specified on the restructuring schedule screen, the restructuring schedule reorganization unit 102c may leave the restructuring schedule before the restructuring start date unchanged, add the bonus balance as of the restructuring start date to the monthly balance, recalculate the restructuring schedule based on the monthly repayment amount before the restructuring, and restructure the restructuring schedule data.

In addition, when a fixed period of reduced repayment amounts, in which only interest is repaid, is specified as the repayment classification, the repayment schedule reorganization unit 102c may, when the repayment start date and reduction period are specified on the repayment schedule reorganization screen, calculate a repayment schedule in which only interest is repaid during the reduced period from the repayment start date onwards, leaving the repayment schedule before the repayment start date unchanged, and after the reduction period ends, recalculate the repayment schedule based on the monthly repayment amount before the reorganization, and reorganize the repayment schedule data.

In addition, when a fixed period of repayment reduction for repayment of principal and interest is specified as the repayment classification, the repayment schedule reorganization unit 102c may, when the repayment start date, reduction period, and reduced monthly repayment amount are specified on the repayment schedule reorganization screen, leave the repayment schedule before the reorganization start date unchanged, and calculate a repayment schedule from the reorganization start date onwards, with the repayment amount per reduction period as the reduced monthly repayment amount, and after the reduction period ends, recalculate the repayment schedule based on the monthly repayment amount before the reorganization, and reorganize the repayment schedule data.

The screen display control unit 102d controls the display and input reception of various screens (e.g., loan information input screen, deposit screen, repayment schedule reorganization screen, etc.) displayed on the monitor 114.

3. Specific Examples
1 to 17, a specific example of the processing performed by the control unit 102 of the loan management system 100 according to this embodiment will be described.

(3-1. Overall processing)
2 is a diagram showing a flow for explaining an outline of the overall processing flow of the control unit 102 of the loan management system 100 in this embodiment. With reference to FIG. 2, an outline of the overall processing flow (from applying for a loan to rearranging the repayment schedule) of the control unit 102 of the loan management system 100 in this embodiment will be explained.

The application input unit 102a executes the application input process (step S1). Specifically, in the application input process, when an application for a loan contract is received, the application input unit 102a inputs loan information data and repayment schedule data in response to, for example, an operator's operation on the loan information input screen displayed on the monitor 114, and registers the data in the memory unit 106.

The deposit processing unit 102b executes the deposit processing (step S2). Specifically, in the deposit processing, when a deposit is made, the deposit processing unit 102b inputs deposit data in response to, for example, an operator's operation on the deposit input screen displayed on the monitor 114, and registers the data in the memory unit 106.

The repayment schedule reorganization unit 102c executes the repayment schedule reorganization process (step S3). Specifically, in the repayment schedule reorganization process, when an application for repayment schedule reorganization is received, the repayment schedule reorganization unit 102c reorganizes the repayment schedule data in response to, for example, the operator's operations on the repayment schedule reorganization screen displayed on the monitor 114.

In this case, when a reorganization category and reorganization start date are specified for the target customer number on the reorganization schedule reorganization screen, the reorganization schedule reorganization unit 102c may reorganize the reorganization schedule data for the target customer number based on the specified reorganization category and reorganization start date.

In addition, restructuring categories may include switching from no bonus repayments to bonus repayments, from bonus repayments to no bonus repayments, reducing the repayment amount for a certain period with interest only repayments, or reducing the repayment amount for a certain period with principal and interest repayments.

In addition, when the restructuring category is changed from "without bonus repayment" to "with bonus repayment," the repayment schedule restructuring unit 102c, upon specifying the restructuring start date, monthly post-restructuring balance, and bonus month on the repayment schedule restructuring screen, leaves the repayment schedule before the restructuring start date unchanged, and recalculates the repayment schedule by dividing the balance from the restructuring start date onwards into monthly and bonus payments.In this case, it may be possible to calculate in advance how many bonus payments will arrive by the final monthly repayment date, and then reverse-calculate the repayment amount per bonus payment to restruct the repayment schedule data.

In addition, when the restructuring category is changed from "with bonus repayment" to "without bonus repayment," and the restructuring start date is specified on the restructuring schedule screen, the restructuring schedule reorganization unit 102c may leave the restructuring schedule before the restructuring start date unchanged, add the bonus balance as of the restructuring start date before the restructuring start date to the monthly balance, recalculate the restructuring schedule based on the monthly repayment amount before the restructuring, and restructure the restructuring schedule data.

In addition, when a fixed period of reduced repayment amounts, in which only interest is repaid, is specified as the repayment classification, the repayment schedule reorganization unit 102c may, when the repayment start date and reduction period are specified on the repayment schedule reorganization screen, calculate a repayment schedule in which only interest is repaid during the reduced period from the repayment start date onwards, leaving the repayment schedule before the repayment start date unchanged, and after the reduction period ends, recalculate the repayment schedule based on the monthly repayment amount before the reorganization, and reorganize the repayment schedule data.

In addition, when a fixed period of repayment reduction for repayment of principal and interest is specified as the repayment classification, the repayment schedule reorganization unit 102c may, when the repayment start date, reduction period, and reduced monthly repayment amount are specified on the repayment schedule reorganization screen, leave the repayment schedule before the reorganization start date unchanged, and calculate a repayment schedule from the reorganization start date onwards, with the repayment amount per reduction period as the reduced monthly repayment amount, and after the reduction period ends, recalculate the repayment schedule based on the monthly repayment amount before the reorganization, and reorganize the repayment schedule data.

(3-2. Sample data)
3 to 17 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the loan management system 100 in this embodiment. A specific example of the processing by the control unit 102 of the loan management system 100 in this embodiment will be explained with reference to FIGS.

(S1: Application input process)
A specific example of the application input process will be described with reference to Figures 3 to 5. In the application input process, loan information data, which is the various conditions for the loan, is registered based on the application input, and repayment schedule data is calculated, expanded, and registered.

Figure 3 shows an example of loan information data. The loan information data includes the following fields: contract date, loan date, loan amount, loan interest rate, repayment method, bonus payment, bonus month, agreement date, number of repayments, monthly repayment amount, bonus repayment amount, first repayment date, customer number, and contract number. In the example shown in the figure, the contract date is 2022/10/01, loan date is "2022/10/05", loan amount is "35,000,000", loan interest rate is "1.50000%", repayment method is "1: equal principal and interest", bonus payment is "0: none", bonus month is "- month/- month", agreement date is the 15th, number of repayments is 420, monthly repayment amount is "105,000", bonus repayment amount is "-", first repayment date is "2022/12/15", customer number is "123", and contract number is "0000000123-001".

4 is a diagram showing a display example of a loan information input screen. The loan information input screen displays a customer number,
It has a header area for specifying the branch number, contract number, contract date, loan date, loan amount, loan interest rate, repayment method, bonus separate payment, bonus month, contract date, number of repayments, monthly repayment amount, bonus repayment amount, and first repayment date, a repayment schedule creation button, a repayment schedule area where the repayment schedule is displayed, and a registration button (not shown).

The repayment schedule area includes fields for the number of payments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, loan balance (monthly), loan balance (bonus), and loan interest rate.

When you enter data in the header area and press the Create Repayment Schedule button, a repayment schedule based on the input information is calculated and displayed in the repayment schedule area, allowing you to simulate the repayment schedule. When you press the Register button (not shown), loan information data based on the input information in the header area and repayment schedule data based on the repayment schedule displayed in the repayment schedule area are registered.
In the example of the loan information input screen shown in FIG. 4, when a registration button (not shown) is pressed, the loan information data shown in FIG. 3 and the repayment schedule data shown in FIG. 5 are registered.

Figure 5 shows an example of repayment schedule data. The repayment schedule data includes the following fields: customer number, branch number, number of payments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, loan balance (monthly), loan balance (bonus), and loan interest rate.

(S2: Deposit processing)
A specific example of the deposit process will be described with reference to Fig. 6. In the deposit process, when a deposit is made based on the repayment schedule, the deposit is applied to the principal and interest every month.

Figure 6 (A) shows an example of deposit data. The deposit data includes the following fields: deposit date, deposit amount, principal application amount, interest application amount, loan balance, customer number, and branch number. In the example shown in the figure, the deposit date is "2022/12/15", deposit amount is "105,000", principal application amount is "100,000", interest application amount is "5,000", loan balance is "34,900,000", customer number is "123", and branch number is "1".

Figure 6 (B) is a diagram showing an example of the deposit screen display. The deposit screen has fields for entering the following items: customer number, branch number, deposit date, deposit amount, principal allocation amount, interest allocation amount, and loan balance, as well as a register button (not shown). When data is entered into each field and the register button (not shown) is pressed, the deposit data corresponding to the input content is registered. In the case of the input content shown in Figure 6 (B), the deposit data shown in Figure 6 (A) is registered.

(S3: Repayment schedule restructuring process)
A specific example of the repayment schedule reorganization process will be described with reference to FIGS.

The conventional operation is as follows (1) to (2).
(1) Since the repayment schedule created and registered at the application input stage cannot be changed midway, the relevant contract will be paid off in full using a dummy loan.
(2) Information based on the changes will be registered as a new contract when the application is submitted, and the repayment schedule will be calculated (it will be recognized as a separate contract in the system). Therefore, it will be necessary to separately report to external credit information agencies and to external partner companies the details of the link between the old and new contracts.

The operation of this embodiment is as follows.
(1) Compared to conventional operations, this function allows rescheduling of repayment schedules to be completed in one operation.
(2) In addition, with this function, there is no need to pay off the old contract and then register a new contract, eliminating the burden (consideration) of reporting to external credit information agencies and external partner companies.

When a reorganization category and reorganization start date are specified for the target (specified) customer number on the reorganization schedule reorganization screen, the reorganization schedule reorganization unit 102c reorganizes the reorganization schedule data for the target customer number based on the specified reorganization category and reorganization start date. Details of each reorganization category pattern that can be reorganized are provided below.

(1) Changing from No Bonus Repayment to Bonus Repayment The case of changing the repayment schedule from No Bonus Repayment to Bonus Repayment will be described with reference to FIGS. 7 and 8. FIG.

When the repayment schedule reorganization unit 102c is configured on the repayment schedule reorganization screen to change the reorganization category from "without bonus repayment" to "with bonus repayment," and when the reorganization start date, monthly post-reorganization balance, and bonus month are specified, it leaves the repayment schedule before the reorganization start date unchanged and recalculates the repayment schedule by dividing the balance from the reorganization start date onwards into monthly and bonus payments. In this process, it pre-calculates how many bonus payments will be made up until the final monthly repayment date, and reorganizes the repayment schedule data by back-calculating the repayment amount per bonus payment.

Figure 7 shows an example of the repayment schedule reorganization screen. Figure 8 shows an example of repayment schedule data after reorganization.

As shown in Figure 7, the repayment schedule reorganization screen has a header area for specifying the following items: customer number, branch number, contract number, reorganization category, reorganization start date, balance at time of reorganization (monthly), balance at time of reorganization (bonus), reduction period, monthly repayment amount at time of reduction, bonus repayment amount at time of reduction, balance after reorganization (monthly), balance after reorganization (bonus), and bonus month; a repayment schedule creation button; a repayment schedule area where the repayment schedule is displayed; and a registration button (not shown).

When a customer number is specified, the loan information data and repayment schedule data in the storage unit 206 are referenced using the customer number as a key. Reorganization categories can be selected from 1: No bonus → Yes, 2: Bonus → No bonus, 3: Fixed-term reduction (interest only repayment), and 4: Fixed-term reduction (principal + interest). Whether or not items can be entered is controlled according to the reorganization category, reducing the input load and preventing input errors.

If "1: No bonus → Yes" is selected as the restructuring category, the restructuring start date, post-restructuring balance (monthly), and bonus month can be entered, and the operator specifies the restructuring start date, post-restructuring balance (monthly), and bonus month. The contract number (read from the loan information data using the customer number as a key), balance at time of restructuring (monthly), and post-restructuring balance (bonus) are automatically displayed (and cannot be changed), and all other items cannot be entered.

The repayment schedule area includes fields for the number of payments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, loan balance (monthly), loan balance (bonus), and loan interest rate. When you press the Create Repayment Schedule button, calculations are performed to rearrange the repayment schedule data for the specified customer number based on the input in the header area, and the data is displayed in the repayment schedule area, allowing you to simulate the repayment schedule.

In the example shown in the figure, the operator has specified customer number "123," restructuring start date "2023/03/15," post-restructuring balance (monthly) "24,000,000," and bonus month "6/12." Using customer number "123" as a key, the restructuring schedule data is referenced, and the restructuring balance (monthly) "34,699,700" and post-restructuring balance (bonus) "10,699,700" are automatically calculated and displayed. When the Create Restructuring Schedule button is pressed, the restructuring of the restructuring schedule is calculated and displayed in the restructuring schedule area.

Specifically, as shown in Figure 8, when the reorganization start date, monthly post-reorganization balance, and bonus month are specified, the reorganization start date is left as is, and the balance from the reorganization start date onwards is split into monthly and bonus payments to recalculate the reorganization schedule. During this process, the number of bonus payments due up until the final monthly reorganization date is calculated in advance, and the reorganization schedule data is reorganized by back-calculating the reorganization start date and the monthly reorganization balance.

When the registration button (not shown) is pressed, the restructured repayment schedule data shown in Figure 8 is registered in the memory unit 206.

(2) Changing from With Bonus Repayment to Without Bonus Repayment A case where the repayment schedule is changed from With Bonus Repayment to Without Bonus Repayment will be described with reference to FIGS.

When the repayment schedule reorganization screen changes the reorganization category from "without bonus repayment" to "with bonus repayment," the repayment schedule reorganization unit 102c specifies the reorganization start date, leaves the repayment schedule before the reorganization start date unchanged, adds the bonus balance as of the reorganization start date to the monthly balance, recalculates the repayment schedule based on the monthly repayment amount before the reorganization, and reorganizes the repayment schedule data.

Figure 9 shows an example of repayment schedule data before reorganization, which is registered in the memory unit 206. Figure 10 shows an example of the repayment schedule reorganization screen. Figure 11 shows an example of repayment schedule data after reorganization.

If "2: With bonus → Without bonus" is selected as the repayment schedule recalculation type on the repayment schedule recalculation screen in Figure 10, the recalculation start date can be entered, and the operator specifies the recalculation start date. The contract number, balance at recalculation (monthly), balance at recalculation (bonus), and balance after recalculation (monthly) are automatically displayed (and cannot be changed), and all other items cannot be entered.

In the example shown in the figure, the operator has specified customer number "222" and reorganization start date "2023/03/15." Using customer number "222" as a key, the reorganization schedule data in Figure 9 is referenced, and the balance at reorganization (monthly) of "24,000,000," balance at reorganization (bonus) of "10,699,700," and balance after reorganization (monthly) of "34,699,700" are automatically displayed. When the Create Reorganization Schedule button is pressed, the reorganization of the reorganization schedule is calculated and displayed in the reorganization schedule area.

Specifically, as shown in Figure 11, when a restructuring start date is specified, the repayment schedule before the restructuring start date remains unchanged, the bonus balance as of the restructuring start date is added to the monthly balance, the repayment schedule is recalculated based on the monthly repayment amount before the restructuring, and the repayment schedule data is restructured. In this case, the final repayment date after the restructuring is extended beyond the final repayment date before the restructuring.

When the registration button (not shown) is pressed, the restructured repayment schedule data shown in Figure 11 is registered in the memory unit 206.

(3) Reducing the repayment amount for a certain period of time (I) Repaying only interest (deferring repayment of principal) Referring to Figures 12 to 14, we will explain the case where the repayment amount is reduced for a certain period of time and only interest is repaid.

When a repayment schedule restructuring section 102c specifies a repayment amount reduction for a certain period in which only interest is repaid as a restructuring category on the repayment schedule restructuring screen, the restructuring start date and the reduction period are specified.
The repayment schedule before the start date of restructuring is left as it is, and a repayment schedule in which only interest for the reduced period is repaid is calculated after the start date of restructuring, and after the end of the reduced period, the repayment schedule is recalculated based on the monthly repayment amount before the restructuring, and the repayment schedule data is restructured.

Figure 12 shows an example of repayment schedule data before reorganization, which is registered in the memory unit 206. Figure 13 shows an example of the repayment schedule reorganization screen. Figure 14 shows an example of repayment schedule data after reorganization.

On the repayment schedule restructuring screen in Figure 13, if "3: Fixed period reduction (interest only repayment)" is selected as the restructuring type, the restructuring start date and reduction period can be entered, and the operator specifies the restructuring start date and reduction period. The contract number and balance at the time of restructuring (monthly) are automatically displayed (and cannot be changed), and all other items cannot be entered.

In the example shown in the figure, the operator has specified customer number "345," restructuring start date "2023/03/15," and reduction period "4 months." Using customer number "345" as a key, the repayment schedule data in Figure 12 is referenced, and the balance at the time of restructuring (monthly) of "34,699,700" is automatically displayed. When the Create Repayment Schedule button is pressed, the restructuring of the repayment schedule is calculated and displayed in the repayment schedule area.

Specifically, as shown in Figure 14, when the restructuring start date and reduction period are specified, the repayment schedule before the restructuring start date remains unchanged, and a repayment schedule is calculated from the restructuring start date onwards, with only the interest for the reduction period being repaid. In this case, there is no principal repayment, so the balance does not decrease. After the reduction period ends, the repayment schedule is recalculated based on the monthly repayment amount before the restructuring, and the repayment schedule data is restructured. In this case, the final repayment date after the restructuring will be longer than the final repayment date before the restructuring.

When the registration button (not shown) is pressed, the restructured repayment schedule data shown in Figure 14 is registered in the memory unit 206.

(II) Repayment of Principal and Interest (Reducing the Amount of Principal Repayment) Referring to FIGS. 15 to 17, a case where the amount of repayment is reduced for a certain period and the principal and interest are repaid will be described.

When a fixed period of repayment reduction for principal and interest repayments is specified as the repayment classification on the repayment schedule recalculation screen, and the repayment start date, reduction period, and reduced monthly repayment amount are specified, the repayment schedule recalculation unit 102c leaves the repayment schedule before the recalculation start date unchanged, and calculates a repayment schedule from the recalculation start date onwards, with the repayment amount per reduction period as the reduced monthly repayment amount; after the reduction period ends, the repayment schedule is recalculated based on the monthly repayment amount before the recalculation, and recalculates the repayment schedule data.

Figure 15 shows an example of repayment schedule data registered in the storage unit 206 before reorganization. Figure 16 shows an example of the repayment schedule reorganization screen. Figure 17 shows an example of repayment schedule data after reorganization.

On the repayment schedule restructuring screen in Figure 16, if "4: Fixed period reduction (principal + interest)" is selected as the restructuring type, the restructuring start date, reduction period, and monthly repayment amount at the time of reduction can be entered, and the operator specifies the restructuring start date, reduction period, and monthly repayment amount at the time of reduction. The contract number and balance at the time of restructuring (monthly) are automatically displayed (and cannot be changed), and all other items cannot be entered.

In the example shown in the figure, the operator has specified customer number "404," restructuring start date "2023/03/15," reduction period "4 months," and monthly repayment amount at time of reduction "50,000." Using customer number "404" as a key, the repayment schedule data in Figure 15 is referenced, and the balance at time of restructuring (monthly) of "34,699,700" is automatically displayed. When the Create Repayment Schedule button is pressed, the restructuring of the repayment schedule is calculated and displayed in the repayment schedule area.

Specifically, as shown in Figure 17, when the restructuring start date, reduction period, and reduced monthly repayment amount are specified, the repayment schedule before the restructuring start date remains unchanged, and from the restructuring start date onwards, a repayment schedule is calculated in which the repayment amount per reduction period is set as the reduced monthly repayment amount. After the reduction period ends, the repayment schedule is recalculated based on the monthly repayment amount before the restructuring, and the repayment schedule data is restructured. In this case, the final repayment date after the restructuring will be longer than the final repayment date before the restructuring.

When the registration button (not shown) is pressed, the restructured repayment schedule data shown in Figure 17 is registered in the memory unit 206.

As explained above, according to this embodiment, when a reorganization category and reorganization start date are specified for the target customer number on the repayment schedule reorganization screen, the repayment schedule reorganization unit 102c is provided, which reorganizes the repayment schedule data for the target customer number based on the specified reorganization category and reorganization start date, making it possible to flexibly reorganize repayment schedule data according to the debtor's circumstances.

[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.

In addition, 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 system 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 system 100, particularly the processing functions performed by the control unit, 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 system 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 system 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 the embodiments, as well as the installation procedure after reading, can use well-known structures and procedures.

The various databases stored in the memory unit 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 system 100 may also be configured as an information processing device such as a known personal computer or workstation, or as such an information processing device to which any peripheral device is connected. The loan management system 100 may also be realized by installing software (including programs, data, etc.) that causes such a 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.

100 Loan management system 102 Control unit 102a Application input unit 102b Deposit processing unit 102c Repayment schedule reorganization unit 102d Screen display control unit 104 Communication interface unit 106 Storage unit 108 Input/output interface unit 112 Input device 114 Output device 300 Network

Claims (7)

A loan management system including a control unit,
The control unit
It is configured to allow access to repayment schedule data including customer number, number of repayments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, monthly loan balance, bonus loan balance, and loan interest rate.
a repayment schedule reorganization means for reorganizing the repayment schedule data of a target customer number based on the reorganization category and reorganization start date specified on the repayment schedule reorganization screen,
A loan management system characterized in that the restructuring classification includes a change from no bonus repayment to bonus repayment, a change from bonus repayment to no bonus repayment, a reduction in repayment amount for a certain period of time with repayment of interest only, or a reduction in repayment amount for a certain period of time with repayment of principal and interest . 2. The loan management system of claim 1, wherein when the restructuring category is changed from "without bonus repayment" to "with bonus repayment," and the restructuring start date, monthly post-restructuring balance, and bonus month are specified on the restructuring schedule screen, the repayment schedule restructuring means leaves the repayment schedule before the restructuring start date unchanged and divides the balance from the restructuring start date onwards into monthly and bonus payments to recalculate the repayment schedule, and in this case, calculates in advance how many bonus payments will arrive until the final monthly repayment date, and reverse-calculates the repayment amount per bonus payment to restructure the repayment schedule data. The loan management system of claim 1, characterized in that when the restructuring category is changed from with bonus repayment to without bonus repayment, and a restructuring start date is specified on the restructuring schedule screen, the repayment schedule restructuring means leaves the repayment schedule before the restructuring start date unchanged, adds the bonus balance as of the restructuring start date to the monthly balance, recalculates the repayment schedule based on the monthly repayment amount before the restructuring, and restructures the repayment schedule data. The loan management system described in claim 1, characterized in that when the restructuring category is specified as a fixed period of reduced repayment amounts with interest-only repayments, and the restructuring start date and reduced period are specified on the restructuring schedule screen, the repayment schedule restructuring means calculates a repayment schedule in which only interest is repaid during the reduced period from the restructuring start date onwards, leaving the repayment schedule before the restructuring start date unchanged, and after the reduced period ends, recalculates the repayment schedule based on the monthly repayment amount before the restructuring, and restructures the repayment schedule data. The loan management system described in claim 1, characterized in that when the restructuring category specifies a fixed period of repayment amount reduction for repayment of principal and interest, and the restructuring start date, reduction period, and reduced monthly repayment amount are specified on the restructuring schedule screen, the repayment schedule restructuring means calculates a repayment schedule from the restructuring start date onwards, leaving the repayment schedule before the restructuring start date unchanged, with the repayment amount per reduction period set as the reduced monthly repayment amount, and after the reduction period ends, recalculates the repayment schedule based on the monthly repayment amount before the restructuring, and restructures the repayment schedule data. A loan management method executed by an information processing device having a control unit,
The control unit
It is configured to allow access to repayment schedule data including customer number, number of repayments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, monthly loan balance, bonus loan balance, and loan interest rate.
Executed in the control unit:
a repayment schedule reorganization step for reorganizing the repayment schedule data of the target customer number based on the reorganization category and the reorganization start date specified for the target customer number on the repayment schedule reorganization screen;
A loan management method characterized in that the restructuring classification includes a change from no bonus repayment to bonus repayment, a change from bonus repayment to no bonus repayment, a reduction in repayment amount for a certain period of time with repayment of interest only, or a reduction in repayment amount for a certain period of time with repayment of principal and interest . A loan management program to be executed by an information processing device having a control unit,
The control unit
It is configured to allow access to repayment schedule data including customer number, number of repayments, scheduled repayment date, repayment amount, principal repayment amount, interest repayment amount, monthly loan balance, bonus loan balance, and loan interest rate.
The control unit
A loan management program for executing a repayment schedule reorganization process that reorganizes the repayment schedule data of a target customer number based on the reorganization category and reorganization start date specified for the target customer number on a repayment schedule reorganization screen,
A loan management program characterized in that the restructuring classification includes a change from no bonus repayment to bonus repayment, a change from bonus repayment to no bonus repayment, a reduction in repayment amount for a certain period of time with repayment of interest only, or a reduction in repayment amount for a certain period of time with repayment of principal and interest.